Isilon: Scheduled job does not start as scheduled because it is already active

Summary: A OneFS's job engine job cannot start because the job is already running. Preventing another instance from starting in clusters running OneFS v8.x or higher. Isilon: Scheduled job does not start as scheduled because it is already active (job id -> Running): scheduled job instance skipped ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

The below event is seen for clusters running OneFS 8.x. and higher:

A scheduled job <Job-Name> will not start as scheduled because it is already active (job id <Job-ID> -> Running): scheduled job instance skipped

Cause

This is by design where in CELOG generates an event when there is a similar job running.

Resolution

Procedure

1. Open an SSH connection to any node in the cluster using the root account.

2. Run:

Cluster-1# isi job status -v



3. Look for the job for which the event had occurred, if it is already running, another instance would not start,
    Also check the date and confirm the event is not an old event as the job could have been completed.

4.Safely clear the alert by running:

 Cluster-1# isi event bulk --ignore=true
 Cluster-1# isi event bulk --resolved=true



Wait 1-2 minutes to verify that the event does not recur:

Cluster-1# isi event events list



If the event is shown again, contact Dell Technical Support.
 

Additional Information

See this video:

Affected Products

Isilon

Products

Isilon
Article Properties
Article Number: 000050861
Article Type: Solution
Last Modified: 29 Mar 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.