or Create a profile

Home → Problems →

too many connection resets

provost.design's Avatar

provost.design

23 Aug, 2011 07:55 PM

When attempting to run bundle install I continue to get:

/Users/inquisitivedzign/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/site_ruby/1.9.1/rubygems/remote_fetcher.rb:428:in `rescue in request': too many connection resets (http://production.cf.rubygems.org/quick/Marshal.4.8/hashie-1.1.0.ge...) (Gem::RemoteFetcher::FetchError)

I cannot get past this.

  1. 2 Posted by Ryan Hanks on 24 Aug, 2011 02:38 AM

    Ryan Hanks's Avatar

    My coworker and I have both also experienced this for extended periods within the last 36 hours. We've noticed this from both our work and home locations in the midwest US. Right now I'm having trouble getting passed guard-spork:
    Using guard-spork (0.2.1)
    /Users/rhanks/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/site_ruby/1.8/rubygems/remote_fetcher.rb:428:in `request': too many connection resets (http://production.cf.rubygems.org/gems/haml-3.1.1.gem) (Gem::RemoteFetcher::FetchError)

    Earlier today I was having trouble with that same gem and before it problems with abstract (1.0.0). The weird thing I noticed with abstract was that when I did "gem install abstract --version=1.0.0" it installed and I ran "bundle install" again and it then got passed that gem. Possible a coincidence.

  2. 3 Posted by provost.design on 24 Aug, 2011 03:30 AM

    provost.design's Avatar

    I am personally having issues with the engineyard gem now...everything has finally beeen able to install with bundler except for that gem...it has now been a little over 10hrs since my first failed attempt and about an hour since my last failed attempt. Funny thing is though is that it only fails with bundler...gem install engineyard works fine.

  3. Support Staff 4 Posted by Gabriel Horner on 26 Aug, 2011 05:49 AM

    Gabriel Horner's Avatar

    As this only happens with only bundler, could you provide the stacktrace of where this is happening in bundler and what bundler version? It's hard to diagnose the problem without being able to replicate it.

  4. 5 Posted by Sean Reilly on 31 Aug, 2011 04:44 PM

    Sean Reilly's Avatar

    Hi,

    I'm getting a very similar error when I try to push the first version of my gem to rubygems. Do you have connectivity issues at your end or is this a problem with my gem

    steps to reproduce

    gem push alacrity_client-0.0.1.gem

    Pushing gem to https://rubygems.org...

    [.. a couple of invalid gemspec warnings]

    ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

    too many connection resets (https://rubygems.org/api/v1/gems)

  5. 6 Posted by gerrit.riessen on 31 Aug, 2011 08:59 PM

    gerrit.riessen's Avatar

    getting this with gem, no bundler involved:

     +1547+> gem push -v -v ./pkg/hitfox_coupon_api-0.0.2.gem
 GET http://gemcutter.org/latest_specs.4.8.gz
 302 Found
 GET http://production.s3.rubygems.org/latest_specs.4.8.gz
 304 Not Modified
 GET http://gems.rubyforge.org/latest_specs.4.8.gz
 302 Found
 GET http://production.s3.rubygems.org/latest_specs.4.8.gz
 304 Not Modified
 GET http://gems.github.com/latest_specs.4.8.gz
 200 OK
 GET http://rubygems.org/latest_specs.4.8.gz
 302 Found
 GET http://production.s3.rubygems.org/latest_specs.4.8.gz
 304 Not Modified
 Pushing gem to https://rubygems.org...
 POST https://rubygems.org/api/v1/gems
 connection reset after 1 requests, retrying
 POST https://rubygems.org/api/v1/gems
 connection reset after 1 requests, retrying
      ERROR:  While executing gem ... (Gem::RemoteFetcher::FetchError)
          too many connection resets (https://rubygems.org/api/v1/gems)

    using:

     +1548+> gem --version
 1.8.10

  6. 7 Posted by mrbrdo on 01 Sep, 2011 04:52 AM

    mrbrdo's Avatar

    Same problem also pushing the first version of my gem (don't have any other). I don't think I did anything wrong, it builds fine.

    $ rake release has_moderated 0.0.1 built to pkg/has_moderated-0.0.1.gem
    Tagged v0.0.1
    Pushed git commits and tags
    Untagged v0.0.1 due to error
    rake aborted!
    ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

    too many connection resets (https://rubygems.org/api/v1/gems)

    Pushing gem to https://rubygems.org...

    Tasks: TOP => release
    (See full trace by running task with --trace)

    or with gem push:

    $ gem push has_moderated-0.0.1.gem Pushing gem to https://rubygems.org...
    ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

    too many connection resets (https://rubygems.org/api/v1/gems)

    trace from rake release:

    ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

    too many connection resets (https://rubygems.org/api/v1/gems)

    Pushing gem to https://rubygems.org...
    /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:135:in sh' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:74:inrubygem_push' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:67:in release_gem' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:114:intag_version' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:65:in release_gem' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:38:ininstall' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:205:in call' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:205:inexecute' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:200:in each' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:200:inexecute' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:158:in invoke_with_call_chain' /home/mrbrdo/.rvm/rubies/ruby-1.8.7-p334/lib/ruby/1.8/monitor.rb:242:insynchronize' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:151:in invoke_with_call_chain' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:144:ininvoke' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:112:in invoke_task' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:intop_level' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:in each' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:intop_level' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:129:in standard_exception_handling' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:84:intop_level' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:62:in run' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:129:instandard_exception_handling' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:59:in run' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/bin/rake:32 /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/bin/rake:19:inload' /home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/bin/rake:19 Tasks: TOP => release

  7. 8 Posted by msharp on 01 Sep, 2011 08:20 AM

    msharp's Avatar

    I've been having trouble with this all day from my workstation in Melbourne, Australia. Have also tried from an Amazon server in (US west coast).

    Backtrace:

    $ gem push -V --backtrace izzup-0.0.1.gem GET http://rubygems.org/latest_specs.4.8.gz
    302 Found
    GET http://production.s3.rubygems.org/latest_specs.4.8.gz
    200 OK
    Pushing gem to https://rubygems.org...
    POST https://rubygems.org/api/v1/gems
    connection reset after 1 requests, retrying
    POST https://rubygems.org/api/v1/gems
    connection reset after 1 requests, retrying
    ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)

    too many connection resets (https://rubygems.org/api/v1/gems)
/usr/local/lib/site_ruby/1.8/rubygems/remote_fetcher.rb:428:in `request'
/usr/local/lib/site_ruby/1.8/rubygems/gemcutter_utilities.rb:56:in `rubygems_api_request'
/usr/local/lib/site_ruby/1.8/rubygems/commands/push_command.rb:49:in `send_gem'
/usr/local/lib/site_ruby/1.8/rubygems/commands/push_command.rb:36:in `execute'
/usr/local/lib/site_ruby/1.8/rubygems/command.rb:278:in `invoke'
/usr/local/lib/site_ruby/1.8/rubygems/command_manager.rb:147:in `process_args'
/usr/local/lib/site_ruby/1.8/rubygems/command_manager.rb:117:in `run'
/usr/local/lib/site_ruby/1.8/rubygems/gem_runner.rb:65:in `run'
/usr/bin/gem:21

  8. 9 Posted by gerrit.riessen on 01 Sep, 2011 08:22 AM

    gerrit.riessen's Avatar

    i just discovered what fixed the problem for me. i wanted to post my first gem and having created a account, gem asked me for my password when i did my push. after that it never asked again --> gem obviously created an api key and stored it somewhere.

    after getting this error continously, i decided to check the ~/.gem/credentials file to see whether, perhaps, it's corrupt:

    :rubygems_api_key: "{\"rubygems_api_key\":\"bsadsadasdasdasdasdasdas\"}"

    that seemed to be incorrect, so i changed it to:

    :rubygems_api_key: "bsadsadasdasdasdasdasdas"

    and magically, the push worked!

    perhaps the error message could be changed to 'your api credentials seem to be incorrect' ....

  9. 10 Posted by msharp on 01 Sep, 2011 09:44 AM

    msharp's Avatar

    @gerrit.riessen solved! thanks.

  10. 11 Posted by jabbrwcky on 01 Sep, 2011 01:40 PM

    jabbrwcky's Avatar

    @gerrit.riessen's solution worked for me too...

  11. 12 Posted by lucapette on 01 Sep, 2011 02:30 PM

    lucapette's Avatar

    And for me too. I wonder what it's going on...

  12. 13 Posted by mrbrdo on 01 Sep, 2011 03:01 PM

    mrbrdo's Avatar

    @gerrit.riessen great find! works now.

    I think this is a bug in "gem push", which asks you for your credentials and generates that file. It seems like it's bugged and created this file wrong.

    I added an issue to rubygems github tracker https://github.com/rubygems/rubygems/issues/172

  13. 14 Posted by Sean Reilly on 01 Sep, 2011 03:13 PM

    Sean Reilly's Avatar

    problem solved for me too

    thanks gerrit, good work!

  14. 15 Posted by Oliver Newland on 01 Sep, 2011 04:47 PM

    Oliver Newland's Avatar

    This also fixed this issue for me.

  15. 16 Posted by gerrit.riessen on 02 Sep, 2011 06:30 AM

    gerrit.riessen's Avatar

    this seems to be addressed with https://github.com/rubygems/rubygems.org/issues/343 so hopefully it won't happen again :)

  16. Support Staff 17 Posted by Gabriel Horner on 13 Sep, 2011 12:32 PM

    Gabriel Horner's Avatar

    As gerrit pointed out, the gem push issue was resolved in https://github.com/rubygems/rubygems.org/issues/343

  17. Gabriel Horner closed this discussion on 13 Sep, 2011 12:32 PM.

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

10 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

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
04 Aug, 2012 05:46 PM No registration email received
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?