Held Job Troubleshooting - Revision history

Barnes at 23:09, 15 April 2017

2017-04-15T23:09:11Z

Barnes at 22:47, 15 April 2017

2017-04-15T22:47:29Z

Barnes: /* Overview */

2017-04-05T20:35:37Z

Overview

Barnes at 20:34, 5 April 2017

2017-04-05T20:34:57Z

Barnes at 20:26, 5 April 2017

2017-04-05T20:26:30Z

Barnes: Created page with "== Overview == There exist various administrative scripts which run on the cluster automatically. If you find that your job has been held, designated by 'H' as a status, pleas..."

2017-04-05T20:22:58Z

Created page with "== Overview == There exist various administrative scripts which run on the cluster automatically. If you find that your job has been held, designated by 'H' as a status, pleas..."

New page

== Overview ==
There exist various administrative scripts which run on the cluster automatically. If you find that your job has been held, designated by 'H' as a status, please use the following guidelines to understand why.

== Viewing Job ClassAds ==
When Condor holds a job, the ClassAd 'HoldReason' can be modified to explain the cause. To see the ClassAds of a job, use the command

<pre>
condor_q -l <jobid>
</pre>

== Hold Reaons ==
=== Over Maximum Run Count ===
=== Used More Memory Than Requested ===
=== Used More Memory Than Slot Provided ===
=== Used More Disk Than Requested ===

@@ Line 34: / Line 34: @@
 The ClassAd <i>HoldReason</i> states
 <pre>
-<user> job <jobid> put on hold because its MemoryUsage # > 1200 and # > <SlotMemory> * 1.2 + 500
+<user> job <jobid> put on hold because its MemoryUsage # > <SlotMemory> * 1.2 + 500 (by user condor)
 </pre>

@@ Line 34: / Line 34: @@
 The ClassAd <i>HoldReason</i> states
 <pre>
-<user> job <jobid> removed because its MemoryUsage # > 1200 and # > <SlotMemory> * 1.2 + 500
+<user> job <jobid> put on hold because its MemoryUsage # > 1200 and # > <SlotMemory> * 1.2 + 500
 </pre>

@@ Line 10: / Line 10: @@
 == Hold Reaons ==
 === Over Maximum Run Count ===
 The ClassAd <i>HoldReason</i> states
@@ Line 16: / Line 17: @@
 </pre>
-This means that your job has started 99 times already and is attempting to start again. Typically, this indicates a problem with the job and should be removed. The code should be examined to find why it continually fails.
+This means that your job has started # times which is more than the maximum allowed restarts. Typically, this indicates a problem with the job and should be removed. The code should be examined to find why it continually fails.
 === Used More Memory Than Requested ===
-=== Used More Memory Than Slot Provided ===
+The ClassAd <i>HoldReason</i> states
 === Used More Disk Than Requested ===

@@ Line 1: / Line 1: @@
 == Overview ==
-There exist various administrative scripts which run on the cluster automatically. If you find that your job has been held, designated by 'H' as a status, please use the following guidelines to understand why.
+There exist various administrative scripts which run on the cluster automatically. One such script will examine running jobs and hold them if they are meet certain conditions. If you find that your job has been held, designated by 'H' as a status, please use the following guidelines to understand why.
 == Viewing Job ClassAds ==