Forwarded to devs MySQL 8 database dump fails

[Duarte N]

Username:

TITLE

MySQL 8 database dump fails

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.65_build20241025.12 os_Windows 2012/2016/2019/2022

PROBLEM DESCRIPTION

After upgrading to build 18.0.65 it is not possible to dump MySQL 8.0 databases:

Unable to make database dump. Error: Failed to exec mysqldump.exe: Exit code: 2: mysqldump.exe: Couldn't execute '/*!100100 SET WAIT_TIMEOUT=DEFAULT */': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0 SET WAIT_TIMEOUT=DEFAULT */' at line 1 (1064)

Scheduled backups also fail to dump the databases with the following warning:

WARNING:      (Database object 'xxxxxxxx')      Unable to make database dump. Error: Failed to exec mysqldump.exe: Exit code: 2: mysqldump.exe: Couldn't execute '/*!100100 SET WAIT_TIMEOUT=DEFAULT */': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0 SET WAIT_TIMEOUT=DEFAULT */' at line 1 (1064)

STEPS TO REPRODUCE

Choose a MySQL 8.0 database and perform "Export Dump".

ACTUAL RESULT

Unable to make database dump. Error: Failed to exec mysqldump.exe: Exit code: 2: mysqldump.exe: Couldn't execute '/*!100100 SET WAIT_TIMEOUT=DEFAULT */': You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '0 SET WAIT_TIMEOUT=DEFAULT */' at line 1 (1064)

EXPECTED RESULT

Database exported successfully, as well as backups performed successfully.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

Thank you for the report, @Duarte N. Our engineers are currently reviewing the provided information.

 

[flyd]

I have the same problem... Backup or exporting database don't work from the last update...

Do you have any update about this bug?

 

[Sebahat.hadzhi]

Hello, @flyd. Our engineers are still investigating the case. We understand that this situation is not pleasant. Our team is doing its best to find the culprit of the issue as quickly as possible. Thank you in advance for your understanding on the matter.