Hi,
Sorry to bother you again, with a new question this time. Am I right in thinking that my postproc, and in particular pptransfer, needs to be updated since I last ran my suite (u-df570) last summer? I gather gridftp is no longer active, and we are using Globus to transfer to JASMIN instead? What do I need to change in order to do this? I’ve looked at a colleague’s suite who is already doing this (u-dm725), but that’s a GC5 suite so is different e.g. it has a “globus_cli” option under Data transfer, whereas my suite doesn’t have this.
Thank you,
Charlie
Charlie
Please see IMPORTANT: Retirement of JASMIN Gridftp server
That points to instructions on how to set up for globus online and how to modify a (standard-ish) suite.
Grenville
Thanks Grenville, but my goodness, they don’t make it easy, do they?
The bad news is that in following your instructions, I think I might have just killed ARCHER2.
I got to Step 5 of Configuring PPTransfer using Globus (having gone through everything else, including setting up the various filesystems), and successfully listed my ARCHER2 home directory doing
globus ls 3e90d018-0d05-461a-bbaf-aab605283d21:/~/.
But then when I repeated for the JASMIN endpoint, followed the instructions, and then tried to list home directory using
globus ls a2f53b7f-1b4e-4dce-9b7c-349ae760fee0:/~/
it generated a load of errors and then completely froze. I had to shut down the entire terminal, and now I can’t log back in again: it just times out:
eval $(ssh-agent -s)
ssh-add ~/.ssh/id_rsa_arch
ssh -Y -A cjrw09@login.archer2.ac.uk
Agent pid 19026
Enter passphrase for /home/bridge/cw18831/.ssh/id_rsa_arch:
Identity added: /home/bridge/cw18831/.ssh/id_rsa_arch (/home/bridge/cw18831/.ssh/id_rsa_arch)
ssh: connect to host login.archer2.ac.uk port 22: Connection timed out
What have I done this time?!
Charlie
Okay, we have now just received an email saying that ARCHER2 has gone down, so at least it’s not just a problem my end. But I still hope I wasn’t responsible for the failure, because it is awfully coincidental!
C
Hi,
So the good news is that I didn’t kill ARCHER2 yesterday, and also that the errors I received when checking the JASMIN endpoint (see message above) must have been related to the failure, because they have now disappeared.
So I have completed Step 1 of Updating UM Workflows.
I have, however, failed at the first section of Step 2, in that my suite (u-df570) does not use either of the postproc branches listed in the instructions. Therefore, as per those instructions, I am contacting you.
Thanks a lot,
Charlie
Hi Charlie,
Glad that worked ok when ARCHER2 came back.
In panel fcm_make_pp → Configuration change the revision number of the postproc_2.3_pptransfer_gridftp_nopw
branch from @4577
to @5411
.
Then add in the 3 globus_*
variables to the pptransfer namelist as per the instructions.
Cheers,
Ros.