Wayne Rasmussen
Cadet
- Joined
- Mar 18, 2014
- Messages
- 5
FYI please read all before you summarily dismiss because there are no hardware details - which are irrelevant as you will see.
I recently set up FreeNAS-9.2.1.2-RELEASE-x64 (002022c) on two machines connected via a LAN and validated Replication worked as expected. I then changed the SSH port from standard 22 to another (outside reserved space) and the IP address of the replication server to its DNS name. Changed the appropriate firewall setting to ensure the new port was routed to the replication server - firewall log subsequently showed incoming request on expected port. I deleted and recreated the replication task to ensure Remote hostkey could be repopulated correctly (correct Remote hostname is shown in Remote host key after scan) via SSH Key Scan (this button is only available during task creation). Replication no longer worked even with "Initialize Remote side for once set.", which also did not clear between invocations (pressing OK button and checking again).
What did return things back to "expected behavior" was deleting /data/ssh/replication after which the initialization worked as expected - I had tried many other permutations before deleting this file including deleting and recreating the ZFS Dataset on the replication server (which included deleting the previous successful snapshot transfers when done via the LAN), changing port back to 22, using external IP address of replication server vs DNS name.
I do not know the full ramifications (beyond having to retransmit the entire dataset) of deleting /data/ssh/replication (a file) but do know it worked for me, as such it MAY (when there is only one dataset involved) be a reasonable step to add to the trouble shooting section for replication.
I recently set up FreeNAS-9.2.1.2-RELEASE-x64 (002022c) on two machines connected via a LAN and validated Replication worked as expected. I then changed the SSH port from standard 22 to another (outside reserved space) and the IP address of the replication server to its DNS name. Changed the appropriate firewall setting to ensure the new port was routed to the replication server - firewall log subsequently showed incoming request on expected port. I deleted and recreated the replication task to ensure Remote hostkey could be repopulated correctly (correct Remote hostname is shown in Remote host key after scan) via SSH Key Scan (this button is only available during task creation). Replication no longer worked even with "Initialize Remote side for once set.", which also did not clear between invocations (pressing OK button and checking again).
What did return things back to "expected behavior" was deleting /data/ssh/replication after which the initialization worked as expected - I had tried many other permutations before deleting this file including deleting and recreating the ZFS Dataset on the replication server (which included deleting the previous successful snapshot transfers when done via the LAN), changing port back to 22, using external IP address of replication server vs DNS name.
I do not know the full ramifications (beyond having to retransmit the entire dataset) of deleting /data/ssh/replication (a file) but do know it worked for me, as such it MAY (when there is only one dataset involved) be a reasonable step to add to the trouble shooting section for replication.