[🐛 Bug]: Node not registering on Hub for non Dockerised grid 4 on AWS Ec2
See original GitHub issueWhat happened?
I’ve create 3 Ec2 Instance all with Elastic IP .In Grid 4 I’m able to create a hub but when I’m trying to register the node machines.
it only giving the [NodeServer$1.lambda$start$1] - Sending registration event.
In Grid Version 3 with selenium server 3.141 jar I am able to register the node from different machine.
In Grid Version 4 with Selenium Server 4.1.2 For same machine hub and node working but I am not able to register any node from different machine.
Hub Registered with Version 4
Node is not registering.
How can we reproduce the issue?
On Machine 1
java -jar selenium-server-4.1.2.jar hub
On Machine 2
java -jar selenium-server-4.1.2.jar node --detect-drivers true --publish-events tcp://172.168.1.157:4442 --subscribe-events tcp://172.168.1.157:4443
Relevant log output
Logs For Hub machine:
C:\Users\Administrator\Desktop\bat>java -jar selenium-server-4.1.2.jar hub
19:24:30.166 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
19:24:30.166 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
19:24:30.463 INFO [BoundZmqEventBus.<init>] - XPUB binding to [binding to tcp://*:4442, advertising as tcp://172.168.1.157:4442], XSUB binding to [binding to tcp://*:4443, advertising as tcp://172.168.1.157:4443]
19:24:30.544 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://172.168.1.157:4442 and tcp://172.168.1.157:4443
19:24:30.575 INFO [UnboundZmqEventBus.<init>] - Sockets created
19:24:31.591 INFO [UnboundZmqEventBus.<init>] - Event bus ready
19:24:32.559 INFO [Hub.execute] - Started Selenium Hub 4.1.2 (revision 9a5a329c5a): http://172.168.1.157:4444
Logs For Node machine:
19:04:51.991 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
19:04:51.994 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
19:04:52.061 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://172.168.1.157:4442 and tcp://172.168.1.157:4443
19:04:52.084 INFO [UnboundZmqEventBus.<init>] - Sockets created
19:04:53.090 INFO [UnboundZmqEventBus.<init>] - Event bus ready
19:04:53.157 INFO [NodeServer.createHandlers] - Reporting self as: http://169.254.228.24:5555
19:04:53.172 INFO [NodeOptions.getSessionFactories] - Detected 12 available processors
19:04:53.187 INFO [NodeOptions.discoverDrivers] - Discovered 2 driver(s)
19:04:53.204 INFO [NodeOptions.report] - Adding Chrome for {"browserName": "chrome"} 12 times
19:04:53.204 INFO [NodeOptions.report] - Adding Safari for {"browserName": "safari"} 1 times
19:04:53.217 INFO [Node.<init>] - Binding additional locator mechanisms: relative, id, name
19:04:53.312 INFO [NodeServer$1.start] - Starting registration process for node id 20fae541-650b-4042-9b8d-91e5471d03b8
19:04:53.312 INFO [NodeServer.execute] - Started Selenium node 4.1.2 (revision 9a5a329c5a): http://169.254.228.24:5555
19:04:53.318 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:03.328 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:13.337 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:23.346 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:33.351 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:43.360 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:05:53.363 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:03.370 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:13.378 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:23.381 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:33.388 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:43.396 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
19:06:53.314 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
Operating System
Mac, Windows, Ubantu ec2
Selenium version
Selenium server 4.1.2
What are the browser(s) and version(s) where you see this issue?
For Grid 4
What are the browser driver(s) and version(s) where you see this issue?
Safari
Are you using Selenium Grid?
4.1.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Node is not able to connect to Hub, keep sending registration ...
What I can achieve: So using this repo I changed the version of Hub and Node to 4.4.0-20220831 and also changed environment variables...
Read more >Selenium Grid node not registering with hub on AWS ECS ...
I have selenium grid running perfectly locally using docker-compose, all nodes register with the hub fine and tests execute great when ran ...
Read more >elgalu/docker-selenium - Gitter
I am using protractor and want to parallelize the tests . The protractor config is using maxInstances: N and shardTestFiles: true to run...
Read more >Autoscaled Distributed Automation using AWS at Selenium ...
29. GRID TOPOLOGY - 1 HUB • parallel execution for small projects • 1 executor - 1 hub - 14 nodes • eg:...
Read more >Cannot execute protractor tests using headless chrome on ...
I'm using Selenium server 3.8.1, with the hub and 2 nodes. ... node -hub http://172.16.0.5:5555/grid/register -port 5558 -nodeConfig config.json -maxSession ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please Refer the SS for ports info.
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.