Is this during the system shutdown? Or whenever your shutdown apparmor? 

To just shutdown apparmor run: 'rcsubdomain stop' from a console as the root user.

The SubDomain evetn daemon is /usr/sbin/sd-event-dispatch.pl (in beta 3 it will be renamed /usr/sbin/aa-eventd).

Thanks

I wanted to test it out but unfortunately even as root there is no "rcsubdomain" to execute

There should be an /sbin/rcsubdomain symlink (and starting in beta 3, an /sbin/rcapparmor as well); if there's not, then somethings been corrupted in the apparmor-parser package. 

Strange, now the command works.
I can stop and restart subdomain with success, but on shutdown I get always a "failed". Sometimes also on startup.

*** Bug 147312 has been marked as a duplicate of this bug. ***

Still the same in beta3

Steve,

 I think this is addressed by the recent shutdown changes you made for aa-eventd. If this is the case can you close when this goes into abuild?
If not re-assign to me and I can look into it some more.

Okay, I see what's happening here. This is a result of the event daemon being moved into the boot.apparmor initscript. During a shutdown, init runs the kill scripts in the current runlevel, then sends sigterm and sigkill to all running processes, and only then does it call the boot.d/ scripts with the stop argument. So by the time boot.apparmor gets called to shutdown, init has already killed the apparmor event daemon (by sending it sigkill, which the bug I fixed wouldn't have stopped) without removing the pidfile. Because the pidfile still exists, the boot.apparmor script tries to kill the daemon and fails.

Really, this is yet another call for resurrecting the initscript dedicated to just the event daemon itself. Alas, it's awfully late in the beta cycle to do so.

Should be fixed by the separation of the aa-eventd into it's own init script. No longer any daemons running as part of boot.apparmor - profile initialization only.