touch-packages team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

Hello Patrice, or anyone else affected,

Accepted rsyslog into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/7.4.4-1ubuntu11.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: rsyslog (Ubuntu Utopic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1366829

Title:
  7.4.4-1ubuntu2.1 makes rsyslogd to take all the CPU in OpenVZ

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Trusty:
  In Progress
Status in rsyslog source package in Utopic:
  Fix Committed

Bug description:
  Test Case
  ---------
  * Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ container environment)
  * Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf
  * Restart rsyslog to make sure any changes to the binaries/config are picked up
  * Run 'top' and observe that the rsyslogd process is running at 100% CPU. When working properly, the rsyslogd process should generally be idle.

  ---------------------------------------------------------------------

  After updating  rsyslog from 7.4.4-1ubuntu2 to 7.4.4-1ubuntu2.1 the rsyslogd process started to take all the CPU on my machine.
  The modification made by this release is described in #1274444, it is the activation of KLogPermitNonKernelFacility option.
  I don't know exactly the effect of this option but it seems to have a permanent effect : even after downgrading the package or manually removing the option from /etc/rsyslog.conf the issue remains.
  My syslog is full of :
  Sep  8 10:28:40 sentry rsyslogd: imklog: error reading kernel log - shutting down: Bad file descriptor
  Sep  8 10:28:40 sentry rsyslogd: message repeated 498 times: [imklog: error reading kernel log - shutting down: Bad file descriptor]
  Sep  8 10:28:46 sentry rsyslogd-2177: rsyslogd[internal_messages]: 519517 messages lost due to rate-limiting
  I guess this is what causes the CPU load.

  I am running Ubuntu 14.04.1 LTS in an OpenVZ container on Proxmox 3.2. The kernel is 2.6.32-28-pve
  ---
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.1
  PackageArchitecture: amd64
  Tags:  trusty
  Uname: Linux 2.6.32-28-pve x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1366829/+subscriptions