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 bac...
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!
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.
Hi mdgm,
I did exactly what you described and after the second restart leafp2p was up and running again.
However I still didn't see the source RN in Replicate, turned out it had unregistered, so I registered again (in the Cloud tab, Replicate was 'on' but no user registered) and that made my primary RN visible in the Replicate app again.
Then I started one of the existing jobs in Replciate (they were all shown) and that suddenly made all my jobs disappear! So my theory is that I was looking at a cached page but once I clicked a job Replicate updated the job list to the clean one. And I can only speculate why, I assume it is because I had to reregister from my broken RN (but that should not have cleared this list!).
I've created a simple Replicate job and can see that this job is working again, so the error -501 is gone for now, but now I'm stuck with my reals jobs being gone.
If I recreate them I again it would mean I need to copy all data again to my remote RN, that is simply not feasible with my slow upload speed...
So now my question is: is there a way to recover or recreate these lost jobs?
Cheers,
Tonv
Can you try recreating the job with the same name and the same settings?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
