Activity log for bug #565288

Date Who What changed Old value New value Message
2010-04-17 10:14:07 Rocko bug added bug
2010-04-17 10:14:07 Rocko attachment added Dependencies.txt http://launchpadlibrarian.net/44568804/Dependencies.txt
2010-04-17 10:17:33 Rocko description Binary package hint: rsyslog Kernel logging is disabled on all kernels other than the stock Ubuntu kernel, because rsyslog fails to read kmsg. Instead, it reports: "kernel: imklog: Cannot read proc file system, 1." This is intentional on older kernels (see bug #523610, comment 35), but it is also happening on the latest 2.6.33.2 kernel: sudo python >>> import os >>> f=open('/proc/kmsg') >>> os.seteuid(1000) >>> f.read(0) '' >>> f.read(1) Traceback (most recent call last): File "<stdin>", line 1, in <module> IOError: [Errno 1] Operation not permitted ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8 Uname: Linux 2.6.33.2-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxSubmission: 1bd8e90541d49b96c13cbfcc9baf103b CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sat Apr 17 17:58:38 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) ProcEnviron: PATH=(custom, user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: rsyslog Binary package hint: rsyslog Kernel logging is disabled on all kernels other than the stock Ubuntu kernel, because rsyslog fails to read kmsg. Instead, it reports: "kernel: imklog: Cannot read proc file system, 1." This is intentional on older kernels (see bug #523610, comment 35), but it is also happening on the latest 2.6.33.2 kernel: sudo python >>> import os >>> f=open('/proc/kmsg') >>> os.seteuid(1000) >>> f.read(0) '' >>> f.read(1) Traceback (most recent call last):   File "<stdin>", line 1, in <module> IOError: [Errno 1] Operation not permitted I don't believe it's in the spirit of things to disable logging on newer kernels (it cuts out a large number of testers for rc kernels, for instance). Why is it necessary for rsymlog to drop root privileges and disable logging if it can't access kmsg? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog 4.2.0-2ubuntu8 Uname: Linux 2.6.33.2-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxSubmission: 1bd8e90541d49b96c13cbfcc9baf103b CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sat Apr 17 17:58:38 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) ProcEnviron:  PATH=(custom, user)  LANG=en_AU.utf8  SHELL=/bin/bash SourcePackage: rsyslog
2010-04-17 17:13:13 Rocko summary rsyslog fails to read kmsg on newer (custom) kernels rsyslog fails to read kmsg on 2.6.33 kernels
2010-06-20 18:42:24 gene rsyslog (Ubuntu): status New Confirmed
2010-11-06 10:28:17 Matt Zimmerman rsyslog (Ubuntu): status Confirmed Fix Released
2012-02-20 21:18:16 Simon Déziel bug added subscriber Simon Déziel