2017-02-02 1 views
0

Ich versuche, einen Selenium Grid Hub auf meinem Mac zu initiieren und dann einen Knoten auf einer Windows 7 VM auch auf meinem Mac (in VirtualBox ausgeführt, wenn das wichtig ist) einzurichten. Ich verwende diesen Befehl auf dem Mac:Selen Grid Node kann keine Verbindung zum Hub herstellen

java -jar selenium-server-standalone-3.0.1.jar -role hub 

Und dann bekomme ich

Nodes should register to http://10.10.3.1:4444/grid/register/ 
Selenium Grid hub is up and running 

fantastisch, groß. Ich gehe dann in meine Windows VM und führe den folgenden Befehl aus:

java -jar selenium-server-standalone-3.0.1.jar -role webdriver -hub http://10.10.3.1:4444/grid/register -port 7777 -debug 

Es wird schließlich Timeout, keine Verbindung herstellen. Ich habe die Debug-Informationen unten eingefügt.

12:12:11.806 INFO - Selenium build info: version: '3.0.1', revision: '1969d75' 
12:12:11.806 INFO - Launching a Selenium Grid node 
12:12:12.817 DEBUG - CookieSpec selected: default 
12:12:12.827 DEBUG - Auth cache not set in the context 
12:12:12.827 DEBUG - Connection request: [route: {}->http://10.10.3.1:4444][tota 
l kept alive: 0; route allocated: 0 of 2000; total allocated: 0 of 2000] 
12:12:12.857 DEBUG - Connection leased: [id: 0][route: {}->http://10.10.3.1:4444 
][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000] 
12:12:12.887 DEBUG - Opening connection {}->http://10.10.3.1:4444 
12:12:12.887 DEBUG - Connecting to /10.10.3.1:4444 
12:12:32.753 DEBUG - http-outgoing-0: Shutdown connection 
12:12:32.753 DEBUG - Connection discarded 
12:12:32.753 DEBUG - Connection released: [id: 0][route: {}->http://10.10.3.1:44 
44][total kept alive: 0; route allocated: 0 of 2000; total allocated: 0 of 2000] 

12:12:32.753 WARN - error getting the parameters from the hub. The node may end 
up with wrong timeouts.Connect to 10.10.3.1:4444 [/10.10.3.1] failed: Connection 
timed out: connect 
2017-02-02 12:12:32.793:INFO::main: Logging initialized @22740ms 
12:12:32.881 INFO - Driver class not found: com.opera.core.systems.OperaDriver 
12:12:32.881 INFO - Driver provider com.opera.core.systems.OperaDriver registrat 
ion is skipped: 
Unable to create new instances on this machine. 
12:12:32.881 INFO - Driver class not found: com.opera.core.systems.OperaDriver 
12:12:32.881 INFO - Driver provider com.opera.core.systems.OperaDriver is not re 
gistered 
12:12:32.891 INFO - Driver provider org.openqa.selenium.safari.SafariDriver regi 
stration is skipped: 
registration capabilities Capabilities [{browserName=safari, version=, platform 
=MAC}] does not match the current platform VISTA 
2017-02-02 12:12:32.999:INFO:osjs.Server:main: jetty-9.2.15.v20160210 
2017-02-02 12:12:33.058:INFO:osjsh.ContextHandler:main: Started o.s.j.s.ServletC 
[email protected]{/,null,AVAILABLE} 
2017-02-02 12:12:33.077:INFO:osjs.ServerConnector:main: Started [email protected] 
ee2816{HTTP/1.1}{0.0.0.0:7777} 
2017-02-02 12:12:33.077:INFO:osjs.Server:main: Started @23031ms 
12:12:33.077 INFO - Selenium Grid node is up and ready to register to the hub 
12:12:33.097 DEBUG - Using the json request : {"class":"org.openqa.grid.common.R 
egistrationRequest","configuration":{"hubHost":"10.10.3.1","hubPort":4444,"id":" 
http://10.0.2.15:7777","capabilities":[{"browserName":"firefox","seleniumProtoco 
l":"WebDriver","maxInstances":5,"platform":"VISTA"},{"browserName":"chrome","sel 
eniumProtocol":"WebDriver","maxInstances":5,"platform":"VISTA"},{"browserName":" 
internet explorer","seleniumProtocol":"WebDriver","maxInstances":1,"platform":"W 
INDOWS"}],"hub":"http://10.10.3.1:4444/grid/register","nodeStatusCheckTimeout":5 
000,"proxy":"org.openqa.grid.selenium.proxy.DefaultRemoteProxy","register":true, 
"registerCycle":5000,"custom":{},"host":"10.0.2.15","maxSession":1,"debug":false 
,"port":7777,"role":"node","timeout":1800}} 
12:12:33.185 INFO - Starting auto registration thread. Will try to register ever 
y 5000 ms. 
12:12:33.185 INFO - Registering the node to the hub: http://10.10.3.1:4444/grid/ 
register 
12:12:33.215 DEBUG - CookieSpec selected: default 
12:12:33.224 DEBUG - Auth cache not set in the context 
12:12:33.224 DEBUG - Connection request: [route: {}->http://10.10.3.1:4444][tota 
l kept alive: 0; route allocated: 0 of 2000; total allocated: 0 of 2000] 
12:12:33.224 DEBUG - Connection leased: [id: 1][route: {}->http://10.10.3.1:4444 
][total kept alive: 0; route allocated: 1 of 2000; total allocated: 1 of 2000] 
12:12:33.224 DEBUG - Opening connection {}->http://10.10.3.1:4444 
12:12:33.224 DEBUG - Connecting to /10.10.3.1:4444 
12:12:54.760 DEBUG - http-outgoing-1: Shutdown connection 
12:12:54.760 DEBUG - Connection discarded 
12:12:54.760 DEBUG - Connection released: [id: 1][route: {}->http://10.10.3.1:44 
44][total kept alive: 0; route allocated: 0 of 2000; total allocated: 0 of 2000] 

12:12:54.760 INFO - Couldn't register this node: Error sending the registration 
request: Connect to 10.10.3.1:4444 [/10.10.3.1] failed: Connection timed out: co 
nnect 

* edit: Ich habe versucht, den Hub und Knoten sowohl an den Fenstern VM, und es funktionierte ohne Probleme laufen. Ich habe auch versucht, den Hub und den Knoten nur auf dem Mac auszuführen, und ich habe das gleiche Problem. Das sagt mir, dass das Problem irgendwie mit meinem Mac zusammenhängt. Keine Ahnung, was zu tun ist ....

Antwort

0

Es stellt sich heraus, der Server, bei dem Versuch, dem Hub automatisch eine IP-Adresse zuzuweisen, wählte die falsche. Aus irgendeinem Grund wählte er die IP-Adresse des VPN-Gateways. Hinzufügen von -host 10.11.xx.xx behoben mein Problem.

+1

sollten Sie vielleicht Ihre eigene Antwort annehmen –

+0

ich plane. Wenn Stapelüberlauf mich lässt. – kroe761

Verwandte Themen