next up previous contents
Next: Bad Configuration files or Up: JOB Error Messages Previous: grid-proxy-init (permission/passphrase)   Contents

Missing resources (cannot plan)

If the matchmaking process does not detect all the required resources, the submitted job fails with status flag Aborted and status reason Cannot plan, i.e. edg-job-status displays an error message of the following type:

*************************************************************
BOOKKEEPING INFORMATION:

Printing status info for the Job :
https://wn-02-32-a.cr.cnaf.infn.it:9000/LHrUgJsLYN4q0VHnJNuz0Q
Current Status:    Aborted
Status Reason:     Cannot plan (a helper failed)
reached on:        Fri Sep 19 10:51:48 2003
*************************************************************

The status Cannot plan (a helper failed) means that a helper of the Workload Manager failed. A possible reason is a matchmaker failure because no suitable resources for a given job are found.

Match making may fail for several reasons that may arise either from a failing middleware component, or application software unavailable, or a wrong request in the job JDL:

Future releases of the Work Load Manager foresee more detailed messages, like the following ones:


next up previous contents
Next: Bad Configuration files or Up: JOB Error Messages Previous: grid-proxy-init (permission/passphrase)   Contents
luvisetto 2003-12-17