Dave Genton
Contributor
- Joined
- Feb 27, 2014
- Messages
- 133
I had been having many failures with replication lately but the issue was just too obvious. While I am digging in network checking mtu, vlan, reach-ability etc. just looking at the error message in replications as well as the email generated says the whole story. I am replicating between 10.1.1.9 and 10.1.1.7 however as you can see in screenshot of web portal and copy/paste below from email its error is because 10.1.1.99 is refusing connectivity. I am not attempting to get to 10.1.1.99 but 10.1.1.7 as configured but none the less it has 10.1.1.99 stuck on the brain somehow someway ?? I do have a VM of FreeNAS with that address I use for testing new code etc. Where/how could .99 be stuck in FreeNAS configuration ?? I have tried putting in several other IP addresses but most all of them go to .99 and fail, only every now and then does it actually go where I want it to go via the host defined. Also I am NOT using DNS on the 10 network, strictly ip addressing only and FreeNAS was just reboot prior to ensure to caching of anything dynamic being stuck.
email copy and paste:
Replication RaidZ3vol/MyData -> 10.1.1.7:RaidZ/Replications failed: Connection to 10.1.1.99 closed by remote host. Error 33 : Write error : cannot write compressed block
I have been overlooking whats right in front of me for days...
Screen shot attached.
email copy and paste:
Replication RaidZ3vol/MyData -> 10.1.1.7:RaidZ/Replications failed: Connection to 10.1.1.99 closed by remote host. Error 33 : Write error : cannot write compressed block
I have been overlooking whats right in front of me for days...
Screen shot attached.