HTCondor - Revision history

Cacosta: /* The htcondor command */

2026-03-27T13:26:05Z

The htcondor command

Cacosta: /* Eventlog */

2026-03-27T13:19:35Z

Eventlog

Cacosta: /* Eventlog */

2026-03-27T13:09:12Z

Eventlog

Cacosta: /* Eventlog */

2026-03-27T13:08:59Z

Eventlog

Cacosta: /* The htcondor command */

2026-03-27T13:08:17Z

The htcondor command

Cacosta: /* Removing your jobs */

2026-03-27T13:03:34Z

Removing your jobs

Cacosta: /* htcondor command */

2026-03-27T10:04:31Z

htcondor command

Cacosta: /* htcondor command */

2026-03-27T08:54:28Z

htcondor command

Cacosta: /* Removing your jobs */

2026-03-27T08:44:16Z

Removing your jobs

Cacosta: /* CPU usage exceeded request_cpus */

2026-03-23T06:23:46Z

CPU usage exceeded request_cpus

← Older revision		Revision as of 13:26, 27 March 2026
Line 1,443:		Line 1,443:

	The goal of the htcondor command is to consolidate the functionality of multiple legacy commands into a single, intuitive interface. HTCondor developers have insisted that the old commands (like condor_submit, condor_q, etc.) are never going to disappear. However, you might find the way this new command interacts with the system and presents information to be quite useful and user-friendly.		The goal of the htcondor command is to consolidate the functionality of multiple legacy commands into a single, intuitive interface. HTCondor developers have insisted that the old commands (like condor_submit, condor_q, etc.) are never going to disappear. However, you might find the way this new command interacts with the system and presents information to be quite useful and user-friendly.
		+
		+	Although the command contains different subcommands, as a standard user, the three main subcommands are <b>job</b>, <b>eventlog</b>, and <b>dag</b>.

	== Managing jobs ==		== Managing jobs ==

@@ Line 1,546: / Line 1,546: @@
 Job         Host                     Start Time      Evict Time      Evictions   Wall Time     Good Time     CPU Usage
 1522209.0   slot1_43@tds515.pic.es   3/27/26 13:56   3/27/26 13:57   0           0+00:01:00    0+00:01:00    0+00:01:58
 </pre>

@@ Line 1,526: / Line 1,526: @@
 The htcondor command is useful for reading and understanding the raw log files.
-You can use the <i>follow</i> subcommand (similar to <i>tail -f<i>) to see how your job evolves, presented in tabulated format:
+You can use the <i>follow</i> subcommand (similar to <i>tail -f</i>) to see how your job evolves, presented in tabulated format:
 <pre>

@@ Line 1,526: / Line 1,526: @@
 The htcondor command is useful for reading and understanding the raw log files.
-You can use the `follow` subcommand (similar to `tail -f`) to see how your job evolves in real-time, presented in a clean, tabulated format:
+You can use the <i>follow</i> subcommand (similar to <i>tail -f<i>) to see how your job evolves, presented in tabulated format:
 <pre>

@@ Line 1,446: / Line 1,446: @@
 == Managing jobs ==
-You can submit a job easily:
+You can easily submit a job:
 <pre>
@@ Line 1,453: / Line 1,453: @@
 </pre>
-And query its status to get a detailed, human-readable summary:
+And query its status to get detailed information. For example, after submission, it might show as idle:
 <pre>
@@ Line 1,462: / Line 1,462: @@
 It requested 15.000 GB of disk space.
 Job has 0.0% goodput for 0.0 second of wall clock time.
 </pre>

← Older revision		Revision as of 13:03, 27 March 2026
Line 1,416:		Line 1,416:
	Or you can remove all your jobs just using the "-all" option.		Or you can remove all your jobs just using the "-all" option.

		+	= The htcondor command =
		+
		+	In newer HTCondor versions, a new unified command, htcondor, has been introduced to help you manage your jobs.
		+
		+	<pre>
		+	$ htcondor -h
		+	usage: htcondor [-h] [-v] [-V] [-q] {dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex} ...
		+
		+	A tool for managing HTCondor jobs and resources.
		+
		+	optional arguments:
		+	-h, --help show this help message and exit
		+	-v, --verbose Increase verbosity of output (can be specified multiple times)
		+	-V, --version Print the HTCondor version and exit
		+	-q, --quiet Decrease verbosity of output (can be specified multiple times)
		+
		+	subcommands:
		+
		+	{dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex}
		+	Types of HTCondor objects that can be managed
		+	</pre>
		+
		+	A complete man page is available via the command line or at the following URL:
		+
		+	https://htcondor.readthedocs.io/en/latest/man-pages/htcondor.html#index-1
		+
		+	The goal of the htcondor command is to consolidate the functionality of multiple legacy commands into a single, intuitive interface. HTCondor developers have insisted that the old commands (like condor_submit, condor_q, etc.) are never going to disappear. However, you might find the way this new command interacts with the system and presents information to be quite useful and user-friendly.
		+
		+	== Managing jobs ==
		+
		+	You can submit a job easily:
		+
		+	<pre>
		+	$ htcondor job submit test.sub
		+	Job 1522136 was submitted.
		+	</pre>
		+
		+	And query its status to get a detailed, human-readable summary:
		+
		+	<pre>
		+	$ htcondor job status 1522136
		+	Job 1522136 is currently idle.
		+	It was submitted 11.100039 seconds ago.
		+	It requested 1.000 GB of memory.
		+	It requested 15.000 GB of disk space.
		+	Job has 0.0% goodput for 0.0 second of wall clock time.
		+	</pre>

	= From Torque to HTCondor =		= From Torque to HTCondor =

← Older revision		Revision as of 10:04, 27 March 2026
Line 1,416:		Line 1,416:
	Or you can remove all your jobs just using the "-all" option.		Or you can remove all your jobs just using the "-all" option.

−
−	~~= htcondor command =~~
−
−	~~With the new HTCondor versions, there is a new command, htcondor, that allows to manage your jobs.~~
−
−	~~<pre>~~
−	~~# htcondor -h~~
−	~~usage: htcondor [-h] [-v] [-V] [-q] {dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex} ...~~
−
−	~~A tool for managing HTCondor jobs and resources.~~
−
−	~~optional arguments:~~
−	~~-h, --help show this help message and exit~~
−	~~-v, --verbose Increase verbosity of output (can be specified multiple times)~~
−	~~-V, --version Print the HTCondor version and exit~~
−	~~-q, --quiet Decrease verbosity of output (can be specified multiple times)~~
−
−	~~subcommands:~~
−
−	~~{dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex}~~
−	~~Types of HTCondor objects that can be managed~~
−	~~</pre>~~
−
−
−	~~There is a complete man page thay you can access by console or in the next url:~~
−
−	~~https://htcondor.readthedocs.io/en/latest/man-pages/htcondor.html#index-1~~
−
−	~~So, for instance, you can submit your job with this command:~~

	= From Torque to HTCondor =		= From Torque to HTCondor =

← Older revision		Revision as of 08:54, 27 March 2026
Line 1,418:		Line 1,418:

	= htcondor command =		= htcondor command =
		+
		+	With the new HTCondor versions, there is a new command, htcondor, that allows to manage your jobs.
		+
		+	<pre>
		+	# htcondor -h
		+	usage: htcondor [-h] [-v] [-V] [-q] {dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex} ...
		+
		+	A tool for managing HTCondor jobs and resources.
		+
		+	optional arguments:
		+	-h, --help show this help message and exit
		+	-v, --verbose Increase verbosity of output (can be specified multiple times)
		+	-V, --version Print the HTCondor version and exit
		+	-q, --quiet Decrease verbosity of output (can be specified multiple times)
		+
		+	subcommands:
		+
		+	{dag,job,jobset,eventlog,credential,server,ap,cm,ocu,annex}
		+	Types of HTCondor objects that can be managed
		+	</pre>
		+
		+
		+	There is a complete man page thay you can access by console or in the next url:
		+
		+	https://htcondor.readthedocs.io/en/latest/man-pages/htcondor.html#index-1
		+
		+	So, for instance, you can submit your job with this command:

	= From Torque to HTCondor =		= From Torque to HTCondor =

← Older revision		Revision as of 08:44, 27 March 2026
Line 1,415:		Line 1,415:

	Or you can remove all your jobs just using the "-all" option.		Or you can remove all your jobs just using the "-all" option.
		+
		+
		+	= htcondor command =

	= From Torque to HTCondor =		= From Torque to HTCondor =

@@ Line 1,480: / Line 1,480: @@
 Thus, in that case, your job is consuming more memory than requested. You should resubmit your job increasing the memory requested.
-=== CPU usage exceeded request_cpus ===
+=== CPU usage (X) exceeded request_cpus (Y) ===
-The HoldReason, in this case, means that your job is taking more cpus than requesting for the last hour. You should resubmit your job increasing the number of requested cpus.
+The HoldReason in this case means that your job has been using more CPUs than requested. You should resubmit your job and increase the number of requested CPUs.
 === Your job has been restarted XX times. Please check. Maybe your $HOME or other quota is full? ===