Opened 3 years ago

Closed 3 years ago

#2022 closed help (fixed)

Failed to start rose job on archer

Reported by: markr Owned by: ros
Component: UM Model Keywords: rose archer um10.3
Cc: Platform: ARCHER
UM Version: 10.3

Description

Hello CMS
I just tried to start a rose job on Archer (from Puma rose edit interface) but it did not work for me.

I followed the guidance that I found:

I set up the mosrs access to allow copy of the rose suite
set up ssh-agent - can ssh into archer okay
add login*.archer.ac.uk to .ssh/config
now possible to ssh without specifying userid
set up known_hosts (8 login nodes)


I am working with a copy of u-aa774 (u-ai081)
My username on puma is markr and my username on Archer is mricha.
Error messge is:
RosePOpenError ssh -oBatchMode=yes mricha@… bash —login -c \'ROSE_VERSION=2016.06.1\ rose\ suite-run\ -v\ -v\ —name=u-ai081\ —run=run\ —remote=uuid=3c4bcf24-4c1c-4e4c-b900-a57ed57fdf1e,root-dir=$DATADIR\'

permission denied (publickey keyboard interactive)

[INFO] 2016-11-22T14:14:12+0000 export CYLC_VERSION=6.10.2
[INFO] 2016-11-22T14:14:12+0000 export ROSE_ORIG_HOST=puma
[INFO] 2016-11-22T14:14:12+0000 export ROSE_VERSION=2016.06.1
[INFO] 2016-11-22T14:14:12+0000 unchanged: app
[INFO] 2016-11-22T14:14:12+0000 source: /home/markr/roses/u-ai081/app
[INFO] 2016-11-22T14:14:12+0000 unchanged: meta
[INFO] 2016-11-22T14:14:12+0000 source: /home/markr/roses/u-ai081/meta
[INFO] 2016-11-22T14:14:12+0000 unchanged: rose-suite.info
[INFO] 2016-11-22T14:14:12+0000 source: /home/markr/roses/u-ai081/rose-suite.info
[INFO] 2016-11-22T14:14:15+0000 ssh -oBatchMode=yes mricha@… bash —login -c \'ROSE_VERSION=2016.06.1\ rose\ suite-run\ -v\ -v\ —name=u-ai081\ —run=run\ —remote=uuid=3c4bcf24-4c1c-4e4c-b900-a57ed57fdf1e,root-dir=$DATADIR\'

Mark

Change History (6)

comment:1 Changed 3 years ago by ros

Hi Mark,

This error is usually because the login to ARCHER is prompting for a passphrase or password. Can you please confirm that you can login to ARCHER without it prompting for input.

Cheers,
Ros.

comment:2 Changed 3 years ago by markr

Hi Ros see this from my puma session as markr and logs into archer as mricha.
Perhaps I should restart the rose editor ? I will retry.

markr@puma markr $ ssh login.archer.ac.uk
--------------------------------------------------------------------------------
This is a private computing facility. Access to this service is limited to those
who have been granted access by the operating service provider on behalf of the
contracting authority and use is restricted to the purposes for which access was
granted. All access and usage are governed by the terms and conditions of access
agreed to by all registered users and are thus subject to the provisions of the
Computer Misuse Act, 1990 under which unauthorised use is a criminal offence.

If you are not authorised to use this service you must disconnect immediately.
--------------------------------------------------------------------------------

Last login: Tue Nov 22 14:12:07 2016 from puma.nerc.ac.uk
================================================================================
login.archer.ac.uk
--------------------------------------------------------------------------------

For assistance please contact the service helpdesk at: support@archer.ac.uk

--------------------------------------------------------------------------------

 IF YOU ARE NOT AUTHORISED TO USE THIS ACCOUNT THEN YOU MUST LOGOUT IMMEDIATELY

USE OF THIS ACCOUNT BY ANYBODY OTHER THAN THE REGISTERED HOLDER IS NOT PERMITTED

--------------------------------------------------------------------------------

================================================================================
mricha@eslogin003:~>
Last edited 3 years ago by ros (previous) (diff)

comment:3 Changed 3 years ago by markr

And this is rose suite-run from the suite directory

markr@puma u-ai081 $ rose suite-run
[INFO] create: log.20161122T145650Z
[INFO] delete: log
[INFO] symlink: log.20161122T145650Z ⇐ log
[INFO] log.20161122T141412Z.tar.gz ⇐ log.20161122T141412Z
[INFO] delete: log.20161122T141412Z/
[INFO] create: log/suite
[INFO] create: log/rose-conf
[INFO] symlink: rose-conf/20161122T145650-run.conf ⇐ log/rose-suite-run.conf
[INFO] symlink: rose-conf/20161122T145650-run.version ⇐ log/rose-suite-run.version
[INFO] export CYLC_VERSION=6.10.2
[INFO] export ROSE_ORIG_HOST=puma
[INFO] export ROSE_VERSION=2016.06.1
[FAIL] ssh -oBatchMode=yes mricha@… bash —login -c \'ROSE_VERSION=2016.06.1\ rose\ suite-run\ -v\ -v\ —name=u-ai081\ —run=run\ —remote=uuid=bd7c38ac-6930-4d06-b031-d0c786394637,root-dir=$DATADIR\' # return-code=127, stderr=
[FAIL] ————————————————————————————————————————
[FAIL] This is a private computing facility. Access to this service is limited to those
[FAIL] who have been granted access by the operating service provider on behalf of the
[FAIL] contracting authority and use is restricted to the purposes for which access was
[FAIL] granted. All access and usage are governed by the terms and conditions of access
[FAIL] agreed to by all registered users and are thus subject to the provisions of the
[FAIL] Computer Misuse Act, 1990 under which unauthorised use is a criminal offence.
[FAIL]
[FAIL] If you are not authorised to use this service you must disconnect immediately.
[FAIL] ————————————————————————————————————————
[FAIL]
[FAIL] bash: rose: command not found

comment:4 Changed 3 years ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Mark,

You need to add Rose & Cylc to your login environment on ARCHER. In your ~/.profile add the line:

export PATH=$PATH:$UMDIR/software/bin

Cheers,
Ros.

comment:5 Changed 3 years ago by markr

Aargh,
sorry!

Missed that in the guide.
I guess that is why a module is not useful.
Suite looks like it is running now.

Mark

comment:6 Changed 3 years ago by ros

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