LSF Version 7.3 - Administering Platform LSF

Administering Platform LSF 707
Troubleshooting and Error Messages
4 If you are using an identification daemon (defined in the lsf.conf file by
LSF_AUTH),
inetd must be configured to run the daemon. The identification
daemon must not be run directly.
5 If LSF_USE_HOSTEQUIV is defined in the
lsf.conf file, check if
/etc/hosts.equiv or HOME/.rhosts on the destination host has the client
host name in it. Inconsistent host names in a name server with
/etc/hosts and
/etc/hosts.equiv can also cause this problem.
6 On SGI hosts running a name server, you can try the following command to tell
the host name lookup code to search the
/etc/hosts file before calling the
name server.
setenv HOSTRESORDER "local,nis,bind"
7 For Windows hosts, users must register and update their Windows passwords
using the
lspasswd command. Passwords must be 3 characters or longer, and
31 characters or less.
For Windows password authentication in a non-shared file system
environment, you must define the parameter LSF_MASTER_LIST in
lsf.conf so that jobs will run with correct permissions. If you do not define
this parameter, LSF assumes that the cluster uses a shared file system
environment.
Non-uniform file name space
A command may fail with the following error message due to a non-uniform file
name space.
chdir(...) failed: no such file or directory
You are trying to execute a command remotely, where either your current working
directory does not exist on the remote host, or your current working directory is
mapped to a different name on the remote host.
If your current working directory does not exist on a remote host, you should not
execute commands remotely on that host.
On UNIX If the directory exists, but is mapped to a different name on the remote host, you
have to create symbolic links to make them consistent.
LSF can resolve most, but not all, problems using
automount. The automount maps
must be managed through NIS. Follow the instructions in your Release Notes for
obtaining technical support if you are running automount and LSF is not able to
locate directories on remote hosts.
Batch daemons die quietly
1 First, check the sbatchd and mbatchd error logs. Try running the following
command to check the configuration.
badmin ckconfig