goosesensor
Dabbler
- Joined
- Jan 7, 2019
- Messages
- 10
In my network I have a Microtik router running a DNS server with some names pointing to local IP addresses. For example, a workstation computer at 10.0.1.4 has a DNS record box.local This works well in general -- from any other machine I can easily reference the workstation using this name. The name is also resolvable from the FreeNAS machine. E.g. I can ssh into the FreeNAS box and do "ping box.local" or "ssh box.local" and all is well.
I have a number of Rsync Tasks setup in FreeNAS to pull from various machines periodically for backup purposes. I have these rsync tasks setup to output logs to the filesystem (using '--log-file=' option) so I can check in on them from time to time to make sure they are in fact backing up my machines. This all works fine if I put the target machine's IP addresses into the "Remote Host" field in FreeNAS's web UI (e.g. "10.0.1.4"). If I use hostname instead of IP address "Remote Host" field (e.g. "box.local") my log file indicates the following error when running the task:
2020/04/09 10:24:17 [63618] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
2020/04/09 10:24:17 [63618] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3]
Not a deal breaker by any means, but annoying regardless. Any idea what's going on here?
I have a number of Rsync Tasks setup in FreeNAS to pull from various machines periodically for backup purposes. I have these rsync tasks setup to output logs to the filesystem (using '--log-file=' option) so I can check in on them from time to time to make sure they are in fact backing up my machines. This all works fine if I put the target machine's IP addresses into the "Remote Host" field in FreeNAS's web UI (e.g. "10.0.1.4"). If I use hostname instead of IP address "Remote Host" field (e.g. "box.local") my log file indicates the following error when running the task:
2020/04/09 10:24:17 [63618] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
2020/04/09 10:24:17 [63618] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3]
Code:
2020/04/09 10:24:17 [63618] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] 2020/04/09 10:24:17 [63618] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3]
Not a deal breaker by any means, but annoying regardless. Any idea what's going on here?
