[Bug 1003888] Re: corrupted kernel messages being logged to syslog

[Alan AZZERA]

*** This bug is a duplicate of bug 460925 ***
    https://bugs.launchpad.net/bugs/460925

Hi,

I saw that this bug was marked as duplicate of bug #460925. Anyhow, I wanted to report that under Precise I'm facing the same problem. The host's kern.log and syslog are clean, until I start a container. Then I can read in kern.log things like :
May 23 09:20:58 <$host> kernel: [ 4715.831085] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
May 23 09:29:35 <$host> kernel: [ 5233.548856] device veth_openm entered promiscuous mode
May 23 09:29:35 <$host> kernel: [ 5233.549397] ADDRCONF(NETDEV_UP): veth_openm: link is not ready
May 23 09:29:35 <$host> kernel: [ 5233.709180] ADDRCONF(NETDEV_CHANGE): veth_openm: link becomes ready
May 23 09:29:35 <$host> kernel: [ 5233.709236] br0: port 2(veth_openm) entering forwarding state
May 23 09:29:35 <$host> kernel: [ 5233.709241] br0: port 2(veth_openm) entering forwarding state
May 23 09:29:35 <$host> kernel: [ 5233.722420] audit_printk_skb: 3 callbacks suppressed
May 23 09:29:35 <$host> kernel: [ 5233.722425] type=1400 audit(1369294175.991:13): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 parent=2799 profile="lxc-container-default" name="/var/lib/ureadahead/debugfs/" pid=2848 comm="ureadahead" fstype="debugfs" srcname="none" flags="rw"
May 23 09:29:46 <$host> kernel: <>[ 24000]vt_pn:n P6ruespeet<7[54.806 t0 oIv otr rsn
May 23 09:29:51 <$host> kernel: [ 5248760]b0 ot2vt_pn)etrn owrn tt

And in syslog :
May 23 09:29:35 <$host> kernel: [ 5233.709241] br0: port 2(veth_openm) entering forwarding state
May 23 09:29:35 <$host> kernel: [ 5233.722420] audit_printk_skb: 3 callbacks suppressed
May 23 09:29:35 <$host> kernel: [ 5233.722425] type=1400 audit(1369294175.991:13): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 parent=2799 profile="lxc-container-default" name="/var/lib/ureadahead/debugfs/" pid=2848 comm="ureadahead" fstype="debugfs" srcname="none" flags="rw"
May 23 09:29:46 <$host> kernel: <>[ 24000]vt_pn:n P6ruespeet<7[54.806 t0 oIv otr rsn
May 23 09:29:51 <$host> kernel: [ 5248760]b0 ot2vt_pn)etrn owrn tt
May 23 10:17:01 <$host> CRON[3471]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

My Ubuntu server 12.04 is up to date and its kernel is 3.2.0-43-generic
x86_64.

I also tried to modify a container config following the suggested way :
lxc.cap.drop = sys_module mac_admin syslog

The container does not start. That is the reason why I wrote here.

Best regards,

Al

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1003888

Title:
  corrupted kernel messages being logged to syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1003888/+subscriptions