Problem description:
Cluster have configured SSH key free land, and then appear "The authenticity of host xx can 't be established", can normal operation after enter yes,
Solution:
1, modify the/etc/SSH/ssh_config:
Add these two lines
StrictHostKeyChecking no
UserKnownHostsFile/dev/null
2, and then restart the
The/etc/rc. D/init. D/SSHD restart

Tend to be the problem, and the other to
This reason could be a local host key has changed, so every time the SSH link will have prompt, you just need to enter yes under the interaction,
Of course, if want to solve the problem for a long time, can adopt the following methods:
1, when using SSH to connect to the remote host with "-o StrictHostKeyChecking=no" option, remove the validation checks on the host,
SSH -o StrictHostKeyChecking=no 192.168. XXX. XXX
Note: 192.168. XXX. XXX for the local IP address: Windows ipconfig view, Linux ifconfig
2, of course, you also can change the configuration file information directly, so thoroughly remove validation,
Modify/etc/SSH/ssh_config file (or $HOME/. SSH/config) in the configuration, add the following two lines of configuration:
StrictHostKeyChecking no
UserKnownHostsFile/dev/null
Note: use the second method, however, easy to cause potential danger, you can refer to Stackoverflow question:
SSH: The authenticity of host 'hostname can' t be established