Comment 4 for bug 1830502
Revision history for this message
| John Johansen (jjohansen) wrote Re: apparmor fails to start with no parser errors | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'm not aware of any way to get the apparmor.service to print out what profile it is working on without actually modifying the service
however your dmesg does show the reason for the failure, it looks like the apparmor_parser is being killed by the oom killer
[ 5986.338089] [13520] 0 13520 3056587 3053749 24539136 0 0 apparmor_parser
[ 5986.338090] Out of memory: Kill process 13520 (apparmor_parser) score 646 or sacrifice child
[ 5986.338095] Killed process 13520 (apparmor_parser) total-vm:
we should be able to narrow down which profile is causing the problem by comparing the set of profiles being reported as loaded to those that are on the system.
We can then manually run the apparmor_parser to see which profile is using some much memory to compile