You'll need to disable imklog or rsyslogd won't start: module(load="imklog") # provides kernel logging support This is essential unless you give full privileges to your container. Here is a full working rsyslog config in Ubuntu/Debian: module(load="imuxsock") # provides support for local system logging $ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat $FileOwner root........

Message from syslogd@server at Sep 14 11:35:59 ... kernel:[Hardware Error]: MC4 Error (node 1): DRAM ECC error detected on the NB. Message from syslogd@server at Sep 14 11:35:59 ... kernel:[Hardware Error]: Error Status: Corrected error, no action required. Message from syslogd@server at Sep 14 11:35:59 ... kernel:[Hardware Error]: CPU:6 (10:8:0) MC4_STATUS[Over|CE|MiscV|-|AddrV|CECC]: 0xdc00400021080813........

This server has been running for weeks without issue, it's currently only using 1 of 2 CPUs as it is running in the office as a test bed (mainly due to the handle 12 bay storage/great for testing HDDs). The errors below seem to mainly be from AMD CPUs, it's only happened a single time and in the days since Igot that error it hasn't occurrred. Interestingly enough /proc/cpuinfo still shows all 4 cores of the CPU (Opteron 2373 Quadcore HE) and the functionality doesn't seem........

Jan 16 04:02:03 centosbox syslogd 1.4.1: restart. Jan 16 04:07:34 centosbox kernel: INFO: task updatedb:20771 blocked for more than 300 seconds. Jan 16 04:07:34 centosbox kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jan 16 04:07:34 centosbox kernel: updatedb D F78BE050 6476 20771 20766&n........