# Replacing id\_rsa\_archerum

**URL:** <https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865>\
**Category:** Uncategorized\
**Tags:** ARCHER2\
**Created:** [17 January 2023 19:14 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865 "2023-01-17T19:14:54Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [17 January 2023 19:14 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/1 "2023-01-17T19:14:54Z")

</div>

Hello,  
I think I have never actually run a UM suite from puma to archer2 and did not have an id\_rsa\_archerum in pumanew ~/.ssh.  
I have just created a fresh one and the help pages say it will be auto detected in the next couple of days. I have also done this:  
markr@pumanew:~/.ssh\>ssh-add ./id\_rsa\_archerum  
Enter passphrase for ./id\_rsa\_archerum:  
Identity added: ./id\_rsa\_archerum (./id\_rsa\_archerum)  
markr@pumanew:~/.ssh\>

Do I have to do anything else? (markr on pumanew and mricha on archer2) I did this because the suite failed to launch. /home/markr/roses/u-ct529 perhaps I should try a simpler suite first.

thanks,  
MarkR

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [18 January 2023 11:50 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/2 "2023-01-18T11:50:14Z")

</div>

Hi Mark,

Your id\_rsa\_archerum key has now been added to ARCHER2. Please check you get the following response when logging to ARCHER2 from puma.

```auto
ros@pumanew$ ssh login.archer2.ac.uk
PTY allocation request failed on channel 0
Comand rejected by policy. Not in authorised list 
Connection to login.archer2.ac.uk closed.

```

Regards,  
Ros.

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:13 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/3 "2023-01-18T12:13:12Z")

</div>

Hi Ros,

Yes I go the message you indicated but rose suite-run still fails.

[FAIL] ssh -oBatchMode=yes -n [mricha@login.archer2.ac.uk](mailto:mricha@login.archer2.ac.uk) env\ ROSE\_VERSION=2019.01.3\ CYLC\_VERSION=7.8.12\ bash\ -l\ -c\ '"$0"\ "$@"'\ rose\ suite-run\ -vv\ -n\ u-ct529\ –run=run\ –remote=uuid=bc3521ee-54fc-4d6e-a889-bb8d3ae2a657,now-str=20230118T120306Z,root-dir='$DATADIR' # return-code=255, stderr=

[FAIL] Host key verification failed.

markr@pumanew:~/roses/u-ct529\>ssh-add -l

4096 SHA256:mniZil9oDVQTvD/Is10l49iREMINH2WXIPK5c8O2NrU ./id\_rsa\_archerum (RSA)

![image001.jpg](https://europe1.discourse-cdn.com/flex013/uploads/cms_support/original/1X/2485d26919316b1d80aa60f5ca8e2cb5bc0275fe.jpeg)

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [18 January 2023 12:16 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/4 "2023-01-18T12:16:09Z")

</div>

Hi Mark,

Please try logging into each login nodes 1-4 (e.g. [login1.archer2.ac.uk](http://login1.archer2.ac.uk)). At least one of them will list a dodgey key that will need removing from your `~/.ssh/known_hosts` file.

Regards,  
Ros.

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:17 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/5 "2023-01-18T12:17:01Z")

</div>

Hi Ros,  
I just the ssh command tried again to make it match the rose suite command:  
markr@pumanew:~/roses/u-ct529\>ssh [mricha@login.archer2.ac.uk](mailto:mricha@login.archer2.ac.uk)  
Warning: the ECDSA host key for ‘[login.archer2.ac.uk](http://login.archer2.ac.uk)’ differs from the key for the IP address ‘193.62.216.42’  
Offending key for IP in /home/markr/.ssh/known\_hosts:6  
Matching host key in /home/markr/.ssh/known\_hosts:18  
Are you sure you want to continue connecting (yes/no)? yes  
PTY allocation request failed on channel 0  
Comand rejected by policy. Not in authorised list  
Connection to [login.archer2.ac.uk](http://login.archer2.ac.uk) closed.

then the suite again still fails like this:  
[FAIL] Host key verification failed.

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [18 January 2023 12:18 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/6 "2023-01-18T12:18:06Z")

</div>

Remove the offending key and try again - there may be more than one offending key.

`Offending key for IP in /home/markr/.ssh/known_hosts:6`

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:23 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/7 "2023-01-18T12:23:12Z")

</div>

Well there are several similar IP in the known hosts 192.62.216.4\* so maybe I have to delete all those as “[login.archer2.ac.uk](http://login.archer2.ac.uk)” is likely to be several machines

markr@pumanew:~/roses/u-ct529\>ssh [mricha@login.archer2.ac.uk](mailto:mricha@login.archer2.ac.uk)  
The authenticity of host ‘[login.archer2.ac.uk](http://login.archer2.ac.uk) (193.62.216.45)’ can’t be established.  
ECDSA key fingerprint is SHA256:UGS+LA8I46LqnD58WiWNlaUFY3uD1WFr+V8RCG09fUg.  
ECDSA key fingerprint is MD5:71:2a:aa:7a:b1:a5:43:03:d2:ec:4a:da:5f:c0:0f:8c.  
Are you sure you want to continue connecting (yes/no)? yes  
Warning: Permanently added ‘[login.archer2.ac.uk](http://login.archer2.ac.uk)’ (ECDSA) to the list of known hosts.  
Warning: the ECDSA host key for ‘[login.archer2.ac.uk](http://login.archer2.ac.uk)’ differs from the key for the IP address ‘193.62.216.45’  
Offending key for IP in /home/markr/.ssh/known\_hosts:2  
Are you sure you want to continue connecting (yes/no)? yes  
PTY allocation request failed on channel 0  
Comand rejected by policy. Not in authorised list  
Connection to [login.archer2.ac.uk](http://login.archer2.ac.uk) closed.

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [18 January 2023 12:24 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/8 "2023-01-18T12:24:50Z")

</div>

Yes, indeed. Hence my comment above about logging into each ARCHER2 login node.

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:26 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/9 "2023-01-18T12:26:00Z")

</div>

oops missed that message! will delete all those 62.4\* and try login1-4 and then tray suite.

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:32 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/10 "2023-01-18T12:32:07Z")

</div>

Hmm,  
no progress yet. the archer2 IPS reoved and logins1 to login4 ssh’d as expected (I can even do an ls command)  
markr@pumanew:~/.ssh\>ssh [mricha@login4.archer2.ac.uk](mailto:mricha@login4.archer2.ac.uk) ls  
bin  
BUILD  
cesm\_prep  
ck-bin  
cylc-run  
Docker  
Experimental  
later\_dot\_cime  
monc\_module\_prep\_202207.txt  
mr\_dot\_cime\_fragments  
mrigrep.txt  
my\_modules  
NOTES  
Projects  
PythonHPC.zip  
SingWork  
SW  
TAR\_files

but no joy from suite u-ct529

not sure where to look next. the id\_rsa\_archerum was generated fresh last night and I used the ssh-setup so that th ssh-add shows it is live. also the “ls” succeeded. I could send you a "ssh -v -v -v " log if it helps.

markr

---

<div class="post-metadata">

**Author:** ![RosalynHatcher](https://dub1.discourse-cdn.com/flex013/user_avatar/cms-helpdesk.ncas.ac.uk/rosalynhatcher/32/11_2.png) [@RosalynHatcher](https://cms-helpdesk.ncas.ac.uk/u/RosalynHatcher)\
**Post date:** [18 January 2023 12:36 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/11 "2023-01-18T12:36:08Z")

</div>

Does `ssh mricha@login.archer2.ac.uk` give the expected response too?

Are you retriggering the task or doing a `rose suite-run`? If the former, try stopping the suite and starting it again. Sometimes cylc doesn’t pickup the new ssh changes.

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:36 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/12 "2023-01-18T12:36:54Z")

</div>

Yeah I’m in:

markr@pumanew:~/.ssh\>grep archer known\_hosts  
[login1.archer2.ac.uk](http://login1.archer2.ac.uk),193.62.216.42 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEnMeFf1TPZ4pbupWeD4IeahEeeqJMAhrCv1znyQGAL45yOIArVltscW8GNhzfaWk5vKb9sIAm2mJZPc3b7te3c=  
[login2.archer2.ac.uk](http://login2.archer2.ac.uk),193.62.216.43 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEnMeFf1TPZ4pbupWeD4IeahEeeqJMAhrCv1znyQGAL45yOIArVltscW8GNhzfaWk5vKb9sIAm2mJZPc3b7te3c=  
[login3.archer2.ac.uk](http://login3.archer2.ac.uk),193.62.216.44 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEnMeFf1TPZ4pbupWeD4IeahEeeqJMAhrCv1znyQGAL45yOIArVltscW8GNhzfaWk5vKb9sIAm2mJZPc3b7te3c=  
[login4.archer2.ac.uk](http://login4.archer2.ac.uk),193.62.216.45 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEnMeFf1TPZ4pbupWeD4IeahEeeqJMAhrCv1znyQGAL45yOIArVltscW8GNhzfaWk5vKb9sIAm2mJZPc3b7te3c=  
markr@pumanew:~/.ssh\>ssh [mricha@login.archer2.ac.uk](mailto:mricha@login.archer2.ac.uk) ls  
The authenticity of host ‘[login.archer2.ac.uk](http://login.archer2.ac.uk) (193.62.216.42)’ can’t be established.  
ECDSA key fingerprint is SHA256:UGS+LA8I46LqnD58WiWNlaUFY3uD1WFr+V8RCG09fUg.  
ECDSA key fingerprint is MD5:71:2a:aa:7a:b1:a5:43:03:d2:ec:4a:da:5f:c0:0f:8c.  
Are you sure you want to continue connecting (yes/no)? yes  
Warning: Permanently added ‘[login.archer2.ac.uk](http://login.archer2.ac.uk)’ (ECDSA) to the list of known hosts.  
bin  
BUILD  
cesm\_prep  
ck-bin  
cylc-run  
Docker  
Experimental  
later\_dot\_cime  
monc\_module\_prep\_202207.txt  
mr\_dot\_cime\_fragments  
mrigrep.txt  
my\_modules  
NOTES  
Projects  
PythonHPC.zip  
SingWork  
SW  
TAR\_files

---

<div class="post-metadata">

**Author:** ![markr](https://avatars.discourse-cdn.com/v4/letter/m/e68b1a/32.png) [@markr](https://cms-helpdesk.ncas.ac.uk/u/markr)\
**Post date:** [18 January 2023 12:39 UTC](https://cms-helpdesk.ncas.ac.uk/t/replacing-id-rsa-archerum/865/13 "2023-01-18T12:39:23Z")

</div>

A weakness of “known\_hosts” I think. DNS lookup and multiple identity for an alias “[login.archer2.ac.uk](http://login.archer2.ac.uk)” added to complications. Suite has started and Gcyls showing correctly.

thanks for the help and good suggestions  
Mark
