Hi, thanks for the information. I have crafted a big patch package for v4 the last two weeks. I will try to merge it in to v5 this week (I guess this will be a bit harder than usual). It may fix the issue.
If you have a moment or two, it would be interesting to know if 5.5.2 has the same problem. Rainer > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Ralph Crongeyer > Sent: Sunday, March 28, 2010 6:45 PM > To: rsyslog-users > Subject: Re: [rsyslog] High cpu usage - rsyslog 5.4.0. > > It's confirmed! > > I've been running for over an hour and a half now and: > load average: 0.06, 0.06, 0.02 > > Looks good so far. > > Let me know if you guys (Michael, Rainer) want me to run in debug mode > without the lines commented out to see if I can catch the problem for > more troubleshooting. > > Thanks, > Ralph > > Ralph Crongeyer wrote: > > Ok, > > I stoped rsyslog apt-get removed the 5.3.7 package, installed the > 5.4.0 > > package: > > > > r...@logs:/opt# aptitude show rsyslog > > Package: rsyslog > > State: installed > > Automatically installed: no > > Version: 5.4.0-1 > > Priority: extra > > Section: extra > > Maintainer: [email protected] > > Uncompressed Size: 3047k > > Depends: libc6 (>= 2.7-1), zlib1g (>= 1:1.1.4), lsb-base (>= 3.2-14) > > Description: enhanced multi-threaded syslogd > > > > commented out the lines from rsyslog.conf: > > #daemon.*;mail.*;\ > > # news.err;\ > > # *.=debug;*.=info;\ > > # *.=notice;*.=warn |/dev/xconsole > > > > > > and restarted rsyslog: > > r...@logs:/opt# /etc/init.d/rsyslog restart > > Stopping enhanced syslogd: rsyslogd. > > Starting enhanced syslogd: rsyslogd. > > > > I'll get back to you in about an hour. > > > > Thanks, > > Ralph > > > > Michael Biebl wrote: > > > >> 2010/3/28 Ralph Crongeyer <[email protected]>: > >> > >> > >>> I'm running Debian Lenny on both machines. > >>> > >>> > >> > >> > >>> Is anyone else seeing high cpu loads with 5.4.0? > >>> > >>> > >>> > >> I can confirm his (on Debian unstable) and already notified Rainer > >> about this particular issue. > >> Some preliminary testing here seems to indicate it's an issue with > pipes. > >> > >> When I removed > >> daemon.*;mail.*;\ > >> news.err;\ > >> *.=debug;*.=info;\ > >> *.=notice;*.=warn |/dev/xconsole > >> > >> from my rsyslog.conf, I could no longer reproduce the problem. > >> > >> Would be interesting to know, if you can confirm this. > >> > >> Cheers, > >> Michael > >> > >> > >> > > > > > > > > > -- > Reminds me of my expedition into the wilds of Afghanistan. We lost our > corkscrew and were compelled to live on food and water for several > days. - > WC Fields > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
