I'm happy to upload this fix to Trusty and Utopic but we will need a
test case in the bug description so that the fix can be verified. Could
somebody please provide one following the example at
http://wiki.ubuntu.com/StableReleaseUpdates? Thanks!

** Changed in: rsyslog (Ubuntu)
       Status: Confirmed => In Progress

** Changed in: rsyslog (Ubuntu)
     Assignee: (unassigned) => Brian Murray (brian-murray)

** Also affects: rsyslog (Ubuntu Utopic)
   Importance: Undecided
       Status: New

** Also affects: rsyslog (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: rsyslog (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: rsyslog (Ubuntu Utopic)
   Importance: Undecided => High

** Changed in: rsyslog (Ubuntu Trusty)
       Status: New => Triaged

** Changed in: rsyslog (Ubuntu Utopic)
       Status: New => Triaged

-- 
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:
  In Progress
Status in rsyslog source package in Trusty:
  Triaged
Status in rsyslog source package in Utopic:
  Triaged

Bug description:
  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: amd64
  DistroRelease: 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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to