condor_fetchlog man page

condor_fetchlogRetrieve a daemon's log file that is located on another computer


condor_fetchlog[-help -version]

condor_fetchlog[-pool centralmanagerhostname[:portnumber]] [-master -startd -schedd -collector -negotiator -kbdd] machine-namesubsystem[.extension]


condor_fetchlogcontacts HTCondor running on the machine specified by machine-name, and asks it to return a log file from that machine. Which log file is determined from the subsystem[.extension]argument. The log file is printed to standard output. This command eliminates the need to remotely log in to a machine in order to retrieve a daemon's log file.

For security purposes of authentication and authorization, this command requires  ADMINISTRATOR level of access.

The subsystem[.extension]argument is utilized to construct the log file's name. Without an optional .extension, the value of the configuration variable named subsystem_LOG defines the log file's name. When specified, the .extensionis appended to this value.

The subsystemargument is any value  $(SUBSYSTEM) that has a defined configuration variable of  $(SUBSYSTEM)_LOG , or any of




A value for the optional .extensionto the subsystemargument is typically one of the three strings:

1.  .old

2.  .slot<X>

3.  .slot<X>.old Within these strings,  <X> is substituted with the slot number.

A subsystemargument of  STARTD_HISTORY fetches all condor_startdhistory by concatenating all instances of log files resulting from rotation.



Display usage information


Display version information

-pool centralmanagerhostname[:portnumber]

Specify a pool by giving the central manager's host name and an optional port number


Send the command to the condor_masterdaemon (default)


Send the command to the condor_startddaemon


Send the command to the condor_schedddaemon


Send the command to the condor_collectordaemon


Send the command to the condor_kbdddaemon


To get the condor_negotiatordaemon's log from a host named from within the current pool:

condor_fetchlog NEGOTIATOR

To get the condor_startddaemon's log from a host named from within the current pool:

condor_fetchlog STARTD

This command requested the condor_startddaemon's log from the condor_master. If the condor_masterhas crashed or is unresponsive, ask another daemon running on that computer to return the log. For example, ask the condor_startddaemon to return the condor_master's log:

condor_fetchlog -startd MASTER

Exit Status

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


Center for High Throughput Computing, University of Wisconsin-Madison