package mysql-server-5.7 5.7.22-0ubuntu18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 2

Bug #1775021 reported by Slavik Koval
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mysql-5.7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Mysql server generates error on start up.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mysql-server-5.7 5.7.22-0ubuntu18.04.1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
Date: Mon Jun 4 09:38:30 2018
ErrorMessage: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 2
InstallationDate: Installed on 2018-06-01 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Logs.var.log.daemon.log:

MySQLVarLibDirListing: ['ibdata1', 'ib_buffer_pool', 'debian-5.7.flag', 'ib_logfile1', 'mysql', 'bcdocs', 'performance_schema', 'sys', 'ib_logfile0', 'auto.cnf']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=e10561fc-59b5-4892-9f33-2dda4dc5c709 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.22-0ubuntu18.04.1 failed to install/upgrade: installed mysql-server-5.7 package post-installation script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.mysql.debian-start: [deleted]
modified.conffile..etc.mysql.mysql.cnf: [modified]
modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [deleted]
modified.conffile..etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [deleted]
mtime.conffile..etc.mysql.mysql.cnf: 2018-06-04T09:43:40.260147

Revision history for this message
Slavik Koval (slakov) wrote :
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Thanks for filing this bug in Ubuntu.

I see you installed and purged mysql multiple times in a matter of minutes, coupled with config file changes.

Eventually it failed with error messages like:
2018-06-04T07:22:38.355592Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.22-0ubuntu18.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
2018-06-04T07:22:44.638691Z 2 [Note] Access denied for user 'root'@'localhost'
2018-06-04T07:28:48.825508Z 3 [Note] Access denied for user 'root'@'localhost'
2018-06-04T07:37:37.691235Z 0 [Note] Giving 0 client threads a chance to die gracefully
2018-06-04T07:37:37.691265Z 0 [Note] Shutting down slave threads
...
2018-06-04T07:37:37.792556Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2018-06-04T07:37:37.792917Z 0 [ERROR] InnoDB: Cannot open '/var/lib/mysql/ib_buffer_pool.incomplete' for writing: No such file or directory
2018-06-04T07:37:39.542696Z 0 [Note] InnoDB: Shutdown completed; log sequence number 2590304

and

Setting up mysql-server-5.7 (5.7.22-0ubuntu18.04.1) ...
update-alternatives: error: alternative path /etc/mysql/mysql.cnf doesn't exist
dpkg: error processing package mysql-server-5.7 (--configure):
 installed mysql-server-5.7 package post-installation script subprocess returned error exit status 2

It is hard to diagnose this sequence of events.

I suggest you really purge all mysql packages and its config files, and start over. If you can get us a precise sequence of events that lead to an error, then please paste them in this bug.

Thanks

Changed in mysql-5.7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.]

Changed in mysql-5.7 (Ubuntu):
status: Incomplete → Expired
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.