Chrome Node Fails to Start in Swarm Mode

[fingermark]

Meta -

Image(s):

Docker Version: Docker version 1.12.2

I'm running the following w/ AWS EC2 instances (3 total hosts):

docker network create seleniumnet --driver overlay
docker service create --name hub --network seleniumnet -p 4444:4444 selenium/hub
docker service create --name chrome --network seleniumnet --replicas 2 selenium/node-chrome

But docker service ps chromeshows that the chrome nodes start and then fail immediately w/ a non-zero exit status. I can't see why, though.

Any ideas why the chrome nodes are failing so quickly. I've even tried allowing all TCP and UDP traffic on the subnet.

[fingermark]

docker logs 6e6f5384df1d
Not linked with a running Hub container

[ddavison]

i believe this might be related to #238

[fingermark]

I just realized I need to pass in -e HUB_PORT_4444_TCP_ADDR=hub, but I'm still seeing no nodes in the console. Going to open more ports or try the ip address.

[testphreak]

The solution suggested here #255 (comment) though not ideal, works.

[fingermark]

@testphreak thanks a lot. I'm trying that, but get

REMOTE_HOST variable is set, appending -remoteHost
Exception in thread "main" com.beust.jcommander.ParameterException: Unknown option: -remoteHost
    at com.beust.jcommander.JCommander.parseValues(JCommander.java:742)
    at com.beust.jcommander.JCommander.parse(JCommander.java:282)
    at com.beust.jcommander.JCommander.parse(JCommander.java:265)
    at com.beust.jcommander.JCommander.<init>(JCommander.java:210)
    at org.openqa.grid.selenium.GridLauncherV3$3.setConfiguration(GridLauncherV3.java:257)
    at org.openqa.grid.selenium.GridLauncherV3.buildLauncher(GridLauncherV3.java:147)
    at org.openqa.grid.selenium.GridLauncherV3.main(GridLauncherV3.java:73)

[ddavison]

that might be because you are using the latest. if you are using Latest, you need to abide by Selenium 3.0.

Try using selenium/hub and node-chrome using version 2.53.1-beryllium with that option.

[fingermark]

Here are the steps I'm using to try to get Selenium Grid + Docker connected via docker swarm in AWS. If anyone else has gotten this working, please let me know if you see anything wrong:

https://gist.github.com/fingermark/5360ec1cb6fc1a51f01985557cc76187

[fingermark]

Just wanted to add some logs. I'm now manually specifying the hub IP address based on this hub log:

19:24:36.804 INFO - Nodes should register to http://10.0.0.2:4444/grid/register/
19:24:36.804 INFO - Selenium Grid hub is up and running

Chrome node log:

12:33:14.645 INFO - Registering the node to the hub: http://10.0.0.2:4444/grid/register
12:35:14.936 INFO - Couldn't register this node: Error sending the registration request: Connect to 10.0.0.2:4444 [/10.0.0.2] failed: connect timed out

[testphreak]

Hi @ddavison, I am unable to setup a selenium grid either using swarm mode using 3.0.0-x. The approach I linked above works only with 2.53.1 images.

So what is the approach we need to abide by as you mentioned above? Do you have any suggestions for setting up a Selenium Grid in Swarm mode with 3.0.0?

Adding log from a node container -

REMOTE_HOST variable is set, appending -remoteHost
Exception in thread "main" com.beust.jcommander.ParameterException: Unknown option: -remoteHost
    at com.beust.jcommander.JCommander.parseValues(JCommander.java:742)
    at com.beust.jcommander.JCommander.parse(JCommander.java:282)
    at com.beust.jcommander.JCommander.parse(JCommander.java:265)
    at com.beust.jcommander.JCommander.<init>(JCommander.java:210)
    at org.openqa.grid.selenium.GridLauncherV3$3.setConfiguration(GridLauncherV3.java:257)
    at org.openqa.grid.selenium.GridLauncherV3.buildLauncher(GridLauncherV3.java:147)
    at org.openqa.grid.selenium.GridLauncherV3.main(GridLauncherV3.java:73)

[ddavison]

@testphreak see #307

[ddavison]

@fingermark same to you. since this appears to be your issue also, I am closing this.

Please see the comments in #307.

REMOTE_HOST has been removed. Please use SE_OPTS="-hubHost <host> -hubPort <port> instead of -remoteHost.

[testphreak]

@ddavison please review my follow up comments in #307. I am not sure if remoteHost has been removed with v3. I still see it under configuration. Appreciate the help.

[ddavison]

remoteHost = host + port therefore there isn't any reason for configuring it.

https://github.com/SeleniumHQ/selenium/blob/master/java/server/src/org/openqa/grid/internal/utils/configuration/GridNodeConfiguration.java#L69

You'll notice that the @Parameter is not configurable for this particular String.