Comment 5 for bug 1112363

Revision history for this message
Laurent Minost (lolomin) wrote : Re: problems with Percona XtraDB Cluster upgrade 5.5.29

Hi,

Some additional notes on the things that are staying wrong after upgrade, my aptitude is trying to finish the job for the percona-xtradb-cluster-server-5.5 package everytime I ask it to upgrade/install a new package which is causing unnecessary stop/start of MySQL server :

root@galera1:~# aptitude upgrade
The following partially installed packages will be configured:
  percona-xtradb-cluster-server-5.5
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Setting up percona-xtradb-cluster-server-5.5 (5.5.29-23.7.1-387.squeeze) ...
[ ok ] Stopping MySQL (Percona XtraDB Cluster): mysqld.
[ ok ] Starting MySQL (Percona XtraDB Cluster) database server: mysqld . . . . . . ..
[info] Checking for corrupt, not cleanly closed and upgrade needing tables..
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing percona-xtradb-cluster-server-5.5 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 percona-xtradb-cluster-server-5.5
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up percona-xtradb-cluster-server-5.5 (5.5.29-23.7.1-387.squeeze) ...
[ ok ] Stopping MySQL (Percona XtraDB Cluster): mysqld.
[ ok ] Starting MySQL (Percona XtraDB Cluster) database server: mysqld . . . . . . . . ..
[info] Checking for corrupt, not cleanly closed and upgrade needing tables..
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing percona-xtradb-cluster-server-5.5 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 percona-xtradb-cluster-server-5.5

Do you know if I can safely avoid it to try finishing the configuration part of the package as it will never finish in the current case due to previous errors reported ? If yes, then how ?

Regards,

Laurent