CONDOR_STATUS(1)

📦
version 25.14.1 · 12 versions
, in fedora 43

💅 CONDOR_STATUS(1) 💅

okay so bestie, welcome to the HTCondor Manual page for condor_status — part 1 of 3, and yes we're doing this, it's giving ✨essential tool✨ energy. no cap, this one's a whole vibe.

🎀 NAME 🎀

condor_status — HTCondor Manual 💖

Display status of the HTCondor pool. periodt.

🦋 SYNOPSIS 🦋

condor_status [-debug ] [help options ] [query options ] [display options ] [custom options ] [name ... ]

🌸 DESCRIPTION 🌸

condor_status is a versatile little icon 💅 that you can use to monitor and query the HTCondor pool. she can query resource information, submitter information, and daemon master information. the specific query she sends and the resulting info display are totally controlled by the query options you hand her. and yes, queries and display formats can be customized. main character energy fr fr.

The options you can give to condor_status belong to five groups:

  • Help options provide information about the condor_status tool.
  • Query options control the content and presentation of status information.
  • Display options control the display of the queried information.
  • Custom options allow the user to customize query and display information.
  • Host options specify specific machines to be queried.

At any time, only one help option, one query option and one display option may be specified. Any number of custom options and host options may be specified. slay.

✨ OPTIONS ✨

  • -debug — causes debugging information to be sent to stderr, based on the value of the configuration variable TOOL_DEBUG. 👀
  • -help — (Help option) display usage information. it's like a little tutorial, bestie.
  • -diagnose — (Help option) print out the ClassAd query without performing the query. it's giving preview mode 🔮.
  • -absent — (Query option) query for and display only absent resources. 🙈
  • -ads filename — (Query option) read the set of ClassAds in the file specified by filename, instead of querying the condor_collector. reading files instead of asking the collector, lowkey iconic.
  • -annex name — (Query option) query for and display only resources in the named annex.
  • -any — (Query option) query all ClassAds and display their type, target type, and name. all of them, no filter, we're nosy 💅.
  • -avail — (Query option) query condor_startd ClassAds and identify resources which are available.
  • -claimed — (Query option) query condor_startd ClassAds and print information about claimed resources.
  • -cod — (Query option) display only machine ClassAds that have COD claims. Information displayed includes the claim ID, the owner of the claim, and the state of the COD claim.
  • -collector — (Query option) query condor_collector ClassAds and display attributes.
  • -defrag — (Query option) query condor_defrag ClassAds.
  • -direct hostname — (Query option) go directly to the given host name to get the ClassAds to display. By default, returns the condor_startd ClassAd. If -schedd is also given, return the condor_schedd ClassAd on that host.
  • -grid — (Query option) query grid resource ClassAds.
  • -java — (Query option) display only Java-capable resources. ☕
  • -license — (Query option) display license attributes.
  • -master — (Query option) query condor_master ClassAds and display daemon master attributes.
  • -negotiator — (Query option) query condor_negotiator ClassAds and display attributes.
  • -pool centralmanagerhostname[:portnumber] — (Query option) query the specified central manager using an optional port number. condor_status queries the machine specified by the configuration variable COLLECTOR_HOST by default.
  • -run — (Query option) display information about machines currently running jobs.
  • -schedd — (Query option) query condor_schedd ClassAds and display attributes.
  • -server — (Query option) query condor_startd ClassAds and display resource attributes.
  • -startd — (Query option) query condor_startd ClassAds.
  • -state — (Query option) query condor_startd ClassAds and display resource state information.
  • -broken — (Query option) query condor_startd ClassAds of broken slots or broken machines and display a reason. Use with -startd to see broken machines. 💀
  • -healthy[:verbose] — (Query option) query condor_startd ClassAds of unhealthy slots or broken machines and display a health factor and the failed health expressions. Use with -slot to see health factor and reason per slot. If :verbose is added, then all machines or slots are printed. Otherwise slots or machines that have full health and are not broken are counted but not printed.
  • -lvm — (Query option) query condor_startd ClassAds of slots current enforced disk usage. Use with -startd to see which condor_startds are enforcing disk usage.
  • -snapshot [details] — (Query option) can only be used if the -direct option has been specified. Requests a full snapshot of the internal state, also including Machine.Extras from cron jobs or resource monitors. 📸
  • -statistics WhichStatistics — (Query option) can only be used if the -direct option has been specified. Identifies which Statistics attributes to include in the ClassAd. WhichStatistics is specified using the same syntax as defined for STATISTICS_TO_PUBLISH.
  • -storage — (Query option) display attributes of machines with network storage resources.
  • -submitters — (Query option) query ClassAds sent by submitters and display important submitter attributes.
  • -subsystem type — (Query option) if type is one of collector, negotiator, master, schedd, or startd, then behavior is the same as the query option without the -subsystem option. For example, -subsystem collector is the same as -collector. A value of type of CkptServer, Machine, DaemonMaster, or Scheduler targets that type of ClassAd.
  • -vm — (Query option) query condor_startd ClassAds, and display only VM-enabled machines. Information displayed includes the machine name, the virtual machine software version, the state of machine, the virtual machine memory, and the type of networking.
  • -offline — (Query option) query condor_startd ClassAds, and display, for each machine with at least one offline universe, which universes are offline for it.
  • -attributes Attr1[,Attr2 ...] — (Display option) explicitly list the attributes in a comma separated list which should be displayed when using the -xml, -json or -long options. Limiting the number of attributes increases the efficiency of the query.
  • -expert — (Display option) display shortened error messages. short king 🫶.
  • -long — (Display option) display entire ClassAds. Implies that totals will not be displayed.
  • -limit num — (Query option) at most num results should be displayed.
  • -sort expr — (Display option) change the display order to be based on ascending values of an evaluated expression given by expr. Evaluated expressions of a string type are in a case insensitive alphabetical order. If multiple -sort arguments appear on the command line, the primary sort will be on the leftmost one within the command line, and it is numbered 0. A secondary sort will be based on the second expression, and it is numbered 1. For informational or debugging purposes, the ClassAd output to be displayed will appear as if the ClassAd had two additional attributes. CondorStatusSortKeyExpr<N> is the expression, where <N> is replaced by the number of the sort. CondorStatusSortKey<N> gives the result of evaluating the sort expression that is numbered <N>.
  • -totals — (Display option) display totals only.
  • -xml — (Display option) display entire ClassAds, in XML format. The XML format is fully defined in the reference manual, obtained from the ClassAds web page, with a link at http://htcondor.org/classad/classad.html.
  • -json — (Display option) display entire ClassAds in JSON format.
  • -constraint const — (Custom option) add constraint expression.
  • -compact — (Custom option) show compact form, with a single line per machine using information from the partitionable slot. Some information will be incorrect if the machine has static slots. ⚠️
  • -autoformat[:jlhVrTY,tng] attr1 [attr2 ...] or -af[:jlhVrTY,tng] attr1 [attr2 ...] — (Output option) display attribute(s) or expression(s) formatted in a default way according to attribute types. This option takes an arbitrary number of attribute names as arguments, and prints out their values, with a space between each value and a newline character after the last value. It is like the -format option without format strings. This output option does not work in conjunction with the -run option. 💖

Okay so quick vibe check before we keep going: there's a whole assumption baked in here — nobody expects an attribute name to start with a dash character. That's the whole trick: the next word that does begin with a dash is the start of the next option. That's it, that's the rule. 🎀

And the -autoformat option can be followed by a colon and some formatting qualifiers, which let you deviate from the default output formatting. Slay. Here's the whole lineup:

  • j — prints the job ID as the first field 👑
  • l — labels each field 🏷️
  • h — prints column headings before the first line of output
  • V — uses %V rather than %v for formatting (string values get quoted) 💬
  • r — prints "raw", or unevaluated values
  • T — uses %T formatting. Use this for elapsed time values in seconds ⏱️
  • Y — uses %Y formatting. Use this for unix timestamp values 📅
  • , — adds a comma character after each field
  • t — adds a tab character before each field instead of the default space character
  • n — adds a newline character after each field
  • g — adds a newline character between ClassAds, and suppresses spaces before each field

Want tabular values with headings? -af:h, bestie. Tabular. Headings. Obsessed. 🫶

Want the -long equivalent format? That's -af:lrng. Go off. ✨

🚨 Real talk though, and this is not a drill: the newline and comma characters may not be used together. And the l and h characters may not be used together either. Pick a lane or the whole thing gets weird, and not in a fun way. 💅
  • -aaf[:VrTY] attr1 [attr2 ...] — (output option) okay so this one is like -autoformat, except instead of replacing the standard output columns, it appends the attribute(s) you name as extra columns, tacked on after whatever standard format or -print-format* file is already in effect. It accepts the -autoformat V, r, T or Y format qualifiers, and those will only affect the appended columns. The whole point? You get to add extra info to the default condor_status output without losing the standard columns. Iconic. And ngl, the appended columns will use the column separator and row terminator characters from the format that is appended to. 💖
  • -format fmt attr — (Custom option) displays the attribute or expression attr in the format fmt. But here's the catch, bestie: to display the attribute or expression, the format must contain a single printf(3)-style conversion specifier. Attributes have to come from the resource ClassAd. Expressions are ClassAd expressions and may refer to attributes in the resource ClassAd. If the attribute is not present in a given ClassAd and cannot be parsed as an expression, then the format option gets silently skipped — no drama, no error, just gone. 👻

And the conversion specifier has to match the type of the attribute or expression or it's not gonna go well:

  • %s — suitable for strings such as Name
  • %d — suitable for integers such as LastHeardFrom
  • %f — suitable for floating point numbers such as LoadAvg
  • %v — identifies the type of the attribute, and then prints the value in an appropriate format
  • %V — identifies the type of the attribute, and then prints the value in an appropriate format as it would appear in the -long format. As an example, strings used with %V will have quote marks 💬
  • %r — prints the unevaluated, or raw values
💀 An incorrect format will result in undefined behavior. Do not use more than one conversion specifier in a given format. More than one conversion specifier will result in undefined behavior. This is the part where you listen to me.

Want to output multiple attributes? Repeat the -format option once for each desired attribute. Just like printf(3)-style formats, you may include other text that will be reproduced directly. A format without any conversion specifiers may be specified, but an attribute is still required. And to get a line break, include a backslash followed by an 'n'. 📝

  • -print-format file — reads output formatting information from the given custom print format file. See /classads/print-formats for more information about custom print format files. ✨
  • -target filename — (Custom option) where evaluation requires a target ClassAd to evaluate against, the file filename contains the target ClassAd. 🎯
  • -merge filename — (Custom option) ads will be read from filename — and filename may be - to indicate standard in — and then compared to the ads selected by the query specified by the remainder of the command line. Ads will be considered the same if their sort keys match; sort keys may be specified with [-sort <key>]. 🫶

This option will cause up to three tables to print, in this order, depending on where a given ad appeared:

  1. the ads which appeared in the query but not in filename
  2. the ads which appeared in both the query and in filename
  3. the ads which appeared in filename but not in the query

By default, banners will label each table. If -xml is also given, the same banners will separate three valid XML documents, one for each table. If -json is also given, a single JSON object will be produced, with the usual JSON output for each table labeled as an element in the object. 🌈

The -annex option changes this default so that the banners are not printed and the tables are formatted differently. In this case, the ads in filename are expected to have different contents from the ads in the query, so many others will behave strangely. 🙈 Proceed accordingly.

🫶 GENERAL REMARKS 🫶

okay bestie, before you go piping anything into awk, pls read this lil list, it's giving mandatory reading energy 💅

  • The default output from condor_status is formatted to be human readable, NOT script readable. In an effort to make the output fit within 80 characters, values in some fields might be truncated. And honestly? The HTCondor Project can (and does) change the formatting of this default output as we see fit. So any script that's trying to parse data from condor_status is strongly encouraged to use the -format option (described above, bestie, scroll up). 🚨
  • The information obtained from condor_startd and condor_schedd daemons may sometimes appear to be inconsistent. This is normal, no cap — condor_startd and condor_schedd daemons update the HTCondor manager at different rates, and there's a delay as information propagates through the network and the system. Just two icons living their lives at different speeds 💀
  • Note that the ActivityTime in the Idle state is not the amount of time that the machine has been idle. The way that these are different things... see the section on condor_startd states in the Administrator's Manual for more info (/admin-manual/installation-startup-shutdown-reconfiguration).
  • When using condor_status on a pool with SMP machines, you've got two options: provide the host name, in which case you'll get back info about all slots that are represented on that host, or list specific slots by name. 👑 See the examples below for the deets.
  • If you specify host names without domains, HTCondor will automatically try to resolve those host names into fully qualified host names for you. 🦋 This also works when specifying specific nodes of an SMP machine. In this case, everything after the "@" sign is treated as a host name, and that is what is resolved.
  • You can use the -direct option in conjunction with almost any other set of options. However, at this time, not all daemons will respond to direct queries for its ad(s). The condor_startd will respond to requests for Startd ads. The condor_schedd will respond to requests for Schedd and Submitter ads. So the only options currently not supported with -direct are -master and -collector. Most other options use startd ads for their information, so they work seamlessly with -direct. The only other restriction on -direct is that you may only use 1 -direct option at a time. If you want to query information directly from multiple hosts, you must run condor_status multiple times. periodt. 🔥
  • Unless you use the local host name with -direct, condor_status will still have to contact a collector to find the address where the specified daemon is listening. So, using a -pool option in conjunction with -direct just tells condor_status which collector to query to find the address of the daemon you want. The information actually displayed will still be retrieved directly from the daemon you specified as the argument to -direct. 👀 And listen: do not use -direct to query the Collector ad, just use -pool and -collector.
bestie fr fr, that last one bites people. -direct = talk straight to the daemon, but you still need a collector to find it. iykyk.

✨ EXAMPLES ✨

🌸 Example 1

To view information from all nodes of an SMP machine, use only the host name. For example, if you had a 4-CPU machine, named vulture.cs.wisc.edu, you might see 💖

$ condor_status vulture

Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime

slot1@vulture.cs.w LINUX      INTEL  Claimed   Busy     1.050   512  0+01:47:42
slot2@vulture.cs.w LINUX      INTEL  Claimed   Busy     1.000   512  0+01:48:19
slot3@vulture.cs.w LINUX      INTEL  Unclaimed Idle     0.070   512  1+11:05:32
slot4@vulture.cs.w LINUX      INTEL  Unclaimed Idle     0.000   512  1+11:05:34

                     Total Owner Claimed Unclaimed Matched Preempting Backfill

             INTEL/LINUX     4     0       2         2       0          0        0

                   Total     4     0       2         2       0          0        0

🦋 Example 2

To view information from a specific node of an SMP machine, specify the node directly. You do this by providing the name of the slot. This has the form slot#@hostname. For example:

$ condor_status slot3@vulture

Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime

slot3@vulture.cs.w LINUX      INTEL  Unclaimed Idle     0.070   512  1+11:10:32

                     Total Owner Claimed Unclaimed Matched Preempting Backfill

             INTEL/LINUX     1     0       0         1       0          0        0

                   Total     1     0       0         1       0          0        0

💅 Example 3

The -compact option gives a one line summary of each machine using information from the partitionable slot. If the normal output is this ⬇️

$ condor_status vulture

Name               OpSys      Arch   State     Activity LoadAv Mem   ActvtyTime

slot1@vulture.cs.w LINUX      X86_64 Unclaimed Idle      0.000  679  1+03:18:58
slot1_1@vulture.cs LINUX      X86_64 Claimed   Busy      1.160 1152  0+03:21:02
slot1_2@vulture.cs LINUX      X86_64 Claimed   Busy      1.150 2560  0+10:20:50
slot1_3@vulture.cs LINUX      X86_64 Claimed   Busy      1.160 2816  0+01:32:08
slot1_4@vulture.cs LINUX      X86_64 Claimed   Busy      0.000 5081  0+00:00:00

                     Machines Owner Claimed Unclaimed Matched Preempting  Drain

            X86_64/LINUX        5     0       4         1       0          0      0

                   Total        5     0       4         1       0          0      0

For the same machine in the same state the -compact option will show this ⬇️

$ condor_status -compact vulture

Machine            Platform    Slots Cpus Gpus  TotalGb FreCpu  FreeGb  CpuLoad ST Jobs/Min MaxSlotGb

vulture.cs.wisc.ed x64/CentOS7     4    8    2       12      0     .66      .98 Cb      .25      4.96

                     Machines Owner Claimed Unclaimed Matched Preempting  Drain

            X86_64/CentOS7      4     0       4         1       0          0      0

                   Total        4     0       4         1       0          0      0

okay let's decode this glow-up, because every column is serving a purpose 🎀

  • The Slots column shows that 4 slots have been carved out of the partitionable slot, leaving 0 cpus and .66 Gigabytes of memory free. Static slots will not be counted in the Slots column.
  • The ST column shows the consensus state of the dynamic slots using a two character code. The first character is the State, the second is the activity. If there is not a consensus for either the state or activity, then # will be shown. The example shows Cb for Claimed/Busy since all of the dynamic slots are in that state. If one of the dynamic slots were Idle, then C# would be shown.
  • The Jobs/Min shows the recent job start rate for the machine. A large number here is normal for a machine that just came online, but if this number stays above 1 for more than a minute, that can be an indication of a machine is acting as a black hole for jobs, starting them quickly and then failing them just as quickly. 💀 not the job blender...
  • The MaxSlotGb column shows the memory allocated to the largest slot in Gigabytes. If the memory allocated for the largest slot cannot be determined, * will be displayed. Static slots are not counted in the MaxSlotGb column.

🌈 Constraint option examples

The Unix command to use the constraint option to see all machines with the OpSys of "LINUX":

$ condor_status -constraint OpSys==\"LINUX\"

Note that quotation marks must be escaped with the backslash characters for most shells. 🙈

The Windows command to do the same thing:

> condor_status -constraint " OpSys==""LINUX"" "

Note that quotation marks are used to delimit the single argument which is the expression, and the quotation marks that identify the string must be escaped by using a set of two double quote marks without any intervening spaces.

To see all machines that are currently in the Idle state, the Unix command is

$ condor_status -constraint State==\"Idle\"

To see all machines that are bench marked to have a MIPS rating of more than 750, the Unix command is

$ condor_status -constraint 'Mips>750'

⭐ -cod option example

The -cod option displays the status of COD claims within a given HTCondor pool.

$ condor_status -cod
Name        ID   ClaimState TimeInState RemoteUser JobId Keyword
astro.cs.wi COD1 Idle        0+00:00:04 wright
chopin.cs.w COD1 Running     0+00:02:05 wright     3.0   fractgen
chopin.cs.w COD2 Suspended   0+00:10:21 wright     4.0   fractgen

               Total  Idle  Running  Suspended  Vacating  Killing
 INTEL/LINUX       3     1        1          1         0        0
       Total       3     1        1          1         0        0

💜 -format option example

To display the name and memory attributes of each job ClassAd in a format that's easily parsable by other tools:

$ condor_status -format "%s " Name -format "%d\n" Memory

To do the same with the autoformat option, run

$ condor_status -autoformat Name Memory

To see current disk usage of all slots enforcing disk limits run

$ condor_status -lvm

NAME                       PROVISION ALLOCATED   USAGE

slot1_1@ep1.chtc.wisc.edu  thick        2.0 MB   1.81%
slot1_2@ep1.chtc.wisc.edu  thick       10.0 GB  74.54%
slot1_8@ep2.chtc.wisc.edu  thin       600.0 MB  18.84%

To see which condor_startds are enforcing disk limits run

$ condor_status -lvm -startd

HOST              DEVICE              PROVISION     DISK  LOOPBACK

ep1.chtc.wisc.edu htc_vg              thick      100.0 GB    false
ep2.chtc.wisc.edu htc_vg/htc_thinpool thin       100.0 GB    false

👑 EXIT STATUS 👑

condor_status will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure. zero means slay, one means uh oh bestie 🫶

🎀 AUTHOR 🎀

HTCondor Team 💖 (the icons who built all of this, fr fr)

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.

and that's the whole page bestie!! 🌈 this one's the CONDOR_STATUS(1) manual from Oct 16, 2026 💅 go forth and query ur pool, u got this 👑✨

📦 where this page comes from