Hello, For the rsync access to the official portage rsync server aka rsync://rsync1.us.gentoo.org/gentoo-portage please add my _new_ IP 213.251.190.162 (mir.zyrianes.net). I provide rsync://mir.zyrianes.net/gentoo-portage. My _old_ IP was 213.186.63.162. Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Remvoed 213.186.63.162 and added 213.251.190.162 to the access list. Report back when the mirror is syncing with the new IP, and I'll add it to the DNS roatation again. Thanks, pjp
Are you sure you have added my IP, I have the same problem : [rsync@ns819 bin]$ /usr/bin/rsync --recursive --links --perms --times --devices --delete --timeout=300 rsync://rsync1.us.gentoo.org/gentoo-portage /home/rsync/rsync-root/gentoo/portage/ gentoo-rsync.afn.org (gentoo2.afn.org) Service provided by the Open Systems Group at the University of Florida. @ERROR: access denied to gentoo-portage from ns819.ovh.net (213.251.190.162) rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(359) Thanks for the help.
I don't see any typos in the IP address. I wonder if it could be related to bug #49933
Ludovic, is this still an issue?
(In reply to comment #4) > Ludovic, > > is this still an issue? Yes, looks my results [rsync@ns819 bin]$ /usr/bin/rsync --recursive --links --perms --times --devices --delete --timeout=300 rsync://rsync1.us.gentoo.org/gentoo-portage /home/rsync/rsync-root/gentoo/portage/ gentoo-rsync.afn.org (gentoo3.afn.org) Service provided by the Open Systems Group at the University of Florida. @ERROR: access denied to gentoo-portage from ns819.ovh.net (213.251.190.162) rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(359) [rsync@ns819 bin]$ If you think it isn't a permission problem from auth server, see my rsync version below. [rsync@ns819 bin]$rsync --version rsync version 2.6.3 protocol version 28 Copyright (C) 1996-2004 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, IPv6, 64-bit system inums, 64-bit internal inums rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. [rsync@ns819 bin]$ Thanks.
Ludovic, I could not find your IP in our ACL, so I just added it this morning. Please make sure you begin to sync from rsync1.us.gentoo.org per our rsync document. After a short time period of your mirror syncing correctly, I will add it into our rotations. -Jeffrey
It works better, now I can connect and synchronise portage. Thanks Anymore, just one thing, sometime I get a timeout, see my logs: Started update at Mon Jul 25 08:13:01 CEST 2005 gentoo-rsync.afn.org (gentoo3.afn.org) Service provided by the Open Systems Group at the University of Florida. End: Mon Jul 25 08:18:07 CEST 2005 Started update at Mon Jul 25 09:13:00 CEST 2005 gentoo-rsync.afn.org (gentoo1.afn.org) Service provided by the Open Systems Group at the University of Florida. rsync error: timeout in data send/receive (code 30) at io.c(109) rsync: connection unexpectedly closed (2818136 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(359) rsync: connection unexpectedly closed (2818136 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(359) End: Mon Jul 25 09:21:26 CEST 2005 (In reply to comment #6) > Ludovic, > > I could not find your IP in our ACL, so I just added it this morning. Please > make sure you begin to sync from rsync1.us.gentoo.org per our rsync document. > After a short time period of your mirror syncing correctly, I will add it into > our rotations. > > -Jeffrey
connection unexpectedly closed errors are usually due to version mismatches. we (gentoo) have found promising results with rsync versions 2.6.5 and above.
I switch from 2.6.4 to 2.6.6 and the problem is the same, but it isn't the original subject of this bug, I'll open a new bug report if I don't find the solution in others bug reports. Thank's for all. (In reply to comment #8) > connection unexpectedly closed errors are usually due to version mismatches. we > (gentoo) have found promising results with rsync versions 2.6.5 and above.
