Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#34268 - [rsyslog] eats cpu, breaks log and system

Attached to Project: Community Packages
Opened by Christian Hesse (eworm) - Monday, 11 March 2013, 22:43 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 19 June 2013, 09:43 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the update to rsyslog 7.2.6-1 system goes mad: rsyslogd eats 100% cpu, not a single line is written to log file. This happens when the process is started by systemd or from a terminal. This breaks some systemd unit waiting for syslog.

Downgrading to rsyslog 7.2.4-1 solves the problem.

I rebuilt libee, libestr and rsyslog without any change.

Additional info:
rsyslog 7.2.6-1
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 19 June 2013, 09:43 GMT
Reason for closing:  No response
Comment by Christian Hesse (eworm) - Tuesday, 12 March 2013, 07:45 GMT
Damn! Tried to bisect the problem, but even a fresh compile of v7.2.4 fails...

*sigh*
Comment by Christian Hesse (eworm) - Tuesday, 12 March 2013, 08:24 GMT
Ah, kind of got it... /etc/rsyslog.conf has been replaced with something completely different...
Comment by Sergej Pupykin (sergej) - Tuesday, 12 March 2013, 12:55 GMT
it is strange, PKGBUILD contains

backup=('etc/rsyslog.conf'
Comment by Christian Hesse (eworm) - Tuesday, 12 March 2013, 13:10 GMT
Sure. But if the file has not been altered (md5 sums of file and in pacman db match) the new file is merged automatically. The new file is placed as /etc/rsyslog.conf.pacnew only if md5 sums differ.

However... Even a new installation should get a "safe default". Getting warnings or errors is ok for me, but just eating cpu time and doing nothing else is really bad.
Comment by startover (startover) - Monday, 15 April 2013, 01:58 GMT
  • Field changed: Percent Complete (100% → 0%)
I have the same problem with rsyslog. After upgrade rsyslogd takes a lot of cpu, and I had to downgrade to 7.2.4-1.
Comment by Sergej Pupykin (sergej) - Friday, 07 June 2013, 17:27 GMT
Can it be reproduced with 7.4.0 ?

Loading...