NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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:06] [Info] Replicate version: 1.3.0 build R2 [2016-02-16 08:00:06] [Info] Starting backup job "Backup RN312 Docs***" [2016-02-16 08:00:06] [Info] Locking target folder: /data/Backup/Backup RN312 Docs*** [2016-02-16 08:00:07] [Info] Resume folder is "/data/Backup/Backup RN312 Docs***/2016-02-15 08-00 (failed)/data" [2016-02-16 08:00:08] [Info] p2p connect to nas-6D-*** in 880*** network [2016-02-16 08:00:32] [Info] p2p connect to nas-6D-*** in 880*** network [2016-02-16 08:00:49] [Error] Unable to connect to nas-6D-*** [2016-02-16 08:00:49] [Error] Connect error code: -51 [2016-02-16 08:00:49] [Error] Please check source device is online and Replicate service is running [2016-02-16 08:00:49] [Info] Unlock target folder: /data/Backup/Backup RN312 Docs*** [2016-02-16 08:00:49] [Info] Job finished
When I go to https://replicate.readynas.com, everything other than "Failed Reports" looks fine.
Apparently there have been some problems with our server recently. Are your Replicate backup jobs completing again now?
23 Replies
Replies have been turned off for this discussion
hello _frantic_,
Please check if source NAS still has Services available and the Internet is marked green under Cloud. If you can access admin page of both NAS units, check the ReadyNAS Remote and ReadyNAS Replicate. Try disabling and re-enabling if you can.
Please also see Communication problems between NASes of article ReadyNAS: Replicate Troubleshooting.
Regards,
hm, I can see both devices on https://replicate.readynas.com / Views / Network.
Therefore I thought everything should be okay with the devices configurations.
I checked it: "ReadyNAS Remote" and "ReadyNAS Replicate" are active on both devices.
Also, "Internet" and "Services" are marked green on both.
Anyway, I have disabled and re-enabled the services on both devices as suggested.
Tomorrow I will check, wether jobs will run successful again.
Thanks and best regards, _frantic_
Hi _frantic_,
Just let us know if the backup runs again and if not, try to recreate and see if it works.
Kind regards,
BrianL
NETGEAR Community Team
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
My thought: there is something happening on the Replicate Server at Netgear, we all suffer the same error, it started around the same time frame and we're on different firmware releases...
My replicate jobs do finish every now and then, for me it is not a hard error (but sometimes very persistant!).
Wondering if it has anything to do with the time of day (and load on the Replicate server)?
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.
About three days ago, my jobs no longer failed. Everything is working again, with no changes on my part.
Add me to the list of people with this issue. Immediately after updating to 6.4.2 replicate stopped being able to connect to one of our ReadyNAS units. Both are on the same network. Error log in replicate shows it fails on p2p connect to the source ReadyNAS. Have rebooted both units several times. Removed and re-added both units to the Replicate service. Starting a new backup fails with the same error, and if I try to "Resume from" one of the previous backups, I'm unable to select one, it just spins and won't show me the previous backups.
Eagerly awating a solution to this problem, as it was clearly caused by the latest firmware update.
Same Issue, Its seem that when you manually force it few time it go trought but yes automanic randomly fail -> Netgear server Issue
But I have to say netgear RN516 & replicate is awsome :) my only exceptation is that I hope in some way the will proceed a Full system back up instead of folders in the futur
Log:
[2016-03-02 15:01:28] [Info] Replicate version: 1.3.0 build R2
[2016-03-02 15:01:28] [Info] Starting backup job "Transfert"
[2016-03-02 15:01:28] [Info] Locking target folder: /data/***
[2016-03-02 15:01:28] [Info] Resume folder is "/data/*** (failed)/data"
[2016-03-02 15:01:35] [Info] p2p connect to NAS*** in 881*** network
[2016-03-02 15:01:58] [Info] p2p connect to NAS*** in 881*** network
[2016-03-02 15:02:11] [Error] Unable to connect to NAS***
[2016-03-02 15:02:11] [Error] Connect error code: -51
[2016-03-02 15:02:11] [Error] Please check source device is online and Replicate service is running
[2016-03-02 15:02:11] [Info] Unlock target folder: /data/***
[2016-03-02 15:02:11] [Info] Job finishedLog:
[2016-03-02 15:04:40] [Info] Replicate version: 1.3.0 build R2
[2016-03-02 15:04:40] [Info] Starting backup job "Transfert"
[2016-03-02 15:04:40] [Info] Locking target folder: /data/***
[2016-03-02 15:04:40] [Info] Resume folder is "/data/*** (failed)/data"
[2016-03-02 15:04:58] [Info] p2p connect to NAS*** in 881*** network
[2016-03-02 15:04:58] [Info] Connection method: 0
[2016-03-02 15:04:58] [Info] LAN connection not available
[2016-03-02 15:04:58] [Info] Using p2p connection
[2016-03-02 15:04:58] [Info] Initializing source device
[2016-03-02 15:04:58] [Info] Sending task to source device
[2016-03-02 15:05:05] [Info] Awaiting task report
[2016-03-02 15:05:08] [Info] Received success report
[2016-03-02 15:05:08] [Info] Device initialization finished
[2016-03-02 15:05:08] [Info] Copy in progress
[2016-03-02 15:05:13] [Info] Copy finished
[2016-03-02 15:05:13] [Info] Deinitialize source device
[2016-03-02 15:05:13] [Info] Sending task to source device
[2016-03-02 15:05:15] [Info] Awaiting task report
[2016-03-02 15:05:17] [Info] Received success report
[2016-03-02 15:05:17] [Info] Device deinitialization finished
[2016-03-02 15:05:17] [Info] p2p disconnect with NAS*** in 881*** network
[2016-03-02 15:05:17] [Info] Unlock target folder: /data/***
[2016-03-02 15:05:17] [Info] Job finished
Summary:
Copy start time: 2016-03-02 15:05
Total files processed: 15731
Total files transferred: 0
Total files size: 233.98 GB
Total files size transferred: 0 B
Average speed: 0 B/s
Exit code: 0 (Ok)
Copy end time: 2016-03-02 15:05Well, all seems to be working again for me, didn't change anything on my side but all my jobs ran over the weekend...
I guess the Netgear Replicate server is feeling better again, hopefully it stays that way :-)
(and I hope it works for the other people as well...)
It would be nice if Netgear would finally enable to UPLOAD an SSH key through the GUI, that would make life easier to setup RSYNC over SSH.
But for reasons totally unclear to me there is only the option to download this key... (so you can RSYNC over SSH to a different brand NAS, but not to a Netgear NAS :-( )
Cheers!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
