| 1 |
On Fri, 19 Jul 2013 17:03:36 -0400 |
| 2 |
Randy Barlow <randy@×××××××××××××××××.com> wrote: |
| 3 |
|
| 4 |
> Alexey Mishustin wrote: |
| 5 |
> >> So, restarting syslog-ng should be all that's required to fix it - |
| 6 |
> >> reboot is |
| 7 |
> >> >overkill. |
| 8 |
> |
| 9 |
> > As for me, first I updated syslog-ng, then I issued |
| 10 |
> > '/etc/init.d/syslog-ng reload' (by mistake, instead of 'restart'), |
| 11 |
> > and then 'restart' as I should. Then, just when syslog-ng was |
| 12 |
> > restarting, the segfault happened. |
| 13 |
> |
| 14 |
> I also noted that restarting syslog didn't seem to solve the problem. |
| 15 |
> I do think Adam's reasoning makes sense, but there must be something |
| 16 |
> else that needed to be restarted as well. |
| 17 |
> |
| 18 |
|
| 19 |
Same behaviour here. In my case with an "lsof | grep libsyslog-ng" I |
| 20 |
see in the physical host hp-systray from hplip was still |
| 21 |
using the old libsyslog-ng.so, so killing that and a restart of |
| 22 |
syslog-ng service stops the segfault lines. YMMV, |
| 23 |
|
| 24 |
Kerwin. |
Archives