1condor_fetchlog(1) General Commands Manual condor_fetchlog(1)
2
3
4
6 condor_fetchlogRetrieve a daemon's log file that is located on another
7 computer
8
10 condor_fetchlog[-help | -version]
11
12 condor_fetchlog[-pool centralmanagerhostname[:portnumber]] [-master |
13 -startd | -schedd | -collector | -negotiator | -kbdd] machine-namesub‐
14 system[.extension]
15
17 condor_fetchlogcontacts HTCondor running on the machine specified by
18 machine-name, and asks it to return a log file from that machine. Which
19 log file is determined from the subsystem[.extension]argument. The log
20 file is printed to standard output. This command eliminates the need to
21 remotely log in to a machine in order to retrieve a daemon's log file.
22
23 For security purposes of authentication and authorization, this command
24 requires ADMINISTRATORlevel of access.
25
26 The subsystem[.extension]argument is utilized to construct the log
27 file's name. Without an optional .extension, the value of the configu‐
28 ration variable named subsystem_LOG defines the log file's name. When
29 specified, the .extensionis appended to this value.
30
31 The subsystemargument is any value $(SUBSYSTEM)that has a defined con‐
32 figuration variable of $(SUBSYSTEM)_LOG, or any of
33
34 * NEGOTIATOR_MATCH
35
36 * HISTORY
37
38 * STARTD_HISTORY
39
40 A value for the optional .extensionto the subsystemargument is typi‐
41 cally one of the three strings:
42
43 1. .old
44
45 2. .slot<X>
46
47 3. .slot<X>.oldWithin these strings, <X> is substituted with the
48 slot number.
49
50 A subsystemargument of STARTD_HISTORYfetches all condor_startdhistory
51 by concatenating all instances of log files resulting from rotation.
52
54 -help
55
56 Display usage information
57
58
59
60 -version
61
62 Display version information
63
64
65
66 -pool centralmanagerhostname[:portnumber]
67
68 Specify a pool by giving the central manager's host name and an
69 optional port number
70
71
72
73 -master
74
75 Send the command to the condor_masterdaemon (default)
76
77
78
79 -startd
80
81 Send the command to the condor_startddaemon
82
83
84
85 -schedd
86
87 Send the command to the condor_schedddaemon
88
89
90
91 -collector
92
93 Send the command to the condor_collectordaemon
94
95
96
97 -kbdd
98
99 Send the command to the condor_kbdddaemon
100
101
102
104 To get the condor_negotiatordaemon's log from a host named head.exam‐
105 ple.comfrom within the current pool:
106
107 condor_fetchlog head.example.com NEGOTIATOR
108
109 To get the condor_startddaemon's log from a host named execute.exam‐
110 ple.comfrom within the current pool:
111
112 condor_fetchlog execute.example.com STARTD
113
114 This command requested the condor_startddaemon's log from the con‐
115 dor_master. If the condor_masterhas crashed or is unresponsive, ask
116 another daemon running on that computer to return the log. For example,
117 ask the condor_startddaemon to return the condor_master's log:
118
119 condor_fetchlog -startd execute.example.com MASTER
120
122 condor_fetchlogwill exit with a status value of 0 (zero) upon success,
123 and it will exit with the value 1 (one) upon failure.
124
126 Center for High Throughput Computing, University of Wisconsin-Madison
127
129 Copyright (C) 1990-2019 Center for High Throughput Computing, Computer
130 Sciences Department, University of Wisconsin-Madison, Madison, WI. All
131 Rights Reserved. Licensed under the Apache License, Version 2.0.
132
133
134
135 date condor_fetchlog(1)