Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All the nodes suddenly failed to register with the hub (periodically, roughly every 30 minitues) #414

Open
kqiang opened this issue Jul 22, 2018 · 1 comment

Comments

@kqiang
Copy link

kqiang commented Jul 22, 2018

screen shot 2018-07-22 at 2 00 27 pm

We have a monitoring system to monitor how many nodes are registered with the hub. It checks every minute with this command:
curl -s -w 'STATUS%{http_code}' --max-time 30 http://hubip:4444/grid/console# | grep 'host:' | wc -l

After upgraded selenium grid extras to the latest version (2.0.4), we started to see that all the nodes suddenly failed to register with the hub (i.e. the above command returns 0 nodes registered with the hub, it might be due to cannot connect to hub at all), roughly every 30 minutes. And every time it recovered by itself in 1 minute.

I also tested all the grid extras 2.X.X version, they all have the same issue. I was using 2.12.12 before, everything worked well with it.

Did anyone else encounter the same issue?

Uploading Screen Shot 2018-07-22 at 2.00.27 PM.png…

@kqiang
Copy link
Author

kqiang commented Jul 23, 2018

The further investigation indicates that we lost connection to hub roughly every 30 minutes. The nodes are still registered with the hub, it's just we lot the connection to the hub. This lasts 1 or 2 minutes and after that we can still detect all the nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant