NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RSYNC ReadyNAS to ReadyNAS - Suddenly Stopped
Please help. I have been successfully (probably a year) backing up (via RSYNC) two ReadyNAS devices to each other in physically separate locations (one 6 bay PRO and another 4 bay Ultra.) It works...
I had the same problem, rSync work from one NAS to the other, but not the other way around. Also for me it used to work to use rSync for Backup between the 2 NAS, but just suddenly stopped working. The errormessage was for me:
"rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.9]"
Both NAS have the correct DNS server IP and it could do lookup of the hostname of "the other " NAS to the correct IP.
From the NAS:s I can SSH into "the other" NAS using IP and hostname.
The rSync port (873) is open in the FW on both sides. I can telnet using the both IP and hostname and the portnumber from both NAS to the other NAS.
What I did to solve it was to restart the rSynd Daemon on the failing server, twice. Not once, but twice in a row. That did the trick. For me at least.
"rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.9]"
Both NAS have the correct DNS server IP and it could do lookup of the hostname of "the other " NAS to the correct IP.
From the NAS:s I can SSH into "the other" NAS using IP and hostname.
The rSync port (873) is open in the FW on both sides. I can telnet using the both IP and hostname and the portnumber from both NAS to the other NAS.
What I did to solve it was to restart the rSynd Daemon on the failing server, twice. Not once, but twice in a row. That did the trick. For me at least.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
