#2340 closed help (fixed)

[FAIL] No hosts selected message when attempting to run a UM10.9 suite

Reported by: MJohnston1 Owned by: um_support
Component: Rose/Cylc Keywords: fail, ssh, UM10.9,
Cc: Platform: ARCHER
UM Version: 10.9


I've copied a working suite (u-at174) as u-at255 (a BOMEX-LES suite in UM10.9 with branches that allow idealised subsidence and a time/height varying geostrophic forcing). I've changed the HPC_USER to 'xb899100' to match my Archer account username.

When I attempt to run this suite from the rose gui, it fails with the error message:

RosePopenError: bash -ec H=$(rose\ host-select\ archer);\ echo\ $H # return-code=1, sterr=
[WARN] login8.archer.ac.uk: (ssh failed)
[WARN] login4.archer.ac.uk: (ssh failed)
[WARN] login1.archer.ac.uk: (ssh failed)
[WARN] login7.archer.ac.uk: (ssh failed)
[WARN] login3.archer.ac.uk: (ssh failed)
[WARN] login.archer.ac.uk: (ssh failed)
[WARN] login6.archer.ac.uk: (ssh failed)
[WARN] login2.archer.ac.uk: (ssh failed)
[WARN] login5.archer.ac.uk: (ssh failed)
[FAIL] No hosts selected.

The log on this message says:

[INFO] 2017-12-12T16:10:33+0000 chdir: /home/MJohnston1/roses/u-at255/
[INFO] 2017-12-12T16:10:33+0000 Configuration: /home/MJohnston1/roses/u-at255/
[INFO] 2017-12-12T16:10:33+0000     file: rose-suite.conf
[INFO] 2017-12-12T16:10:33+0000 create: log.20171212T161033Z
[INFO] 2017-12-12T16:10:33+0000 delete: log
[INFO] 2017-12-12T16:10:33+0000 symlink: log.20171212T161033Z <= log
[INFO] 2017-12-12T16:10:33+0000 tar -czf log.20171212T155906Z.tar.gz log.20171212T155906Z
[INFO] 2017-12-12T16:10:33+0000 log.20171212T155906Z.tar.gz <= log.20171212T155906Z
[INFO] 2017-12-12T16:10:33+0000 delete: log.20171212T155906Z/
[INFO] 2017-12-12T16:10:33+0000 create: log/suite
[INFO] 2017-12-12T16:10:33+0000 create: log/rose-conf
[INFO] 2017-12-12T16:10:33+0000 svn info --non-interactive
[INFO] 2017-12-12T16:10:33+0000 svn status --non-interactive
[INFO] 2017-12-12T16:10:34+0000 svn diff --internal-diff --non-interactive
[INFO] 2017-12-12T16:10:34+0000 git describe
[INFO] 2017-12-12T16:10:34+0000 symlink: rose-conf/20171212T161033-run.conf <= log/rose-suite-run.conf
[INFO] 2017-12-12T16:10:34+0000 symlink: rose-conf/20171212T161033-run.version <= log/rose-suite-run.version
[INFO] 2017-12-12T16:10:34+0000 export CYLC_VERSION=6.11.4
[INFO] 2017-12-12T16:10:34+0000 export ROSE_ORIG_HOST=puma
[INFO] 2017-12-12T16:10:34+0000 export ROSE_VERSION=2016.11.1
[INFO] 2017-12-12T16:10:34+0000 unchanged: app
[INFO] 2017-12-12T16:10:34+0000     source: /home/MJohnston1/roses/u-at255/app
[INFO] 2017-12-12T16:10:34+0000 unchanged: bin
[INFO] 2017-12-12T16:10:34+0000     source: /home/MJohnston1/roses/u-at255/bin
[INFO] 2017-12-12T16:10:34+0000 unchanged: meta
[INFO] 2017-12-12T16:10:34+0000     source: /home/MJohnston1/roses/u-at255/meta
[INFO] 2017-12-12T16:10:34+0000 unchanged: rose-suite.info
[INFO] 2017-12-12T16:10:34+0000     source: /home/MJohnston1/roses/u-at255/rose-suite.info
[INFO] 2017-12-12T16:10:34+0000 delete: suite.rc
[INFO] 2017-12-12T16:10:34+0000 install: suite.rc

I suspect this may have something to do with the branches used for some of the idealised forcing, but I'm not sure what to do from here.

Best Regards,

Change History (2)

comment:1 Changed 18 months ago by annette

  • Component changed from UM Model to Rose/Cylc

Hi Michael,

Try following these instructions here: http://cms.ncas.ac.uk/wiki/RoseCylc/Hints#Settinguprosehost-selectarcher

The rose host-select archer in the suite.rc file command requires some setup on PUMA in order to work.


comment:2 Changed 18 months ago by MJohnston1

  • Resolution set to fixed
  • Status changed from new to closed

Thanks Annette,

That was indeed the problem - solved!


Note: See TracTickets for help on using tickets.