package mysql-server-5.5 5.5.28-0ubuntu0.12.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1075251 reported by arulvg
312
This bug affects 60 people
Affects Status Importance Assigned to Milestone
mysql-5.5 (Ubuntu)
Fix Released
Critical
mudays

Bug Description

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
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 mysql-server-5.5

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.28-0ubuntu0.12.04.2
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Mon Nov 5 22:55:40 2012
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['mysql', 'debian-5.5.flag', 'test', 'ijdb', 'ib_logfile1', 'ibdata1', 'performance_schema', 'ib_logfile0', 'mysql_upgrade_info']
SourcePackage: mysql-5.5
Title: package mysql-server-5.5 5.5.28-0ubuntu0.12.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
arulvg (arulvg) wrote :
tags: removed: need-duplicate-check
Revision history for this message
awilliams (the-squad) wrote :

I am also having this problem:

Reading package lists... Done
Building dependency tree
Reading state information... Done
mysql-server-core-5.5 is already the newest version.
The following packages were automatically installed and are no longer required:
  libboost-program-options1.49.0 libboost-thread1.49.0 libkolabxml0 phpmyadmin
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up mysql-server-5.5 (5.5.28-0ubuntu0.12.10.1) ...
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
No apport report written because MaxReports is reached already
                                                              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
No apport report written because MaxReports is reached already
                                                              Errors were encountered while processing:
 mysql-server-5.5
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mysql-5.5 (Ubuntu):
status: New → Confirmed
Revision history for this message
J.D. Stone (jdstone) wrote :

I was able to fix this...

Steps

1) I ran 'sudo mysqld' and noticed the error:

[Note] Server hostname (bind-address): '10.0.1.13'; port: 3306
[Note] - '10.0.1.13' resolves to '10.0.1.13';
[Note] Server socket created on IP: '10.0.1.13'.
[ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address

I realized that I had the 'bind-address' directive set to: 'bind-address = 10.0.1.13' and remembered that my IP address changed on my server, so once I commented that out or changed it to 'bind-address = 192.168.11.45', I was able to re-run 'upgrade' on apt again and this time 'Setting up mysql-server-5.5 (5.5.28-0ubuntu0.12.04.2) ...' passed and didn't fail.

So this might work for you...

Revision history for this message
Andrey Kudinov (elhana) wrote :

In my case /var/log/mysql/error.log says:
InnoDB: Operating system error number 22 in a file operation.
InnoDB: Error number 22 means 'Invalid argument'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html
InnoDB: File name ./ib_logfile0
InnoDB: File operation call: 'aio write'.
InnoDB: Cannot continue operation.

google blames tmpfs, disabling Linux native aio solves it for me: innodb_use_native_aio = 0 in my.cnf

Changed in mysql-5.5 (Ubuntu):
importance: Undecided → High
Changed in mysql-5.5 (Ubuntu):
importance: High → Critical
Revision history for this message
wannabeelinux (bas-douma) wrote :

I tried to install MySQL and change the location of my databases. After that MySQL stopped working.

Revision history for this message
Oh the Huge Manatee (vertesi-n) wrote :

Noting that I had this problem too... and like wannabeelinux my mysql datadir was non-default.

MySQL runs just fine pre-update (with some tweaking of the apparmor directory access config), but it's possible that the upgrade script assumes a datadir location. I have it simlinked to the default directory for convenience, so it's possible that a test for /var/lib/mysql passes even though the actual data is elsewhere (on another filesystem).

Revision history for this message
Michael Hasenstein (hasenstein) wrote :

The deprecated character-set setting mentioned above did it for me: I had to change default-character-set=utf8 to character-set-server=utf8

Also see http://ronaldbradford.com/blog/tag/mysql-5-5/

Revision history for this message
Michael Hasenstein (hasenstein) wrote :

Addendum:

It helps to run

sudo mysqld

to see what the mysql-daemon has to complain about on your particular system - the messages one sees in apt-get don't help in these cases. The mysql log files had no contents either.

Revision history for this message
cement_head (andorjkiss) wrote :

Any suggestions on fixing my issue?

$ sudo mysqld
130222 9:41:07 [Note] Plugin 'FEDERATED' is disabled.
130222 9:41:07 InnoDB: The InnoDB memory heap is disabled
130222 9:41:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130222 9:41:07 InnoDB: Compressed tables use zlib 1.2.3.4
mysqld: Can't create/write to file '/tmp/ibL88fI1' (Errcode: 13)
130222 9:41:07 InnoDB: Error: unable to create temporary file; errno: 13
130222 9:41:07 [ERROR] Plugin 'InnoDB' init function returned error.
130222 9:41:07 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
130222 9:41:07 [ERROR] Unknown/unsupported storage engine: InnoDB
130222 9:41:07 [ERROR] Aborting

Revision history for this message
Andrey Kudinov (elhana) wrote :

@cement_head: errno 13 - permission denied, most likely that will help:
sudo chmod 1777 /tmp
sudo chown root:root /tmp

Revision history for this message
cement_head (andorjkiss) wrote :

@elhana

Nope, it was an AppArmour setting - we have our tmp drive linked to another location (our boot drive is only 120 GB SSD).

Thanks,
CH

Revision history for this message
valentinh (valentin-hancu) wrote :

During the upgrade I accepted the maintainer my.cnf and resulted in mysql not starting.
I reverted to the old my.cnf and the upgrade process finished with succes.

I attached the diff between old and new my.cnf.

# diff -u my.cnf.dpkg-new my.cnf.dpkg-old
--- my.cnf.dpkg-new 2013-03-05 11:01:55.738893959 +0200
+++ my.cnf.dpkg-old 2013-01-15 16:12:43.695754573 +0200
@@ -72,9 +72,7 @@
 #general_log_file = /var/log/mysql/mysql.log
 #general_log = 1
 #
-# Error log - should be very few entries.
-#
-log_error = /var/log/mysql/error.log
+# Error logging goes to syslog due to /etc/mysql/conf.d/mysqld_safe_syslog.cnf.
 #
 # Here you can see queries with especially long duration
 #log_slow_queries = /var/log/mysql/mysql-slow.log
@@ -96,6 +94,8 @@
 # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
 # Read the manual for more InnoDB related options. There are many!
 #
+
+innodb_log_file_size=268435456
 # * Security Features
 #
 # Read the manual, too, if you want chroot!

Revision history for this message
Luis Henrique Puhl de Souza (luispuhl) wrote :

After lost my machine (bad lucky week) i try to set a new one;
I've tried twice painfully that was my fault;

Setting up mysql-server-core-5.5 (5.5.29-0ubuntu0.12.04.2) ...
Setting up mysql-server-5.5 (5.5.29-0ubuntu0.12.04.2) ...
130315 12:22:27 [Note] Plugin 'FEDERATED' is disabled.
130315 12:22:27 InnoDB: The InnoDB memory heap is disabled
130315 12:22:27 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130315 12:22:27 InnoDB: Compressed tables use zlib 1.2.3.4
130315 12:22:27 InnoDB: Initializing buffer pool, size = 128.0M
130315 12:22:27 InnoDB: Completed initialization of buffer pool
130315 12:22:27 InnoDB: highest supported file format is Barracuda.
130315 12:22:27 InnoDB: Waiting for the background threads to start
130315 12:22:28 InnoDB: 1.1.8 started; log sequence number 1595675
130315 12:22:28 InnoDB: Starting shutdown...
130315 12:22:29 InnoDB: Shutdown completed; log sequence number 1595675
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
No apport report written because the error message indicates its a followup error from a previous failure.
                                                                                                          Errors were encountered while processing:
 mysql-server-5.5
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error

mudays (muday23schatzi)
Changed in mysql-5.5 (Ubuntu):
assignee: nobody → mudays (muday23schatzi)
Changed in mysql-5.5 (Ubuntu):
status: Confirmed → Fix Released
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.