Error In Certificate Voms Extension Not Found
Contents |
Account Grid Certificate CMS Virtual Organization SiteDB Renewing Your Grid Certificate These are the steps for getting getting an account on
Voms Proxy Init Cms
Wisconsin computers and getting credentials so that you may run jobs voms-proxy-init atlas on many computers# # AFS Account# Email help@hep.wisc.edu to get an AFS account on Wisconsin machines. Then# ssh login.hep.wisc.edu and type the command# kpasswd to change your password.# # Grid Certificate# A grid certificate gives you authorization to run jobs on many computers in the world-wide LHC Computing Grid and to access files stored in CMS storage elements, such as the HDFS system in Wisconsin.# If you have an existing DOEGrids certificate, you will not be able to renew it, because the DOEGrids Certification Authority is being phased out. You will need to follow the new procedure for getting a certificate from the CERN Certification Authority and registering it as a member in the CMS VO. In order to retain ownership of existing files belonging to you in HDFS, you will then need to contact help@hep.wisc.edu to map your new certificate to the same grid account as your old certificate.# To get a certificate, you must be a registered user at CERN for the CMS experiment and should have a valid CERN email address.# Do you have a valid CERN account/email address ? NO : please contact help@hep.wisc.edu to get this first. Otherwise, read on.# Using Firefox, go to: https://ca.cern.ch/ca/user/Request.aspx. (We have not confirmed whether other browsers work for this function.) Enter the requested information and download the new certificate into your browser. Once you have the certificate in your browser, the procedure for extracting it to a file depends on the specific browser. For Firefox 3.5.7, go to Preferences/Advanced/Encryption/View Certificates/Your Certificate. Click on your certificate and select Backup. Save it as mycert.p12 and choose whatev
Software 3 for any new or updated installations. We are considering May 31, 2013 as possible OSG 1.2 End of Life (EOL). ReleaseDocumentation VomsInstallGuide Reviewed Passedby TerrenceMartin Test Passedby MarcoMambelli Releasedby StevenTimm Voms Install Guide Introduction About this Document Installation and First Startup Requirements Installation package Create the Installation Directory Installation using Pacman Update the Environment Install the OSG CA Certificate Authority Package Starting VOMS https://www.hep.wisc.edu/cms/comp/accountSetup.html Starting/Stopping VOMS Enable Services Disable Services Service Activation Service Deactivation Included topic: Voms Installation Verification The Certificate update cron The CRL update cron The apache/tomcat daemon The mysql daemon The VOMS WEB UI The VOMS server daemon The VOMS version Security Included topic: Voms Software Discovering which version of the https://twiki.opensciencegrid.org/bin/view/ReleaseDocumentation/VomsInstallGuide OSG Software Stack you've installed. Discovering exactly what software has been installed Finding all services that are part of your install The init.d services that are included Cron jobs Log file rotation Included topic: Voms Configuration Configuration script Creating a VO Removing a VO Enabling read-only access to your VO Establishing a VO-Admin Adding a user to the VO Verifying you are a VO-Admin About VOMS testing Testing voms-proxy-init Testing voms-proxy-info Testing edg-mkgridmap Testing the GUMS interface VOMS Replication References Comments Introduction The Virtual Organization Membership Service (VOMS - https://twiki.cnaf.infn.it/cgi-bin/twiki/view/VOMS/WebHome) has three main parts: MySQL database which is a persistent repository for VO membership information, VOMS admin which provides the Web UI/services to maintain the VO membership. This requires Apache/Tomcat. VOMS server, a daemon process which services the voms-proxy-init requests. Also included in the installation is a VOMS client containing the voms-proxy-init for testing. About th
a: voms-proxy-init --voms cms:/cms/becms How can I check the validity of my Grid proxy? voms-proxy-info --all How can I destroy my proxy? voms-proxy-destroy http://doc.iihe.ac.be/wiki/t2b/index.php?title=FAQ_CMSSW_on_the_Grid&action=edit Why is my interactive analysis on a local Grid file so slow? are you writing CMSSW EDProducts to file, in addition to root histograms? If yes, this is very slow. Try to comment out the endpath in your config file and re-run. myproxy-info times out, forcing re-authentication each time a crab job is submitted. How can I by-pass that? At IIHE, modify the [GRID] section of error in your crab.cfg as follows: [GRID] dont_check_proxy = 1 Using CRAB, I got a "ASAP ERROR: Unable to ship a valid proxy to the server" When you do a "crab -submit", it tries to delegate proxy generation to the server, doing, for example: asap-user-register --server vocms58.cern.ch --myproxy In some case, when the ~/.glite/vomses is missing, it can give an error. The workaround is to create this file error in certificate with the correct information: mkdir ~/.glite cat $GLITE_LOCATION/etc/vomses/cms-voms.cern.ch.vo.ncm-vomsclient > ~/.glite/vomses It can also fail for other reasons, like a library missing (libgridsite.so.1.1 for example). Always have a look in the crab.log to get the precise cause of the failure. This problem will disappear with CRAB client release 2.7.x and CRAB server 1.1.x because it does not use ASAP anymore. Doing a "crab -create", I get the error "Unable to connect to myproxy.cern.ch" It means that CRAB has tried to create a proxy on myproxy.cern.ch, but it failed. The reason may be that our firewall (managed by the Computer Center team) has blocked the port. By default, myproxy-init takes the first port available in the range given by: echo $GLOBUS_TCP_PORT_RANGE The best solution is to change the minimum value of the range, doing, for example: export GLOBUS_TCP_PORT_RANGE="20036,25000" Notice that now, a script is doing it for you automatically, with a random minimum number, when you log on our user interfaces. So, you should not meet this problem anymore. Using CRAB, I got an error saying: crab: voms-proxy-info -identity failed with exit code 256=0(signal)+1(status) crab: /C=BE/O=BEGRID/OU=IIHE/OU=ULB/CN=Marcel Dupont crab: WARNING: Unable to verify signature! Server certificate possibly not installed.