tag:help.rubygems.org,2010-01-19:/discussions/problems/914-bad-response-internal-server-error-500RubyGems.org: Discussion 2012-02-23T16:56:50Ztag:help.rubygems.org,2010-01-19:Comment/138611652012-02-21T12:28:29Z2012-02-21T12:28:29Zbad response Internal Server Error 500<div><p>directly gem installing also gives similar errors:</p>
<p>gem install mysql -v '2.8.1'<br>
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>bad response Internal Server Error 500 (http://production.cf.rubygems.org/gems/mysql-2.8.1.gem)</code>
</pre></div>Kevin Wheatleytag:help.rubygems.org,2010-01-19:Comment/138611652012-02-23T06:14:05Z2012-02-23T06:14:05Zbad response Internal Server Error 500<div><p>Are you still seeing this problem?</p></div>Evan Phoenixtag:help.rubygems.org,2010-01-19:Comment/138611652012-02-23T10:06:24Z2012-02-23T10:06:24Zbad response Internal Server Error 500<div><p>Hi,</p>
<p>I eventually used a workaround by going via a different http
proxy, not sure if the fault was with the original proxy, gem, or
something in combination.</p>
<p>thanks</p>
<p>Kevin</p></div>Kevin Wheatleytag:help.rubygems.org,2010-01-19:Comment/138611652012-02-23T11:41:51Z2012-02-23T11:41:52Zbad response Internal Server Error 500<div><p>Just after I sent that.... you do a new bundle install and the
following...<br>
... lots of good installs... Using rmagick (2.13.1)<br>
Installing rspec (1.3.2)<br>
Installing rspec-rails (1.3.4)<br>
Using ruby-openid (2.1.8)<br>
Using rubytree (0.7.0)<br>
Installing shoulda (2.10.3)<br>
Installing sqlite3 (1.3.5) with native extensions<br>
Using sqlite3-ruby (1.2.5)</p>
<p>Gem::RemoteFetcher::FetchError: bad response Internal Server
Error 500 (<a href=
"http://production.cf.rubygems.org/gems/test-unit-1.2.3.gem">http://production.cf.rubygems.org/gems/test-unit-1.2.3.gem</a>)<br>
An error occured while installing test-unit (1.2.3), and Bundler
cannot continue.<br>
Make sure that <code>gem install test-unit -v '1.2.3'</code>
succeeds before bundling.</p>
<p>So everything was nicely installing and then it breaks part way
through as it turns out that was the last gem needing installing,
but that is probably coincidence. Immediately repeating the command
fails at the same point. Pointing at a different proxy and
repeating it works. Now obviously it could still be our proxy, that
has now cached a negative. But the day I had the problem I saw
others logging similar sounding issues so I wondered if it was
common issue.</p>
<p>Kevin</p></div>Kevin Wheatleytag:help.rubygems.org,2010-01-19:Comment/138611652012-02-23T16:56:49Z2012-02-23T16:56:49Zbad response Internal Server Error 500<div><p>Given that what you've got there is that S3 is returning a 500
and the problem only occurs when you use a certain proxy, I'm
certain this is an issue with your proxy only.</p></div>Evan Phoenix