NEWS
Kein Admin nach Update
Error/Bug
36
Beiträge
5
Kommentatoren
1.5k
Aufrufe
4
Watching
-
@rj3n53n
Alles...Sorry, hat einen Moment gedauert.
Ich muss den Beitrag teilen.========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:09:33 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Sep 13 14:09:33 UTC 2025 Sat Sep 13 16:09:33 CEST 2025 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker sudo: unable to resolve host ioBroker: Name or service not known HOME=/opt/iobroker sudo: unable to resolve host ioBroker: Name or service not known GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 859M 208M 10G 10G Swap: 12G 996M 11G Total: 28G 6.9G 11G Active iob-Instances: 32 15854 M total memory 5585 M used memory 6429 M active memory 6748 M inactive memory 819 M free memory 658 M buffer memory 9395 M swap cache 11563 M total swap 950 M used swap 10613 M free swap *** top - Table Of Processes *** top - 16:09:34 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 Tasks: 40 total, 1 running, 39 sleeping, 0 stopped, 0 zombie %Cpu(s): 50.0 us, 0.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15854.0 total, 819.9 free, 5584.7 used, 10054.0 buff/cache MiB Swap: 11563.9 total, 10613.5 free, 950.5 used. 10269.3 avail Mem *** DMESG CRITICAL ERRORS *** sudo: unable to resolve host ioBroker: Name or service not known No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 13T 1.4T 12T 11% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 13T 1.4T 12T 11% /opt/iobroker tmpfs tmpfs 7.8G 0 7.8G 0% /proc/acpi tmpfs tmpfs 7.8G 0 7.8G 0% /proc/scsi tmpfs tmpfs 7.8G 0 7.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host ioBroker: Name or service not known Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=faf9736b0331140a,dio,d irperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/ioBroker_mount] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/resolv.conf] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hostname] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hosts] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: sudo: unable to resolve host ioBroker: Name or service not known 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 12K /opt/iobroker/backups/ 8.0K /opt/iobroker/backups/@eaDir /opt/iobroker/iobroker-data: 662M /opt/iobroker/iobroker-data/ 423M /opt/iobroker/iobroker-data/files 177M /opt/iobroker/iobroker-data/backup-objects 73M /opt/iobroker/iobroker-data/files/vis-2 56M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 30M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.19.0 /usr/bin/node v22.19.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.19.0-1nodesource1 Candidate: 22.19.0-1nodesource1 Version table: *** 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host ioBroker: Name or service not known sudo: unable to resolve host ioBroker: Name or service not known █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ -
Sorry, hat einen Moment gedauert.
Ich muss den Beitrag teilen.========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:09:33 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Sep 13 14:09:33 UTC 2025 Sat Sep 13 16:09:33 CEST 2025 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker sudo: unable to resolve host ioBroker: Name or service not known HOME=/opt/iobroker sudo: unable to resolve host ioBroker: Name or service not known GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 859M 208M 10G 10G Swap: 12G 996M 11G Total: 28G 6.9G 11G Active iob-Instances: 32 15854 M total memory 5585 M used memory 6429 M active memory 6748 M inactive memory 819 M free memory 658 M buffer memory 9395 M swap cache 11563 M total swap 950 M used swap 10613 M free swap *** top - Table Of Processes *** top - 16:09:34 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 Tasks: 40 total, 1 running, 39 sleeping, 0 stopped, 0 zombie %Cpu(s): 50.0 us, 0.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15854.0 total, 819.9 free, 5584.7 used, 10054.0 buff/cache MiB Swap: 11563.9 total, 10613.5 free, 950.5 used. 10269.3 avail Mem *** DMESG CRITICAL ERRORS *** sudo: unable to resolve host ioBroker: Name or service not known No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 13T 1.4T 12T 11% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 13T 1.4T 12T 11% /opt/iobroker tmpfs tmpfs 7.8G 0 7.8G 0% /proc/acpi tmpfs tmpfs 7.8G 0 7.8G 0% /proc/scsi tmpfs tmpfs 7.8G 0 7.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host ioBroker: Name or service not known Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=faf9736b0331140a,dio,d irperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/ioBroker_mount] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/resolv.conf] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hostname] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hosts] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: sudo: unable to resolve host ioBroker: Name or service not known 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 12K /opt/iobroker/backups/ 8.0K /opt/iobroker/backups/@eaDir /opt/iobroker/iobroker-data: 662M /opt/iobroker/iobroker-data/ 423M /opt/iobroker/iobroker-data/files 177M /opt/iobroker/iobroker-data/backup-objects 73M /opt/iobroker/iobroker-data/files/vis-2 56M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 30M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.19.0 /usr/bin/node v22.19.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.19.0-1nodesource1 Candidate: 22.19.0-1nodesource1 Version table: *** 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host ioBroker: Name or service not known sudo: unable to resolve host ioBroker: Name or service not known █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██@rj3n53n sagte in Kein Admin nach Update:
Ich muss den Beitrag teilen.
Nein, musst du nicht.
Die Ausgabe passt normalerweise in Gänze in ein Posting rein. -
Sorry, hat einen Moment gedauert.
Ich muss den Beitrag teilen.========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:09:33 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Sep 13 14:09:33 UTC 2025 Sat Sep 13 16:09:33 CEST 2025 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker sudo: unable to resolve host ioBroker: Name or service not known HOME=/opt/iobroker sudo: unable to resolve host ioBroker: Name or service not known GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 859M 208M 10G 10G Swap: 12G 996M 11G Total: 28G 6.9G 11G Active iob-Instances: 32 15854 M total memory 5585 M used memory 6429 M active memory 6748 M inactive memory 819 M free memory 658 M buffer memory 9395 M swap cache 11563 M total swap 950 M used swap 10613 M free swap *** top - Table Of Processes *** top - 16:09:34 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 Tasks: 40 total, 1 running, 39 sleeping, 0 stopped, 0 zombie %Cpu(s): 50.0 us, 0.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15854.0 total, 819.9 free, 5584.7 used, 10054.0 buff/cache MiB Swap: 11563.9 total, 10613.5 free, 950.5 used. 10269.3 avail Mem *** DMESG CRITICAL ERRORS *** sudo: unable to resolve host ioBroker: Name or service not known No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 13T 1.4T 12T 11% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 13T 1.4T 12T 11% /opt/iobroker tmpfs tmpfs 7.8G 0 7.8G 0% /proc/acpi tmpfs tmpfs 7.8G 0 7.8G 0% /proc/scsi tmpfs tmpfs 7.8G 0 7.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host ioBroker: Name or service not known Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=faf9736b0331140a,dio,d irperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/ioBroker_mount] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/resolv.conf] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hostname] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hosts] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: sudo: unable to resolve host ioBroker: Name or service not known 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 12K /opt/iobroker/backups/ 8.0K /opt/iobroker/backups/@eaDir /opt/iobroker/iobroker-data: 662M /opt/iobroker/iobroker-data/ 423M /opt/iobroker/iobroker-data/files 177M /opt/iobroker/iobroker-data/backup-objects 73M /opt/iobroker/iobroker-data/files/vis-2 56M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 30M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.19.0 /usr/bin/node v22.19.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.19.0-1nodesource1 Candidate: 22.19.0-1nodesource1 Version table: *** 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host ioBroker: Name or service not known sudo: unable to resolve host ioBroker: Name or service not known █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██*** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: ioBroker ioBroker (version: 6.0.11, hostname: ioBroker , alive, uptime: 13447) Core adapters versions js-controller: 6.0.11 admin: 3.7.9 javascript: 8.9.2 nodejs modules from github: 1 | +-- syno@3.0.0 (git+https://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0) Adapter State system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : ioBroker - enabled system.adapter.alias-manager.0 : alias-manager : ioBroker - enabled + system.adapter.backitup.0 : backitup : ioBroker - enabled + system.adapter.bring.0 : bring : ioBroker - enabled system.adapter.daikin.0 : daikin : ioBroker - disabled system.adapter.daswetter.0 : daswetter : ioBroker - enabled + system.adapter.device-reminder.0 : device-reminder : ioBroker - enabled system.adapter.devices.0 : devices : ioBroker - enabled system.adapter.discovery.0 : discovery : ioBroker - disabled system.adapter.ds18b20.0 : ds18b20 : ioBroker - disabled system.adapter.dwd.0 : dwd : ioBroker - enabled + system.adapter.evcc.0 : evcc : ioBroker - enabled, port: 7070 system.adapter.flot.0 : flot : ioBroker - disabled + system.adapter.history.0 : history : ioBroker - enabled + system.adapter.hm-rega.0 : hm-rega : ioBroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : ioBroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : ioBroker - enabled, port: 0 system.adapter.ical.0 : ical : ioBroker - enabled system.adapter.ical.1 : ical : ioBroker - enabled system.adapter.ical.2 : ical : ioBroker - enabled system.adapter.ical.3 : ical : ioBroker - disabled system.adapter.iceroad.0 : iceroad : ioBroker - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : ioBroker - enabled + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.iot.0 : iot : ioBroker - enabled + system.adapter.javascript.0 : javascript : ioBroker - enabled system.adapter.lcn.0 : lcn : ioBroker - disabled, port: 4114 system.adapter.lorawan.0 : lorawan : ioBroker - disabled, port: 8883 system.adapter.modbus.0 : modbus : ioBroker - disabled system.adapter.mqtt-client.0 : mqtt-client : ioBroker - disabled, port: 1883 + system.adapter.mqtt.0 : mqtt : ioBroker - enabled, port: 1883, bind: 192.168.178.70 system.adapter.netatmo-crawler.0 : netatmo-crawler : io : ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.welcome.0 : welcome : ioBroker - disabled, port: 80, bind: 192.168.178.70, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : ioBroker - enabled system.adapter.wiffi-wz.0 : wiffi-wz : ioBroker - disabled + system.adapter.wled.0 : wled : ioBroker - enabled Broker - enabled + system.adapter.nina.0 : nina : ioBroker - enabled system.adapter.node-red.0 : node-red : ioBroker - disabled, port: 6335, bind: 192.168.178.70 + system.adapter.nut.0 : nut : ioBroker - enabled system.adapter.pegelalarm.0 : pegelalarm : ioBroker - enabled system.adapter.pi-hole.0 : pi-hole : ioBroker - disabled + system.adapter.ping.0 : ping : ioBroker - enabled + system.adapter.plenticore.0 : plenticore : ioBroker - enabled, port: 443 + system.adapter.pollenflug.0 : pollenflug : ioBroker - enabled system.adapter.rpi2.0 : rpi2 : ioBroker - disabled + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.snmp.0 : snmp : ioBroker - enabled + system.adapter.synology.0 : synology : ioBroker - enabled, port: 5000 + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : ioBroker - enabled + system.adapter.tibberlink.0 : tibberlink : ioBroker - enabled + system.adapter.tr-064.0 : tr-064 : ioBroker - enabled + system.adapter.trashschedule.0 : trashschedule : ioBroker - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : ioBroker - enabled + system.adapter.vis-2.0 : vis-2 : ioBroker - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : ioBroker - enabled system.adapter.vis-icontwo.0 : vis-icontwo : ioBroker - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : ioBroker - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : ioBroker - disabled system.adapter.vis-justgage.0 : vis-justgage : ioBroker - disabled system.adapter.vis-material-advanced.0 : vis-material-advanced : ioBroker - enabled system.adapter.vis-material.0 : vis-material : ioBroker - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : ioBroker - enabled system.adapter.vis-plumb.0 : vis-plumb : ioBroker - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : ioBroker - disabled system.adapter.vis-weather.0 : vis-weather : ioBroker - enabled system.adapter.vis.0 : vis : ioBroker - enabled system.adapter.weatherunderground.0 : weatherunderground : ioBroker - disabled + system.adapter.web.0 : web + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.evcc.0 : evcc : ioBroker - enabled, port: 7070 + system.adapter.hm-rpc.0 : hm-rpc : ioBroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : ioBroker - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : ioBroker - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : ioBroker - enabled, port: 1883, bind: 192.168.178.70 + system.adapter.plenticore.0 : plenticore : ioBroker - enabled, port: 443 + system.adapter.shelly.0 : shelly : ioBroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.synology.0 : synology : ioBroker - enabled, port: 5000 + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, 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-Adapters Used repository: stable Adapter "admin" : 7.7.2 , installed 3.7.9 [Updatable] Adapter "alexa2" : 3.27.3 , installed 3.27.3 Adapter "alias-manager": 2.0.0 , installed 2.0.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "bring" : 1.8.4 , installed 1.8.4 Adapter "daikin" : 1.5.1 , installed 1.5.1 Adapter "daswetter" : 3.2.3 , installed 3.2.3 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "devices" : 1.2.8 , installed 1.2.8 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "ds18b20" : 3.0.1 , installed 3.0.1 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "evcc" : 0.2.3 , installed 0.2.3 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "ical" : 1.16.2 , installed 1.16.2 Adapter "iceroad" : 1.2.1 , installed 1.2.1 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 6.0.11 [Updatable] Adapter "lcn" : 3.0.1 , installed 3.0.1 Adapter "lorawan" : 1.10.22 , installed 1.6.0 [Updatable] Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "mqtt-client" : 3.0.0 , installed 3.0.0 Adapter "netatmo-crawler": 1.0.0 , installed 1.0.0 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "nut" : 1.6.0 , installed 1.6.0 Adapter "pegelalarm" : 1.3.9 , installed 1.3.9 Adapter "pi-hole" : 1.3.6 , installed 1.3.6 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "plenticore" : 2.2.0 , installed 2.2.0 Adapter "pollenflug" : 2.0.0 , installed 2.0.0 Adapter "rpi2" : 2.4.0 , installed 2.4.0 Adapter "shelly" : 10.1.0 , installed 10.1.0 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "snmp" : 3.3.0 , installed 3.3.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "synology" : 3.1.0 , installed 3.1.0 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "tibberlink" : 5.0.0 , installed 5.0.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.13.4 , installed 2.13.4 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-icontwo" : 1.18.0 , installed 1.18.0 Adapter "vis-inventwo" : 3.3.5 , installed 3.3.5 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-material" : 0.2.0 , installed 0.2.0 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.12 , installed 2.5.12 Adapter "weatherunderground": 3.7.0, installed 3.7.0 Adapter "web" : 7.0.8 , installed 6.2.5 [Updatable] Adapter "welcome" : 1.0.2 , installed 1.0.2 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "wiffi-wz" : 2.2.1 , installed 2.2.1 Adapter "wled" : 0.7.2 , installed 0.7.2 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 14283 States: 11962 *** OS-Repositories and Updates *** sudo: unable to resolve host ioBroker: Name or service not known sudo: unable to resolve host ioBroker: Name or service not known Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** sudo: unable to resolve host ioBroker: Name or service not known 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:9001 0.0.0.0:* LISTEN 1000 1021077767 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 47362 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 47361 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 47360 - tcp 0 0 0.0.0.0:5001 0.0.0.0:* LISTEN 0 47348 - tcp 0 0 0.0.0.0:9002 0.0.0.0:* LISTEN 0 181183 - tcp 0 0 0.0.0.0:554 0.0.0.0:* LISTEN 0 102514 - tcp 0 0 0.0.0.0:23883 0.0.0.0:* LISTEN 0 202376 - tcp 0 0 0.0.0.0:3307 0.0.0.0:* LISTEN 66 92206 - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 52752 - tcp 0 0 127.0.0.1:2380 0.0.0.0:* LISTEN 0 140798 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 244860 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 244859 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 244858 - tcp 0 0 0.0.0.0:5357 0.0.0.0:* LISTEN 0 244856 - tcp 0 0 0.0.0.0:4045 0.0.0.0:* LISTEN 0 53285 - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 24795 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 47368 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 47367 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 47366 - tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 47350 - tcp 0 0 192.168.178.70:2001 0.0.0.0:* LISTEN 1000 1021085318 - tcp 0 0 127.0.0.1:2385 0.0.0.0:* LISTEN 0 228518 - tcp 0 0 192.168.178.70:50001 0.0.0.0:* LISTEN 0 92703 - tcp 0 0 192.168.178.70:50002 0.0.0.0:* LISTEN 0 95823 - tcp 0 0 192.168.178.70:49170 0.0.0.0:* LISTEN 254178 92148 - tcp 0 0 127.0.0.1:5555 0.0.0.0:* LISTEN 0 299981638 - tcp 0 0 127.0.0.1:915 0.0.0.0:* LISTEN 0 171331 - tcp 0 0 0.0.0.0:662 0.0.0.0:* LISTEN 0 40192 - tcp 0 0 0.0.0.0:3000 0.0.0.0:* LISTEN 0 824890506 - tcp 0 0 0.0.0.0:23000 0.0.0.0:* LISTEN 0 202297 - tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 55 76580 - tcp 0 0 127.0.0.1:33304 0.0.0.0:* LISTEN 0 54232 - tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN 0 212185 - tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1000 1021103558 - tcp 0 0 192.168.178.70:2010 0.0.0.0:* LISTEN 1000 1021086258 - tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 0 183324 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 47374 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 47373 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 47372 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 47352 - tcp 0 0 127.0.0.1:30300 0.0.0.0:* LISTEN 0 231391 - tcp 0 0 0.0.0.0:892 0.0.0.0:* LISTEN 0 39166 - tcp 0 0 127.0.0.1:16509 0.0.0.0:* LISTEN 0 221036 - tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 52751 - tcp 0 0 0.0.0.0:6335 0.0.0.0:* LISTEN 0 1021099404 - tcp 0 0 127.0.0.1:512 0.0.0.0:* LISTEN 0 266626 - tcp 0 0 0.0.0.0:5888 0.0.0.0:* LISTEN 0 248223 - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 0 53264 - tcp 0 0 127.0.0.1:161 0.0.0.0:* LISTEN 0 41249 - tcp 0 0 0.0.0.0:6690 0.0.0.0:* LISTEN 0 150084 - tcp 0 0 0.0.0.0:9443 0.0.0.0:* LISTEN 0 824943935 - tcp 0 0 0.0.0.0:3493 0.0.0.0:* LISTEN 0 30131 - tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1000 1021077778 - tcp 0 0 0.0.0.0:23080 0.0.0.0:* LISTEN 0 201307 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 47356 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 47355 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 47354 - tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN 0 47346 - tcp6 0 0 :::5001 :::* LISTEN 0 47365 - tcp6 0 0 :::5001 :::* LISTEN 0 47364 - tcp6 0 0 :::5001 :::* LISTEN 0 47363 - tcp6 0 0 :::5001 :::* LISTEN 0 47349 - tcp6 0 0 :::9002 :::* LISTEN 0 182284 - tcp6 0 0 :::23883 :::* LISTEN 0 200401 - tcp6 0 0 :::139 :::* LISTEN 0 52750 - tcp6 0 0 :::5357 :::* LISTEN 0 244863 - tcp6 0 0 :::5357 :::* LISTEN 0 244862 - tcp6 0 0 :::5357 :::* LISTEN 0 244861 - tcp6 0 0 :::5357 :::* LISTEN 0 244857 - tcp6 0 0 :::4045 :::* LISTEN 0 53287 - tcp6 0 0 :::1935 :::* LISTEN 233155 101868 - tcp6 0 0 :::111 :::* LISTEN 0 24798 - tcp6 0 0 :::80 :::* LISTEN 0 47371 - tcp6 0 0 :::80 :::* LISTEN 0 47370 - tcp6 0 0 :::80 :::* LISTEN 0 47369 - tcp6 0 0 :::80 :::* LISTEN 0 47351 - tcp6 0 0 :::8082 :::* LISTEN 1000 1021107683 - tcp6 0 0 :::8086 :::* LISTEN 1000 1005191441 - tcp6 0 0 :::662 :::* LISTEN 0 40196 - tcp6 0 0 :::3000 :::* LISTEN 0 824888236 - tcp6 0 0 :::23000 :::* LISTEN 0 202304 - tcp6 0 0 :::3001 :::* LISTEN 0 206500 - tcp6 0 0 :::1883 :::* LISTEN 0 181200 - tcp6 0 0 :::443 :::* LISTEN 0 47377 - tcp6 0 0 :::443 :::* LISTEN 0 47376 - tcp6 0 0 :::443 :::* LISTEN 0 47375 - tcp6 0 0 :::443 :::* LISTEN 0 47353 - tcp6 0 0 :::892 :::* LISTEN 0 39170 - tcp6 0 0 :::3261 :::* LISTEN 0 54081 - tcp6 0 0 :::445 :::* LISTEN 0 52749 - tcp6 0 0 :::5566 :::* LISTEN 0 81073 - tcp6 0 0 :::6335 :::* LISTEN 0 1021097460 - tcp6 0 0 :::3263 :::* LISTEN 0 54080 - tcp6 0 0 :::5888 :::* LISTEN 0 247603 - tcp6 0 0 :::3264 :::* LISTEN 0 54082 - tcp6 0 0 :::3265 :::* LISTEN 0 989674843 - tcp6 0 0 :::2049 :::* LISTEN 0 53275 - tcp6 0 0 :::6690 :::* LISTEN 0 150085 - tcp6 0 0 :::9443 :::* LISTEN 0 824943312 - tcp6 0 0 :::23080 :::* LISTEN 0 202410 - tcp6 0 0 :::5000 :::* LISTEN 0 47359 - tcp6 0 0 :::5000 :::* LISTEN 0 47358 - tcp6 0 0 :::5000 :::* LISTEN 0 47357 - tcp6 0 0 :::5000 :::* LISTEN 0 47347 - udp 0 0 0.0.0.0:111 0.0.0.0:* 0 24793 - udp 0 0 0.0.0.0:123 0.0.0.0:* 0 37719 - udp 0 0 192.168.178.255:137 0.0.0.0:* 0 1024636905 - udp 0 0 192.168.178.70:137 0.0.0.0:* 0 1024636904 - udp 0 0 0.0.0.0:137 0.0.0.0:* 0 1024636840 - udp 0 0 192.168.178.255:138 0.0.0.0:* 0 1024636907 - udp 0 0 192.168.178.70:138 0.0.0.0:* 0 1024636906 - udp 0 0 0.0.0.0:138 0.0.0.0:* 0 1024636841 - udp 0 0 127.0.0.1:161 0.0.0.0:* 0 41248 - udp 0 0 127.0.0.1:323 0.0.0.0:* 0 37717 - udp 0 0 192.168.178.70:500 0.0.0.0:* 0 129298 - udp 0 0 127.0.0.1:626 0.0.0.0:* 0 37816 - udp 0 0 0.0.0.0:662 0.0.0.0:* 0 40190 - udp 0 0 0.0.0.0:41779 0.0.0.0:* 0 1019960907 - udp 0 0 0.0.0.0:892 0.0.0.0:* 0 39164 - udp 0 0 192.168.178.70:1701 0.0.0.0:* 0 125536 - udp 0 0 0.0.0.0:9997 0.0.0.0:* 0 27285 - udp 0 0 0.0.0.0:9998 0.0.0.0:* 0 27284 - udp 0 0 0.0.0.0:9999 0.0.0.0:* 0 27283 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 243812 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 92706 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 254178 92151 - udp 0 0 0.0.0.0:2049 0.0.0.0:* 0 53274 - udp 0 0 127.0.0.1:35108 0.0.0.0:* 254178 92149 - udp 0 0 127.0.0.1:43807 0.0.0.0:* 0 92704 - udp 0 0 0.0.0.0:43930 0.0.0.0:* 1000 1021092392 - udp 0 0 0.0.0.0:52642 0.0.0.0:* 0 914611939 - udp 0 0 0.0.0.0:19996 0.0.0.0:* 233155 102485 - udp 0 0 0.0.0.0:19997 0.0.0.0:* 233155 102484 - udp 0 0 0.0.0.0:19998 0.0.0.0:* 233155 102483 - udp 0 0 0.0.0.0:3702 0.0.0.0:* 99 225978 - udp 0 0 0.0.0.0:4045 0.0.0.0:* 0 53284 - udp 0 0 192.168.178.70:4500 0.0.0.0:* 0 129299 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 1021109873 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 0 914611937 - udp 0 0 0.0.0.0:54983 0.0.0.0:* 0 24794 - udp 0 0 0.0.0.0:55443 0.0.0.0:* 1000 1021094364 - udp 0 0 127.0.0.1:31067 0.0.0.0:* 0 128719 - udp 0 0 127.0.0.1:31068 0.0.0.0:* 0 128720 - udp 0 0 192.168.178.70:55900 0.0.0.0:* 254178 92150 - udp 0 0 192.168.178.70:55901 0.0.0.0:* 0 92705 - udp6 0 0 :::57209 :::* 0 24797 - udp6 0 0 :::111 :::* 0 24796 - udp6 0 0 :::123 :::* 0 37720 - udp6 0 0 ::1:323 :::* 0 37718 - udp6 0 0 fe80::211:32ff:fec5:546 :::* 0 387459 - udp6 0 0 :::662 :::* 0 40194 - udp6 0 0 :::892 :::* 0 39168 - udp6 0 0 :::2049 :::* 0 53276 - udp6 0 0 :::3702 :::* 99 225981 - udp6 0 0 :::4045 :::* 0 53286 - udp6 0 0 :::5353 :::* 0 914611938 - udp6 0 0 :::47739 :::* 0 914611940 - *** Log File - Last 25 Lines *** 2025-09-13 16:05:27.775 - error: shelly.0 (679) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-d4d4daedddb0" 2025-09-13 16:05:40.023 - info: host.ioBroker instance system.adapter.netatmo-crawler.0 in version "1.0.0" started with pid 21227 2025-09-13 16:05:42.531 - info: netatmo-crawler.0 (21227) starting. Version 1.0.0 in /opt/iobroker/node_modules/iobroker.netatmo-crawler, node: v22.19.0, js-controller: 6.0.11 2025-09-13 16:05:42.583 - info: netatmo-crawler.0 (21227) Getting data for stationid:70:ee:50:03:e0:ea 2025-09-13 16:05:44.349 - info: netatmo-crawler.0 (21227) Terminated (NO_ERROR): Everything done. Going to terminate till next schedule 2025-09-13 16:05:44.885 - info: host.ioBroker instance system.adapter.netatmo-crawler.0 having pid 21227 terminated with code 0 (NO_ERROR) 2025-09-13 16:06:20.343 - info: shelly.0 (679) [MQTT] Device with client id "shellyplusplugs-d4d4daedddb0" connected from 10.10.30.141! 2025-09-13 16:06:30.352 - info: shelly.0 (679) [MQTT] Client Close: 10.10.30.141 (shellyplusplugs / shellyplusplugs-d4d4daedddb0 / shellyplusplugs#d4d4daedddb0#1) (false) 2025-09-13 16:06:37.367 - error: shelly.0 (679) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for client undefined: TypeError: Cannot read properties of undefined (reading 'repla ce') 2025-09-13 16:06:37.368 - error: shelly.0 (679) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-d4d4daedddb0" 2025-09-13 16:07:04.339 - info: web.0 (774) ==> Connected system.user.admin from ::ffff:192.168.178.32 2025-09-13 16:07:05.187 - info: web.0 (774) ==> Connected system.user.admin from ::ffff:192.168.178.32 2025-09-13 16:07:25.485 - info: shelly.0 (679) [MQTT] Device with client id "shellyplusplugs-d4d4daedddb0" connected from 10.10.30.141! 2025-09-13 16:07:35.479 - info: shelly.0 (679) [MQTT] Client Close: 10.10.30.141 (shellyplusplugs / shellyplusplugs-d4d4daedddb0 / shellyplusplugs#d4d4daedddb0#1) (false) 2025-09-13 16:07:36.276 - error: shelly.0 (679) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for client undefined: TypeError: Cannot read properties of undefined (reading 'repla ce') 2025-09-13 16:07:36.277 - error: shelly.0 (679) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-d4d4daedddb0" 2025-09-13 16:08:31.087 - info: shelly.0 (679) [MQTT] Device with client id "shellyplusplugs-d4d4daedddb0" connected from 10.10.30.141! 2025-09-13 16:08:41.065 - info: shelly.0 (679) [MQTT] Client Close: 10.10.30.141 (shellyplusplugs / shellyplusplugs-d4d4daedddb0 / shellyplusplugs#d4d4daedddb0#1) (false) 2025-09-13 16:08:41.206 - error: shelly.0 (679) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for client undefined: TypeError: Cannot read properties of undefined (reading 'repla ce') 2025-09-13 16:08:41.206 - error: shelly.0 (679) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-d4d4daedddb0" 2025-09-13 16:09:34.363 - info: web.0 (774) <== Disconnect system.user.admin from ::ffff:192.168.178.32 vis.0 2025-09-13 16:09:38.273 - info: shelly.0 (679) [MQTT] Device with client id "shellyplusplugs-d4d4daedddb0" connected from 10.10.30.141! 2025-09-13 16:09:48.264 - info: shelly.0 (679) [MQTT] Client Close: 10.10.30.141 (shellyplusplugs / shellyplusplugs-d4d4daedddb0 / shellyplusplugs#d4d4daedddb0#1) (false) 2025-09-13 16:09:55.928 - error: shelly.0 (679) [MQTT] Error in function setMqttPrefixHttp (Gen 1) for client undefined: TypeError: Cannot read properties of undefined (reading 'repla ce') 2025-09-13 16:09:55.928 - error: shelly.0 (679) [MQTT] Unable to get mqttprefix of client with id "shellyplusplugs-d4d4daedddb0" ============ Mark until here for C&P ============= iob diag has finished. -
@rj3n53n sagte in Kein Admin nach Update:
Ich muss den Beitrag teilen.
Nein, musst du nicht.
Die Ausgabe passt normalerweise in Gänze in ein Posting rein. -
Sorry, hat einen Moment gedauert.
Ich muss den Beitrag teilen.========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64 bit Docker : v11.0.0 Virtualization : docker Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:09:33 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Sep 13 14:09:33 UTC 2025 Sat Sep 13 16:09:33 CEST 2025 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker sudo: unable to resolve host ioBroker: Name or service not known HOME=/opt/iobroker sudo: unable to resolve host ioBroker: Name or service not known GROUPS=iobroker tty dialout audio video plugdev *** DISPLAY-SERVER SETUP *** Display-Server: false System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 859M 208M 10G 10G Swap: 12G 996M 11G Total: 28G 6.9G 11G Active iob-Instances: 32 15854 M total memory 5585 M used memory 6429 M active memory 6748 M inactive memory 819 M free memory 658 M buffer memory 9395 M swap cache 11563 M total swap 950 M used swap 10613 M free swap *** top - Table Of Processes *** top - 16:09:34 up 45 days, 11:50, 0 user, load average: 2.51, 1.98, 2.03 Tasks: 40 total, 1 running, 39 sleeping, 0 stopped, 0 zombie %Cpu(s): 50.0 us, 0.0 sy, 0.0 ni, 50.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 15854.0 total, 819.9 free, 5584.7 used, 10054.0 buff/cache MiB Swap: 11563.9 total, 10613.5 free, 950.5 used. 10269.3 avail Mem *** DMESG CRITICAL ERRORS *** sudo: unable to resolve host ioBroker: Name or service not known No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 13T 1.4T 12T 11% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/mapper/cachedev_0 ext4 13T 1.4T 12T 11% /opt/iobroker tmpfs tmpfs 7.8G 0 7.8G 0% /proc/acpi tmpfs tmpfs 7.8G 0 7.8G 0% /proc/scsi tmpfs tmpfs 7.8G 0 7.8G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: sudo: unable to resolve host ioBroker: Name or service not known Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=faf9736b0331140a,dio,d irperm1 |-/opt/iobroker /dev/mapper/cachedev_0[/docker/ioBroker_mount] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/resolv.conf] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hostname] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/mapper/cachedev_0[/@docker/containers/d3241ec779e3b13b8c77eab6b9b4347d110de1b7dfaa04ae33ac8b9de0fa5daf/hosts] ext4 rw,nodev,relatime,synoacl,jqfmt=vfsv0 ,usrjquota=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: sudo: unable to resolve host ioBroker: Name or service not known 35M /var/ 33M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 14M /var/lib/dpkg /opt/iobroker/backups: 12K /opt/iobroker/backups/ 8.0K /opt/iobroker/backups/@eaDir /opt/iobroker/iobroker-data: 662M /opt/iobroker/iobroker-data/ 423M /opt/iobroker/iobroker-data/files 177M /opt/iobroker/iobroker-data/backup-objects 73M /opt/iobroker/iobroker-data/files/vis-2 56M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 38M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.d3d286bd.js.map 30M /opt/iobroker/iobroker-data/objects.jsonl 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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' Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.19.0 /usr/bin/node v22.19.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.19.0-1nodesource1 Candidate: 22.19.0-1nodesource1 Version table: *** 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host ioBroker: Name or service not known sudo: unable to resolve host ioBroker: Name or service not known █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██@rj3n53n sagte in Kein Admin nach Update:
Failed to connect to bus: Host is down
-
Adapter "admin" : 7.7.2 , installed 3.7.9 [Updatable]Damit kommste halt nicht mehr weit...
Dringendst alles updaten. Inkl. js-controller usw. -
Adapter "admin" : 7.7.2 , installed 3.7.9 [Updatable]Damit kommste halt nicht mehr weit...
Dringendst alles updaten. Inkl. js-controller usw. -
Ich hatte eigentlich regelmäßige Updates gemacht, wenn sie angezeigt wurden.
Kann man das jetzt noch glattziehen?@rj3n53n sagte in Kein Admin nach Update:
Kann man das jetzt noch glattziehen?
Bestimmt. Aber bei Docker hab ich keine Aktien.
-
@rj3n53n sagte in Kein Admin nach Update:
Kann man das jetzt noch glattziehen?
Bestimmt. Aber bei Docker hab ich keine Aktien.
Im Container Manager hatte ich zeitnah jedes Update gemacht, wenn es angezeigt wurde.
Hab aber trotzdem vielen Dank für Deine Hilfe. -
@rj3n53n sagte in Kein Admin nach Update:
Failed to connect to bus: Host is down
-
@rj3n53n sagte in Kein Admin nach Update:
Wie kann ich das ändern?
keine Ahnung!
mit Containern kenne ich mich nicht aus, mit Docker schon gar nicht.Wenn das eine native Installation wäre würde ich versuchen in kleinen Schritten die Versionen hochzubringen.
Ob man das bei Docker darf weiss ich nicht.
Ob die nötigen Versionen überhaupt noch verfügbar sind weiß ich auch nicht.Wenn das eine native Installation wäre, würde ich zu einer Neuinstallation mit anschließendem wiederherstellen des letzten Backups taten.
Ob und wie das bei Docker geht entzieht sich meiner Kenntnis -
@rj3n53n sagte in Kein Admin nach Update:
Wie kann ich das ändern?
keine Ahnung!
mit Containern kenne ich mich nicht aus, mit Docker schon gar nicht.Wenn das eine native Installation wäre würde ich versuchen in kleinen Schritten die Versionen hochzubringen.
Ob man das bei Docker darf weiss ich nicht.
Ob die nötigen Versionen überhaupt noch verfügbar sind weiß ich auch nicht.Wenn das eine native Installation wäre, würde ich zu einer Neuinstallation mit anschließendem wiederherstellen des letzten Backups taten.
Ob und wie das bei Docker geht entzieht sich meiner Kenntnis -
Sind alle benötigten Container-Ports gemappt?
Läuft da 'ne Firewall?Ich empfehle außerdem, das Ganze auf ein "Projekt" zu migrieren. Das lässt sich deutlich einfacher administrieren als das Gefummel an irgendwelchen Container-Einstellungen. Und zum Update muss lediglich das Projekt neu gestsartet werden.
Siehe hier: https://forum.iobroker.net/topic/82045/installtion-ffmpeg/6?_=1757840464651"Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")
Proxmox 9.1.1 LXC|8 GB|Core i7-6700
HmIP|ZigBee|Tasmota|Unifi
Zabbix Certified Specialist
Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag -
Sind alle benötigten Container-Ports gemappt?
Läuft da 'ne Firewall?Ich empfehle außerdem, das Ganze auf ein "Projekt" zu migrieren. Das lässt sich deutlich einfacher administrieren als das Gefummel an irgendwelchen Container-Einstellungen. Und zum Update muss lediglich das Projekt neu gestsartet werden.
Siehe hier: https://forum.iobroker.net/topic/82045/installtion-ffmpeg/6?_=1757840464651@codierknecht sagte in Kein Admin nach Update:
Sind alle benötigten Ports nach außen freigegeben?
@RJ3n53n
bitte nicht missverstehen!!nicht ins Internet, nur aus dem/in den Container weitergeleitet
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@codierknecht sagte in Kein Admin nach Update:
Sind alle benötigten Ports nach außen freigegeben?
@RJ3n53n
bitte nicht missverstehen!!nicht ins Internet, nur aus dem/in den Container weitergeleitet
@homoran
Danke für den Hinweis. Hab's korrigiert.
Nicht dass da jemand auf komische Ideen kommt ;-) -
An den Ports habe ich nichts geändert. Bisher hatte es ja funktioniert.
Ich schaue mir gerade mal den Link an, den Du angehängt hast. Ich weiß gerade nicht, wie Du das mit ein Projekt meinst.
Vielen Dank aber schon mal für den Tipp sowie den Link. -
An den Ports habe ich nichts geändert. Bisher hatte es ja funktioniert.
Ich schaue mir gerade mal den Link an, den Du angehängt hast. Ich weiß gerade nicht, wie Du das mit ein Projekt meinst.
Vielen Dank aber schon mal für den Tipp sowie den Link.@rj3n53n sagte in Kein Admin nach Update:
Ich weiß gerade nicht, wie Du das mit ein Projekt meinst
Ich vermute mal: Du hast das bislang über den Container-Manager als Container aufgesetzt.
Dann muss man den ganzen Kram "von Hand" passend einstellen. Volumes, Ports, Variablen etc.Man kann das im Container-Manager auch als "Projekt" aufsetzen. Dann wird die komplette Konfiguration in einer YAML-Datei abgelegt. In Docker nennt sich das "Compose" und in Portainer "Stacks". Ist aber alles das gleiche.
Als Quelle wählst Du "docker-compose.yml erstellen" und fügst dann den folgenden Inhalt in den Editor ein.
Ein grundlegendesdocker-compose.ymlfür ioBroker könnte so aussehen:services: iobroker: container_name: ioBroker image: buanet/iobroker:latest hostname: iobroker network_mode: "host" volumes: - /volume1/Docker/ioBroker:/opt/iobroker environment: PACKAGES: "nano" AVAHI: "true" restart: unless-stoppedMuss halt ggf. etwas an die eigenen Gegebenheiten angepasst werden.
Man beachte hier: Der Container läuft als "host". Man muss also keine Ports speziell mappen.
Könnte allerding schiefgehen, wenn auf der Synology noch ander Dienste (WebStation, Fotos usw.) laufen, die Ports beanspruchen die auch vom ioBroker verwendet werden. -
@rj3n53n sagte in Kein Admin nach Update:
Ich weiß gerade nicht, wie Du das mit ein Projekt meinst
Ich vermute mal: Du hast das bislang über den Container-Manager als Container aufgesetzt.
Dann muss man den ganzen Kram "von Hand" passend einstellen. Volumes, Ports, Variablen etc.Man kann das im Container-Manager auch als "Projekt" aufsetzen. Dann wird die komplette Konfiguration in einer YAML-Datei abgelegt. In Docker nennt sich das "Compose" und in Portainer "Stacks". Ist aber alles das gleiche.
Als Quelle wählst Du "docker-compose.yml erstellen" und fügst dann den folgenden Inhalt in den Editor ein.
Ein grundlegendesdocker-compose.ymlfür ioBroker könnte so aussehen:services: iobroker: container_name: ioBroker image: buanet/iobroker:latest hostname: iobroker network_mode: "host" volumes: - /volume1/Docker/ioBroker:/opt/iobroker environment: PACKAGES: "nano" AVAHI: "true" restart: unless-stoppedMuss halt ggf. etwas an die eigenen Gegebenheiten angepasst werden.
Man beachte hier: Der Container läuft als "host". Man muss also keine Ports speziell mappen.
Könnte allerding schiefgehen, wenn auf der Synology noch ander Dienste (WebStation, Fotos usw.) laufen, die Ports beanspruchen die auch vom ioBroker verwendet werden.@codierknecht
Okay, jetzt weiß ich, was Du meinst. Ja, so hatte ich das gemacht. Eingerichttet hatte ich es nach einer Anleitung. Noch bevor es bei Synology Container-Manager hieß. Da war damals auch beschrieben, welche Ports ich öffnen musste. -
@codierknecht
Okay, jetzt weiß ich, was Du meinst. Ja, so hatte ich das gemacht. Eingerichttet hatte ich es nach einer Anleitung. Noch bevor es bei Synology Container-Manager hieß. Da war damals auch beschrieben, welche Ports ich öffnen musste.@rj3n53n sagte in Kein Admin nach Update:
Noch bevor es bei Synology Container-Manager hieß
Seit DSM 7 gibt's den Container-Manager und damit auch die "Projekte".
Macht das Ganze deutlich einfacher.welche Ports ich öffnen musste
Wenn der Container im Host-Mode läuft, muss man keine Ports mehr freigeben.
Solange auf der Syno nix läuft was dem Container da in die Suppe spucken kann, spart man sich die ganze Port-Litanei. -
@rj3n53n sagte in Kein Admin nach Update:
Noch bevor es bei Synology Container-Manager hieß
Seit DSM 7 gibt's den Container-Manager und damit auch die "Projekte".
Macht das Ganze deutlich einfacher.welche Ports ich öffnen musste
Wenn der Container im Host-Mode läuft, muss man keine Ports mehr freigeben.
Solange auf der Syno nix läuft was dem Container da in die Suppe spucken kann, spart man sich die ganze Port-Litanei.
Support us
592
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge