Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 5.5.27
-
Fix Version/s: 5.5.28
-
Component/s: None
-
Labels:None
-
Environment:Ubuntu 12.04.1 Precise i386
Description
After using the DEB repository for a while without any problem, the upgrade just broke. Here is the entire log of dpkg.
Selecting previously unselected package mariadb-server-5.5. (Reading database ... 134882 files and directories currently installed.) Preparing to replace mariadb-server-5.5 5.5.25-mariadb1~precise (using .../mariadb-server-5.5_5.5.27-mariadb1~precise_i386.deb) ... * Stopping MariaDB database server mysqld ...fail! invoke-rc.d: initscript mysql, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... * Stopping MariaDB database server mysqld ...fail! invoke-rc.d: initscript mysql, action "stop" failed. dpkg: error processing /var/cache/apt/archives/mariadb-server-5.5_5.5.27-mariadb1~precise_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 1 * Stopping MariaDB database server mysqld ...fail! invoke-rc.d: initscript mysql, action "stop" failed. * Starting MariaDB database server mysqld ...done.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
It seems this was a one-time-only case. We had to brute-force down the SQL and save everything. After package breakage, a few days, a lot of downtime, we managed to kick MariaDB back in shape.
I don't know what caused the problem. The server only used MariaDB's APT source besides the Ubuntu ones.
Anyway, thanks for looking into it.
I failed to reproduce it.
I've booted precise in a VM, built 5.5.25 debs.
Created local apt repo, installed 5.5.25 from there. Verified that it is installed ok and works.
Replaced local repo with the mariadb repo from http://downloads.mariadb.org/mariadb/repositories/
Upgraded 5.5.25 to 5.5.27 - everything worked.