NEWS
Problem Installation auf Raspi4
-
Guten Abend,
bin neu hier. Bisschen linux Erfahrung (komme eigentlich von open-suse und vm-ware), habe eine Heizungssteuerung mit z-wave.me auf einem raspi laufen und will iobroker drüberlegen.
Bei der Installation unter root-rechten mit script gemäß "Einfacher gehts nicht" gibt es folgende Fehlermeldung im Log:
MOD-Edit: Code in code-tags gesetzt!Im syslog taucht folgendes auf:
MOD-Edit: Code in code-tags gesetzt!npm -v = 6.14.16
node -v = 14.19.0
nodejs -v = 14.19.0Der Versuch mit npm i iobroker.js-controller --production scheitert ebenfalls:
Sorry wenn ich das ganze log als Datei log_npm_js-controller.txt drangehängt habe, aber auffällig darin mehrfache Warnungen "deprecated" zB Zeile 109,
oder Zeile 402 :"warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details."?? Mir sagt v8.dev nichts...
Was bedeuteted das?
für jede Hilfe dankbar.
manfred -
Guten Abend,
bin neu hier. Bisschen linux Erfahrung (komme eigentlich von open-suse und vm-ware), habe eine Heizungssteuerung mit z-wave.me auf einem raspi laufen und will iobroker drüberlegen.
Bei der Installation unter root-rechten mit script gemäß "Einfacher gehts nicht" gibt es folgende Fehlermeldung im Log:
MOD-Edit: Code in code-tags gesetzt!Im syslog taucht folgendes auf:
MOD-Edit: Code in code-tags gesetzt!npm -v = 6.14.16
node -v = 14.19.0
nodejs -v = 14.19.0Der Versuch mit npm i iobroker.js-controller --production scheitert ebenfalls:
Sorry wenn ich das ganze log als Datei log_npm_js-controller.txt drangehängt habe, aber auffällig darin mehrfache Warnungen "deprecated" zB Zeile 109,
oder Zeile 402 :"warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details."?? Mir sagt v8.dev nichts...
Was bedeuteted das?
für jede Hilfe dankbar.
manfred@goofy1800 sagte in Problem Installation auf Raspi4:
Bei der Installation unter root-rechten
Wird nicht unter root installiert. Wie auf einem Raspberry üblich wird das Skript als User mit sudo-Befähigung aufgerufen.
In /home/moelli/ darf da eigentlich auch nichts passieren.
-
Guten Abend,
bin neu hier. Bisschen linux Erfahrung (komme eigentlich von open-suse und vm-ware), habe eine Heizungssteuerung mit z-wave.me auf einem raspi laufen und will iobroker drüberlegen.
Bei der Installation unter root-rechten mit script gemäß "Einfacher gehts nicht" gibt es folgende Fehlermeldung im Log:
MOD-Edit: Code in code-tags gesetzt!Im syslog taucht folgendes auf:
MOD-Edit: Code in code-tags gesetzt!npm -v = 6.14.16
node -v = 14.19.0
nodejs -v = 14.19.0Der Versuch mit npm i iobroker.js-controller --production scheitert ebenfalls:
Sorry wenn ich das ganze log als Datei log_npm_js-controller.txt drangehängt habe, aber auffällig darin mehrfache Warnungen "deprecated" zB Zeile 109,
oder Zeile 402 :"warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details."?? Mir sagt v8.dev nichts...
Was bedeuteted das?
für jede Hilfe dankbar.
manfred@goofy1800 meinst du diese Anleitung
Bitte keine Fragen per PN, die gehören ins Forum!
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
-
@goofy1800 meinst du diese Anleitung
Ich hoffe doch nicht. Da steht nämlich von root-Rechten nix drin. Weiß ich zufällig ganz genau.
-
Guten Abend,
bin neu hier. Bisschen linux Erfahrung (komme eigentlich von open-suse und vm-ware), habe eine Heizungssteuerung mit z-wave.me auf einem raspi laufen und will iobroker drüberlegen.
Bei der Installation unter root-rechten mit script gemäß "Einfacher gehts nicht" gibt es folgende Fehlermeldung im Log:
MOD-Edit: Code in code-tags gesetzt!Im syslog taucht folgendes auf:
MOD-Edit: Code in code-tags gesetzt!npm -v = 6.14.16
node -v = 14.19.0
nodejs -v = 14.19.0Der Versuch mit npm i iobroker.js-controller --production scheitert ebenfalls:
Sorry wenn ich das ganze log als Datei log_npm_js-controller.txt drangehängt habe, aber auffällig darin mehrfache Warnungen "deprecated" zB Zeile 109,
oder Zeile 402 :"warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details."?? Mir sagt v8.dev nichts...
Was bedeuteted das?
für jede Hilfe dankbar.
manfred@goofy1800
danke für die rasche Antwort:
habe selbst gesehen, daß ich zunächst aus Versehen in eimem user-verzeichnis gearbeitet habe.
Beim Aufruf von npm im iobroker Verzeichnis kam uA. folgende Bildschirmausgabe (nur als screen-shot):
das entscheidende Kriterium dürfte wohl sein "cast between incompatible function types from"Dürfte von meinem Verständnis nicht am user root liegen ?
-
Ich hoffe doch nicht. Da steht nämlich von root-Rechten nix drin. Weiß ich zufällig ganz genau.
@thomas-braun deshalb meine Frage
-
@goofy1800
danke für die rasche Antwort:
habe selbst gesehen, daß ich zunächst aus Versehen in eimem user-verzeichnis gearbeitet habe.
Beim Aufruf von npm im iobroker Verzeichnis kam uA. folgende Bildschirmausgabe (nur als screen-shot):
das entscheidende Kriterium dürfte wohl sein "cast between incompatible function types from"Dürfte von meinem Verständnis nicht am user root liegen ?
@goofy1800 sagte in Problem Installation auf Raspi4:
@goofy1800
danke für die rasche Antwort:
habe selbst gesehen, daß ich zunächst aus Versehen in eimem user-verzeichnis gearbeitet habe.
Beim Aufruf von npm im iobroker Verzeichnis kam uA. folgende Bildschirmausgabe (nur als screen-shot):
das entscheidende Kriterium dürfte wohl sein "cast between incompatible function types from"Dürfte von meinem Verständnis nicht am user root liegen ?
Bitte die logs als Text in Code Tags posten. So ist das nicht zu bearbeiten
-
@goofy1800
danke für die rasche Antwort:
habe selbst gesehen, daß ich zunächst aus Versehen in eimem user-verzeichnis gearbeitet habe.
Beim Aufruf von npm im iobroker Verzeichnis kam uA. folgende Bildschirmausgabe (nur als screen-shot):
das entscheidende Kriterium dürfte wohl sein "cast between incompatible function types from"Dürfte von meinem Verständnis nicht am user root liegen ?
@goofy1800
Bitte keine Screenshots von Texten. Kann ich nicht lesen. -
@goofy1800
danke für die rasche Antwort:
habe selbst gesehen, daß ich zunächst aus Versehen in eimem user-verzeichnis gearbeitet habe.
Beim Aufruf von npm im iobroker Verzeichnis kam uA. folgende Bildschirmausgabe (nur als screen-shot):
das entscheidende Kriterium dürfte wohl sein "cast between incompatible function types from"Dürfte von meinem Verständnis nicht am user root liegen ?
@goofy1800 sagte in Problem Installation auf Raspi4:
Dürfte von meinem Verständnis nicht am user root liegen ?
Nein, es liegt nicht am root, weil man sich nie als root einloggt. Deswegen kann das nicht am root liegen. Tust du es doch: Es liegt am root.
-
Bin nocham Probieren mit diesem Forum, daher der screenshot.
Anbei die Textausgabe
MOD-Edit: Code in code-tags gesetzt!Ich lasse mich gern belehren - auch wenn es mir unverständlich erscheint - daß ein funktionstypen missmatch in einer headerdatei
>>>> In file included from ../../nan/nan.h:58, from ../src/unix_dgram.cc:5: /home/iobroker/.cache/node-gyp/14.19.0/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), ..... <<<<<<< \durch den Aufruf des make Lauf als root entsteht?
MOD EDIT: LOG in Code Tags gesetzt
-
Bin nocham Probieren mit diesem Forum, daher der screenshot.
Anbei die Textausgabe
MOD-Edit: Code in code-tags gesetzt!Ich lasse mich gern belehren - auch wenn es mir unverständlich erscheint - daß ein funktionstypen missmatch in einer headerdatei
>>>> In file included from ../../nan/nan.h:58, from ../src/unix_dgram.cc:5: /home/iobroker/.cache/node-gyp/14.19.0/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), ..... <<<<<<< \durch den Aufruf des make Lauf als root entsteht?
MOD EDIT: LOG in Code Tags gesetzt
@goofy1800
Die Meldungen vom kompilieren sind harmlos. Aber du eierst da immer noch als root rum.Und bitte CodeTags verwenden. Spoiler sind nicht so wichtig.
-
@Thomas-Braun
habe das ganze eben nochmals als normaler user mit sudo gemacht: -> ditto gleiche Fehlermeldung -
@Thomas-Braun
habe das ganze eben nochmals als normaler user mit sudo gemacht: -> ditto gleiche Fehlermeldung@goofy1800
Du hast dir ja jetzt auch den cacache mit falschen Rechten zugeballert. -
@Thomas-Braun
habe das ganze eben nochmals als normaler user mit sudo gemacht: -> ditto gleiche Fehlermeldung -
@Thomas-Braun
habe das ganze eben nochmals als normaler user mit sudo gemacht: -> ditto gleiche Fehlermeldung@goofy1800 sagte in Problem Installation auf Raspi4:
normaler user mit sudo gemacht
Aufruf des Installations-Skripts mit
sudo curl blablubboder was hast du jetzt gemacht?
-
@Thomas-Braun
Ich finde diese Antworten "jetzt hast du dir auch noch den cache zugeballert" gegenüber einem Forumsneuling vorsichtig ausgedrückt nicht gerade zielführend...
wie der Aufruf mit sudo geht hat sich auch zu mir rumgesprochen....@wendy2702
bestehende seit ca. einem Jahr laufende Linuxinstallation mit uA. einer z-wave.me Installation u. einem vpn-server.
Vor iobroker hatte ich versuchsweise "openhab" installiert, aber wieder entfernt.```
code_text[23:19:06] root@openhabraspi4:/home/moelli# sudo 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 ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== OK:1 https://repo.mosquitto.org/debian buster InRelease Holen:2 https://repo.z-wave.me/z-way/raspbian buster InRelease [1.806 B] OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:4 http://archive.raspberrypi.org/debian buster InRelease Ign:5 http://repos.azulsystems.com/debian stable InRelease OK:6 http://repos.azulsystems.com/debian stable Release OK:7 https://packages.grafana.com/oss/deb stable InRelease OK:8 http://deb.debian.org/debian buster-backports InRelease OK:9 https://deb.nodesource.com/node_14.x buster InRelease OK:10 https://repos.influxdata.com/debian buster InRelease OK:11 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease Es wurden 1.806 B in 5 s geholt (390 B/s). 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:58, from ../src/main.cpp:3: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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:58, from ../src/unix_dgram.cc:5: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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 22 npm ERR! iobroker.js-controller@3.3.22 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@3.3.22 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! /root/.npm/_logs/2022-02-15T22_20_44_642Z-debug.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.11.117 192.168.11.217 192.168.55.1 10.6.0.1:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! [23:20:46] root@openhabraspi4:/home/moelli# sudo systemctl status iobroker ● iobroker.service - ioBroker Server Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: Active: activating (auto-restart) (Result: exit-code) since Tue 2022-02-15 23 Docs: http://iobroker.net Process: 22589 ExecStart=/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobro Main PID: 22589 (code=exited, status=1/FAILURE) -
@Thomas-Braun
Ich finde diese Antworten "jetzt hast du dir auch noch den cache zugeballert" gegenüber einem Forumsneuling vorsichtig ausgedrückt nicht gerade zielführend...
wie der Aufruf mit sudo geht hat sich auch zu mir rumgesprochen....@wendy2702
bestehende seit ca. einem Jahr laufende Linuxinstallation mit uA. einer z-wave.me Installation u. einem vpn-server.
Vor iobroker hatte ich versuchsweise "openhab" installiert, aber wieder entfernt.```
code_text[23:19:06] root@openhabraspi4:/home/moelli# sudo 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 ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== OK:1 https://repo.mosquitto.org/debian buster InRelease Holen:2 https://repo.z-wave.me/z-way/raspbian buster InRelease [1.806 B] OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:4 http://archive.raspberrypi.org/debian buster InRelease Ign:5 http://repos.azulsystems.com/debian stable InRelease OK:6 http://repos.azulsystems.com/debian stable Release OK:7 https://packages.grafana.com/oss/deb stable InRelease OK:8 http://deb.debian.org/debian buster-backports InRelease OK:9 https://deb.nodesource.com/node_14.x buster InRelease OK:10 https://repos.influxdata.com/debian buster InRelease OK:11 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease Es wurden 1.806 B in 5 s geholt (390 B/s). 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:58, from ../src/main.cpp:3: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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:58, from ../src/unix_dgram.cc:5: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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 22 npm ERR! iobroker.js-controller@3.3.22 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@3.3.22 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! /root/.npm/_logs/2022-02-15T22_20_44_642Z-debug.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.11.117 192.168.11.217 192.168.55.1 10.6.0.1:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! [23:20:46] root@openhabraspi4:/home/moelli# sudo systemctl status iobroker ● iobroker.service - ioBroker Server Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: Active: activating (auto-restart) (Result: exit-code) since Tue 2022-02-15 23 Docs: http://iobroker.net Process: 22589 ExecStart=/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobro Main PID: 22589 (code=exited, status=1/FAILURE)@goofy1800
Jetzt mal ernsthaft:
Wo steht, dass der root (auch noch mit 'sudo' kombiniert...) das Installationsskript aufruft?
In der verlinkten Anleitung steht, dass der User pi ein einfachescurl -sLf https://iobroker.net/install.sh | bash -absetzt. Nicht mehr, nicht weniger.
Alternativ halt auch mit einem anderen Standarduser (der sudo-Rechte erlangen kann) auszuführen. Dann funktioniert das auch. Ich weiß das, ich hab das schon so gemacht. -
@Thomas-Braun
Ich finde diese Antworten "jetzt hast du dir auch noch den cache zugeballert" gegenüber einem Forumsneuling vorsichtig ausgedrückt nicht gerade zielführend...
wie der Aufruf mit sudo geht hat sich auch zu mir rumgesprochen....@wendy2702
bestehende seit ca. einem Jahr laufende Linuxinstallation mit uA. einer z-wave.me Installation u. einem vpn-server.
Vor iobroker hatte ich versuchsweise "openhab" installiert, aber wieder entfernt.```
code_text[23:19:06] root@openhabraspi4:/home/moelli# sudo 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 ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== OK:1 https://repo.mosquitto.org/debian buster InRelease Holen:2 https://repo.z-wave.me/z-way/raspbian buster InRelease [1.806 B] OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:4 http://archive.raspberrypi.org/debian buster InRelease Ign:5 http://repos.azulsystems.com/debian stable InRelease OK:6 http://repos.azulsystems.com/debian stable Release OK:7 https://packages.grafana.com/oss/deb stable InRelease OK:8 http://deb.debian.org/debian buster-backports InRelease OK:9 https://deb.nodesource.com/node_14.x buster InRelease OK:10 https://repos.influxdata.com/debian buster InRelease OK:11 https://openhab.jfrog.io/artifactory/openhab-linuxpkg stable InRelease Es wurden 1.806 B in 5 s geholt (390 B/s). 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:58, from ../src/main.cpp:3: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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:58, from ../src/unix_dgram.cc:5: /root/.cache/node-gyp/14.19.0/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), \ ^ /root/.cache/node-gyp/14.19.0/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 22 npm ERR! iobroker.js-controller@3.3.22 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@3.3.22 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! /root/.npm/_logs/2022-02-15T22_20_44_642Z-debug.log ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.11.117 192.168.11.217 192.168.55.1 10.6.0.1:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! [23:20:46] root@openhabraspi4:/home/moelli# sudo systemctl status iobroker ● iobroker.service - ioBroker Server Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: Active: activating (auto-restart) (Result: exit-code) since Tue 2022-02-15 23 Docs: http://iobroker.net Process: 22589 ExecStart=/bin/bash -c ${NODE} /opt/iobroker/node_modules/iobro Main PID: 22589 (code=exited, status=1/FAILURE)@goofy1800
Wieso hast du so viele Netzwerk Interfaces? Keine Ahnung ob das von der Fehlerhaften installation kommt oder deine Konfiguration das hergibt.
Was du mal versuchen kannst um noch bisschen was zu retten:
cd /opt/iobroker/ npm install iobroker.js-controller@3.3.22Wenn fertig mal
iob fix iob start -
@Thomas-Braun
völlig egal mit welchem user (pi/moelli/root): es bleibt bei der Fehlermeldung der typmissmatch in der headerdatei.erstmal dankefür Deine Hilfe: netzwerkinterfaces für vpn
$ cd /opt/iobroker $ npm install iobroker.js-controller@3.3.22 > iobroker.js-controller@3.3.22 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > 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:58, from ../src/unix_dgram.cc:5: /home/moelli/.cache/node-gyp/14.19.0/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/moelli/.cache/node-gyp/14.19.0/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:58, from ../src/main.cpp:3: /home/moelli/.cache/node-gyp/14.19.0/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/moelli/.cache/node-gyp/14.19.0/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@3.3.22 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! Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup! Server Cannot load /opt/iobroker/iobroker-data/objects.json.bak: Database file /opt/iobroker/iobroker-data/objects.json.bak does not exists.. Continue with empty dataset! Server If this is no Migration or initial start please restore the last backup from /opt/iobroker/iobroker-data/backup-objects No 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@3.3.22 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@3.3.22 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/moelli/.npm/_logs/2022-02-15T22_56_22_260Z-debug.logcode_textder compiler motzt weiter über nan.h und node.h und erzeugt nicht js-controller. Insofern startet IOB auch nicht und es gibt keine Verbindung zu Port 9001.
Für mich sieht das nach einer Incompatibiltät zw java und dden benutzten C-Biblotheken aus.Erst mal danke und gute nacht - gibt sonst auch noch Dinge die man um die Uhrzeit macht...
-
@Thomas-Braun
völlig egal mit welchem user (pi/moelli/root): es bleibt bei der Fehlermeldung der typmissmatch in der headerdatei.erstmal dankefür Deine Hilfe: netzwerkinterfaces für vpn
$ cd /opt/iobroker $ npm install iobroker.js-controller@3.3.22 > iobroker.js-controller@3.3.22 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > 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:58, from ../src/unix_dgram.cc:5: /home/moelli/.cache/node-gyp/14.19.0/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/moelli/.cache/node-gyp/14.19.0/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:58, from ../src/main.cpp:3: /home/moelli/.cache/node-gyp/14.19.0/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/moelli/.cache/node-gyp/14.19.0/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@3.3.22 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! Server Cannot load /opt/iobroker/iobroker-data/objects.json: Database file /opt/iobroker/iobroker-data/objects.json does not exists.. We try last Backup! Server Cannot load /opt/iobroker/iobroker-data/objects.json.bak: Database file /opt/iobroker/iobroker-data/objects.json.bak does not exists.. Continue with empty dataset! Server If this is no Migration or initial start please restore the last backup from /opt/iobroker/iobroker-data/backup-objects No 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@3.3.22 install: `node iobroker.js setup first` npm ERR! Exit status 22 npm ERR! npm ERR! Failed at the iobroker.js-controller@3.3.22 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/moelli/.npm/_logs/2022-02-15T22_56_22_260Z-debug.logcode_textder compiler motzt weiter über nan.h und node.h und erzeugt nicht js-controller. Insofern startet IOB auch nicht und es gibt keine Verbindung zu Port 9001.
Für mich sieht das nach einer Incompatibiltät zw java und dden benutzten C-Biblotheken aus.Erst mal danke und gute nacht - gibt sonst auch noch Dinge die man um die Uhrzeit macht...
@goofy1800 sagte in Problem Installation auf Raspi4:
der compiler motzt weiter über nan.h und node.h
Lass ihn motzen. Das ist vollkommen normal.
Nicht normal ist das Nichterreichen der Datenbank.
Läuft da schon was anderes auf dem Port?
Support us
716
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge