On 2020-06-30 20:35, Steve Freeman wrote:
I have a local gentoo repo mirror that has been running well for
years. It is essentially the same setup as described at
https://wiki.gentoo.org/wiki/Local_Mirror except that it runs on a
non-default port.
After upgrading to net-misc/rsync-3.2.0-r1 (from rsync-3.1.3), I can
no longer emerge --sync from my clients. I receive messages such as:
# emerge --sync
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'...
>>> Starting rsync with rsync://10.10.10.10:5873/gentoo-portage...
>>> Checking server timestamp ...
opening tcp connection to 10.10.10.10 port 5873
Connected to 10.10.10.10
msg checking charset: UTF-8
sending daemon args: --server --sender -vvvvlWtprze.iLsfxCIv
--timeout=180 --safe-links --inplace .
gentoo-portage/metadata/timestamp.chk (8 args)
rsync: didn't get server startup line
[Receiver] _exit_cleanup(code=5, file=main.c, line=1777): entered
rsync error: error starting client-server protocol (code 5) at
main.c(1777) [Receiver=3.2.0]
[Receiver] _exit_cleanup(code=5, file=main.c, line=1777): about to
call exit(5)
[SNIPPED]
According to this page:
https://www.lagerhaus128.ch/?p=1281
there appears to be a bug in rsync 3.2.0 and 3.2.1 involving transfer
logging.
He provides two workarounds in /etc/rsyncd.conf. Both worked for me.
1) Disable transfer logging (commenting out "transfer logging = yes"
fixed my issue).
2) Set a log format, for example "log format = %t %a %m %f %b". This
is the option I chose.
I wanted to pass this on in case someone else runs into the problem.
Cheers.
-Steve Freeman
