From: bjoern@...
Date: 2014-02-07T14:23:06+00:00
Subject: [ruby-core:60560] [ruby-trunk - Bug #9477] Address family not supported by protocol - socket(2) - udp

Issue #9477 has been updated by Bjoern Rennhak.


Sorry for that, misread that.

```sh
% cat /etc/resolv.conf 
nameserver 213.133.99.99
nameserver 213.133.100.100
nameserver 213.133.98.98
nameserver 2a01:4f8:0:a111::add:9898
nameserver 2a01:4f8:0:a102::add:9999
nameserver 2a01:4f8:0:a0a1::add:1010

```

----------------------------------------
Bug #9477: Address family not supported by protocol - socket(2) - udp
https://bugs.ruby-lang.org/issues/9477#change-45013

* Author: Bjoern Rennhak
* Status: Open
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-linux]
* Backport: 
----------------------------------------
On a fresh Debian GNU/Linux VServer guest running the latest RVM HEAD I experienced the following error:

```
Exception `LoadError' at /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:169 - LoadError
Exception `Errno::EAFNOSUPPORT' at /usr/local/rvm/rubies/ruby-2.1.0/lib/ruby/2.1.0/resolv.rb:744 - Address family not supported by protocol - socket(2) - udp
ERROR: While executing gem ... (Errno::EAFNOSUPPORT)
Address family not supported by protocol - socket(2) - udp
```
(Please see gist below for entire stacktrace).

After discussion on irc.freenode.org #rvm with mpapis (rvm maintainer) it turns out

```
 rvm rubygems latest-2.0
```

fixes the issue.  ```rvm rubygems head``` did not work.

Not quite sure what went wrong here and if this affects anyone who isn't running vserver.

Reference:

https://gist.github.com/anonymous/483c42ce132495271fc2
https://github.com/rubygems/rubygems/issues/803#issuecomment-33835128




-- 
http://bugs.ruby-lang.org/