I have a similar  issue, getting these messages from apparmor:

May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.nscd in /etc/apparmor.d/tunables/multiarch at line 13: 
syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN
May 28 06:52:02 bureau apparmor[993]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.smbd in /etc/apparmor.d/tunables/multiarch at line 13: 
syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN
May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.smbldap-useradd in /etc/apparmor.d/tunables/multiarch 
at line 13: syntax error, unexpected TOK_EQUALS, expecting TOK
May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.tcpdump in /etc/apparmor.d/tunables/multiarch at line 
13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN
May 28 06:52:02 bureau apparmor[993]: AppArmor parser error for 
/etc/apparmor.d/usr.sbin.traceroute in /etc/apparmor.d/tunables/multiarch at 
line 13: syntax error, unexpected TOK_EQUALS, expecting TOK_OPEN
May 28 06:52:02 bureau apparmor[993]:    ...fail!


However, I think the error is deeper than some faulty profiles because no 
profiles get loaded at all:

> sudo aa-status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.


Does anybody have a suggestion for how to investigate further?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756800

Title:
  Failed to start AppArmor initialization with status=123/n/a

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to