Frequently Asked Questions (FAQs)
Here you can find answers to some of the most frequently asked questions.
If you have a question not answered in these pages, please contact us via the Helpdesk.
Details about automatic resubmission are described in the article Docs/AutomaticResubmission.
See the article Faq/ConvertMonsoonJobToArcher
Often when you set a model running, it only runs for a certain length of simulation time (say a year), and then halts - even when you've set the run length to be longer. This is to allow you to check everything is running OK, and in UM parlance is known as an initial or new run (NRUN).
Once done, you can now proceed with a continuation run (CRUN), and the model should now start from the end of the first run to completion. Instructions for submitting the continuation run can be found here. This page also contains information on setting up the initial run and resubmission period here.
See the article Archer/NercArchiving
Note: Not all versions are available on every platform.
Please email Grenville, g.m.s.lister @ reading.ac.uk , to request a ARCHER account.
There are currently two disk space areas on ARCHER.
- HOME space
This disk space is backed up by ARCHER so NCAS has limited space, an NCAS user allocation is therefore relatively small.
- WORK space
This disk space is NOT backed up and is the only disk space accessible by ARCHER batch jobs. NCAS has a large allocation and so an NCAS user allocation can be relatively large, up to a few Tbytes.
There is no specific scratch filesystem, and /tmp is not accessible by users from jobs running on the compute nodes. Thus users who desire a temporary scratch directory should set the environment variable $TMPDIR to point to a valid directory within their account on the work filesystem.
Normally your ssh agent persists even when you log out of puma. However, from time to time it can vanish.
If you are prompted for your passphrase, this means the ssh agent has stopped for some reason. The agent should have been re-initialised when you logged into puma, but you will need to re-associate your ssh keys to the agent.
To do so, run the following command:
If you have forgotten your passphrase you will need to regenerate your ssh keys. Before doing so, you will need to tidy up the old keys otherwise the ssh agent can get itself confused.
Go to your ~/.ssh directory, and look at the files, you should see something like:
puma$ ls ~/.ssh environment.puma id_rsa id_rsa.pub known_hosts ssh-setup
Delete the public and private keys. These will normally be named id_rsa and id_rsa.pub, or id_dsa and id_dsa.pub.
You should also delete the environment.puma file.
Next check if you have an agent running:
puma$ ps -flu <puma-username> | grep ssh-agent
If an agent is running, one or more lines like the following will be returned:
15658 ? 00:00:00 ssh-agent
The number in the first column is the process-id, pass this to the kill command to stop the process, for example:
puma$ kill -9 15658
This is because your ssh-agent has stopped running for some reason and is unable to restart automatically. Try removing the following file on PUMA:
puma$ rm ~/.ssh/environment.puma
Then log out of PUMA and back in again. You should then see a message similar to:
Initialising new SSH agent...
And you should then be able to run ssh-add successfully.