Connection Closed xterm.js

[karlsiu1]

It is strange that whatever I reinstall the node the shell always give me this error

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:trMB5GLUZTh7sdL9+aGCGgGxyiZg+itfVFQWSV/47kk.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending RSA key in /etc/ssh/ssh_known_hosts:15
  remove with:
  ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "192.168.60.23"
Host key for 192.168.60.23 has changed and you have requested strict checking.
Host key verification failed.

The cluster is fine. Not all the node has this error. Any insight how to solve this error? I browse the forum and cannot find an answer to this. Any help would be great.

 

[Kingneutron]

This is how ssh works, the answer is right in the message:

Offending RSA key in /etc/ssh/ssh_known_hosts:15
remove with:

ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "192.168.60.23" # this is what you need to run

When you reinstalled the OS, it generated new ssh keys.

 

[karlsiu1]

This is how ssh works, the answer is right in the message:

Offending RSA key in /etc/ssh/ssh_known_hosts:15
remove with:

ssh-keygen -f "/etc/ssh/ssh_known_hosts" -R "192.168.60.23" # this is what you need to run

When you reinstalled the OS, it generated new ssh keys.

I tried that, but the funny thing is, there are 4 nodes with the same error. Whenever I tried on node A, node A return to normal, so I go on with node 2, node 2 is fine, but then node 1 return the same error.

 

[Kingneutron]

Check if you have a duplicate IP address / conflict in your network. I've seen this when ssh thought it was connecting to server #1 and it actually turned out to be an old server that was supposed to be powered off with the same IP address

 

[karlsiu1]

N

Check if you have a duplicate IP address / conflict in your network. I've seen this when ssh thought it was connecting to server #1 and it actually turned out to be an old server that was supposed to be powered off with the same IP address

No, the IP static assigned and there is no conflict in IP or whatosever. That is one reason I have no clue on what's going on.

 

[Kingneutron]

Did you run the ssh-keygen remove command on ALL instances that you are trying to ssh FROM?
Every instance has its own copy of that known_hosts file and needs to be updated

Otherwise you can try turning off "strict checking" in ssh settings

 

[karlsiu1]

Did you run the ssh-keygen remove command on ALL instances that you are trying to ssh FROM?
Every instance has its own copy of that known_hosts file and needs to be updated

Otherwise you can try turning off "strict checking" in ssh settings

I browse the net and found this solution.

# Do not keep HostKeys for internal networks.
Host 10.*.*.*  192.168.*.*
    UserKnownHostsFile /dev/null
    StrictHostKeyChecking no

But I use Putty to login and type nano ~/.ssh/config

and paste the code from above. It is not working, I think I did something wrong to disable the strict checking....