Infinite loop upgrading to 5.1.41-3ubuntu12.6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-dfsg-5.1 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
If MySQL is not startable, the package cannot continue. History...
Performed a dist-upgrade on a Lucid box installed a few weeks ago.
The dist-upgrade became stuck:
Setting up libmysqlclient16 (5.1.41-
Setting up mysql-client-
Setting up mysql-client-5.1 (5.1.41-
Setting up mysql-server-
Setting up mysql-server-5.1 (5.1.41-
Installing new version of config file /etc/init/
Looking at vmstat in another shell it was doing nothing, 100% idle.
Looking at ps:
jamesg@sutton:~$ ps ax | grep mysql
3665 pts/1 S+ 0:00 /usr/bin/perl -w /usr/share/
3675 pts/1 S+ 0:00 /bin/bash -e /var/lib/
3779 pts/1 S+ 0:00 start mysql
5962 pts/2 S+ 0:00 grep --color=auto mysql
31891 pts/1 Ss+ 0:00 /usr/bin/dpkg --status-fd 24 --configure linux-image-
Figured I'd kill pid 3675 which did indeed complete the dist-upgrade.
Seems I had left MySQL in an un-startable state (Innodb unhappy with the log file sizes being changed, they needed to be removed).
This should not however cause a dist-upgrade to hang!
Changed in mysql-dfsg-5.1 (Ubuntu): | |
status: | Incomplete → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
According to the log files:
Installing new version of config file /etc/init/ mysql.conf ...
Was there a prompt for merging configuration files?
How long did you wait? Could you add the content of /var/log/daemon.log at the time of the upgrade to figure out why mysql was failing to start?