The only server in rsync.ipv6.gentoo.org has a stale timestamp.chk. The same result happens on rsync against the IPv4 or IPv6 IP. -[~:$]- date Tue Apr 13 12:58:24 MST 2010 -[~:$]- rsync 81.93.240.111::gentoo-portage/metadata/timestamp.chk Welcome to flycatcher.gentoo.org / rsync.gentoo.org, rsync.ipv6.gentoo.org Server Address : 81.93.240.111, 2001:758:f00:4732::a1 Contact Name : mirror-admin@gentoo.org Hardware : 8 x Intel(R) Xeon(R) CPU E5405 @ 2.00GHz, 16084MB RAM Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Mon Apr 5 14:37:53 UTC 2010 -rw-r--r-- 32 2010/04/05 17:00:01 timestamp.chk Reproducible: Always Steps to Reproduce: PORTAGE_RSYNC_EXTRA_OPTS="-6" SYNC="rsync://rsync.ipv6.gentoo.org/gentoo-portage/" emerge --sync Actual Results: Portage will not sync due to timestamp.chk matching perpetually with the server's Expected Results: Portage should have synced This should affect the normal rsync.gentoo.org rotation. Sync failures are probably happening sporadically for all users with the default config due to this.
We need to move that service to a different host. In the meantime, I have disabled it from the rsync.gentoo.org (IPv4) rotation.
Fixed. Sorry for the trouble. %% host rsync.ipv6.gentoo.org rsync.ipv6.gentoo.org is an alias for magpie-rsync.ipv6.gentoo.org. magpie-rsync.ipv6.gentoo.org has IPv6 address 2607:f740:0:29:230:48ff:fef8:a064
