gem list --remote failing on old version of rubygems

Jesse Newland's Avatar

Jesse Newland

17 Feb, 2011 02:15 PM

On 1.3.1:

$ gem list --remote passenger --verbose

*** REMOTE GEMS ***

GET 302 Found: http://rubygems.org/latest_specs.4.8.gz

On 1.5.0:

$     gem list --remote passenger --verbose

*** REMOTE GEMS ***

GET http://gemcutter.org/latest_specs.4.8.gz
302 Found
GET http://production.s3.rubygems.org/latest_specs.4.8.gz
200 OK
GET http://gems.rubyforge.org/latest_specs.4.8.gz
302 Found
GET http://production.s3.rubygems.org/latest_specs.4.8.gz
200 OK
GET http://gems.github.com/latest_specs.4.8.gz
200 OK
passenger (3.0.2 ruby)
passenger-jmazzi (2.2.10 ruby)
passenger-recipes (0.1.2 ruby)
passenger_debugger (0.1.3 ruby)
passenger_dudemeister (3.0.1 ruby)
passenger_dyno (0.0.2 ruby)

Is 1.3.x not supported anymore? If so, is there a minimum supported version documented anywhere?

  1. 1 Posted by Jesse Newland on 17 Feb, 2011 02:18 PM

    Jesse Newland's Avatar

    More output from the 1.3.1 version:

    $ gem list --remote passenger --verbose
    
    *** REMOTE GEMS ***
    
    GET 302 Found: http://rubygems.org/latest_specs.4.8.gz
    connection reset after 2 requests, retrying
    HEAD 302 Found: http://rubygems.org/specs.4.8.gz
    connection reset after 2 requests, retrying
    HEAD 302 Found: http://rubygems.org/yaml
    

    Taking around 5 minutes as of now, still nothing.

    Upgrading makes sense, of course, but it'd be nice to keep a minimum supported version documented.

  2. 2 Posted by scribblethink on 17 Feb, 2011 03:18 PM

    scribblethink's Avatar

    I'm seeing the same error after upgrading rubygems from 1.3.1 to 1.4.2:

    $ gem list --remote passenger --verbose
    
    *** REMOTE GEMS ***
    
    GET http://rubygems.org/latest_specs.4.8.gz
    302 Found
    HEAD http://rubygems.org/specs.4.8.gz
    connection reset after 2 requests, retrying
    HEAD http://rubygems.org/specs.4.8.gz
    302 Found
    HEAD http://rubygems.org/yaml
    connection reset after 2 requests, retrying
    HEAD http://rubygems.org/yaml
    302 Found
    
  3. Support Staff 3 Posted by Eric Hodel on 17 Feb, 2011 11:53 PM

    Eric Hodel's Avatar

    It appears you are having a network issue of some kind. Are you behind a proxy?

  4. Support Staff 4 Posted by Eric Hodel on 17 Feb, 2011 11:55 PM

    Eric Hodel's Avatar

    It works for me from a slow coffee-shop network:

    $ ruby -Ilib bin/gem env version
    1.3.1
    $ ruby -Ilib bin/gem list -r passenger -V
    
    *** REMOTE GEMS ***
    
    GET 302 Found: http://rubygems.org/latest_specs.4.8.gz
    GET 200 OK: http://production.s3.rubygems.org/latest_specs.4.8.gz
    passenger (3.0.2)
    passenger-jmazzi (2.2.10)
    passenger-recipes (0.1.2)
    passenger_debugger (0.1.3)
    passenger_dudemeister (3.0.1)
    passenger_dyno (0.0.2)
    
  5. 5 Posted by Jesse Newland on 18 Feb, 2011 12:14 AM

    Jesse Newland's Avatar

    Hi Eric -

    No proxy, no firewall. I'm jnewland in #rubygems if you have a sec to help me debug this further. We're seeing this from many places inside the railsmachine network (again, no proxy, no firewall).

  6. 6 Posted by Jesse Newland on 18 Feb, 2011 12:22 AM

    Jesse Newland 's Avatar

    Looking into it further, it appears to be a routing issue at Level3:

    $ ping production.s3.rubygems.org
    PING production.s3.rubygems.org (207.171.181.231) 56(84) bytes of data.
    From AMAZON.COM.car1.Seattle1.Level3.net (4.53.144.74) icmp_seq=2 Packet filtered
    

    Strange. Sorry to bother. We'll raise it with them.

  7. Support Staff 7 Posted by Eric Hodel on 18 Feb, 2011 12:30 AM

    Eric Hodel's Avatar

    Ok!

  8. Eric Hodel closed this discussion on 18 Feb, 2011 12:30 AM.

  9. Jesse Newland re-opened this discussion on 18 Feb, 2011 12:31 AM

  10. 8 Posted by Jesse Newland on 18 Feb, 2011 12:31 AM

    Jesse Newland's Avatar

    Sorry to continue to re-open, but wanted to document this here for those that may find this via search:

    S3 blocks pings in general, but this server seems to be blocked by s3:

    $ curl -I http://production.s3.rubygems.org/latest_specs.4.8.gz
    

    If you're having strange rubygems timeouts, try that. If it times out - it's a problem connecting to S3, not a problem with rubygems.

  11. 9 Posted by Jesse Newland on 18 Feb, 2011 12:41 AM

    Jesse Newland's Avatar

    Tracked it down, and notating here for teh googlez.

    This server had the following in /etc/hosts from the great rubygems.org DNS failure of June 08, 2010:

    72.4.120.124 rubygems.org
    207.171.181.231 production.s3.rubygems.org
    216.137.45.24 production.cf.rubygems.org
    

    Removing that fixed the issue. Explains this happening on multiple hosts - all those that had added this to on that day and hadn't removed it yet. Phew!

  12. Support Staff 10 Posted by Eric Hodel on 18 Feb, 2011 12:43 AM

    Eric Hodel's Avatar

    Awesome, thanks for the further information!

  13. Eric Hodel closed this discussion on 18 Feb, 2011 12:43 AM.

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

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac