• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

After scheduled backup began, server blocked...

albans

Regular Pleskian
Hi,

My config: Fedora Core 2/Plesk 7.5r

I defined scheduled FTP backups for each of the domain I host (about 15).
Each backup had to start at 1am (same time for every domain)...
I tried the FTP settings => worked well via a manual FTP backup (still in Plesk).

Then, the scheduled backup started => I received 10 mails telling me that the backup for "x" domain has begun.
And then the server was not responding anymore (SSH included).

Since then, each time I reboot it, it starts working for ~2 minutes and then blocked again...

I think that the scheduled backups start again and again and make the server crash.

How can I deactivate them? As I cannot access the webinterface or any network services.

Thanks for you help!
 
I'm getting the exact same problem.

After 3 or 4 reboots I eventually got emails saying:

Backup process has failed for domain domain.com

error: cURL execution failed: This doesn't seem like a nice ftp-server response

Any information on how to fix / stop this bug and why the backup brings the server down in the first place would be great.

Regards.

Jay.
 
Try stopping the cron job linked to the daemon "updatemng".
Also try to update your version of Plesk.

This helps me getting my server working again and I don't use the auto-ftp backup anymore.
 
Back
Top