[syslog-ng] segfault upon starting

Balazs Scheidler bazsi at balabit.hu
Wed Mar 14 21:08:23 CET 2012


On Sun, 2012-03-04 at 11:40 +0100, Jenei Gábor wrote:
> Hello,
> 
> On friday I said about this problem already, but now I could captured 
> some messages by rsyslog(it has other logfiles set manually than 
> syslog-ng). So, syslog-ng sends the following messages upon its init:
> 
> Mar  4 11:32:18 gabor-netbook supervise/syslog-ng[18834]: Daemon exited 
> due to a deadlock/signal/failure, restarting; exitcode='11'
> 
> Mar  4 11:32:19 gabor-netbook kernel: [ 3039.971733] syslog-ng[21594]: 
> segfault at 8f95000 ip b74ce758 sp bfd86e88 error 4 in 
> libc-2.13.so[b73be000+153000]
> 
> Do you know what the problem is? Maybe I should disable linux 
> capabilities?(actually I am using linux mint, so it should work though)
> I'm using version 3.4 complied on my own, so there maybe some 
> configuration issues.
> 

I've just committed a couple of patches to 3.4, that should fix a number
of segfaults in the 3.4 tree.

Otherwise if you could produce a backtrace that'd help tremendously.

gdb syslog-ng core
(gdb) bt full

-- 
Bazsi




More information about the syslog-ng mailing list