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: * *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, outages, news, etc.) or for discussions among users and admins. * To privately contact the CMS Tier-3 administrators, 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 usages, quotas, etc.. Tier3Policies. ---++ T3 Linux Groups All the T3 users are partitioned in several primary groups and the users also belong to the secondary group %GREEN%cms%ENDCOLOR% that's used for common files like the CMS files uploaded at T3 by [[https://cmsweb.cern.ch/phedex/][PhEDEx]]: | *ETHZ* | *UniZ* | *PSI* | | =%ORANGE%ethz-ecal%ENDCOLOR%= | =uniz-higgs= | =%TEAL%psi-bphys%ENDCOLOR%= | | =%BROWN%ethz-bphys%ENDCOLOR%= | =%BLUE%uniz-pixel%ENDCOLOR%= | =%PURPLE%psi-pixel%ENDCOLOR%= | | =%RED%ethz-ewk%ENDCOLOR%= | =%ORANGE%uniz-bphys%ENDCOLOR%= | | | =%BLUE%ethz-higgs%ENDCOLOR%= | | | | =%PURPLE%ethz-susy%ENDCOLOR%= | | | The T3 Linux Groups: * allow a faster and simpler understanding of the =/pnfs= space usage by leveraging on the =gid= setting. * allow to make accounting in the Sun Grid Engine batch system also according to the =gid= setting. * made possible the creation of the "group dirs" =/pnfs/psi.ch/cms/trivcat/store/t3groups/= where just the group members can write or delete. * simplify the =/shome=, =/pnfs=, =/scratch= and =/tmp= space usage accounting. Following an ETHZ user with his %BLUE%primary%ENDCOLOR% and his %GREEN%secondary%ENDCOLOR% group: <pre> $ id auser uid=571(auser) gid=532(%BLUE%ethz-higgs%ENDCOLOR%) groups=532(%BLUE%ethz-higgs%ENDCOLOR%),500(%GREEN%cms%ENDCOLOR%) </pre> Following the users dirs =/pnfs/psi.ch/cms/trivcat/store/user/= : <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 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 98 buchmann %PURPLE%ethz-susy%ENDCOLOR% 512 Nov 5 20:36 buchmann ... </pre> Following the "group dirs" =/pnfs/psi.ch/cms/trivcat/store/t3groups/= ; since they're "group dirs" there is not a real owner so they belong to the =root= user and the group has the =w= permission: <pre> $ ls -l /pnfs/psi.ch/cms/trivcat/store/t3groups/ total 5 drwxrwxr-x 2 root ethz-bphys 512 Nov 8 15:18 %BROWN%ethz-bphys%ENDCOLOR% drwxrwxr-x 2 root ethz-ecal 512 Nov 8 15:18 %ORANGE%ethz-ecal%ENDCOLOR% drwxrwxr-x 2 root ethz-ewk 512 Nov 8 15:18 %RED%ethz-ewk%ENDCOLOR% drwxrwxr-x 2 root ethz-higgs 512 Nov 8 15:18 %BLUE%ethz-higgs%ENDCOLOR% drwxrwxr-x 2 root ethz-susy 512 Nov 8 15:18 %PURPLE%ethz-susy%ENDCOLOR% drwxrwxr-x 2 root psi-bphys 512 Nov 8 15:18 %TEAL%psi-bphys%ENDCOLOR% drwxrwxr-x 2 root psi-pixel 512 Nov 8 15:18 %PURPLE%psi-pixel%ENDCOLOR% drwxrwxr-x 2 root uniz-bphys 512 Nov 8 15:18 %ORANGE%uniz-bphys%ENDCOLOR% drwxrwxr-x 2 root uniz-higgs 512 Nov 8 15:18 uniz-higgs drwxrwxr-x 2 root uniz-pixel 512 Nov 8 15:18 %BLUE%uniz-pixel%ENDCOLOR% </pre> ---++ Basic setup We offer the following SL6 user interfaces ( UIs ) : %INCLUDE{"Tier3Policies" section="UisPerGroup"}% 1. Login into a =t3ui1*= machine by =ssh= ; use =-Y= or =-X= flag for working with X applications; you might also try to [[UserNxClientInstallation][connect by NX client]], which allows to work efficiently with graphical applications<pre> ssh -Y username@t3ui12.psi.ch </pre> 1. *If you are an external user and you don't have a standard PSI account, you'll have to change your initial 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 their files permissions are set correctly: <pre> -rw-r--r-- 1 feichtinger cms 2961 Mar 17 2008 usercert.pem -r-------- 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 the grid environment associated to your login shell: <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]], e.g. who is your representative. 1. Create a proxy certificate for CMS by: <pre> voms-proxy-init -voms cms </pre> %GREEN%If that fails, run the command with an additional =-debug= flag, and the error message will usually be sufficient for the T3 Admins to point out the problem.</br> 1. Test your access to the PSI Storage element with the =test-dCacheProtocols= command. You should see an output like this (without any failed test): <pre> $ test-dCacheProtocols Test directory: /tmp/dcachetest-20150115-1328-23031 TEST: GFTP-write ...... [OK] TEST: GFTP-ls ...... [OK] TEST: GFTP-read ...... [OK] TEST: DCAP-read ...... [OK] TEST: SRMv2-write ...... [OK] TEST: SRMv2-ls ...... [OK] TEST: SRMv2-read ...... [OK] TEST: SRMv2-rm ...... [OK] </pre> 1. [[https://wiki.chipp.ch/twiki/bin/view/LCGTier2/CMSInfoPagesUsers][Be aware of the external CSCS CMS User Page]] 1. The =test-dCacheProtocols= tool can also be used to test a *remote* storage element (use the =-h= flag to get more info about it): e.g. to test the CSCS storage element:<pre> $ test-dCacheProtocols -n %BLUE%storage01.lcg.cscs.ch%ENDCOLOR% -p /pnfs/lcg.cscs.ch/cms/trivcat/store/user/YOUR_CMS_ACCOUNT -i "DCAP-read" Test directory: /tmp/dcachetest-20150115-1333-23178 TEST: GFTP-write ...... [OK] TEST: GFTP-ls ...... [OK] TEST: GFTP-read ...... [OK] TEST: DCAP-read ...... [IGNORE] TEST: SRMv2-write ...... [OK] TEST: SRMv2-ls ...... [OK] TEST: SRMv2-read ...... [OK] TEST: SRMv2-rm ...... [OK] </pre> It's possible to get changed your login shell, e.g. from =bash= to =tcsh=, your group, also your account name ; often users requested to change their =Grid cert subject:=, e.g. because they were moving from a country to an other where they got a new certificate. ---++ AFS CERN Ticket In order to access the CERN =/afs= protected dirs ( e.g. your home ) : <pre> kinit ${Your_CERN_Username}@CERN.CH aklog cern.ch </pre> The first command gives you a kerberos ticket, the second command uses that ticket to obtain an authentication token from CERN's AFS service ---++ t3ui1* SSH pub keys Hackers on Internet are constantly waiting for user mistakes, even just a misspelled %RED%letter%ENDCOLOR% like in this example: <pre> $ ssh t3ui02.psi.%RED%s%ENDCOLOR%h The authenticity of host 't3ui02.psi.%RED%s%ENDCOLOR%h (62.210.217.195)' can't be established. RSA key fingerprint is c0:c5:af:36:4b:2d:1f:88:0d:f3:9c:08:cc:87:df:42. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 't3ui02.psi.%RED%s%ENDCOLOR%h,62.210.217.195' (RSA) to the list of known hosts. at3user@t3ui02.psi.%RED%s%ENDCOLOR%h's %RED%password%ENDCOLOR%: </pre> %RED%The T3 Admins can't prevent a T3 user from confusing =.ch= with a =.sh= so pay attention to these cases ! %ENDCOLOR% To avoid to digit the T3 hostnames you might define these permanent aliases instead : </br> %TWISTY% <pre> $ grep alias ~/.bash_profile | grep t3ui alias ui12='ssh -X at3user@t3ui12.psi.ch' alias ui15='ssh -X at3user@t3ui15.psi.ch' alias ui16='ssh -X at3user@t3ui16.psi.ch' alias ui17='ssh -X at3user@t3ui17.psi.ch' alias ui18='ssh -X at3user@t3ui18.psi.ch' alias ui19='ssh -X at3user@t3ui19.psi.ch' </pre> %ENDTWISTY% </br></br> More subdole attacks are the [[http://www.vandyke.com/solutions/ssh_overview/ssh_overview_threats.html][SSH man in the middle attacks]] ; to detect them you have to register in =/$HOME/.ssh/known_hosts= each =t3ui1*= SSH RSA public key by running these steps on each laptop/desktop/server ( also =lxplus= ! ) that you're going use to login at T3: <pre> cp -p /$HOME/.ssh/known_hosts /$HOME/.ssh/known_hosts.`date +"%d-%m-%Y"` mkdir /tmp/t3ssh/ for X in 19 18 17 16 15 12 ; do TMPFILE=`mktemp /tmp/t3ssh/XXXXXX` && ssh-keyscan -t rsa t3ui$X.psi.ch,t3ui$X,`host t3ui$X.psi.ch| awk '{ print $4}'` | cat - /$HOME/.ssh/known_hosts | grep -v 'psi\.sh' > $TMPFILE && mv $TMPFILE /$HOME/.ssh/known_hosts ; done rm -rf /tmp/t3ssh for X in 12 15 16 17 18 19 ; do echo -n "# entries for t3ui$X = " ; grep -c t3ui$X /$HOME/.ssh/known_hosts ; grep -Hn --color t3ui$X /$HOME/.ssh/known_hosts ; echo ; done echo done </pre> last =for= reports if there are duplicated rows in =/$HOME/.ssh/known_hosts= for a =t3ui1*= server ; if there are you're suppose to preserve the correct occurrence and delete the others ; to delete you can use =sed -i= or by hands by =vim= or =emacs= ; once you'll get just one row per =t3ui1*= server run this command and carefully compare your output with this output: </br> %TWISTY% <pre> $ ssh-keygen -l -f /$HOME/.ssh/known_hosts | grep t3ui </pre> | 2048 | d0:9c:a0:e9:8f:9c:3f:b2:f1:88:6c:15:32:07:fc:a0 | t3ui12.psi.ch,t3ui12,192.33.123.132 (RSA) | | 2048 | 77:1b:27:5e:c8:74:64:86:f8:50:f6:58:e6:6f:41:65 | t3ui15.psi.ch,t3ui15,192.33.123.135 (RSA) | | 2048 | 35:bb:d6:be:64:86:8d:db:1d:57:43:ef:05:39:72:c8 | t3ui16.psi.ch,t3ui16,192.33.123.136 (RSA) | | 2048 | 27:d1:57:f0:ac:da:1d:db:54:11:5c:46:4d:93:63:59 | t3ui17.psi.ch,t3ui17,192.33.123.137 (RSA) | | 2048 | b1:56:06:5b:d3:da:1a:79:60:e9:02:16:be:82:fe:f7 | t3ui18.psi.ch,t3ui18,192.33.123.138 (RSA) | | 2048 | 73:fe:97:b2:e7:54:df:99:50:dc:19:3d:6f:cd:01:11 | t3ui19.psi.ch,t3ui19,192.33.123.139 (RSA) | %ENDTWISTY% </br></br> force your ssh client to always check if the server you're connecting to is already mentioned in the =/$HOME/.ssh/known_hosts= file and to request your consensus for servers that are absent by adding this line in =/$HOME/.ssh/config= : <pre> StrictHostKeychecking %GREEN%ask%ENDCOLOR% </pre> your =/$HOME/.ssh/config= can be more complex than just that line, study the [[http://linux.die.net/man/5/ssh_config][ssh_config man page]] or contact the T3 Admins; ideally you should put =StrictHostKeychecking %GREEN%yes%ENDCOLOR%= but in real life that's impractical. now your ssh client will be able to detect the [[http://www.vandyke.com/solutions/ssh_overview/ssh_overview_threats.html][SSH man in the middle attacks]] and if so it will report : <pre> WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. </pre> The =t3ui1*= SSH RSA public and private keys will be *never* changed, so the case =It is also possible that the RSA host key has just been changed= will be *never* true. ---++ Primary T3 Admin Skype Account %N% Both to help you with your T3/T2 errors or misunderstandings and to interactively support your next 'what-if' T3/T2 plans there is a dedicated Skype account to video talk, interactively copy/paste your crashes/logs/links or share your screen furthermore feel free to invite the Primary T3 Admin ( so far is Fabio Martinelli ) to any future phone call or meeting focused on the T3/T2 CMS computing the Skype account is : =fabio.martinelli_2= each T3 user, not only the Institutes representatives, can add him as a contact ; the account will be active during the usual working hours for all the other ordinary cases the =cms-tier3@lists.psi.ch= remains the usual 1st line of support ---++ VOMS Group =/cms/chcms= %N% So far the T3 is not treating differently the CMS VOMS 'Swiss' group =/cms/chcms= but this might change in the next future, so [[https://voms2.cern.ch:8443/voms/cms/group/edit.action?groupId=5][ask for the =/cms/chcms= membership]] ; conversely the T2 located at CSCS Lugano already treats differently the =/cms/chcms= members by both raising their Jobs priorities and providing additional =/pnfs= space ; so it's worth to be a member ; by running the usual =voms-proxy-init --voms cms= you'll automatically get the =/cms/chcms= attribute.
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r80
|
r39
<
r38
<
r37
<
r36
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r37 - 2015-03-10
-
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