Node keeps sending registration event but no success

2,368 views
Skip to first unread message

Prashant Chavan

unread,
Jan 19, 2022, 1:37:45 AM1/19/22
to Selenium Users
Hi All,

I am trying to use selenium grid with multiple windows VMs. Following is the scenario. 


Selenium Version : 4.1.1
Started Hub on Windows VM with following command -
java -jar selenium-server-4.1.1.jar hub

Node started successfully.

Now trying to register node from another windows VM with following -
java -jar selenium-server-4.1.1.jar node --detect-drivers true --publish-events tcp://HUB_IP:4442 --subscribe-events tcp://HUB_IP:4443

Console OutPut-
06:13:37.272 INFO [LogManager$RootLogger.log] - Using the system default encoding
 06:13:37.304 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
 06:13:37.743 INFO [UnboundZmqEventBus.<init>] - Connecting to tcp://HUB_IP:4442 and tcp://HUB_IP:4443
 06:13:37.805 INFO [UnboundZmqEventBus.<init>] - Sockets created
 06:13:38.828 INFO [UnboundZmqEventBus.<init>] - Event bus ready
 06:13:39.062 INFO [NodeServer.createHandlers] - Reporting self as: http://Node_IP:5555
 06:13:39.375 INFO [NodeOptions.getSessionFactories] - Detected 1 available processors
 06:13:39.406 INFO [NodeOptions.discoverDrivers] - Discovered 1 driver(s)
 06:13:39.453 INFO [NodeOptions.report] - Adding Chrome for {"browserName": "chrome"} 1 times
 06:13:39.453 INFO [Node.<init>] - Binding additional locator mechanisms: relative, id, name
 06:13:39.999 INFO [NodeServer$1.start] - Starting registration process for node id 28722b0b-c3a4-41b2-8bc4-83ec0e1f5148
 06:13:39.999 INFO [NodeServer.execute] - Started Selenium node 4.1.1 (revision e8fcc2cecf): http://Node_IP:5555
 06:13:39.999 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:13:50.000 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:00.016 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:10.034 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:30.041 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:20.039 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:40.048 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:14:50.054 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:15:00.062 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:15:10.072 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:15:30.089 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:15:20.085 INFO [NodeServer$1.lambda$start$1] - Sending registration event...
 06:15:40.009 INFO [NodeServer$1.lambda$start$1] - Sending registration event...

If I try firing same command on VM-1 (where my hub is running I get success). 

Can someone please help me on this.

Regards,
Prashant

Todd Ogin

unread,
Mar 14, 2022, 5:29:15 PM3/14/22
to Selenium Users
Hey Prashant,

Realize it's been awhile since you posted, but my team was able to get this to work eventually for a test.

In our case, one machine ran:

java -jar .\selenium-server-4.1.2.jar hub

Another machine ran:

java -jar .\selenium-server-4.1.2.jar node --hub http://xxx.xxx.xxx.xxx

Where you'll replace the xxx's with the hub's ip address.

In order for them to talk to each other, and get by the "Sending registration event..."  issue we needed to make sure Windows Defender Firewall had all the relevant software products unblocked on the correct networks. I don't know whether you have windows defender or a different firewall product, but it's likely a similar problem. If you're using VMs, then the VM host software might be restricting network communication as well. For windows defender at least, hub and node couldn't communicate until the "public" networks were unblocked for the app for us. This was somewhat surprising but it worked for our testing needs.

If you are using windows defender, I attached a screenshot of what it looks like set up in a way that allows the previous described Selenium hub/node setup to function. You'll want to review your network security settings after you get it working to see if you are correctly limiting access to only necessary resources.

Hopefully this helps anyone else hitting the "Sending registration event..." issue

Todd
windowsdefenderunblocked.png
Reply all
Reply to author
Forward
0 new messages