AppArmor Errors in Syslog on Node...

N

n1ete

New Member
Feb 26, 2017
16
1
1
41
So i got a bunch of AppArmor Errors since a last Update i think it is related to my fileserver container.

and one is related to nfs but there are a bunch of other APPArmor Errors i dont know yet to manage...
would love to get a little help thanks

Code: 
Jun 01 23:59:22 proxmox systemd[1]: Startup finished in 9.967s (kernel) + 19.115s (userspace) = 29.082s.
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.016:10): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=4185 comm="mount" flags="rw, remount, silent"
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.064:11): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=4186 comm="mount" flags="rw, remount"
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.112:12): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/run/" pid=4241 comm="mount" flags="rw, nosuid, noexec, remount, relatime"
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.116:13): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/run/lock/" pid=4252 comm="mount" flags="rw, nosuid, nodev, noexec, remount, relatime"
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.136:14): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/run/shm/" pid=4333 comm="mount" flags="rw, nosuid, nodev, noexec, remount, relatime"
Jun 01 23:59:23 proxmox kernel: audit: type=1400 audit(1496354363.140:15): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/dev/pts/" pid=4341 comm="mount" flags="rw, nosuid, noexec, remount, relatime"
Jun 01 23:59:24 proxmox kernel: vmbr0: port 2(veth100i0) entered forwarding state
Jun 01 23:59:24 proxmox kernel: vmbr0: port 2(veth100i0) entered forwarding state
Jun 01 23:59:26 proxmox kernel: audit: type=1400 audit(1496354366.340:16): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/run/rpc_pipefs/" pid=4812 comm="mount" fstype="rpc_pipefs" srcname="rpc_pipefs"
Jun 01 23:59:26 proxmox kernel: audit: type=1400 audit(1496354366.340:17): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/run/rpc_pipefs/" pid=4812 comm="mount" fstype="rpc_pipefs" srcname="rpc_pipefs" flags="ro"
Jun 01 23:59:26 proxmox kernel: audit: type=1400 audit(1496354366.940:18): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=4951 comm="cgmanager" flags="rw, rprivate"
Jun 01 23:59:27 proxmox pvestatd[3681]: modified cpu set for lxc/100: 0-1
Jun 01 23:59:27 proxmox kernel: audit: type=1400 audit(1496354367.300:19): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/proc/fs/nfsd/" pid=5085 comm="mount" fstype="nfsd" srcname="nfsd"
Jun 01 23:59:27 proxmox kernel: audit: type=1400 audit(1496354367.300:20): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/proc/fs/nfsd/" pid=5085 comm="mount" fstype="nfsd" srcname="nfsd" flags="ro"
Jun 01 23:59:27 proxmox kernel: audit: type=1400 audit(1496354367.568:21): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/proc/fs/nfsd/" pid=5149 comm="mount" fstype="nfsd" srcname="nfsd"
Jun 01 23:59:27 proxmox kernel: audit: type=1400 audit(1496354367.568:22): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/proc/fs/nfsd/" pid=5149 comm="mount" fstype="nfsd" srcname="nfsd" flags="ro"
 
those are not errors, but apparmor reporting that it blocked some operations according to the active profile.
 
You must log in or register to reply here.
Top Bottom