Check Certificate UIs: Difference between revisions

From T2B Wiki
Jump to navigation Jump to search
(Created page with "=== We are going to check the following:=== # You can create a proxy using your certificate, which means it is registered to the VO cms # We can extract your username from sit...")
 
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
__NOTOC__
=== We are going to check the following:===
=== We are going to check the following:===
# You can create a proxy using your certificate, which means it is registered to the VO cms
# You can create a proxy using your certificate, which means it is registered to the VO
# We can extract your username from siteDB based on your certificate.
# [CMS only] We can extract your username from siteDB based on your certificate.
# You have write access to the T2_BE_IIHE
# You have write access to the T2_BE_IIHE


All the commands below need to be executed on an UI (mX machine). This requires your certificate is correctly installed there ([[Certificate_to_UI | check here]] for all the steps, although it should already have been done).
All the commands below need to be executed on an UI (mX machine). This requires your certificate is correctly installed there ([[Certificate_to_UI | check here]] for all the steps, although it should already have been done).


=== 1. Checking you can get a proxy with your certificate ===
=== 1. Checking you can get a proxy with your certificate ===
  voms-proxy-init
  voms-proxy-init --voms cms|icecube|beapps
should give you
should give you
<pre>
<pre>
Enter GRID pass phrase for this identity:
Enter GRID pass phrase for this identity:
Contacting voms01.begrid.be:18004 [/DC=org/DC=terena/DC=tcs/C=BE/ST=Brussels/L=Brussels/O=Le reseau telematique belge de la recherche/CN=voms01.begrid.be] "beapps"...
Remote VOMS server contacted succesfully.


Created proxy in /tmp/x509up_u20522.
Created proxy in /tmp/x509up_u20522.


Your proxy is valid until Fri Nov 06 04:33:33 CET 2015
Your proxy is valid until Wed Nov 09 01:47:29 CET 2016
</pre>
</pre>


if not, then first check with the error message if you can't fix it (check -again- all the [[Certificate_to_UI | '''steps to install the p12 on the UIs''']] have been followed), or send us a mail with the content of the error message.
if not, then first check with the error message if you can't fix it (check -again- all the [[Certificate_to_UI | '''steps to install the p12 on the UIs''']] have been followed), or send us a mail with the content of the error message.


<br><br>


=== 2. Extraction of your username from siteDB ===
=== [For CMS only steps] Get a working CMSSW environment ===
In order for the next steps to work, you need a working cmssw environment. You need to check out any CMSSW version available on the site.
To determine which exist, do:
source $VO_CMS_SW_DIR/cmsset_default.sh
scram list CMSSW
 
This returns a list of CMSSW versions. Just pick one and do:
cmsrel CMSSW_<version>                (replace<version> by the version you chose, eg: 10_6_29)
cd CMSSW_<version>/src
cmsenv
 
=== 3. [CMS only] Extraction of your username from siteDB ===
For this, we are going to use crab3. Source the init script to enable crab3:
For this, we are going to use crab3. Source the init script to enable crab3:
  source /cvmfs/cms.cern.ch/crab3/crab.sh
  source /cvmfs/cms.cern.ch/common/crab-setup.sh
then do:
then do:
  crab checkusername
  crab checkusername
It should print your DN, as well as your username. <br>
It should simply return your username. <br>
If it doesn't work, make sure all the [[CERN_certificate_management | '''steps here''']] have been followed.
If it doesn't work, make sure all the [[CERN_certificate_management | '''steps here''']] have been followed.


 
=== 4. Test write access to T2_BE_IIHE ===
=== 3. Test write access to T2_BE_IIHE ===
<br>
Again, using crab3:
* For CMS users, again, using crab3:
  crab checkwrite --site=T2_BE_IIHE
  crab checkwrite --site=T2_BE_IIHE
It should give you the following
It should give you the following
Line 38: Line 54:
If it doesn't work and all previous steps are fine, then send us an email with your DN, we will make sure it matches what we have.
If it doesn't work and all previous steps are fine, then send us an email with your DN, we will make sure it matches what we have.


<br>
* For everyone, you can try writing a file in your '''/pnfs''' directory:
gfal-copy file:///user/$USER/mytestfile srm://maite.iihe.ac.be:8443/pnfs/iihe/MYEXPERIMENT/store/user/$USER/


:where '''MYEXPERIMENT''' is either cms, icecube or solid .


<br>
For more grid commands to manipulate files, please read [[GridStorageAccess|this page]]


 
<br><br>
<span style="font-size: 200%;"> <center>You should now be able to submit grid jobs ! Congratulations !! </center></span>
<span style="font-size: 200%;"> <center>You should now be able to submit grid jobs ! Congratulations !! </center></span>
<span style="font-size: 70%;"> <center>And that's the end of the story ... </center></span>
<span style="font-size: 70%;"> <center>And that's the end of the story ... </center></span>

Latest revision as of 11:05, 28 March 2023


We are going to check the following:

  1. You can create a proxy using your certificate, which means it is registered to the VO
  2. [CMS only] We can extract your username from siteDB based on your certificate.
  3. You have write access to the T2_BE_IIHE

All the commands below need to be executed on an UI (mX machine). This requires your certificate is correctly installed there ( check here for all the steps, although it should already have been done).

1. Checking you can get a proxy with your certificate

voms-proxy-init --voms cms|icecube|beapps

should give you

Enter GRID pass phrase for this identity:
Contacting voms01.begrid.be:18004 [/DC=org/DC=terena/DC=tcs/C=BE/ST=Brussels/L=Brussels/O=Le reseau telematique belge de la recherche/CN=voms01.begrid.be] "beapps"...
Remote VOMS server contacted succesfully.


Created proxy in /tmp/x509up_u20522.

Your proxy is valid until Wed Nov 09 01:47:29 CET 2016

if not, then first check with the error message if you can't fix it (check -again- all the steps to install the p12 on the UIs have been followed), or send us a mail with the content of the error message.



[For CMS only steps] Get a working CMSSW environment

In order for the next steps to work, you need a working cmssw environment. You need to check out any CMSSW version available on the site. To determine which exist, do:

source $VO_CMS_SW_DIR/cmsset_default.sh
scram list CMSSW

This returns a list of CMSSW versions. Just pick one and do:

cmsrel CMSSW_<version>                (replace<version> by the version you chose, eg: 10_6_29)
cd CMSSW_<version>/src
cmsenv

3. [CMS only] Extraction of your username from siteDB

For this, we are going to use crab3. Source the init script to enable crab3:

source /cvmfs/cms.cern.ch/common/crab-setup.sh

then do:

crab checkusername

It should simply return your username.
If it doesn't work, make sure all the steps here have been followed.

4. Test write access to T2_BE_IIHE


  • For CMS users, again, using crab3:
crab checkwrite --site=T2_BE_IIHE

It should give you the following

 Checkwrite Result:
  Success: Able to write in /store/user/rougny on site T2_BE_IIHE

If it doesn't work and all previous steps are fine, then send us an email with your DN, we will make sure it matches what we have.


  • For everyone, you can try writing a file in your /pnfs directory:
gfal-copy file:///user/$USER/mytestfile srm://maite.iihe.ac.be:8443/pnfs/iihe/MYEXPERIMENT/store/user/$USER/
where MYEXPERIMENT is either cms, icecube or solid .


For more grid commands to manipulate files, please read this page



You should now be able to submit grid jobs ! Congratulations !!
And that's the end of the story ...