On Fri, 19 Jul 2013 17:03:36 -0400
Randy Barlow <ra...@electronsweatshop.com> wrote:

> Alexey Mishustin wrote:
> >> 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.
> 
> I also noted that restarting syslog didn't seem to solve the problem.
> I do think Adam's reasoning makes sense, but there must be something
> else that needed to be restarted as well.
> 

Same behaviour here.  In my case with an "lsof | grep libsyslog-ng" I
see in the physical host hp-systray from hplip was still
using the old libsyslog-ng.so, so killing that and a restart of
syslog-ng service stops the segfault lines.  YMMV,

Kerwin.

Attachment: signature.asc
Description: PGP signature

Reply via email to