Difference: Crabguide (1 vs. 4)

Revision 42009-06-20 - ZhangXiaomei

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

Usage of CMS CRAB

Line: 7 to 6
 This segment introduces how to use CRAB and the bugs of some CRAB versions I met when I do the tests on our UI.

How to use crab?

Changed:
<
<
There are two ways. one way is to use CRAB installed at CERN, the other is to install CRAB in our UI.
*Use CRAB installed at CERN:
1.The last version of CRAB is already installed at CERN, just do:
      source  /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.(c)sh
2.Then copy locally the crab.cfg file from dir $CRABDIR/python/crab.cfg.
*Use CRAB installed in cmsui01 or lcg003:
   1.download the last CRAB_X_Y_Z tgz archive from [[http://cmsdoc.cern.ch/cms/ccs/wm/www/Crab/download.html][Download]] or from the CERN afs server:
     /afs/cern.ch/cms/ccs/wm/scripts/Crab/      
   2. untar the tgz file in a directory "YOUR_DIR" of your UI
   3. run the configure file you can find in "YOUR_DIR"/CRAB_X_Y_Z/ from a clean shell: 
       cd YOUR_DIR/CRAB_X_Y_Z/
       ./configure 
   4. source YOUR_DIR/CRAB_X_Y_Z/crab.(c)sh.
>
>
There are two ways. one way is to use CRAB installed at CERN, the other is to install CRAB in our UI.
*Use CRAB installed at CERN:
1.The last version of CRAB is already installed at CERN, just do:       source  /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.(c)sh 2.Then copy locally the crab.cfg file from dir $CRABDIR/python/crab.cfg. 
*Use CRAB installed in cmsui01 or lcg003:
   1.download the last CRAB_X_Y_Z tgz archive from [[http://cmsdoc.cern.ch/cms/ccs/wm/www/Crab/download.html][Download]] or from the CERN afs server:      /afs/cern.ch/cms/ccs/wm/scripts/Crab/          2. untar the tgz file in a directory "YOUR_DIR" of your UI    3. run the configure file you can find in "YOUR_DIR"/CRAB_X_Y_Z/ from a clean shell:         cd YOUR_DIR/CRAB_X_Y_Z/        ./configure     4. source YOUR_DIR/CRAB_X_Y_Z/crab.(c)sh. 
 

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.
  2. check if you have a valid grid certificate
Changed:
<
<
  1. Have you tested your code locally?
  2. Are you using the latest CRAB version? (See the latest CRAB tarball ) * If not, download it.
  3. 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.
  4. 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.
  5. 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.
>
>
  1. Have you tested your code locally?
  2. Are you using the latest CRAB version? (See the latest CRAB tarball ) * If not, download it.
  3. 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.
  4. 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.
  5. 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.
 
  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.
  2. 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

Changed:
<
<
I have tried to install three CRAB versions in cmsui01. I am successful with CRAB_2_0_4, CRAB_2_1_2, but failed with CRAB_2_2_1.
*the following error found when I use crab_2_2_1 in lcg003
crab: Scheduler Session: 'Cannot create scheduler SchedulerGLiteAPI  \t \n         missing glite environment.\n         Try export PYTHONPATH=$PYTHONPATH GLITE_LOCATION/lib\n         No module named SOAPpy.Client'
*the following error found when I use crab_2_2_1 in cmsui01
Error: Unable to find pyOpenSSL module
>
>
I have tried to install three CRAB versions in cmsui01. I am successful with CRAB_2_0_4, CRAB_2_1_2, but failed with CRAB_2_2_1.
*the following error found when I use crab_2_2_1 in lcg003
crab: Scheduler Session: 'Cannot create scheduler SchedulerGLiteAPI  \t \n         missing glite environment.\n         Try export PYTHONPATH=$PYTHONPATH GLITE_LOCATION/lib\n         No module named SOAPpy.Client' 
*the following error found when I use crab_2_2_1 in cmsui01
Error: Unable to find pyOpenSSL module 

Official links for CRAB

CRAB Users

CRAB Developpers

  Please feel free to give some comments.

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

Revision 22008-06-24 - ZhangXiaomei

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

Usage of CMS CRAB

Line: 7 to 8
 

How to use crab?

There are two ways. one way is to use CRAB installed at CERN, the other is to install CRAB in our UI.
Changed:
<
<

*Use CRAB installed at CERN:
>
>

*Use CRAB installed at CERN:
 
1.The last version of CRAB is already installed at CERN, just do:
      source  /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.(c)sh

Line: 24 to 25
 
  1. source YOUR_DIR/CRAB_X_Y_Z/crab.(c)sh.
Added:
>
>

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.
  2. Do you have a valid grid certificate? (See Test your grid certifacate below)
  3. Have you tested your code locally? (See Test your code locally below)
  4. Are you using the latest CRAB version? (See the latest CRAB tarball ) * If not, download it.
  5. 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.
  6. 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.
  7. 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.
  8. 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)
  9. 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

I have tried to install three CRAB versions in cmsui01. I am successful with CRAB_2_0_4, CRAB_2_1_2, but failed with CRAB_2_2_1.
Changed:
<
<

*the following error found when I use crab_2_2_1 in lcg003
>
>

*the following error found when I use crab_2_2_1 in lcg003
 
crab: Scheduler Session: 'Cannot create scheduler SchedulerGLiteAPI  \t \n         missing glite environment.\n         Try export PYTHONPATH=$PYTHONPATH GLITE_LOCATION/lib\n         No module named SOAPpy.Client'

Revision 12008-06-05 - ZhangXiaomei

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

Usage of CMS CRAB

This segment introduces how to use CRAB and the bugs of some CRAB versions I met when I do the tests on our UI.

How to use crab?

There are two ways. one way is to use CRAB installed at CERN, the other is to install CRAB in our UI.
*Use CRAB installed at CERN:
1.The last version of CRAB is already installed at CERN, just do:
      source  /afs/cern.ch/cms/ccs/wm/scripts/Crab/crab.(c)sh
2.Then copy locally the crab.cfg file from dir $CRABDIR/python/crab.cfg.
*Use CRAB installed in cmsui01 or lcg003:
   1.download the last CRAB_X_Y_Z tgz archive from [[http://cmsdoc.cern.ch/cms/ccs/wm/www/Crab/download.html][Download]] or from the CERN afs server:
     /afs/cern.ch/cms/ccs/wm/scripts/Crab/      
   2. untar the tgz file in a directory "YOUR_DIR" of your UI
   3. run the configure file you can find in "YOUR_DIR"/CRAB_X_Y_Z/ from a clean shell: 
       cd YOUR_DIR/CRAB_X_Y_Z/
       ./configure 
   4. source YOUR_DIR/CRAB_X_Y_Z/crab.(c)sh.

The bugs found in some CRAB versions

I have tried to install three CRAB versions in cmsui01. I am successful with CRAB_2_0_4, CRAB_2_1_2, but failed with CRAB_2_2_1.
*the following error found when I use crab_2_2_1 in lcg003
crab: Scheduler Session: 'Cannot create scheduler SchedulerGLiteAPI  \t \n         missing glite environment.\n         Try export PYTHONPATH=$PYTHONPATH GLITE_LOCATION/lib\n         No module named SOAPpy.Client'
*the following error found when I use crab_2_2_1 in cmsui01
Error: Unable to find pyOpenSSL module

Please feel free to give some comments.

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