Skip to content
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

Invoker domains do not work on 10.11 El Capitan #139

Closed
chrismanderson opened this issue Jun 20, 2015 · 6 comments
Closed

Invoker domains do not work on 10.11 El Capitan #139

chrismanderson opened this issue Jun 20, 2015 · 6 comments

Comments

@chrismanderson
Copy link

Seems like Invoker 1.3.2 domains do not work in 10.11 - ran invoker setup, and things seemed like they were set up properly, but cannot hit any domain with the .dev extension. I can hit the sites directly by IP.

Obviously, 10.11 is early beta, just posting this as a heads up.

@gnufied
Copy link
Contributor

gnufied commented Aug 16, 2015

We will look into this as soon as we near El Capitan release. Thank you for alerting us.

@iffyuva
Copy link
Member

iffyuva commented Oct 4, 2015

@chrismanderson i upgraded to 10.11 from 10.10, and invoker works on 10.11. can you please explain the issue that you are facing or help me in reproducing this bug? thanks.

@R167
Copy link

R167 commented Oct 10, 2015

I have been getting similar problems:
/Users/wmd/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/invoker-1.3.2/lib/invoker/power/powerup.rb:12: warning: epoll is not supported on this platform
Have tried multiple reinstalls.

@iffyuva
Copy link
Member

iffyuva commented Oct 11, 2015

i doubt if this issue is related to eventmachine again. what i have observed is: when invoker tries to connect to any of backend using em-proxy, its throwing Errno::ECONNREFUSED error. investigating more into this.

@iffyuva
Copy link
Member

iffyuva commented Oct 19, 2015

@chrismanderson @R167 your issue might be related to #154 please make sure that your servers are not running in ipv6 mode.

to test this on osx, please run this command:

 lsof -iTCP -sTCP:LISTEN -P

and make sure that type is IPv4. thanks to @emilsoman for pointing this out :)

@iffyuva
Copy link
Member

iffyuva commented Oct 19, 2015

im closing this issue, please re-open this issue if the problem still persists.

@iffyuva iffyuva closed this as completed Oct 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants