Home → Problems →

bad response Internal Server Error 500

Admin Functions

• Remove

Kevin Wheatley

21 Feb, 2012 12:07 PM

Hi,

just trying a new bundle install of some gems and I'm getting:

bad response Internal Server Error 500 (http://production.cf.rubygems.org/gems/rubytree-0.5.3.gem)

for at least two separate gems (rubytree and sqlite3-ruby)

is there a 'server'/CDN problem as this normally works.

Thanks

Kevin

1. 2 Posted by Kevin Wheatley on 21 Feb, 2012 12:28 PM

   

   directly gem installing also gives similar errors:

   gem install mysql -v '2.8.1'
   ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

   bad response Internal Server Error 500 (http://production.cf.rubygems.org/gems/mysql-2.8.1.gem)
   

   Admin Functions

   • Split
   • Remove

2. Support Staff 3 Posted by Evan Phoenix on 23 Feb, 2012 06:14 AM

   

   Are you still seeing this problem?

   Admin Functions

   • Remove

3. 4 Posted by Kevin Wheatley on 23 Feb, 2012 10:06 AM

   

   Hi,

   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.

   thanks

   Kevin

   Admin Functions

   • Split
   • Remove

4. 5 Posted by Kevin Wheatley on 23 Feb, 2012 11:41 AM

   

   Just after I sent that.... you do a new bundle install and the following...
   ... lots of good installs... Using rmagick (2.13.1)
   Installing rspec (1.3.2)
   Installing rspec-rails (1.3.4)
   Using ruby-openid (2.1.8)
   Using rubytree (0.7.0)
   Installing shoulda (2.10.3)
   Installing sqlite3 (1.3.5) with native extensions
   Using sqlite3-ruby (1.2.5)

   Gem::RemoteFetcher::FetchError: bad response Internal Server Error 500 (http://production.cf.rubygems.org/gems/test-unit-1.2.3.gem)
   An error occured while installing test-unit (1.2.3), and Bundler cannot continue.
   Make sure that gem install test-unit -v '1.2.3' succeeds before bundling.

   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.

   Kevin

   Admin Functions

   • Split
   • Remove

5. Support Staff 6 Posted by Evan Phoenix on 23 Feb, 2012 04:56 PM

   

   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.

   Admin Functions

   • Remove

6. Evan Phoenix closed this discussion on 23 Feb, 2012 04:56 PM.

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