Ubuntu
apparmor package

Afterupgrade from Fiesty to Gutsy, AppArmor prevents syslogd from starting.

Bug #140274 reported by Rick Clark
2
Affects Status Importance Assigned to Milestone
apparmor (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: apparmor-profiles

After an upgrade from Fiesty to Gutsy, syslogd was unable to get a lock on it's pid file. It hung for several minutes and then failed.

audit(1189990898.810:3): operation="file_lock" requested_mask="k"
denied_mask="k" name="/var/run/syslogd.pid" pid=4870 profile="/sbin/syslogd"

stopping AppArmor, or removing the profile fixed the problem.

Related branches

lp:ubuntu/karmic/apparmor
Mathias Gug (mathiaz)
Changed in apparmor:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Mathias Gug (mathiaz) wrote :

apparmor (2.1+993-0ubuntu1) gutsy; urgency=low

  * new merge from upstream:
    * fixes to support new audit messages sent by the kernel module.
    * bump in minor library version for libapparmor.
  * debian/control: Add perl libterm-readkey-perl and librpc-xml-perl
    dependencies for apparmor-utils. Fixes LP: #139757, LP: #139091.
  * utils/SubDomain.pm: Re-enable RPC client for remote repositories.
  * profiles/apparmor.d/sbin.syslogd: update profile.
    Fixes LP: #140672, LP: #140274.

 -- Mathias Gug <email address hidden> Tue, 18 Sep 2007 11:12:50 -0400

Changed in apparmor:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.