I was wondering if anyone else has had the experience of checking out processes on their DMZ log forwarder after a couple of weeks of running syslog-ng (~5 machines logging to it, one file destination, one TCP remote), only to find its VSZ to be approaching 80MB :) Obviously some kind of significant memory leak. According to the list archives, another poster put up a patch but he has not responded to my inquiries; I'm wondering if anyone else has patches or has used the patch posted not too long ago...or at least, perhaps someone could confirm that they also must restart the syslog-ng process daily to combat memory leakage.
Obviously some kind of significant memory leak. According to the list archives, another poster put up a patch but he has not responded to my inquiries; I'm wondering if anyone else has patches or has used the patch posted not too long ago...or at least, perhaps someone could confirm that they also must restart the syslog-ng process daily to combat memory leakage.
I tend to restart the syslog-ng when ever it starts using over 35% CPU. I find that when the usage is that high it doesn't log at all, if so just the occasional log. If I leave it, it ends up using 99% :-( I don't think it's my syslog-ng.conf that's doing it as it's fairly generic. Cheers, John
John on Wed 28/06 14:51 +0100:
I tend to restart the syslog-ng when ever it starts using over 35% CPU. I find that when the usage is that high it doesn't log at all, if so just the occasional log.
If I leave it, it ends up using 99% :-( I don't think it's my syslog-ng.conf that's doing it as it's fairly generic.
I haven't had it start taking up CPU yet, but it sure leaks memory like a seive. Sounds like a great program...loads CPU even when inactive, and eats up all available memory within a couple of weeks on a machine otherwise mostly unused. Hmm, sounds like Netscape ;) Unfortunately, syslog-ng's ability to do TCP logging, unlimited forwarding, and the nice log-by-host/program makes it an invaluable tool, so it's worth fixing rather than abandoning. Does the author read the list? Respond well to patches? The code isn't too huge, I might try to find the leak myself.
Scott McDermott (mcdermot@questra.com) wrote:
I tend to restart the syslog-ng when ever it starts using over 35% CPU. I find that when the usage is that high it doesn't log at all, if so just the occasional log.
If I leave it, it ends up using 99% :-( I don't think it's my syslog-ng.conf that's doing it as it's fairly generic.
Sounds like a great program...loads CPU even when inactive, and eats up all available memory within a couple of weeks on a machine otherwise mostly unused. Hmm, sounds like Netscape ;)
:-)
Unfortunately, syslog-ng's ability to do TCP logging, unlimited forwarding, and the nice log-by-host/program makes it an invaluable tool, so it's worth fixing rather than abandoning.
Sure is.
Does the author read the list? Respond well to patches? The code isn't too huge, I might try to find the leak myself.
Yep, the author is really good. Cheers, John
CPU. I find that when the usage is that high it doesn't log at all, if so just the occasional log.
If I leave it, it ends up using 99% :-( I don't think it's my syslog-ng.conf that's doing it as it's fairly generic.
I haven't had it start taking up CPU yet, but it sure leaks memory like a seive.
Sounds like a great program...loads CPU even when inactive, and eats up all available memory within a couple of weeks on a machine otherwise mostly unused. Hmm, sounds like Netscape ;)
Unfortunately, syslog-ng's ability to do TCP logging, unlimited forwarding, and the nice log-by-host/program makes it an invaluable tool, so it's worth fixing rather than abandoning.
Does the author read the list? Respond well to patches? The code isn't too huge, I might try to find the leak myself.
I'm the author, and I host this list so obviously I read it sometimes. Things were quite rough here nowadays, so I couldn't do anything useful on syslog-ng. However I know about the problem so a fix will be available ASAP. (whatever this means) -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler on Wed 28/06 17:56 +0200:
[consistent memory leak(s)]
I'm the author, and I host this list so obviously I read it sometimes.
Well, you could be really busy and have abandoned the code :) I just joined the list, so I had no idea...
Things were quite rough here nowadays, so I couldn't do anything useful on syslog-ng. However I know about the problem so a fix will be available ASAP. (whatever this means)
It's an acronym: As Soon As Possible. Your efforts are greatly appreciated...let me know if other things come up and I'll help to track it down.
participants (3)
-
Balazs Scheidler
-
John
-
Scott McDermott