LSF Version 7.3 - Platform LSF Configuration Reference

lsb.events
The LSF batch event log file lsb.events is used to display LSF batch event history and for mbatchd failure recovery.
Whenever a host, job, or queue changes status, a record is appended to the event log file. The file is located in
LSB_SHAREDIR/cluster_name/logdir, where LSB_SHAREDIR must be defined in lsf.conf(5) and
cluster_name is the name of the LSF cluster, as returned by lsid. See mbatchd(8) for the description of
LSB_SHAREDIR.
The bhist command searches the most current lsb.events file for its output.
lsb.events structure
The event log file is an ASCII file with one record per line. For the lsb.events file, the first
line has the format # history_seek_position>, which indicates the file position of the
first history event after log switch. For the lsb.events.# file, the first line has the format #
timestamp_most_recent_event, which gives the timestamp of the most recent event in
the file.
Limiting the size of lsb.events
Use MAX_JOB_NUM in lsb.params to set the maximum number of finished jobs whose
events are to be stored in the lsb.events log file.
Once the limit is reached, mbatchd starts a new event log file. The old event log file is saved
as lsb.events.n, with subsequent sequence number suffixes incremented by 1 each time a
new log file is started. Event logging continues in the new lsb.events file.
Records and fields
The fields of a record are separated by blanks. The first string of an event record indicates its
type. The following types of events are recorded:
•
JOB_NEW
•
JOB_FORWARD
•
JOB_ACCEPT
•
JOB_START
•
JOB_START_ACCEPT
•
JOB_STATUS
•
JOB_SWITCH
•
JOB_MOVE
•
QUEUE_CTRL
•
HOST_CTRL
•
MBD_START
•
MBD_DIE
•
UNFULFILL
•
LOAD_INDEX
•
JOB_SIGACT
•
MIG
•
JOB_MODIFY2
•
JOB_SIGNAL
•
JOB_EXECUTE
lsb.events
188 Platform LSF Configuration Reference