# emerge sync >>> starting rsync with rsync://193.1.219.100/gentoo-portage... >>> checking server timestamp ... @ERROR: Unknown module 'gentoo-portage' rsync: connection unexpectedly closed (52 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189)
Brian, Is this mirror still available?
Hi Peter, Yes indeed, the mirror is still available and syncing happily. I'm not sure what exactly your script is looking at, but it lokos like it might be missing some path information - we dont (and never have) have /gentoo* - we do have: rsync://ftp.heanet.ie/pub/gentoo-portage rsync://ftp.heanet.ie/pub/gentoo Which are links to: rsync://ftp.heanet.ie/mirrors/gentoo.org-portage rsync://ftp.heanet.ie/mirrors/gentoo.org You can take a look at our most recent sync times for gentoo and other projects at: http://ftp.heanet.ie/status/ and the most recent log of rsync's output at: http://ftp.heanet.ie/pub/heanet/log/gentoo/ If you want the verbosity turned up, let me know. Brian.
Neither gentoo-portage nor gentoo-x86-portage (legacy support) seem to be available. Does everything look ok in the config files? # rsync -avz 193.1.219.100:: ftp HEAnet FTP Mirror Server pub HEAnet FTP Mirror Server pub contents mirrors HEAnet FTP Mirror Server mirrors contents debian Main Debian archive (64GB+) debian-non-US Debian non-US archive (1GB+) debian-cd Debian CD images (74Gb+) sourceforge SourceForge project files # rsync -avz 193.1.219.100::gentoo-portage/metadata/timestamp.chk . @ERROR: Unknown module 'gentoo-portage' rsync: connection unexpectedly closed (52 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) # rsync -avz 193.1.219.100::gentoo-x86-portage/metadata/timestamp.chk . @ERROR: Unknown module 'gentoo-x86-portage' rsync: connection unexpectedly closed (56 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189)
Ah, I see the cause of confusion. We do not make gentoo available through direct rsync targets. They are accessible within the "pub" target: $ rsync -avz 193.1.219.100::pub/gentoo-portage/metadata/timestamp.chk . Do you require us to make the various gentoo trees available via direct rsync targets, or is this approach ok? If you require an rsync target for each gentoo tree, I'm afraid it will have to wait until Monday morning at 9am UTC - we dont make weekend changes. Best regards, Brian.
Anyone rsync'ing with a mirror will be expecting a "direct" target. Typically, gentoo-x86-portage is just a link to gentoo-portage. The x86 version doesn't have anything different, it is just kept around for legacy systems. Monday is fine, just post back when you get a chance to update it. Thanks, Pete.
Hi Pete, I've added the targets. Let me know if you see any more problems. Best regards, Brian.
Thanks for adding the targets. They are working, but the timestamp seems out of sync. The current UTC time from my machine is Mon, 08 Mar 2004 22:45:05 +0000, but the timestamp contains Mon, 08 Mar 2004 10:50:00 +0000. Is the cron running OK, or are there any connection errors?
Hi Pete, I think the problem here is congestion with ftp.ibiblio.org - every half hour we try to run two rsyncs, one after another: ftp.ibiblio.org::gentoo/ rsync1.us.gentoo.org::gentoo-portage/ The ftp.ibiblio.org one is taking a very long time to complete - I see one running at the moment that is on the go now for over 8 hours. As we use lock files in our cron jobs to prevent problems, this is holding up the gentoo-portage sync. Do you have a faster candidate than ftp.ibiblio.org for the gentoo tree? We reach ibiblio through Abilene, and our link there is not congested (peak utilisation of about 50 Mbps out of a possible 622 Mbps), and I'm sure Abilene itself is not slow. Many thanks, Brian.
Ugh! That would be the problem. I think somewhere along the way there was a miscommunication. For the rsync mirror (portage tree), syncing is done every 1/2 hour with rsync1.us.gentoo.org. Access is restricted by IP. We have 193.1.219.88 as the IP authorized to sync. Let me know if that is incorrect and I'll update it. For source mirrors, syncing is done every 4 hours, beginning at midnight local time (local to where your server is). This is also done with a private mirror (not rsync1.us). You should have received instructions on how to connect when the mirror was established. If you don't have them, let me know and I'll send them (to <brian.boyle@heanet.ie> ?). Thanks, Pete.
Hi, I've corrected the mirror script. I've separated the two mirroring jobs up, one to run every half hour (gentoo-portage) and one to run every four hours. I did get to read the documentation on mirroring the portage and source, and the different characteristics of each, but I assumed (wrongly) that mirroring both at the higer frequency would suffice. I'll keep an eye on things today to make sure they work out. Brian.
Looks good, saw it synching today in the logs. Thanks for helping out! For Infrastructure, Jeffrey
