Starting 2006-09-01, I noticed that /opt/gentoo-rsync/rsync-gentoo-portage.sh (of app-admin/gentoo-rsync-mirror) was no longer able to rsync against any of the gentoo rsync mirrors it tried. I was able to resolve the problem by changing the rsync options in /etc/rsync/gentoo-mirror.conf such that they (nearly) matched the same set of rsync options used by the regular "emerge --sync" command. If others have the same problem as I, then perhaps these rsync options should be included in the gentoo-rsync-mirror ebuild. Here is the working line from /etc/rsync/gentoo-mirror.conf : OPTS="--quiet --recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
Now that the problem's been described and I've provided a solution, I'll give some background information in case it proves useful to others having the same problem. 1. gentoo-rsync-mirror was working fine for me until 2006-09-01. This just so happens to be the first time it had run after updating the system to gcc-4.1.1 and glibc-2.4-r3, which had just become available in portage. After emerging the new gcc and glibc packages, I took care to perform sanity checks, including: (a) following the instructions in the Gentoo GCC upgrade guide at http://www.gentoo.org/doc/en/gcc-upgrading.xml (b) waiting until the new glibc and gcc had been emerged (c) rebooting, then "emerge -e world" (d) rebooting, rebuilding the kernel & modules, and rebooting again The problem described in this bug persisted after doing all of the above. It wasn't until I changed the rsync options that I was able to use rsync-gentoo-portage.sh successfully. 2. Pasted below is a copy of the log from /opt/gentoo-rsync/rsync-gentoo-portage.sh.log showing the error that was appearing. The rsync mirror defined in /etc/rsync/gentoo-mirror.conf was "SRC="rsync://rsync.us.gentoo.org/gentoo-portage"". I noticed this problem when I noticed that there didn't appear to have been any changes to the portage tree and that /opt/gentoo-rsync/portage/metadata/timestamp.chk was stale. ---- start of rsync-gentoo-portage.sh.log paste ---- Started update at Wed Aug 30 03:10:02 EDT 2006 End: Wed Aug 30 03:11:15 EDT 2006 Started update at Thu Aug 31 03:10:01 EDT 2006 End: Thu Aug 31 03:11:44 EDT 2006 Started update at Fri Sep 1 03:10:02 EDT 2006 rsync: on remote machine: --no-specials: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(616) [receiver=2.6.8] End: Fri Sep 1 03:14:10 EDT 2006 Started update at Sat Sep 2 03:10:01 EDT 2006 rsync: on remote machine: --no-specials: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: connection unexpectedly closed (4 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(465) [receiver=2.6.8] End: Sat Sep 2 03:13:53 EDT 2006 Started update at Sat Sep 2 18:00:42 EDT 2006 rsync: on remote machine: --no-specials: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(616) [receiver=2.6.8] End: Sat Sep 2 18:04:01 EDT 2006 Started update at Sun Sep 3 03:10:01 EDT 2006 rsync: on remote machine: --no-specials: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(616) [receiver=2.6.8] End: Sun Sep 3 03:13:15 EDT 2006 ---- end of rsync-gentoo-portage.sh.log paste ----
*** This bug has been marked as a duplicate of bug 199128 ***
