The backup was not able to be completed...
Hello everyone.
I'm having trouble creating backups on my server (CentOS 6). Every day at 6 am I getting a message saying "The backup was not able to be completed because it timed out waiting for / scripts / cpbackup to finish."
I checked via SSH that there is a backup running indefinitely since February with the command "ps faux | grep cpbackup". I killed the backup process and forced a new backup with the command "/ scripts / cpbackup --force" but the new backup is generating indefinitely and I keep getting the message "The backup was not able to be completed ..."
I do not know what to do. Attached is information from February processes along with your log, and also the processes that are currently locked.
aquariunweb.com.br/server/Erro%20de%20Backup.png
aquariunweb.com.br/server/Erro%20de%20Backup%202.png
-
Hello, Is there any reason you prefer to use the legacy backup system instead of the new backup system? You can force a generation of backups with the new backup system via: /usr/local/cpanel/bin/backup --force
Thank you.0 -
I did not know there was another way to create a backup. I can set this up to run automatically on the "Main >> Backup >> Backup Configuration" am I correct? Right now I'm running it, and if you give a problem I return here. Thank you! 0 -
Same defect that the legacy :( aquariunweb.com.br/server/Erro%20de%20Backup%203.png 0 -
Hello, You can either reduce the server load, or increase the load threshold via the following option under "Stats and Logs" in "WHM Main >> Server Configuration >> Tweak Settings": "Extra CPUs for server load" Per it's description, this is the load average above the number of CPUs at which cpuwatch, cpanellogd, backups, and CPU stats consider the system to be in a critical load state. For example, a server with 4 physical CPUs and a value of 2 in this field will be considered "critical" in these cases once the load reaches 6. Thank you. 0 -
Not quite know why he returned to work, but I have disabled the Mod Security 2 and made a change in my.cnf who was with the max_allowed_packet equal to 2048M and moved to 500M . Now it is operating normally. Thank you 0 -
It's possible that modification reduced your server load, which allowed backups to proceed. Thank you. 0
Please sign in to leave a comment.
Comments
6 comments