sandro/specjour

Cannot start specjour (nodename nor servname provided, or not known)

txus opened this issue · 5 comments

txus commented

Looking for managers...
(druby://192.168.1.51:50283) /Users/txus/.rvm/gems/ruby-1.8.7-head@rails3/gems/specjour-0.3.0.rc5/lib/specjour/socket_helper.rb:4:in `getaddrinfo': getaddrinfo: nodename nor servname provided, or not known (SocketError)

I get this error when running "specjour". Should I specify any special arguments, or do something else..?

Looks like specjour is having issues resolving the ip from the hostname. I think someone else had this issue but I haven't been able to reproduce it on my local networks. Do you still encounter the issue when you disconnect from the network?

DRb connects via hostname if IP can't be resolved

Closed by 217c2c4
Closed by 217c2c4

coop commented

I am still experiencing this problem although I think it might be related to my machine (but not really sure). I took at a look at the commit messages and ticket 16 was referenced so I took a look there and sandro suggested the following to require 'socket' and make the connection manually (to test). My console fails when I try that:

ruby-1.9.2-p0 > require 'socket'
 => nil 
ruby-1.9.2-p0 > Socket.getaddrinfo(Socket.gethostname, nil, Socket::AF_INET,     Socket::SOCK_STREAM)
SocketError: getaddrinfo: nodename nor servname provided, or not known
        from (irb):2:in `getaddrinfo'
        from (irb):2
        from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-    3.0.3/lib/rails/commands/console.rb:44:in `start'
    from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-3.0.3/lib/rails/commands/console.rb:8:in `start'
    from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-3.0.3/lib/rails/commands.rb:23:in `<top (required)>'
    from script/rails:6:in `require'
    from script/rails:6:in `<main>'
coop commented

I am still experiencing this problem although I think it might be related to my machine (but not really sure). I took at a look at the commit messages and ticket 16 was referenced so I took a look there and sandro suggested the following to require 'socket' and make the connection manually (to test). My console fails when I try that:

ruby-1.9.2-p0 > require 'socket'
 => nil 
ruby-1.9.2-p0 > Socket.getaddrinfo(Socket.gethostname, nil, Socket::AF_INET,     Socket::SOCK_STREAM)
SocketError: getaddrinfo: nodename nor servname provided, or not known
        from (irb):2:in `getaddrinfo'
        from (irb):2
        from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-    3.0.3/lib/rails/commands/console.rb:44:in `start'
    from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-3.0.3/lib/rails/commands/console.rb:8:in `start'
    from /Users/sheldon/.rvm/gems/ruby-1.9.2-p0/gems/railties-3.0.3/lib/rails/commands.rb:23:in `<top (required)>'
    from script/rails:6:in `require'
    from script/rails:6:in `<main>'

Did you try running against the master branch directly? I think that commit fixes the problem but I haven't pushed out an updated gem yet so you'll have to reference the git repo in your Gemfile.