Administering Platform LSF - SAS

Chapter 36
Event Generation
Events list
The following daemon operations cause mbatchd or the master LIM to call the
event program to generate an event. Each LSF event is identified by a
predefined number, which is passed as an argument to the event program.
Events 1-9 also return the name of the host on which on an event occurred.
1 LIM goes down (detected by the master LIM). This event may also occur if
LIM temporarily stops communicating to the master LIM.
2 RES goes down (detected by the master LIM).
3 sbatchd goes down (detected by mbatchd).
4 An LSF server or client host becomes unlicensed (detected by the master
LIM).
5 A host becomes the new master host (detected by the master LIM).
6 The master host stops being the master (detected by the master LIM).
7 mbatchd comes up and is ready to schedule jobs (detected by mbatchd).
8 mbatchd goes down (detected by mbatchd).
9 mbatchd receives a reconfiguration request and is being reconfigured
(detected by mbatchd).
10 LSB_SHAREDIR becomes full (detected by mbatchd).
Arguments passed to the LSF event program
Example
If LSF_EVENT_RECEIVER is defined, a function called ls_postevent() allows
specific daemon operations to generate LSF events. This function then calls the
LSF event program and passes the following arguments:
◆ The event receiver (LSF_EVENT_RECEIVER in lsf.conf)
◆ The cluster name
◆ The LSF event number (LSF events list or LSF_EVENT_XXXX macros in
lsf.h)
◆ The event argument (for events that take an argument)
For example, if the event receiver is the string xxx and LIM goes down on
HostA in Cluster1, the function returns:
xxx Cluster1 1 HostA
The custom LSF event program can interpret or ignore these arguments.
Administering Platform LSF 479