Hi there, I attempted to submit a newly copied job but was unsuccessful. The error message is shown in the attached screenshot. It seems the copied job was not stored correctly (but I am unsure), and despite waiting a long time before running it, I still received the same error message. Could you please review it and let me know what went wrong? Thanks. The new job I am working on is u-dt963.
Best,
Xin
Xin
Please search the help desk - this error has arisen previously and the solution provided.
Grenville
Hi Grenville,
Thanks for pointing this out. Yes, I found my previously raised question, which is similar to this one. I then followed the solutions given before, by: “fcm commit u-dr592” before “rosie copy” it to get a new suite, which is u-dt967. I manually added the missing files in the “rose-suite.conf” for AINITIAL_FILE and ARCHER2_AINITIAL_DIR, and did “fcm commit” before running the suite. However, the submission still failed with the same error message, which is strange. Please help.
Cheers,
Xin
Hi Xin,
Search all the helpdesk tickets not just your own queries.
https://cms-helpdesk.ncas.ac.uk/t/archer2-restart-ssh-fail/1805
Cheers,
Ros
Hi Ros,
After I “ssh-add my ARCHER2 key” on puma2 to my ssh-agent, I can successfully submit jobs. This is via the following steps:
On PUMA2 you can list all your SSH keys by running:
ls ~/.ssh/
Look for a private key file it’s usually named something like id_rsa_archer2
(or whatever name you chose when you created it).
Once you’ve found it, you can add it with
ssh-add ~/.ssh/yourkeyname
You can also check which keys are currently loaded with this:
ssh-add -l
Cheers,
Xin
