mysql_upgrade failed with exit status 11

[Ivan Podporin]

reboot pc

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server 5.7.16-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
Uname: Linux 4.4.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Oct 26 05:28:01 2016
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2013-11-09 (1084 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Logs.var.log.daemon.log:

Logs.var.log.mysql.error.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: ['shard2', 'auto.cnf', 'performance_schema', 'ib_buffer_pool', 'sys', 'mysql', 'ib_logfile1', 'debian-5.7.flag', 'ib_logfile0', 'mysql_upgrade_info', 'debian-5.6.flag', 'shard1', 'ibdata1', 'debian-5.5.flag', 'phpmyadmin']
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic root=UUID=78a94456-a1e9-47bb-87f0-d8dbe7ce9590 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.14
SourcePackage: mysql-5.7
Title: package mysql-server 5.7.16-0ubuntu0.16.04.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

[Nish Aravamudan (nacc)]

Hello and thank you for this bug report:

Did you ever have MySQL successfully running on this system?

From: https://launchpadlibrarian.net/291382463/Logs.var.log.mysql.error.log.txt, it seems like there might have been historical configuration issues (unable to lock ./ibdata1), but the last line indicates a successful start-up. Can you please clarify what the precise issue is at the current moment?

[Nish Aravamudan (nacc)]

I apologize! I confused this bug with another mysql-5.7 bug's logs I was examining at the same time.

[Launchpad Janitor (janitor)]

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

[Daniel Black (daniel-black)]

"unable to lock ./ibdata1" is a pretty sure indication that an existing mysqld is running at the time another instance was trying to start up.

[Joshua Powers (powersj)]

Thank you for taking the time to file a bug report.

As pointed out above it is likely that another mysql daemon is running.

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

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

[Launchpad Janitor (janitor)]

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