Bug #9488

ruby/2.1.0/net/protocol.rb:153 - Resource temporarily unavailable - read would block

Added by jigar joshi over 1 year ago. Updated over 1 year ago.

[ruby-core:60514]
Status:Rejected
Priority:Normal
Assignee:Eric Hodel
ruby -v:2.1.0 Backport:1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN

Description

/opt/rubies/ruby-2.1.0/bin/gem env
RubyGems Environment:
- RUBYGEMS VERSION: 2.2.0
- RUBY VERSION: 2.1.0 (2013-12-25 patchlevel 0) [x86_64-linux]
- INSTALLATION DIRECTORY: /opt/rubies/ruby-2.1.0/lib/ruby/gems/2.1.0
- RUBY EXECUTABLE: /opt/rubies/ruby-2.1.0/bin/ruby
- EXECUTABLE DIRECTORY: /opt/rubies/ruby-2.1.0/bin
- SPEC CACHE DIRECTORY: /home/vagrant/.gem/specs
- RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
- GEM PATHS:
- /opt/rubies/ruby-2.1.0/lib/ruby/gems/2.1.0
- /home/vagrant/.gem/ruby/2.1.0
- GEM CONFIGURATION:
- :update_sources => true
- :verbose => true
- :backtrace => false
- :bulk_threshold => 1000
- :sources => ["http://rubygems.org/"]
- REMOTE SOURCES:
- http://rubygems.org/
- SHELL PATH:
- /usr/local/bin
- /bin
- /usr/bin
- /usr/local/sbin
- /usr/sbin
- /sbin
- /home/vagrant/bin

$ /opt/rubies/ruby-2.1.0/bin/gem list -r | grep 'foodcritic'
daptiv-foodcritic-rules (0.0.1)
foodcritic (3.0.3)
guard-foodcritic (1.0.2)
rake-foodcritic (0.0.3)
thor-foodcritic (1.1.0)

$ /opt/rubies/ruby-2.1.0/bin/gem install foodcritic --debug
Exception `LoadError' at
/opt/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:169 - LoadError
Exception `Resolv::DNS::Config::OtherResolvError' at
/opt/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:548 -
_rubygems._tcp.rubygems.org
Exception `Resolv::ResolvError' at
/opt/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:492 - DNS result has no
information for _rubygems._tcp.rubygems.org
Exception `Errno::EEXIST' at
/opt/rubies/ruby-2.1.0/lib/ruby/2.1.0/fileutils.rb:250 - File exists @
dir_s_mkdir - /home/vagrant/.gem/specs/rubygems.org%80
Exception `IO::EAGAINWaitReadable' at
/opt/rubies/ruby-2.1.0/lib/ruby/2.1.0/net/protocol.rb:153 - Resource
temporarily unavailable - read would block

what could be wrong here ?

note: googling resulted into multiple thing (didn't work)

  • could be dns issue, I reset the dns setting similar to another machine (mac) where this command worked fine
  • removed https:// from source and added http://

History

#1 Updated by Eric Hodel over 1 year ago

  • Status changed from Open to Rejected
  • Assignee set to Eric Hodel

There is no bug here. You told RubyGems to print out ever exception raised even if it is rescued. Remove the --debug flag if you are not debugging RubyGems.

Also available in: Atom PDF