Which events are logged for a particular daemon are determined by the value of configuration variable <SUBSYS>_DEBUG. The possible values for <SUBSYS>_DEBUG categorize events, such that it is possible to control the level and quantity of events written to the daemon's log.
Configuration variables that affect daemon logs are
Daemon logs are often investigated to accomplish administrative debugging. condor_config_val can be used to determine the location and file name of the daemon log. For example, to display the location of the log for the condor_collector daemon, use
condor_config_val COLLECTOR_LOG
Within the log, each transaction is identified with an integer value and followed where appropriate with other values relevant to the transaction. To reduce the size of the log and remove any transactions that are no longer relevant, a copy of the log is kept by renaming the log at each time interval defined by configuration variable QUEUE_CLEAN_INTERVAL, and then a new log is written with only current and relevant transactions.
Configuration variables that affect the job queue log are
This log exists to help administrators track the activities of pool users.
The file name is set by configuration variable SCHEDD_AUDIT_LOG.
Configuration variables that affect the audit log are
This log exists to help administrators track the activities of pool users.
The file name is set by configuration variable SHARED_PORT_AUDIT_LOG.
Configuration variables that affect the audit log are
Configuration variables that affect the event log, setting details such as the maximum size to which this log may grow and details of file rotation and locking are
username@uid_domain
.
To reduce the size and remove information that is no longer relevant, a copy of the log is made when its size hits the number of bytes defined by configuration variable MAX_ACCOUNTANT_DATABASE_SIZE, and then a new log is written in a more compact form.
Administrators can change user priorities kept in this log by using the command line tool condor_userprio.
Administrators can change view this historical information by using the command line tool condor_history.
Configuration variables that affect the history log, setting details such as the maximum size to which this log may grow are
The file name is set by configuration variable DAGMAN_DEFAULT_NODE_LOG, and the full path name of this file must be unique while any and all submitted DAGs and other jobs from the submit host run. The syntax used in the definition of this configuration variable is different to enable the setting of a unique file name. See section 3.5.23 for the complete definition.
Configuration variables that affect this log are
This log may be helpful in debugging what has happened in the execution of a DAG, as well as help to determine the final state of the DAG.
Configuration variables that affect this log are