Comment 1 for bug 556343

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Michael, I think that the apparmor message is innocuous. As mentioned, this message is caused by the apparmor_parser call, but it hits '|| true' and proceeds to restart bind9. The call to apparmor_parser fails because we have a new profile and apparmor-utils on an old kernel. To be sure that apparmor isn't getting in the way of the restart, can you check if there are any apparmor denials in the kern.log of this machine at the time that bind9 was restarted?