NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
_frantic_
Feb 16, 2016Aspirant
ReadyNAS Replicate: "Connect error code: -51" since firmware update to 6.4.2
I have updated source (RN312) and target (RN104) from 6.4.1. to 6.4.2. Since that, every job failed. Example Log (eMail): [2016-02-16 08:00:05] [Info] Job updated from server
[2016-02-16 08:00:...
- Feb 18, 2016
Apparently there have been some problems with our server recently. Are your Replicate backup jobs completing again now?
PhysicsTeacher
Feb 28, 2016Aspirant
I am suffering from this issue, as well, but I do not believe that it is associated with a firmware update.
I updated my two units to 4.2.28 on December 6, and Replicate continued to complete successfully for another two months.
Sun Dec 6 14:06:50 EST 2015 System Update Status (LABNAS) : Your ReadyNAS device has been updated with a new firmware image. (RAIDiator-x86 4.2.28)
Sun Dec 6 14:13:52 EST 2015 System Update Status (BKUPNAS) : Your ReadyNAS device has been updated with a new firmware image. (RAIDiator-x86 4.2.28)
Through February 16, my logs typicially look like this:
[2016-02-16 02:00:02] [Info] Job updated from server
[2016-02-16 02:00:02] [Info] Replicate version: 1.2.0 build R1
[2016-02-16 02:00:02] [Info] Starting backup job "System Backup [2014-02-19 04:30 PM]"
[2016-02-16 02:00:02] [Info] Locking target folder: /c/System Backup [2014-02-19 04:30 PM]
[2016-02-16 02:00:04] [Info] Resume folder is "/c/System Backup [2014-02-19 04:30 PM]/2016-02-15 02-00/data"
[2016-02-16 02:03:12] [Info] p2p connect to LABNAS in 2819143 network
[2016-02-16 02:05:49] [Info] Connection method: 5
[2016-02-16 02:05:49] [Warning] Using a relayed connection, consider setting up port forwarding
[2016-02-16 02:05:49] [Info] LAN connection not available
[2016-02-16 02:05:49] [Info] Using p2p connection
[2016-02-16 02:05:49] [Info] Initializing source device
[2016-02-16 02:05:49] [Info] Sending task to source device
[2016-02-16 02:05:51] [Info] Awaiting task report
[2016-02-16 02:05:53] [Info] Received success report
[2016-02-16 02:05:53] [Warning] Snapshot is not requested
[2016-02-16 02:05:53] [Warning] Backup could be inconsistent
[2016-02-16 02:05:53] [Info] Device initialization finished
[2016-02-16 02:05:53] [Info] Starting system config backup
[2016-02-16 02:05:53] [Info] Sending task to source device
[2016-02-16 02:05:56] [Info] Awaiting task report
[2016-02-16 02:06:09] [Info] Received success report
[2016-02-16 02:06:09] [Info] Copy in progress
[2016-02-16 02:13:03] [Info] Copy finished
[2016-02-16 02:13:03] [Info] Deinitialize source device
[2016-02-16 02:13:03] [Info] Sending task to source device
[2016-02-16 02:13:06] [Info] Awaiting task report
[2016-02-16 02:13:08] [Info] Received success report
[2016-02-16 02:13:08] [Info] Device deinitialization finished
[2016-02-16 02:13:08] [Info] p2p disconnect with LABNAS in 2819143 network
[2016-02-16 02:13:09] [Info] Unlock target folder: /c/System Backup [2014-02-19 04:30 PM]
[2016-02-16 02:13:09] [Info] Job finished
Files copied:
...
Summary:
Copy start time: 2016-02-16 02:06
Total files processed: 507972
Total files transferred: 6
Total files size: 2.51 TB
Total files size transferred: 91.40 MB
Average speed: 225.52 KB/s
Exit code: 0 (Ok)
Copy end time: 2016-02-16 02:13
Beginning on February 17, they all resemble this:
[2016-02-17 02:00:03] [Info] Job updated from server
[2016-02-17 02:00:04] [Info] Replicate version: 1.2.0 build R1
[2016-02-17 02:00:04] [Info] Starting backup job "System Backup [2014-02-19 04:30 PM]"
[2016-02-17 02:00:04] [Info] Locking target folder: /c/System Backup [2014-02-19 04:30 PM]
[2016-02-17 02:00:06] [Info] Resume folder is "/c/System Backup [2014-02-19 04:30 PM]/2016-02-16 02-00/data"
[2016-02-17 02:03:24] [Info] p2p connect to LABNAS in 2819143 network
[2016-02-17 02:03:46] [Info] p2p connect to LABNAS in 2819143 network
[2016-02-17 02:03:58] [Error] Unable to connect to LABNAS
[2016-02-17 02:03:58] [Error] Connect error code: -51
[2016-02-17 02:03:58] [Error] Please check source device is online and Replicate service is running
[2016-02-17 02:03:58] [Info] Unlock target folder: /c/System Backup [2014-02-19 04:30 PM]
[2016-02-17 02:03:58] [Info] Job finished
I do not believe that it is coincidence that my jobs began failing on the same day as other people's jobs. Thoughts?
Bob Breum
_frantic_
Feb 28, 2016Aspirant
For me, the latest series of failed jobs (code -51) started on 2016-02-10.
Every day since that most of all jobs (except one on 2016-02-13 and another one on 2016-02-17) failed until 2016-02-18, 20:00 UTC.
The other day, mdgm posted "Apparently there have been some problems with our server recently.".
PhysicsTeacher wrote:I do not believe that it is coincidence that my jobs began failing on the same day as other people's jobs. Thoughts?
no, your problems started, when my problems began to disappear :-)
So, perhaps they have changed something on the server side...
I have checked my logs and e-mails again:
[2016/02/12 10:28:10] Updated from ReadyNASOS 6.4.1 (ReadyNASOS) to 6.4.2 (ReadyNASOS).
So, that was _after_ the series of failures began for me.
Therefore, I am relatively certain now, that all of this has nothing to do with client versions.
It is more likely related to something on the server side.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!