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

Issue Error in scheduled copies of plesk

Inma

Regular Pleskian
Hi, I think this is due to a mysql crash... or restart or something while trying to copy and that's why it doesn't copy... am I wrong? Any suggestions or log where to look? thanks

1690381444913.png
 
Yes, this is a very typical picture of a database server outage during a running backup. It does not necessarily need to be a crash. Just a restart of the database server could also trigger this situation. Does it happen each time when you try to do a backup? Or is that a one-time event?
 
it happens to me twice a day-night

And it doesn't match the copies

is that the copy is made and MySQL is already down or crashing

I can't find the culprit for the reboots

I have already done a Plesk repair and the same thing happens
 
In your syslog (/var/log/messages or /var/log/syslog or similar) you'll find mariadb log entries on the crash. These will normally show the reason why there is a problem.
 
Back
Top