Closed HackToday closed 7 years ago
Not information here to reproduce, and I also suspect this is a Selenium issue. You need to include the stdout from geckodriver as it starts up. I would suggest checking the geckodriver.log file that the Python bindings produce and post it here. If you provide enough reproducible information, I’m happy to re-open this.
@andreastt sure. I can post here. The firefox and selenium did have such serious annoying random failure issue like this. I suggest we try to solve that issue instead of suspect each other. :smile:
We want to fix all issues in geckodriver, but we can’t fix the issue unless we know what is wrong or how to reproduce it.
@andreastt I have collected geckodriver.log please check the file. Let's debug the root cause of the issue. Thanks
https://gist.github.com/HackToday/76c7a767342d495dac0e6b815e0d3c2d
Also found more serious errors in log here
1481771416951 addons.manager DEBUG Provider finished startup: PluginProvider
1481771416951 addons.manager DEBUG Completed startup sequence
1481771417136 Marionette ERROR Error on starting server: [Exception... "Component returned failure code: 0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]" nsresult: "0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE)" location: "JS frame :: chrome://marionette/content/server.js :: MarionetteServer.prototype.start :: line 85" data: no]
[Exception... "Component returned failure code: 0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE) [nsIServerSocket.initSpecialConnection]" nsresult: "0x804b0036 (NS_ERROR_SOCKET_ADDRESS_IN_USE)" location: "JS frame :: chrome://marionette/content/server.js :: MarionetteServer.prototype.start :: line 85" data: no]
MarionetteServer.prototype.start@chrome://marionette/content/server.js:85:19
MarionetteComponent.prototype.init@resource://gre/components/marionettecomponent.js:218:5
MarionetteComponent.prototype.observe@resource://gre/components/marionettecomponent.js:142:7
Perhaps you can check full logs to discover more. @andreastt
@HackToday That Gecko log doesn’t include Marionette unfortunately. See the README on how to enable verbose logging from Marionette.
Your last paste shows you have something already bound on port 2828.
This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue.
If you are having an issue with GeckoDriver starting up, please make sure that your client bindings support using it.
Meta -
OS: CentOS 7.2 e.g.: Windows 10? OSX?
Browser Version: Firefox 50.0 e.g.: 50.0.2623.87 (64-bit)
Expected Behavior -
Test would run OK
Actual Behavior -
Sometimes test would fail with connection refused, it is clearly not test issue, it is possible about selenium or Firefox issue
Steps to reproduce -
Note: Please be sure to include an SSCCE (Short, Self Contained, Correct [compilable] example) http://sscce.org/ If you can't provide a link to the page, consider creating a reproducible page on https://jsfiddle.net/
Can not give a easy steps to reproduce, it can sometime happen. (maybe 3 in 10 times)
As issue here https://github.com/SeleniumHQ/selenium/issues/3201 selenium guys said
The connection refused would be happening when trying to communicate with GeckoDriver
If any of the above are missing we will have to unforunately close your issue. We will gladly reopen the issue once all the information requested has been added