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
35
36 All values within <> are substituted with current values. The building
37 of this potentially large tar file can require a fair amount of tempo‐
38 rary space. If the -- scratchoption is specified, it identifies a
39 directory in which to build the tar file. If the -- scratchoption is
40 notspecified, then the directory will be /tmp/cgi-<PID>, where the
41 process ID is that of the condor_gather_infoexecutable.
42
43 The information gathered by this tool:
44
45 1. Identity
46
47 * User name who generated the report
48
49 * Script location and machine name
50
51 * Date of report creation
52
53 * uname -a
54
55 * Contents of /etc/issue
56
57 * Contents of /etc/redhat-release
58
59 * Contents of /etc/debian_version
60
61 * Contents of $(LOG)/MasterLog
62
63 * Contents of $(LOG)/ShadowLog
64
65 * Contents of $(LOG)/SchedLog
66
67 * Output of ps -auxww -forest
68
69 * Output of df -h
70
71 * Output of iptables -L
72
73 * Output of ls `condor_config_val LOG`
74
75 * Output of ldd `condor_config_val SBIN`/condor_schedd
76
77 * Contents of /etc/hosts
78
79 * Contents of /etc/nsswitch.conf
80
81 * Output of ulimit -a
82
83 * Output of uptime
84
85 * Output of free
86
87 * Network interface configuration (ifconfig)
88
89 * HTCondor version
90
91 * Location of HTCondor configuration files
92
93 * HTCondor configuration variables
94
95 * All variables and values
96
97 * Definition locations for each configuration variable
98
99 2. Job Information
100
101 * Output of condor_q jobid
102
103 * Output of condor_q -l jobid
104
105 * Output of condor_q -analyze jobid
106
107 * Job event log, if it exists
108
109 * Only events pertaining to the job ID
110
111 * If condor_gather_infohas the proper permissions, it runs con‐
112 dor_fetchlogon the machine where the job most recently ran, and
113 includes the contents of the logs from the condor_master, con‐
114 dor_startd, and condor_starter.
115
117 --jobid <ClusterId.ProcId>
118
119 Data mine information about this HTCondor job from the local HTCon‐
120 dor installation and condor_schedd.
121
122
123
124 --scratch /path/to/directory
125
126 A path to temporary space needed when building the output tar file.
127 Defaults to /tmp/cgi-<PID>, where <PID>is replaced by the process ID
128 of condor_gather_info.
129
130
131
133 * condor-profile.txtThe Identity portion of the information gathered
134 when condor_gather_infois run without arguments.
135
136
137
138 * cgi-<username>-jid<clus‐
139 ter>.<proc>-<year>-<month>-<day>-<hour>_<minute>_<sec‐
140 ond>-<TZ>.tar.gzThe output file which contains all of the informa‐
141 tion produced by this tool.
142
144 condor_gather_infowill exit with a status value of 0 (zero) upon suc‐
145 cess, and it will exit with the value 1 (one) upon failure.
146
148 Center for High Throughput Computing, University of Wisconsin-Madison
149
151 Copyright (C) 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)