Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ECONNREFUSED whilst shutting down server #11

Open
pp-james opened this issue Dec 23, 2014 · 6 comments
Open

ECONNREFUSED whilst shutting down server #11

pp-james opened this issue Dec 23, 2014 · 6 comments

Comments

@pp-james
Copy link

Selenium server runs fine, and all of my tests run without a hitch, however when the server starts to shutdown I get this message:

Shut down Selenium server: http://127.0.0.1:4444 (OKOK)

C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\http\index.js:145
      callback(new Error(message));
               ^
Error: ECONNREFUSED connect ECONNREFUSED
    at ClientRequest.<anonymous> (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdri
ver\http\index.js:145:16)
    at ClientRequest.emit (events.js:95:17)
    at Socket.socketErrorListener (http.js:1551:9)
    at Socket.emit (events.js:95:17)
    at net.js:440:14
    at process._tickCallback (node.js:419:13)
==== async task ====
WebDriver.quit()
    at [object Object].webdriver.WebDriver.schedule (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:345:15)
    at [object Object].webdriver.WebDriver.quit (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\webdriver.js:418:21)
    at C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\lib\driverProviders\driverProvider.js:28:16
    at C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\goog\base.js:1582:15
    at [object Object].webdriver.promise.ControlFlow.runInNewFrame_ (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:1654:20)
    at notify (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:465:12)
    at [object Object].then (C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:522:7)
    at C:\dev\sites\myapp\myapp-frontend\node_modules\grunt-protractor-runner\node_modules\protractor\lib\driverProviders\driverProvider.js:26:25
    at Array.map (native)
[launcher] Process exited with error code 1
>>
Fatal error: protractor exited with code: 1
@MrDefinite
Copy link

+1 same problem.
Environment:
"protractor": "^1.5.0",
"grunt-protractor-runner": "^1.1.4",
"jasmine-reporters": "^1.0.1",
"grunt-protractor-webdriver": "^0.2.0"

@pp-james
Copy link
Author

pp-james commented Jan 5, 2015

I should add, I am running Windows, however my colleague running Ubuntu does not get any errors.

@CThuleHansen
Copy link

I am getting the same issue on windows server 2012. Related SO: http://stackoverflow.com/questions/20055593/unable-to-run-protractor-econnrefused-connect-econnrefused

@chazzlabs
Copy link

I'm seeing this same issue on Windows 8.1. My package.json includes:

"grunt-protractor-runner": "~2.0.0",
"grunt-protractor-webdriver": "~0.2.0"

Adding

command: 'webdriver-manager start --standalone'

to my protractor_webdriver options per the StackOverflow post referenced above didn't solve this for me. @pp-james did you ever find a resolution?

@chazzlabs
Copy link

I'm no longer seeing this error if I add

keepAlive: true

to my protractor_webdriver options. This seems like a shaky workaround, however.

@arteforme
Copy link

I, too, am getting this error, but the work around provided by @chazzlabs resolves it.

aullman pushed a commit to aullman/opentok-meet that referenced this issue Apr 14, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants