Platform LSF Administrator's Primer Version 6.2

Common LSF Problems
Platform LSF Administrator’s Primer
62
◆ Permissions or ownership of your submission directory is incorrect for the home
directory on the execution host
◆ You have a non-shared file system
A command may fail with the following error message due to a non-uniform file name
space.
chdir(...) failed: no such file or directory
This error means that you are trying to run a command remotely, and:
◆ Your current working directory does not exist 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.
or
◆ Your current working directory is mapped to a different name on the remote host.
If the directory exists, but is mapped to a different name on the remote host, you
must 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.
10 Job is killed by some unknown signal or unknown reason
A job exit value smaller than 128 is the real exit value from your application.
If neither a user nor an LSF administrator kills the job, check if it was killed because it
exceeded a resource usage limit:
◆ Use bjobs -l to check if any limit is specified on the job submission command.
◆ Use bqueues -l to check if any limit is specified on the queue.
◆ Use bsub -q -I csh -c limit to check if any other limit is set for the job.
If none of these applies to your situation, contact
[e-mail].