Issue #10203 has been updated by Eric Wong.


 lucas / lucas-nussbaum.net wrote:
 > It might be fixed in Ruby 2.2... I don't have an easy way to test. Akira, do you have an easy way to test with Ruby 2.1?
 > 
 > If it is indeed fixed, it might be worth backporting to 2.1.
 
 It may be fixed in trunk r44497.
 Lucas: can you apply on your end and confirm?  Thanks.
 
 commit 5b0fb1aaddad03e111606e0d0eaf8ed9c9f7b0b6
 Author: nobu <nobu / b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
 Date:   Sat Jan 4 10:15:31 2014 +0000
 
     socket.c: format flags
     
     * ext/socket/socket.c (rsock_syserr_fail_host_port): use format flags,
       '+' to inspect, ' ' to quote unprintables.
     * ext/socket/socket.c (rsock_syserr_fail_path): ditto.
     * ext/socket/socket.c (rsock_syserr_fail_raddrinfo): ditto.
     
     git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@44497 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

----------------------------------------
Bug #10203: TCPServer.new has strange behaviour when EADDRINUSE without specifying hostname
https://bugs.ruby-lang.org/issues/10203#change-49389

* Author: Lucas Nussbaum
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.1.2p95
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
after:
irb(main):003:0> TCPServer::new(10001)
=> #<TCPServer:fd 9>
I get irb listening to port 10001 using IPv4, but not IPv6:
tcp        0      0 0.0.0.0:10001           0.0.0.0:* LISTEN      1000       376068      24437/irb

a second creation also works, but only binds the IPv6 address:
irb(main):004:0> TCPServer::new(10001)
=> #<TCPServer:fd 10>
tcp6       0      0 :::10001                :::* LISTEN      1000       376098      24437/irb

=> I would have expected the first creation to bind to both IPv4 and IPv6, not just IPv4, and the second attempt to fail.

Trying once again, the creation fails with a strange exception:
irb(main):007:0> TCPServer::new(10001)
TypeError: no implicit conversion of nil into String
	from (irb):7:in `initialize'
	from (irb):7:in `new'
	from (irb):7
	from /usr/bin/irb:11:in `<main>'


Binding explicitely to 0.0.0.0 avoids this:
irb(main):005:0> TCPServer::new('0.0.0.0', 10002)
=> #<TCPServer:fd 11>
irb(main):006:0> TCPServer::new('0.0.0.0', 10002)
Errno::EADDRINUSE: Address already in use - bind(2) for "0.0.0.0" port 10002
	from (irb):6:in `initialize'
	from (irb):6:in `new'
	from (irb):6
	from /usr/bin/irb:11:in `<main>'



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