Protractor - error starting webdriver-manager, seleniumProcess.pid: undefined
I got a problem running webdriver-manager in node_modules \ protractor with windows 7. command:
node webdriver-manager start
Then I got the following error messages:
seleniumProcess.pid: undefined
events.js:85
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at exports._errnoException (util.js:742:11)
at Process.ChildProcess._handle.onexit (child_process.js:1028:32)
at child_process.js:1109:20
at process._tickCallback (node.js:343:11)
at Function.Module.runMain (module.js:492:11)
at startup (node.js:124:16)
at node.js:807:3
After searching the web, I cannot find the same question as mine that seleniumProcess.pid is undefined.
Below is the output for java -version:
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
Any idea?
source to share
Ok, I figured out why I was having this problem. You only have JRE, but
You will need to install the Java Development Kit (JDK) to run the Selenium standalone server. Check it out by running java -version from the command line. Tutorial
On Ubuntu I did
$ sudo apt-get install openjdk-7-jdk
And now I have this Java:
$ java -version
java version "1.7.0_95"
OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.1)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
And it webdriver-manager start
works.
source to share
Error: C: \ XXXX \ AppData \ Roaming \ NPM \ node_modules \ protractor \ node_modules \ webdriv er-manager \ bin> webdriver-manager - updated update
events.js: 160 throw er; // Unhandled 'error' event ^
Error: Unable to validate first certificate on error (native) in TLSSocket. (_tls_wrap.js: 1092: 38) at emitNone (events.js: 86: 13) at TLSSocket.emit (events.js: 185: 7) at TLSSocket._finishInit (_tls_wrap.js: 610: 8) at TLSWrap.ssl .onhandshakedone (_tls_wrap.js: 440: 38)
I did the following to remove this:
Try: 1. C: \ XX \ Roaming \ npm \ node_modules \ protractor \ node_modules \ webdriv er-manager \ bin> webdriver-manager --proxy http: // username: passwd @ IP : port 080 / update (Then it updated drivers in location)
-
webdriver-manager status
-
C: \ XX \ AppData \ Roaming \ npm \ node_modules \ protractor \ node_modules \ webdriver-manager \ bin> webdriver-manager --verbose start
Work starts, I expect it to happen repeatedly due to driver corruption. May we need to gracefully stop working.
source to share