Problem Installation auf Raspi4
-
@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) -
@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. -
@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...
-
@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? -
die Idee nach der Portbelegung zu schauen, war nicht schlecht:
Port 9001 Ausgabe von netstat:
$ sudo netstat -tulpn |grep 9001 [sudo] Passwort für ****: tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 426/node code_textpid 426 betrifft noch einen openhab Prozeß "frontail", eigentlich ist openhab deinstalliert:
426 frontail vor 2 Tagen node /usr/lib/node_modules/frontail/bin/frontail --disable-usage-stats --ui-high ... 1180 frontail vor 2 Tagen tail -n 200 -F /var/log/openhab/openhab.log /var/log/openhab/events.logwerde demnächst weiter suchen, erstmal danke
-
Abschalten von frontail und anschließender Aufruf des Installscriptes ergab dann folgendes:
[20:44:16] root@openhabraspi4:/opt/iobroker# systemctl status iobroker ● iobroker.service - ioBroker Server Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: Active: active (running) since Wed 2022-02-16 20:43:22 CET; 2min 11s ago Docs: http://iobroker.net Main PID: 14896 (iobroker.js-con) Tasks: 11 (limit: 4915) CGroup: /system.slice/iobroker.service └─14896 iobroker.js-controller Feb 16 20:43:22 openhabraspi4 systemd[1]: Started ioBroker Server. lines 1-10/10 (END) code_textich kann aber über den Port 8081 dann die web-Oberfläche nicht aufrufen, egal ob über die IP Adresse oder localhost:8081 -> Verbindung abgelehnt.
die Kontrolle mit netstat zeigt keinen offenen Port unter 8081 an,
9001 erscheint.code[20:30:58] root@openhabraspi4:/home/moelli# netstat -tulpn | grep 8081 _text [20:46:08] root@openhabraspi4:/opt/iobroker# netstat -tulpn | grep 9001 tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 14896/iobroker.js-cetwas ratlos
-
-
als USER:
iob list instances -
ich habe alle Varianten durchgespielt: root, pi, sonst. user
bei user kommt ungültige Gruppe user****:user**** -
@goofy1800
Du sollst halt nicht als root da rumhampeln.
Das ist jetzt Rat genug an der Stelle. -
pi@openhabraspi4:/opt/iobroker $ 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://archive.raspberrypi.org/debian buster InRelease OK:2 http://deb.debian.org/debian buster-backports InRelease OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease OK:4 https://packages.grafana.com/oss/deb stable InRelease Ign:5 http://repos.azulsystems.com/debian stable InRelease OK:6 http://repos.azulsystems.com/debian stable Release OK:7 https://repos.influxdata.com/debian buster InRelease Holen:8 https://repo.z-wave.me/z-way/raspbian buster InRelease [1.806 B] OK:9 https://deb.nodesource.com/node_16.x buster InRelease OK:10 https://repo.mosquitto.org/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) ========================================================================== ========================================================================== 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! pi@openhabraspi4:/opt/iobroker $ ode_textich finde Ihren Ton (rumhampeln) nicht gerade angemessen, man wweiß ja nicht wen man auf der Gegenseite vor sich hat - ....
-
@goofy1800 sagte in Problem Installation auf Raspi4:
man wweiß ja nicht wen man auf der Gegenseite vor sich hat - ....
Einen Goofy. Sehe ich.
-
@goofy1800 sagte in Problem Installation auf Raspi4:
man wweiß ja nicht wen man auf der Gegenseite vor sich hat
Leute die versuchen einem zu helfen.
Laut fixer sollte IOB laufen.
Wie die IP Addressen zustande kommen erschliesst sich mir aktuell nicht da ich die Konfig vom PI nicht kenne, daher kann ich nicht sagen welche jetzt zu verwenden wäre.
-
@goofy1800 sagte in Problem Installation auf Raspi4:
ich finde Ihren Ton (rumhampeln) nicht gerade angemessen
Ein lockerer Ton darf doch erlaubt sein. Bei dir motzt der compiler ja auc
@Ein ehemaliger Benutzer sagte in Problem Installation auf Raspi4:
man wweiß ja nicht wen man auf der Gegenseite vor sich hat -
da ist jemand , dem man in entspannter Atmosphäre helfen will.
-
Oha....
da hat sich aber schnell wieder jemand von ioBroker verabschiedet.
