NEWS
Kann IoBroker nicht mehr aufrufen
ioBroker Allgemein
36
Beiträge
4
Kommentatoren
3.4k
Aufrufe
4
Watching
-
Guten Morgen zusammen,
ich habe eben den Admin Adapter auf die Version 7.1.2 geupdatet.
Danach war der Iobroker irgendwie nicht mehrerreichbar und nach einem Neustart kann ich die Admin Oberfläche nicht mehr im Firefox aufrufen.Es scheint aber so als würde der Iobroker laufen... da meine Lichter zum Beispiel gesteuert werden.
Könnt ihr mir irgendwie helfen?
-
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
nur was soll ich jetzt tun?
erst mal die Langfassung von
iob diagposten.
Da sehen wir dann mehr -
Okay... hier also im Anhang
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 246 Pending iob updates: 0 Nodejs-Installation: nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 Recommended versions are nodejs and npm *** nodejs is NOT correctly installed *** Wrong installation path detected. This needs to be fixed. Please execute iobroker nodejs-update to fix these errors. MEMORY: total used free shared buff/cache available Mem: 3.8G 1.5G 1.5G 35M 770M 2.2G Swap: 99M 0B 99M Total: 3.9G 1.5G 1.6G Active iob-Instances: 20 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.2 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6973 States: 5279 Size of iob-Database: 22M /opt/iobroker/iobroker-data/objects.jsonl 5.5M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ==================== -
Okay... hier also im Anhang
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 246 Pending iob updates: 0 Nodejs-Installation: nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 Recommended versions are nodejs and npm *** nodejs is NOT correctly installed *** Wrong installation path detected. This needs to be fixed. Please execute iobroker nodejs-update to fix these errors. MEMORY: total used free shared buff/cache available Mem: 3.8G 1.5G 1.5G 35M 770M 2.2G Swap: 99M 0B 99M Total: 3.9G 1.5G 1.6G Active iob-Instances: 20 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.2 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6973 States: 5279 Size of iob-Database: 22M /opt/iobroker/iobroker-data/objects.jsonl 5.5M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================iob nodejs-update 20 iob start adminDisplay-Server: true
Und schalt den graphischen Mumpitz auf einem Server AUS!
Und das Betriebssystem möchte auch regelmäßig aktualisiert werden!sudo systemctl set-default multi-user.target sudo apt update sudo apt full-upgrade sudo reboot -
iob nodejs-update 20 iob start adminDisplay-Server: true
Und schalt den graphischen Mumpitz auf einem Server AUS!
Und das Betriebssystem möchte auch regelmäßig aktualisiert werden!sudo systemctl set-default multi-user.target sudo apt update sudo apt full-upgrade sudo reboot@thomas-braun
also bisher hängt er wohl noch an diesem nodejs updateUpdating fallback to latest nodejs v20 release
-
@thomas-braun
also bisher hängt er wohl noch an diesem nodejs updateUpdating fallback to latest nodejs v20 release
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
hängt er wohl noch an diesem nodejs update
können wir nicht sehen!
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
SUMMARY
ist nicht die Langfassung!
die kommt vorher@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
Pending OS-Updates: 246
aber das ist schon heftig!
Seit der Installation keine Betriebssystem Updates gefahren? -
@thomas-braun
also bisher hängt er wohl noch an diesem nodejs updateUpdating fallback to latest nodejs v20 release
Könnte daran liegen, daß nicht die aktuelle Version verfügbar ist.
Versuch mal die Beta-Version von hier:https://forum.iobroker.net/topic/68035/iob-node-fix-skript
@apollon77 Bitte hochladen!!!
-
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
hängt er wohl noch an diesem nodejs update
können wir nicht sehen!
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
SUMMARY
ist nicht die Langfassung!
die kommt vorher@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
Pending OS-Updates: 246
aber das ist schon heftig!
Seit der Installation keine Betriebssystem Updates gefahren?@homoran
hmm ich fürchte ehrlich gesagt nicht.
Bin da nicht son fit und bin froh wenn alles läuft ;-)Ich mache in regelmäßigen abständen diesen Update Durchlauf mit
iob stop
iob update
iob upgrade self
iob fixdas war es dann aber auch schon mehr oder weniger.
Das Update er Node läuft Imme rnoch... er ist kräftig am installieren und am installieren...
-
schaut mal was hier nun so abläuft:
ioBroker nodejs fixer 2024-05-23 You requested to install latest version from nodejs v20 tree. Your current setup is: /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 We found these nodejs versions available for installation: nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u5 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Nothing to do - Your installation is using the correct paths. You are running nodejs v18.17.1. Do you want to install latest version from nodejs v.20 tree? Press <y> to continue or any other key to quit Trying to fix your installation now. Please be patient. [sudo] password for iobroker: find: '/run/user/1000/gvfs': Permission denied Waiting for ioBroker to shut down - Give me a minute... ############################################################ *** These repos are active on your system: Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Reading package lists... Done *** Installing ca-certificates, curl and gnupg, just in case they are missing. (Reading database ... 107742 files and directories currently installed.) Preparing to unpack .../curl_7.74.0-1.3+deb11u13_arm64.deb ... Unpacking curl (7.74.0-1.3+deb11u13) over (7.74.0-1.3+deb11u7) ... Preparing to unpack .../libcurl4_7.74.0-1.3+deb11u13_arm64.deb ... Unpacking libcurl4:arm64 (7.74.0-1.3+deb11u13) over (7.74.0-1.3+deb11u7) ... Setting up libcurl4:arm64 (7.74.0-1.3+deb11u13) ... Setting up curl (7.74.0-1.3+deb11u13) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ... *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x nodistro main Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 1001 *** These repos are active after the adjustments: Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Get:5 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB] Get:6 https://deb.nodesource.com/node_20.x nodistro/main armhf Packages [9132 B] Get:7 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages [9124 B] Fetched 30.4 kB in 2s (19.7 kB/s) Reading package lists... Done Installing nodejs now! /home/iobroker/.nodejs-update.sh: line 370: [: : integer expression expected Exact recommended version unknown, installing a fallback! (Reading database ... 107742 files and directories currently installed.) Preparing to unpack .../nodejs_20.0.0-1nodesource1_arm64.deb ... Detected old npm client, removing... Unpacking nodejs (20.0.0-1nodesource1) over (18.17.1-deb-1nodesource1) ... Setting up nodejs (20.0.0-1nodesource1) ... Processing triggers for man-db (2.9.4-2) ... Updating fallback to latest nodejs v20 release E: Failed to fetch http://archive.raspberrypi.org/debian/pool/main/f/ffmpeg/libavcodec58_4.3.7-0%2bdeb11u1%2brpt2_arm64.deb Error reading from server - read (104: Connection reset by peer) [IP: 2a00:1098:80:56::2:1 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? v20.0.0 has been installed! You are using the latest version now! /home/iobroker/.nodejs-update.sh: line 387: [: : integer expression expected Installing the nodejs! Extracting templates from packages: 100% Preconfiguring packages ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../base-files_11.1+deb11u11_arm64.deb ... Unpacking base-files (11.1+deb11u11) over (11.1+deb11u7) ... Setting up base-files (11.1+deb11u11) ... Installing new version of config file /etc/debian_version ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../bsdutils_1%3a2.36.1-8+deb11u2_arm64.deb ... Unpacking bsdutils (1:2.36.1-8+deb11u2) over (1:2.36.1-8+deb11u1) ... Setting up bsdutils (1:2.36.1-8+deb11u2) ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../tar_1.34+dfsg-1+deb11u1_arm64.deb ... Unpacking tar (1.34+dfsg-1+deb11u1) over (1.34+dfsg-1) ... Setting up tar (1.34+dfsg-1+deb11u1) ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../dpkg_1.20.13_arm64.deb ... Unpacking dpkg (1.20.13) over (1.20.12) ... Setting up dpkg (1.20.13) ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../ncurses-bin_6.2+20201114-2+deb11u2_arm64.deb ... Unpacking ncurses-bin (6.2+20201114-2+deb11u2) over (6.2+20201114-2+deb11u1) ... Setting up ncurses-bin (6.2+20201114-2+deb11u2) ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../libperl5.32_5.32.1-4+deb11u3_arm64.deb ... Unpacking libperl5.32:arm64 (5.32.1-4+deb11u3) over (5.32.1-4+deb11u2) ... Preparing to unpack .../perl_5.32.1-4+deb11u3_arm64.deb ... Unpacking perl (5.32.1-4+deb11u3) over (5.32.1-4+deb11u2) ... Preparing to unpack .../perl-base_5.32.1-4+deb11u3_arm64.deb ... Unpacking perl-base (5.32.1-4+deb11u3) over (5.32.1-4+deb11u2) ... Setting up perl-base (5.32.1-4+deb11u3) ... (Reading database ... 107506 files and directories currently installed.) Preparing to unpack .../0-perl-modules-5.32_5.32.1-4+deb11u3_all.deb ... Unpacking perl-modules-5.32 (5.32.1-4+deb11u3) over (5.32.1-4+deb11u2) ... Preparing to unpack .../1-libc6-dbg_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc6-dbg:arm64 (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Preparing to unpack .../2-libc-devtools_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc-devtools (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Preparing to unpack .../3-libc6-dev_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc6-dev:arm64 (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Preparing to unpack .../4-libc-dev-bin_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc-dev-bin (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Preparing to unpack .../5-libc6_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc6:arm64 (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Setting up libc6:arm64 (2.31-13+rpt2+rpi1+deb11u11) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../uuid-dev_2.36.1-8+deb11u2_arm64.deb ... Unpacking uuid-dev:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../libuuid1_2.36.1-8+deb11u2_arm64.deb ... Unpacking libuuid1:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Setting up libuuid1:arm64 (2.36.1-8+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libblkid-dev_2.36.1-8+deb11u2_arm64.deb ... Unpacking libblkid-dev:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../libblkid1_2.36.1-8+deb11u2_arm64.deb ... Unpacking libblkid1:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Setting up libblkid1:arm64 (2.36.1-8+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libfdisk1_2.36.1-8+deb11u2_arm64.deb ... Unpacking libfdisk1:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../libmount-dev_2.36.1-8+deb11u2_arm64.deb ... Unpacking libmount-dev:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../libmount1_2.36.1-8+deb11u2_arm64.deb ... Unpacking libmount1:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Setting up libmount1:arm64 (2.36.1-8+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libncurses6_6.2+20201114-2+deb11u2_arm64.deb ... Unpacking libncurses6:arm64 (6.2+20201114-2+deb11u2) over (6.2+20201114-2+deb11u1) ... Preparing to unpack .../libncursesw6_6.2+20201114-2+deb11u2_arm64.deb ... Unpacking libncursesw6:arm64 (6.2+20201114-2+deb11u2) over (6.2+20201114-2+deb11u1) ... Preparing to unpack .../libtinfo6_6.2+20201114-2+deb11u2_arm64.deb ... Unpacking libtinfo6:arm64 (6.2+20201114-2+deb11u2) over (6.2+20201114-2+deb11u1) ... Setting up libtinfo6:arm64 (6.2+20201114-2+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libsmartcols1_2.36.1-8+deb11u2_arm64.deb ... Unpacking libsmartcols1:arm64 (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Setting up libsmartcols1:arm64 (2.36.1-8+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../fdisk_2.36.1-8+deb11u2_arm64.deb ... Unpacking fdisk (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../util-linux_2.36.1-8+deb11u2_arm64.deb ... Unpacking util-linux (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Setting up util-linux (2.36.1-8+deb11u2) ... fstrim.service is a disabled or a static unit not running, not starting it. (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libc-bin_2.31-13+rpt2+rpi1+deb11u11_arm64.deb ... Unpacking libc-bin (2.31-13+rpt2+rpi1+deb11u11) over (2.31-13+rpt2+rpi1+deb11u5) ... Setting up libc-bin (2.31-13+rpt2+rpi1+deb11u11) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../ncurses-base_6.2+20201114-2+deb11u2_all.deb ... Unpacking ncurses-base (6.2+20201114-2+deb11u2) over (6.2+20201114-2+deb11u1) ... Setting up ncurses-base (6.2+20201114-2+deb11u2) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../0-libdbus-1-dev_1.12.28-0+deb11u1_arm64.deb ... Unpacking libdbus-1-dev:arm64 (1.12.28-0+deb11u1) over (1.12.24-0+deb11u1) ... Preparing to unpack .../1-dbus-user-session_1.12.28-0+deb11u1_arm64.deb ... Unpacking dbus-user-session (1.12.28-0+deb11u1) over (1.12.24-0+deb11u1) ... Preparing to unpack .../2-libx11-dev_2%3a1.7.2-1+deb11u2_arm64.deb ... Unpacking libx11-dev:arm64 (2:1.7.2-1+deb11u2) over (2:1.7.2-1+deb11u1) ... Preparing to unpack .../3-libx11-data_2%3a1.7.2-1+deb11u2_all.deb ... Unpacking libx11-data (2:1.7.2-1+deb11u2) over (2:1.7.2-1) ... Preparing to unpack .../4-libx11-6_2%3a1.7.2-1+deb11u2_arm64.deb ... Unpacking libx11-6:arm64 (2:1.7.2-1+deb11u2) over (2:1.7.2-1+deb11u1) ... Preparing to unpack .../5-libx11-xcb1_2%3a1.7.2-1+deb11u2_arm64.deb ... Unpacking libx11-xcb1:arm64 (2:1.7.2-1+deb11u2) over (2:1.7.2-1+deb11u1) ... Preparing to unpack .../6-dbus-x11_1.12.28-0+deb11u1_arm64.deb ... Unpacking dbus-x11 (1.12.28-0+deb11u1) over (1.12.24-0+deb11u1) ... Preparing to unpack .../7-dbus_1.12.28-0+deb11u1_arm64.deb ... Unpacking dbus (1.12.28-0+deb11u1) over (1.12.24-0+deb11u1) ... Preparing to unpack .../8-libdbus-1-3_1.12.28-0+deb11u1_arm64.deb ... Unpacking libdbus-1-3:arm64 (1.12.28-0+deb11u1) over (1.12.24-0+deb11u1) ... Preparing to unpack .../9-adduser_3.118+deb11u1_all.deb ... Unpacking adduser (3.118+deb11u1) over (3.118) ... Setting up adduser (3.118+deb11u1) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../0-libexpat1-dev_2.2.10-2+deb11u6_arm64.deb ... Unpacking libexpat1-dev:arm64 (2.2.10-2+deb11u6) over (2.2.10-2+deb11u5) ... Preparing to unpack .../1-libexpat1_2.2.10-2+deb11u6_arm64.deb ... Unpacking libexpat1:arm64 (2.2.10-2+deb11u6) over (2.2.10-2+deb11u5) ... Preparing to unpack .../2-systemd-sysv_247.3-7+deb11u6_arm64.deb ... Unpacking systemd-sysv (247.3-7+deb11u6) over (247.3-7+deb11u2) ... Preparing to unpack .../3-libpam-systemd_247.3-7+deb11u6_arm64.deb ... Unpacking libpam-systemd:arm64 (247.3-7+deb11u6) over (247.3-7+deb11u2) ... Preparing to unpack .../4-xserver-common_2%3a1.20.11-1+rpt3+deb11u13_all.deb ... Unpacking xserver-common (2:1.20.11-1+rpt3+deb11u13) over (2:1.20.11-1+rpt3+deb11u6) ... Preparing to unpack .../5-libudev-dev_247.3-7+deb11u6_arm64.deb ... Unpacking libudev-dev:arm64 (247.3-7+deb11u6) over (247.3-7+deb11u4) ... Preparing to unpack .../6-libsystemd0_247.3-7+deb11u6_arm64.deb ... Unpacking libsystemd0:arm64 (247.3-7+deb11u6) over (247.3-7+deb11u2) ... Setting up libsystemd0:arm64 (247.3-7+deb11u6) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../0-xserver-xorg-core_2%3a1.20.11-1+rpt3+deb11u13_arm64.deb ... Unpacking xserver-xorg-core (2:1.20.11-1+rpt3+deb11u13) over (2:1.20.11-1+rpt3+deb11u6) ... Preparing to unpack .../1-systemd-timesyncd_247.3-7+deb11u6_arm64.deb ... Unpacking systemd-timesyncd (247.3-7+deb11u6) over (247.3-7+deb11u2) ... Preparing to unpack .../2-systemd_247.3-7+deb11u6_arm64.deb ... Unpacking systemd (247.3-7+deb11u6) over (247.3-7+deb11u2) ... Preparing to unpack .../3-bluez_5.55-3.1+rpt2+deb11u1_arm64.deb ... Unpacking bluez (5.55-3.1+rpt2+deb11u1) over (5.55-3.1+rpt2) ... Preparing to unpack .../4-udev_247.3-7+deb11u6_arm64.deb ... Unpacking udev (247.3-7+deb11u6) over (247.3-7+deb11u4) ... Preparing to unpack .../5-libudev1_247.3-7+deb11u6_arm64.deb ... Unpacking libudev1:arm64 (247.3-7+deb11u6) over (247.3-7+deb11u4) ... Setting up libudev1:arm64 (247.3-7+deb11u6) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../0-libglib2.0-dev_2.66.8-1+deb11u4_arm64.deb ... Unpacking libglib2.0-dev:arm64 (2.66.8-1+deb11u4) over (2.66.8-1) ... Preparing to unpack .../1-libglib2.0-dev-bin_2.66.8-1+deb11u4_arm64.deb ... Unpacking libglib2.0-dev-bin (2.66.8-1+deb11u4) over (2.66.8-1) ... Preparing to unpack .../2-libglib2.0-data_2.66.8-1+deb11u4_all.deb ... Unpacking libglib2.0-data (2.66.8-1+deb11u4) over (2.66.8-1) ... Preparing to unpack .../3-libglib2.0-bin_2.66.8-1+deb11u4_arm64.deb ... Unpacking libglib2.0-bin (2.66.8-1+deb11u4) over (2.66.8-1) ... Preparing to unpack .../4-libglib2.0-0_2.66.8-1+deb11u4_arm64.deb ... Unpacking libglib2.0-0:arm64 (2.66.8-1+deb11u4) over (2.66.8-1) ... Preparing to unpack .../5-libbsd0_0.11.3-1+deb11u1_arm64.deb ... Unpacking libbsd0:arm64 (0.11.3-1+deb11u1) over (0.11.3-1) ... Preparing to unpack .../6-libgnutls30_3.7.1-5+deb11u6_arm64.deb ... Unpacking libgnutls30:arm64 (3.7.1-5+deb11u6) over (3.7.1-5+deb11u3) ... Setting up libgnutls30:arm64 (3.7.1-5+deb11u6) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../0-mount_2.36.1-8+deb11u2_arm64.deb ... Unpacking mount (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../1-nftables_0.9.8-3.1+deb11u2_arm64.deb ... Unpacking nftables (0.9.8-3.1+deb11u2) over (0.9.8-3.1+deb11u1) ... Preparing to unpack .../2-libnftables1_0.9.8-3.1+deb11u2_arm64.deb ... Unpacking libnftables1:arm64 (0.9.8-3.1+deb11u2) over (0.9.8-3.1+deb11u1) ... Preparing to unpack .../3-bsdextrautils_2.36.1-8+deb11u2_arm64.deb ... Unpacking bsdextrautils (2.36.1-8+deb11u2) over (2.36.1-8+deb11u1) ... Preparing to unpack .../4-chromium-browser-l10n_126.0.6478.164-rpt1_all.deb ... Unpacking chromium-browser-l10n (126.0.6478.164-rpt1) over (113.0.5672.59-rpt1) ... Preparing to unpack .../5-libk5crypto3_1.18.3-6+deb11u5_arm64.deb ... Unpacking libk5crypto3:arm64 (1.18.3-6+deb11u5) over (1.18.3-6+deb11u3) ... Setting up libk5crypto3:arm64 (1.18.3-6+deb11u5) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libkrb5support0_1.18.3-6+deb11u5_arm64.deb ... Unpacking libkrb5support0:arm64 (1.18.3-6+deb11u5) over (1.18.3-6+deb11u3) ... Setting up libkrb5support0:arm64 (1.18.3-6+deb11u5) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libkrb5-3_1.18.3-6+deb11u5_arm64.deb ... Unpacking libkrb5-3:arm64 (1.18.3-6+deb11u5) over (1.18.3-6+deb11u3) ... Setting up libkrb5-3:arm64 (1.18.3-6+deb11u5) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libgssapi-krb5-2_1.18.3-6+deb11u5_arm64.deb ... Unpacking libgssapi-krb5-2:arm64 (1.18.3-6+deb11u5) over (1.18.3-6+deb11u3) ... Setting up libgssapi-krb5-2:arm64 (1.18.3-6+deb11u5) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../libssl1.1_1.1.1w-0+deb11u1+rpt1_arm64.deb ... Unpacking libssl1.1:arm64 (1.1.1w-0+deb11u1+rpt1) over (1.1.1n-0+deb11u4+rpt1) ... Setting up libssl1.1:arm64 (1.1.1w-0+deb11u1+rpt1) ... (Reading database ... 107509 files and directories currently installed.) Preparing to unpack .../000-cups-daemon_2.3.3op2-3+deb11u8_arm64.deb ... Unpacking cups-daemon (2.3.3op2-3+deb11u8) over (2.3.3op2-3+deb11u2) ... Preparing to unpack .../001-cups-ipp-utils_2.3.3op2-3+deb11u8_arm64.deb ... Unpacking cups-ipp-utils (2.3.3op2-3+deb11u8) over (2.3.3op2-3+deb11u2) ... Preparing to unpack .../002-cups-common_2.3.3op2-3+deb11u8_all.deb ... Unpacking cups-common (2.3.3op2-3+deb11u8) over (2.3.3op2-3+deb11u2) ... Preparing to unpack .../003-cups-client_2.3.3op2-3+deb11u8_arm64.deb ... Unpacking cups-client (2.3.3op2-3+deb11u8) over (2.3.3op2-3+deb11u2) ... Preparing to unpack .../004-libwebp6_0.6.1-2.1+deb11u2_arm64.deb ... Unpacking libwebp6:arm64 (0.6.1-2.1+deb11u2) over (0.6.1-2.1) ... Preparing to unpack .../005-libtiff5_4.2.0-1+deb11u5_arm64.deb ... Unpacking libtiff5:arm64 (4.2.0-1+deb11u5) over (4.2.0-1+deb11u4) ... Preparing to unpack .../006-libcupsfilters1_1.28.7-1+deb11u2_arm64.deb ... -
@homoran
hmm ich fürchte ehrlich gesagt nicht.
Bin da nicht son fit und bin froh wenn alles läuft ;-)Ich mache in regelmäßigen abständen diesen Update Durchlauf mit
iob stop
iob update
iob upgrade self
iob fixdas war es dann aber auch schon mehr oder weniger.
Das Update er Node läuft Imme rnoch... er ist kräftig am installieren und am installieren...
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
Bin da nicht son fit und bin froh wenn alles läuft
Dann fux dich da rein und halte das System immer auf Stand, damit das auch weiterhin 'läuft'.
'Never tatsch a rannink süstäm' ist jedenfalls großer Bullshit.das war es dann aber auch schon mehr oder weniger.
Dann erweiter es um ein gefälliges
sudo apt update sudo apt full-upgrade -
@homoran
hmm ich fürchte ehrlich gesagt nicht.
Bin da nicht son fit und bin froh wenn alles läuft ;-)Ich mache in regelmäßigen abständen diesen Update Durchlauf mit
iob stop
iob update
iob upgrade self
iob fixdas war es dann aber auch schon mehr oder weniger.
Das Update er Node läuft Imme rnoch... er ist kräftig am installieren und am installieren...
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
Das Update er Node läuft Imme rnoch... er ist kräftig am installieren und am installieren...
Ja, das System schraubt jetzt die versäumten 246 Updates rein.
Davon wäre vermutlich ein Großteil gar nicht erforderlich, wenn du nicht da einen vollen Desktopt mit Druckerserver, Videoplayer usw. am Start hättest... -
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
Das Update er Node läuft Imme rnoch... er ist kräftig am installieren und am installieren...
Ja, das System schraubt jetzt die versäumten 246 Updates rein.
Davon wäre vermutlich ein Großteil gar nicht erforderlich, wenn du nicht da einen vollen Desktopt mit Druckerserver, Videoplayer usw. am Start hättest... -
@thomas-braun
und das wird nun n Tag dauern so ca??@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
und das wird nun n Tag dauern so ca??
Ein paar Minuten wird das dauern. Wenn keine Fehler auftauchen.
Das ist natürlich bei 246 mit höherer Wahrscheinlichkeit möglich als auf einem schlank aufgesetzen, regelmäßig gewarteten System.Du sparst dir also durch deinen 'never tatsch a ranning süstäm'-Ansatz nichts, es wird im Gegenteil nur komplexer und aufwändiger und fehleranfälliger, wenn man das Ding versumpfen lässt.
-
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
und das wird nun n Tag dauern so ca??
Ein paar Minuten wird das dauern. Wenn keine Fehler auftauchen.
Das ist natürlich bei 246 mit höherer Wahrscheinlichkeit möglich als auf einem schlank aufgesetzen, regelmäßig gewarteten System.Du sparst dir also durch deinen 'never tatsch a ranning süstäm'-Ansatz nichts, es wird im Gegenteil nur komplexer und aufwändiger und fehleranfälliger, wenn man das Ding versumpfen lässt.
@thomas-braun
ja... das Gefühl habe ich auch gerade...War aber keine Absicht :-)
-
@worxweis sagte in Kann IoBroker nicht mehr aufrufen:
Sorry, habe jetzt die iobroker-Oberfläche nochmal ganz normal aufgerufen und sie funktioniert wieder. Auch der Admin sieht aus, als wäre er aktuell auf 1.7,2.
Aber auch für dich gilt:
Updates einspielen und den Desktop AUS!
also die updates scheinen jetzt durch zu sein.
Da stand nun noch einmal mit iob diagnostiziert bestätigen.
Dabei kam nun das raus:======== Start marking the full check here =========
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 13:07:13 up 1:05, 3 users, load average: 4.21, 3.34, 3.12 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. This system needs to be REBOOTED! *** Time and Time Zones *** Local time: Sun 2024-09-22 13:07:13 CEST Universal time: Sun 2024-09-22 11:07:13 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': iobroker HOME=/home/iobroker GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth lpadmin gpio i2c spi *** Display-Server-Setup *** Display-Server: true Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.5G 130M 35M 2.2G 2.1G Swap: 99M 0B 99M Total: 3.9G 1.5G 230M Active iob-Instances: 15 3794 M total memory 1510 M used memory 1673 M active memory 1684 M inactive memory 130 M free memory 78 M buffer memory 2075 M swap cache 99 M total swap 0 M used swap 99 M free swap *** top - Table Of Processes *** top - 13:07:13 up 1:05, 3 users, load average: 4.21, 3.34, 3.12 Tasks: 214 total, 3 running, 211 sleeping, 0 stopped, 0 zombie %Cpu(s): 23.6 us, 5.6 sy, 0.0 ni, 70.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3794.3 total, 127.4 free, 1513.4 used, 2153.5 buff/cache MiB Swap: 100.0 total, 100.0 free, 0.0 used. 2122.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 7.8G 20G 29% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 32M 224M 13% /boot tmpfs tmpfs 380M 20K 380M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: [Sun Sep 22 12:01:29 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:8E:3F:E4 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=7e9f8956-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Sun Sep 22 12:01:30 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Sun Sep 22 12:01:30 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Sun Sep 22 12:01:32 2024] EXT4-fs (mmcblk0p2): recovery complete [Sun Sep 22 12:01:32 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Sun Sep 22 12:01:32 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Sun Sep 22 12:01:34 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=1678472k,nr_inodes=419618,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,size=777080k,nr_inodes=819200,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=388536k,nr_inodes=97134,mode=700,uid=1000,gid=1000 | `-/run/user/1000/gvfs gvfsd-fuse fuse.gvfsd-fuse rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.8G /var/ 931M /var/log 929M /var/log/journal/365fb86da8514c2a85a61e3d210b6795 929M /var/log/journal 609M /var/cache Archived and active journals take up 928.1M in the file system. /opt/iobroker/backups: 22M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 588M /opt/iobroker/iobroker-data/ 520M /opt/iobroker/iobroker-data/files 441M /opt/iobroker/iobroker-data/files/javascript.admin 409M /opt/iobroker/iobroker-data/files/javascript.admin/static 408M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 14M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.2cca4954.js 10M /opt/iobroker/iobroker-data/objects.jsonl 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map 8.6M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** NodeJS-Installation *** /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.17.0-1nodesource1 Candidate: 20.17.0-1nodesource1 Version table: *** 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u5 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 6.0.11 admin: 7.1.2 javascript: 8.7.6 nodejs modules from github: 0 Adapter State system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled + system.adapter.backitup.0 : backitup : iobroker - enabled system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.hue.0 : hue : iobroker - enabled, port: 443 + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.lgtv.0 : lgtv : iobroker - enabled + system.adapter.meross.0 : meross : iobroker - enabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : iobroker - enabled, port: 54321 + system.adapter.mihome-vacuum.1 : mihome-vacuum : iobroker - enabled, port: 54321 + system.adapter.nuki-extended.0 : nuki-extended : iobroker - enabled + system.adapter.pushover.0 : pushover : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.socketio.0 : socketio : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: :: + system.adapter.sonoff.1 : sonoff : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.sonoff.2 : sonoff : iobroker - enabled, port: 1885, bind: 0.0.0.0 system.adapter.sonoff.3 : sonoff : iobroker - enabled, port: 1886, bind: 0.0.0.0 system.adapter.tado.0 : tado : iobroker - enabled system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.hue.0 : hue : iobroker - enabled, port: 443 + system.adapter.mihome-vacuum.0 : mihome-vacuum : iobroker - enabled, port: 54321 + system.adapter.mihome-vacuum.1 : mihome-vacuum : iobroker - enabled, port: 54321 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 system.adapter.socketio.0 : socketio : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1883, bind: :: + system.adapter.sonoff.1 : sonoff : iobroker - enabled, port: 1884, bind: 0.0.0.0 + system.adapter.sonoff.2 : sonoff : iobroker - enabled, port: 1885, bind: 0.0.0.0 system.adapter.sonoff.3 : sonoff : iobroker - enabled, port: 1886, bind: 0.0.0.0 system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Instances Used repository: stable Adapter "admin" : 7.1.2 , installed 7.1.2 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 3.0.22 , installed 3.0.22 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "hue" : 3.12.0 , installed 3.12.0 Adapter "javascript" : 8.7.6 , installed 8.7.6 Controller "js-controller": 6.0.11 , installed 6.0.11 Adapter "lgtv" : 2.2.0 , installed 2.2.0 Adapter "meross" : 1.17.0 , installed 1.17.0 Adapter "mihome-vacuum": 4.2.0 , installed 4.2.0 Adapter "nuki-extended": 2.7.0 , installed 2.7.0 Adapter "pushover" : 4.1.0 , installed 4.1.0 Adapter "shelly" : 7.0.0 , installed 7.0.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.1.0 , installed 3.1.0 Adapter "tado" : 0.5.6 , installed 0.5.6 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 6973 States: 5294 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 57969 10932/sshd: /usr/sb tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 59458 11334/cupsd tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 66609 17374/iobroker.js-c tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 66614 17374/iobroker.js-c tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1000 66890 17603/io.sonoff.1 tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1000 66910 17646/io.sonoff.2 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1000 67768 17673/io.sonoff.3 tcp6 0 0 :::51989 :::* LISTEN 1000 66747 17477/io.nuki-exten tcp6 0 0 :::22 :::* LISTEN 0 57971 10932/sshd: /usr/sb tcp6 0 0 :::1883 :::* LISTEN 1000 66832 17553/io.sonoff.0 tcp6 0 0 :::8084 :::* LISTEN 1000 67815 17730/io.socketio.0 tcp6 0 0 :::8082 :::* LISTEN 1000 68627 17714/io.web.0 tcp6 0 0 ::1:631 :::* LISTEN 0 59457 11334/cupsd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 14883 375/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 66843 17521/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 15434 452/dhcpcd udp 0 0 0.0.0.0:53421 0.0.0.0:* 1000 64376 17492/io.mihome-vac udp 0 0 0.0.0.0:53422 0.0.0.0:* 1000 67706 17556/io.mihome-vac udp 0 0 0.0.0.0:47504 0.0.0.0:* 108 14885 375/avahi-daemon: r udp 0 0 0.0.0.0:631 0.0.0.0:* 0 61466 11453/cups-browsed udp6 0 0 :::5353 :::* 108 14884 375/avahi-daemon: r udp6 0 0 :::39079 :::* 108 14886 375/avahi-daemon: r udp6 0 0 :::546 :::* 0 15445 452/dhcpcd *** Log File - Last 25 Lines *** 2024-09-22 13:06:57.667 - info: host.iobroker instance system.adapter.discovery.0 in version "5.0.0" started with pid 17694 2024-09-22 13:06:57.951 - info: sonoff.3 (17673) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.sonoff, node: v20.17.0, js-controller: 6.0.11 2024-09-22 13:06:58.027 - info: sonoff.3 (17673) Starting MQTT authenticated server on port 1886 2024-09-22 13:07:01.718 - info: host.iobroker instance system.adapter.web.0 in version "6.2.5" started with pid 17714 2024-09-22 13:07:01.876 - info: discovery.0 (17694) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.17.0, js-controller: 6.0.11 2024-09-22 13:07:05.582 - info: host.iobroker instance system.adapter.socketio.0 in version "6.7.1" started with pid 17730 2024-09-22 13:07:05.815 - info: web.0 (17714) starting. Version 6.2.5 in /opt/iobroker/node_modules/iobroker.web, node: v20.17.0, js-controller: 6.0.11 2024-09-22 13:07:06.316 - info: web.0 (17714) socket.io server listening on port 8082 2024-09-22 13:07:06.327 - info: web.0 (17714) http server listening on port 8082 2024-09-22 13:07:08.788 - info: socketio.0 (17730) starting. Version 6.7.1 in /opt/iobroker/node_modules/iobroker.socketio, node: v20.17.0, js-controller: 6.0.11 2024-09-22 13:07:08.881 - info: socketio.0 (17730) socket.io server listening on port 8084 2024-09-22 13:07:09.565 - info: host.iobroker instance system.adapter.tado.0 in version "0.5.6" started with pid 17760 2024-09-22 13:07:13.576 - info: tado.0 (17760) starting. Version 0.5.6 in /opt/iobroker/node_modules/iobroker.tado, node: v20.17.0, js-controller: 6.0.11 2024-09-22 13:07:13.611 - info: tado.0 (17760) Started with JSON-Explorer version 0.1.16 2024-09-22 13:07:14.263 - info: tado.0 (17760) Connected to Tado cloud, initialyzing... 2024-09-22 13:07:20.929 - info: tado.0 (17760) Initialisation finished, connected to Tado cloud service refreshing every 30 seconds 2024-09-22 13:07:49.273 - info: alexa2.0 (17447) No smart home devices to query 2024-09-22 13:07:52.362 - info: javascript.0 (17395) script.js.Hue_Push: missing update instructions for sensors.light.light_level_report 2024-09-22 13:07:52.363 - info: javascript.0 (17395) script.js.Hue_Push: {"light":{"light_level":18437,"light_level_report":{"changed":"2024-09-22T11:07:52.269Z","light_level":18437}},"owner":{"rid":"29e5dd1b-dce7-41dc-8f39-1e6205527c74","rtype":"device"}} 2024-09-22 13:07:50.997 - info: alexa2.0 (17447) Subscribing to states... 2024-09-22 13:07:51.004 - info: alexa2.0 (17447) Deleting the following states: ["Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.#enabled","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.#delete","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.powerState","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.connectivity","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.connectivity-reason","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.#query","Smart-Home-Devices.9a149c71-2334-4f37-ba0a-191ce6da7cb7.#includeInAllQuery","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.#enabled","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.#delete","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.powerState","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.connectivity","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.connectivity-reason","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.#query","Smart-Home-Devices.57550b1c-5943-4d84-9324-307a61cd0c13.#includeInAllQuery","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.#enabled","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.#delete","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.powerState","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.connectivity","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.connectivity-reason","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.#query","Smart-Home-Devices.aae785aa-8a9e-422e-8266-ddb3e80d836b.#includeInAllQuery","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.#enabled","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.#delete","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.powerState","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.connectivity","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.connectivity-reason","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.#query","Smart-Home-Devices.73c1f150-8997-4752-bf73-9b687e46cf99.#includeInAllQuery","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.#enabled","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.#delete","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.powerState","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.connectivity","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.connectivity-reason","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.#query","Smart-Home-Devices.30cb7c91-b1be-4228-a814-804cb8cc0a0a.#includeInAllQuery","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.#enabled","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.#delete","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.powerState","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.connectivity","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.connectivity-reason","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.#query","Smart-Home-Devices.3d78131d-adfc-42f1-a9ff-d485ca5769a5.#includeInAllQuery","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.#enabled","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.#delete","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.powerState","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.connectivity","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.connectivity-reason","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.#query","Smart-Home-Devices.b408872e-a06b-430a-ac61-2db625a35858.#includeInAllQuery","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.#enabled","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.#delete","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.powerState","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.connectivity","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.connectivity-reason","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.#query","Smart-Home-Devices.3c2026ad-2e95-4955-8b1e-b5a2b87978aa.#includeInAllQuery","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.#enabled","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.#delete","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.powerState","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.brightness","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.connectivity","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.connectivity-reason","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.#query","Smart-Home-Devices.b08a9684-6542-46aa-989c-b14b406faa27.#includeInAllQuery","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.#enabled","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.#delete","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.powerState","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.brightness","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.connectivity","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.connectivity-reason","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.#query","Smart-Home-Devices.bdbbb442-2579-42b6-9c8f-5cc8cbbb4457.#includeInAllQuery","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.#enabled","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.#delete","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.powerState","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.connectivity","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.connectivity-reason","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.#query","Smart-Home-Devices.0c3b5822-3998-42d3-8064-3e443f575a10.#includeInAllQuery","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.#enabled","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.#delete","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.powerState","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.connectivity","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.connectivity-reason","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.#query","Smart-Home-Devices.18337ae9-f949-4b40-8959-e7e9397ceb83.#includeInAllQuery","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.#enabled","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.#delete","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.powerState","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.connectivity","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.connectivity-reason","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.#query","Smart-Home-Devices.2db89f87-9eae-4c24-b003-e28b07d27c76.#includeInAllQuery","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.#enabled","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.#delete","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.powerState","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.connectivity","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.connectivity-reason","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.#query","Smart-Home-Devices.9d6f241d-e347-4c1b-94b6-009bd35cb597.#includeInAllQuery","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.#enabled","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.#delete","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.powerState","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.connectivity","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.connectivity-reason","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.#query","Smart-Home-Devices.010add55-37cc-48b4-b43b-7cc065f12ccb.#includeInAllQuery"] 2024-09-22 13:07:55.951 - info: alexa2.0 (17447) Alexa-Push-Connection (macDms = true) established. Disable Polling 2024-09-22 13:08:06.251 - info: alexa2.0 (17447) Initialization Done ... 2024-09-22 13:08:06.703 - info: javascript.0 (17395) script.js.Hue_Push: missing update instructions for sensors.light.light_level_report 2024-09-22 13:08:06.704 - info: javascript.0 (17395) script.js.Hue_Push: {"light":{"light_level":10401,"light_level_report":{"changed":"2024-09-22T11:08:06.609Z","light_level":10401}},"owner":{"rid":"0045d363-a198-4f59-a8b4-8281aac23ba4","rtype":"device"}}============ Mark until here for C&P =============
-
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 This system needs to be REBOOTED NOW! Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 1.3G 409M 35M 2.1G 2.4G Swap: 99M 0B 99M Total: 3.9G 1.3G 509M Active iob-Instances: 15 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.2 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6973 States: 5294 Size of iob-Database: 12M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Was mache ich denn nun?
-
======================= SUMMARY ======================= v.2024-05-22 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 0 This system needs to be REBOOTED NOW! Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 3.8G 1.3G 409M 35M 2.1G 2.4G Swap: 99M 0B 99M Total: 3.9G 1.3G 509M Active iob-Instances: 15 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 7.1.2 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 6973 States: 5294 Size of iob-Database: 12M /opt/iobroker/iobroker-data/objects.jsonl 8.0M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================Was mache ich denn nun?
This system needs to be REBOOTED!
Mach das!
sudo systemctl set-default multi-user.target iob stop sudo reboot -
This system needs to be REBOOTED!
Mach das!
sudo systemctl set-default multi-user.target iob stop sudo reboot -
@thomas-braun
hab ich gemacht...dann neu auf der Konsole anmelden?
@fuxsism sagte in Kann IoBroker nicht mehr aufrufen:
dann neu auf der Konsole anmelden?
Ja, und dann einen frischen Lauf von
iob diag
346
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge