Protractor: Unable to start a webdriver session for chrome

Created on 6 Mar 2015  Â·  33Comments  Â·  Source: angular/protractor

I am a new comer to protractor and I got problem trying to using protractor with webdriver.
I installed protractor and did "webdriver-manager update" to get selenium server and chromedriver and iedriver downloaded.

Then I start the selenium standalone server at local (127.0.0.1:4444)
then try to perform testing with "protractor conf.js", then I got following error message.

$ protractor conf.js
Using the selenium server at http://127.0.0.1:4444/wd/hub
[launcher] Running 1 instances of WebDriver
ERROR - Unable to start a WebDriver session.

c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node_modules\seleniu
m-webdriver\lib\atoms\error.js:113
var template = new Error(this.message);
^
UnknownError: null
at new bot.Error (c:\Users\dc\AppData\Roaming\npm\node_modules\protracto
r\node_modules\selenium-webdriver\lib\atoms\error.js:113:18)
at Object.bot.response.checkResponse (c:\Users\dc\AppData\Roaming\npm\no
de_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:106:
9)
at c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\webdriver\webdriver.js:152:24
at c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\goog\base.js:1582:15
at [object Object].webdriver.promise.ControlFlow.runInNewFrame_ (c:\Users\do
ncui\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver
\lib\webdriver\promise.js:1654:20)
at notify (c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node_
modules\selenium-webdriver\lib\webdriver\promise.js:465:12)
at notifyAll (c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\no
de_modules\selenium-webdriver\lib\webdriver\promise.js:442:7)
at resolve (c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node
_modules\selenium-webdriver\lib\webdriver\promise.js:420:7)
at fulfill (c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node
_modules\selenium-webdriver\lib\webdriver\promise.js:535:5)
at c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\goog\base.js:1582:15
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (c:\Users\dc\AppData\Roa
ming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\w
ebdriver.js:149:22)
at Function.webdriver.WebDriver.createSession (c:\Users\dc\AppData\Roami
ng\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\web
driver.js:123:30)
at Builder.build (c:\Users\dc\AppData\Roaming\npm\node_modules\protracto
r\node_modules\selenium-webdriver\builder.js:294:22)
at DriverProvider.getNewDriver (c:\Users\dc\AppData\Roaming\npm\node_mod
ules\protractor\lib\driverProviders\driverProvider.js:38:7)
at Runner.createBrowser (c:\Users\dc\AppData\Roaming\npm\node_modules\pr
otractor\lib\runner.js:180:37)
at c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\lib\runner.js
:257:21
at _fulfilled (c:\Users\dc\AppData\Roaming\npm\node_modules\protractor\n
ode_modules\q\q.js:797:54)
at self.promiseDispatch.done (c:\Users\dc\AppData\Roaming\npm\node_modul
es\protractor\node_modules\q\q.js:826:30)
at Promise.promise.promiseDispatch (c:\Users\dc\AppData\Roaming\npm\node
_modules\protractor\node_modules\q\q.js:759:13)
[launcher] Process exited with error code 1

windows needs more info

Most helpful comment

Sigh... I'm seeing this on linux but not my mac. Protractor 5.1.1, node v6.10.0, java 1.8.0_121

[10:53:57] E/launcher - chrome not reachable
  (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-72-generic x86_64)
[10:53:57] E/launcher - WebDriverError: chrome not reachable
  (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-72-generic x86_64)
    at WebDriverError (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/error.js:27:5)
    at Object.checkLegacyResponse (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/root/co/tests/e2e/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/root/co/tests/e2e/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser (/root/co/tests/e2e/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/root/co/tests/e2e/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled (/root/co/tests/e2e/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/root/co/tests/e2e/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/root/co/tests/e2e/node_modules/q/q.js:796:13)
    at /root/co/tests/e2e/node_modules/q/q.js:556:49
    at runSingle (/root/co/tests/e2e/node_modules/q/q.js:137:13)
[10:53:57] E/launcher - Process exited with error code 199

All 33 comments

the content of conf.js

// conf.js
exports.config = {
seleniumAddress: 'http://127.0.0.1:4444/wd/hub',
specs: ['spec.js'],
capabilities: {
browserName: 'chrome',
chromeOptions: {
binary: 'C:/Program Files (x86)/Google/Chrome/Application/chrome.exe',
args: [],
extensions: [],
}
}
};

I assume you start WebDriver with webdriver-manager start?

If so, I cannot reproduce this with your config. Maybe adding spec.js (partially) would help.

I just use this tutorial to pratice
http://angular.github.io/protractor/#/tutorial
and the content of spec.js
// spec.js
describe('angularjs homepage', function() {
it('should have a title', function() {
browser.get('http://juliemr.github.io/protractor-demo/');

expect(browser.getTitle()).toEqual('Super Calculator');

});
});

I guess the problem lies in chromedriver or chrome.exe.
But it should be no wrong in chromedriver as it is downloaded by webdriver-manager.

Hmmm, works for me :cry:

where is the chrome.exe in your machine? and what OS do you have?

In my own Protractor tests I do not even specify the location of the Chrome-executable, but I did try to specify it as you did.

I use Windows 7 (x64) with Chrome 40.0.2214.115 m (located on exactly the same path as your copy) in combination with node v0.12.0 and webdriver-manager gives me 21:35:11.109 INFO - v2.44.0, with Core v2.44.0. Built from revision 76d78cf.

I tried both http://localhost:4444/wd/hub as I did your option with 127.0.0.1: both work.

Please run your test with the --troubleshoot and post the output.

I try to use --troubleshoot but it is not accepted.
C:\Users\doncui\protractor_test>protractor --troubleshoot conf.js
**you must either specify a configuration file or at least 3 options. See below
for the options:

Usage: protractor [options] [configFile]
configFile defaults to protractor.conf.js
The [options] object will override values from the config file.
See the reference config for a full list of options.

Options:
--help Print Protractor help menu

--version Print Protractor version

--browser, --capabilities.browserName Browsername, e.g. chrome or
firefox
--seleniumAddress A running selenium address
to use
--seleniumServerJar Location of the standalone
selenium jar file
--seleniumPort Optional port for the selen
ium standalone server
--baseUrl URL to prepend to all relat
ive paths
--rootElement Element housing ng-app, if
not html or body
--specs Comma-separated list of fil
es to test
--exclude Comma-separated list of fil
es to exclude
--verbose, --jasmineNodeOpts.isVerbose Print full spec names

--stackTrace, --jasmineNodeOpts.includeStackTrace Print stack trace on error

--params Param object to be passed t
o the tests
--framework Test framework to use: jasm
ine, cucumber or mocha
--resultJsonOutputFile Path to save JSON test resu
lt
--troubleshoot Turn on troubleshooting out
put
--elementExplorer Interactively test Protract
or commands

The --troubleshoot parameter requires an argument, so try:

protractor --troubleshoot true conf.js

C:\Users\doncui\protractor_test>protractor --troubleshoot true conf.js
DEBUG - Running with --troubleshoot
DEBUG - Protractor version: 1.8.0
DEBUG - Your base url for tests is undefined
Using the selenium server at http://127.0.0.1:4444/wd/hub
[launcher] Running 1 instances of WebDriver
ERROR - Unable to start a WebDriver session.

C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node_modules\seleniu
m-webdriver\lib\atoms\error.js:113
var template = new Error(this.message);
^
UnknownError: null
at new bot.Error (C:\Users\doncui\AppData\Roaming\npm\node_modules\protracto
r\node_modules\selenium-webdriver\lib\atoms\error.js:113:18)
at Object.bot.response.checkResponse (C:\Users\doncui\AppData\Roaming\npm\no
de_modules\protractor\node_modules\selenium-webdriver\lib\atoms\response.js:106:
9)
at C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\webdriver\webdriver.js:152:24
at C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\goog\base.js:1582:15
at [object Object].webdriver.promise.ControlFlow.runInNewFrame_ (C:\Users\do
ncui\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver
\lib\webdriver\promise.js:1654:20)
at notify (C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node_
modules\selenium-webdriver\lib\webdriver\promise.js:465:12)
at notifyAll (C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\no
de_modules\selenium-webdriver\lib\webdriver\promise.js:442:7)
at resolve (C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node
_modules\selenium-webdriver\lib\webdriver\promise.js:420:7)
at fulfill (C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node
_modules\selenium-webdriver\lib\webdriver\promise.js:535:5)
at C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\node_modules\
selenium-webdriver\lib\goog\base.js:1582:15
==== async task ====
WebDriver.createSession()
at Function.webdriver.WebDriver.acquireSession_ (C:\Users\doncui\AppData\Roa
ming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\w
ebdriver.js:149:22)
at Function.webdriver.WebDriver.createSession (C:\Users\doncui\AppData\Roami
ng\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\web
driver.js:123:30)
at Builder.build (C:\Users\doncui\AppData\Roaming\npm\node_modules\protracto
r\node_modules\selenium-webdriver\builder.js:294:22)
at DriverProvider.getNewDriver (C:\Users\doncui\AppData\Roaming\npm\node_mod
ules\protractor\lib\driverProviders\driverProvider.js:38:7)
at Runner.createBrowser (C:\Users\doncui\AppData\Roaming\npm\node_modules\pr
otractor\lib\runner.js:180:37)
at C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\lib\runner.js
:257:21
at _fulfilled (C:\Users\doncui\AppData\Roaming\npm\node_modules\protractor\n
ode_modules\q\q.js:797:54)
at self.promiseDispatch.done (C:\Users\doncui\AppData\Roaming\npm\node_modul
es\protractor\node_modules\q\q.js:826:30)
at Promise.promise.promiseDispatch (C:\Users\doncui\AppData\Roaming\npm\node
_modules\protractor\node_modules\q\q.js:759:13)
[launcher] Process exited with error code 1

I'm guessing this is an issue with where your Chrome binary is. Can you check and make sure it's at C:/Program Files (x86)/Google/Chrome/Application/chrome.exe? Can you run other browsers?

The path is correct.
I can run firefox and IE successfully.

Br/Dongbo

2015-03-17 0:18 GMT+01:00 Julie Ralph [email protected]:

I'm guessing this is an issue with where your Chrome binary is. Can you
check and make sure it's at C:/Program Files
(x86)/Google/Chrome/Application/chrome.exe? Can you run other browsers?

—
Reply to this email directly or view it on GitHub
https://github.com/angular/protractor/issues/1905#issuecomment-81985393.

Not sure what to say - we can't reproduce the problem. It's an issue with chromedriver, chrome, or the selenium standalone server. Can you try reinstalling them?

I'm going to close this issue sine it's not a general problem, but we can keep discussing here.

I'm having the same problem, but with a different configuration and OS (Linux), see relevant parts here: https://gist.github.com/orbitbot/b544d61fa4f51ed5170e. Confusingly my setup is working fine on my linux development machine, but is failing on a CI machine, while still using the same commands and same npm package versions...

On my development machine I can successfully run tests manually (with browsersync running) with ./node_modules/protractor/bin/protractor --troubleshoot true config/protractor.conf --baseUrl 'http://localhost:3000/#/' --specs test/integration/app.spec.js, but the development machine fails with

$ ./node_modules/protractor/bin/protractor --troubleshoot true config/protractor.conf --baseUrl 'http://localhost:3000/#/' --specs test/integration/app.spec.js
DEBUG - Running with --troubleshoot
DEBUG - Protractor version: 2.0.0
DEBUG - Your base url for tests is http://localhost:3000/#/
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://192.168.1.10:33998/wd/hub
ERROR - Unable to start a WebDriver session.

/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113
  var template = new Error(this.message);
                 ^
UnknownError: unknown error: Chrome failed to start: exited abnormally
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Linux 3.11.0-26-generic x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 60.90 seconds
Build info: version: '2.45.0', revision: '5017cb8', time: '2015-02-26 23:59:50'
System info: host: 'mule', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.11.0-26-generic', java.version: '1.7.0_51'
Driver info: org.openqa.selenium.chrome.ChromeDriver
    at new bot.Error (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113:18)
    at Object.bot.response.checkResponse (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)
    at /var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:158:24
    at [object Object].promise.ControlFlow.runInFrame_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1877:20)
    at [object Object].promise.Callback_.goog.defineClass.notify (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:2464:25)
    at [object Object].promise.Promise.notify_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:563:12)
    at Array.forEach (native)
    at Object.goog.array.forEach (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/array/array.js:203:43)
    at [object Object].promise.Promise.notifyAll_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:552:16)
    at [object Object].goog.async.run.processWorkQueue as _onTimeout
From: Task: WebDriver.createSession()
    at Function.webdriver.WebDriver.acquireSession_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/seleni

Firefox also works on development machine, but not on CI (in both cases by just changing capabilities.browserName to 'firefox' in protractor.conf):

ERROR - Unable to start a WebDriver session.

/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113
  var template = new Error(this.message);
                 ^
UnknownError: Unable to connect to host 127.0.0.1 on port 7055 after 45000 ms. Firefox console output:

(process:4534): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Error: no display specified

(process:4542): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Error: no display specified

    at new bot.Error (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113:18)
    at Object.bot.response.checkResponse (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)
    at /var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:158:24
    at [object Object].promise.ControlFlow.runInFrame_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1877:20)
    at [object Object].promise.Callback_.goog.defineClass.notify (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:2464:25)
    at [object Object].promise.Promise.notify_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:563:12)
    at Array.forEach (native)
    at Object.goog.array.forEach (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/array/array.js:203:43)
    at [object Object].promise.Promise.notifyAll_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:552:16)
    at [object Object].goog.async.run.processWorkQueue as _onTimeout
From: Task: WebDriver.createSession()
    at Function.webdriver.WebDriver.acquireSession_ (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:155:22)
    at Function.webdriver.WebDriver.createSession (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:129:30)
    at [object Object].Builder.build (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/selenium-webdriver/builder.js:416:22)
    at [object Object].DriverProvider.getNewDriver (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/lib/driverProviders/driverProvider.js:38:7)
    at [object Object].Runner.createBrowser (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/lib/runner.js:180:37)
    at /var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/lib/runner.js:257:21
    at _fulfilled (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/q/q.js:797:54)
    at self.promiseDispatch.done (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/q/q.js:826:30)
    at Promise.promise.promiseDispatch (/var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/q/q.js:759:13)
    at /var/lib/jenkins/jobs/aloha/workspace/node_modules/protractor/node_modules/q/q.js:573:44
[launcher] Process exited with error code 1

Have you tried run webdriver-manager update?

Installing chromedriver manually might help as well:

  • download chromedriver (https://code.google.com/p/selenium/wiki/ChromeDriver)
  • extract
  • put the chromedriver file into your windows/system32 folder

I'm receiving the same error as @orbitbot and @iamblackheat. I'm on Linux.

Also experiencing the same issue as @orbitbot, @iamblackheat, and @cboden. Windows, with webdriver-manager up to date.

Edit: I finally resolved it by downgrading protractor to v1.8.0

You probably have java 8 installed, remove it and install java 7.

Just to add a helpful note: Instead of passing --troubleshoot true to the command line, which does not work for me, this can also be specified in the configuration file: troubleshoot: true,

Thanks @gilamran. That worked!
I am on OSX 10.10.5. Simply switching JAVA_HOME to jdk1.7 solved the problem.
Here is what I did:

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ ll /Library/Java/JavaVirtualMachines/
total 24
8 lrwxr-xr-x  1 root  wheel   16 Aug 23 14:43 jdk1.7@ -> jdk1.7.0_79.jdk/
0 drwxr-xr-x  3 root  wheel  102 May  2 16:10 jdk1.7.0_79.jdk/
8 lrwxr-xr-x  1 root  wheel   16 Aug 23 14:42 jdk1.8@ -> jdk1.8.0_45.jdk/
0 drwxr-xr-x  3 root  wheel  102 Jul  3 21:10 jdk1.8.0_45.jdk/
8 lrwxr-xr-x  1 root  wheel   16 Jul  3 21:12 latest@ -> jdk1.8.0_45.jdk/

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ java -version
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ protractor test/protractor-conf.js 
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://192.168.2.14:55941/wd/hub

/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113
  var template = new Error(this.message);
                 ^
UnknownError: The process has not exited yet therefore no result is available ...
    at new bot.Error (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:113:18)
    at Object.bot.response.checkResponse (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)
    at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:158:24
    at [object Object].promise.ControlFlow.runInFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1877:20)
    at [object Object].promise.Callback_.goog.defineClass.notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:2464:25)
    at [object Object].promise.Promise.notify_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:563:12)
    at Array.forEach (native)
    at Object.goog.array.forEach (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/array/array.js:203:43)
    at [object Object].promise.Promise.notifyAll_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:552:16)
    at goog.async.run.processWorkQueue (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/async/run.js:125:21)
From: Task: WebDriver.createSession()
    at Function.webdriver.WebDriver.acquireSession_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:155:22)
    at Function.webdriver.WebDriver.createSession (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:129:30)
    at [object Object].Builder.build (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/builder.js:416:22)
    at [object Object].DriverProvider.getNewDriver (/usr/local/lib/node_modules/protractor/lib/driverProviders/driverProvider.js:38:7)
    at [object Object].Runner.createBrowser (/usr/local/lib/node_modules/protractor/lib/runner.js:180:37)
    at /usr/local/lib/node_modules/protractor/lib/runner.js:268:21
    at _fulfilled (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:797:54)
    at self.promiseDispatch.done (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:826:30)
    at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:759:13)
    at /usr/local/lib/node_modules/protractor/node_modules/q/q.js:573:44
[launcher] Process exited with error code 1

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7/Contents/Home

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ java -version
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

ryba@localhost:/tmp/angular-phonecat[(step-7)]
$ protractor test/protractor-conf.js 
Starting selenium standalone server...
[launcher] Running 1 instances of WebDriver
Selenium standalone server started at http://192.168.2.14:62098/wd/hub
...WARNING - more than one element found for locator By.cssSelector(".phones li a") - the first result will be used
..

Finished in 2.817 seconds
5 tests, 8 assertions, 0 failures

Shutting down selenium standalone server.
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 passed

That's it. Works like a charm.
PS: I did install protractor globally but that should not matter.

For me it works for chrome and firefox but not safari.
@tomaszrybakiewicz did you test this with safari. I have checked my JDK and it is:

$ echo $JAVA_HOME
/Library/Java/JavaVirtualMachines/jdk1.7.0_76.jdk/Contents/Home

$ ll /Library/Java/JavaVirtualMachines/
total 0
drwxr-xr-x  3 root  wheel  102  9 Oct  2014 jdk1.7.0_67.jdk
drwxr-xr-x  3 root  wheel  102 10 Apr 09:21 jdk1.7.0_76.jdk

Thanks
Rob

@robwatkin Unfortunately no. I did not have a need to test it in Safari. Running E2E tests against 2 different web browsers was enough for me.

@orbitbot Your failures on the CI machine are due to not having a display available, try with XVFB

@martin770 Thanks for the catch! We have XVFB installed but it wasn't configured properly, for posterity, fixed with xvfb-run gulp integration in the CI config.

thanks @gilamran and @tomaszrybakiewicz .,
I had the same problem using OSX 10.11
pointing $JAVA_HOME to JDK1.7 did the trick for me

I had a similar problem and tried the various suggestions here, including the Java 7 solution, but I was still getting this error:

protractor protractor.conf.js
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver

/usr/lib/node_modules/protractor/node_modules/selenium-webdriver/error.js:26
constructor(opt_error) {
^
WebDriverError: chrome not reachable

Turns out I had too many terminals open and was running webdriver-manager start as root.

Don't do this.

@GeraldScott Don't do what? Run webdriver-manager start multiple times or run it as root?

Don't run as root.

C:\Users\channakg\Source\Workspaces\VueFramework\Dev\VueFramework\VueFrameworkSanityTests>protractor Protractor.conf.js --browser="internet explorer" --Capabilities.seleniumAddress='http://localhost:5555/ --troubleshoot
[04:44:53] D/launcher - Running with --troubleshoot
[04:44:53] D/launcher - Protractor version: 5.1.1
[04:44:53] D/launcher - Your base url for tests is undefined
[04:44:53] I/launcher - Running 1 instances of WebDriver
[04:44:53] D/local - Attempting to find the SeleniumServerJar in the default location used by webdriver-manager
[04:44:53] I/local - Starting selenium standalone server...
[04:44:57] I/local - Selenium standalone server started at http://10.240.21.86:51916/wd/hub
[04:45:01] E/launcher - Unable to create new remote session. desired capabilities = Capabilities [{count=1, browserName=internet explorer}], required capabilities = Capabilities [{}]
Build info: version: '3.0.1', revision: '1969d75', time: '2016-10-18 09:48:19 -0700'
System info: host: 'VUE-FRW-WIN10', ip: '10.240.21.86', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_121'
Driver info: driver.version: InternetExplorerDriver
[04:45:01] E/launcher - SessionNotCreatedError: Unable to create new remote session. desired capabilities = Capabilities [{count=1, browserName=internet explorer}], required capabilities = Capabilities [{}]
Build info: version: '3.0.1', revision: '1969d75', time: '2016-10-18 09:48:19 -0700'
System info: host: 'VUE-FRW-WIN10', ip: '10.240.21.86', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_121'
Driver info: driver.version: InternetExplorerDriver
at WebDriverError (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:27:5)
at SessionNotCreatedError (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:214:5)
at Object.checkLegacyResponse (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:505:15)
at parseHttpResponse (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at doSend.then.response (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:440:13)
at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:777:24)
at createDriver (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:167:33)
at Builder.build (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:632:14)
at Local.getNewDriver (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\lib\driverProviders\driverProvider.ts:60:29)
at Runner.createBrowser (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\lib\runner.ts:225:39)
at q.then.then (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\lib\runner.ts:391:27)
at _fulfilled (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at self.promiseDispatch.done (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
at Promise.promise.promiseDispatch (C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
at C:\Users\channakg\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:604:44
[04:45:01] E/launcher - Process exited with error code 199

I'm unable to launch protractor in ie11

Sigh... I'm seeing this on linux but not my mac. Protractor 5.1.1, node v6.10.0, java 1.8.0_121

[10:53:57] E/launcher - chrome not reachable
  (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-72-generic x86_64)
[10:53:57] E/launcher - WebDriverError: chrome not reachable
  (Driver info: chromedriver=2.29.461571 (8a88bbe0775e2a23afda0ceaf2ef7ee74e822cc5),platform=Linux 4.4.0-72-generic x86_64)
    at WebDriverError (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/error.js:27:5)
    at Object.checkLegacyResponse (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/error.js:505:15)
    at parseHttpResponse (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/http.js:440:13)
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/root/co/tests/e2e/node_modules/selenium-webdriver/lib/webdriver.js:777:24)
    at Function.createSession (/root/co/tests/e2e/node_modules/selenium-webdriver/chrome.js:709:29)
    at Direct.getNewDriver (/root/co/tests/e2e/node_modules/protractor/lib/driverProviders/direct.ts:90:25)
    at Runner.createBrowser (/root/co/tests/e2e/node_modules/protractor/lib/runner.ts:225:39)
    at q.then.then (/root/co/tests/e2e/node_modules/protractor/lib/runner.ts:391:27)
    at _fulfilled (/root/co/tests/e2e/node_modules/q/q.js:834:54)
    at self.promiseDispatch.done (/root/co/tests/e2e/node_modules/q/q.js:863:30)
    at Promise.promise.promiseDispatch (/root/co/tests/e2e/node_modules/q/q.js:796:13)
    at /root/co/tests/e2e/node_modules/q/q.js:556:49
    at runSingle (/root/co/tests/e2e/node_modules/q/q.js:137:13)
[10:53:57] E/launcher - Process exited with error code 199

Adding Chromedriver to the /usr/local/bin folder solved the issue for me.

I faced the same issue. Just install or update the protractor. If you still installed the protractor also Do the following steps, run the following in cmd prompt or PowerShell

npm install protractor -g

npm install webdriver-manager -g

If you got the error as running in the background, check the running processor and close all the running processor and try.

After the above steps run the following

webdriver-manager update
webdriver-manager start
Was this page helpful?
0 / 5 - 0 ratings