1CONDOR_GATHER_INFO(1) HTCondor Manual CONDOR_GATHER_INFO(1)
2
3
4
6 condor_gather_info - HTCondor Manual
7
8 Gather information about an HTCondor installation and a queued job
9
10
12 condor_gather_info [--jobid ClusterId.ProcId] [--scratch /path/to/di‐
13 rectory]
14
16 condor_gather_info is a Linux-only tool that will collect and output
17 information about the machine it is run upon, about the HTCondor in‐
18 stallation local to the machine, and optionally about a specified HT‐
19 Condor job. The information gathered by this tool is most often used as
20 a debugging aid for the developers of HTCondor.
21
22 Without the --jobid option, information about the local machine and its
23 HTCondor installation is gathered and placed into the file called con‐
24 dor-profile.txt, in the current working directory. The information
25 gathered is under the category of Identity.
26
27 With the --jobid option, additional information is gathered about the
28 job given in the command line argument and identified by its ClusterId
29 and ProcId ClassAd attributes. The information includes both cate‐
30 gories, Identity and Job information. As the quantity of information
31 can be extensive, this information is placed into a compressed tar
32 file. The file is placed into the current working directory, and it is
33 named using the format
34
35 cgi-<username>-jid<ClusterId>.<ProcId>-<year>-<month>-<day>-<hour>_<minute>_<second>-<TZ>.tar.gz
36
37 All values within <> are substituted with current values. The building
38 of this potentially large tar file can require a fair amount of tempo‐
39 rary space. If the --scratch option is specified, it identifies a di‐
40 rectory in which to build the tar file. If the --scratch option is not
41 specified, then the directory will be /tmp/cgi-<PID>, where the process
42 ID is that of the condor_gather_info executable.
43
44 The information gathered by this tool:
45
46 1. Identity
47
48 • User name who generated the report
49
50 • Script location and machine name
51
52 • Date of report creation
53
54 • uname -a
55
56 • Contents of /etc/issue
57
58 • Contents of /etc/redhat-release
59
60 • Contents of /etc/debian_version
61
62 • Contents of $(LOG)/MasterLog
63
64 • Contents of $(LOG)/ShadowLog
65
66 • Contents of $(LOG)/SchedLog
67
68 • Output of ps -auxww -forest
69
70 • Output of df -h
71
72 • Output of iptables -L
73
74 • Output of ls 'condor_config_val LOG'
75
76 • Output of ldd 'condor_config_val SBIN'/condor_schedd
77
78 • Contents of /etc/hosts
79
80 • Contents of /etc/nsswitch.conf
81
82 • Output of ulimit -a
83
84 • Output of uptime
85
86 • Output of free
87
88 • Network interface configuration (ifconfig)
89
90 • HTCondor version
91
92 • Location of HTCondor configuration files
93
94 • HTCondor configuration variables
95
96 • All variables and values
97
98 • Definition locations for each configuration variable
99
100 2. Job Information
101
102 • Output of condor_q jobid
103
104 • Output of condor_q -l jobid
105
106 • Output of condor_q -analyze jobid
107
108 • Job event log, if it exists
109
110 • Only events pertaining to the job ID
111
112 • If condor_gather_info has the proper permissions, it runs con‐
113 dor_fetchlog on the machine where the job most recently ran, and
114 includes the contents of the logs from the condor_master, con‐
115 dor_startd, and condor_starter.
116
118 -jobid <ClusterId.ProcId>
119 Data mine information about this HTCondor job from the local
120 HTCondor installation and condor_schedd.
121
122 -scratch /path/to/directory
123 A path to temporary space needed when building the output tar
124 file. Defaults to /tmp/cgi-<PID>, where <PID> is replaced by
125 the process ID of condor_gather_info.
126
128 • condor-profile.txt The Identity portion of the information gathered
129 when condor_gather_info is run without arguments.
130
131 • cgi-<username>-jid<clus‐
132 ter>.<proc>-<year>-<month>-<day>-<hour>_<minute>_<second>-<TZ>.tar.gz
133 The output file which contains all of the information produced by
134 this tool.
135
137 condor_gather_info will exit with a status value of 0 (zero) upon suc‐
138 cess, and it will exit with the value 1 (one) upon failure.
139
141 HTCondor Team
142
144 1990-2022, Center for High Throughput Computing, Computer Sciences De‐
145 partment, University of Wisconsin-Madison, Madison, WI, US. Licensed
146 under the Apache License, Version 2.0.
147
148
149
150
1518.8 Jan 19, 2022 CONDOR_GATHER_INFO(1)