Cannot launch Chrome: OSX 10.9.3, Selenium 2.42.0, chromedriver 2.10

[ldeavila]

Trying to run protractor tests on OSX. We get the error below. Have tried a variety of fixes suggested. I think we're running the latest stand-alone server and chrome driver. Thoughts?

/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:109
 var template = new Error(this.message);
                ^
UnknownError: null
   at new bot.Error (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/error.js:109:18)
   at Object.bot.response.checkResponse (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/atoms/response.js:106:9)
   at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:134:24
   at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1243:15
   at webdriver.promise.ControlFlow.runInNewFrame_ (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1531:20)
   at notify (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:354:12)
   at notifyAll (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:323:7)
   at resolve (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:301:7)
   at fulfill (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:421:5)
   at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1243:15
==== async task ====
WebDriver.createSession()
   at Function.webdriver.WebDriver.acquireSession_ (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:131:49)
   at Function.webdriver.WebDriver.createSession (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/webdriver.js:111:30)
   at Builder.build (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/selenium-webdriver/builder.js:106:20)
   at HostedDriverProvider.getDriver (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/lib/driverProviders/hosted.js:54:9)
   at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/lib/runner.js:207:35
   at _fulfilled (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:797:54)
   at self.promiseDispatch.done (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:826:30)
   at Promise.promise.promiseDispatch (/Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:759:13)
   at /Users/riley/dash.frontend/node_modules/grunt-protractor-runner/node_modules/protractor/node_modules/q/q.js:525:49

[juliemr]

You're right, the error is in not starting chrome. Can you post the logs from the selenium stand-alone server?

[ldeavila]

Hi Julie.

Here is the log. The log is from a different box (first was a macbook pro, this one is from a mac mini) but the errors are exactly the same.

Browsers-Mac-mini:dash.frontend btp$ ./node_modules/protractor/bin/webdriver-manager start
seleniumProcess.pid: 2695
Jun 20, 2014 10:56:02 AM org.openqa.grid.selenium.GridLauncher main
INFO: Launching a standalone server
Setting system property webdriver.chrome.driver to /Users/btp/dash.frontend/node_modules/protractor/selenium/chromedriver
10:56:02.323 INFO - Java: Apple Inc. 20.65-b04-462
10:56:02.323 INFO - OS: Mac OS X 10.9.2 x86_64
10:56:02.334 INFO - v2.42.0, with Core v2.42.0. Built from revision 5e82430
10:56:02.397 INFO - Default driver org.openqa.selenium.ie.InternetExplorerDriver registration is skipped: registration capabilities Capabilities [{platform=WINDOWS, ensureCleanSession=true, browserName=internet explorer, version=}] does not match with current platform: MAC
10:56:02.447 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
10:56:02.448 INFO - Version Jetty/5.1.x
10:56:02.448 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
10:56:02.449 INFO - Started HttpContext[/selenium-server,/selenium-server]
10:56:02.449 INFO - Started HttpContext[/,/]
10:56:02.489 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@56d73c7a
10:56:02.490 INFO - Started HttpContext[/wd,/wd]
10:56:02.495 INFO - Started SocketListener on 0.0.0.0:4444
10:56:02.495 INFO - Started org.openqa.jetty.jetty.Server@4ca31e1b
10:56:16.516 INFO - Executing: [new session: Capabilities [{count=1, browserName=chrome}]])
10:56:16.530 INFO - Creating a new session for Capabilities [{count=1, browserName=chrome}]
Starting ChromeDriver (v2.10.267517) on port 48763
Only local connections are allowed.
10:56:36.860 WARN - Exception thrown
java.util.concurrent.ExecutionException: org.openqa.selenium.WebDriverException: java.lang.reflect.InvocationTargetException
Build info: version: '2.42.0', revision: '5e82430', time: '2014-05-22 20:18:07'
System info: host: 'Browsers-Mac-mini.local', ip: '192.168.0.31', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.2', java.version: '1.6.0_65'
Driver info: driver.version: unknown
    at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
    at java.util.concurrent.FutureTask.get(FutureTask.java:83)
    at org.openqa.selenium.remote.server.DefaultSession.execute(DefaultSession.java:176)
    at org.openqa.selenium.remote.server.DefaultSession.<init>(DefaultSession.java:112)
    at org.openqa.selenium.remote.server.DefaultSession.createSession(DefaultSession.java:89)
    at org.openqa.selenium.remote.server.DefaultDriverSessions.newSession(DefaultDriverSessions.java:110)
    at org.openqa.selenium.remote.server.handler.NewSession.handle(NewSession.java:57)
10:56:36.869 WARN - Exception: null

Many Thanks

[juliemr]

Look suspiciously similar to this ChromeDriver issue: https://code.google.com/p/chromedriver/issues/detail?id=736

[ldeavila]

Does look very similar.
Started stand-alone server with java, like in the linked issue, and got a similar stack trace.
I verified that Chrome is installed in the expected path as defined here: https://code.google.com/p/selenium/wiki/ChromeDriver

I'm pretty stumped.

[juliemr]

I just updated the version of selenium-standalone on master from 2.42.0 to 2.42.2. If you're able, could you try running with that and see if it's fixed?

The next version of protractor on npm with this bump should be out next week.

[juliemr]

Version bump is now out. Is this fixed?

[ldeavila]

Hi Julie. Sorry for the delay. Unfortunately, the update to version 2.42.2 did not help. Also, unfortunately, the team is moving on and is going to write python-based selenium tests so the priority on this is pretty low now.

I'd personally would still like to get this working for other projects. I'll keep pounding away at this every once in a while. Any other suggestions?

[juliemr]

I'm curious how the team is starting ChromeDriver with python based tests, since this issue doesn't seem specific to Protractor versus other methods of using selenium.

Unfortunately, my only suggestions are to keep watching that chromedriver issue.

[seanrafferty]

I was getting the exact same errors. I battled this issue for a few hours today. It seemed to be caused by a mismatch between the versions of chromedriver and selenium-server-standalone. The config.js file was referencing a directory that had chromedriver 2.9 and selenium-server-standalone 2.35.0. Once I made sure we were referencing 2.10 and 2.42.2, it worked.

Is it possible protractor is finding different versions of these files on your PATH somewhere other than you expect? As a test, you can try to explicitly set the seleniumServerJar and chromeDriver values in the protractor conf.js file e.g.

seleniumServerJar: '/usr/local/lib/node_modules/protractor/selenium/selenium-server-standalone-2.42.2.jar',
chromeDriver: '/usr/local/lib/node_modules/protractor/selenium/chromedriver',

You might also unzip /usr/local/lib/node_modules/protractor/selenium/chromedriver_2.10.zip to be certain you have the correct version.

[ldeavila]

Finally had some time to work on this again. Unfortunately, even with Sean's suggestions I was unable to get selenium to launch a chrome instance. I still get the same error. I don't think it's a file version issue since this is a brand new machine. I'll keep investigating.

[lopesc]

Same issue here on Windows with standalone jar 2.42.2 and chromedriver 2.10!

[danemacaulay]

Ditto, with same versions on osx

[lopesc]

Does anybody know how the issue here was fixed:
https://groups.google.com/forum/#!topic/angular-dev/kXk4bkHdY5A

You'll note that build 402 fails with the same error we are getting and then build 403 is fine. It might be indicating that something was misconfigured on the machine, since there were no changes in the repository between those two builds.

Date: Mon, 28 Jul 2014 14:13:55 -0700
From: notifications@github.com
To: protractor@noreply.github.com
Subject: Re: [protractor] Cannot launch Chrome: OSX 10.9.3, Selenium 2.42.0, chromedriver 2.10 (#954)

Ditto, with same versions on osx

—
Reply to this email directly or view it on GitHub.

[coderigo]

Fixed same issue here on OS X 10.9.4.

Was able to get it to work by downlading chromedriver 2.9, and renaming the existing 2.10 version to end with 2.10 so that protractor picks up the 2.9 version I copied in there:

That is the chromedriver in the above image is the 2.9 version.

My protractor config file looks like this and it works fine with chrome now:

I'm very green to this but hopefully that helps someone. Not sure what I'm missing out on by downgrading to 2.9 but will find out I guess and in the meantime keep an eye on the issue to see when it's OK to try with >2.10.

I'm off to learn more about all this now.