| 1 |
> |
| 2 |
> > syslog-ng[32015]: segfault at 44d8 ip 00007f4f3fa23c83 sp |
| 3 |
> > 00007fffb233b940 error 4 in libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000 |
| 4 |
> > +67000] |
| 5 |
> > |
| 6 |
> > Has anybody else seen anything like that? |
| 7 |
> |
| 8 |
|
| 9 |
Perhaps you forgot to restart syslog-ng after the update? |
| 10 |
|
| 11 |
# ldd /usr/sbin/syslog-ng | grep libsyslog-ng |
| 12 |
libsyslog-ng-3.4.2.so => |
| 13 |
/usr/lib64/libsyslog-ng-3.4.2.so(0x00007fe7dfe5b000) |
| 14 |
|
| 15 |
If the library was called libsyslog-ng.so.0.0.0 in the previous version, |
| 16 |
and if syslog-ng tried to reload it, it would fail after the update which |
| 17 |
could cause the segfault. |
| 18 |
|
| 19 |
So, restarting syslog-ng should be all that's required to fix it - reboot |
| 20 |
is overkill. |
| 21 |
|
| 22 |
Also, any errors in the config file should not cause segfault. If it does, |
| 23 |
that indicates a bug in the input validation/config parsing code. Errors in |
| 24 |
the config should result in a graceful termination. |
Archives