| 1 |
I have a local gentoo repo mirror that has been running well for years. |
| 2 |
It is essentially the same setup as described at |
| 3 |
https://wiki.gentoo.org/wiki/Local_Mirror except that it runs on a |
| 4 |
non-default port. |
| 5 |
|
| 6 |
After upgrading to net-misc/rsync-3.2.0-r1 (from rsync-3.1.3), I can no |
| 7 |
longer emerge --sync from my clients. I receive messages such as: |
| 8 |
|
| 9 |
# emerge --sync |
| 10 |
>>> Syncing repository 'gentoo' into '/var/db/repos/gentoo'... |
| 11 |
>>> Starting rsync with rsync://10.10.10.10:5873/gentoo-portage... |
| 12 |
>>> Checking server timestamp ... |
| 13 |
opening tcp connection to 10.10.10.10 port 5873 |
| 14 |
Connected to 10.10.10.10 |
| 15 |
msg checking charset: UTF-8 |
| 16 |
sending daemon args: --server --sender -vvvvlWtprze.iLsfxCIv |
| 17 |
--timeout=180 --safe-links --inplace . |
| 18 |
gentoo-portage/metadata/timestamp.chk (8 args) |
| 19 |
|
| 20 |
rsync: didn't get server startup line |
| 21 |
[Receiver] _exit_cleanup(code=5, file=main.c, line=1777): entered |
| 22 |
rsync error: error starting client-server protocol (code 5) at |
| 23 |
main.c(1777) [Receiver=3.2.0] |
| 24 |
[Receiver] _exit_cleanup(code=5, file=main.c, line=1777): about to call |
| 25 |
exit(5) |
| 26 |
|
| 27 |
|
| 28 |
The rsyncd server shows a successful connection in the logs, and it even |
| 29 |
logs "rsync allowed access on module gentoo-portage". |
| 30 |
|
| 31 |
I've tried turning up the verbosity on both the server and client, but |
| 32 |
it doesn't really change much. |
| 33 |
|
| 34 |
Googlies such as "rsync didn't get server startup line" have turned up |
| 35 |
nothing useful at all. |
| 36 |
|
| 37 |
The rsync 3.2.0 changelog didn't help me either ( |
| 38 |
https://download.samba.org/pub/rsync/NEWS#3.2.0 ), but I suspect there |
| 39 |
must be a clue here. |
| 40 |
|
| 41 |
If I roll the server version back to rsync-3.1.3, it performs normally. |
| 42 |
Upgrading the server again to rsync-3.2.0-r1 causes it to break again. |
| 43 |
Client version appears to be irrelevant. |
| 44 |
|
| 45 |
Running rsync as a non-daemon appears to work fine regardless of |
| 46 |
server/client versions; it's only rsyncd that fails. |
| 47 |
|
| 48 |
With no useful logs or output, I'm finding this impossible to diagnose. |
| 49 |
Does anyone have any ideas? |
| 50 |
|
| 51 |
Thanks, |
| 52 |
|
| 53 |
Steve Freeman |
Archives