getting 'chrome failed to start' when trying to run an instance of protractor

[ClemannD]

Current setup:
I have an ECS cluster with 4 EC2 instances, one of them running selenium-hub and i have 4 selenium/chrome-node containers running, using your python script to get the nodes and hub to be able to communicate.

Using selenium/3.141.59-vanadium for hub and nodes.

My grid configuration:

My EC2 instances have 16gb ram, I have given the nodes 2gb ram, and am mounting to dev/shm of the host. (confirmed the mount is actually working by creating test file in dev/shm of host and am able to see it in dev/shm of docker container).

The Issue:
When I start protractor and point it to my selenium hub, I am getting

All the suggestions when I google (unknown error: DevToolsActivePort file doesn't exist) say to try different combinations of --no-sandbox, --disable-dev-shm-usage and so on, tried them all, no luck.

Was wondering if this issue has been encountered by anyone and what possible solutions may be,
Thank you

[ClemannD]

I ended up solving this.

Turns out we were setting chromeOptions: instead of goog:chromeOptions:.
Not sure what the difference is, since chromeOptions: always worked for us in the past.

[mmerrell]

The difference might be in the fact that chromeOptions by itself isn't W3C-compliant, which has been switched on in ChromeDriver by default as of version 76.0. It's not a change on the part of the selenium project. MM

…

Sent from my iPhone

On Oct 7, 2019, at 1:12 PM, Dylan Clemann ***@***.***> wrote: I ended up solving this. Turns out we were setting chromeOptions: instead of goog:chromeOptions:. Not sure what the difference is, since chromeOptions: always worked for us in the past. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.