• 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.

problem: server stopping once a day

D

dz69

Guest
hi,

my plesk 7.5 server has a strange behaviour for some weeks, and i can't figure out what i changed to provoke that.

the plesk server is running in virtuozzo, but is not accessible. when i login to plesk i get directly to virtuozzo and when i click on the clients or domains i get a blank page.

it isnt possible to fetch emails or connect to the mysql database for php scripts. but webservice are running.

outlook reports the following error:
db_connect: failed to connect to database: Error: Can\'t connect to local MySQL server through socket \'/var/lib/mysql/mysql.sock\' (111)\"

when i restart the VPS in virtuozzo everything runs fine again. and then, next day, booooooom, again that error.

does anyone have a clue for that? maybe so failure in the mysql server? what can i do to solve that problem?
 
What version of MySQL are you running?

You might need to edit my.cfg to "old password" usage...
 
In /etc/my.cnf

insert under:
[mysql.server]
old-passwords

and then restart mysql and try again :)

Hope this helps, I a bit sleepy!
 
nope...that doesn't solved the problem...the server stopped again with the same error messages...

any more clues? :(
 
Back
Top