TroubleShootingUsing
From Begrid Wiki
Jump to navigationJump to search
Troubleshooting and FAQ's for Using the BEgrid
Jobs stay in the state READY and is later aborted
Contact the administrator of the Computing Element to resolve this issue.
1. SSL Error (sslv3 alert bad certificate)
2. Unable to submit a job: Scenario 1
Selected Virtual Organisation name (from --vo option): betest **** Error: API_NATIVE_ERROR **** Error while calling the "NSClient::multi" native api AuthenticationException: Failed to establish security context... **** Error: UI_NO_NS_CONTACT **** Unable to contact any Network Server
Running it with --debug reveals:
**** Warning: UI_NO_VOMS **** Unable to find VOMS Extensions inside credential
Browse to https://voms.begrid.be:8443/voms/betest/webui/info or https://voms.begrid.be:8443/voms/beapps/webui/info to ensure you are a member of the VO in question.
3. Job proxy is expired.
All my jobs are canceled with "Job proxy is expired."
This means (a) job(s) is/are still running on an expired proxy. To resolve this: edg-job-cancel --all --vo some-vo
4. Job remains in Waiting state
Errors after submitting jobs :
Status: ************************************************************* BOOKKEEPING INFORMATION: Status info for the Job : https://gridy8.begrid.be:9000/PcGXA24FB19nIjDPXQC3OA Current Status: Waiting Status Reason: Syntax error on file "/var/edgwl/workload_manager/input.fl" (_file_sequence_t::getEnd()[202]) reached on: Mon Jan 7 09:47:50 2008 *************************************************************
