It may not be necessary anymore but I found out why I couldn't start
klog. The problem was an AppArmor profile (sbin.klogd, part of the
apparmor-profiles package) in enforce mode, which only allowed
/sbin/klogd read access to /proc/kmsg. After disabling the profile I
could start klogd:
18:36:25/etc/apparmor.d>sudo ln -s /etc/apparmor.d/sbin.klogd
/etc/apparmor.d/disable/
18:37:21/etc/apparmor.d>sudo apparmor_parser -R /etc/apparmor.d/sbin.klogd
Removal succeeded for "/sbin/klogd".
18:38:01/etc/apparmor.d>sudo /etc/init.d/klogd stop
* Stopping kernel log daemon...
[ OK ]
18:45:23/etc/apparmor.d>sudo start-stop-daemon --start --verbose --exec
/sbin/klogd -- /proc/kmsg
Starting /sbin/klogd...
18:46:31/etc/apparmor.d>ps aux | grep logd
syslog 4967 0.0 0.0 1916 732 ? Ss 18:29 0:00 /sbin/syslogd
-u syslog
root 7063 0.4 0.1 2504 1396 ? Ss 18:46 0:00 /sbin/klogd
/proc/kmsg
ubuntu 7065 0.0 0.0 2980 772 pts/0 R+ 18:46 0:00 grep logd
18:46:50/etc/apparmor.d>
--
Corrupted AppArmor audit log messages
https://bugs.launchpad.net/bugs/160238
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
