Hosting on 206.251.252.32 I work for an ISP, CCC Communications; and we would like to mirror Gentoo. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I've added 206.251.252.32 to the access list for rsync1.us.gentoo.org. Please update your rsync cron jobs to point to rsync1.us.gentoo.org and post back here when you've done so. We'll monitor the server for a couple days to make sure things are working fine. Thanks.
Done
Can you check to see if there are any errors? The server doesn't appear to be syncing. Checked (UTC) Timestamp ================================================ 17:50:25 Wed, 30 Jul 2003 12:32:01 +0000 18:20:25 Wed, 30 Jul 2003 12:32:01 +0000 18:50:26 Wed, 30 Jul 2003 12:32:01 +0000 19:20:27 Wed, 30 Jul 2003 12:32:01 +0000 19:50:36 Wed, 30 Jul 2003 12:32:01 +0000 20:20:29 Wed, 30 Jul 2003 12:32:01 +0000
Started update at Tue Jul 29 23:00:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Tue Jul 29 23:00:03 PDT 2003 Started update at Tue Jul 29 23:30:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Tue Jul 29 23:30:01 PDT 2003 Started update at Wed Jul 30 00:00:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 00:00:01 PDT 2003 Started update at Wed Jul 30 00:30:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 00:30:03 PDT 2003 Started update at Wed Jul 30 01:00:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 01:00:03 PDT 2003 Started update at Wed Jul 30 01:30:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 01:30:03 PDT 2003 Started update at Wed Jul 30 02:00:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 02:00:01 PDT 2003 Started update at Wed Jul 30 02:30:00 PDT 2003 @ERROR: max connections (7) reached - try again later rsync: connection unexpectedly closed (67 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) End: Wed Jul 30 02:30:03 PDT 2003 etc... etc...
And now: Started update at Wed Jul 30 09:00:00 PDT 2003 rsync: failed to connect to rsync1.us.gentoo.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(89) End: Wed Jul 30 09:03:09 PDT 2003 Started update at Wed Jul 30 09:30:00 PDT 2003 rsync: failed to connect to rsync1.us.gentoo.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(89) End: Wed Jul 30 09:33:09 PDT 2003 Started update at Wed Jul 30 10:00:00 PDT 2003 rsync: failed to connect to rsync1.us.gentoo.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(89) End: Wed Jul 30 10:03:09 PDT 2003 Started update at Wed Jul 30 10:30:00 PDT 2003 rsync: failed to connect to rsync1.us.gentoo.org: Connection timed out rsync error: error in socket IO (code 10) at clientserver.c(89) End: Wed Jul 30 10:33:09 PDT 2003 etc... etc...
What ip does rsync1.us.gentoo.org resolve to?
I had checked that earlier too, rsync1.us.gentoo.org has address 128.193.0.34
traceroute 128.193.0.34 traceroute to 128.193.0.34 (128.193.0.34), 30 hops max, 38 byte packets 1 206.251.252.1 (206.251.252.1) 0.354 ms 0.241 ms 0.223 ms 2 g4-0-0.br02.sndg.ca.us.adnc.net (206.251.233.237) 0.412 ms 0.454 ms 0.306 ms 3 gigabitethernet5-0-147.hsipaccess1.SanDiego1.Level3.net (63.210.165.93) 0.654 ms 0.583 ms 0.713 ms 4 ge-6-0-0.mp1.SanDiego1.Level3.net (64.159.1.49) 1.101 ms 1.066 ms 1.077 ms 5 so-1-0-0.mp1.Seattle1.Level3.net (209.247.10.137) 28.397 ms 28.237 ms 28.258 ms 6 gig11-2.hsa2.Seattle1.level3.net (209.247.9.62) 28.689 ms 28.614 ms 28.673 ms 7 unknown.Level3.net (63.211.200.246) 31.974 ms 31.960 ms 31.931 ms 8 ptld-core2-gw.nero.net (207.98.64.9) 32.403 ms 32.390 ms 32.130 ms 9 ptld-core1-gw.nero.net (207.98.64.178) 32.322 ms 32.266 ms 32.514 ms 10 corv-core2-gw.nero.net (207.98.64.22) 34.330 ms 34.628 ms 35.385 ms 11 corv-core1-gw.nero.net (207.98.64.197) 54.109 ms 42.996 ms 35.584 ms 12 orstbrdr-gw.orst.edu (199.201.139.1) 35.124 ms 35.457 ms 35.319 ms 13 orstsw1-gw.orst.edu (128.193.6.21) 34.950 ms 36.485 ms 35.074 ms 14 * * * 15 * * * 16 * * * 17 * * * 18 * * Looks like it's a routing issue on our end. We've been making changes on our network, I'll have to check some routes and get back to this.
Looks like it dies in the same spot coming from an RoadRunner and AT&T line as well. Some more examples pulled from www.traceroute.org(to attempt connection from other networks): Router: oslo-gw1.uninett.no Command: trace 128.193.0.34 Type escape sequence to abort. Tracing the route to eagle.gentoo.oregonstate.edu (128.193.0.34) 1 no-gw.nordu.net (193.10.68.49) [AS 2603] 0 msec 0 msec 0 msec 2 sw-gw.nordu.net (193.10.68.29) [AS 2603] 8 msec 4 msec 4 msec 3 nordunet.se1.se.geant.net (62.40.103.117) [AS 2603] 8 msec 8 msec 8 msec 4 se.uk1.uk.geant.net (62.40.96.126) [AS 2603] 44 msec 44 msec 44 msec 5 uk.ny1.ny.geant.net (62.40.96.169) [AS 2603] 108 msec 108 msec 108 msec 6 198.32.11.61 [AS 2603] 112 msec 108 msec 112 msec 7 chinng-nycmng.abilene.ucaid.edu (198.32.8.82) [AS 2603] 132 msec 128 msec 132 msec 8 iplsng-chinng.abilene.ucaid.edu (198.32.8.77) [AS 2603] 140 msec 148 msec 136 msec 9 kscyng-iplsng.abilene.ucaid.edu (198.32.8.81) [AS 2603] 144 msec 140 msec 140 msec 10 dnvrng-kscyng.abilene.ucaid.edu (198.32.8.13) [AS 2603] 152 msec 156 msec 152 msec 11 pos-6-3.core0.eug.oregon-gigapop.net (198.32.163.13) [AS 2603] 184 msec 188 msec 188 msec 12 nero.eug.oregon-gigapop.net (198.32.163.151) [AS 2603] 188 msec 188 msec 196 msec 13 eugn-core1-gw.nero.net (207.98.64.168) [AS 2603] 200 msec 200 msec 216 msec 14 corv-core1-gw.nero.net (207.98.64.18) [AS 2603] 212 msec 200 msec 196 msec 15 orstbrdr-gw.orst.edu (199.201.139.1) [AS 2603] 200 msec 196 msec 200 msec 16 orstsw1-gw.orst.edu (128.193.6.21) [AS 2603] 200 msec 192 msec 188 msec *.... I can't get a trace to work successfully from anywhere.
What about tcptraceroute? rsyn1.us' firewall might be dropping it.
tcptraceroute 128.193.0.34 Selected device eth0, address 206.251.252.55, port 42135 for outgoing packets Tracing the path to 128.193.0.34 on TCP port 80, 30 hops max 1 206.251.252.1 (206.251.252.1) 0.319 ms 0.199 ms 0.198 ms 2 g4-0-0.br02.sndg.ca.us.adnc.net (206.251.233.237) 0.354 ms 0.330 ms 0.335 ms 3 gigabitethernet5-0-147.hsipaccess1.SanDiego1.Level3.net (63.210.165.93) 0.659 ms 0.586 ms 0.580 ms 4 ge-6-0-0.mp1.SanDiego1.Level3.net (64.159.1.49) 1.064 ms 1.074 ms 1.071 ms 5 so-3-0-0.mp2.Seattle1.Level3.net (209.247.9.122) 28.468 ms 28.395 ms 28.487 ms 6 gig10-2.hsa2.Seattle1.level3.net (209.247.9.94) 28.611 ms 28.604 ms 28.602 ms 7 unknown.Level3.net (63.211.200.246) 31.999 ms 32.039 ms 31.954 ms 8 ptld-core2-gw.nero.net (207.98.64.9) 32.198 ms 32.123 ms 32.296 ms 9 ptld-core1-gw.nero.net (207.98.64.178) 32.345 ms 32.549 ms 32.340 ms 10 corv-core2-gw.nero.net (207.98.64.22) 44.201 ms 226.552 ms 65.397 ms 11 corv-core1-gw.nero.net (207.98.64.197) 34.936 ms 35.204 ms 35.079 ms 12 orstbrdr-gw.orst.edu (199.201.139.1) 35.317 ms 36.108 ms 34.604 ms 13 orstsw1-gw.orst.edu (128.193.6.21) 53.021 ms 35.176 ms 35.631 ms 14 eagle.gentoo.oregonstate.edu (128.193.0.34) [closed] 34.942 ms 35.714 ms 34.948 ms I was able to tcptraceroute just fine.
My request is coming from 206.251.252.55 which reverses to gentoo.ccccom.com Perhaps that was/is the issue?
That could be a problem. What is 206.251.252.55? Only .32 is allowed access to rsync1.us.
Looks like somebody was playing w/ IP's on our server and didn't tell me. The box(our server) had 8 default GW's. I am going to smack somebody. The request is now coming from 206.251.252.32 and will always.
Started update at Wed Jul 30 15:18:43 PDT 2003 End: Wed Jul 30 15:18:55 PDT 2003 Looks like it's working now no?
OK, monitoring again.
I've added the server as rsync22.us.gentoo.org. Please update your motd to include that info. I've also subscribed chrisl@adnc.com to our low volume mirrors mailing list. Thanks for supportig Gentoo.
