Casual googling seems to show this is possibly due to an AppArmor configuration setting. Workaround seems to be to kill the old mysqld process and resume installation.
https://stackoverflow.com/questions/35978228/how-to-solve-innodb-unable-to-lock-ibdata1-mysql-error https://serverfault.com/questions/477448/mysql-keeps-crashing-innodb-unable-to-lock-ibdata1-error-11 https://bobcares.com/blog/innodb-unable-to-lock-ibdata1-error-11/ ** Description changed: The mysql package it's not installing ProblemType: Package DistroRelease: Ubuntu 19.10 Package: mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Jan 29 15:44:29 2020 ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-01-29 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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 + [mysqldump] + quick + quote-names + max_allowed_packet = 16M MySQLVarLibDirListing: ['ib_logfile1', 'binlog.000005', 'client-key.pem', 'binlog.000002', 'binlog.000001', 'binlog.index', 'server-cert.pem', 'undo_002', 'ca.pem', 'private_key.pem', '#innodb_temp', 'binlog.000006', 'ib_buffer_pool', 'binlog.000003', 'auto.cnf', 'public_key.pem', 'sys', 'client-cert.pem', 'mysql', 'server-key.pem', 'undo_001', 'binlog.000004', 'ca-key.pem', 'memelli.pid', 'ibdata1', 'ib_logfile0', 'mysql.ibd', 'binlog.000007', 'performance_schema', 'ibtmp1', 'debian-5.7.flag'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=6cce31bf-b407-4edb-b53a-e826bbad020e ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: - dpkg 1.19.7ubuntu2 - apt 1.9.4 + dpkg 1.19.7ubuntu2 + apt 1.9.4 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) + + From /var/log/mysql/error.log: + 2020-01-29T18:42:48.412365Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.19-0ubuntu0.19.10.3) starting as process 15295 + 2020-01-29T18:42:48.484149Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 + 2020-01-29T18:42:49.484784Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 + ... + + 2020-01-29T18:44:28.604249Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 + 2020-01-29T18:44:28.607059Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation. + 2020-01-29T18:44:28.608039Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable' + 2020-01-29T18:44:28.609768Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1' + 2020-01-29T18:44:28.610647Z 1 [ERROR] [MY-012959] [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! + 2020-01-29T18:44:28.611075Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file. + 2020-01-29T18:44:29.000778Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine + 2020-01-29T18:44:29.002706Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. + 2020-01-29T18:44:29.004586Z 0 [ERROR] [MY-010119] [Server] Aborting + 2020-01-29T18:44:29.005492Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.19-0ubuntu0.19.10.3) (Ubuntu). + 2020-01-29T18:44:29.638006Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.19-0ubuntu0.19.10.3) starting as process 15409 + 2020-01-29T18:44:29.851537Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 ** Summary changed: - package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 + package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: Unable to lock ./ibdata1 error: 11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861323 Title: package mysql-server-8.0 8.0.19-0ubuntu0.19.10.3 failed to install/upgrade: Unable to lock ./ibdata1 error: 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1861323/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
