NEWS
[gelöst] Fehler bei IOB Installation unter Trixie
ioBroker Allgemein
5
Beiträge
2
Kommentatoren
119
Aufrufe
2
Watching
-
Hallo, da ich jetzt etwas Zeit habe, soll Trixie installiert werden.
Ich habe einen Raspi 4 ohne Container usw.
Trixie habe ich mit dem Pi Imager auf die SD Karte geschrieben. Ohne Fehler.
Dann mit Putty angemeldet und "sudo apt update && sudo apt full-upgrade" durchgeführt.
Dann wollte ich mit "curl -sLf https://iobroker.net/install.sh | bash -" den IOB installieren.
Da kommt dann der Fehler, dass Node.js nicht installiert werden kann.
Den Text/Screen habe ich leider nicht mehr.
Mache ich etwas falsch oder ist das Verhalten normal?
Gibt es eine empfohlene Anleitung für eine Neuinstallation von Trixie? -
Hallo, da ich jetzt etwas Zeit habe, soll Trixie installiert werden.
Ich habe einen Raspi 4 ohne Container usw.
Trixie habe ich mit dem Pi Imager auf die SD Karte geschrieben. Ohne Fehler.
Dann mit Putty angemeldet und "sudo apt update && sudo apt full-upgrade" durchgeführt.
Dann wollte ich mit "curl -sLf https://iobroker.net/install.sh | bash -" den IOB installieren.
Da kommt dann der Fehler, dass Node.js nicht installiert werden kann.
Den Text/Screen habe ich leider nicht mehr.
Mache ich etwas falsch oder ist das Verhalten normal?
Gibt es eine empfohlene Anleitung für eine Neuinstallation von Trixie?@Gonzokalle sagte in Fehler bei IOB Installation unter Trixie:
Gibt es eine empfohlene Anleitung für eine Neuinstallation von Trixie?
Nein, genauso.
Da kommt dann der Fehler, dass Node.js nicht installiert werden kann.
Den Text/Screen habe ich leider nicht mehr.Das ist schlecht. So kann man da halt auch nix sehen.
Edit:
Geht immer noch grundsätzlich so:https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht
Ich setz mich die Tage mal dran und akttualisiere die Screenshots auf den aktuellen Imager 2.0
-
Gleich nochmal probiert.
Diesmal ist es ohne Node.js Fehler durchgelaufen. Warum auch immer.....
Die letzten beiden Zeilen sind ja bestimmt so gewollt.
Also neu einloggen mit Putty und den "iob fix" durchlaufen lassen.login as: martin martin@192.168.10.9's password: Linux RaspberryPi-Test 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Dec 23 13:27:07 2025 from 192.168.10.11 martin@RaspberryPi-Test:~ $ curl -sLf https://iobroker.net/install.sh | bash - martin@RaspberryPi-Test:~ $ curl -sLf https://iobroker.net/install.sh | bash - Your system is booting into 'graphical.target', which means that a user interface or desktop is available. Usually a server is running without a desktop for security reasons and to save RAM. Please run 'iob fix' after the installation to change this. library: loaded Library version=2025-08-09 ========================================================================== Welcome to the ioBroker installer! Installer version: 2025-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 http://archive.raspberrypi.com/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://deb.debian.org/debian-security trixie-security InRelease Reading package lists... Done ========================================================================== Node.js not found. Installing... ========================================================================== rm: cannot remove '/etc/apt/keyrings/nodesource.gpg': No such file or directory deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 1001 W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...ource1_arm64.deb ...lled.) Installed nodejs Node.js Installed successfully! Changing npm registry to https://registry.npmjs.org W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libavahi-compat-libdnssd-dev:arm64 (0.8-16) ...-16_arm64.deb ... Installed libavahi-compat-libdnssd-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...) ...1_arm64.deb ...lled.) Installed libudev-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libpam0g-dev:arm64 (1.7.0-5) ...5_arm64.deb ...y installed.) Installed libpam0g-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...4.deb ...ently installed.) Installed distro-info W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libcairo2-dev:arm64 (1.18.4-1+rpt1) ... ...3~deb13u1) .............. Installed libcairo2-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ......) ...eb ..........b ... Installed libpango1.0-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libjpeg-dev:arm64 (1:2.1.5-4) ...5-4) ...4.deb ....deb ....) Installed libjpeg-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libgif-dev:arm64 (5.2.2-1+b1) ...1_arm64.deb ... installed.) Installed libgif-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ...g-4) ...deb13u2) ...13u2_arm64.deb ... Installed librsvg2-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ........... installed.) Installed cmake ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== User iobroker created Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Created symlink '/etc/systemd/system/multi-user.target.wants/iobroker.service' → '/usr/lib/systemd/system/iobroker.service'. Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.10.9:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! ========================================================================== Please run 'iob fix' after the required re-login to fix some common issues. -
Gleich nochmal probiert.
Diesmal ist es ohne Node.js Fehler durchgelaufen. Warum auch immer.....
Die letzten beiden Zeilen sind ja bestimmt so gewollt.
Also neu einloggen mit Putty und den "iob fix" durchlaufen lassen.login as: martin martin@192.168.10.9's password: Linux RaspberryPi-Test 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.47-1+rpt1 (2025-09-16) aarch64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Tue Dec 23 13:27:07 2025 from 192.168.10.11 martin@RaspberryPi-Test:~ $ curl -sLf https://iobroker.net/install.sh | bash - martin@RaspberryPi-Test:~ $ curl -sLf https://iobroker.net/install.sh | bash - Your system is booting into 'graphical.target', which means that a user interface or desktop is available. Usually a server is running without a desktop for security reasons and to save RAM. Please run 'iob fix' after the installation to change this. library: loaded Library version=2025-08-09 ========================================================================== Welcome to the ioBroker installer! Installer version: 2025-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/4) ========================================================================== Hit:1 http://archive.raspberrypi.com/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://deb.debian.org/debian-security trixie-security InRelease Reading package lists... Done ========================================================================== Node.js not found. Installing... ========================================================================== rm: cannot remove '/etc/apt/keyrings/nodesource.gpg': No such file or directory deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_22.x nodistro main Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 1001 W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...ource1_arm64.deb ...lled.) Installed nodejs Node.js Installed successfully! Changing npm registry to https://registry.npmjs.org W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libavahi-compat-libdnssd-dev:arm64 (0.8-16) ...-16_arm64.deb ... Installed libavahi-compat-libdnssd-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...) ...1_arm64.deb ...lled.) Installed libudev-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libpam0g-dev:arm64 (1.7.0-5) ...5_arm64.deb ...y installed.) Installed libpam0g-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for man-db (2.13.1-1) ...4.deb ...ently installed.) Installed distro-info W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libcairo2-dev:arm64 (1.18.4-1+rpt1) ... ...3~deb13u1) .............. Installed libcairo2-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ......) ...eb ..........b ... Installed libpango1.0-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libjpeg-dev:arm64 (1:2.1.5-4) ...5-4) ...4.deb ....deb ....) Installed libjpeg-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Setting up libgif-dev:arm64 (5.2.2-1+b1) ...1_arm64.deb ... installed.) Installed libgif-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ...g-4) ...deb13u2) ...13u2_arm64.deb ... Installed librsvg2-dev W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Processing triggers for libc-bin (2.41-12+rpt1) ........... installed.) Installed cmake ========================================================================== Creating ioBroker user and directory (2/4) ========================================================================== User iobroker created Created /etc/sudoers.d/iobroker Directory /opt/iobroker created ========================================================================== Installing ioBroker (3/4) ========================================================================== ========================================================================== Finalizing installation (4/4) ========================================================================== Enabling autostart... Created symlink '/etc/systemd/system/multi-user.target.wants/iobroker.service' → '/usr/lib/systemd/system/iobroker.service'. Autostart enabled! Fixing directory permissions... ========================================================================== ioBroker was installed successfully Open http://192.168.10.9:8081 in a browser and start configuring! ========================================================================== You need to re-login before doing anything else on the console! ========================================================================== Please run 'iob fix' after the required re-login to fix some common issues.@Gonzokalle sagte in Fehler bei IOB Installation unter Trixie:
Die letzten beiden Zeilen sind ja bestimmt so gewollt.
Ja, die gehören zwingend zum Installationsprozess.
-
Vielen Dank für deine Hilfe
265
Online32.7k
Benutzer82.3k
Themen1.3m
Beiträge