Thank you for taking the time to file a bug report. Checking the logs I found quite a number of messages like these:
2020-09-29T09:51:21.976605Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2020-09-29T09:51:22.977176Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2020-09-29T09:51:23.977731Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2020-09-29T09:51:24.978318Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 ... 2020-09-29T09:53:02.131335Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation. 2020-09-29T09:53:02.132460Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable' 2020-09-29T09:53:02.134555Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1' 2020-09-29T09:53:02.135632Z 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-09-29T09:53:02.136765Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file. 2020-09-29T09:53:02.507848Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2020-09-29T09:53:02.509330Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2020-09-29T09:53:02.511577Z 0 [ERROR] [MY-010119] [Server] Aborting As is explained above, "error 11" means that the resource (in thi case, the file "./ibdata1") is unavailable. MySQL tried to acquire a lock on the file but didn't succeed. This probably means that there is a lock already in place for the file. If that's the case, then it is likely that there is still an instance of mysql-server running. You could try checking that with "htop" or something like "lsof -i:3306". If you see a mysqld process running, you should kill it before trying to reinstall the package. 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 ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897714 Title: package mysql-server-8.0 8.0.21-0ubuntu0.20.04.4 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1897714/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
