Can you confirm that the md5sum of /etc/apparmor.d/usr.sbin.dhcpd is c4a3f842da64006353d11d907b8b1752?
If it's, then try: - sudo /etc/init.d/apparmor reload - start isc-dhcp-server The bug you're describing above is exactly the same as was introduced in 4.2.4-1ubuntu10.2 and then fixed in 4.2.4-1ubuntu10.3 so the fact you're still seeing it suggest that apparmor didn't reload the profile properly. If the above doesn't work, I'd suggest trying to reboot the machine to be perfectly sure that apparmor did parse the new profile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172148 Title: isc-dhcp-server didn't restart after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1172148/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
