touch-packages team mailing list archive

[Chris J Arges <1366829@xxxxxxxxxxxxxxxxxx>]

@Patrice:
Running 'apport-collect 1366829' as mentioned above would help to debug the issue. Please do so when you get a chance.
Thanks,

The commit that fixes the debian issue above is:
https://github.com/rsyslog/rsyslog/commit/ff091b7ea963b63130cfb77af57f137e632bf765
However, I'm unsure if this is the same issue.

-- 
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:
  Updating to rsyslog - 7.4.4-1ubuntu2.1 makes rsyslogd to take all the
  CPU

Status in “rsyslog” package in Ubuntu:
  New

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 of is 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

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