Difference: Crabguide (2 vs. 3)

Revision 32008-06-24 - ZhangXiaomei

Line: 1 to 1
 
META TOPICPARENT name="WebHome"

Usage of CMS CRAB

Line: 28 to 28
 

How to diagnose the problem of CRAB(grid job)?

  1. Did you check if the problem is among the CRAB FAQ (See SWGuideCrabFaq) or reported in the CRAB Feedback list.
Changed:
<
<
  1. Do you have a valid grid certificate? (See Test your grid certifacate below)
  2. Have you tested your code locally? (See Test your code locally below)
>
>
  1. check if you have a valid grid certificate
  2. Have you tested your code locally?
 
  1. Are you using the latest CRAB version? (See the latest CRAB tarball ) * If not, download it.
Changed:
<
<
  1. Is your CMSSW version available at target site(s)? (See the software availability page)
>
>
  1. Is your CMSSW version available at target site(s)? (See the software availability page)
  * If not, report to Computing Infrastructure savannah in the Facilities Operations category.
Changed:
<
<
  1. Is(are) the remote site(s) operational? (See the site availability page)
>
>
  1. Is(are) the remote site(s) operational? (See the site availability page)
  * If you see the site being marked red during the time when the job failed, the reason for the failure is likely the site unavailability. The red comes from the results of the standard tests, and the failure has already been reported to the site. Try later.
Changed:
<
<
  1. Have you discovered your dataset on DBS? (See the DBS browser)
>
>
  1. Have you discovered your dataset on DBS? (See the DBS browser)
  * If you find the dataset in DBS, but your job cannot access the data, report to Computing Infrastructure savannah in the Data Operations category.
Changed:
<
<
  1. Have you planned your output handling carefully? Your job output has to be smaller than 50MB, otherwise you will be not able to retrieve it. CRAB limited the OutputSandbox size due to disk space problem in RB-WMSs. If the output of your job will be bigger than 50MB you have to copy directly the produced output from the WorkerNode to a StorageElement, selecting copy_data = 1 in crab.cfg. (Ouput files size) 1 Jobs ran but didn't produce expected output, stdout and stderr returned? (application problem, send to application support list)
>
>
  1. Have you planned your output handling carefully? Your job output has to be smaller than 50MB, otherwise you will be not able to retrieve it. CRAB limited the OutputSandbox size due to disk space problem in RB-WMSs. If the output of your job will be bigger than 50MB you have to copy directly the produced output from the WorkerNode to a StorageElement, selecting copy_data = 1 in crab.cfg.
 
  1. If everything above worked, but the problem persists, put crab.cfg, crab.log, job stderr and job stdout on webspace or in afs-public and send your question to the CRAB feedback hypernews list.

The bugs found in some CRAB versions

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback