Opened 6 months ago

Closed 5 months ago

#3162 closed help (fixed)

fail to login to ARCHER host from pumatest

Reported by: luciad Owned by: um_support
Component: PUMA Keywords: login host
Cc: Platform: PUMA
UM Version: 11.1

Description

Hello,
I really hope you can help me with this as soon as possible.

My suite fails because it cannot login to archer nodes ([FAIL] No hosts selected.) from pumatest. However, when I type login.archer.ac.uk from the pumatest it logs into archer without requiring password.
I have the following lines in the /.profile, that ask for the /home/luciad/.ssh/id_rsa password when I login to pumatest:

# ssh-agent setup
. $HOME/.ssh/ssh-setup

if [ -n "SSH_AUTH_SOCK" ] ; then

eval $(ssh-agent)
ssh-add

fi

I've set up these lines so that I don't have to deal with this error anymore. And yet..something happened that I don't understand.
This started this morning, without any obvious reason why it failed.

I would greatly appreciate your help,
Lucia

Change History (7)

comment:1 Changed 6 months ago by dcase

There are a lot of tickets with similar problems, and you can use the search facility of this website to find them. For e.g. : http://cms.ncas.ac.uk/ticket/3090 has a good suggestion at the top.

I would try this as a first step.

comment:2 Changed 6 months ago by ros

HI Lucia,

Did you do the initial set up for rose host-select? All the ARCHER login nodes need to be added to the ~/.ssh/known_hosts file for it to work.

See here: http://cms.ncas.ac.uk/wiki/RoseCylc/Hints#Settinguprosehost-selectarcher

Regards,
Ros.

comment:3 Changed 6 months ago by luciad

Hi Ros,

  1. I tried the suggestions in the ticket #3090, and getthe same errors…And I don't understand how the issue was solved - it is not clear in the ticket.
  1. I did ~um/um-training/setup-archer-hosts and then rose host-select archer

and it returns with all the archer login nodes, with no error. As I said, I can manually login to archer from pumatest, without a password. The error occurs in fcm_make_um, not when I submit the run.

Regards,
Lucia

comment:4 Changed 6 months ago by ros

Hi Lucia,

Sorry, should have read your original message properly. You don't need the

if [ -n "SSH_AUTH_SOCK" ] ; then

eval $(ssh-agent)
ssh-add

fi

in your ~/.profile this is all handled by the ssh-setup script you call before it.

Can you try removing these lines, kill the hundred odd ssh-agent processes you have running (ps -flu luciad | grep ssh-agent shows you have 195!). Then log out and back into pumatest. It should start a new agent and then do ssh-add.

Regards,
Ros.

comment:5 Changed 6 months ago by luciad

Hi Ros,

Thank you . This solved my problem.
It's puzzling how I had 195 ssh-agent processes running…maybe this was the issue, because the lines in the .profile were there before and the login was working without issues.

One last question: Do I have to do ssh-add everytime I login to pumatest (or before submitting a job to archer)?

Regards,
Lucia

comment:6 Changed 6 months ago by ros

Hi Lucia,

The ssh-agent will persist between login sessions in the same way as on current PUMA so no you don't need to run ssh-add everytime you log in.

Cheers,
Ros

comment:7 Changed 5 months ago by grenville

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