Insufficient configured threads selenium-standalone-chrome

I’m receiving the following error when running selenium in Gitlab’s CI. It was working fine yesterday. I’m on gold tier so this is pretty frustrating.

    Running with gitlab-runner 11.4.2 (cf91d5e1)
  on docker-auto-scale 0277ea0f
Using Docker executor with image starefossen/ruby-node ...
Starting service postgres:latest ...
Pulling docker image postgres:latest ...
Using docker image sha256:7a2907672aabc8acef32a62a1e0af63bc3e461377376a9201e45a87be3f075c2 for postgres:latest ...
Starting service selenium/standalone-chrome:latest ...
Pulling docker image selenium/standalone-chrome:latest ...
Using docker image sha256:b5cf9c7221ba46adea531f24b396ebebc881a8a5b26b84724f93eb24216f723d for selenium/standalone-chrome:latest ...
Starting service redis:latest ...
Pulling docker image redis:latest ...
Using docker image sha256:1babb1dde7e1fc7520ce56ce6d39843a074151bb192522b1988c65a067b15e96 for redis:latest ...
Waiting for services to be up and running...

*** WARNING: Service runner-0277ea0f-project-6756636-concurrent-0-selenium__standalone-chrome-1 probably didn't start properly.

Health check error:
service "runner-0277ea0f-project-6756636-concurrent-0-selenium__standalone-chrome-1-wait-for-service" timeout

Health check container logs:


Service container logs:
2018-11-04T19:03:29.693480402Z 2018-11-04 19:03:29,693 WARN Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2018-11-04T19:03:29.695620128Z 2018-11-04 19:03:29,695 INFO supervisord started with pid 6
2018-11-04T19:03:30.700035700Z 2018-11-04 19:03:30,698 INFO spawned: 'xvfb' with pid 9
2018-11-04T19:03:30.700883912Z 2018-11-04 19:03:30,700 INFO spawned: 'selenium-standalone' with pid 10
2018-11-04T19:03:31.495237932Z 19:03:31.457 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.0, revision: 2ecb7d9a
2018-11-04T19:03:31.495262206Z 2018-11-04 19:03:31,461 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-11-04T19:03:31.495266697Z 2018-11-04 19:03:31,461 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2018-11-04T19:03:31.868300291Z 19:03:31.806 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444
2018-11-04T19:03:32.086475829Z 2018-11-04 19:03:31.975:INFO::main: Logging initialized @1255ms to org.seleniumhq.jetty9.util.log.StdErrLog
2018-11-04T19:03:32.805915267Z 19:03:32.782 INFO [WebDriverServlet.<init>] - Initialising WebDriverServlet
2018-11-04T19:03:33.023638318Z Exception in thread "main" java.lang.IllegalStateException: Insufficient configured threads: required=3 < max=3 for QueuedThreadPool[qtp2081853534]@7c16905e{STARTED,3<=3<=3,i=3,q=0}[ReservedThreadExecutor@2f7c2f4f{s=0/1,p=0}]
2018-11-04T19:03:33.024166429Z 	at org.seleniumhq.jetty9.util.thread.ThreadPoolBudget.check(ThreadPoolBudget.java:155)
2018-11-04T19:03:33.024449046Z 	at org.seleniumhq.jetty9.util.thread.ThreadPoolBudget.leaseTo(ThreadPoolBudget.java:129)
2018-11-04T19:03:33.024766144Z 	at org.seleniumhq.jetty9.util.thread.ThreadPoolBudget.leaseFrom(ThreadPoolBudget.java:181)
2018-11-04T19:03:33.025047150Z 	at org.seleniumhq.jetty9.io.SelectorManager.doStart(SelectorManager.java:255)
2018-11-04T19:03:33.025350660Z 	at org.seleniumhq.jetty9.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018-11-04T19:03:33.025620808Z 	at org.seleniumhq.jetty9.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138)
2018-11-04T19:03:33.025906288Z 	at org.seleniumhq.jetty9.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108)
2018-11-04T19:03:33.026164263Z 	at org.seleniumhq.jetty9.server.AbstractConnector.doStart(AbstractConnector.java:282)
2018-11-04T19:03:33.026444222Z 	at org.seleniumhq.jetty9.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
2018-11-04T19:03:33.027921916Z 	at org.seleniumhq.jetty9.server.ServerConnector.doStart(ServerConnector.java:235)
2018-11-04T19:03:33.028219664Z 	at org.seleniumhq.jetty9.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018-11-04T19:03:33.028488972Z 	at org.seleniumhq.jetty9.server.Server.doStart(Server.java:395)
2018-11-04T19:03:33.028921507Z 	at org.seleniumhq.jetty9.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
2018-11-04T19:03:33.029758814Z 	at org.openqa.selenium.grid.server.BaseServer.start(BaseServer.java:193)
2018-11-04T19:03:33.029766621Z 	at org.openqa.selenium.remote.server.SeleniumServer.boot(SeleniumServer.java:137)
2018-11-04T19:03:33.029771987Z 	at org.openqa.grid.selenium.GridLauncherV3.lambda$buildLaunchers$3(GridLauncherV3.java:249)
2018-11-04T19:03:33.030439695Z 	at org.openqa.grid.selenium.GridLauncherV3.lambda$launch$0(GridLauncherV3.java:86)
2018-11-04T19:03:33.030816884Z 	at java.util.Optional.map(Optional.java:215)
2018-11-04T19:03:33.031573559Z 	at org.openqa.grid.selenium.GridLauncherV3.launch(GridLauncherV3.java:86)
2018-11-04T19:03:33.031874008Z 	at org.openqa.grid.selenium.GridLauncherV3.main(GridLauncherV3.java:70)

*********