Symptoms
-
The backup log contains errors that are similar to the following:
Warning: Database "admin_wp_example"
Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol.
mysqldump: Got error: 1045: "Access denied for user 'admin'@'::1' (using password: YES)" when trying to connect -
The Plesk Migrator fails to connect to the source database server and issues the following error:
Failed to fetch basic information about resellers, clients and domains data from source servers
Cause: Failed to execute SQL query on panel database: Can not connect to the Plesk database. Please, check database server is running.
That is a critical error, migration was stopped. -
The following warnings can be found for the MariaDB (or MySQL) service:
# journalctl -u mariadb
Jan 01 00:00:00 host.example.com mariadbd[PID]: 2000-01-01 0:00:00 [Warning] Access denied for user 'admin'@'::1' (using password: YES)
Jan 01 00:00:00 host.example.com mariadbd[PID]: 2000-01-01 0:00:00 [Warning] Access denied for user 'admin'@'::1' (using password: YES) -
WordPress cloning or copying attempts may fail with the following error:
Unable to import database. Error message: ERROR 1045 (28000): Access denied for user 'username'@'127.0.0.1' (using password: YES)
Cause
Plesk may use host specifications like -h 127.0.0.1 or -h ::1 to connect to MySQL (or MariaDB) server.
Normally, these host specifications are covered by the 'admin'@'localhost' user definition.
With the skip-name-resolve variable enabled, 'admin'@'localhost' no longer covers specifications like -h 127.0.0.1 or -h ::1 and Plesk connection to MySQL (or MariaDB) server fails.
Resolution
In order to resolve the issue, use one of the two solutions below:
Disable usage of the skip-name-resolve variable for the database server:
-
-
Remove the skip-name-resolve variable to
/etc/my.cnf(or/etc/mysql/my.cnf) config file. -
Check database connection by using the following commands:
# MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h ::1
# MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h 127.0.0.1
# MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin -h localhost
Define additional MySQL
'admin' user definitions to specifically cover for the -h 127.0.0.1 and -h ::1 host specification cases:
-
-
Connect to the server via SSH
-
Login to the MySQL shell by executing the following command:
# MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysql -uadmin
-
Run the following commands:
GRANT ALL PRIVILEGES ON *.* TO 'admin'@'::1' IDENTIFIED BY 'password' WITH GRANT OPTION;
GRANT ALL PRIVILEGES ON *.* TO 'admin'@'127.0.0.1' IDENTIFIED BY 'password' WITH GRANT OPTION;
-
Log out of mysql shell and run the following command in Linux shell:
# plesk bin admin --set-admin-password -passwd 'password'
This command sets the same password for all three 'admin' accounts.
-
Check that new 'admin' user definitions works by running the following commands:
MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysqlcheck -c -u admin -h ::1 --all-databases
MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysqlcheck -c -u admin -h 127.0.0.1 --all-databases
MYSQL_PWD=$(cat /etc/psa/.psa.shadow) mysqlcheck -c -u admin -h localhost --all-databases
-
with