[MDEV-566] MariaDB 5.5.25 fails to upgrade (with .27) on Precise Created: 2012-09-29  Updated: 2012-10-10  Resolved: 2012-10-10

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.27
Fix Version/s: 5.5.28

Type: Bug Priority: Major
Reporter: Pjotr Assignee: Sergei Golubchik
Resolution: Cannot Reproduce Votes: 0
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.



 Comments   
Comment by Sergei Golubchik [ 2012-10-10 ]

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.

Comment by Pjotr [ 2012-10-10 ]

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.

Generated at Thu Feb 08 06:29:42 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.