Server log message "Couldn't look up properties of... because: The specified key does not exist"

• Problem: Server log shows message "Bucket XXXX...: Couldn't look up properties of locks/YYYY.... because: The specified key does not exist."
• Description: Magnus Box has found a reference to a lockfile in the list of lockfiles, but when attempting to read that lockfile, the lockfile no-longer exists.
• Cause: The normal sequence is that a backup job will complete, remove its lockfile, then immediately remove the lockfile from the list of lockfiles. Where there is high-volume usage of the vault, or multiple simultaneous backup jobs, it is possible for a backup job to read the list of lockfiles, and then to try to read all the lockfiles for their details, but find that a lockfile from the list has already been deleted in the split-second between reading the list and attempting to read the lockfiles. The backup job may hang while waiting to find the expected file.
• Immediate Solution:
  • Stop the backup jobs & restart them. This will reset the list of lockfiles.
• Long-term solution:
  • Stagger the schedule of backup jobs
  • Have fewer jobs into the same vault

A future version of Magnus Box will better handle the absence of expected lockfiles, automatically restarting the appropriate backup job.