Test ssh access
On your local UNIX system where ssh client software is installed, make sure that your ssh private key is correctly installed in ~/.ssh directory. List of ~/.ssh directory should show both public and private key files. For example:
$ ls -l ~/.ssh … -rw------- 1 cindy cindy 951 Mar 7 2007 id_rsa -rw-r--r-- 1 cindy cindy 234 Mar 7 2007 id_rsa.pub …
(Make sure that you have a backup copy of these files.) To test ssh, run
$ ssh <username>@<remote-hostname>
You should be prompted for a passphrase. Enter the passphrase you used to create the ssh key and this should enable you to login.
(After you login, if the remote system is a Rocks cluster, as a new user on your first login, you maybe asked to create a ssh key. This ssh key should only be used internally within the cluster. For simplicity, hit the return key 3 times to accept the default location for .ssh key files and to create the passphrase with empty strings.)
If you failed ssh login, then run
$ ssh –v <username>@<remote-hostname>
And email the output to the site administrator. (See site page to find site contact information)
Test Globus access
Globus WS requires different test from Pre-WS services. Most PRAGMA grid sites are running both. Some sites are running only one. To find out which service(s) each site is running, see http://goc.pragma-grid.net/pragma-doc/computegrid.html.
For either pre-WS or WS tests, logon to a local UNIX system where Globus client software is installed, make sure that your Globus user certificate and key files are correctly installed in ~/.globus directory. List of ~/.globus directory should show the certificate and key files. For example:
$ ls -l ~/.globus … -r-------- 1 cindy cindy 4998 Jan 25 2007 usercert.pem -r-------- 1 cindy cindy 1743 Jan 25 2007 userkey.pem
(Make sure that you have a backup copy of these files.)
To create a proxy, run
It will prompt you for your “GRID pass phrase”. Enter the passphrase you used when you requested your Globus user certificate. If successful, it will return “Creating proxy ... Done”.
Now you are ready to test Globus access to a remote system.
If the remote system is running Pre-WS service, run
$ globusrun -a –r <remote-hostname>
If successful, it will return “GRAM Authentication test successful”.
If any problems, please email all the output from the above commands to the site administrator. (See site page to find site contact information)
If the Globus access tests are successful, you can test job submission by running
$ globus-job-run <remote-hostname>/jobmanager-<type> /bin/date
If the job manager is sge, then it should be jobmanager-sge. You can find the jobmanager type for each site/cluster at http://goc.pragma-grid.net/pragma-doc/computegrid.html.
Depending how busy the remote host is (you can check by ssh login to the host and run “qstat –f”), you may need to wait until the job get its turn to execute. Then it should return the current date. (On SDSC Rocks systems, you may ignore warning messages in this output, as long as it returns the current date, the job submission is successful.)
If the job submission fails, please email the output to the site administrator. (See site page to find site contact information).
If the remote system is running WS service, run
$ globusrun-ws -submit -F <target-system-FQDN>:<port#> -c /bin/hostname $ globusrun-ws -submit -factory <target-system-FQDN>:<port#> -Ft SGE -J -S -s -c /bin/hostname