This is an outdated version of the HTCondor Manual. You can find current documentation at http://htcondor.org/manual.

condor_fetchlog

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

Synopsis

condor_fetchlog [-help $\vert$ -version]

condor_fetchlog [-pool centralmanagerhostname[:portnumber]] [-master $\vert$ -startd $\vert$ -schedd $\vert$ -collector $\vert$ -negotiator $\vert$ -kbdd] machine-name subsystem[.extension]

Description

condor_fetchlog contacts Condor 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 an administrator's level of access. See section 3.6.1 on page  for more details about Condor's security mechanisms.

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 .extension is appended to this value.

Typical strings for the argument subsystem are as given as possible values of the predefined configuration variable $(SUBSYSTEM). See the definition in section 3.3.1. Note that access to any additional logs can be enabled by simply specifying the path to each log in the configuration file with a configuration parameter named <NAME>_LOG, choosing an arbitrary unique name for each case.

A value for the optional .extension argument 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.

Options

-help

Display usage information

-version

Display version information

-pool centralmanagerhostname[:portnumber]

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

-master

Send the command to the condor_master daemon (default)

-startd

Send the command to the condor_startd daemon

-schedd

Send the command to the condor_schedd daemon

-collector

Send the command to the condor_collector daemon

-kbdd

Send the command to the condor_kbdd daemon

Examples

To get the condor_negotiator daemon's log from a host named head.example.com from within the current pool:

condor_fetchlog head.example.com NEGOTIATOR

To get the condor_startd daemon's log from a host named execute.example.com from within the current pool:

condor_fetchlog execute.example.com STARTD

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

condor_fetchlog -startd execute.example.com MASTER

Exit Status

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

Author

Center for High Throughput Computing, University of Wisconsin-Madison

Copyright

Copyright © 1990-2012 Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. Licensed under the Apache License, Version 2.0.

See the Condor Version 7.6.10 Manual or http://research.cs.wisc.edu/htcondor/ for additional notices.