Some of the more common error messages displayed when yod detects a problem are listed here.
If a fully qualified path name is not given, yod searches first in your
current working directory and then along your PATH variable for the
program or load file listed on the yod command line. This error message
results if the file is not found.
yod can not parse the load file. If the file named on the yod command
line is not executable, yod assumes it's a load file and that it has
the format described in section 5.1.4.
yod knows how many nodes your PBS job has been allocated. If you
request more than that on the yod command line or in the load
file, yod will not load your job.
yod contacts the bebopd to get compute nodes for the application. The
bebopd knows how many compute nodes are already in use by the PBS job
that started yod. If the new nodes would cause the PBS job to have too
many compute nodes, bebopd will refuse to allocate the nodes and yod
will display this message.
If you are running yod interactively (not as part of a PBS
job), you may see one of these errors. In the first case, there
are no compute nodes allocated to non-PBS jobs. In the second
case, there are some compute nodes allocated to non-PBS jobs, but
there are not enough available to run your job.
If you are running an interactive (non-PBS) job, this message simply
means there are insufficient free nodes to run your job. If your
PBS job gets this error, something is out of balance in the runtime
system. PBS should not schedule a job unless there are sufficient
nodes to run it. The system administrator should at this point
investigate the PBS attribute values and queues to determine
what is wrong and fix it. See the PBS chapter for more information.
If you see this error, the bebopd believes that PBS scheduling
is turned off. But if a PBS job requested nodes, PBS must in
fact be scheduling jobs. A system administrator must turn on PBS
support in the bebopd with the pingd -PBSupdate on command,
or turn off scheduling in PBS with the qmgr command
set server scheduling=false.