Unable to Request a DB Dump – “Already One in Progress” Error During Backup
Original Question or Issue:
I encountered the following error during backup without making any changes
Environment:
- Product - FileCloud Server
- Version - 23.253
- Platform - Linux
Steps to Reproduce:
Error or Log Message:
Backup Filecloud Server Logs showing:
2026-03-09 1:36:37.569447 ERROR: [1288032][17730381973631] Unable to request a db dump. Already one in progress. rc=1 []
Defect or Enhancement Number:
Cause:
This error typically occurs when a previous backup job failed or was canceled, leaving behind a database dump lock file.
Because the lock remains in place, FileCloud assumes another database dump is still running and prevents new backup jobs from starting.
Resolution or Workaround:
-
Check if any backup job is currently running.
-
On the FileCloud server that is being backed up, locate the following directory:
/var/www/html/scratch/dbdump*
-
If no backup job is currently running, the directory can be safely removed.
Example:
rm -rf /var/www/html/scratch/dbdump*
-
After removing the lock directory, stop any pending or stuck backup jobs.
-
Start a new backup job from the backup server.
Notes:
-
Always confirm that no backup job is actively running before deleting the
dbdump*directory. -
This issue is typically caused by interrupted or failed backup operations that leave the lock in place.