I was hopeful that MarkJBobak's suggestion to filter out CPU Temperature messages before passing them to rsyslog would work, but it actually made my system unbootable. On boot, my computer would halt after mounting and checking the disk partitions, even in recovery mode. I found the following related messages in /var/log/syslog:
Nov 19 16:46:29 arethusa kernel: imklog: Cannot open proc file system, 4. Nov 19 16:46:29 arethusa rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="847" x-info="http://www.rsyslog.com";] (re)start Nov 19 16:46:29 arethusa kernel: imklog: Cannot open proc file system, 4. Nov 19 16:46:29 arethusa rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="1691" x-info="http://www.rsyslog.com";] (re)start Nov 19 16:46:29 arethusa rsyslogd: rsyslogd's groupid changed to 102 Nov 20 06:50:54 arethusa kernel: imklog: Cannot open proc file system, 4. Nov 20 06:55:18 arethusa kernel: imklog: Cannot open proc file system, 4. Once I changed the /etc/init/rsyslog-kmsg.conf file back to its original state, I could boot normally again. Just a word of caution in case this bites someone else. -- /var/log fills up with "all normal" messages @ about 575/sec fill up the available space https://bugs.launchpad.net/bugs/453444 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
