package mysql-server-5.7 5.7.30-0ubuntu0.16.04.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1

[Tiago Moreira]

I was installing this package when the error ocurred.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.30-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.15.0-101.102~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu May 28 03:24:49 2020
ErrorMessage: subprocesso script post-installation instalado retornou erro do status de saída 1
Logs.var.log.daemon.log:

MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['public_key.pem', 'ib_logfile0', 'debian-5.7.flag', 'performance_schema', 'ibdata1', 'server-key.pem', 'server-cert.pem', 'client-cert.pem', 'ca.pem', 'ib_logfile1', 'private_key.pem', 'client-key.pem', 'auto.cnf', 'ib_buffer_pool', 'sys', 'ca-key.pem', 'mysql']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1e5d1b18-b400-4e5a-815a-02e69b204107 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt 1.2.29ubuntu0.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.30-0ubuntu0.16.04.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Mark Morlino (markmorlino)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Christian Ehrhardt  (paelzer)]

Hi,
the logs all point to the assumption that there might be a seconds mysl daemon process still running, from your logs:

2020-05-28T01:47:45.943449Z 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2020-05-28T01:47:45.943476Z 0 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2020-05-28T01:47:45.943485Z 0 [Note] InnoDB: Retrying to lock the first data file

...

2020-05-28T02:25:51.531290Z 0 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use
2020-05-28T02:25:51.531294Z 0 [ERROR] Do you already have another mysqld server running on port: 3306 ?
2020-05-28T02:25:51.531307Z 0 [ERROR] Aborting

That is a conflict as on the update/upgrade the packaging system needs to restart the service.
By restarting the packaged service the collision with - whatever else is up - is happening.

The only other chance is that stopping the process failed, but I found many proper
2020-05-27T15:54:28.098127Z 0 [Note] /usr/sbin/mysqld: Shutdown complete
So I'd tihnk that isn't the case.

You'd need to find what you have running in background and resolve that - then restarting and thereby the upgrade will work again.

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

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