Thanks Cliff! Note: the server question you wondered would have been the details how exactly (commands&config( you do "syncd is enabled and started at boot with the rsyncd.conf". Because in that might lay the details we need.
I was setting up a server on my own aligned to your config. The following makes it easy for everyone to try to re-create as it is just copy&paste to get it working - it will work on a fresh install of any Ubuntu with rsync installed. Summary: Host 20.10 - Rsync 3.2.1 Client 20.04 - Rsync 3.1.3 #1 Setup on the Host to prep, config and debug-start rsyncd as demon: # Something to sync mkdir /mnt/testrsync touch /mnt/testrsync/testfile mkdir /mnt/testrsync/testdir touch /mnt/testrsync/testdir/testfile2 # Config cat << EOF > /etc/rsyncd.conf pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [test_dir] path = /mnt/testrsync comment = Test Directory uid = ubuntu gid = ubuntu read only = no list = yes hosts allow = 10.253.194.0/24 auth users = ubuntu secrets file = /etc/rsyncd.scrt strict modes = false EOF cat << EOF > /etc/rsyncd.scrt ubuntu:ubuntu EOF # Start with max debug in local console rsync -vv --daemon --config /etc/rsyncd.conf --no-detach #2 Then on the client try to connect mkdir /mnt/client export RSYNC_PASSWORD=ubuntu rsync -vurptC rsync://[email protected]/test_dir /mnt/client receiving incremental file list ./ testfile testdir/ testdir/testfile2 sent 77 bytes received 218 bytes 590.00 bytes/sec total size is 0 speedup is 0.00 Works just fine, at the same time the server says: $ rsync -vv --daemon --config /etc/rsyncd.conf --no-detach --log-file=/dev/stdout 2020/07/28 05:55:52 [7940] rsyncd version 3.2.1 starting, listening on port 873 2020/07/28 05:56:21 [7942] connect from f.lxd (10.253.194.30) 2020/07/28 05:56:21 [7942] rsync allowed access on module test_dir from f.lxd (10.253.194.30) In my case (just like in yours) it recognizes the configured module "test_dir" in my case "Bin_dir" in yours. From there it finds all the content and syncs it. Your error suggests a chroot issue that I can't reproduce even with that setup close to yours. I added "use chroot = yes" to the daemon config but it behaves the same. Might on your upgrade anything else have changed that influences this - like under which user the daemon runs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
