<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Message: 3<br>
Date: Mon, 05 Dec 2011 10:10:40 +0100<br>
From: Gergely Nagy <<a href="mailto:algernon@balabit.hu">algernon@balabit.hu</a>><br>
Subject: Re: [syslog-ng] syslog-ng 3.1.2 segmentation fault in Ubuntu<br>
10.10<br>
To: Syslog-ng users' and developers' mailing list<br>
<<a href="mailto:syslog-ng@lists.balabit.hu">syslog-ng@lists.balabit.hu</a>><br>
Message-ID: <87aa77l6y7.fsf@algernon.balabit><br>
Content-Type: text/plain<br>
<br>
Luis Pugoy <<a href="mailto:lpugoy@insynchq.com">lpugoy@insynchq.com</a>> writes:<br>
<br>
> Does anyone have any insight into this? The segfault is happening more<br>
> often now. :(<br>
<br>
I'd suggest either upgrading to 3.3 from my repo[1], or if an upgrade is<br>
not feasible, then if you could compile 3.1 with debug symbols, get it<br>
to drop a core, and do a backtrace, that would help tremendously.<br>
<br>
[1]: <a href="http://asylum.madhouse-project.org/projects/debian/" target="_blank">http://asylum.madhouse-project.org/projects/debian/</a><br>
<br>
To do the latter, the following steps should work:<br>
<br>
$ apt-get source syslog-ng<br>
$ sudo apt-get build-dep syslog-ng<br>
$ cd syslog-ng-*<br>
$ DEB_BUILD_OPTIONS="debug nostrip" dpkg-buildpackage -us -uc -rfakeroot<br>
$ sudo dpkg -i ../syslog-ng_*.deb<br>
<br>
Then add --enable-core to SYSLOGNG_OPTS in /etc/default/syslog-ng, and<br>
when it segfaults, it'll make a core in (as far as I remember) /. Once<br>
that happened, do something like this:<br>
<br>
$ gdb -c /core /usr/bin/syslog-ng<br>
(gdb) thread apply all bt full<br>
<br>
This should give us a few hints.<br>
<br>
--<br>
|8]<br></blockquote><div><br></div><div> I installed a newer version of the PCRE library. That seems to have worked for now. If it happens again I will be sure to follow your instructions, thanks.</div></div>