NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Error while backing up w/ RSync on 4.2.12
Backing up from one NAS to another via RSync.
Both brand new RN Pro BE's on 4.2.12 - oriignally Factory-defaulted on 4.2.11 w/ ext4 filesystems and dual redundancy.
Getting a similar failure as Flip-SA in this thread: viewtopic.php?f=31&t=42698
Specifically...
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(760) [receiver=3.0.7]
rsync: connection unexpectedly closed (183 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]
Backup failed. Sat Jul 10 01:22:20 MDT 2010.
Reason for failure:
Error encountered copying data from remote source path TIBMain::ARCHIVE ==> /ARCHIVE/ due to unknown reason. Please see log.
There are no network errors seen by either NAS unit - and their shouldn't be - my network
is in top condition with an HP Procurve switch at the core.
I'm sending my logs in for BOTH machines.
Both brand new RN Pro BE's on 4.2.12 - oriignally Factory-defaulted on 4.2.11 w/ ext4 filesystems and dual redundancy.
Getting a similar failure as Flip-SA in this thread: viewtopic.php?f=31&t=42698
Specifically...
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(760) [receiver=3.0.7]
rsync: connection unexpectedly closed (183 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7]
Backup failed. Sat Jul 10 01:22:20 MDT 2010.
Reason for failure:
Error encountered copying data from remote source path TIBMain::ARCHIVE ==> /ARCHIVE/ due to unknown reason. Please see log.
There are no network errors seen by either NAS unit - and their shouldn't be - my network
is in top condition with an HP Procurve switch at the core.
I'm sending my logs in for BOTH machines.
12 Replies
Replies have been turned off for this discussion
- I would consider updating your production box to 4.2.13 as this may solve the problem.
However if you like, you should try to troubleshoot the problem with the backup box first to determine the cause. There could e.g. be a faulty ethernet cable, faulty port on the router/switch or some other issue. - Just my experiences with the same problem...
I know this is long after the original post, but having just had an rsync NAS-->NAS stop working that had been working for months, I finally got it working.
I had an NV+ with 4.1.8 rsync from an Ultra 2 Plus. The connection started and I then got
Mar 8 07:13:30 xxxxxx rsyncd[3864]: rsync: read error: Connection timed out (110)
Mar 8 07:13:30 xxxxxx rsyncd[3864]: rsync error: error in rsync protocol data stream (code 12) at io.c(760) [sender=3.0.8]
I read that rsync might have been an issue so I disabled JF on both NAS and tried the backup again and it started working.
I then re-enabled them on the U2+ and it still worked then re-enabled on the NV+ and it still worked...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
