Bug in rsync-3.2.1 on current

I think I've discovered a bug in the recent upgrade of rsync in -current.

The bug only seems to show its head when you use the 'transfer logging' option in your rsyncd.conf.

To identify the problem, you can use a very basic rsyncd.conf as a test:

use chroot              = true
read only               = true

transfer logging        = true
log file                = /tmp/rsyncd.log

[test]
  path                  = /tmp

Then run the daemon:

rsync --daemon --config=</path/to/config>

As soon as you try to access the daemon with:

rsync <server-name-or-IP>::test/

you get an error:

rsync: didn't get server startup line
rsync error: error starting client-server protocol (code 5) at main.c(1675) [Receiver=3.1.3]

When you remove the 'transfer logging' line from the daemon configuration, you can access the rsync module without problem.

I reverted the rsync package back to 3.1.3, the problem goes away.

Can anyone confirm this problem? I've been able to confirm it on slackware.uk and two other -current boxes I have here in VMs.

Cheers

Originally Posted by tadgy I think I've discovered a bug in the recent upgrade of rsync in -current. The bug only seems to show its head when you use the 'transfer logging' option in your rsyncd.conf.

I found this commit in the rsync repository: Avoid crash of transfer logging w/default log format., so it's maybe already fixed in 3.2.2pre3 and you can work around this bug by setting a log format?

And when I look at the last (pre-)release dates in the commit log, I wouldn't be surprised if 3.2.2 will be released in the next days.

Originally Posted by Markus Wiesner you can work around this bug by setting a log format?

I can just stick with the previous version of rsync that I have installed now.

This is a good advertisement for the cumulative archive I have on slackware.uk, where all previous versions of packages are kept available: https://slackware.uk/cumulative/