[syslog-ng] Memory leaks...?

Eiji Inatsu le.petit.planet at gmail.com
Tue Feb 5 13:06:23 CET 2008


Hi,

> Mine really is just the one that came with the Debian package:
Thanks!
I thought "sync(n) option" has relevance to memory leaking.
So, I wanted you to show.
Now I know your options and mine don't have, it shows sync(n) has no
relevence.

I will report after version uped.

Thank you for your help!
Regards,
-- 
// mailto: le.petit.planet at gmail.com

On Feb 5, 2008 6:45 PM, Alexander Clouter <ac56 at soas.ac.uk> wrote:

> Hi,
>
> Eiji Inatsu <le.petit.planet at gmail.com> [20080205 12:23:28 +0900]:
> >
> > 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);};
> >
> Mine really is just the one that came with the Debian package:
>
>  options {
>    chain_hostnames(1);
>    time_reopen(10);
>    time_reap(360);
>    log_fifo_size(2048);
>    create_dirs(yes);
>    group(adm);
>    perm(0640);
>    dir_perm(0755);
>    use_dns(no);
>    stats_freq(0);
>  };
>
> Cheers
>
> Alex
>
> > On Feb 4, 2008 5:53 PM, Alexander Clouter <ac56 at 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 at 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 at lists.balabit.hu
> > > https://lists.balabit.hu/mailman/listinfo/syslog-ng
> > > Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
> > >
> > >
>
> > _______________________________________________
> > syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> > https://lists.balabit.hu/mailman/listinfo/syslog-ng
> > Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
> >
>
> _______________________________________________
> syslog-ng maillist  -  syslog-ng at lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20080205/58e34bcb/attachment.htm 


More information about the syslog-ng mailing list