condor_ fetchlog

Retrieve a log file that is located on another computer

Synopsis

condor_ fetchlog [-help | -version]

condor_ fetchlog [-pool centralmanagerhostname[:portnumber]] [-master | -startd | -schedd | -collector | -negotiator | -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. The log file is determined by combining the log file name for the specified subsystem (e.g. STARTER) with the optional extension (e.g. ``.vm2''). This simplifies the retrieval of log file by bypassing the need to log on to the machine in order to get the log file.

For security purposes of authentication and authorization, this command requires an administrator's level of access. See section 3.7.2 on page  for more details about Condor's security mechanisms.

The subsystem[.extension] argument identifies the log file to retrieve. It is defined by the subsystem_LOG entry given in the configuration file. For instance, the collector's log file is specified in the configuration file as COLLECTOR_LOG. Therefore, to read the collector's log file, COLLECTOR should be specified. The optional extension is appended to this file name (e.g. ``STARTER.vm1'' becomes ``StarterLog.vm1''). The complete list of log files that can be specified is:

  MASTER
  COLLECTOR
  NEGOTIATOR
  NEGOTIATOR_MATCH
  SCHEDD
  SHADOW
  STARTD
  STARTER
  KBDD

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

Condor Team, University of Wisconsin-Madison

Copyright

Copyright © 1990-2006 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved. No use of the Condor Software Program is authorized without the express consent of the Condor Team. For more information contact: Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

U.S. Government Rights Restrictions: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of Commercial Computer Software-Restricted Rights at 48 CFR 52.227-19, as applicable, Condor Team, Attention: Professor Miron Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison, WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.

See the Condor Version 6.7.16 Manual for additional notices.