-
Title
ESX based replications fail after a host rebuild - RSA Host key for <ESX Host Name> has cha -
Description
The error below appears on all replications after you have rebuilt an existing host. This error produces several forms.
An internal error occurred during execution, please contact Vizioncore support if the error persists. Error Message: 3185 - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
e9:a0:bd:e3:3d:f6:8f:d6:75:7b:15:ed:62:d0:85:51.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending key in /root/.ssh/known_hosts:2
RSA host key for <ESX Host Name> has changed and you have requested strict checking.
Host key verification failed.
FATAL internal internal error [at pkt_recv:43] -
Cause
Host is rebuilt with the same name and RSA keys for this name and/or IP address have already been established on the target host for replication and the rebuilt host has a different RSA key.
-
Resolution
This can be resolved by removing the known_hosts files from target replication host.
Instructions:
1. Connect to the target host with Putty or similar tool.
2. Log in as root.
3. Change to the .ssh directory by typing cd /root/.ssh.
4. List out the contents of the directory by typing ls –lah. You should see a file called known_hosts. If this is a newly created host, the file will not exist.
5. To delete the known_hosts file type rm known_hosts.
6. Once you have done this, you need to re-establich the keys for each source host that will be used in replication. You do this by connecting directly from the root console by typing ssh <IP or FQDN of each ESX source host>.
7. You will see the following message appear “The authenticity of host <ESX Host Name> can't be established.RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx. Are you sure you want to continue connecting (yes/no)?” At this point type in “yes” and hit enter. You will have to enter the ROOT password again for the target ESX host.
8. Run the replication job once again.