[🐛 Bug]: Unable to use same port across multiple nodes in selenium grid 4
What happened?
The way grid 3 set up was environment integ and pre-production will listen to port 5555 . Integ will listen to development server hub and pre-production in prepoduction server hub. sandbox and user acceptance will listen to 4444
In grid 4 same configuration we did for port 5955 4944 respectively. Integ is working fine. But when try to run the command with --port 5950 getting error " address in use" how can we use same port across multiple nodes.
command we run is
JAVA -jar "jar " node --hub http:selenium:5955/grid/register --port 5900 --host "computer name "
How can we reproduce the issue?
Two nodes with same port in different environment with different server.
Add first node and validate
JAVA -jar "jar " node --hub http:selenium:5955/grid/register --port 5900 --host "computer name "
go to the second server, configure same port for diff envt. and run again
will get exception at point --port
Relevant log output
value is not acceptable for --port .
Operating System
windows 10
Selenium version
4.1.3
What are the browser(s) and version(s) where you see this issue?
chrome 102, edge -103
What are the browser driver(s) and version(s) where you see this issue?
chromeDriver 102, edye -103
Are you using Selenium Grid?
4.1.3
@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!
A few things, http:selenium:5955/grid/register is not a valid URL to register, and we also need the full commands and logs for each command. We cannot triage this until more information is provided.
@diemol I set up this port and hub was working fine. I was able to resolve the issue by mentioning—publish-events and —subscriber-events .
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.