Tags:
view all tags
<!-- 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 . ---++ T3 Linux Groups The T3 users are partitioned in the following Linux groups; the former primary group %GREEN%cms%ENDCOLOR% became now a secondary group to whom each user belongs to. * =ethz-ecal= | =ethz-bphys= | =ethz-ewk= | =ethz-higgs= | =ethz-susy= * =psi-bphys= | =psi-pixel= | =uniz-phys= * =uniz-higgs= | =uniz-pixel= The groups partitioning: * allows a faster and simpler understanding of the =/pnfs= space usage by leveraging on the =gid= setting: in the past having all the files assigned to the unique group =cms= made this kind of accounting very tricky in dCache. * allows to make accounting in the batch system also according to the =gid= setting. * allowed the creation of dedicated "group dirs" in =/pnfs= where just the group members can operate. * as a side effect, each new file written in =/shome=, =/pnfs=, =/scratch= or =/tmp= has a specific =gid=, as explained different from %GREEN%cms%ENDCOLOR%, and this specific =gid= prevents the accidental deletion of files by other groups. Following a user with his two groups: <pre> $ id auser uid=571(auser) gid=532(%BLUE%ethz-higgs%ENDCOLOR%) groups=532(%BLUE%ethz-higgs%ENDCOLOR%),500(%GREEN%cms%ENDCOLOR%) </pre> Following an output that points out how the =/pnfs= dirs are assigned according to the groups partitioning: <pre> $ ls -l /pnfs/psi.ch/cms/trivcat/store/user | grep -v cms total 56 drwxr-xr-x 2 alschmid %ORANGE%uniz-bphys%ENDCOLOR% 512 Feb 21 2013 alschmid drwxr-xr-x 5 amarini %RED%ethz-ewk%ENDCOLOR% 512 Nov 7 15:37 amarini drwxr-xr-x 18 andis %BROWN%ethz-bphys%ENDCOLOR% 512 Jan 5 2010 andis drwxr-xr-x 2 arizzi %BROWN%ethz-bphys%ENDCOLOR% 512 Sep 16 17:49 arizzi drwxr-xr-x 5 bean %TEAL%psi-bphys%ENDCOLOR% 512 Aug 24 2010 bean drwxr-xr-x 5 bianchi %BLUE%ethz-higgs%ENDCOLOR% 512 Sep 9 09:40 bianchi drwxr-xr-x 30 bmillanm %ORANGE%uniz-bphys%ENDCOLOR% 512 Jan 17 2012 bmillanm drwxr-xr-x 29 bortigno %BLUE%ethz-higgs%ENDCOLOR% 512 Apr 18 2013 bortigno drwxr-xr-x 98 buchmann %PURPLE%ethz-susy%ENDCOLOR% 512 Nov 5 20:36 buchmann ... </pre> This last output shows the "group dirs" mentioned before: <pre> $ ls -l /pnfs/psi.ch/cms/trivcat/store/t3groups/ total 5 drwxrwxr-x 2 root ethz-bphys 512 Nov 8 15:18 ethz-bphys drwxrwxr-x 2 root ethz-ecal 512 Nov 8 15:18 ethz-ecal drwxrwxr-x 2 root ethz-ewk 512 Nov 8 15:18 ethz-ewk drwxrwxr-x 2 root ethz-higgs 512 Nov 8 15:18 ethz-higgs drwxrwxr-x 2 root ethz-susy 512 Nov 8 15:18 ethz-susy drwxrwxr-x 2 root psi-bphys 512 Nov 8 15:18 psi-bphys drwxrwxr-x 2 root psi-pixel 512 Nov 8 15:18 psi-pixel drwxrwxr-x 2 root uniz-bphys 512 Nov 8 15:18 uniz-bphys drwxrwxr-x 2 root uniz-higgs 512 Nov 8 15:18 uniz-higgs drwxrwxr-x 2 root uniz-pixel 512 Nov 8 15:18 uniz-pixel </pre> *If your account hasn't a Linux group assigned please write us.* ---++ 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 into a =t3ui*= 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 by NX client]], which allows to work efficiently with graphical applications)<pre> ssh -Y username@t3ui02.psi.ch </pre> 1. *If you are an external user and you don't have a standard PSI account, you need to change your password* the first time you log in; 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> For details about how to extract those files from your CERN User Grid-Certificate please read [[https://gridca.cern.ch/gridca/Help/?kbid=024010]]. 1. 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. You have to complete the [[https://lcg-voms.cern.ch:8443/vo/cms/vomrs?path=/RootNode][CMS "Virtual Organization" subscription]] or the following command =voms-proxy-init -voms cms= won't work. [[https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideLcgAccess#How_to_register_in_the_CMS_VO][CERN details about that]]. 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.</br> 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 -n %BLUE%t3se01.psi.ch%ENDCOLOR% -p /pnfs/%BLUE%psi.ch%ENDCOLOR%/cms/testing -i "GSIDCAP-write SRMv1-adv-del SRMv1-adv-del1 SRMv1-write SRMv1-get-meta SRMv1-read SRMv1-adv-del2" Test directory: /tmp/dcachetest-20131118-1202-1970 TEST: GSIDCAP-write ...... [IGNORE] TEST: SRMv1-adv-del ...... [IGNORE] TEST: GFTP-write ...... [%GREEN%OK%ENDCOLOR%] TEST: GFTP-ls ...... [%GREEN%OK%ENDCOLOR%] TEST: GFTP-read ...... [%GREEN%OK%ENDCOLOR%] TEST: DCAP-read ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv1-adv-del1 ...... [IGNORE] TEST: SRMv1-write ...... [IGNORE] TEST: SRMv1-get-meta ...... [IGNORE] TEST: SRMv1-read ...... [IGNORE] TEST: SRMv1-adv-del2 ...... [IGNORE] TEST: SRMv2-write ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-ls ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-read ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-rm ...... [%GREEN%OK%ENDCOLOR%] </pre> 1. Note: The =test-dCacheProtocols= tool can also be used to test a *remote* element access (use the =-h= flag to get more info about it): e.g. to test CSCS:<pre> $ test-dCacheProtocols -n %BLUE%storage01.lcg.cscs.ch%ENDCOLOR% -p /pnfs/%BLUE%lcg.cscs.ch%ENDCOLOR%/cms/testing -i "GSIDCAP-write %BLUE%DCAP-read%ENDCOLOR% SRMv1-adv-del SRMv1-adv-del1 SRMv1-write SRMv1-get-meta SRMv1-read SRMv1-adv-del2" Test directory: /tmp/dcachetest-20131118-1201-1784 TEST: GSIDCAP-write ...... [IGNORE] TEST: SRMv1-adv-del ...... [IGNORE] TEST: GFTP-write ...... [%GREEN%OK%ENDCOLOR%] TEST: GFTP-ls ...... [%GREEN%OK%ENDCOLOR%] TEST: GFTP-read ...... [%GREEN%OK%ENDCOLOR%] TEST: DCAP-read ...... [IGNORE] TEST: SRMv1-adv-del1 ...... [IGNORE] TEST: SRMv1-write ...... [IGNORE] TEST: SRMv1-get-meta ...... [IGNORE] TEST: SRMv1-read ...... [IGNORE] TEST: SRMv1-adv-del2 ...... [IGNORE] TEST: SRMv2-write ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-ls ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-read ...... [%GREEN%OK%ENDCOLOR%] TEST: SRMv2-rm ...... [%GREEN%OK%ENDCOLOR%] </pre> ---+++ 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
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r80
|
r24
<
r23
<
r22
<
r21
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r22 - 2014-02-19
-
FabioMartinelli
CmsTier3
Log In
CmsTier3 Web
Create New Topic
Index
Search
Changes
Notifications
Statistics
Preferences
User Pages
Main Page
Policies
Monitoring Storage Space
Monitoring Slurm Usage
Physics Groups
Steering Board Meetings
Admin Pages
AdminArea
Cluster Specs
Home
Site map
CmsTier3 web
LCGTier2 web
PhaseC web
Main web
Sandbox web
TWiki web
CmsTier3 Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
Edit
Attach
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