Hi, I don't recall hearing a similar report about my packages. Could you open a bug report about the memory leak at https://github.com/balabit/syslog-ng/issues/ including your configuration? Thanks, Peter Czanik (CzP) <peter.czanik@balabit.com> BalaBit IT Security / syslog-ng upstream http://czanik.blogs.balabit.com/ https://twitter.com/PCzanik On Mon, Mar 30, 2015 at 8:22 PM, Pradeep Sanders <psanders@ultraviolet.us> wrote:
Hello, I'm seeing a similar problem to what was reported here:
http://communities.balabit.com/balabit/topics/stats-from-syslog-remote-sourc...
I'm trying to upgrade from the RHEL 6 default 3.2 version to 3.5 or 3.6, in order to enable threaded support. I've tried a 3.6 build from the following location:
https://copr-be.cloud.fedoraproject.org/results/czanik/syslog-ng36epel6/epel...
However, this build consumes all my host memory (48GB) in a matter of hours before starting on swap space.
I've tried a 3.5.4 and a 3.5.6 package but both of them exhibit the same issue, with remote sources not reported in "syslog-ng-ctl stats".
Does anyone have any advice on how I might fix the stats for remote sources in 3.5?
Thanks,
-Pradeep
______________________________________________________________________________ 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