Re: [gentoo-user] syslog-ng segfaults
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
Re: [gentoo-user] syslog-ng segfaults
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. signature.asc Description: PGP signature
Re: [gentoo-user] syslog-ng segfaults
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 lines. YMMV, Try app-admin/checkrestart, I generally run this after updating any daemons or libraries. -- Neil Bothwick RAM DISK is NOT an installation procedure! signature.asc Description: PGP signature
Re: [gentoo-user] syslog-ng segfaults
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 libsyslog-ng libsyslog-ng-3.4.2.so = /usr/lib64/libsyslog-ng-3.4.2.so(0x7fe7dfe5b000) 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. 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.
Re: [gentoo-user] syslog-ng segfaults
2013/7/19 Adam Carter adamcart...@gmail.com: 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 libsyslog-ng libsyslog-ng-3.4.2.so = /usr/lib64/libsyslog-ng-3.4.2.so (0x7fe7dfe5b000) 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
Re: [gentoo-user] syslog-ng segfaults
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. -- R
Re: [gentoo-user] syslog-ng segfaults
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]: segfault at 44d8 ip 7f4f3fa23c83 sp 7fffb233b940 error 4 in libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000 +67000] I forgot to mention my version: $ equery list syslog-ng * Searching for syslog-ng ... [IP-] [ ] app-admin/syslog-ng-3.4.2:0 -- R
Re: [gentoo-user] syslog-ng segfaults
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[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? Try changing the version at the top of the config file to the present version. -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] syslog-ng segfaults
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[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? If it wasn't clear before: router ~ # diff /etc/syslog-ng/syslog-ng.conf /etc/syslog-ng/syslog-ng.conf~ 1c1 @version: 3.4 --- @version: 3.3 Cheers, Bruce -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
Re: [gentoo-user] syslog-ng segfaults
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
Re: [gentoo-user] syslog-ng segfaults
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
Re: [gentoo-user] syslog-ng segfaults
2013/7/19 Randy Barlow ra...@electronsweatshop.com: 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 libsyslog-ng.so.0.0.0 (deleted)[7f4f3f9eb000 +67000] Has anybody else seen anything like that? Yes, I had the same issue last Sunday. At x86_64 XEN-based VPS. It's gone after the reboot too. What is CFLAGS there, I don't remember. I'll check it. -- Regards, Alex
