Comment 6 for bug 1434022

Revision history for this message
Michael Wang (xw73) wrote :

This bug affects more on the install and upgrade process than starting up the database routinely, because if you start up the database manually, you can always wait and check the log file after it reports startup "failure", however during the upgrade, after the startup failure, the post configuration process also fails and package state is in limbo. Next time when you try to run the package command, it will try to re-run the command to finish the unfinished business (at least this is the case on Ubuntu).

The workaround is to have a version of modified /etc/init.d/mysql in place, and run the installation command with the option NOT to replace the configuration file. It is like below on Ubuntu:

# export DEBIAN_FRONTEND=noninteractive
# apt-get -y -o Dpkg::Options::="--force-confold" install percona-server-server-5.6

I spent a lot of time figured out all these, hope this helps.