Neil Bothwick wrote:
Try app-admin/checkrestart, I generally run this after updating any
daemons or libraries.
This sounds very helpful, thanks for the suggestion Neil!
--
R
On Sat, 20 Jul 2013 20:27:51 +0800, kwk...@hkbn.net wrote:
> 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 lin
On Fri, 19 Jul 2013 17:03:36 -0400
Randy Barlow 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, instea
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 r
2013/7/19 Adam Carter :
>> > syslog-ng[32015]: segfault at 44d8 ip 7f4f3fa23c83 sp
>> > 7fffb233b940 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?
>
> #
>
> > syslog-ng[32015]: segfault at 44d8 ip 7f4f3fa23c83 sp
> > 7fffb233b940 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 l
2013/7/19 Randy Barlow :
> I saw that there were a couple of syslog-ng threads recently, but
> neither of them mentioned any segfaulting which I am currently
> experiencing. My log file (dmesg and /var/log/messages) is full of lines
> like this:
>
> syslog-ng[32015]: segfault at 44d8 ip 7f4f3fa
On Thu, 2013-07-18 at 18:41 -0400, Randy Barlow wrote:
> Has anybody else seen anything like that?
I'll add in that this seems to be happening to all three of my x86_64
hosts. It does not appear to happen on my x86 host.
--
R
On Thu, 2013-07-18 at 17:49 -0500, Bruce Hill wrote:
> Try changing the version at the top of the config file to the present version.
It's at 3.4, and I have the gentoo default config. Thanks for the
suggestion!
--
R
On Thu, Jul 18, 2013 at 06:41:14PM -0400, Randy Barlow wrote:
> I saw that there were a couple of syslog-ng threads recently, but
> neither of them mentioned any segfaulting which I am currently
> experiencing. My log file (dmesg and /var/log/messages) is full of lines
> like this:
>
> syslog-ng[3
On Thu, Jul 18, 2013 at 06:41:14PM -0400, Randy Barlow wrote:
> I saw that there were a couple of syslog-ng threads recently, but
> neither of them mentioned any segfaulting which I am currently
> experiencing. My log file (dmesg and /var/log/messages) is full of lines
> like this:
>
> syslog-ng[3
On Thu, 2013-07-18 at 18:41 -0400, Randy Barlow wrote:
> I saw that there were a couple of syslog-ng threads recently, but
> neither of them mentioned any segfaulting which I am currently
> experiencing. My log file (dmesg and /var/log/messages) is full of lines
> like this:
>
> syslog-ng[32015]:
I saw that there were a couple of syslog-ng threads recently, but
neither of them mentioned any segfaulting which I am currently
experiencing. My log file (dmesg and /var/log/messages) is full of lines
like this:
syslog-ng[32015]: segfault at 44d8 ip 7f4f3fa23c83 sp
7fffb233b940 error 4 in
13 matches
Mail list logo
