Selenium grid resets connection #646
Comments
|
Hi @ViljarVoidula, Could you please help us by providing:
|
|
@diemol Thank You so much for fast response. I did setup a repository so the problem would be easy to reproduce . https://github.com/ViljarVoidula/nightwatch-selenium-firefox. You will need https://yarnpkg.com/en/docs/install . I did find issue facing quite similar problem in geckodriver mozilla/geckodriver#1015 . Maybe my problem is duplicate of the issue mentioned there, but I'm not enough experienced yet to confirm that . I use docker-compose up
|
|
Hi @ViljarVoidula, I used your project and I bumped into the same error. So I tried to figure out if there was some option making that error happen and in short, I was not able to figure it out. So I decided to create my own small Nightwatch project, with the smallest config, to see if it still happens, and yes, the error also shows up: After that, I tried with a small setup for WebDriverIO, and no error happened. These are the couple of projects https://github.com/diemol/docker-selenium-issues/tree/master/issue-646 I also tried to start a local grid without docker, by doing: (I have FF 57.0.4 and GeckoDriver 0.19.1 locally installed). and the same error happened when running the Nightwatch test. So I suspect that the problem is actually related to Nightwatch, and I'd recommend that you create an issue in their repo because it looks like those bindings are having some issue with the latest Selenium version. Since this is not a docker-selenium issue, I'll go ahead and close this issue. |
|
@diemol Thank you very much for confirmation. Atleast now I have somekind of direction to go on with that's confirmed by expert . |
Meta -
Image(s):
<hub,firefox_node_debug>
Docker-Selenium Image Version(s):
3.8.1-chlorine
Docker Version:
Docker version 17.09.1-ce, build 19e2cf6
OS:
Ubuntu 16.04 x64
4.10.0-42-generic
Expected Behavior -
Firefox node not dropping connection
Actual Behavior -
Using nightwatch JS as testframework:
output:
`Running: Open player
INFO Request: POST /wd/hub/session
INFO Response 200 POST /wd/hub/session (2526ms) { value:
{ sessionId: '974cc51f-39ea-4bd7-a325-4fe554e93c0b',
capabilities:
{ 'moz:profile': '/tmp/rust_mozprofile.KjkHHCmcV3O1',
rotatable: false,
timeouts: { implicit: 0, pageLoad: 300000, script: 30000 },
pageLoadStrategy: 'normal',
'moz:headless': false,
'moz:accessibilityChecks': false,
acceptInsecureCerts: false,
browserVersion: '57.0.2',
platformVersion: '4.10.0-42-generic',
'moz:processID': 114,
browserName: 'firefox',
platformName: 'linux',
'moz:webdriverClick': false } } }
Error retrieving a new session from the selenium server
Connection refused! Is selenium server started?
{ value:
{ sessionId: '974cc51f-39ea-4bd7-a325-4fe554e93c0b',
capabilities:
{ 'moz:profile': '/tmp/rust_mozprofile.KjkHHCmcV3O1',
rotatable: false,
timeouts: [Object],
pageLoadStrategy: 'normal',
'moz:headless': false,
'moz:accessibilityChecks': false,
acceptInsecureCerts: false,
browserVersion: '57.0.2',
platformVersion: '4.10.0-42-generic',
'moz:processID': 114,
browserName: 'firefox',
platformName: 'linux',
'moz:webdriverClick': false } } }`
The text was updated successfully, but these errors were encountered: