LSF Version 7.3 - Platform LSF Configuration Reference

Batch command client messages
LSF displays error messages when a batch command cannot communicate with mbatchd. The
following table provides a list of possible error reasons and the associated error message output.
Point of failure Possible reason Error message output
Establishing a
connection with mbatchd
mbatchd is too busy to accept new
connections. The connect() system call times
out.
LSF is processing your request. Please
wait…
mbatchd is down or there is no process
listening at either the LSB_MBD_PORT or the
LSB_QUERY_PORT
LSF is down. Please wait…
mbatchd is down and the
LSB_QUERY_PORT is busy
bhosts displays "LSF is down. Please
wait. . ."
bjobs displays "Cannot connect to LSF.
Please wait…"
Socket error on the client side Cannot connect to LSF. Please wait…
connect() system call fails Cannot connect to LSF. Please wait…
Internal library error Cannot connect to LSF. Please wait…
Send/receive handshake
message to/from
mbatchd
mbatchd is busy. Client times out when
waiting to receive a message from mbatchd.
LSF is processing your request. Please
wait…
Socket read()/write() fails Cannot connect to LSF. Please wait…
Internal library error Cannot connect to LSF. Please wait…
Batch event format errors
When mbatchd and batch commands fail reading lsb.events, LSF logs and displays details
about which event field was reached when parsing of the event file failed.
event time_stamp offset[byte:field]: field_name [field_name ...]
where:
event
The name of the event being parsed.
time_stamp
The timestamp of the event. Use this field to search for the problem record from history
event files.
offset[byte:field]
Byte offset is the approximate position in the line (number of characters from
beginning of the line) where parsing the fields failed.
Field offset is the number of field where parsing failed.
field_name
Troubleshooting and error messages
Platform LSF Configuration Reference 607