NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
cguers
Mar 26, 2013Aspirant
[SOLVED] SSH rsync error
I just wanted to post this as there may be others experiencing the same issue. 8)
I have two NAS devices, a PRO and an ULTRA, on separate locations and I am doing an rsync between the devices over the Internet. To do this safely, I enabled SSH on the ULTRA (pretty cool and useful plugin RSync over SSH Enabler). This worked great for quite some time and then, all of a sudden, my main NAS started complaining with the following messages:
The way to solve this is to SSH into the NAS device(s) (Enable Root SSH Access) and rename all the "known_hosts" files (my system had several). You can delete the files, but renaming them will give you some piece of mind ,just in case. Next time your backup jobs start up again, this file will be re-created automagically and correctly.
How to find these files?
then you rename them as follows, using each file found.
In other words, if a file that was found is
you would type
GOOD LUCK!
I have two NAS devices, a PRO and an ULTRA, on separate locations and I am doing an rsync between the devices over the Internet. To do this safely, I enabled SSH on the ULTRA (pretty cool and useful plugin RSync over SSH Enabler). This worked great for quite some time and then, all of a sudden, my main NAS started complaining with the following messages:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for <host> has changed,
and the key for the according IP address <IP>
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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
<fingerprint>.
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:15
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
The way to solve this is to SSH into the NAS device(s) (Enable Root SSH Access) and rename all the "known_hosts" files (my system had several). You can delete the files, but renaming them will give you some piece of mind ,just in case. Next time your backup jobs start up again, this file will be re-created automagically and correctly.
How to find these files?
find / -name known_hosts -print
then you rename them as follows, using each file found.
mv path_and_file path_and_file.OLD
In other words, if a file that was found is
/root/.ssh/known_hosts
you would type
mv /root/.ssh/known_hosts /root/.ssh/known_hosts.OLD
GOOD LUCK!
3 Replies
Replies have been turned off for this discussion
- kossbossGuideThis is a typical issue I see with ssh, its not really a readynas issue. It just using a pretty bad method to see if your being hacked. It has the ssh key and the some other info, and its not matching. After you fix - did the problem persist? Did you add the key of the source nas to the authorized list of the destination (from the rsync share settings menu)?
- kossbossGuide
- cguersAspirant@kossboss
After removing the known hosts files, the problem with the "man in the middle" the was fixed. :D
Now I am getting some timeouts on long sync jobs (multi-GB shares), but I believe that is due to something else. Possibly some issues with the ISP on either end. This is the error message I see now in the log file:INCREMENTAL Backup started. Wed Mar 27 09:42:21 ART 2013
Job: 006
Protocol: rsync
Source: [media]/
Destination: <remote host>:/media
sending incremental file list
<file 1>
<file 2>
<file 3>
Read from remote host <remote host>: Connection timed out
rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: No child processes (10)
rsync: connection unexpectedly closed (4006 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(605) [sender=3.0.9]
Backup failed.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!