Technical Support Pages


I get the message Lock File Existed! Backup Aborted!
schedule simple_job lockfile schedule.lck error 1 Failed
Product Release(s)
03.02.0x 03.00.0x 03.01.0x 01.02.0x 02.00.0x 02.01.0x 02.02.0x
Operating System(s)
All Supported
Problem Description
My nightly job failed with the message - Lock File Existed! Backup Aborted! What does it mean and what should I do?
A unique lockfile (schedule.lck) is created for each Scheduled Job. If it still exists when the next instance of a Scheduled Job runs, it means that the prior Scheduled job has not yet completed.

This may be because it is waiting for user intervention. Typically, a new volume prompt is being issued. Other possibilities the job has locked up due to a bus issue, or some other catastrophic failure. Most likely however, the job is waiting for User Intervention/Input.

The FIRST solution is to run EDGEMENU -> Schedule -> Acknowledge All and check for jobs waiting for operator input. Instructions are clear on what the User must do.

If no solution is offered here, the SECOND choice is to run EDGEMENU -> Schedule -> Browse Running Jobs. This will give you a chance to see the status of a job and to terminate the job if anything seems amiss.

The THIRD choice is for the operator to run a process status (ps) from the command line, then kill any running BackupEDGE process (except edge.websrv if running). This should remove the lockfile (unless kill -9 is used).

When all this has been done, check for the existence of, and remove the .schedule.lck. file in the listing directory of the job. The default schedule is called .simple_job., so the correct directory is ./usr/lib/edge/lists/simple_job. If .schedule.lck. still exists in the listing directory of your job , remove it.

Lockfiles are automatically removed during a system reboot /restart.

In addition, a system reboot may also be in order to clear any hung processes from the previous job.

Get a printer-friendly version of this document



Last Updated - 2018/05/16