upgrade error on 8.04 -> 10.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Confirmed
|
Medium
|
John Johansen | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bind9
The automatic upgrade tester found the follow problem on a server upgrade test with all task packages installed:
...
[89.3263] bind9: Configuring bind9
apparmor_parser: Unable to replace "/usr/sbin/named". Profile version not supported by Apparmor module
* Starting domain name service... bind9
...fail!
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: Fehler beim Bearbeiten von bind9 (--configure):
Unterprozess installiertes post-installati
...
Sorry for the bits of the log in german, it mans the post-installation script failed with exit status 1.
Full details can be found here:
http://
around line 2295.
I'm not sure if the apparmor_parser lines are relevant or a red-herring. The bit in the postinst is guarded by || true
and I see a bunch of similar errors in the logs. It also appears to be transient. When I log into the machine after the
upgrade I can restart bind9 just fine.
Changed in bind9 (Ubuntu): | |
importance: | Undecided → High |
tags: | added: apparmor |
Changed in bind9 (Ubuntu Lucid): | |
milestone: | none → ubuntu-10.04 |
Changed in bind9 (Ubuntu Lucid): | |
assignee: | nobody → Chuck Short (zulcss) |
Changed in linux (Ubuntu): | |
importance: | High → Medium |
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?