According to http://mirrorstats.gentoo.org/rsync/ it's delayed by a few days. This is a gentoo portage mirror. rsync8.de.gentoo.org gentoo64.net Server Address : 188.165.231.20 / 2001:41d0:2:b214::1 Contact : rsync@gentoo64.net Hardware : Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz, 8G RAM Bandwidth : 200Mbps receiving incremental file list timestamp.chk Number of files: 1 Number of files transferred: 1 Total file size: 32 bytes Total transferred file size: 32 bytes Literal data: 32 bytes Matched data: 0 bytes File list size: 27 File list generation time: 0.001 seconds File list transfer time: 0.000 seconds Total bytes sent: 98 Total bytes received: 417 sent 98 bytes received 417 bytes 1030.00 bytes/sec total size is 32 speedup is 0.06 >>> Starting rsync with rsync://188.165.231.20/gentoo-portage... >>> Checking server timestamp ... >>> >>> SERVER OUT OF DATE: rsync://188.165.231.20/gentoo-portage >>> >>> In order to force sync, remove '/world/gentoo/portage/metadata/timestamp.chk'. >>> >>> Retrying... >>> Starting retry 1 of 20 with rsync://134.147.32.114/gentoo-portage
Ole, can you check on this, please.
Hi, there seem to be some problems syncing via v6: Started update at Thu Nov 10 14:35:01 CET 2011 [Receiver] io timeout after 300 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(140) [Receiver=3.0.8] End: Thu Nov 10 14:41:01 CET 2011 Started update at Thu Nov 10 15:05:01 CET 2011 rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(760) [Receiver=3.0.8] End: Thu Nov 10 15:05:01 CET 2011 I switched to IPv4 for now, which seems to work properly, and will keep an eye on the issue.
(In reply to comment #2) > I switched to IPv4 for now, which seems to work properly, and will keep an eye > on the issue. Never found out what that issue was, maybe a bad v6 route at the time?
