• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Database backup doesn't work - Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2 - MariaDB 10.6

octet

Basic Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
Plesk Obsidian v18.0.50_build1800230213.12
Plesk BackUp of databases fail:

</description>
</message>
<object type="Database" name="XXXXdb">
<message severity="warning">
<description>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: 1130: "Host '::1' is not allowed to connect to this MariaDB server" when trying to connect
</description>

my.cnf

[mysqld]
bind-address = ::
#skip_name_resolve=1

[root@hive ~]# mysql -V
mysql Ver 15.1 Distrib 10.6.12-MariaDB, for Linux (x86_64) using readline 5.1

Anything else I need to do?
 
Are there additional directives in the [mysqldump] section? Has MariaDB been restarted since my.cnf was modified?
 
I've also seen your other post on a very strange webmail behavior. Maybe SELinux is interfering, e.g. limiting access to the MariaDB socket?
 
No mysqldump section. Yes, I've just restarted it again earlier this morning. Backup is set to daily so we will see if we get the same error tomorrow. Is there a way to check now?
 
Same issue also - turn off skip_name_resolve

Fix it by doing this:

edit /etc/mysql/my.cnf, e.g.:
# nano /etc/mysql/my.cnf


add the line and save the file:
skip_name_resolve = off

restart sql service with the command:
systemctl restart mariadb


**

the issue is caused by name resolution in mariadb as [email protected] and admin@localhost are two different users
 
Back
Top