The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Tools/Manuals/TS53
Back to Troubleshooting Guide
BrokerHelper: no compatible resources
Full message
************************************************************* BOOKKEEPING INFORMATION: Status info for the Job : https://gswms01.cern.ch:9000/ZUYZjkKFx8AfK6qq34E2Qw Current Status: Waiting Status Reason: BrokerHelper: no compatible resources Submitted: Sun Mar 27 23:16:52 2011 CEST *************************************************************
And finally:
************************************************************* BOOKKEEPING INFORMATION: Status info for the Job : https://gswms01.cern.ch:9000/ZUYZjkKFx8AfK6qq34E2Qw Current Status: Aborted Status Reason: request expired Submitted: Sun Mar 27 23:16:52 2011 CEST *************************************************************
Diagnosis
The job's JDL file contained requirements that could not be satisfied by any CE listed in the BDII used by the WMS. There can be various causes:
- typo in the JDL
- the target CE/site is unavailable
- the BDII used by the WMS has some problem (e.g. too slow)
- the WMS parameters for querying the BDII are suboptimal (e.g. timeout too short)
The WMS will repeatedly retry the match making after a configurable delay (by default 600s) until the end of a configurable grace period (by default 2h), after which the request is considered expired and the job is aborted if it still does not match any CE.
Usually it is advisable to avoid large values for the grace period, such that users may learn after a reasonable time which jobs are affected by the problem. The user can shorten the grace period through the "--to" and "--valid" options of glite-wms-job-submit.