I just tested upgrading from 5.5.30 to 5.5.31 and it still fails to upgrade when you put an 'exit 0' directly at the start of debian-start:
Preparing to replace percona-server-server-5.5 5.5.30-rel30.1-465.precise (using .../percona-server-server-5.5_1%3a5.5.31-rel30.3-520.precise_amd64.deb) ...
* Stopping MySQL (Percona Server) mysqld [ OK ]
Unpacking replacement percona-server-server-5.5 ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up percona-server-server-5.5 (1:5.5.31-rel30.3-520.precise) ...
* Stopping MySQL (Percona Server) mysqld [ OK ]
* Percona Server is distributed with several useful UDF (User Defined Function) from Percona Toolkit.
* Run the following commands to create these functions:
mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
* Starting MySQL (Percona Server) database server mysqld [ OK ]
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing percona-server-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
percona-server-server-5.5
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also, if I currently start a server part of a percona-cluster with the initscript and it's going to do an SST it claims to have failed as well, so there are still things to tweak on the init-script.
I just tested upgrading from 5.5.30 to 5.5.31 and it still fails to upgrade when you put an 'exit 0' directly at the start of debian-start:
Preparing to replace percona- server- server- 5.5 5.5.30- rel30.1- 465.precise (using .../percona- server- server- 5.5_1%3a5. 5.31-rel30. 3-520.precise_ amd64.deb) ... server- server- 5.5 ... server- server- 5.5 (1:5.5. 31-rel30. 3-520.precise) ...
* Stopping MySQL (Percona Server) mysqld [ OK ]
Unpacking replacement percona-
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up percona-
* Stopping MySQL (Percona Server) mysqld [ OK ]
* Percona Server is distributed with several useful UDF (User Defined Function) from Percona Toolkit.
* Run the following commands to create these functions:
mysql -e "CREATE FUNCTION fnv1a_64 RETURNS INTEGER SONAME 'libfnv1a_udf.so'"
mysql -e "CREATE FUNCTION fnv_64 RETURNS INTEGER SONAME 'libfnv_udf.so'"
mysql -e "CREATE FUNCTION murmur_hash RETURNS INTEGER SONAME 'libmurmur_udf.so'"
* See http:// www.percona. com/doc/ percona- server/ 5.5/management/ udf_percona_ toolkit. html for more details
* Starting MySQL (Percona Server) database server mysqld [ OK ] server- server- 5.5 (--configure): server- server- 5.5
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing percona-
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
percona-
E: Sub-process /usr/bin/dpkg returned an error code (1)
Also, if I currently start a server part of a percona-cluster with the initscript and it's going to do an SST it claims to have failed as well, so there are still things to tweak on the init-script.