unkillable apparmor_parser

Bug #544764 reported by LaMont Jones
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)

Bug Description

Binary package hint: apparmor

during an upgrade to lucid (from karmic) apparmor_parser was freerunning (100% CPU usage) and unkillable, while processing ntpd's profile. I do still have the broken root tree available, please pester me if I haven't already attached the tarball of apparmor.d to this bug.

Killed the parent, and the upgrade continued to a point where the machine locked up hard, starting a series of pain.


Revision history for this message
John Johansen (jjohansen) wrote :

Lamont, how long did you let it run for before trying to kill it, and what are the machine specs (so I can make a guess at how long it should have been computing for)? Did you check the apparmor_parser's reported state and if so what was it?

Kees Cook (kees)
Changed in apparmor (Ubuntu):
status: New → Incomplete
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in apparmor (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers