Richmond Cluster (21)

Tuesday 13 May, 2008 - 12:52

Added Richmond2 Successfully.

The ssh problem appears to be have been caused by having a dsa public key in the id_rsa.pub file.

As usual, the ssh command was very helpful in diagnosing this problem by saying:

connection closed by 192.168.100.66

The problem was immediately evident from this message which is why it has taken me a day to work this out.

Have to recover the keys on richmond1 and restore the authorized_keys on richmond1.