Technical Support Pages

 

Title
I get the message Lock File Existed! Backup Aborted!
Keywords
schedule simple_job lockfile schedule.lck error 1 Failed
Product Release(s)
03.04.0x 03.03.0x 03.02.0x 03.01.0x 03.00.0x 02.02.0x 02.01.0x 02.00.0x 01.02.0x
Operating System(s)
All Supported
Problem Description
My nightly job failed with the message - Lock File Existed! Backup Aborted! What does this mean and what should I do?
Cause
A unique lockfile (schedule.lck) is created when each Scheduled Job begins. It is removed when the Scheduled Job completes.
If the lockfile still exists when the next instance of the Scheduled Job runs, it means that the prior Scheduled job has not yet completed. This is the problem that must be resolved.
There are three reasons this occurs:

- 1 - The Job is waiting for User Intervention because the Resource has reached its Quota, is physically full, or in the case of a tape, optical media, or SharpDrive has reach End-Of-Media (most likely reason).
- 2 - The job is hung because of a hardware issue.
- 3 - The last job is actually still running and hasn't yet completed.

Solution

ONE - Identify the Problem
As root, launch EDGEMENU. If Scheduled Job requires attention, you will be prompted to view the action box for that job. If you choose to do this later, you can go to Schedule -> Browse Running Jobs.
A pop up menu will show a message (such as "Please Insert Volume 2". You may choose to:
- - a perform the requested action and select Continue.
- - b End the job.
- - c Do nothing and defer the action.

TWO - Resolve the Issue and Continue the Job
You may need to replace the optical media, tape, SharpDrive, etc. or take some corrective action.
When the issue is resolved, go back to step ONE above, browse to the Job, and select Continue.

or

THREE - Cancel The Job
If no solution is easily available, run EDGEMENU -> Schedule -> Browse Running Jobs. This will give you a chance to see the status of a job and to cancel (terminate) the job if anything seems amiss.

FOUR - Manually Killing Processes
(This should only be performed as a last resort)
The operator can run a process status (ps -ef | grep edge) as root from the command line, then kill any running BackupEDGE (edge) processes (except edge.websrv if running) by process number. This should remove the lockfile (unless kill -9 is used).

When all this has been done, check for the existence of, and if necessary 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 of your job directory, remove it.

If a process is hung (can't be killed by option FOUR), a system reboot may also be required. Lockfiles are automatically removed during a system reboot / restart.

Notes
Please see the BackupEDGE User Guide sections related to Quota and Retention for your particular Resource type.
Get a printer-friendly version of this document

 

 

Last Updated - 2020/07/01

 

Top
MENU