aerokube / ggr

A lightweight load balancer used to create big Selenium clusters
https://aerokube.com/ggr/latest/
Apache License 2.0
314 stars 74 forks source link

Unable to start a WebDriver session. #239

Closed yosserO closed 6 years ago

yosserO commented 6 years ago

Hi guys,

I really don't know if this is a bug or if I'm doing something wrong.

I'm trying to start ggr with the user listed in the tutorial:

htpasswd -bc /etc/grid-router/users.htpasswd test test-password

My quota file is named test.xml and looks like this

`

</qa:browsers> `

I'm running Selenoid on the host and the Selenoid-UI is showing chrome 68.0 under the available capabilities.

When I start the tests I m getting this error:

E/runner - Unable to start a WebDriver session. [chrome #01-11] (node:10776) UnhandledPromiseRejectionWarning: WebDriverError: cannot create session chrome-68.0 on any hosts after 1 attempt(s) [chrome #01-11] at Object.checkLegacyResponse (AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15) [chrome #01-11] at parseHttpResponse (AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13) [chrome #01-11] at doSend.then.response (AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30) [chrome #01-11] at <anonymous> [chrome #01-11] at process._tickCallback (internal/process/next_tick.js:189:7) [chrome #01-11] (node:10776) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) [chrome #01-11] (node:10776) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. [chrome #01-11] [14:21:27] I/runnerCli - cannot create session chrome-68.0 on any hosts after 1 attempt(s)

Thanks!!!

vania-pooh commented 6 years ago

@yosserO is your Selenoid host listening on port 4445? Browsers file seems to be correct.

yosserO commented 6 years ago

Good Point!! It was listening on port 4444 :/

yosserO commented 6 years ago

@vania-pooh Thanks for your help !!

I have some questions:

vania-pooh commented 6 years ago

@yosserO 1) Ggr has no way to limit browser consumption because it has no internal state. You have to limit such consumption on the hosts where browsers reside. E.g. when using Selenoid this can be delivered by changing -limit flag. All requests on top of this limit are queued. 2) We only have Telegram support channel https://t.me/aerokube You can also ask questions by email: support[at]aerokube.com