UKESM1.1 AMIP run -- u-dp730

(post deleted by author)

Hi Simon,

In postproc -> post processing select Archer for the archive_command
and then
transfer_dir under postproc -> postprocessing -> JASMIN Transfer is where you want the data to go on JASMIN.

Cheers,
Ros.

Thanks Ros,
did all that and rerun workflow – cylc vip. Now getting a failure from fcm_make_um
[FAIL] ln04:cylc-run/u-dr157/run2/share/fcm_make_um: cannot create mirror target
make extract has worked…

Simon

Hi Simon,

Please retrigger the fcm_make_um task. It tried to use ln04 - see Grenville’s previous comment above.

Cheers,
Ros

Hi Ros,
Thanks and it worked this time.

Is there a way of having fcm_make_um try different login nodes if the first one it tried did not work? I guess I could add some cylc retry options, but that would retry (repeatedly) if there was a failure due to messing up the build… Presumably the mirror step is copying stuff from puma to archer2.

Simon

Hi Simon,

Cylc automatically tries each of the 4 login nodes until it finds one it can connect to. Unfortunately at the moment login node 4 is alive and contactable but is only allowing those users with access to test the new os upgrade on.

Yes you can add retries to a task but it can’t diagnose when and when not to retry. If the task fails it will retry whatever the reason.

Cheers,
Ros

Ok – annoying! I guess cylc needs a does node exist and are allowed to logon test :slight_smile:
Simon

Hi Ros,

And pptransfer failed :frowning:
Looks like I need to authenticate… But I thought I did that yesterday when I set up globus and the keys are good for 30 days… See /home/n02/n02/tetts/cylc-run/u-dr157/run2/log/job/19790101T0000Z/pptransfer/01/job.err [You should have read permission for all my files..]

[SUBPROCESS]: Error = 4:

  • The resource you are trying to access requires you to re-authenticate.*
    message: Missing required data_access consent

Please use “globus session update” to re-authenticate with specific identities.

Do I need to make sure the new globus-cli module is loaded ~(module load globus-cli/3.35.2)? I don’t see any obvious way of doing that for my suite. Or pay attention to the short-lived credentials stuff…

Simon