[syslog-ng]syslog-ng dies randomly on solaris

[Balazs Scheidler]

On Wed, 2005-03-16 at 14:01 -0800, Ian Veach wrote:
> Greetings -
> 
> We're just chomping at the bit to switch to syslog-ng from the standard
> syslog.  Although it sounds like plenty of solaris people are having
> success, our testing is not going well.  Our configs are all great, but
> syslog-ng just simply stops running at random times (sometimes an hour,
> the last one 35 days) on my test machine (low volume except for
> occasional load testing).  Can anyone give me (a neophyte in this arena)
> any ideas on how to fix this?
> 
> Ideally, I would like to solve the problem (or figure out what it is), but
> am open to things like a cron to verify syslog-ng is running...Could try
> to debug, but not great with truss, and for some reason syslog-ng cores
> don't show much useful info (to me, a noob).
> 
> Syslog-ng 1.6.5 and libol version required at the time
> 	standard compile for solaris (details available)
> Solaris 9, recently patched

can you show the core file nevertheless? the best would be to compile
both libol and syslog-ng with debug information (--enable-debug
configure switch) let it run with ulimit -c unlimited and then try to
analyze the core files using gdb

gdb -c /path/to/core.file
(gdb) bt

-- 
Bazsi