Hi Alex, Than you for your reply.
Strange, I was just chatting about this with my colleague a minute ago and turned to look at the mail I received and here is your email...spooky. Same for me...spooky.;-) Well, can you show me "options" line in syslog-ngd.conf? Mine is very simple as follows. #options {create_dirs(yes); use_fqdn(yes); dir_owner(syslog-ng); dir_perm(0750); owner(syslog-ng); perm(0740);};
We were running 2.0.5 however when I moved to 2.0.7 the problem disappeared. Sure I will. Upgrade to 2.0.7 or 2.0.8 is not determined yet. (mkml suggested me to use 2.0.8 a little minutes ago.)
Regards, -- // mailto: le.petit.planet@gmail.com On Feb 4, 2008 5:53 PM, Alexander Clouter <ac56@soas.ac.uk> wrote:
Hi,
Strange, I was just chatting about this with my colleague a minute ago and turned to look at the mail I received and here is your email...spooky.
Eiji Inatsu <le.petit.planet@gmail.com> [20080204 12:00:37 +0900]:
Hi, and finally physical memory and swap spaces are exhausted. Is this a memory leak or not?
My version # /usr/local/sbin/syslog-ng -V syslog-ng 2.0.2 My H/W and OS Solaris 10, sparc 64
This syslog-ng is running about 2 or 3 days until restarted. This host is central loghost and receives about 40GB data per day.
Up to about a two weeks ago (for six months) syslog-ng started off with 2MB of RAM usage and I had about two weeks before I had to restart it as it creeped up to 2GB.
We were running 2.0.5 however when I moved to 2.0.7 the problem disappeared.
I guess I would recommend you up to a newer version, there have been a lot of bug fixes since 2.0.2 and you should move on :)
Cheers
Alex _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html