package apache2.2-common 2.2.22-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Dustin Rue]

Probably caused because I normally have an NFS share mounted on my /etc/apache2 directory

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: apache2.2-common 2.2.22-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-41.89-server 2.6.32.59+drm33.24
Uname: Linux 2.6.32-41-server x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Mon Jun 11 10:02:22 2012
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
SourcePackage: apache2
Title: package apache2.2-common 2.2.22-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to precise on 2012-06-11 (0 days ago)

[Robie Basak (racb)]

From the log, it all seems to stem from this:

Setting up linux-image-3.2.0-24-generic (3.2.0-24.39) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Running postinst hook script /usr/sbin/update-grub.
Generating grub.cfg ...
/usr/sbin/grub-probe: error: failed to get canonical path of /boot/grub/locale.
/usr/sbin/grub-probe: error: cannot stat `'.
User postinst hook script [/usr/sbin/update-grub] exited with value 1
dpkg: error processing linux-image-3.2.0-24-generic (--configure):
 subprocess installed post-installation script returned error exit status 1

[Serge Hallyn (serge-hallyn)]

Thanks for taking the time to report this bug. There seem to be quite a few errors in the update.

Could you re-mount your nfs share, then re-try the upgrade? I will mark this bug invalid - if errors remain with the all filesystems mounted, then new bugs will be automatically created.

[Dustin Rue (ruedu)]

Sorry, probably not what you're going to want to hear but I simply removed the apache and related packages and finished the upgrade. After rebooting I attempted to install the apache packages I need only to be thwarted by apache2-2-bin. Seems that that file was the issue all along.

At any rate, removing all apache packages and installing them "fresh" resolved the issue. Server is back up and running properly.