• 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 not working since upgrade

R

rookie00

Guest
i upgrade to mysql from 3.23 to 4.1.20 lastnight and all was working before i upgrade. but now i am getting a mysql error.
i am using fedora 2, plesk 7.5.4. i also tried to restart mysql but when i try it says it failed to restart. anyway i can fix this.

Mysql Error : Connection Error
Error Number: 2002 Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111)

any suggestion please. thanks
 
Did you verify that no mysql processes were running? Is the /var/lib/mysql directory owned by the mysql user and mysql group? All of the files should also be owned by mysql.

chown -R mysql:mysql /var/lib/mysql


You can also verify the settings that mysqld would use for startup by running "mysqld --verbose --help".

You may need to set the "old-passwords" option in the my.cnf file -- unless you have dealt with that problem as well. I have 5 different versions of mysql installed, but they are all in different paths with independent UNIX sockets and mysql data directories.
 
Originally posted by wagnerch
Did you verify that no mysql processes were running? Is the /var/lib/mysql directory owned by the mysql user and mysql group? All of the files should also be owned by mysql.

chown -R mysql:mysql /var/lib/mysql


You can also verify the settings that mysqld would use for startup by running "mysqld --verbose --help".

You may need to set the "old-passwords" option in the my.cnf file -- unless you have dealt with that problem as well. I have 5 different versions of mysql installed, but they are all in different paths with independent UNIX sockets and mysql data directories.
i tried all ur suggestion except the one that check the settings seems like that's a bad command and it still doesn't work.
i did a "service mysql start" and says mysql:unrecognize service. also i check mysql.sock and it says "unknown file size".
is there a way i can go back to 3.23 and start over again.
 
Back
Top