Problem AppArmor reboot system

Jesus Fdz

New Member
Feb 3, 2017
1
0
1
44
Sorry for my bad english, I have a problem with apparmor in proxmox v4.4 which does not get to mount units and I am the machine the previous registration to the fall is next.


Code:
Feb 16 17:40:01 nodo1 kernel: [76282.010836] audit: type=1400 audit(1487263201.515:455): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/home/virtfs/xxxxxxx/dev/" pid=1$
Feb 16 17:40:01 nodo1 kernel: [76282.010846] audit: type=1400 audit(1487263201.515:456): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/home/virtfs/xxxxxxx/dev/" pid=13$
Feb 16 17:40:01 nodo1 kernel: [76282.010864] audit: type=1400 audit(1487263201.515:457): apparmor="DENIED" operation="mount" info="failed type match" error=-13 profile="lxc-container-default-cgns" name="/home/virtfs/xxxxxxx/dev/" pid=13$
Feb 16 17:40:01 nodo1 kernel: [76282.037189] audit: type=1400 audit(1487263201.543:458): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=13575 comm="jailshell" fl$
Feb 16 17:40:01 nodo1 CRON[13583]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:40:04 nodo1 pvedaemon[8977]: worker exit
Feb 16 17:40:04 nodo1 pvedaemon[2581]: worker 8977 finished
Feb 16 17:40:04 nodo1 pvedaemon[2581]: starting 1 worker(s)
Feb 16 17:40:04 nodo1 pvedaemon[2581]: worker 13697 started
Feb 16 17:40:06 nodo1 kernel: [76287.213289] audit: type=1400 audit(1487263206.719:459): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="lxc-container-default-cgns" name="/" pid=13838 comm="(imedated)" f$
Feb 16 17:41:01 nodo1 CRON[15227]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:42:01 nodo1 CRON[16212]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:43:01 nodo1 CRON[17007]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:44:01 nodo1 CRON[18754]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:45:01 nodo1 CRON[21289]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:46:01 nodo1 CRON[22863]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:46:10 nodo1 pvedaemon[15936]: <root@pam> successful auth for user 'root@pam'
Feb 16 17:47:01 nodo1 CRON[23900]: (root) CMD (/usr/local/rtm/bin/rtm 32 > /dev/null 2> /dev/null)
Feb 16 17:53:28 nodo1 rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="2482" x-info="http://www.rsyslog.com"] start
Feb 16 17:53:28 nodo1 systemd-modules-load[276]: Module 'fuse' is builtin

I would appreciate any help since it is driving me crazy for the rest, it works perfectly
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!