We at Planet Mirror are still getting access denied to sync gentoo archive. Can you please check to see if our Host: tiktok.planetmirror.com and IP: 203.16.234.17 is allowed by your rsync config and firewall. RUNNING: rsync -rltvH --stats --numeric-ids rsync1.us.gentoo.org::gentoo-portage/ ERROR: @ERROR: access denied to gentoo-portage from tiktok.planetmirror.com (203.16.234.17) rsync error: error starting client-server protocol (code 5) at main.c(1171)
Admin, Your mirror was stated to be horribly out of date previously, and attemps at contacting you were not responded to. If you could provide an IP you will be coming to, along with the IP to which the dns record should point for your rsync server, I can begin the process of getting you back into rotation.
Any update on the above comment on this bug? -Jeffrey
Bug time-out. Marking NEEDINFO for now, before closing later.
Sorry for late replay just didn't receve your previous emails.. The IP we try to rsync from is 203.16.234.17. Let us know if we halp with anything else.
This is the rsync (rsync1.us.gentoo.org) server we try to connect to from the following address 203.16.234.17
I can't connect to your rsync server, please rectify the same... $ rsync tiktok.planetmirror.com:: rsync: failed to connect to tiktok.planetmirror.com: No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8] Seems an edge router or something similar similar is blocking rsync.
I don't understand why you want to connect to our rsync server? The reason I added this request from the beginning was that WE are having problem rsyncing from your server rsync1.us.gentoo.org for the following module "gentoo-portage". The error message we are getting is @ERROR: access denied to gentoo-portage from tiktok.planetmirror.com (203.16.234.17) rsync error: error starting client-server protocol (code 5) at main.c(1171) This could mean that either your firwall is blocking planetmirror.com or you are not allowing planetmirror.com (203.16.234.17) to sync on your rsync.conf file. I hope you know what I mean. Let us know if we can help with anything. thanks & regards Planet Mirror Team
(In reply to comment #7) > I don't understand why you want to connect to our rsync server? We need to connect to your server to verify the timestamp. We can't add your server until we verify it's syncing correctly from anywhere I have added the ip you mentioned into our ACL. It should take about an hour to update to rsync1.us.g.o to which you can begin syncing. But please be advised, that we need to be able to connect to your server (in other words, you can't restrict it to just .au domains) for us to verify its up to date. -Jeffrey # rsync2.au PROBATION :: planet mirror admins :: bugs@planetmirror.com 203.16.234.17
Ah ok.... I understand.. Our mirror is not restricted to anybody.. everyone from all around the world can connect to it. All opensource is available as modules to rsync. rsync rsync.planetmirror.com::gentoo/ thank you very much and have a great day. Planet Mirror Team.
IP: rsync.planetmirror.com Checked at (UTC) Timestamp ================================================ 14:58:22 Sat, 03 Jun 2006 14:50:01 +0000 Seems okay.
IP: rsync.planetmirror.com Checked at (UTC) Timestamp ================================================ 09:10:44 Tue, 06 Jun 2006 08:50:01 +0000 Seems fine, closing bug.
Hi, We are getting these errors now! rsync error: timeout in data send/receive (code 30) at io.c(171) [sender=2.6.8] rsync: connection unexpectedly closed (3514409 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync: connection unexpectedly closed (3514409 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync error: timeout in data send/receive (code 30) at io.c(171) [sender=2.6.8] rsync: connection unexpectedly closed (3514142 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync: connection unexpectedly closed (3514142 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Running: rsync -rltvH --stats --numeric-ids --delete --max-delete=500 rsync1.us.gentoo.org::gentoo-portage/ please attend to this as soon as possible. Thank you Planet Mirror
IP: rsync.planetmirror.com Checked at (UTC) Timestamp ================================================ 17:42:16 Sat, 15 Jul 2006 17:20:01 +0000 Seems okay. Are you still seeing these errors?
Seems to be working now. Thank you.
Hi we are getting these errors again. rsync error: timeout in data send/receive (code 30) at io.c(171) [sender=2.6.8] rsync: connection unexpectedly closed (3568674 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(434) rsync: connection unexpectedly closed (3568674 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(434) Can you please attend to this ASAP and find out what the problem because this has been happening alot now. Running: rsync -rltvH --stats --numeric-ids --delete --max-delete=500 rsync1.us.gentoo.org::gentoo-portage/ regards Planet Mirror
Planet Mirror, Please upgrade to the latest version of rsync, namely 2.6.9, which was just released some days ago. This has shown success for our other mirrors. -jforman
Mirror still seems several days off. Please get that working and we can work on getting you back into the rsync.au.gentoo.org rotation. Thanks, Jeffrey IP: rsync.planetmirror.com Checked at (UTC) Timestamp ================================================ 20:51:55 Mon, 25 Dec 2006 21:50:01 +0000 jforman@napa ~/gentoo $ date -u Fri Dec 29 20:52:08 UTC 2006
I believe that the mirror freshness issue is now resolved. I should note that with rsync 2.6.9, errors such as those in comment #12 are still appearing, but it seems to be syncing ok. Regards, Robert.
Closing.
