Administering Platform LSF - SAS

Common LSF Problems
LIM dies quietly
LIM unavailable
RES does not start
UNIX
Windows
Chapter 42
Troubleshooting and Error Messages
This section lists some other common problems with the LIM, RES, mbatchd,
sbatchd, and interactive applications.
Most problems are due to incorrect installation or configuration. Check the
error log files; often the log message points directly to the problem.
Run the following command to check for errors in the LIM configuration files.
% lsadmin ckconfig -v
This displays most configuration errors. If this does not report any errors, check
in the LIM error log.
Sometimes the LIM is up, but executing the lsload command prints the
following error message:
Communication time out.
If the LIM has just been started, this is normal, because the LIM needs time to
get initialized by reading configuration files and contacting other LIMs.
If the LIM does not become available within one or two minutes, check the
LIM error log for the host you are working on.
When the local LIM is running but there is no master LIM in the cluster, LSF
applications display the following message:
Cannot locate master LIM now, try later.
Check the LIM error logs on the first few hosts listed in the Host section of the
lsf.cluster.cluster_name file. If LSF_MASTER_LIST is defined in
lsf.conf, check the LIM error logs on the hosts listed in this parameter
instead.
Check the RES error log.
If the RES is unable to read the lsf.conf file and does not know where to
write error messages, it logs errors into syslog(3).
If the RES is unable to read the lsf.conf file and does not know where to
write error messages, it logs errors into C:\temp.
Administering Platform LSF 529