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