[🐛 Bug]:Selenium grid 4 console is in loading state intermittently

[remyanekkuth]

What happened?

Have migrated to selenium grid 4 (4.1.3) and working fine. But sometimes when open the console, cannot see nodes, rather seeing " loading " message on the screen. Attached screenshot.

Whenever we see this issue, have to go to hub and restart the task for this environment and it works. But would like to get this issue fixed.

How can we reproduce the issue?

set up selenium nodes for selenium grid 4 . 
Intermittently get the loading page. 
port used to set up is 5955.

Relevant log output

Getting "loading " message in console

Operating System

windows10

Selenium version

java 8

What are the browser(s) and version(s) where you see this issue?

chrome 104, edge 104

What are the browser driver(s) and version(s) where you see this issue?

chrome driver 104.

Are you using Selenium Grid?

4.1.3

[github-actions[bot]]

@remyanekkuth, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

Can you please share the Grid logs after upgrading to 4.4.0?

[remyanekkuth]

@diemol

How to get the grid log? we have tasks configured in task scheduler and just click run to execute windows command batch script . when “loading” message comes up , not seeing anything in console.

Please help on checking the grid log

[diemol]

@remyanekkuth by the logs I mean all the output from the execution. You can also send it to a file https://www.selenium.dev/documentation/grid/configuration/cli_options/#logging

[remyanekkuth]

@diemol attaching the logs that I got. Hope this is what you asked for. https://github.com/SeleniumHQ/docker-selenium/issues/1640 looks similar to mine.

output.log output-preprod-sel4 - Copy.log

[remyanekkuth]

any update on this issue ? Please suggest what can be done to avoid nodes going to loading state .

@diemol attaching the logs that I got. Hope this is what you asked for. SeleniumHQ/docker-selenium#1640 looks similar to mine.

output.log output-preprod-sel4 - Copy.log

[pujagani]

@remyanekkuth Thank you for sharing the logs. I have had a look at the logs and I am not seeing anything odd. The status endpoint seems to return Http status code 200 each time. Maybe the /graphql end point is not responding. When you see the loading state of Grid, are you able to run a new session? or it just gets stuck? Also, as based on https://github.com/SeleniumHQ/docker-selenium/issues/1640#issuecomment-1241884103 Is your machine using any security scan mechanism that might be causing this? It might be good to rule out that possibility for the root cause.

[remyanekkuth]

@pujagani No. We are getting driver exception when try to run.
There is a vulnerability check once in a month I guess. but this is happening every week. Once I reboot , nodes will get connected.

As a work around , I scheduled a weekly reboot for the server for now, which we shouldn’t do .

Not sure if it is related, but I see the nodes getting graying out and getting removed from console for couple of minutes and registering again.

[pujagani]

Thank you for the quick response. Can you share that exception trace? But after the restart does it work as expected? I think the vulnerability check might be potentially causing the need for restart. It sounds awfully similar to https://github.com/SeleniumHQ/docker-selenium/issues/1646. Is it possible to disable the scan and see if it works fine (I understand this might not be easily possible)? Just trying to narrow down the root cause. Any pointers on how can we reproduce the issue? It is only possible to fix this if we are able to reproduce the issue.

[diemol]

Since this is caused by a vulnerability check, I will close this as a duplicate of https://github.com/SeleniumHQ/docker-selenium/issues/1646

[github-actions[bot]]

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