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

Bug #1017258 reported by Doug Orleans
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mysql-5.5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

During routine upgrade, mysql-server-5.5 started failing to be installed.

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
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-5.5; however:
  Package mysql-server-5.5 is not configured yet.
dpkg: error processing mysql-server (--configure):
 dependency problems - leaving unconfigured

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.24-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
Uname: Linux 3.2.0-25-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
AptOrdering:
 mysql-server-5.5: Configure
 mysql-server: Configure
Architecture: i386
Date: Sun Jun 24 17:32:33 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLConf.etc.mysql.conf.d.utf8.cnf:
 [mysqld]
 default-character-set = utf8

 [mysql]
 default-character-set = utf8
MySQLVarLibDirListing: ['editions_test', 'debian-5.1.flag', 'taction800', 'editions_dev', 'ibdata1', 'ib_logfile1', 'taper', 'nea', 'dcm', 'ib_logfile0', 'mysql', 'test', 'myworker', 'longtrail', 'cider', 'debian-5.5.flag', 'mysql_upgrade_info']
SourcePackage: mysql-5.5
Title: 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
UpgradeStatus: Upgraded to precise on 2012-05-04 (51 days ago)

Revision history for this message
Doug Orleans (dougorleans) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Marc Cluet (lynxman) wrote :

Hi Doug,

Thank you very much for your bug report!

I'm afraid I don't have enough information with what you provided in order to make an assessment of what's going wrong in your installation.

Could you please provide the mysql error log as well? It normally resides in /var/log/mysql/

As soon as you've attached the log please mark the bug again as 'New' so it can be reviewed.

Thanks!

Changed in mysql-5.5 (Ubuntu):
status: New → Incomplete
Revision history for this message
Ryan (silverphp) wrote :

I am too having this problem. I have a new installation of ubuntu 12.04 and logs in /var/log/mysql/ are empty. I get the same errors as Doug's initial report.

Apologies if I have missed anything, first time here.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

It appears /var/log/mysql/error.log was left out of 12.04's mysql default configuration. However, upstart should be logging the output of all jobs. So can you look at /var/log/upstart/mysql.log ?

Also anybody affected can try 'sudo /usr/sbin/mysqld' and paste that here.. it will likely give the reason mysqld failed to start.

Changed in mysql-5.5 (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Doug Orleans (dougorleans) wrote :
Revision history for this message
Doug Orleans (dougorleans) wrote :

dougo@quiet:~$ sudo /usr/sbin/mysqld
120908 17:59:11 [Note] Plugin 'FEDERATED' is disabled.
120908 17:59:11 InnoDB: The InnoDB memory heap is disabled
120908 17:59:11 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120908 17:59:11 InnoDB: Compressed tables use zlib 1.2.3.4
120908 17:59:11 InnoDB: Initializing buffer pool, size = 128.0M
120908 17:59:11 InnoDB: Completed initialization of buffer pool
120908 17:59:11 InnoDB: highest supported file format is Barracuda.
120908 17:59:11 InnoDB: Waiting for the background threads to start
120908 17:59:12 InnoDB: 1.1.8 started; log sequence number 175907270
120908 17:59:12 [ERROR] /usr/sbin/mysqld: unknown variable 'default-character-set=utf8'
120908 17:59:12 [ERROR] Aborting

120908 17:59:12 InnoDB: Starting shutdown...
120908 17:59:13 InnoDB: Shutdown completed; log sequence number 175907270
120908 17:59:13 [Note] /usr/sbin/mysqld: Shutdown complete

Revision history for this message
Doug Orleans (dougorleans) wrote :

So it turns out that I have the file /etc/mysql/conf.d/utf8.cnf:

[mysqld]
default-character-set = utf8

[mysql]
default-character-set = utf8

I don't remember if I put that there myself or not (it's dated Jul 29 2011). But following the advice from http://bugs.mysql.com/bug.php?id=52047 I changed the setting for [mysqld] to this:

character-set-server = utf8

and now I am up and running again. Whew!

Changed in mysql-5.5 (Ubuntu):
status: Incomplete → New
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Doug, thanks for responding. I suspect others may be bitten by that problem if they have modified /etc/mysql/my.cnf

Changed in mysql-5.5 (Ubuntu):
status: New → Invalid
Revision history for this message
Doug Orleans (dougorleans) wrote :

Is there a way for the installation process to check for that problem, to at least fail with a more useful message? (I'm surprised there was no deprecation message in previous versions.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.