Hello, Thanks for filing this bug. However, from your logs: [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11
This looks like a duplicate of LP: #1928329. Further, this is actually a local configuration issue rather than a bug and here's the known workaround: https://serverfault.com/questions/477448/mysql-keeps-crashing-innodb-unable-to-lock-ibdata1-error-11 Let me know if you this doesn't work for you. That said, I'm marking this as "Incomplete" since this doesn't look like a bug but if you think otherwise, please set it back to "New" and let us know why? While at it, could you also help us with a reproducer of this issue? So that we can reproduce and help fix this. Thank you! From /var/log/mysql/error.log.txt: 2025-05-10T17:26:54.761581Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2025-05-10T17:26:55.761925Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2025-05-10T17:26:56.762448Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11 2025-05-10T17:26:56.762574Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 11 in a file operation. 2025-05-10T17:26:56.762593Z 1 [ERROR] [MY-012596] [InnoDB] Error number 11 means 'Resource temporarily unavailable' 2025-05-10T17:26:56.762609Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1' 2025-05-10T17:26:56.762623Z 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! 2025-05-10T17:26:56.762648Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file. 2025-05-10T17:26:56.767906Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2025-05-10T17:26:56.768508Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2025-05-10T17:26:56.768674Z 0 [ERROR] [MY-010119] [Server] Aborting 2025-05-10T17:26:56.770135Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.42-0ubuntu0.24.04.1) (Ubuntu). From DpkgTerminal.log: Removing mysql-server (8.0.42-0ubuntu0.24.04.1) ... Removing mysql-server-8.0 (8.0.42-0ubuntu0.24.04.1) ... [0;1;38;5;185mWarning: The unit file, source configuration file or drop-ins of mysql.service changed on disk. Run 'systemctl daemon-reload' to reload units.[0m ^X^e[0;1;31mJob for mysql.service canceled.[0m invoke-rc.d: initscript mysql, action "stop" failed. [1mdpkg:[0m error processing package mysql-server-8.0 (--remove): installed mysql-server-8.0 package pre-removal script subprocess returned error exit status 1 [1mdpkg:[0m too many errors, stopping ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete ** Summary changed: - package mysql-server-8.0 8.0.42-0ubuntu0.24.04.1 failed to install/upgrade: installed mysql-server-8.0 package pre-removal script subprocess returned error exit status 1 + package mysql-server-8.0 8.0.42-0ubuntu0.24.04.1 failed to install/upgrade: [InnoDB] 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/2110379 Title: package mysql-server-8.0 8.0.42-0ubuntu0.24.04.1 failed to install/upgrade: [InnoDB] Unable to lock ./ibdata1 error: 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2110379/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
