NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Replicate fails with error -501
Hi all,
My Replicate jobs suddenly all fail with error -501 (I can't find any info an what that means), but this is what the log in Replicate shows:
Replicate version1.3.0 build R2
Starting backup job
Locking target folder: /...
Resume folder is "....
p2p connection to nas-xy-xy (remote RN102)
X Unable to connect to nas-34-xx-yy (local RN104)
X Connect error code -501
X Please check network connection between devices
This was working fine for months since the last upgrade to 6.5.1, I'm not aware of any changes I've made in any of the configurations.
Both RN's are visible in ReadyCloud, Replicate sees both RN's in the Network tab but when starting any of the jobs to replicate from my local RN to the remote RN I get the failure message described above.
I'm very reluctant to upgrade to 6.5.2 as this was working fine on 6.5.1 for so long and I don't have really pleasant experiences from past updates...
Does anyone have similar experiences (I'm inclined to think the issue is on the Replicate Server as it happened before that jobs failed for a period but were successful after a few days without any changes on my side.
Any suggestion what error -501 means (and how to fix it)?
And if all fails, I'm getting a bit tired of the Replicate issues, does anyone have a procedure to install SSH certificates on the RN's to enable RSYNC over SSH?
Any feedback is much appreciated!
Yep, just tried that and got that working, turns out that apart from source and target settings requiring to be identical to the old job also the name of the job is critical, it has to be exactly the same as the lost job. (at the target side files are stored in a folder named after the name of the job, found that rather confusing, but anyway, once you are aware of it...)
Did that and I have my old jobs resume from where they left off, seems like I'm in business again.
Thanks for your support!
7 Replies
Replies have been turned off for this discussion
Hello TonV,
You might want to see this article: ReadyNAS: Replicate Troubleshooting.
Also, firmware version 6.5.2 is already available. I suggest updating to it.
Regards,
I would echo that you should update the firmware to 6.5.2.
There is a known issue that we may need to fix remotely or if you are comfortable with the implications of SSH you may be able to fix. Can you send in your logs so we can confirm if you're seeing that issue?
Do you also use ReadyCLOUD or just Replicate?Hi mdgm,
thanks for your help, I upgraded to 6.5.2 this morning, the upgrade went fine but it didn't fix my -501 error with Replicate.
I've just sent you the logs, please have a look. I'm fine doing some SSH stuff, as long as the instructions are detailed enough :-)
I have ReadyCloud enabled on all 3 RN's I have, but I'm actually not using it, Replicate is the tool that I'm really depending on!
Cheers,
Ton
As suspected there are a few lines from /etc/default/config/opt/p2p/conf/lnconfiguration.xml missing from /opt/p2p/conf/lnconfiguration.xml as you were running very old firmware on this box when you last did a factory default (wipes all data, settings, everything).
You could do e.g.
# cp -a /etc/default/config/opt/p2p/conf/lnconfiguration.xml /opt/p2p/conf/lnconfiguration.xml
# systemctl restart leafp2p
Wait say half a minute or so and check the status of leafp2p
# systemctl status -a leafp2p
You may then need to restart it once more (if the service is not running) and the problem should be resolved.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
