Return
-
Title
When running a system backup receive the error, "Internal locking error, lock was not unlocked; lock='backuparchive_', backtrace='" -
Description
When running a system backup the error message "Internal locking error, lock was not unlocked; lock='backuparchive_', backtrace='" is received and the backup does not proceed.
-
Cause
Disk was full when a backup task started which caused it to stall. When space was freed or more space added, another backup task was triggered but it could not complete because the previous failed backup was still locked. -
Resolution
1. Re-enter the credentials on the backup policy, confirming that the Anonymous login checkbox is not checked, then commit.
2. From the core shell enter these two commands:rm /opt/scb/var/lock/backupa*
pkill archive.phpThese commands will remove all lock files having to do with backup archiving and end the process archive.php.
3. Try to run the system backup manually again.
If the above steps do not work it is recommended to restart the SPS appliance or VM so that the locks are removed and shares are remounted.
-
Additional Information
The error message will present in the messages log for the day the backup was triggered.