LSF Version 7.3 - Administering Platform LSF
Error Messages
718 Administering Platform LSF
LSF command messages
LSF daemon (LIM) not responding ... still trying
During LIM restart, LSF commands will fail and display this error message. User
programs linked to the LIM API will also fail for the same reason. This message is
displayed when LIM running on the master host list or server host list is restarted
after configuration changes, such as adding new resources, binary upgrade, and so
on.
Use LSF_LIM_API_NTRIES in
lsf.conf or as an environment variable to define
how many times LSF commands will retry to communicate with the LIM API while
LIM is not available. LSF_LIM_API_NTRIES is ignored by LSF and EGO daemons
and all EGO commands.
When LSB_API_VERBOSE=Y in
lsf.conf, LSF batch commands will display the
not responding retry error message to
stderr when LIM is not available.
When LSB_API_VERBOSE=N in
lsf.conf, LSF batch commands will not display
the retry error meesage when LIM is not available.
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.
EGO command messages
You cannot run the egosh command because the administrator has chosen
not to enable EGO in lsf.conf: LSF_ENABLE_EGO=N.
If EGO is disabled, the egosh command cannot find ego.conf or cannot contact
vemkd (not started).
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…