fehlender iobroker.js-controller nach Installation
-
Hallo,
ich bekomme auf meinem raspberry 4 den iobroker einfach nicht zum laufen - es läuft immer wieder auf folgende Fehlermeldung hinaus:
node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }ich habe es mit verschiedenen Versionen von node und npm versucht - Resultat ist immer das gleiche (aktuell arbeite ich mit 8.11 und 16.15.1 - in der Kombination lief zumindest mal die Skriptinstallation durch). Der Fixer bringt auch nichts, da folgender Output:
root@raspberrypi:/opt/iobroker# curl -sL https://iobroker.net/fix.sh | bash - library: loaded Library version=2022-02-10 ioBroker is not installed in /opt/iobroker! Cannot fix anything...Aber er ist doch installiert!!!
Das übliche habe ich auch schon hinter mir apt ist up to date, reboot etc. Vielleicht kennt jemand das Problem, denn der Ordner /opt/iobroker/node_modules fehlt tatsächich... ich hab es auch als User statt root probiert, gleiches Problem.
-
In der ersten Meldung steht schon was er will....JS-Controller.
Den nochmal sauber installieren.
Und dann die Nodejs auf die empfohlene Version bringen V14, NPM6 -
Das übliche...
Kein root verwenden. Nie. Gar nicht.
Die Installation per Einzeiler? Ist eigentlich Idiotensicher.
-
@nabonid sagte in fehlender iobroker.js-controller nach Installation:
Aber er ist doch installiert!!!
aber anscheinend
@nabonid sagte in fehlender iobroker.js-controller nach Installation:
not installed in /opt/iobroker
-
Vielen Dank für den superschnellen Input - hatte gestern noch Nachtdienst, daher gehts erst heute weiter.
- Versionen sind auf die Empfehlung angepasst
pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.3 v14.19.3 6.14.17 pi /home/pi OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 https://packages.grafana.com/oss/deb stable InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:5 https://repos.influxdata.com/debian buster InRelease OK:6 http://dl-origin.ubnt.com/unifi/debian stable InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. nodejs: Installiert: 14.19.3-deb-1nodesource1 Installationskandidat: 14.19.3-deb-1nodesource1 Versionstabelle: *** 14.19.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages- erneute Installation ioBroker über den Installer nach löschen der alten Installation:
pi@raspberrypi:~ $ curl -sLf https://iobroker.net/install.sh | bash - library: loaded Library version=2022-02-10 ========================================================================== Welcome to the ioBroker installer! Installer version: 2022-02-13 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== OK:1 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:2 https://packages.grafana.com/oss/deb stable InRelease OK:3 http://archive.raspberrypi.org/debian buster InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:5 https://repos.influxdata.com/debian buster InRelease OK:6 http://dl-origin.ubnt.com/unifi/debian stable InRelease Paketlisten werden gelesen... Fertig Changing npm registry to https://registry.npmjs.org Installed gcc-c++ ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== In file included from ../../nan/nan.h:60, from ../src/main.cpp:3: /home/pi/.cache/node-gyp/14.19.3/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/pi/.cache/node-gyp/14.19.3/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(diskusage, Init) ^~~~~~~~~~~ In file included from ../../nan/nan.h:60, from ../src/unix_dgram.cc:5: /home/pi/.cache/node-gyp/14.19.3/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/pi/.cache/node-gyp/14.19.3/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(unix_dgram, Initialize) ^~~~~~~~~~~ npm ERR! code ELIFECYCLE npm ERR! errno 24 npm ERR! iobroker.js-controller@4.0.23 install: `node iobroker.js setup first` npm ERR! Exit status 24 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.23 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! /home/pi/.npm/_logs/2022-06-03T11_43_35_389Z-debug.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.1.242 192.168.193.5:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! pi@raspberrypi:~ $- WebUI nicht errreichbar und weiterhin die Fehlermeldung
pi@raspberrypi:/opt/iobroker $ iobroker internal/modules/cjs/loader.js:905 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15) at Function.Module._load (internal/modules/cjs/loader.js:746:27) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12) at internal/main/run_main_module.js:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }- manuelle Installation des Controllers
pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs internal/modules/cjs/loader.js:905 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/controller.js' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15) at Function.Module._load (internal/modules/cjs/loader.js:746:27) at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:75:12) at internal/main/run_main_module.js:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] } pi@raspberrypi:/opt/iobroker $ iobroker stop pi@raspberrypi:/opt/iobroker $ npm install iobroker.js-controller > iobroker.js-controller@4.0.23 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.17 > unix-dgram@2.0.4 install /opt/iobroker/node_modules/unix-dgram > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird betreten CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o In file included from ../../nan/nan.h:60, from ../src/unix_dgram.cc:5: /home/iobroker/.cache/node-gyp/14.19.3/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/14.19.3/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(unix_dgram, Initialize) ^~~~~~~~~~~ SOLINK_MODULE(target) Release/obj.target/unix_dgram.node COPY Release/unix_dgram.node make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird verlassen > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional > node rebuild.js ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks. > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage > node-gyp rebuild make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird betreten CXX(target) Release/obj.target/diskusage/src/main.o In file included from ../../nan/nan.h:60, from ../src/main.cpp:3: /home/iobroker/.cache/node-gyp/14.19.3/include/node/node.h:793:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/iobroker/.cache/node-gyp/14.19.3/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(diskusage, Init) ^~~~~~~~~~~ CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o SOLINK_MODULE(target) Release/obj.target/diskusage.node COPY Release/diskusage.node make: Verzeichnis „/opt/iobroker/node_modules/diskusage/build“ wird verlassen > iobroker.js-controller@4.0.23 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software! pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs armv7l /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.3 v14.19.3 6.14.17 pi /home/pi OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:3 https://packages.grafana.com/oss/deb stable InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:5 https://repos.influxdata.com/debian buster InRelease OK:6 http://dl-origin.ubnt.com/unifi/debian stable InRelease Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. nodejs: Installiert: 14.19.3-deb-1nodesource1 Installationskandidat: 14.19.3-deb-1nodesource1 Versionstabelle: *** 14.19.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf PackagesNo connection to databases possible ... npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code ELIFECYCLE npm ERR! errno 22 npm ERR! iobroker.js-controller@4.0.23 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.23 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! /home/iobroker/.npm/_logs/2022-06-04T12_17_51_287Z-debug.log pi@raspberrypi:/opt/iobroker $ pi@raspberrypi:~ $ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs -bash: pi@raspberrypi:~: Kommando nicht gefunden. pi@raspberrypi:/opt/iobroker $ armv7l -bash: armv7l: Kommando nicht gefunden. pi@raspberrypi:/opt/iobroker $ /usr/bin/nodejs Welcome to Node.js v14.19.3. Type ".help" for more information. > /usr/bin/node /usr/bin/node ^ Uncaught SyntaxError: Invalid regular expression flags > /usr/bin/npm /usr/bin/npm ^ Uncaught SyntaxError: Invalid regular expression flags > v14.19.3 v14.19.3 ^^^ Uncaught SyntaxError: Unexpected number > v14.19.3 v14.19.3 ^^^ Uncaught SyntaxError: Unexpected number > 6.14.17 6.14.17 ^^^ Uncaught SyntaxError: Unexpected number > pi Uncaught ReferenceError: pi is not defined > /home/pi /home/pi ^ Uncaught SyntaxError: Invalid regular expression flags > OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:1 http://archive.raspberrypi.org/debian buster InRelease ^^^^ Uncaught SyntaxError: Unexpected identifier > OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease ^^^^ Uncaught SyntaxError: Unexpected identifier > OK:3 https://packages.grafana.com/oss/deb stable InRelease OK:3 https://packages.grafana.com/oss/deb stable InRelease ^^^^^ Uncaught SyntaxError: Unexpected identifier > OK:4 https://deb.nodesource.com/node_14.x buster InRelease OK:4 https://deb.nodesource.com/node_14.x buster InRelease ^^^^^ Uncaught SyntaxError: Unexpected identifier > OK:5 https://repos.influxdata.com/debian buster InRelease OK:5 https://repos.influxdata.com/debian buster InRelease ^^^^^ Uncaught SyntaxError: Unexpected identifier > OK:6 http://dl-origin.ubnt.com/unifi/debian stable InRelease OK:6 http://dl-origin.ubnt.com/unifi/debian stable InRelease ^^^^ Uncaught SyntaxError: Unexpected identifier > Paketlisten werden gelesen... Fertig Paketlisten werden gelesen... Fertig ^^^^^^ Uncaught SyntaxError: Unexpected identifier > Abhängigkeitsbaum wird aufgebaut. Abhängigkeitsbaum wird aufgebaut. ^^^^ Uncaught SyntaxError: Unexpected identifier > Statusinformationen werden eingelesen.... Fertig Statusinformationen werden eingelesen.... Fertig ^^^^^^ Uncaught SyntaxError: Unexpected identifier > Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. Aktualisierung für 1 Paket verfügbar. Führen Sie »apt list --upgradable« aus, um es anzuzeigen. ^^^ Uncaught SyntaxError: Unexpected identifier > nodejs: ... Installiert: 14.19.3-deb-1nodesource1 Installiert: 14.19.3-deb-1nodesource1 ^^ Uncaught SyntaxError: Unexpected number > Installationskandidat: 14.19.3-deb-1nodesource1 Installationskandidat: 14.19.3-deb-1nodesource1 ^^ Uncaught SyntaxError: Unexpected number > Versionstabelle: ... *** 14.19.3-deb-1nodesource1 500 *** 14.19.3-deb-1nodesource1 500 ^^ Uncaught SyntaxError: Unexpected token '**' > 500 https://deb.nodesource.com/node_14.x buster/main armhf Packages 500 https://deb.nodesource.com/node_14.x buster/main armhf Packages ^^^^^ Uncaught SyntaxError: Unexpected identifier > 100 /var/lib/dpkg/status 100 /var/lib/dpkg/status ^^^ Uncaught SyntaxError: Unexpected token 'var' > 10.24.0~dfsg-1~deb10u1 500 10.24.0~dfsg-1~deb10u1 500 ^^ Uncaught SyntaxError: Unexpected number > 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packagesleider erneut kein js.controller
pi@raspberrypi:/opt/iobroker $ ls /opt/iobroker/node_modules/ abort-controller caseless end-of-stream googleapis-common isstream nested-property qs tunnel-agent accepts charenc escape-html google-auth-library is-typedarray netmask querystringify tweetnacl agent-base chownr etag google-p12-pem jsbn node-addon-api random-bytes type-is ajv combined-stream event-target-shim graceful-fs json-bigint node-fetch range-parser @types array-flatten compressible express gtoken jsonfile node-forge raw-body uid-safe arrify compression express-fileupload har-schema json-schema node-gyp-build readable-stream universalify asn1 connect-flash express-session har-validator json-schema-traverse node-mndp request unpipe assert-plus content-disposition extend has json-stringify-safe node-schedule requires-port uri-js async content-type extsprintf has-property-descriptors jsprim node-ssdp safe-buffer url-join asynckit cookie fast-deep-equal has-symbols jwa node-wol safer-buffer url-parse aws4 cookie-parser fast-json-stable-stringify he jws oauth-sign semver url-template aws-sign2 cookie-signature fast-text-encoding hot-patcher layerr object-inspect send util-deprecate axios core-util-is fast-xml-parser http-errors lodash object-keys @serialport utils-merge balanced-match cron-parser finalhandler http-signature long-timeout once serialport uuid base-64 crypt follow-redirects https-proxy-agent lru-cache on-finished serve-static vary base64-js dashdash forever-agent iconv-lite luxon on-headers setprototypeof verror bcrypt-pbkdf debug form-data ieee754 md5 parseurl side-channel webdav bignumber.js define-properties forwarded inherits mdns-discovery passport sorted-array-functions webidl-conversions bl delayed-stream fresh @iobroker media-typer passport-local sshpk whatwg-url bluebird depd fs-constants iobroker.admin merge-descriptors passport-strategy statuses wrappy body-parser destroy fs-extra iobroker.backitup methods path-posix streamsearch ws brace-expansion dgram ftp iobroker.discovery mime path-to-regexp string_decoder xregexp buffer dns-packet function-bind ip mime-db pause strnum yallist buffer-equal-constant-time dropbox-v2-api gaxios ipaddr.js mime-types performance-now tar-fs busboy ecc-jsbn gcp-metadata isarray minimatch proxy-addr tar-stream byte-length ecdsa-sig-formatter get-intrinsic is-buffer mkdirp-classic psl toidentifier bytes ee-first getpass is-nan ms pump tough-cookie call-bind encodeurl @googleapis is-stream negotiator punycode tr46Nach all dem gibt der fixer weiterhin an, dass der iobroker nicht im Verzeichnis istalliert ist und die Fehlermeldung über den fehlenden js-controller bleibt die gleiche. Hat jemand eine Idee?
-
Kann es sein, dass sich der iobroker nicht mit openWB oder dem Unifi Controller verträgt? Egal, was ich tue, der iobroker controller wird nicht mit installiert - es ist zum verzweifeln...
-
@nabonid sagte in fehlender iobroker.js-controller nach Installation:
Open http://192.168.1.242 192.168.193.5:8081 in a browser and start configuring
da stimmt doch was nicht
-
@crunchip @crunchip 192.168.193.5 ist die IP des virtuellen Netzwerkadapaters der openWB
Konfiguration openWB "Hier kann die IP des virtuellen Netzwerkadapters angepasst werden. Wenn hier ungültige Daten eingetragen werden, funktioniert die Verbindung zu einem openWB EVU-/PV-/Speicher-/AlphaESS-Kit nicht mehr! Ein externes Display kann ebenfalls keine Verbindung mehr aufbauen!
Die Standardeinstellung ist 192.168.193.5 und sollte nur in Ausnahmefällen geändert werden!
Die openWB wird direkt nach der Änderung neu gestartet! Alle Fahrzeuge sind vorher abzustecken!
wlan0"pi@raspberrypi:~ $ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether dc:a6:32:4a:43:22 brd ff:ff:ff:ff:ff:ff inet 192.168.1.242/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0 valid_lft 86360sec preferred_lft 75560sec inet 192.168.193.5/24 brd 192.168.193.255 scope global eth0:0 valid_lft forever preferred_lft forever inet6 fe80::46af:80c6:b2b7:c21f/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether dc:a6:32:4a:43:24 brd ff:ff:ff:ff:ff:ff -
@nabonid mit openWB hab ich nichts am Hut, sorry
wie rufst du dann iobroker auf?warum allerdings deine Installation fehlschlägt, bzw wie man das lösen könnte, kann ich dir nicht beantworten
Problem besteht jedenfalls hiermit, IP bzw Port@nabonid sagte in fehlender iobroker.js-controller nach Installation:
Could not connect to objects database at 127.0.0.1:9001 (invalid protocol). Please make sure the configured IP and port points to a host running JS-Controller >= 2.0. and that the port is not occupied by other software!
-
@nabonid auf die schnelle gegoogelt https://openwb.de/forum/viewtopic.php?f=9&t=2232&start=10
-
@crunchip said in fehlender iobroker.js-controller nach Installation:
@nabonid auf die schnelle gegoogelt https://openwb.de/forum/viewtopic.php?f=9&t=2232&start=10
Das hatte ich in der zwischenzeit auch gelsen - scheint ein großes Problem zu werden, immerhin haben sie dort auch keine Lösung gefunden...
egal welchen Befehl ich eingebe:
iobroker iobroker update etc...es kommt immer das gleiche und der Controller ist ja auch tatsächlich nicht im Verzeichnis
-
@nabonid sagte in fehlender iobroker.js-controller nach Installation:
dort auch keine Lösung
Lösung, zweiter Raspberry
@nabonid sagte in fehlender iobroker.js-controller nach Installation:
es kommt immer das gleiche und der Controller ist ja auch tatsächlich nicht im Verzeichnis
weil es nicht installiert wird
