tag:help.rubygems.org,2010-01-19:/discussions/problems/715-too-many-connection-resetsRubyGems.org: Discussion 2017-04-12T18:13:50Ztag:help.rubygems.org,2010-01-19:Comment/95063812011-08-24T02:38:00Z2011-08-24T02:38:03Ztoo many connection resets<div><p>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:<br>
Using guard-spork (0.2.1)<br>
/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 (<a href=
"http://production.cf.rubygems.org/gems/haml-3.1.1.gem">http://production.cf.rubygems.org/gems/haml-3.1.1.gem</a>)
(Gem::RemoteFetcher::FetchError)</p>
<p>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.</p></div>Ryan Hankstag:help.rubygems.org,2010-01-19:Comment/95063812011-08-24T03:30:05Z2011-08-24T03:30:06Ztoo many connection resets<div><p>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.</p></div>provost.designtag:help.rubygems.org,2010-01-19:Comment/95063812011-08-26T05:49:56Z2011-08-26T05:49:56Ztoo many connection resets<div><p>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.</p></div>Gabriel Hornertag:help.rubygems.org,2010-01-19:Comment/95063812011-08-31T16:44:19Z2011-08-31T16:44:22Ztoo many connection resets<div><p>Hi,</p>
<p>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</p>
<p>steps to reproduce</p>
<p>gem push alacrity_client-0.0.1.gem</p>
<p>Pushing gem to <a href=
"https://rubygems.org">https://rubygems.org</a>...</p>
<p>[.. a couple of invalid gemspec warnings]</p>
<p>ERROR: While executing gem ...
(Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>too many connection resets (https://rubygems.org/api/v1/gems)</code>
</pre></div>Sean Reillytag:help.rubygems.org,2010-01-19:Comment/95063812011-08-31T20:59:04Z2011-09-23T14:58:37Ztoo many connection resets<div><p>getting this with gem, no bundler involved:</p>
<pre>
<code> +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)</code>
</pre>
<p>using:</p>
<pre>
<code> +1548+> gem --version
1.8.10</code>
</pre></div>gerrit.riessentag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T04:52:28Z2011-09-01T04:52:29Ztoo many connection resets<div><p>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.</p>
<p>$ rake release has_moderated 0.0.1 built to
pkg/has_moderated-0.0.1.gem<br>
Tagged v0.0.1<br>
Pushed git commits and tags<br>
Untagged v0.0.1 due to error<br>
rake aborted!<br>
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>too many connection resets (https://rubygems.org/api/v1/gems)</code>
</pre>
<p>Pushing gem to <a href=
"https://rubygems.org">https://rubygems.org</a>...</p>
<p>Tasks: TOP => release<br>
(See full trace by running task with --trace)</p>
<p>or with gem push:</p>
<p>$ gem push has_moderated-0.0.1.gem Pushing gem to <a href=
"https://rubygems.org">https://rubygems.org</a>...<br>
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>too many connection resets (https://rubygems.org/api/v1/gems)</code>
</pre>
<p>trace from rake release:</p>
<p>ERROR: While executing gem ...
(Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>too many connection resets (https://rubygems.org/api/v1/gems)</code>
</pre>
<p>Pushing gem to <a href=
"https://rubygems.org">https://rubygems.org</a>...<br>
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:135:in
<code>sh'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:74:in</code>rubygem_push'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:67:in
<code>release_gem'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:114:in</code>tag_version'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:65:in
<code>release_gem'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/bundler-1.0.18/lib/bundler/gem_helper.rb:38:in</code>install'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:205:in
<code>call'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:205:in</code>execute'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:200:in
<code>each'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:200:in</code>execute'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:158:in
<code>invoke_with_call_chain'
/home/mrbrdo/.rvm/rubies/ruby-1.8.7-p334/lib/ruby/1.8/monitor.rb:242:in</code>synchronize'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:151:in
<code>invoke_with_call_chain'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/task.rb:144:in</code>invoke'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:112:in
<code>invoke_task'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:in</code>top_level'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:in
<code>each'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:90:in</code>top_level'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:129:in
<code>standard_exception_handling'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:84:in</code>top_level'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:62:in
<code>run'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:129:in</code>standard_exception_handling'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/gems/rake-0.9.2/lib/rake/application.rb:59:in
<code>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:in</code>load'
/home/mrbrdo/.rvm/gems/ruby-1.8.7-p334/bin/rake:19 Tasks: TOP =>
release</p></div>mrbrdotag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T08:20:10Z2011-09-23T14:58:36Ztoo many connection resets<div><p>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).</p>
<p>Backtrace:</p>
<p>$ gem push -V --backtrace izzup-0.0.1.gem GET <a href=
"http://rubygems.org/latest_specs.4.8.gz">http://rubygems.org/latest_specs.4.8.gz</a><br>
302 Found<br>
GET <a href=
"http://production.s3.rubygems.org/latest_specs.4.8.gz">http://production.s3.rubygems.org/latest_specs.4.8.gz</a><br>
200 OK<br>
Pushing gem to <a href=
"https://rubygems.org">https://rubygems.org</a>...<br>
POST <a href=
"https://rubygems.org/api/v1/gems">https://rubygems.org/api/v1/gems</a><br>
connection reset after 1 requests, retrying<br>
POST <a href=
"https://rubygems.org/api/v1/gems">https://rubygems.org/api/v1/gems</a><br>
connection reset after 1 requests, retrying<br>
ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError)</p>
<pre>
<code>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</code>
</pre></div>msharptag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T08:22:14Z2011-09-01T08:22:16Ztoo many connection resets<div><p>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.</p>
<p>after getting this error continously, i decided to check the
<em>~/.gem/credentials</em> file to see whether, perhaps, it's
corrupt:</p>
<p><code>:rubygems_api_key:
"{\"rubygems_api_key\":\"bsadsadasdasdasdasdasdas\"}"</code></p>
<p>that seemed to be incorrect, so i changed it to:</p>
<p><code>:rubygems_api_key: "bsadsadasdasdasdasdasdas"</code></p>
<p>and magically, the push worked!</p>
<p>perhaps the error message could be changed to 'your api
credentials seem to be incorrect' ....</p></div>gerrit.riessentag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T09:44:11Z2011-09-01T09:44:11Ztoo many connection resets<div><p>@gerrit.riessen solved! thanks.</p></div>msharptag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T13:40:01Z2011-09-01T13:40:01Ztoo many connection resets<div><p>@gerrit.riessen's solution worked for me too...</p></div>jabbrwckytag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T14:30:58Z2011-09-01T14:31:01Ztoo many connection resets<div><p>And for me too. I wonder what it's going on...</p></div>lucapettetag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T15:01:59Z2011-09-01T15:02:00Ztoo many connection resets<div><p>@gerrit.riessen great find! works now.</p>
<p>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.</p>
<p>I added an issue to rubygems github tracker <a href=
"https://github.com/rubygems/rubygems/issues/172">https://github.com/rubygems/rubygems/issues/172</a></p></div>mrbrdotag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T15:13:08Z2011-09-01T15:13:08Ztoo many connection resets<div><p>problem solved for me too</p>
<p>thanks gerrit, good work!</p></div>Sean Reillytag:help.rubygems.org,2010-01-19:Comment/95063812011-09-01T16:47:52Z2011-09-01T16:47:54Ztoo many connection resets<div><p>This also fixed this issue for me.</p></div>Oliver Newlandtag:help.rubygems.org,2010-01-19:Comment/95063812011-09-02T06:30:41Z2011-09-02T06:30:42Ztoo many connection resets<div><p>this seems to be addressed with <a href=
"https://github.com/rubygems/rubygems.org/issues/343">https://github.com/rubygems/rubygems.org/issues/343</a>
so hopefully it won't happen again :)</p></div>gerrit.riessentag:help.rubygems.org,2010-01-19:Comment/95063812011-09-13T12:32:09Z2011-09-13T12:32:09Ztoo many connection resets<div><p>As gerrit pointed out, the gem push issue was resolved in
<a href=
"https://github.com/rubygems/rubygems.org/issues/343">https://github.com/rubygems/rubygems.org/issues/343</a></p></div>Gabriel Horner