• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

mysql.sock

R

redpaint

Guest
Hi All,

We're running freebsd 6.2 and recently upgraded to plesk v8.1.1 from v8.1.0.

Problem is that when we reboot the server we get a fatal exception:
ERROR: PleskFatalException
Unable to connect to database: Can't connect to local MySQL server
through socket '/tmp/mysql.sock' (2)

0: /usr/local/psa/admin/plib/common_func.php3:151
psaerror(string 'Unable to connect to database: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)')
1: /usr/local/psa/admin/auto_prepend/auth.php3:90
It looks like mysql.sock is being deleted when we reboot?? To get it to work again we have to kill running mysql processes and then restart mysql-server:
/usr/local/etc/rc.d/mysql-server start

This has only started happening since we upgraded. I'm a complete newbie to plesk and to freebsd. Does anyone have any ideas why this could be happening? Could it be a permissions problem on the tmp folder? Or could it be a redundant symlink?

Thanks
 
It has been a while since I touched FBSD, but can you make sure that there isn't an rc.d script that is running that cleans out the /tmp directory on startup? It sounds like there is something that is running after mysql starts up that clears out the /tmp directory.

Good luck.
 
Hi,

Just to update anyone who finds this post in the future I submitted a support request to swsoft and got the following response:

For now you have mysql 5 installed:

plesk# pkg_info | grep mysql|grep server
mysql-server-5.0.37 Multithreaded SQL database (server)

File /usr/local/etc/rc.d/mysql-server.sh is init script from mysql 4 package, so I removed it:

plesk# grep server /usr/local/etc/rc.d/mysql-server.sh /usr/local/etc/rc.d/mysql-server /usr/local/etc/rc.d/mysql-server.sh:# $FreeBSD: ports/databases/mysql41-server/files/mysql-server.sh.in,v 1.4 2006/03/07 16:25:00 ale Exp $ /usr/local/etc/rc.d/mysql-server:# $FreeBSD: ports/databases/mysql50-server/files/mysql-server.sh.in,v 1.3 2006/03/07 16:25:00 ale Exp $

plesk# mv /usr/local/etc/rc.d/mysql-server.sh /root/

Please check now if problem exists.
Server reboots perfectly now, and we now have MySQL 5 installed as well an unexpected bonus!
 
Back
Top