Getting "unable to discover open pages" error intermittently in Jenkins/Selenium/Docker/Chrome setup

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Getting "unable to discover open pages" error intermittently in Jenkins/Selenium/Docker/Chrome setup

Micah Lapping-Carr
Hi all,

My team has automation that gets kicked off by Jenkins whenever there's a new build of our website available. Our Jenkins job uses docker-compose to spin up a selenium/hub:3.6.0 instance, 5 linked selenium/node-chrome:3.6.0 instances, and 1 selenium/node-firefox:3.6.0 instance (which isn't being used in this case, but I'm including it here for completeness) on our Jenkins machine. The test then connects to the selenium hub running on the same machine and requests to connect to the 5 chrome nodes in parallel. Most of the time, our tests run fine. However, once in a while, they get an error that looks like this:

setup(com.some.package)  Time elapsed: 0.668 sec  <<< FAILURE!
org.openqa.selenium.WebDriverException: 
chrome not reachable
  (Driver info: chromedriver=2.33.506092 (733a02544d189eeb751fe0d7ddca79a0ee28cce4),platform=Linux 3.10.0-327.36.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 88.18 seconds
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T16:15:40.131Z'
System info: host: '8b76b61d7082', ip: '172.17.0.28', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-327.36.2.el7.x86_64', java.version: '1.8.0_131'
Driver info: driver.version: unknown
Command duration or timeout: 102.79 seconds
Caused by: org.openqa.selenium.WebDriverException: 
chrome not reachable
  (Driver info: chromedriver=2.33.506092 (733a02544d189eeb751fe0d7ddca79a0ee28cce4),platform=Linux 3.10.0-327.36.2.el7.x86_64 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 88.18 seconds
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T16:15:40.131Z'
System info: host: '8b76b61d7082', ip: '172.17.0.28', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-327.36.2.el7.x86_64', java.version: '1.8.0_131'
Driver info: driver.version: unknown
Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
System info: host: 'REDACTED_HOST.net', ip: '10.66.209.102', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-327.36.2.el7.x86_64', java.version: '1.8.0_141'
Driver info: driver.version: unknown

You can find a gist with the setup code and docker-compose fileĀ here. Our tests are more complicated than this, but this captures the setup right up until it fails. I should also note that these tests run in 4 different Jenkins jobs which sometimes are running at the same time. Each test spins up and connects to its own selenium hub/node docker containers. The machine that these tests are running on is super beefy (like 125 gigs of RAM), so I'm pretty confident that's not the issue, but it's quite possible that something, somewhere, is getting overloaded, I just haven't been able to figure out what.

I'm open to any instructions or suggestions on experiments to try or how to gather the necessary debug information. I've looked around at a bunch of different issues that people have had, on this site and others, and haven't been able to find anything that helped.

Thanks!
Micah

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/11f03ad9-0795-4fdd-9df4-951214e382fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.