NEWS
[Aufruf] Bitte js-controller 1.0.3 + admin 1.7.6 testen
-
Hallo Bluefox,
bei der Admin Installation kommt folgender Fehler:
root@iobroker2:/opt/iobroker# npm install iobroker.admin > mdns@2.3.3 install /opt/iobroker/node_modules/mdns > node-gyp rebuild make: Entering directory '/opt/iobroker/node_modules/mdns/build' CXX(target) Release/obj.target/dns_sd_bindings/src/dns_sd.o In file included from ../src/dns_sd.cpp:1:0: ../src/mdns.hpp:32:20: fatal error: dns_sd.h: Datei oder Verzeichnis nicht gefunden #include <dns_sd.h>^ compilation terminated. dns_sd_bindings.target.mk:149: recipe for target 'Release/obj.target/dns_sd_bindings/src/dns_sd.o' failed make: *** [Release/obj.target/dns_sd_bindings/src/dns_sd.o] Error 1 make: Leaving directory '/opt/iobroker/node_modules/mdns/build' gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23) gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at ChildProcess.emit (events.js:191:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) gyp ERR! System Linux 3.16.0-4-686-pae gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /opt/iobroker/node_modules/mdns gyp ERR! node -v v6.10.3 gyp ERR! node-gyp -v v3.4.0 gyp ERR! not ok iobroker.core@0.1.0 /opt/iobroker └── (empty) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.3 (node_modules/mdns): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.3 install: `node-gyp rebuild` npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 npm ERR! code 1</dns_sd.h> -
Aber geht trotzdem alles. :?
JS-Controller auf 1.0.3 und admin auf 1.7.6.
-
Updates auf Win10 durchgeführt.
Keine Probleme.
Grüße
-
Ich habe auf Pi3 geupdatet ohne Probleme danach, nur paar Fehlermeldungen (npm ERR) während der Installation.
Beim brix lief es nicht so gut. Habe dabei auch ein apt-get update und upgrade durchgeführt (8 ubuntu updates).
root@brix-3150:/opt/iobroker# sudo iobroker status module.js:471 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.runMain (module.js:604:10) at run (bootstrap_node.js:390:7) at startup (bootstrap_node.js:150:9) at bootstrap_node.js:505:3 root@brix-3150:/opt/iobroker#EDIT: es reichte folgendes aus. Scheint erstmal normal zu laufen
root@brix-3150:/opt/iobroker# npm install iobroker.js-controller --production -
Hallo in die Runde,
habe mich auch getraut und wollte meinen Beitrag zum Test leisten. System läuft seit paar Minuten unauffällig. Hatte nur bei der installation auf meinem Raspberry Pi3 unten angehangene Fehlermeldung via Putty:
root@raspberrypi3:/opt/iobroker# sudo iobroker upgrade self
npm install iobroker.js-controller@1.0.3 –production --prefix "/opt/iobroker" (System call)
Cannot save file /opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json: Error: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json'
Host "raspberrypi3" (linux) updated
Execute: chmod 777 -R /opt/iobroker
Chmod finished. Restart controller
Starting node restart.js
VG kueppert
PS: gerade festgestellt, dass beim Adapter fritz.box die history Einträge jetzt leer sind… Keine Ahnung, ob das nach einem Neustart immer so ist?!
-
Läuft seit 12 Stunden ohne sichtbare Probleme
–-----------------------
Send from mobile device
-
Verdammt - bei mir läuft es natürlich wieder mal nicht…
Habe gerade zuerst admin und dann js-controller upgedatet. Danach verabschiedete sich iobroker...
Habe jetzt schon einiges versucht, inkl. iobroker Neuinstallation - keine Reaktion, nur npm Fehler...
root@raspberrypi:/opt/iobroker# npm install iobroker.js-controller --production npm ERR! Linux 4.4.43-v7+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker.js-controller" "--production" npm ERR! node v4.7.2 npm ERR! npm v2.15.11 npm ERR! file /root/.npm/iobroker.js-controller/1.0.3/package/package.json npm ERR! code EJSONPARSE npm ERR! Failed to parse json npm ERR! No data, empty input at 1:1 npm ERR! npm ERR! ^ npm ERR! File: /root/.npm/iobroker.js-controller/1.0.3/package/package.json npm ERR! Failed to parse package.json data. npm ERR! package.json must be actual JSON, not just JavaScript. npm ERR! npm ERR! This is not a bug in npm. npm ERR! Tell the package author to fix their package.json file. JSON.parse npm ERR! Please include the following file with any support request: npm ERR! /opt/iobroker/npm-debug.log root@raspberrypi:/opt/iobroker#root@raspberrypi:/opt/iobroker# sudo npm install iobroker --unsafe-perm npm ERR! not a package /opt/iobroker/iobroker npm ERR! addLocal Could not install /opt/iobroker/iobroker npm ERR! Linux 4.4.43-v7+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "iobroker" "--unsafe-perm" npm ERR! node v4.7.2 npm ERR! npm v2.15.11 npm ERR! path /tmp/npm-1585-16846667/unpack-82b0f14b7517/package.json npm ERR! code ENOENT npm ERR! errno -2 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-1585-16846667/unpack-82b0f14b7517/package.json' 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! Please include the following file with any support request: npm ERR! /opt/iobroker/npm-debug.log root@raspberrypi:/opt/iobroker#Kann mir bitte mal jemand helfen?
-
Jippie - läuft! Vielen Dank. Jetzt muss ich nur noch mein web.1 (SSL Zugriff) wieder zum Laufen bringen.
Was zur Hölle ist "greenlock"?!?
host.raspberrypi 2017-06-05 19:48:18.722 error instance system.adapter.web.1 terminated with code 0 (OK) web.1 2017-06-05 19:48:18.314 error at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12) web.1 2017-06-05 19:48:18.314 error at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9) web.1 2017-06-05 19:48:18.314 error at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:639:21) web.1 2017-06-05 19:48:18.314 error at /opt/iobroker/node_modules/iobroker.web/main.js:166:29 web.1 2017-06-05 19:48:18.314 error at initWebServer (/opt/iobroker/node_modules/iobroker.web/main.js:507:28) web.1 2017-06-05 19:48:18.314 error at Object.createServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:13:25) web.1 2017-06-05 19:48:18.314 error at require (internal/module.js:12:17) web.1 2017-06-05 19:48:18.314 error at Module.require (module.js:353:17) web.1 2017-06-05 19:48:18.314 error at Function.Module._load (module.js:276:25) web.1 2017-06-05 19:48:18.314 error at Function.Module._resolveFilename (module.js:325:15) web.1 2017-06-05 19:48:18.314 error Error: Cannot find module 'greenlock' web.1 2017-06-05 19:48:18.294 error uncaught exception: Cannot find module 'greenlock' -
Guten Morgen,
was mir heute aufgefallen ist, da ich nun 2 ModBus-Instanzen habe. Die erste Instanz ist knapp 2 Jahre alt und die neue ein paar Tage.
Schaut mal. (Einstellungen unter ModBus sind identisch außer die Adressen) Es gibt in der letzten Instanz Input-Level und Output-Level. Ist das so geplant?
Jetzt bekomme ich ab und an auch mal den gleichen Fehler wie Apollon:
modbus.1 2017-06-10 06:14:30.985 warn Poll error count: 6 code: "App Timeout" modbus.1 2017-06-10 06:14:30.969 warn Poll error count: 5 code: "App Timeout" modbus.1 2017-06-10 06:14:30.508 warn Poll error count: 4 code: "App Timeout" modbus.1 2017-06-10 06:14:30.380 warn Poll error count: 3 code: "App Timeout" modbus.1 2017-06-10 06:14:30.360 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:30.211 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:29.589 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:27.973 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:27.950 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:25.665 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:24.954 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:24.787 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:24.767 warn Poll error count: 3 code: "App Timeout" modbus.1 2017-06-10 06:14:24.609 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:24.325 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:24.178 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:21.907 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:21.769 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:18.751 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:18.584 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:18.421 warn Poll error count: 1 code: "App Timeout" modbus.1 2017-06-10 06:14:18.122 warn Poll error count: 3 code: "App Timeout" modbus.1 2017-06-10 06:14:17.975 warn Poll error count: 2 code: "App Timeout" modbus.1 2017-06-10 06:14:17.823 warn Poll error count: 1 code: "App Timeout"Daten kommen trotzdem.
Gruß Marco
Support us
706
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge