Details
-
Type:
Feature Request
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Fix Version/s: OpenVZ-legacy
-
Component/s: Containers::Kernel
-
Security Level: Public
-
Environment:Operating System: Other
Platform: Other
-
External issue URL:
-
External issue ID:2693
Description
To reproduce:
- Create a VM using the 13.04 template
- apt-get update && apt-get install rsyslog
Notice the CPU going to 100% caused by the rsyslogd process.
From /var/log/syslog:
Jul 30 16:53:14 Test-Ubuntu-13 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1513" x-info="http://www.rsyslog.com"] start
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: rsyslogd's groupid changed to 109
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: rsyslogd's userid changed to 105
Jul 30 16:53:14 Test-Ubuntu-13 kernel: Cannot read proc file system: 1 - Operation not permitted.
Jul 30 16:53:45 Test-Ubuntu-13 kernel: last message repeated 3389194 times
Jul 30 16:54:45 Test-Ubuntu-13 kernel: last message repeated 6800396 times
Problem seems to be caused by an incompatibility between newer rsyslog and older kernel (including RHEL6 kernel). Found this post that seems to explain the problem quite well: http://www.nostate.com/4228/fixing-the-100-cpu-and-no-useful-output-imklogrsyslog-kernel-logging-problem-on-ubuntu-guests-under-xen-pv/
Work around is to remove rsyslog (revert to klogd / sysklogd)
Simon
- Create a VM using the 13.04 template
- apt-get update && apt-get install rsyslog
Notice the CPU going to 100% caused by the rsyslogd process.
From /var/log/syslog:
Jul 30 16:53:14 Test-Ubuntu-13 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1513" x-info="http://www.rsyslog.com"] start
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: rsyslogd's groupid changed to 109
Jul 30 16:53:14 Test-Ubuntu-13 rsyslogd: rsyslogd's userid changed to 105
Jul 30 16:53:14 Test-Ubuntu-13 kernel: Cannot read proc file system: 1 - Operation not permitted.
Jul 30 16:53:45 Test-Ubuntu-13 kernel: last message repeated 3389194 times
Jul 30 16:54:45 Test-Ubuntu-13 kernel: last message repeated 6800396 times
Problem seems to be caused by an incompatibility between newer rsyslog and older kernel (including RHEL6 kernel). Found this post that seems to explain the problem quite well: http://www.nostate.com/4228/fixing-the-100-cpu-and-no-useful-output-imklogrsyslog-kernel-logging-problem-on-ubuntu-guests-under-xen-pv/
Work around is to remove rsyslog (revert to klogd / sysklogd)
Simon
