• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

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