• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

psadump / backup utils not working - plesk 7.5.4 - debian 3.1

M

mlambjr

Guest
ran the following first:

/opt/psa/bin/psadump -F -z -f /home/backup/domain.com.dump --domains-names /home/backup/domains.list --nostop

===============================================================================

Load list for dumping ... done

===============================================================================

Attempt to connect to MySQL server ... Unable to find file mysql.sock, possible reason: mysql service is not started.

failed

Now the MySQL PSA service will be stopped.
sh: line 1: /etc/init.d/mysqld: No such file or directory

Now the MySQL PSA service will be started.
sh: line 1: /etc/init.d/mysqld: No such file or directory

===============================================================================

Attempt to reconnect to MySQL server ... Unable to find file mysql.sock, possible reason: mysql service is not started.

Unable to connect to PSA database.


so then i tried to copy /etc/init.d/mysql -> /etc/init.d/mysqld and ran it again:

/opt/psa/bin/psadump -F -z -f /home/backup/domain.com.dump --domains-names /home/backup/domains.list --nostop

===============================================================================

Load list for dumping ... done

===============================================================================

Attempt to connect to MySQL server ... Unable to find file mysql.sock, possible reason: mysql service is not started.

failed

Now the MySQL PSA service will be stopped.
Stopping MySQL database server: mysqld.

Now the MySQL PSA service will be started.
Starting MySQL database server: mysqld.
Checking for crashed MySQL tables in the background.

===============================================================================

Attempt to reconnect to MySQL server ... Unable to find file mysql.sock, possible reason: mysql service is not started.

Unable to connect to PSA database.

so i look for mysql.sock, there is none on this debian box, only /var/run/mysqld/mysqld.sock.

attempting to create a link to that file then results in the following:

/opt/psa/bin/psadump -F -z -f /home/backup/domain.com.dump --domains-names /home/backup/domains.list --nostop

===============================================================================

Load list for dumping ... done

===============================================================================

Attempt to connect to MySQL server ... done

===============================================================================


===============================================================================

Checking packages installation ... Error: unsupported OS is detected.


Any ideas??
 
Check your /etc/my.cnf file and see where the socket is located. You could change the location to see if that helps - on RHEL3 the location is /var/lib/mysql/mysql.sock and the line in /etc/my.cnf reads:

socket=/var/lib/mysql/mysql.sock

Have to say we don't use Debian so I can be of limited use to you. On Red Hat the MySQl should be accessible at:

/etc/rc.d/init.d/mysqld

It should be "mysqld" and not "mysql" which is probably what you were trying to accomplish by moving the file.

Try checking where the socket file is located and changing it if necessary, then restarting MySQL:

/etc/rc.d/init.d/mysqld restart

And see how the dump progresses.

- Chris
 
Back
Top