ReadyNAS Replicate job returning "Unable to get local p2p address" Error

[KayZak]

Hi All,

I recently purchased a second ReadyNAS RN102. Both ReadyNAS RN 102's are running on OS 6.6.0 and are on the same network.

I enabled ReadyNAS Replicate on both devices and registered them with the same ReadyNAS Replicate account. Both have static IP addresses, are a part of the same DNS server with 8.8.8.8 and 4.4.2.2 added as alternative DNS's, and IPv6 is disabled completely.

Eventually, I want to be able to move one of these devices to another location, but still have them replicate to each other.

When I create a job that is supposed to replicate some data (a small amount for test purposes) from one ReadyNAS to the other (and vice versa), I receive the below error in an email message stating, "Unable to get local p2p address".

[2016-10-25 10:57:37] [Info] Replicate version: 1.3.0 build R2
[2016-10-25 10:57:37] [Info] Starting backup job "Data Backup [2016-10-25 10h 37m AM]"
[2016-10-25 10:57:37] [Info] Locking target folder: /data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM]
[2016-10-25 10:57:38] [Info] Resume folder is "/data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM]/2016-10-25 10-39 (failed)/data"
[2016-10-25 10:57:38] [Warning] Incremental not possible
[2016-10-25 10:57:48] [Error] Unable to get local p2p address
[2016-10-25 10:57:48] [Error] Unable to get p2p local ip address
[2016-10-25 10:57:48] [Info] Unlock target folder: /data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM]
[2016-10-25 10:57:48] [Info] Job finished

No actual data from one server is transfered to the other, HOWEVER, empty folders are created to prepare for the backups every time I run the job. Please see this picture:

This implies that at least the cloud is able to communicate with the two ReadyNAS devices, but the two devices are not able to communicate with each other.

This leads me to a few questions:

1. After ReadyNAS Cloud connects to both devices, is there a point where the devices are attempting to communicate directly with each other. This would make sense. If there is a firewall issue, my firewall may be allowing the ReadyNAS Cloud to pass, but not the other ReadyNAS device. But both devices are on the same network. Idk.
2. If it is a port issue, what port does ReadyCloud use to communicate?

Any tips of the trade would be highly appreciated.

[StephenB]

---

@KayZak wrote:

Both have static IP addresses, are a part of the same DNS server with 8.8.8.8 and 4.4.2.2 added as alternative DNS's, and IPv6 is disabled completely.

---

Is 4.4.2.2 a typo?  The alternative google DNS server is 8.8.4.4.

[KayZak]

Looking it up to verify, but I believe 4.4.2.2 is valid. I contacted NetGear Support they asked me to add 8.8.8.8 and 4.4.2.2. They could be wrong. God knows if a support representitive has ever been wrong.

[KayZak]

Yeah, I don't know whre 4.4.2.2 came from. I double checked, and I didn't add 4.4.2.2, although they did ask me to. Instead I added 8.8.4.4.

[KayZak]

Yeah, I don't know where 4.4.2.2 came from. I double checked, and I didn't add 4.4.2.2, although they did ask me to. Instead I added 8.8.4.4.

[mdgm-ntgr]

If you download the logs from both units and look in initrd.log was either unit running 6.1.9 or earlier after the last factory reset (wipes all data, settings, everything)?

If yes, that may suggest there's a config file which needs fixing.

[KayZak]

Here are the logs for both:

[2013/09/13 02:45:24] Factory default initiated due to new disks (no RAID, no partitions)!
[2013/09/13 02:45:29] Defaulting to X-RAID2 mode, RAID level 1
[2013/09/13 02:45:57] Factory default initiated on ReadyNASOS .
[2013/09/12 19:33:50] Updated from ReadyNASOS 6.0.0 to 6.1.2.
[2014/01/01 10:02:24] Updated from ReadyNASOS 6.1.2 to 6.1.5.
[2014/02/24 08:31:51] Updated from ReadyNASOS 6.1.5 to 6.1.6.
[2016/02/15 18:57:31] Updated from ReadyNASOS 6.1.6 () to 6.2.5 (ReadyNASOS).
[2016/02/15 19:08:41] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.4.2 (ReadyNASOS).
[2016/10/07 14:08:07] Updated from ReadyNASOS 6.4.2 (ReadyNASOS) to 6.6.0 (ReadyNASOS).

And

[2016/09/09 19:13:03] Factory default initiated by RAIDar (format used disks)!
[2016/09/09 19:13:06] Defaulting to X-RAID2 mode, RAID level 1
[2016/09/09 19:13:29] Factory default initiated on ReadyNASOS 6.0.8.
[2016/09/09 19:13:31] Factory default initiated by Frontview!
[2016/09/09 11:38:33] Updated from ReadyNASOS 6.0.8 () to 6.2.5 (ReadyNASOS).
[2016/09/09 11:51:24] Updated from ReadyNASOS 6.2.5 (ReadyNASOS) to 6.5.1 (ReadyNASOS).
[2016/09/20 10:50:35] Updated from ReadyNASOS 6.5.1 (ReadyNASOS) to 6.5.2 (ReadyNASOS).
[2016/10/06 15:31:19] Updated from ReadyNASOS 6.5.2 (ReadyNASOS) to 6.6.0 (ReadyNASOS).

They are both running 6.6.0 as I stated in my initial post. Is there a chance there is still something wrong with the file?

[StephenB]

---

@KayZak wrote:

They are both running 6.6.0 as I stated in my initial post. Is there a chance there is still something wrong with the file?

---

Right, but at the last factory reset they were running 6.0.0 and 6.0.8 (which is what @mdgm-ntgr wanted to know).

Which means something could be wrong with the file.

[KayZak]

Thanks Stephen! What steps can I take to repair that file?

[StephenB]

---

@KayZak wrote:

Thanks Stephen! What steps can I take to repair that file?

---

You'll need to wait for @mdgm-ntgr for that.  He should be back on line in a few hours.

[KayZak]

@mdgm-ntgr Hi, I just wanted to follow up and see if there is a way I can resolve my issue with the config file? Thank you!

[FramerV]

Hi KayZak,

We normally use config files in replication to find out the solution. Its not really the solution.

I would suggest you to try to get in touch with support, I checked and you still have your support available.

Contact NETGEAR Support

Regards,

[KayZak]

@FramerV Support simply runs you around in a circle, and eventually asks you to pay $75 to fix the issue. The furthest I've gotten to receiving an answer is on this forum. How do you fix the config file. Is there steps that I can take to replace that config file?