LSF Version 7.3 - Platform LSF Configuration Reference

releaseElogLock: unlink(<logdir/lockfile>) failed: error
touchElogLock: Failed to open lock file <logdir/file>: error
touchElogLock: close <logdir/file> failed: error
mbatchd failed to create, remove, read, or write the log directory or a file in the log directory,
for the reason given in error. Check that LSF administrator has read, write, and execute
permissions on the logdir directory.
If logdir is on AFS, check that the instructions in Administering Platform LSF have been
followed. Use the fs ls command to verify that the LSF administrator owns logdir and
that the directory has the correct ACL.
replay_newjob: File <logfile> at line <line>: Queue <queue> not
found, saving to queue <lost_and_found>replay_switchjob: File
<logfile> at line <line>: Destination queue <queue> not found,
switching to queue <lost_and_found>
When mbatchd was reconfigured, jobs were found in queue but that queue is no longer in the
configuration.
replay_startjob: JobId <jobId>: exec host <host> not found, saving to
host <lost_and_found>
When mbatchd was reconfigured, the event log contained jobs dispatched to host, but that
host is no longer configured to be used by LSF.
do_restartReq: Failed to get hData of host <host_name>/<host_addr>
mbatchd received a request from sbatchd on host host_name, but that host is not known to
mbatchd. Either the configuration file has been changed but mbatchd has not been
reconfigured to pick up the new configuration, or host_name is a client host but the sbatchd
daemon is running on that host. Run the following command to reconfigure the mbatchd or
kill the sbatchd daemon on host_name.
badmin reconfig
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.
Troubleshooting and error messages
606 Platform LSF Configuration Reference