search

groupon / Selenium-Grid-Extras

Simplify the management of the Selenium Grid Nodes and stabilize said nodes by cleaning up the test environment after the build has been completed
BSD 3-Clause "New" or "Revised" License
536 stars 209 forks source link

Remote node not registering with hub #409

Open dillanmann opened 6 years ago

dillanmann commented 6 years ago

I'm having trouble with my extras node registering with the hub. I'd hoped not to have to post here but I can't get past the problem.

The config files are:

Hub Config

``` json { "port": 4445, "newSessionWaitTimeout": 25000, "servlets": [ "com.groupon.seleniumgridextras.grid.servlets.ProxyStatusJsonServlet" ], "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher", "throwOnCapabilityNotPresent": true, "nodePolling": 5000, "cleanUpCycle": 5000, "browserTimeout": 120000, "timeout": 120000, "maxSession": 5 } ```

Node Config

```json { "unregisterIfStillDownAfter": 10000, "capabilities": [ { "seleniumProtocol": "WebDriver", "browserName": "firefox", "maxInstances": 3, "version": "", "platform": "VISTA" }, { "seleniumProtocol": "WebDriver", "browserName": "internet explorer", "maxInstances": 1, "version": "11", "platform": "VISTA" }, { "seleniumProtocol": "WebDriver", "browserName": "chrome", "maxInstances": 3, "version": "67", "platform": "VISTA" } ], "custom": { "grid_extras_port": 3000 }, "nodeStatusCheckTimeout": 10000, "hubHost": "10.10.1.25", "hubPort": 4445, "downPollingLimit": 0, "proxy": "com.groupon.seleniumgridextras.grid.proxies.SetupTeardownProxy", "loadedFromFile": "node_5555.json", "port": 5555, "servlets": [], "maxSession": 3, "registerCycle": 5000, "register": true } ```

I'm using the latest version of SeleniumGridExtras (2.0.4, 15th April) for both the hub and node.

The hub is on a Windows Server (not sure version, whatever the latest is) VM and the node is a Windows 7 VM. I'm using the latest JRE (10.0.1, x64)

I've tried:

Interestingly I can start the hub and then use the selenium-server-standalone.jar (the raw selenium grid server), point it at the hub and it registers correctly and will run tests I point at the hub. My only issue with this is that I don't get the benefits of using Grid Extras this way.

Any input appreciated!

mayukhg commented 6 years ago

Facing the same issue relating to Remote node unable to register to HUB. I am using the latest version of the Selenium Grid extras (12th July,2018) Following is the error from the node log file 15:28:05.352 INFO [SeleniumServer.boot] - Welcome to Selenium for Workgroups.... 15:28:05.352 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 5555 15:28:05.352 INFO [GridLauncherV3$3.launch] - Selenium Grid node is up and ready to register to the hub 15:28:05.363 INFO [SelfRegisteringRemote$1.run] - Starting auto registration thread. Will try to register every 5000 ms. 15:28:05.363 INFO [SelfRegisteringRemote.registerToHub] - Registering the node to the hub: http://127.0.0.1:4444/grid/register 15:28:06.234 INFO [SelfRegisteringRemote$1.run] - Couldn't register this node: Error sending the registration request: The hub responded with 500

Following is my hub config { "port": 4444, "newSessionWaitTimeout": 25000, "servlets": [ "com.groupon.seleniumgridextras.grid.servlets.ProxyStatusJsonServlet" ], "capabilityMatcher": "org.openqa.grid.internal.utils.DefaultCapabilityMatcher", "throwOnCapabilityNotPresent": true, "nodePolling": 5000, "cleanUpCycle": 5000, "browserTimeout": 120000, "timeout": 120000, "maxSession": 5 }

Following is my node config { "capabilities": [ { "seleniumProtocol": "WebDriver", "browserName": "chrome", "maxInstances": 3, "version": "67", "platform": "WIN10" } ], "loadedFromFile": "node_5555.json", "proxy": "com.groupon.seleniumgridextras.grid.proxies.SetupTeardownProxy", "servlets": [], "maxSession": 3, "port": 5555, "register": true, "unregisterIfStillDownAfter": 10000, "hubPort": 4444, "hubHost": "127.0.0.1", "registerCycle": 5000, "nodeStatusCheckTimeout": 10000, "custom": { "grid_extras_port": 3000 }, "downPollingLimit": 0 }

rkieft commented 6 years ago

@mayukhg just to verify... So you have a machine (VM or physical or what so ever) that functions as a HUB and as a NODE?

mayukhg commented 6 years ago

I am trying to run on my local laptop.

I am able to launch the grid extras ui as well as the hub but when i try to register node to the hub then the error is thrown

On Mon, 16 Jul 2018 at 10:55, Richard Kieft notifications@github.com wrote:

@mayukhg https://github.com/mayukhg just to verify... So you have a machine (VM or physical or what so ever) that functions as a HUB and as a NODE?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/groupon/Selenium-Grid-Extras/issues/409#issuecomment-405151712, or mute the thread https://github.com/notifications/unsubscribe-auth/AFv_tTxRSXdCRMBkKc3i3XUXca9J-mCaks5uHCO4gaJpZM4UyCP8 .

-- Regards Mayukh Ghosh Cell:9860345364

leogcba commented 6 years ago

Is there any update on this or any workaround? I'm facing the same problem but I have the hub in a different host than the node

dillanmann commented 6 years ago

@leogcba My fix was unfortunately to just stop using Extras and just set up using the base Selenium Grid

leogcba commented 6 years ago

@leogcba My fix was unfortunately to just stop using Extras and just set up using the base Selenium Grid

What a pity! I think this project has a lot of potentials. I'll keep trying to make it work. I'll share my update or workaround, if I find any

leogcba commented 6 years ago

Hello guys! I've been performing a lot of tests regarding this bug and there seems to be something wrong with the WebDriver version. According this PRhttps://github.com/groupon/Selenium-Grid-Extras/pull/420 there are some pending changes to make Selenium Grid Extras work with version 3.14.

Also, I've been performing some tests using the version 3.12 and I still getting the same error.

But If I use the WebDriver 3.13, the node is registred as expected.

This is my selenium_grid_extras_config.json: { "theConfigMap": { "auto_update_browser_versions": "0", "hub_config_files": [], "auto_start_hub": "0", "iedriver": { "bit": "Win32", "version": "3.13.0" }, "default_role": "node", "unregisterNodeDuringReboot": "false", "chromedriver": { "bit": "32", "version": "2.42" }, "auto_update_drivers": "0", "video_recording_options": { "videos_to_keep": "5" }, "auto_start_node": "1", "hub_config": {}, "geckodriver": { "bit": "32", "version": "0.23.0" }, "log_maximum_age_ms": 864000000, "reboot_after_sessions": "3", "grid_extras_port": "3000", "webdriver": { "version": "3.13.0" }, "node_config_files": [ "node_5555.json" ] } }

Let me know if you have the same results. Hope this helps.

Regards

dillanmann commented 6 years ago

Oh excellent work @leogcba ! I hope the PR gets merged in soon, rolling my own infrastructure is a real pain, would much prefer to use Extras. I'm also not sure I'd be able to roll back to 3.13 so easily, but I'll take a look if it at least gets it working in the mean time!

dillanmann commented 6 years ago

The 'close and comment' button is extremely unintuitive, apologies for the opening/closing!

leogcba commented 6 years ago

The 'close and comment' button is extremely unintuitive, apologies for the opening/closing!

It's ok. Let me now if you can get the same behavior w/ 3.13 in the grid ;)

sureshbogireddy commented 4 years ago

im still facing the issue with 3.141.59 version ? does it not resolved yet.