Symptoms
After cPanel daily backups run, the below error is received:
Note: The backup logs can be found at path "/usr/local/cpanel/logs/cpbackup/".
Note: The backup transporter logs can be found at path "/usr/local/cpanel/logs/cpbackup_transporter/".
[2021-01-24 03:21:57 +0100] info [backup] Queuing transport of file:
/backup/2021-01-24/backup_incomplete
[2021-01-24 03:21:57 +0100] info [backup] no_transport = 0 .. and
queueid = TQ:TaskQueue:52444
[2021-01-24 03:21:57 +0100] info [backup] leaving queue_backup_transport_item
[2021-01-24 03:21:57 +0100] warn [backup] Pruning of backup files skipped due to
errors. at /usr/local/cpanel/bin/backup line 395.
bin::backup::run("bin::backup") called at /usr/local/cpanel/bin/backup line 120
[2021-01-24 03:21:57 +0100] info [backup] Scheduling backup metadata vacuum
[2021-01-24 03:21:57 +0100] info [backup] Queuing transport reporter
[2021-01-24 03:21:57 +0100] info [backup] no_transport = 0 .. and
queueid = TQ:TaskQueue:52445
[2021-01-24 03:21:57 +0100] info [backup] leaving queue_backup_transport_item
[2021-01-24 03:21:57 +0100] info [backup] Completed at Sun Jan 24 03:21:57 2021
[2021-01-24 03:21:57 +0100] info [backup] Final state is Backup::PartialFailure (0)
[2021-01-24 03:21:57 +0100] info [backup] Sent Backup::PartialFailure notification.
Description
cPanel daily backups will check the log files to determine if any errors have occurred. A backup will perform many different tasks to ensure all the contents of each account is stored in the backup file. When a function fails, it will return one of the error strings listed below.
For example, any of the below search strings can cause a backup to return a failure status, which triggers a partial failure or the creation of file "backup_incomplete".
Unable to get user id
Unable to load cPanel user data
You cannot copy the root user
pkgacct failed to copy daily backup
Could not use daily backup
Bailing out
The REMOTE_PASSWORD variable is missing
Unable to find domain name
Exiting with error code
Could not remove directory
Hook denied execution of pkgacct
Could not open
Could not chmod
Could not rename
failed to create the working dir
Unable to fork
Unable to waitpid
Unable to open
Failure dumping
Unable to read
does not appear to be valid XML
Could not create directory
mysqldump: Got error
mysqldump: Error
mysqldump: Couldn't
mysqldump failed
“Mysql” failed with an error
Failed to generate backup metadata
rsync: connection unexpectedly closed
rsync:.*write error: Broken pipe
Workaround
Most commonly, we see that the MySQL database or a table is crashed. Repairing the crashed database will resolve the issue. For example:
Note: Replace database_name with the crashed database if the failure reason is a "mysqldump" type error message.
mysqlcheck -r database_name
It is important to ensure you've reviewed the backup failure notification to determine which issue caused the backup to fail. Please also ensure the alert types are set to send notification emails to an active account where this information can be easily retrieved to determine the best solution.
WHM Contact Manager - Notifications
The notifications for these tasks fall under the below categories:
- Backup Finished With Partial Failure
- Backup Transport Error
Comments
0 comments
Article is closed for comments.