Windows 10 installation schlägt fehl
-
Hallo, sorry für das Noob Thema, aber ich bekomme iobroker nicht installiert unter Windows 10 (64bit)
Habe es über den Windowsinstaller probiert (auch mal ala Admin) - der endet damit, das localhost:8081 aufgerufen wird - was nichts zum Vorschein brachte.
Dann habe ich es auch probiert mit npm install iobroker in einer Eingabeaufforderung mit Adminrechten. Erfolglos.
Wer das log lesen will:
! ````
iobroker@1.0.8 install C:\installs\ioBroker\node_modules\iobroker
node lib/setup.js
! NPM version: 2.15.9
! npm install iobroker.discovery --production --save --prefix "C:/installs/ioBroker"
npm install iobroker.admin --production --save --prefix "C:/installs/ioBroker"
npm install iobroker.js-controller --production --save --prefix "C:/installs/ioBroker"
npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:449:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:404:11
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:82:15)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\winston-syslog\node_modules\unix-dgram
gyp ERR! node -v v4.5.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional dep failed, continuing unix-dgram@0.2.3
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:449:14)
gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:404:11
gyp ERR! stack at FSReqWrap.oncomplete (fs.js:82:15)
gyp ERR! System Windows_NT 10.0.16299
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\greenlock\node_modules\rsa-compat\node_modules\ursa
gyp ERR! node -v v4.5.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional dep failed, continuing ursa@0.9.4
Write "iobroker start" to start the ioBroker
npm install https://github.com/arthurblake/node-windows/tarball/f1fd60e93e2469663b99a9cf3a64086ecedfe1e4 --production --save --prefix "C:/installs/ioBroker/"
ioBroker service installed. Write "serviceIoBroker start" to start the service and go to http://localhost:8081 to open the admin UI.
To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller"
iobroker@1.0.8 node_modules\iobroker
└── yargs@7.1.0 (get-caller-file@1.0.2, decamelize@1.2.0, camelcase@3.0.0, y18n@3.2.1, which-module@1.0.0, set-blocking@2.0.0, require-main-filename@1.0.1, yargs-parser@5.0.0, require-directory@2.1.1, os-locale@1.4.0, cliui@3.2.0, string-width@1.0.2, read-pkg-up@1.0.1)Weil ich irgendwo gelesen haben, dass man ein aktuelles __npm__ braucht, hab ich auf das neuste stable aktualisiert. Danach wieder ein installversuch, der nichts brachte. Log: >! ```` > unix-dgram@0.2.3 install C:\installs\ioBroker\node_modules\unix-dgram > node-gyp rebuild >! C:\installs\ioBroker\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19) gyp ERR! stack at PythonFinder. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\installs\ioBroker\node_modules\unix-dgram gyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok >! > ursa@0.9.4 install C:\installs\ioBroker\node_modules\ursa > node-gyp rebuild >! C:\installs\ioBroker\node_modules\ursa>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19) gyp ERR! stack at PythonFinder. <anonymous>(C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\installs\ioBroker\node_modules\ursa gyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok >! > iobroker@1.0.8 install C:\installs\ioBroker\node_modules\iobroker > node lib/setup.js >! NPM version: 5.6.0 >! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! NPM 5 is currently NOT supported! Please use "npm install -g npm@4" to downgrade npm to 4.x and try again. You need to make sure to downgrade again with the above command after you installed an update to nodejs/npm! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\unix-dgram): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 (node_modules\ursa): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 >! npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! iobroker@1.0.8 install: `node lib/setup.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the iobroker@1.0.8 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. >! npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-01-31T22_06_37_811Z-debug.log</anonymous></anonymous>Er meckert eine zu hohe npm Version an, also ein Downgrade von npm mit npm install -g npm@4 und wieder npm install iobroker
Ergebnis:
> unix-dgram@0.2.3 install C:\installs\ioBroker\node_modules\unix-dgram > node-gyp rebuild C:\installs\ioBroker\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Users\User\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:482:19) gyp ERR! stack at PythonFinder. <anonymous>(C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\User\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\installs\ioBroker\node_modules\unix-dgram gyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.0 gyp ERR! not ok > ursa@0.9.4 install C:\installs\ioBroker\node_modules\ursa > node-gyp rebuild C:\installs\ioBroker\node_modules\ursa>if not defined npm_config_node_gyp (node "C:\Users\User\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:482:19) gyp ERR! stack at PythonFinder. <anonymous>(C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Users\User\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:152:21) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\User\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" gyp ERR! cwd C:\installs\ioBroker\node_modules\ursa gyp ERR! node -v v8.9.4 gyp ERR! node-gyp -v v3.6.0 gyp ERR! not ok > iobroker@1.0.8 install C:\installs\ioBroker\node_modules\iobroker > node lib/setup.js NPM version: 4.6.1 npm install iobroker.discovery --production --save --prefix "C:/installs/ioBroker" npm install iobroker.admin --production --save --prefix "C:/installs/ioBroker" npm install iobroker.js-controller --production --save --prefix "C:/installs/ioBroker" npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated npm ERR! path C:\installs\ioBroker\node_modules\.staging\ansicolors-61fc3ae1 npm ERR! code ENOENT npm ERR! errno -4058 npm ERR! syscall rename npm ERR! enoent ENOENT: no such file or directory, rename 'C:\installs\ioBroker\node_modules\.staging\ansicolors-61fc3ae1' -> 'C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\npm\node_modules\ansicolors' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-01-31T22_12_02_270Z-debug.log Write "iobroker start" to start the ioBroker npm install https://github.com/arthurblake/node-windows/tarball/f1fd60e93e2469663b99a9cf3a64086ecedfe1e4 --production --save --prefix "C:/installs/ioBroker/" ioBroker service installed. Write "serviceIoBroker start" to start the service and go to http://localhost:8081 to open the admin UI. To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller" iobroker.inst@1.0.8 C:\installs\ioBroker `-- iobroker@1.0.8 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\unix-dgram): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 (node_modules\ursa): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1</anonymous></anonymous>Danach gebe ich serviceIoBroker start ein und es kommt:
============================= Running Admin shell ============================= Der Name für den Dienst ist ungültig.Was sollte ich als nächstes probieren? DANKE!
-
Was mir erstmal auffällt: Stimmt der Pfad "C:/installs/ioBroker" wirklich? Hast du den so angegeben? Hast du dann in der Konsole auch dran gedacht ggf. in diesen Pfad zu wechseln? Standardmäßig installieren wir alle nach "C:/ioBroker"… Nicht dass da was durcheinander ist...
-
Deinem windows fehlen Build Tools und Python und sowas. Installieren mal https://www.npmjs.com/package/windows-build-tools … dann Versuch nochmal.
-
Was mir erstmal auffällt: Stimmt der Pfad "C:/installs/ioBroker" wirklich? Hast du den so angegeben? Hast du dann in der Konsole auch dran gedacht ggf. in diesen Pfad zu wechseln? Standardmäßig installieren wir alle nach "C:/ioBroker"… Nicht dass da was durcheinander ist... `
ja, das ist korrekt so. In dem Verzeichnis stehe ich mit der Eingabeaufforderung bei meinen Installationsversuchen. -
Deinem windows fehlen Build Tools und Python und sowas. Installieren mal https://www.npmjs.com/package/windows-build-tools … dann Versuch nochmal. `
OK danke, probiere ich mal. Dauert aber schon eine halbe Stunde… morgen weiß ich mehr. -
Deinem windows fehlen Build Tools und Python und sowas. Installieren mal https://www.npmjs.com/package/windows-build-tools … dann Versuch nochmal. `
Das geht bei mir nicht
C:\WINDOWS\system32>npm install --global --production windows-build-tools > windows-build-tools@1.4.0 postinstall C:\Users\User\AppData\Roaming\npm\node_modules\windows-build-tools > node ./lib/index.js Downloading BuildTools_Full.exe Downloading python-2.7.14.amd64.msi [============================================>] 100.0% of 20.17 MB (5.76 MB/s) Downloaded python-2.7.14.amd64.msi. Saved to C:\Users\User\.windows-build-tools\python-2.7.14.amd64.msi. Starting installation... Launched installers, now waiting for them to finish. This will likely take some time - please be patient! Waiting for installers... \Successfully installed Visual Studio Build Tools. Waiting for installers... |Batchvorgang abbrechen (J/N)? j C:\WINDOWS\system32>npm install --global --production windows-build-tools > windows-build-tools@1.4.0 postinstall C:\Users\User\AppData\Roaming\npm\node_modules\windows-build-tools > node ./lib/index.js Downloading BuildTools_Full.exe Downloading python-2.7.14.amd64.msi [> ] 0.0% (0 B/s) Downloaded python-2.7.14.amd64.msi. Saved to C:\Users\User\.windows-build-tools\python-2.7.14.amd64.msi. Starting installation... Launched installers, now waiting for them to finish. This will likely take some time - please be patient! Waiting for installers... -Successfully installed Visual Studio Build Tools. Waiting for installers... | ````und da bleibt er hängen für Stunden ein ioBroker install danach endet so: ` > C:\installs\ioBroker>npm install iobroker > > > iobroker@1.0.8 install C:\installs\ioBroker\node_modules\iobroker > > > node lib/setup.js > > NPM version: 4.6.1 > > npm install iobroker.discovery –production --save --prefix "C:/installs/ioBroker" > > npm install iobroker.admin --production --save --prefix "C:/installs/ioBroker" > > npm install iobroker.js-controller --production --save --prefix "C:/installs/ioBroker" > > npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated > > npm ERR! path C:\installs\ioBroker\node_modules\.staging\ansicolors-61fc3ae1 > > npm ERR! code ENOENT > > npm ERR! errno -4058 > > npm ERR! syscall rename > > npm ERR! enoent ENOENT: no such file or directory, rename 'C:\installs\ioBroker\node_modules\.staging\ansicolors-61fc3ae1' -> 'C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\npm\node_modules\ansicolors' > > npm ERR! enoent This is most likely not a problem with npm itself > > npm ERR! enoent and is related to npm not being able to find a file. > > npm ERR! enoent > > npm ERR! A complete log of this run can be found in: > > npm ERR! C:\Users\User\AppData\Roaming\npm-cache\_logs\2018-02-01T07_43_43_682Z-debug.log > > Write "iobroker start" to start the ioBroker > > npm install [https://github.com/arthurblake/node-win ... 6ecedfe1e4](https://github.com/arthurblake/node-windows/tarball/f1fd60e93e2469663b99a9cf3a64086ecedfe1e4) --production --save --prefix "C:/installs/ioBroker/" > > ioBroker service installed. Write "serviceIoBroker start" to start the service and go to [http://localhost:8081](http://localhost:8081) to open the admin UI. > > To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller" > > iobroker.inst@1.0.8 C:\installs\ioBroker > > `-- iobroker@1.0.8 > > npm WARN enoent ENOENT: no such file or directory, open 'C:\installs\ioBroker\node_modules\iobroker.js-controller\package.json' > > npm WARN enoent ENOENT: no such file or directory, open 'C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\express\package.json' > > npm WARN enoent ENOENT: no such file or directory, open 'C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\finalhandler\package.json' > > npm WARN enoent ENOENT: no such file or directory, open 'C:\installs\ioBroker\node_modules\iobroker.js-controller\node_modules\http-errors\package.json' > > C:\installs\ioBroker> ` -
versuch mal ein npm cache clean und dann nochmal neu
-
versuch mal ein npm cache clean und dann nochmal neu `
Danke, aber hilft nicht. Bleibt wieder da hängen..dabei will ich doch nur ein bisschen rumprobieren, bevor ich mich an einen Raspi-Install wage. Weil ich dachte DER ist kompliziert
-
Dann weiss ich leider auch nimmer weiter. Haben es leztztens in einem anderen thread ausführlich getestet …auch auf Win10 ...
-
Danke, aber hilft nicht. Bleibt wieder da hängen
..dabei will ich doch nur ein bisschen rumprobieren, bevor ich mich an einen Raspi-Install wage. Weil ich dachte DER ist kompliziert
`Wo bleibt er "da" hängen? Beim "Waiting for installers…" oder bei "npm WARN enoent..."?
Was mit gerade noch aufgefallen ist:
Waiting for installers... \Successfully installed Visual Studio Build Tools. Waiting for installers... |Batchvorgang abbrechen (J/N)? j C:\WINDOWS\system32>npm install --global --production windows-build-toolsWarum hast du da den Batchvorgang abgebrochen??? Vielleicht die VS Build Tools nochmal vollständig installieren…
Allerdings ist mir auch ziemlich schleierhaft was da mit deinem Windows los ist. Ich habe vor kurzem erst testweise 2 Windows-Installationen gemacht, die sind ohne zu mucken durchgelaufen...
