The installation is a fresh 1.6.6 installation
on a clean install of Redhat 3.0. It's been running fine for
about 2 weeks logging the same amount of traffic to local files only.
When I turned on the UDP destinations,
it started chewing up memory. The destinations are receiving logs
entries properly, and the source address is properly spoofed.
Versions of libs:
libnet 1.1.2
libol 0.3.14
Here's the syslog-ng config file - the
only thing that changed to cause this memory eating behavior is the 3 lines
under "# Sets up local destination for Cisco logs". It makes
no difference if I am sending to a single host, or multiple, the memory
"leak" is still there.
I have it currently running under "ElectricFence"
looking for malloc problems - so far none, just memory consumption.
# Log all non cisco stuff to localfile
for debugging
log { source(net); filter(f_notcisco);
destination(allnet); };
Henry -
Balazs Scheidler <bazsi@balabit.hu> Sent by: syslog-ng-admin@lists.balabit.hu
02/28/2005 11:11 AM
Please respond to
syslog-ng@lists.balabit.hu
To
syslog-ng@lists.balabit.hu
cc
Subject
Re: [syslog-ng]Syslog-NG
1.6.6 memory leak when sending UDP logs
On Mon, 2005-02-28 at 09:36 -0500, henry@shoelacecity.com
wrote:
>
> I'm running 1.6.6 on Linux Redhat ES 3.0 logging Cisco router logs
to
> local files and it's been running just fine for over a week.
> I just enabled forwarding for local4 and local7 (with spoof
UDP) to
> 2 additional hosts via UDP and noticed, within a day, that it
> syslog-NG has consumed all available memory. It continues to
log,
> however, the system starts killing processes off unless I restart
> syslog-ng.
If I understand you correctly you use syslog-ng to send logs to another
host via UDP. Is it a new installation or this installation has worked
so far and upgrading to 1.6.6 is what triggered the problem?
Are you using address spoofing (spoof-source(yes))? Can you post your
configuration file?