Hi Gergely, Looks like I have a syslog-ng 3.3beta1 (fetched from GITHEAD) that is having a serious memory leak (and I'm not yet pushing all our logs to it ;( Any advice in how to help you track this problem? Hendrik On Fri, Jul 15, 2011 at 4:06 PM, Gergely Nagy <algernon@balabit.hu> wrote:
Hendrik Visage <hvjunk@gmail.com> writes:
On Fri, Jul 15, 2011 at 12:21 PM, Gergely Nagy <algernon@balabit.hu> wrote:
Hendrik Visage <hvjunk@gmail.com> writes:
I've have a syslog-ng 3.3.0beta1 (at least the tag I get from the git build) that keeps falling over as it receives logs from ESX servers, this is on a Red Hat Enterprise Linux Server release 6.0 (Santiago) inside a VM. The dmesg output gives "interesting" responses:
[...snip...]
Would it be possible to compile syslog-ng with debugging symbols (CFLAGS="-g" ./configure --enable-debug), and run it with --enable-core?
Done.
A backtrace of the crash would then be useful to have. O:)
,---- | $ gdb -c /path/to/core-file /path/to/syslog-ng | (gdb) bt full `----
Other than that, I'd suggest either going back to 3.2, or trying the latest version of 3.3 from git head, as there have been quite a lot of stability fixes since beta1.
Jul 15 15:47:09 tsysl01 syslog-ng[27978]: syslog-ng starting up; version='3.3.0beta1'
Just "which beta1 is this that I've downloaded from githead???" comes to mind :(
Perhaps embed a githead version for the git repositories ;)
That's a bit tricky, but you're right - it would be nice to have an indication about what revision the binary was compiled from.
-- |8]
______________________________________________________________________________ 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