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

Not found matching IPv4/IPv6 settings #7541

Closed
zcmgyu opened this issue Sep 6, 2019 · 5 comments
Closed

Not found matching IPv4/IPv6 settings #7541

zcmgyu opened this issue Sep 6, 2019 · 5 comments
Assignees
Labels

Comments

@zcmgyu
Copy link
Contributor

zcmgyu commented Sep 6, 2019

🐛 Bug Report

Could not start hub because not found matching IPv4/IPv6 settings.

To Reproduce

Start a Hub by source:

Screen Shot 2019-09-06 at 15 52 10

Start a Hub by built jar file:

$ java -jar selenium_server_deploy.jar hub

Result:

15:55:08.537 INFO [EventBusConfig.createBus] - Creating event bus: org.openqa.selenium.events.zeromq.ZeroMqEventBus
15:55:08.701 INFO [BoundZmqEventBus.] - XPUB binding to [binding to tcp://:4442, advertising as tcp://fe80:0:0:0:142f:99c:ee0:455b%en0:4442], XSUB binding to [binding to tcp://:4443, advertising as tcp://fe80:0:0:0:142f:99c:ee0:455b%en0:4443]
15:55:08.762 INFO [UnboundZmqEventBus.] - Connecting to tcp://fe80:0:0:0:142f:99c:ee0:455b%en0:4442 and tcp://fe80:0:0:0:142f:99c:ee0:455b%en0:4443
Exception in thread "main" java.lang.IllegalArgumentException: Unable to find event bus class: org.openqa.selenium.events.zeromq.ZeroMqEventBus
at org.openqa.selenium.grid.server.EventBusConfig.createBus(EventBusConfig.java:74)
at org.openqa.selenium.grid.server.EventBusConfig.getEventBus(EventBusConfig.java:44)
at org.openqa.selenium.grid.commands.Hub.lambda$configure$0(Hub.java:103)
at org.openqa.selenium.grid.Main.launch(Main.java:123)
at org.openqa.selenium.grid.Main.main(Main.java:100)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.openqa.selenium.grid.server.EventBusConfig.createBus(EventBusConfig.java:69)
... 4 more
Caused by: org.zeromq.ZMQException: fe80:0:0:0:142f:99c:ee0:455b%en0 not found matching IPv4/IPv6 settings : errno 49
at zmq.io.net.tcp.TcpAddress.resolve(TcpAddress.java:147)
at zmq.io.net.tcp.TcpAddress.(TcpAddress.java:40)
at zmq.io.net.Address.resolve(Address.java:93)
at zmq.SocketBase.connect(SocketBase.java:549)
at org.zeromq.ZMQ$Socket.connect(ZMQ.java:3069)
at org.openqa.selenium.events.zeromq.UnboundZmqEventBus.(UnboundEventBus.java:67)
at org.openqa.selenium.events.zeromq.BoundZmqEventBus.(BoundZmqEventBus.java:63)
at org.openqa.selenium.events.zeromq.ZeroMqEventBus.create(ZeroMqEventBus.java:35)
at org.openqa.selenium.events.zeromq.ZeroMqEventBus.create(ZeroMqEventBus.java:51)
... 9 more

Expected behavior

Could start a hub normally.
I researched how to config IPv4/IPv6 for Selenium, but seem like no description about it.
But I've found the same error log of Selenium Grid Hub on Selenium Gist.

https://gist.github.com/seleniumgists/51dad712b2cb48213c4694371315145c
https://gist.github.com/seleniumgists/4b042f7f9b3c09a58d22649f7ecf911b

Environment

OS: OSX
Language Bindings version: Java 4.0.0-alpha-3
Selenium Grid version (if applicable): 4.0.0-alpha-3

@adamgoucher
Copy link
Contributor

disabling ipv6 per https://support.nordvpn.com/Connectivity/macOS/1047410442/How-to-disable-IPv6-on-macOS.htm allowed me to get around this just now.

@thasso
Copy link

thasso commented Dec 20, 2019

Another workaround is to set the system property java.net.preferIPv4Stack to true, i.e. java -Djava.net.preferIPv4Stack=true -jar selenium_server_deploy.jar hub

@shs96c
Copy link
Member

shs96c commented Feb 17, 2020

You shouldn't need to force your machine to prefer IPv4 in 2020. @diemol can reproduce this issue on his machine, and I think we have a path to a fix in place.

@diemol
Copy link
Member

diemol commented Feb 17, 2020

Thanks for the hint @shs96c, this now works and it will be released in the next alpha.

@lock
Copy link

lock bot commented Mar 21, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants