Opened 3 months ago

Closed 8 weeks ago

#2865 closed help (fixed)

Difficulty submitting a UKCA run

Reported by: anmcr Owned by: ros
Component: Rose/Cylc Keywords: ssh
Cc: Platform: ARCHER
UM Version: 11.2

Description

Hello,

I want to run a recent version of the UKCA model. I made a copy of u-be045 (vn11.2, running on ARCHER, taken from http://www.ukca.ac.uk/wiki/index.php/GA7.1_StratTrop_suites). This is u-bh705. However, when I try to submit it on the command line I get the error:

anmcr@puma:/home/anmcr/cylc-run/u-bh705> rose suite-run
[FAIL] /home/anmcr/cylc-run/u-bh705: rose-suite.conf not found.

And when i try to submit it via CYLC/ROSE I get the error: 'return-code=255, stderr= [FAIL] Host key verification failed'.

I searched the NCAS CMS tickets, and the UKCA tutorial, for help but wasn't able to resolve the issue. I would be greatful for any suggestions.

Many thanks,

Andrew

Change History (10)

comment:1 Changed 3 months ago by ros

Hi Andrew,

The transcript you included shows you running rose suite-run from within the ~/cylc-run directory for the suite which won't work; make sure you are in ~/roses/u-bh705 directory and try again.

Cheers,
Ros.

comment:2 Changed 3 months ago by anmcr

Hello,

Sorry, when I submit on the command line I get the error:

anmcr@puma:/home/anmcr/roses/u-bh705> rose suite-run
[INFO] create: log.20190409T210303Z
[INFO] delete: log
[INFO] symlink: log.20190409T210303Z ⇐ log
[INFO] log.20190409T160218Z.tar.gz ⇐ log.20190409T160218Z
[INFO] delete: log.20190409T160218Z/
[INFO] create: log/suite
[INFO] create: log/rose-conf
[INFO] symlink: rose-conf/20190409T220303-run.conf ⇐ log/rose-suite-run.conf
[INFO] symlink: rose-conf/20190409T220303-run.version ⇐ log/rose-suite-run.version
[INFO] export CYLC_VERSION=6.11.4
[INFO] export ROSE_ORIG_HOST=puma
[INFO] export ROSE_VERSION=2016.11.1
[INFO] install: ana
[INFO] source: /home/anmcr/roses/u-bh705/ana
[INFO] WARNING: deprecated items were automatically upgraded in 'suite definition':
[INFO] * (6.0.0) [scheduling][special tasks][sequential] - value unchanged
[INFO] 2019-04-09T21:03:08Z WARNING - task "supermean" not used in the graph.
[INFO] 2019-04-09T21:03:08Z WARNING - task "rose_arch_logs" not used in the graph.
[INFO] 2019-04-09T21:03:08Z WARNING - task "rose_arch_wallclock" not used in the graph.
[FAIL] ssh -oBatchMode=yes dtn02.rdf.ac.uk bash —login -c \'ROSE_VERSION=2016.11.1\ rose\ suite-run\ -v\ -v\ —name=u-bh705\ —run=run\ —remote=uuid=72d78a51-fd78-4e7b-aa10-aa945d8f9074\' # return-code=255, stderr=
[FAIL] Host key verification failed.

comment:3 Changed 3 months ago by ros

  • Component changed from UKCA to Rose/Cylc
  • Keywords ssh added; UKCA removed
  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Andrew,

Please make sure you can log into the dtn02 and archer without any prompt for password, passphrase or anything else. I suspect you need to remove an offending host key from your known_hosts file. The error message should tell you what you need to do.

Cheers,
Ros.

comment:4 Changed 3 months ago by anmcr

Hi Ros,

Thanks very much for the quick reply. I can log into dtn02 now without any prompt for a password (and archer). However, when I submit there still seems to be an issue about logging into dtn02. The error message is given below. Note that I also followed the advice on http://cms.ncas.ac.uk/wiki/Docs/PostProcessingApp to remove the transfer of files to JASMIN (postproc > JASMIN Transfer). I also couldn't see any mention of an issue with my known_hosts file. I would be grateful if you could please advise further.

Best wishes,

Andrew

anmcr@puma:/home/anmcr/roses/u-bh705> rose suite-run
[INFO] create: log.20190410T111721Z
[INFO] delete: log
[INFO] symlink: log.20190410T111721Z ⇐ log
[INFO] log.20190410T111557Z.tar.gz ⇐ log.20190410T111557Z
[INFO] delete: log.20190410T111557Z/
[INFO] create: log/suite
[INFO] create: log/rose-conf
[INFO] symlink: rose-conf/20190410T121721-run.conf ⇐ log/rose-suite-run.conf
[INFO] symlink: rose-conf/20190410T121721-run.version ⇐ log/rose-suite-run.version
[INFO] export CYLC_VERSION=6.11.4
[INFO] export ROSE_ORIG_HOST=puma
[INFO] export ROSE_VERSION=2016.11.1
[INFO] install: ana/mule_cumf.py
[INFO] source: svn://puma/um.xm_svn/main/trunk/rose-stem/ana/mule_cumf.py@43344 (fcm:um.xm_tr/rose-stem/ana/mule_cumf.py@43344)
[INFO] WARNING: deprecated items were automatically upgraded in 'suite definition':
[INFO] * (6.0.0) [scheduling][special tasks][sequential] - value unchanged
[INFO] 2019-04-10T11:17:25Z WARNING - task "supermean" not used in the graph.
[INFO] 2019-04-10T11:17:25Z WARNING - task "rose_arch_logs" not used in the graph.
[INFO] 2019-04-10T11:17:25Z WARNING - task "rose_arch_wallclock" not used in the graph.
[FAIL] ssh -oBatchMode=yes dtn02.rdf.ac.uk bash —login -c \'ROSE_VERSION=2016.11.1\ rose\ suite-run\ -v\ -v\ —name=u-bh705\ —run=run\ —remote=uuid=4de349ba-4345-4244-91ea-7f048caa05f8\' # return-code=127, stderr=
[FAIL] bash: rose: command not found

comment:5 Changed 3 months ago by ros

Hi Andrew,

If you are not going to use pptransfer to transfer the archived files from RDF to JASMIN then you need to switch off the task in suite conf → Tasks

Regards,
Ros.

comment:6 Changed 2 months ago by anmcr

Hi Ros,

I got it to run, thanks.

Would it be possible to get your advice on using fcm branch-create? I'm trying to create a vn11.2 branch for this UKCA run, see below. But it fails. I'm not sure what I am doing wrong as this is as suggested in the UKCA tutorial.

Many thanks,

Andrew

anmcr@puma:/home/anmcr/um_work> fcm branch-create —type dev -k 4831 UKCA_PSC_GW_Scheme fcm:um.x_tr@vn11.2
[FAIL] svn info —xml fcm:um.x_tr@vn11.2 # rc=1
[FAIL] svn: E205000: Try 'svn help info' for more information
[FAIL] svn: E205000: Syntax error parsing peg revision 'vn11.2'

comment:7 Changed 2 months ago by willie

Hi Andrew,

It's fcm:um.x-tr, not with the underscore.

Willie

comment:8 Changed 2 months ago by ros

Hi Andrew,

Usually when fcm says it can't find the peg revision it means your MOSRS password isn't cached and it therefore has no idea what the revision keywords are. Password only stays cached for 12 hours so perhaps has expired.

fcm:um.x_tr should work as well as fcm:um.x-tr

Cheers,
Ros.

comment:9 Changed 2 months ago by ros

Hi Andrew,

I assume this problem has now been solve and can now close this ticket.

Regards,
Ros.

comment:10 Changed 8 weeks ago by ros

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.