{page-title}
{kb-symptom}
When restoring a mySQL database, you may encounter the following error:
{code}Failed to start temporary database instance
MySQLD executable not found! (Path: (deleted) /usr/sbin/mysqld)
{code}
{kb-cause}
The CDP agent is unable to determine the path to the mysqld binary. This can occur when MySQL is updated but not restarted following the updates. The agent reads information about the reported MySQL pid to get the path to the mysqld binary. In some cases, after updates are applied, the information read by the agent is no longer current.
Example: (Assuming the pid is reported by MySQL as 12345)
{code}root@mysql# ls \-ld /proc/12345/exe
lrwxrwxrwx 1 root root 0 Jan 01 00:00 /proc/12345/exe \-> (deleted)\ /usr/sbin/mysqld
{code}
The method that the CDP Agent uses to determine the path to mysqld may change in the future, but for now this is the current method.
{kb-resolution}
Restart MySQL to refresh the pid information.
Re-try the restore.
{kb-related-articles}
{kb-symptom}
When restoring a mySQL database, you may encounter the following error:
{code}Failed to start temporary database instance
MySQLD executable not found! (Path: (deleted) /usr/sbin/mysqld)
{code}
{kb-cause}
The CDP agent is unable to determine the path to the mysqld binary. This can occur when MySQL is updated but not restarted following the updates. The agent reads information about the reported MySQL pid to get the path to the mysqld binary. In some cases, after updates are applied, the information read by the agent is no longer current.
Example: (Assuming the pid is reported by MySQL as 12345)
{code}root@mysql# ls \-ld /proc/12345/exe
lrwxrwxrwx 1 root root 0 Jan 01 00:00 /proc/12345/exe \-> (deleted)\ /usr/sbin/mysqld
{code}
The method that the CDP Agent uses to determine the path to mysqld may change in the future, but for now this is the current method.
{kb-resolution}
Restart MySQL to refresh the pid information.
Re-try the restore.
{kb-related-articles}