1CONDOR_FETCHLOG(1)              HTCondor Manual             CONDOR_FETCHLOG(1)
2
3
4

NAME

6       condor_fetchlog - HTCondor Manual
7
8       Retrieve a daemon's log file that is located on another computer
9
10
11

SYNOPSIS

13       condor_fetchlog [-help | -version ]
14
15       condor_fetchlog  [-pool centralmanagerhostname[:portnumber]] [-master |
16       -startd | -schedd | -collector | -negotiator  |  -kbdd  ]  machine-name
17       subsystem[.extension]
18

DESCRIPTION

20       condor_fetchlog  contacts  HTCondor running on the machine specified by
21       machine-name, and asks it to return  a  log  file  from  that  machine.
22       Which  log  file is determined from the subsystem[.extension] argument.
23       The log file is printed to standard output. This command eliminates the
24       need  to  remotely  log in to a machine in order to retrieve a daemon's
25       log file.
26
27       For security purposes of authentication and authorization, this command
28       requires ADMINISTRATOR level of access.
29
30       The  subsystem[.extension]  argument  is  utilized to construct the log
31       file's name. Without an optional .extension, the value of the  configu‐
32       ration  variable named subsystem _LOG defines the log file's name. When
33       specified, the .extension is appended to this value.
34
35       The subsystem argument is any value $(SUBSYSTEM)  that  has  a  defined
36       configuration variable of $(SUBSYSTEM)_LOG, or any of
37
38       • NEGOTIATOR_MATCH
39
40       • HISTORY
41
42       • STARTD_HISTORY
43
44       A  value for the optional .extension to the subsystem argument is typi‐
45       cally one of the three strings:
46
47       1. .old
48
49       2. .slot<X>
50
51       3. .slot<X>.old
52
53       Within these strings, <X> is substituted with the slot number.
54
55       A subsystem argument of STARTD_HISTORY fetches all  condor_startd  his‐
56       tory  by  concatenating all instances of log files resulting from rota‐
57       tion.
58

OPTIONS

60          -help  Display usage information
61
62          -version
63                 Display version information
64
65          -pool centralmanagerhostname[:portnumber]
66                 Specify a pool by giving the central manager's host name  and
67                 an optional port number
68
69          -master
70                 Send the command to the condor_master daemon (default)
71
72          -startd
73                 Send the command to the condor_startd daemon
74
75          -schedd
76                 Send the command to the condor_schedd daemon
77
78          -collector
79                 Send the command to the condor_collector daemon
80
81          -kbdd  Send the command to the condor_kbdd daemon
82

EXAMPLES

84       To  get the condor_negotiator daemon's log from a host named head.exam‐
85       ple.com from within the current pool:
86
87          condor_fetchlog head.example.com NEGOTIATOR
88
89       To get the condor_startd daemon's log from a host  named  execute.exam‐
90       ple.com from within the current pool:
91
92          condor_fetchlog execute.example.com STARTD
93
94       This  command  requested  the  condor_startd daemon's log from the con‐
95       dor_master. If the condor_master has crashed or  is  unresponsive,  ask
96       another daemon running on that computer to return the log. For example,
97       ask the condor_startd daemon to return the condor_master 's log:
98
99          condor_fetchlog -startd execute.example.com MASTER
100

EXIT STATUS

102       condor_fetchlog will exit with a status value of 0 (zero) upon success,
103       and it will exit with the value 1 (one) upon failure.
104

AUTHOR

106       HTCondor Team
107

109       1990-2021,  Center for High Throughput Computing, Computer Sciences De‐
110       partment, University of Wisconsin-Madison, Madison,  WI,  US.  Licensed
111       under the Apache License, Version 2.0.
112
113
114
115
1168.8                              Jan 26, 2021               CONDOR_FETCHLOG(1)
Impressum