next up previous contents index
Next: Common load errors reported Up: Load errors Previous: Load errors   Contents   Index

Common load errors detected by yod

Some of the more common error messages displayed when yod detects a problem are listed here.




\fbox{\parbox{5.5 in}{\tt Unable to find {\em file} in current working directory or in your PATH}}

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.




\fbox{\parbox{5.5 in}{\tt bad format in load file}}

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.




\fbox{\parbox{5.5 in}{\tt Compute nodes requested exceed PBS allocation}}

\fbox{\parbox{5.5 in}{\tt The total number of nodes requested in your load file\linebreak[4]
exceeds the number of nodes allocated to your job by PBS }}

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.




\fbox{\parbox{5.5 in}{\tt
Unable to allocate these nodes to your job.\linebreak...
...d give you more \linebreak[4]
total nodes than the limit allocated you by PBS.}}

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.




\fbox{\parbox{5.5 in}{\tt
Unable to allocate nodes to your interactive job. The...
...ition is dedicated completely to PBS jobs \linebreak[4]
at this point in time.}}

\fbox{\parbox{5.5 in}{\tt Unable to allocate nodes to your job. The compute part...
...\linebreak[4]
Run ''pingd'' to learn about nodes reserved for interactive use.}}

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.




\fbox{\parbox{5.5 in}{\tt Unable to allocate the requested nodes.\linebreak[4]
Insufficient number of free compute nodes.}}

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.




\fbox{\parbox{5.5 in}{\tt Unable to allocate nodes to your PBS batch job.\linebr...
...scheduling at this time.\linebreak[4]
Please contact the system adminstrators.}}

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.


next up previous contents index
Next: Common load errors reported Up: Load errors Previous: Load errors   Contents   Index
Lee Ann Fisk 2001-06-25