syslog-ng-users July 2011 archive
Main Archive Page > Month Archives  > syslog-ng-users archives
syslog-ng-users: Re: [syslog-ng] syslog-ng 3.3.0beta & ESX c

Re: [syslog-ng] syslog-ng 3.3.0beta & ESX crashes

From: Gergely Nagy <algernon_at_nospam>
Date: Mon Jul 18 2011 - 13:02:25 GMT
To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu>

Hendrik Visage <hvjunk@gmail.com> writes:

> 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?

Hrm. Well, valgrind would be best, but that slows things down to almost
a grounding halt. (But in case you want to try that:
G_SLICE=always-malloc valgrind --leak-check=full -v --show-reachable-yes
--log-file=valgrind.log syslog-ng -F would be the command to run ;)

Other than that, a config could be useful, so I can try and reproduce
the problem (or at least identify possible areas where the leak might be
coming from, and go from there), and see if I can fix it.

-- |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