package mysql-server-5.7 5.7.20-0ubuntu0.17.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[sullyvan]

Error with package mysql-server-5.7 in ubuntu version upgrade and others cases like dpkg --configure -a

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: mysql-server-5.7 5.7.20-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Thu Nov 2 10:19:52 2017
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1
InstallationDate: Installed on 2017-07-09 (115 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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: ['Auths_test', 'sys', 'ib_logfile1', 'ib_logfile0', 'qcx_test', 'redacao_development', 'auto.cnf', 'ib_buffer_pool', 'Auths_development', 'sullyvan_database', 'ibdata1', 'debian-5.7.flag', 'mysql', 'redacao_test', 'mysql_upgrade_info', 'ibtmp1', 'performance_schema', 'sullyvan_test_database', 'qcx_development']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=f35b905a-d766-4c83-8c62-af5b73183f06 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4.6~17.04.1
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.20-0ubuntu0.17.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: Upgraded to zesty on 2017-11-02 (0 days ago)

[Christian Ehrhardt  (paelzer)]

Hi Sullyvan,
from your log:

[ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
[Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
[Note] InnoDB: Retrying to lock the first data file
[ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
[...]
[Note] InnoDB: Unable to open the first data file
[ERROR] InnoDB: Operating system error number 11 in a file operation.
[ERROR] InnoDB: Error number 11 means 'Resource temporarily unavailable'
[Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
[ERROR] InnoDB: Cannot open datafile './ibdata1'
[ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
[ERROR] InnoDB: Plugin initialization aborted with error Cannot open a file

Are there any mysql services still running, like sharing with another version running concurrently.
It also could be a daemon that aborted in a really bad state.
You could start checking if that file is actually open by any process via using "lsof".

Most similar cases [1] also seem to point to still running processes that you have to clean up.
As I suggested lsof is probably the best start tp get this sorted out.

[1]: https://serverfault.com/questions/477448/mysql-keeps-crashing-innodb-unable-to-lock-ibdata1-error-11

[Launchpad Janitor (janitor)]

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