-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot start specjour (nodename nor servname provided, or not known) #12
Comments
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? |
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:
|
1 similar comment
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:
|
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. |
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..?
The text was updated successfully, but these errors were encountered: