server upgrade gutsy->hardy failed - Errors were encountered while processing: libapache2-mod-php5 (probably my fault)

[MarianoAbsatz]

Hi,

it's probably my fault but since it told me to report the bug here, here I come :-)

I was remotely upgrading a server from gutsy to hardy (I had upgraded it from feisty a few months ago).

At one point it told me I had modified php.ini and whether I wanted to see the differences, keep my old php.ini or replace it with the new one (using the "blue menu", not plain text console).

I asked for an option I hadn't used before: "see side-by-side differences", and it probably tried to launch something it didn't have or that wasn't running properly, the point is that it went back to the text console, nothing happened:

#################### START CONSOLE OUTPUT ####################

Setting up apache2 (2.2.8-1ubuntu0.3) ...
Setting up g++-4.1 (4.1.2-21ubuntu1) ...
Setting up libstdc++6-4.2-dev (4.2.3-2ubuntu7) ...
Setting up libapache2-mod-ruby (1.2.6-1.2) ...
This module is already enabled!

Setting up libapache2-mod-fastcgi (2.4.6-0ubuntu1) ...
Installing new version of config file /etc/apache2/mods-available/fastcgi.conf ...

Setting up libapache2-mod-fcgid (1:2.2-1) ...
Installing new version of config file /etc/apache2/mods-available/fcgid.conf ...

Setting up libapache2-mod-php5 (5.2.4-2ubuntu5.3) ...
##################### END CONSOLE OUTPUT #####################

after waiting a while, the only thing I (thought I) could do was hit ctrl-C, which I did and it went on:

#################### START CONSOLE OUTPUT ####################

dpkg: error processing libapache2-mod-php5 (--configure):
 subprocess post-installation script killed by signal (Interrupt)
Setting up libapache2-mod-python (3.3.1-2build1) ...

Setting up libapache2-mod-suphp (0.6.2-2ubuntu1) ...
Installing new version of config file /etc/apache2/mods-available/suphp.conf ...

Setting up libsvn1 (1.5.1dfsg1-1ubuntu2~hardy1) ...

Setting up subversion (1.5.1dfsg1-1ubuntu2~hardy1) ...
Installing new version of config file /etc/bash_completion.d/subversion ...
Installing new version of config file /etc/subversion/config ...
Installing new version of config file /etc/subversion/servers ...
Setting up libapache2-svn (1.5.1dfsg1-1ubuntu2~hardy1) ...
This module is already enabled!
##################### END CONSOLE OUTPUT #####################

I never chose that option again (the plain "see differences" worked OK showing a "diff -u" of both files), at the end of the process I got:

#################### START CONSOLE OUTPUT ####################

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.24-19-server
Errors were encountered while processing:
 libapache2-mod-php5

Could not install the upgrades

The upgrade aborts now. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Please report this bug against the 'update-manager' package and
include the files in /var/log/dist-upgrade/ in the bugreport.
E:Sub-process /usr/bin/dpkg returned an error code (1)

Setting up libapache2-mod-php5 (5.2.4-2ubuntu5.3) ...
Replacing config file /etc/php5/apache2/php.ini with new version
 * Reloading web server config apache2

Could not install the upgrades

The upgrade aborts now. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Please report this bug against the 'update-manager' package and
include the files in /var/log/dist-upgrade/ in the bugreport.
installArchives() failed
##################### END CONSOLE OUTPUT #####################

and here I am...

I manually started apache and it's working, and within it, subversion over https and a moinmoin wiki and a bugzilla I installed manually (not from .deb).

But I didn't dare to reboot until the process somehow tells me everything has been done.

I'm attaching the /var/log/dist-upgrade logs along with the complete console output.

Any hint appreciated.

[MarianoAbsatz (el-baby)]

Well,

finally I took courage and after

Well, apparantly everything went smoothly after

dpkg --configure -a
apt-get autoremove
shutdown -r now

everything went smoothly

PS: I don't think I'm able to close this bug, but whoever sees it that has the power, please do so.

[Michael Vogt (mvo)]

This looks like its a issue with ucf, I reassign.

[MarianoAbsatz (el-baby)]

The reasingatnio could be appropiate, Mike... thanx.

so, IIRC, some packages ask about keeping old config files or installing new ones with options to see diff's via good ole nice console, and others use a "blue" menu (is it debconf?).

One of the choices in the blue menu was about showing "side by side" differences and choosing it got me back to the console terminal, showed nothing and did nothing after hitting <enter>.

After I pressed ctrl-c it apparently aborted the current package upgrade and went on with the next one.

[Steve Langasek (vorlon)]

As best as I can tell, this was a bug in the gutsy version of the ucf package which was used during the upgrade, and is no longer present in current versions of ucf (including the hardy version). Since gutsy is EOLed and there's no way to publish a fix for the ucf package to gutsy-updates, I think we should treat this as resolved.