<!-- keep this as a security measure: #uncomment if the subject should only be modifiable by the listed groups # * Set ALLOWTOPICCHANGE = Main.TWikiAdminGroup,Main.CMSAdminGroup # * Set ALLOWTOPICRENAME = Main.TWikiAdminGroup,Main.CMSAdminGroup #uncomment this if you want the page only be viewable by the listed groups # * Set ALLOWTOPICVIEW = Main.TWikiAdminGroup,Main.CMSAdminGroup,Main.CMSAdminReaderGroup --> ---+ !!How to access, set up, and test your account %TOC% ---++ Preliminary steps All the documentation is maintained in the T3 twiki pages: https://wiki.chipp.ch/twiki/bin/view/CmsTier3/WebHome . Please take a look at it to explore T3's capabilities. Information about T3 mailing-lists: * *Please subscribe to the cms-tier3-users* list using [[https://lists.web.psi.ch/mailman/listinfo/cms-tier3-users][this web interface]] ([[https://lists.web.psi.ch/pipermail/cms-tier3-users/][list archives]]): cms-tier3-users@lists.psi.ch. This mailing-list is used to communicate information on Tier-3 matters (downtimes, etc.) or for discussions among users and admins, * To contact the CMS Tier-3 administrators alone, write to: cms-tier3@lists.psi.ch * *NOTE:* Both lists are read by the administrators and are archived. You can submit support requests to either of them. Mails to the user list have the added advantage that they can be read by everyone. Please also take a look at our policies about usage, quotas etc.. here: Tier3Policies . ---++ Basic setup We offer the following user interfaces. Please note that there is a convention on which users should access which UIs. %INCLUDE{"Tier3Policies" section="UisPerGroup"}% 1. Try to log in to the User Interface machine (=-Y= or =-X= flag for working with X applications. You can also try to [[https://wiki.chipp.ch/twiki/bin/view/CmsTier3/UserNxClientInstallation][connect with NX client]], which allows an to work efficiently with graphical applications)<pre> ssh -Y username@t3ui02.psi.ch </pre> 1. *If you are an external user and do not have a standard PSI account, you need to change your password* the first time you log in. Please use the standard =passwd= utility. 1. Copy your grid credentials to the standard places, i.e. to =~/.globus/userkey.pem= and =~/.globus/usercert.pem= and make sure that the permissions are set correctly like in this output: <pre> -rw-r--r-- 1 feichtinger cms 2961 Mar 17 2008 usercert.pem -rw------- 1 feichtinger cms 1917 Mar 17 2008 userkey.pem </pre> 1. %N% source a grid environment <pre> source /swshare/psit3/etc/profile.d/cms_ui_env.sh # for bash source /swshare/psit3/etc/profile.d/cms_ui_env.csh # for tcsh </pre> 1. Try to create a proxy certificate for CMS <pre> voms-proxy-init -voms cms </pre> %GREEN%If this fails, run the command with an additional =-debug= flag, and the error message will usually be sufficient for us to point out the problem. Make sure that your certificate is signed up with CMS as in [[https://twiki.cscs.ch/twiki/bin/view/LCGTier2/CMSInfoPagesUsers#How_can_I_get_access_Authenticat][these instructions from our Tier-2 wiki]].%ENDCOLOR% 1. Test your access to the PSI Storage element with the =test-dCacheProtocols= command. You should see output like this (no failed tests): <pre> $> test-dCacheProtocols Test directory: /tmp/dcachetest-20081105-1632-8387 TEST: GSIDCAP-write ...... [IGNORE] TEST: SRMv1-adv-del ...... [SKIPPED] (dependencies did not run: GSIDCAP-write) TEST: GFTP-write ...... [OK] TEST: GFTP-ls ...... [OK] TEST: GFTP-read ...... [OK] TEST: DCAP-read ...... [OK] TEST: SRMv1-adv-del1 ...... [OK] TEST: SRMv1-write ...... [OK] TEST: SRMv1-get-meta ...... [OK] TEST: SRMv1-read ...... [OK] TEST: SRMv1-adv-del2 ...... [OK] TEST: SRMv2-write ...... [OK] TEST: SRMv2-ls ...... [OK] TEST: SRMv2-read ...... [OK] TEST: SRMv2-rm ...... [OK] </pre> Note: This tool can also be used to test remote element access (use the =-h= flag to get information on it) ---+++ Changing your login shell If later you need to change your default login shell then please ask that to the t3 admin list. ---++ AFS CERN Ticket You should use the following sequence of commands at T3: <pre> kinit ${Your_CERN_Username}@CERN.CH aklog cern.ch </pre> The first command gets you a kerberos ticket, the second command uses that ticket to obtain an authentication token from CERN's AFS service -- Main.DerekFeichtinger - 05 Nov 2008
This topic: CmsTier3
>
WebHome
>
HowToSetupYourAccount
Topic revision: r15 - 2012-10-06 - FabioMartinelli
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback