syslog-ng 3.1.2 segmentation fault in Ubuntu 10.10
Hello, Our syslog-ng server is lately raising a segfault every day or so. The error is of the form "segfault at 7f8677df0338 ip 00007f8676fa8e9d sp 00007fff1d2ec280 error 4 in libpcre.so.3.12.1[7f8676f96000+30000]." Does anyone know what this means? Thanks.
Does anyone have any insight into this? The segfault is happening more often now. :( On Sat, Dec 3, 2011 at 4:44 PM, Luis Pugoy <lpugoy@insynchq.com> wrote:
Hello,
Our syslog-ng server is lately raising a segfault every day or so. The error is of the form "segfault at 7f8677df0338 ip 00007f8676fa8e9d sp 00007fff1d2ec280 error 4 in libpcre.so.3.12.1[7f8676f96000+30000]." Does anyone know what this means? Thanks.
Hi, Algernon, one of the syslog-ng developers has a repository with recent packages for ubuntu as well. I'd recommend trying it, as 3.1 is an older version. http://asylum.madhouse-project.org/projects/debian/ On the other hand, your segfault message refers to the underlying pcre library. Have you changed your config recently? Tweaked the regular expressions in filters or anything similar? Robert On 12/05/2011 08:15 AM, Luis Pugoy wrote:
Does anyone have any insight into this? The segfault is happening more often now. :(
On Sat, Dec 3, 2011 at 4:44 PM, Luis Pugoy <lpugoy@insynchq.com <mailto:lpugoy@insynchq.com>> wrote:
Hello,
Our syslog-ng server is lately raising a segfault every day or so. The error is of the form "segfault at 7f8677df0338 ip 00007f8676fa8e9d sp 00007fff1d2ec280 error 4 in libpcre.so.3.12.1[7f8676f96000+30000]." Does anyone know what this means? Thanks.
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
Luis Pugoy <lpugoy@insynchq.com> writes:
Does anyone have any insight into this? The segfault is happening more often now. :(
I'd suggest either upgrading to 3.3 from my repo[1], or if an upgrade is not feasible, then if you could compile 3.1 with debug symbols, get it to drop a core, and do a backtrace, that would help tremendously. [1]: http://asylum.madhouse-project.org/projects/debian/ To do the latter, the following steps should work: $ apt-get source syslog-ng $ sudo apt-get build-dep syslog-ng $ cd syslog-ng-* $ DEB_BUILD_OPTIONS="debug nostrip" dpkg-buildpackage -us -uc -rfakeroot $ sudo dpkg -i ../syslog-ng_*.deb Then add --enable-core to SYSLOGNG_OPTS in /etc/default/syslog-ng, and when it segfaults, it'll make a core in (as far as I remember) /. Once that happened, do something like this: $ gdb -c /core /usr/bin/syslog-ng (gdb) thread apply all bt full This should give us a few hints. -- |8]
participants (3)
-
Fekete Robert
-
Gergely Nagy
-
Luis Pugoy