home | tech | misc | code | bookmarks (broken) | contact | README


rsync notes

Last update to this page was in 2019-06-18.

Troubleshooting

rsync: failed to connect to XXX.XX.X.XXX: No route to host (113)

When trying to use rsync using the rsync protocol (by using the rsync daemon on the target side), I got an error like this:

rsync: failed to connect to XXX.XX.X.XXX: No route to host (113)
rsync error: error in socket IO (code 10) at clientserver.c(124) [sender=3.0.6]

The host was reachable and rsync worked fine over ssh. What was happening? The problem is that I forgot to turn off the firewall that was blocking port 873, that the rsync protocol uses.

rsync: recv_generator: mkdir "/foo" (in share) failed: Permission denied (13)

An error like this:

rsync: recv_generator: mkdir "/foo" (in share) failed: Permission denied (13)
*** Skipping any contents from this failed directory ***

Probably means that the user that is running the daemon (options uid and gid of /etc/rsyncd.conf) don't have permissions to write to the area you specified in the /etc/rsyncd.conf file. First of all, check the permissions.

In my case, I rechecked the permissions different times and they were right. What was the problem, them? I forgot to add the necessary rules to SELinux (or disable SELinux at all) so it would allow rsync to write to the area I specified in /etc/rsyncd.conf.