[syslog-ng] Do stats cause memory leak

[Czanik, Péter]

Hi,

https://github.com/balabit/syslog-ng/pull/1505 seems to address memory
problems. If you use my git head packages, I can add this patch for you and
see if it resolves your problems.

Bye,

Peter Czanik (CzP) <peter.czanik at balabit.com>
Balabit / syslog-ng upstream
https://www.balabit.com/blog/author/peterczanik/
https://twitter.com/PCzanik

On Wed, May 31, 2017 at 4:28 AM, Evan Rempel <erempel at uvic.ca> wrote:

> We are running git head download post 3.9.1 and the memory footprint seems
> to continually grow.
>
> Looking at the statistics for queued messages I found none, but discovered
> that we have nearly 22,000
> statistic sets for a total of 68195 tracked statistics.
> % /usr/local/sbin/syslog-ng-ctl stats | wc -l
> 68195
>
> It it possible that all of these statistics take up a non-trivial amount
> of RAM?
>
> USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
> root      1489 79.2 61.5 12134140 10139760 ?   Ssl  Apr24 41581:22
> /usr/local/sbin/syslog-ng
>
> That is a 12GB footprint after 1 month of uptime.
>
> Evan.
> ____________________________________________________________
> __________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20170531/17467c53/attachment.html>