I'll try this tomorrow.  Took today off to get some work done on the house. 
Thanks,
Jim



Sent from my Verizon Wireless 4G LTE smartphone


-------- Original message --------
From: "Czanik, Péter" <peter.czanik@balabit.com>
Date: 04/29/2015 9:57 AM (GMT-05:00)
To: Syslog-ng users' and developers' mailing list <syslog-ng@lists.balabit.hu>
Subject: Re: [syslog-ng] syslog-ng memory leak ? valgrind attached

For the redis destination it's a know problem, was quickly fixed after 3.6.2 release: https://github.com/balabit/syslog-ng/commit/53606941b1b6b6726c4945f3560984a73ff23381

If you use my unofficial syslog-ng packages, let me know, and I can add this patch.

Bye,

Peter Czanik (CzP) <peter.czanik@balabit.com>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
https://twitter.com/PCzanik

On Wed, Apr 29, 2015 at 3:49 PM, Jim Hendrick <jrhendri@roadrunner.com> wrote:

From 3.6.2 OSE built with json & redis

Seeing steady memory growth (> 10 GB after ~ a day at ~7000 EPS load)

This was from a few minutes of runtime. (~5)

Is this a known issue or did I trip over something?

Thanks!
Jim




______________________________________________________________________________
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