• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

MySQL upgrade caused PSA to crash

W

w3it

Guest
Hi
I have just upgraded using yum mysql version 3.23.58-9.1 to version 12.22 Distrib 4.0.24, for redhat-linux-gnu (i686)

When I refreshed PSA I got the following error:

Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) 0: /usr/local/psa/admin/auto_prepend/auth.php3:66 psaerror(string "Unable to connect to database: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)")

Help greatly appreciated on this one!
Ian
 
make sure you are pointing at the right mysql.sock file. You can specify where the sock file is, in a file named "/etc/my.cnf"

Do a search on the system and find the previous mysql.sock.

Then specify the location in your my.cnf file. (example versions are included in the plesk/mysql folder; they are named "my-small.cnf, my-medium.cnf, and my-large.cnf"... just copy one of them to /etc/my.cnf and set the sock directive to point to the proper place.

Hope that helps,

-J
 
Hi
this is the current my.cnf. Has the Plesk one been overwritten by yum upgrading? How do I find where yum has placed the upgrades? Could it be the user and password fields?

[mysqld]
innodb_data_file_path=ibdata1:10M:autoextend
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
skip-networking

[mysql.server]
user=mysql
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
 
Have you tried to restart mysqld?

For me, MySQL always stops working (but is running) after upgrade to a newer version.
A simple restart of mysqld does the trick (at least for me).
 
Hi and thanks

Thats what it was! Once I restarted, it worked fine. Bit poor that no prompt was given that I should restart mysql. Still at least I know for next time.
 
And for anyone reading this thread looking for help in the future, I find that ALWAYS after an mysql upgrade I have to reboot the server. restarting mysql just doesn't work for me.

Faris.
 
Back
Top