tag:help.rubygems.org,2010-01-19:/discussions/problems/492-gem-list-remote-failing-on-old-version-of-rubygemsRubyGems.org: Discussion 2011-09-23T14:59:26Ztag:help.rubygems.org,2010-01-19:Comment/54079872011-02-17T14:15:14Z2011-09-23T14:59:25Zgem list --remote failing on old version of rubygems<div><p>On 1.3.1:</p>
<pre>
<code>$ gem list --remote passenger --verbose
*** REMOTE GEMS ***
GET 302 Found: http://rubygems.org/latest_specs.4.8.gz</code>
</pre>
<p>On 1.5.0:</p>
<pre>
<code>$ 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)</code>
</pre>
<p>Is 1.3.x not supported anymore? If so, is there a minimum
supported version documented anywhere?</p></div>Jesse Newlandtag:help.rubygems.org,2010-01-19:Comment/54079872011-02-17T14:18:00Z2011-02-17T14:18:02Zgem list --remote failing on old version of rubygems<div><p>More output from the 1.3.1 version:</p>
<pre>
<code>$ 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</code>
</pre>
<p>Taking around 5 minutes as of now, still nothing.</p>
<p>Upgrading makes sense, of course, but it'd be nice to keep a
minimum supported version documented.</p></div>Jesse Newlandtag:help.rubygems.org,2010-01-19:Comment/54079872011-02-17T15:18:27Z2011-02-17T15:18:28Zgem list --remote failing on old version of rubygems<div><p>I'm seeing the same error after upgrading rubygems from 1.3.1 to
1.4.2:</p>
<pre>
<code>$ 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</code>
</pre></div>scribblethinktag:help.rubygems.org,2010-01-19:Comment/54079872011-02-17T23:53:14Z2011-02-17T23:53:14Zgem list --remote failing on old version of rubygems<div><p>It appears you are having a network issue of some kind. Are you
behind a proxy?</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/54079872011-02-17T23:55:02Z2011-02-17T23:55:02Zgem list --remote failing on old version of rubygems<div><p>It works for me from a slow coffee-shop network:</p>
<pre>
<code>$ 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)</code>
</pre></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:14:20Z2011-02-18T00:14:21Zgem list --remote failing on old version of rubygems<div><p>Hi Eric -</p>
<p>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).</p></div>Jesse Newlandtag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:22:53Z2011-02-18T00:22:53Zgem list --remote failing on old version of rubygems<div><p>Looking into it further, it appears to be a routing issue at
Level3:</p>
<pre>
<code>$ 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</code>
</pre>
<p>Strange. Sorry to bother. We'll raise it with them.</p></div>Jesse Newland tag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:30:44Z2011-02-18T00:30:44Zgem list --remote failing on old version of rubygems<div><p>Ok!</p></div>Eric Hodeltag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:31:34Z2011-02-18T00:31:35Zgem list --remote failing on old version of rubygems<div><p>Sorry to continue to re-open, but wanted to document this here
for those that may find this via search:</p>
<p>S3 blocks pings in general, but this server seems to be blocked
by s3:</p>
<pre>
<code>$ curl -I http://production.s3.rubygems.org/latest_specs.4.8.gz</code>
</pre>
<p>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.</p></div>Jesse Newlandtag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:41:09Z2011-02-18T00:41:09Zgem list --remote failing on old version of rubygems<div><p>Tracked it down, and notating here for teh googlez.</p>
<p>This server had the following in <code>/etc/hosts</code> from
the great rubygems.org DNS failure of June 08, 2010:</p>
<pre>
<code>72.4.120.124 rubygems.org
207.171.181.231 production.s3.rubygems.org
216.137.45.24 production.cf.rubygems.org</code>
</pre>
<p>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!</p></div>Jesse Newlandtag:help.rubygems.org,2010-01-19:Comment/54079872011-02-18T00:43:53Z2011-02-18T00:43:53Zgem list --remote failing on old version of rubygems<div><p>Awesome, thanks for the further information!</p></div>Eric Hodel