[syslog-ng] syslog-ng Potential Memory Leak

[Jakub Jankowski]

On 19.03.2014 23:13, Tamayo, Andres wrote:
> Hello,
>
> I have been testing syslog-ng under different scenarios and I noticed
> that when syslog-ng is trying to connect to an external syslog-ng
> server, it exhibits what could be called a memory leak.
>
> Let me explain how I am setting up my test.  I have a syslog-ng client
> running collecting logs from a file (source) and sending them to an
> external syslog-ng server over TCP (destination).  If the syslog-ng
> server is online, the syslog-ng client daemon process virtual memory
> does not increase. Now, when I kill the syslog-ng server, the syslog-ng
> client daemon process starts to request more and more virtual memory.
[...]

What you're seeing is not a memory leak. Syslog-ng memory usage grows, 
because it maintains an output buffer, in which it stores messages if 
the destination becomes unavailable. Size of this buffer is controlled 
by log_fifo_size() config option.

Read more about it in the docs: 
http://www.balabit.com/sites/default/files/documents/syslog-ng-ose-3.3-guides/en/syslog-ng-ose-v3.3-guide-admin-en/html-single/index.html


HTH

-- 
Jakub Jankowski|shasta at toxcorp.com|http://toxcorp.com/
GPG: FCBF F03D 9ADB B768 8B92 BB52 0341 9037 A875 942D