OK, so the directory being in /home is the culprit, I could reproduce the issue and found where the problem is. At some point rsync added
ProtectHome=on option to its service file, /lib/systemd/system/rsync.service. This has been reverted in upstream git at [1] as it's too restrictive. The fix landed in rsync v3.2.2 which is already in Debian; Ubuntu will pick it up with the next sync. In the meantime you can workaround the problem by manually disabling ProtectHome. Thanks again for reporting the issue and for providing all the details. [1] https://github.com/WayneD/rsync/commit/ce12142c459788b611da5f5d525e0486822b043a ** Changed in: rsync (Ubuntu) Status: Incomplete => Triaged ** Changed in: rsync (Ubuntu) Milestone: None => ubuntu-20.10 ** Also affects: rsync (Debian) Importance: Undecided Status: New ** Changed in: rsync (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
