Startup Issue with MySQL - MySQL fails to start: missing libaio.so.1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 13 on x86_64
Product AMP ‘Phobos’ v2.6.3.2 (Mainline)
Virtualization Docker
Application MySQL
Module GenericModule
Running in Container Yes
Current State Stopped

Problem Description

Issue

Hello,
when attempting to start the MySQL service within my AMP GamePanel, the server fails to launch and reports the following error:

mysql/bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

This indicates that the system library libaio (required by MySQL for asynchronous I/O) is missing from the host environment. Since I do not have terminal or root access to the host system, I’m unable to install it myself.

How do i install libaio?

Reproduction Steps

  • Start or restart the AMP instance containing MySQL.
  • Check the AMP logs or MySQL startup logs
  • Observe the error message:

The wonderful bugs of AMP

It should be installing the package in the Docker container when starting the instance, but is not

Click on the pencil icon on the instance, go to Container Settings, check that the package is listed under Extra container packages, and if so click Save Changes

Yes, saving what is already there seems to kick AMP into gear

Sigh

Actually, I take that back on this occasion xD

The package name needs to be updated for debian 13, since it has changed from libaio1 to libaio1t64. Often debian is able to automatically transition the installation, not in this case

So you can manually change the extra container package name, or update your instance by clicking on the down arrow on the instance tile, and it will be fixed for you

I added the package, but i still get following error:
mysql/bin/mysqld: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory

Im going to add an screenshot of the config for clarity:

Just click the down arrow on the instance tile to update it

Did it 3 times already. could there be some other error?

Did some further testing. MySQL claims that 8.4 supports Debian 13, but the server continues to look for libaio1 rather than libaio1t64 and so fails

Currently testing an alternative solution

I’ve reverted the template to use the Debian 12 image for the time being, so that the required libs are available

Create a new instance

Down the track I will look at putting together a custom image for MySQL so that it can run on Debian 13

is there any way, to keep the data or revert the update?

Sure, just update the instance again, and it should switch the image and the extra packages being installed

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.