rsyslogd suddenly went crazy (120% cpu)

Reindl Harald h.reindl at thelounge.net
Fri Jun 14 21:12:49 UTC 2013


Am 14.06.2013 23:10, schrieb Clemens Eisserer:
> I am running Fedora 19 + updates-testing and suddenly rsyslogd went crazy, and is now consuming constantly 120% cpu
> (and is also constantly expanding allocated memory).
> I first thought it could have something to do with updates I've applied recently, so I rolled back to an older
> btrfs-snapshot - which however didn't improve the situation.
> 
> I've recorded some stack-traces: http://pastebin.com/ikwC3h4g
> 
> When executing "tail -f /var/log/messages" I get the same messages from 16. and 17. May over and over again.
> 
> Any ideas what could cause these problems?

wrong mailing-list because F19 is *not* released now and
so your question belongs to the testing-list, but however

-------- Original-Nachricht --------
Betreff: Re: rsyslog-7.4.0-1 is bad
Datum: Fri, 14 Jun 2013 00:24:24 -0700
Von: Adam Williamson <awilliam at redhat.com>
Antwort an: Development discussions related to Fedora <devel at lists.fedoraproject.org>
Organisation: Red Hat
An: For testing and quality assurance of Fedora releases <test at lists.fedoraproject.org>
Kopie (CC): devel at lists.fedoraproject.org

On Thu, 2013-06-13 at 23:48 -0700, Adam Williamson wrote:
> Just a heads up for F19 / F20 users - rsyslog-7.4.0-1 is a bad update,
> many users (inc. me on two systems) are seeing it
> spamming /var/log/messages with old logs and sucking up 100% CPU time.
> You might not notice immediately if you're not running something that
> spins its fans up. I recommend downgrading to 7.2.6-1 ASAP. Bug is
> https://bugzilla.redhat.com/show_bug.cgi?id=974335 .

Better bug link:

https://bugzilla.redhat.com/show_bug.cgi?id=974132

Turns out this is ultimately a journald bug (and explains why journalctl
has been busted for me lately). But still, if you're hit by it, you're
going to want to nerf rsyslogd ASAP, because until you do, it will
spam /var/log/messages until your disk is full. Mine had reached 8GB by
the time I noticed. Some other poor bugger's got to 30GB.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130614/3dbab453/attachment.sig>


More information about the users mailing list