2013/7/19 Adam Carter <adamcart...@gmail.com>: >> > syslog-ng[32015]: segfault at 44d8 ip 00007f4f3fa23c83 sp >> > 00007fffb233b940 error 4 in libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000 >> > +67000] >> > >> > Has anybody else seen anything like that? > > > Perhaps you forgot to restart syslog-ng after the update? > > # ldd /usr/sbin/syslog-ng | grep libsyslog-ng > libsyslog-ng-3.4.2.so => /usr/lib64/libsyslog-ng-3.4.2.so > (0x00007fe7dfe5b000) > > If the library was called libsyslog-ng.so.0.0.0 in the previous version, and > if syslog-ng tried to reload it, it would fail after the update which could > cause the segfault. > > So, restarting syslog-ng should be all that's required to fix it - reboot is > overkill.
As for me, first I updated syslog-ng, then I issued '/etc/init.d/syslog-ng reload' (by mistake, instead of 'restart'), and then 'restart' as I should. Then, just when syslog-ng was restarting, the segfault happened. > Also, any errors in the config file should not cause segfault. If it does, > that indicates a bug in the input validation/config parsing code. Errors in > the config should result in a graceful termination. -- Regards, Alex
