package mysql-server-5.5 5.5.24-0ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-5.5 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
philip@
Description: Ubuntu 12.04 LTS
Release: 12.04
apt-cache policy mysql-server-5.5
mysql-server-5.5:
Installed: 5.5.24-
Candidate: 5.5.24-
Version table:
*** 5.5.24-
500 http://
500 http://
100 /var/lib/
5.
500 http://
expectation:
Mysql to complete update-reinstall from Ubuntu 11.10 to 12.04. Mysql stopped working since the 12.04 release.
Unexpected:
Setting up mysql-server-5.5 (5.5.24-
start: Job failed to start
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.24-
ProcVersionSign
Uname: Linux 3.2.0-25-generic i686
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Wed Jun 27 10:31:21 2012
DuplicateSignature:
Setting up mysql-server-5.5 (5.5.24-
start: Job failed to start
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.5 (--configure):
subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release i386 (20101008.1)
Logs.var.
MySQLConf.
[mysqld_safe]
syslog
MySQLVarLibDirL
SourcePackage: mysql-5.5
Title: package mysql-server-5.5 5.5.24-
UpgradeStatus: Upgraded to precise on 2012-04-28 (60 days ago)
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1012058, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.