or Create a profile

Home → Problems →

Network connectivity issues

Eirik Dentz Sinclair's Avatar

Eirik Dentz Sinclair

13 Feb, 2013 08:13 PM

Initially I opened an issue here:
https://github.com/rubygems/bundler-api/issues/31

But I think the real issue is that bundler has an agressive timeout policy and there are some slow network hops between me and rubygems.org. I'm not sure if this is something I need to take up with my ISP (AT&T) or if there is something misconfigured in the rubygems.org DNS but I'm seeing the following traceroute results:

traceroute production.cf.rubygems.org
traceroute: Warning: production.cf.rubygems.org has multiple addresses; using 205.251.253.113
traceroute to d2chzxaqi4y7f8.cloudfront.net (205.251.253.113), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 1.676 ms 1.499 ms 1.431 ms 2 108-69-248-2.lightspeed.frokca.sbcglobal.net (108.69.248.2) 28.570 ms 23.974 ms 23.170 ms 3 * * * 4 * * * 5 * * * 6 12.83.77.137 (12.83.77.137) 25.264 ms 12.83.77.145 (12.83.77.145) 24.091 ms 23.420 ms 7 gar23.sffca.ip.att.net (12.122.114.5) 28.553 ms 27.851 ms 28.208 ms 8 * 192.205.32.210 (192.205.32.210) 144.307 ms * 9 vlan60.csw1.sanjose1.level3.net (4.69.152.62) 78.354 ms 77.415 ms vlan80.csw3.sanjose1.level3.net (4.69.152.190) 78.699 ms 10 ae-72-72.ebr2.sanjose1.level3.net (4.69.153.21) 77.075 ms
ae-92-92.ebr2.sanjose1.level3.net (4.69.153.29) 79.193 ms ae-82-82.ebr2.sanjose1.level3.net (4.69.153.25) 78.740 ms 11 ae-3-3.ebr1.denver1.level3.net (4.69.132.58) 79.252 ms 76.445 ms 79.950 ms
12 ae-1-100.ebr2.denver1.level3.net (4.69.151.182) 77.541 ms 79.087 ms 77.903 ms
13 ae-3-3.ebr1.chicago2.level3.net (4.69.132.62) 79.283 ms 77.847 ms 78.821 ms
14 * * *
15 amazon.com.edge4.chicago3.level3.net (4.53.98.78) 105.450 ms 81.501 ms 77.852 ms
16 server-205-251-253-113.ind6.r.cloudfront.net (205.251.253.113) 80.773 ms 79.363 ms 81.475 ms

I'm not sure if anyone else is seeing these issues, but any suggestions you can provide would be appreciated.

thanks

Eirik Dentz Sinclair

  1. 2 Posted by Eirik Dentz Sinclair on 13 Feb, 2013 08:18 PM

    Eirik Dentz Sinclair's Avatar

    attaching traceroute output since it got mangled a bit above

  2. 3 Posted by deric on 14 Feb, 2013 09:10 AM

    deric's Avatar

    I had similar issues when performing bundle update. Two times the update was canceled due to connection errors. Third try went fine.

    Gem::RemoteFetcher::FetchError: too many connection resets (http://bb-m.rubygems.org/gems/jquery-ui-rails-4.0.1.gem)
    An error occurred while installing jquery-ui-rails (4.0.1), and Bundler cannot continue.

    I guess that everyone is upgrading to get the patches for rails and JSON and rubygems servers are overloaded.

  3. Support Staff 4 Posted by Nick Quaranto on 08 May, 2013 12:43 AM

    Nick Quaranto's Avatar

    Looks like some temporary connection issues. Sorry everyone :(

  4. Nick Quaranto closed this discussion on 08 May, 2013 12:43 AM.

Comments are currently closed for this discussion. You can start a new one.

3 people watching.

  • New Issue

  • Conversation Started

  • The discussion is closed

    No more actions from RubyGems.org or the discussion starter are required.

  • Re-open the discussion

Recent Discussions

04 Aug, 2012 05:46 PM No registration email received
21 May, 2013 11:33 PM Many connectivity errors from production.cf.rubygems.org
10 Oct, 2012 12:56 AM Can't create a new user account
08 May, 2013 07:56 AM Connection reset while pushing gem
13 May, 2013 06:18 PM Redirect Loop when Downloading Rubygems

Recent Articles

Supporter FAQ
Gem ownership
Installing gems with no network
Removing a published RubyGem
Why do I get HTTP Response 302 or 301 when installing a gem?