[syslog-ng] 3.3.4 anyone else notice a memory leak
Martin Holste
mcholste at gmail.com
Wed Feb 8 17:58:56 CET 2012
Hm, I'm not seeing the leak in ELSA (which uses program()) and I'm
using 3.3.4 from the latest tarball (not git).
On Tue, Feb 7, 2012 at 11:49 PM, Evan Rempel <erempel at uvic.ca> wrote:
> It looks like it must be writing to a program destination, or writing to a pipe that leaks the memory.
>
> The only syslog-ng processes I have that do not leak memory are;
>
> - read from a pipe and writes to files.
> - read from ksm /dev/log, write to files and tcp destination
>
> The rest leak;
>
> - Read from network, write to many pipes
> - Read from pipe and write to program
>
> Evan.
> ________________________________________
> From: syslog-ng-bounces at lists.balabit.hu [syslog-ng-bounces at lists.balabit.hu] On Behalf Of Evan Rempel [erempel at uvic.ca]
> Sent: Tuesday, February 07, 2012 9:35 PM
> To: Syslog-ng users' and developers' mailing list
> Subject: [syslog-ng] 3.3.4 anyone else notice a memory leak
>
> I run a number of syslog-ng processes, and I am noticing that the processes that read from
> a pipe, and write to a program destination all seem to have a memory leak in them.
>
> The rate of leak seems to be dependent on the volume of log lines (not surprising).
>
> Has anyone else noticed this.
>
> My config is;
>
>
>
>
> @version: 3.3
>
> #
> # UVic syslog-ng configuration
>
> options {
> log_fifo_size(100000);
> use_fqdn(yes);
> keep_hostname(yes);
> chain_hostnames(yes);
> time_reap(60);
> time_reopen(5);
> flush_lines(1000);
> flush_timeout(1000);
> };
>
> source local { pipe("/var/log/syslog.pipes/syslogstats" log_iw_size(90000) log_fetch_limit(500) flags(no-parse)); };
> source int { internal(); };
>
> destination localsyslog { tcp("localhost" port(1514) localip(localhost) log_fifo_size(50000) template("<$PRI>$S_DATE syslogstats@$HOST syslogstats: $MSGONLY\n") template_escape(no) ); };
>
> destination syslog_stats { program("/home/sysprog/syslog-apps/syslog_stats/syslogstats" template("$MESSAGE\n") template_escape(no) ); };
>
> log { source(local); destination(syslog_stats); flags(flow-control); };
> log { source(int); destination(localsyslog); };
> ______________________________________________________________________________
> 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
>
> ______________________________________________________________________________
> 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
>
More information about the syslog-ng
mailing list