NEWS
Fehlermeldungen beim Biobroker Update
ioBroker Allgemein
37
Beiträge
4
Kommentatoren
2.8k
Aufrufe
3
Watching
-
Hallo,
mir wurde in der Facebook "iobroker SmartHome und IoT" Gruppe schon ein wenig geholfen und ich wurde darum geben hier mein Diagnose Log rein zu stellen.Vielen Dank schon mal dafür. Ich hoffe das funktioniert mit dem angehängten log File.
[3J[H[2J*** iob diag is starting up, please wait *** [3J[H[2J [34;107m*** ioBroker Diagnosis ***[0m Please stretch the window of your terminal programm (puTTY) as wide as possible or switch to full screen The following checks may give hints to potential malconfigurations or errors, please post them in our forum: https://forum.iobroker.net Just copy and paste the Summary Page, including the ``` characters at start and end. It helps us to help you! Press any key to continue [3J[H[2J [33m======== Start marking the full check here =========[0m Skript v.2023-10-25 [34;107m*** BASE SYSTEM ***[0m Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 11:59:39 up 20:43, 1 user, load average: 1.35, 1.38, 0.98 CPU threads: 4 [34;107m*** Time and Time Zones ***[0m Local time: Sat 2024-01-20 11:59:39 CET Universal time: Sat 2024-01-20 10:59:39 UTC RTC time: Sat 2024-01-20 10:59:39 Time zone: Europe/Berlin (CET, +0100) Network time on: yes NTP synchronized: yes RTC in local TZ: no [34;107m*** User and Groups ***[0m pi /home/pi pi tty disk dialout sudo audio video plugdev games users systemd-journal input netdev ssh iobroker [34;107m*** X-Server-Setup ***[0m X-Server: false Desktop: Terminal: Boot Target: graphical.target [34;107m*** MEMORY ***[0m total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 651M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G 3988 M total memory 1347 M used memory 1556 M active memory 280 M inactive memory 2004 M free memory 77 M buffer memory 559 M swap cache 1023 M total swap 0 M used swap 1023 M free swap [34;107m*** FAILED SERVICES ***[0m 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. [34;107m*** FILESYSTEM ***[0m Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.0G 0 2.0G 0% /dev tmpfs tmpfs 399M 5.4M 394M 2% /run /dev/mmcblk0p1 ext4 15G 4.8G 9.2G 34% / tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs tmpfs 2.0G 636K 2.0G 1% /tmp /dev/zram0 ext4 49M 3.9M 42M 9% /var/log tmpfs tmpfs 399M 0 399M 0% /run/user/1000 [32mMessages concerning ext4 filesystem in dmesg:[0m [Fri Jan 19 15:16:20 2024] Kernel command line: earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=aadb45fc-8b8b-4b5b-ad50-7e6416a4e1c5 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=9dd9d2a5-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [Fri Jan 19 15:16:31 2024] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 12288 [32mShow mounted filesystems:[0m TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,relatime,memory | | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/hugetlb cgroup cgroup rw,nosuid,nodev,noexec,relatime,hugetlb | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,relatime | | `-/sys/kernel/debug/tracing tracefs tracefs rw,relatime | |-/sys/kernel/config configfs configfs rw,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/dev udev devtmpfs rw,nosuid,relatime,size=2039432k,nr_inodes=509858,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/mqueue mqueue mqueue rw,relatime | `-/dev/hugepages hugetlbfs hugetlbfs rw,relatime |-/run tmpfs tmpfs rw,nosuid,noexec,relatime,size=408448k,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=408444k,mode=700,uid=1000,gid=1000 |-/tmp tmpfs tmpfs rw,nosuid,relatime |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 `-/var/log /dev/zram0 ext4 rw,relatime,discard [32mFiles in neuralgic directories:[0m [32m/var:[0m 569M /var/ 286M /var/lib 274M /var/cache 269M /var/cache/apt 266M /var/lib/apt/lists Archived and active journals take up 4.9M in the file system. [32m/opt/iobroker/backups:[0m 71M /opt/iobroker/backups/ 43M /opt/iobroker/backups/Alt [32m/opt/iobroker/iobroker-data:[0m 357M /opt/iobroker/iobroker-data/ 234M /opt/iobroker/iobroker-data/files 83M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 51M /opt/iobroker/iobroker-data/files/javascript.admin [32mThe five largest files in iobroker-data are:[0m 23M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 8.2M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js [32mUSB-Devices by-id:[0m USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': [34;107m*** NodeJS-Installation ***[0m /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 nodejs: Installed: 14.21.3-1nodesource1 Candidate: 14.21.3-1nodesource1 Version table: *** 14.21.3-1nodesource1 500 500 https://deb.nodesource.com/node_14.x stretch/main arm64 Packages 100 /var/lib/dpkg/status 8.11.1~dfsg-2~bpo9+1 100 100 http://httpredir.debian.org/debian stretch-backports/main arm64 Packages 4.8.2~dfsg-1 500 500 http://httpredir.debian.org/debian stretch/main arm64 Packages [32mTemp directories causing npm8 problem:[0m 0 No problems detected Errors in npm tree: [34;107m*** ioBroker-Installation ***[0m [32mioBroker Status[0m iobroker is running on this host. Objects type: jsonl States type: jsonl [32mCore adapters versions[0m js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 Adapters from github: 3 [32mAdapter State[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : rock64 - disabled + system.adapter.bluelink.0 : bluelink : rock64 - enabled + system.adapter.discovery.0 : discovery : rock64 - enabled system.adapter.fronius.0 : fronius : rock64 - disabled + system.adapter.fronius.1 : fronius : rock64 - enabled + system.adapter.history.0 : history : rock64 - enabled + system.adapter.hm-rega.0 : hm-rega : rock64 - enabled + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.info.0 : info : rock64 - enabled + system.adapter.iot.0 : iot : rock64 - enabled + system.adapter.javascript.0 : javascript : rock64 - enabled system.adapter.midea.0 : midea : rock64 - disabled + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.pushover.0 : pushover : rock64 - enabled + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : rock64 - enabled + system.adapter.tr-064.0 : tr-064 : rock64 - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : rock64 - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : rock64 - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : rock64 - enabled system.adapter.vis.0 : vis : rock64 - enabled + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : rock64 - enabled + system.adapter.yahka.1 : yahka : rock64 - enabled + instance is alive [32mEnabled adapters with bindings[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin [32mioBroker-Repositories[0m stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable [32mInstalled ioBroker-Instances[0m Used repository: stable Adapter "admin" : 6.12.0 , installed 6.3.5 [Updatable] Adapter "backitup" : 2.9.8 , installed 2.8.1 [Updatable] Adapter "bluelink" : 2.3.6 , installed 2.3.2 [Updatable] Adapter "discovery" : 4.2.0 , installed 3.1.0 [Updatable] Adapter "fronius" : 2.0.2 , installed 2.0.2 Adapter "history" : 3.0.1 , installed 2.2.4 [Updatable] Adapter "hm-rega" : 4.0.0 , installed 3.0.46 [Updatable] Adapter "hm-rpc" : 1.15.19 , installed 1.15.16 [Updatable] Adapter "hue" : 3.10.1 , installed 3.7.1 [Updatable] Adapter "info" : 2.0.0 , installed 1.9.26 [Updatable] Adapter "iot" : 2.0.11 , installed 1.14.5 [Updatable] Adapter "javascript" : 7.1.6 , installed 6.1.4 [Updatable] Controller "js-controller": 5.0.17 , installed 4.0.24 [Updatable] Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "pushover" : 3.0.6 , installed 3.0.3 [Updatable] Adapter "shelly" : 6.6.1 , installed 6.4.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 4.2.0 [Updatable] Adapter "telegram" : 3.0.1 , installed 1.15.6 [Updatable] Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.1.10 , installed 4.3.0 [Updatable] Adapter "worx" : 2.3.4 , installed 2.3.2 [Updatable] Adapter "ws" : 2.5.8 , installed 1.3.0 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 [32mObjects and States[0m Please stand by - This may take a while Objects: 5463 States: 3094 [34;107m*** OS-Repositories and Updates ***[0m Pending Updates: 136 [34;107m*** Listening Ports ***[0m Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port udp UNCONN 0 0 *:9898 *:* users:(("io.mihome.0",pid=1750,fd=27)) udp UNCONN 0 0 *:68 *:* users:(("dhclient",pid=906,fd=6)) udp UNCONN 0 0 *:111 *:* users:(("rpcbind",pid=443,fd=6)) udp UNCONN 0 0 192.168.0.176:123 *:* users:(("ntpd",pid=1481,fd=19)) udp UNCONN 0 0 127.0.0.1:123 *:* users:(("ntpd",pid=1481,fd=18)) udp UNCONN 0 0 *:123 *:* users:(("ntpd",pid=1481,fd=17)) udp UNCONN 0 0 *:619 *:* users:(("rpcbind",pid=443,fd=7)) udp UNCONN 0 0 *:5353 *:* users:(("io.yahka.1",pid=2294,fd=27)) udp UNCONN 0 0 :::111 :::* users:(("rpcbind",pid=443,fd=9)) udp UNCONN 0 0 fdad:a636:5c1e:ff4d:8907:c27d:dc5a:3529:123 :::* users:(("ntpd",pid=1481,fd=25)) udp UNCONN 0 0 fe80::f777:1c02:d801:d955%eth0:123 :::* users:(("ntpd",pid=1481,fd=21)) udp UNCONN 0 0 ::1:123 :::* users:(("ntpd",pid=1481,fd=20)) udp UNCONN 0 0 :::123 :::* users:(("ntpd",pid=1481,fd=16)) udp UNCONN 0 0 :::619 :::* users:(("rpcbind",pid=443,fd=10)) tcp LISTEN 0 128 127.0.0.1:9000 *:* users:(("iobroker.js-con",pid=838,fd=26)) tcp LISTEN 0 128 127.0.0.1:9001 *:* users:(("iobroker.js-con",pid=838,fd=20)) tcp LISTEN 0 128 *:111 *:* users:(("rpcbind",pid=443,fd=8)) tcp LISTEN 0 128 192.168.0.176:2001 *:* users:(("io.hm-rpc.0",pid=1684,fd=27)) tcp LISTEN 0 128 127.0.0.1:42836 *:* users:(("io.yahka.1",pid=2294,fd=30)) tcp LISTEN 0 128 *:22 *:* users:(("sshd",pid=857,fd=3)) tcp LISTEN 0 128 192.168.0.176:1882 *:* users:(("io.shelly.0",pid=1781,fd=27)) tcp LISTEN 0 128 192.168.0.176:2010 *:* users:(("io.hm-rpc.1",pid=1712,fd=27)) tcp LISTEN 0 128 :::40972 :::* users:(("io.yahka.1",pid=2294,fd=26)) tcp LISTEN 0 128 :::111 :::* users:(("rpcbind",pid=443,fd=11)) tcp LISTEN 0 128 :::8081 :::* users:(("io.admin.0",pid=1489,fd=27)) tcp LISTEN 0 128 :::8082 :::* users:(("io.web.0",pid=1856,fd=27)) tcp LISTEN 0 128 :::22 :::* users:(("sshd",pid=857,fd=4)) [34;107m*** Log File - Last 25 Lines ***[0m 2024-01-20 12:00:44.991 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.58" greater than max "100" 2024-01-20 12:00:47.513 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:47.845 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:51.499 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:57.801 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:58.422 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:02.168 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.258 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.972 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:13.540 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:14.954 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.47" greater than max "100" 2024-01-20 12:01:18.555 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:19.303 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:20.258 - [32minfo[39m: admin.0 (1489) <== Disconnect system.user.admin from ::ffff:192.168.0.100 admin 2024-01-20 12:01:25.247 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.139 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.794 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:35.888 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:38.567 - [31merror[39m: shelly.0 (1781) [MQTT] (Shelly?) device unknown, configuration for client with id "shellypmmini-543204a97f50" does not exist! 2024-01-20 12:01:38.568 - [31merror[39m: shelly.0 (1781) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2024-01-20 12:01:38.605 - [32minfo[39m: shelly.0 (1781) [MQTT] Client Close: (shellypmmini / shellypmmini-543204a97f50 / undefined) (false) 2024-01-20 12:01:39.697 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:40.202 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:44.922 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.12" greater than max "100" 2024-01-20 12:01:46.455 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) [33m============ Mark until here for C&P =============[0m iob diag has finished. Press any key for a summary [3J[H[2JCopy text starting here: ======================= SUMMARY ======================= v.2023-10-25 Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: rlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 136 Pending iob updates: 20 Nodejs-Installation: /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 Recommended versions are nodejs 16.20.2 and npm 8.19.4 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 653M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G Active iob-Instances: 22 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 5463 States: 3094 Size of iob-Database: 23M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/objects.json.migrated 6.3M /opt/iobroker/iobroker-data/objects.json.bak.migrated 3.8M /opt/iobroker/iobroker-data/states.jsonl 1000K /opt/iobroker/iobroker-data/states.json.migrated 1000K /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== === Mark text until here for copying ===Mein Versionen:
pi@rock64:~$ type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
v14.21.3
v14.21.3
6.14.18
6.14.18Mein iobroker läuft sehr gut und stabil (backitup Adapter ausgenommen) ich kann nur einige wichtige Adapter nicht mehr updaten (u.a. Shelly) weil meine Versionen zu alt sind. Beim Updaten kommen dann diverse npm Fehlermeldungen.
Meine Idee war jetzt erstmal ein backup zu ziehen, ein neues System auf dem neuesten Stand aufzusetzen und das Backup wieder einzuspielen.
Achso, das ganze läuft auf einem ROCK64.
Danke an Thomas Braun. Das Diagnose Tool ist mega gut!!
Gruß Andy
Da ist aber auch alles hoffnungslos veraltet...
Debian 9 'Stretch'...
Mittlerweile sind wir bei 12 und 10 ist auch bereits tot, 11 ist im Auslauf...Versuch mal:
iob stop iob fix iob nodejs-update 16 -
Hallo,
mir wurde in der Facebook "iobroker SmartHome und IoT" Gruppe schon ein wenig geholfen und ich wurde darum geben hier mein Diagnose Log rein zu stellen.Vielen Dank schon mal dafür. Ich hoffe das funktioniert mit dem angehängten log File.
[3J[H[2J*** iob diag is starting up, please wait *** [3J[H[2J [34;107m*** ioBroker Diagnosis ***[0m Please stretch the window of your terminal programm (puTTY) as wide as possible or switch to full screen The following checks may give hints to potential malconfigurations or errors, please post them in our forum: https://forum.iobroker.net Just copy and paste the Summary Page, including the ``` characters at start and end. It helps us to help you! Press any key to continue [3J[H[2J [33m======== Start marking the full check here =========[0m Skript v.2023-10-25 [34;107m*** BASE SYSTEM ***[0m Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 11:59:39 up 20:43, 1 user, load average: 1.35, 1.38, 0.98 CPU threads: 4 [34;107m*** Time and Time Zones ***[0m Local time: Sat 2024-01-20 11:59:39 CET Universal time: Sat 2024-01-20 10:59:39 UTC RTC time: Sat 2024-01-20 10:59:39 Time zone: Europe/Berlin (CET, +0100) Network time on: yes NTP synchronized: yes RTC in local TZ: no [34;107m*** User and Groups ***[0m pi /home/pi pi tty disk dialout sudo audio video plugdev games users systemd-journal input netdev ssh iobroker [34;107m*** X-Server-Setup ***[0m X-Server: false Desktop: Terminal: Boot Target: graphical.target [34;107m*** MEMORY ***[0m total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 651M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G 3988 M total memory 1347 M used memory 1556 M active memory 280 M inactive memory 2004 M free memory 77 M buffer memory 559 M swap cache 1023 M total swap 0 M used swap 1023 M free swap [34;107m*** FAILED SERVICES ***[0m 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. [34;107m*** FILESYSTEM ***[0m Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.0G 0 2.0G 0% /dev tmpfs tmpfs 399M 5.4M 394M 2% /run /dev/mmcblk0p1 ext4 15G 4.8G 9.2G 34% / tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs tmpfs 2.0G 636K 2.0G 1% /tmp /dev/zram0 ext4 49M 3.9M 42M 9% /var/log tmpfs tmpfs 399M 0 399M 0% /run/user/1000 [32mMessages concerning ext4 filesystem in dmesg:[0m [Fri Jan 19 15:16:20 2024] Kernel command line: earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=aadb45fc-8b8b-4b5b-ad50-7e6416a4e1c5 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=9dd9d2a5-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [Fri Jan 19 15:16:31 2024] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 12288 [32mShow mounted filesystems:[0m TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,relatime,memory | | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/hugetlb cgroup cgroup rw,nosuid,nodev,noexec,relatime,hugetlb | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,relatime | | `-/sys/kernel/debug/tracing tracefs tracefs rw,relatime | |-/sys/kernel/config configfs configfs rw,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/dev udev devtmpfs rw,nosuid,relatime,size=2039432k,nr_inodes=509858,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/mqueue mqueue mqueue rw,relatime | `-/dev/hugepages hugetlbfs hugetlbfs rw,relatime |-/run tmpfs tmpfs rw,nosuid,noexec,relatime,size=408448k,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=408444k,mode=700,uid=1000,gid=1000 |-/tmp tmpfs tmpfs rw,nosuid,relatime |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 `-/var/log /dev/zram0 ext4 rw,relatime,discard [32mFiles in neuralgic directories:[0m [32m/var:[0m 569M /var/ 286M /var/lib 274M /var/cache 269M /var/cache/apt 266M /var/lib/apt/lists Archived and active journals take up 4.9M in the file system. [32m/opt/iobroker/backups:[0m 71M /opt/iobroker/backups/ 43M /opt/iobroker/backups/Alt [32m/opt/iobroker/iobroker-data:[0m 357M /opt/iobroker/iobroker-data/ 234M /opt/iobroker/iobroker-data/files 83M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 51M /opt/iobroker/iobroker-data/files/javascript.admin [32mThe five largest files in iobroker-data are:[0m 23M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 8.2M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js [32mUSB-Devices by-id:[0m USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': [34;107m*** NodeJS-Installation ***[0m /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 nodejs: Installed: 14.21.3-1nodesource1 Candidate: 14.21.3-1nodesource1 Version table: *** 14.21.3-1nodesource1 500 500 https://deb.nodesource.com/node_14.x stretch/main arm64 Packages 100 /var/lib/dpkg/status 8.11.1~dfsg-2~bpo9+1 100 100 http://httpredir.debian.org/debian stretch-backports/main arm64 Packages 4.8.2~dfsg-1 500 500 http://httpredir.debian.org/debian stretch/main arm64 Packages [32mTemp directories causing npm8 problem:[0m 0 No problems detected Errors in npm tree: [34;107m*** ioBroker-Installation ***[0m [32mioBroker Status[0m iobroker is running on this host. Objects type: jsonl States type: jsonl [32mCore adapters versions[0m js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 Adapters from github: 3 [32mAdapter State[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : rock64 - disabled + system.adapter.bluelink.0 : bluelink : rock64 - enabled + system.adapter.discovery.0 : discovery : rock64 - enabled system.adapter.fronius.0 : fronius : rock64 - disabled + system.adapter.fronius.1 : fronius : rock64 - enabled + system.adapter.history.0 : history : rock64 - enabled + system.adapter.hm-rega.0 : hm-rega : rock64 - enabled + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.info.0 : info : rock64 - enabled + system.adapter.iot.0 : iot : rock64 - enabled + system.adapter.javascript.0 : javascript : rock64 - enabled system.adapter.midea.0 : midea : rock64 - disabled + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.pushover.0 : pushover : rock64 - enabled + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : rock64 - enabled + system.adapter.tr-064.0 : tr-064 : rock64 - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : rock64 - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : rock64 - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : rock64 - enabled system.adapter.vis.0 : vis : rock64 - enabled + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : rock64 - enabled + system.adapter.yahka.1 : yahka : rock64 - enabled + instance is alive [32mEnabled adapters with bindings[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin [32mioBroker-Repositories[0m stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable [32mInstalled ioBroker-Instances[0m Used repository: stable Adapter "admin" : 6.12.0 , installed 6.3.5 [Updatable] Adapter "backitup" : 2.9.8 , installed 2.8.1 [Updatable] Adapter "bluelink" : 2.3.6 , installed 2.3.2 [Updatable] Adapter "discovery" : 4.2.0 , installed 3.1.0 [Updatable] Adapter "fronius" : 2.0.2 , installed 2.0.2 Adapter "history" : 3.0.1 , installed 2.2.4 [Updatable] Adapter "hm-rega" : 4.0.0 , installed 3.0.46 [Updatable] Adapter "hm-rpc" : 1.15.19 , installed 1.15.16 [Updatable] Adapter "hue" : 3.10.1 , installed 3.7.1 [Updatable] Adapter "info" : 2.0.0 , installed 1.9.26 [Updatable] Adapter "iot" : 2.0.11 , installed 1.14.5 [Updatable] Adapter "javascript" : 7.1.6 , installed 6.1.4 [Updatable] Controller "js-controller": 5.0.17 , installed 4.0.24 [Updatable] Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "pushover" : 3.0.6 , installed 3.0.3 [Updatable] Adapter "shelly" : 6.6.1 , installed 6.4.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 4.2.0 [Updatable] Adapter "telegram" : 3.0.1 , installed 1.15.6 [Updatable] Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.1.10 , installed 4.3.0 [Updatable] Adapter "worx" : 2.3.4 , installed 2.3.2 [Updatable] Adapter "ws" : 2.5.8 , installed 1.3.0 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 [32mObjects and States[0m Please stand by - This may take a while Objects: 5463 States: 3094 [34;107m*** OS-Repositories and Updates ***[0m Pending Updates: 136 [34;107m*** Listening Ports ***[0m Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port udp UNCONN 0 0 *:9898 *:* users:(("io.mihome.0",pid=1750,fd=27)) udp UNCONN 0 0 *:68 *:* users:(("dhclient",pid=906,fd=6)) udp UNCONN 0 0 *:111 *:* users:(("rpcbind",pid=443,fd=6)) udp UNCONN 0 0 192.168.0.176:123 *:* users:(("ntpd",pid=1481,fd=19)) udp UNCONN 0 0 127.0.0.1:123 *:* users:(("ntpd",pid=1481,fd=18)) udp UNCONN 0 0 *:123 *:* users:(("ntpd",pid=1481,fd=17)) udp UNCONN 0 0 *:619 *:* users:(("rpcbind",pid=443,fd=7)) udp UNCONN 0 0 *:5353 *:* users:(("io.yahka.1",pid=2294,fd=27)) udp UNCONN 0 0 :::111 :::* users:(("rpcbind",pid=443,fd=9)) udp UNCONN 0 0 fdad:a636:5c1e:ff4d:8907:c27d:dc5a:3529:123 :::* users:(("ntpd",pid=1481,fd=25)) udp UNCONN 0 0 fe80::f777:1c02:d801:d955%eth0:123 :::* users:(("ntpd",pid=1481,fd=21)) udp UNCONN 0 0 ::1:123 :::* users:(("ntpd",pid=1481,fd=20)) udp UNCONN 0 0 :::123 :::* users:(("ntpd",pid=1481,fd=16)) udp UNCONN 0 0 :::619 :::* users:(("rpcbind",pid=443,fd=10)) tcp LISTEN 0 128 127.0.0.1:9000 *:* users:(("iobroker.js-con",pid=838,fd=26)) tcp LISTEN 0 128 127.0.0.1:9001 *:* users:(("iobroker.js-con",pid=838,fd=20)) tcp LISTEN 0 128 *:111 *:* users:(("rpcbind",pid=443,fd=8)) tcp LISTEN 0 128 192.168.0.176:2001 *:* users:(("io.hm-rpc.0",pid=1684,fd=27)) tcp LISTEN 0 128 127.0.0.1:42836 *:* users:(("io.yahka.1",pid=2294,fd=30)) tcp LISTEN 0 128 *:22 *:* users:(("sshd",pid=857,fd=3)) tcp LISTEN 0 128 192.168.0.176:1882 *:* users:(("io.shelly.0",pid=1781,fd=27)) tcp LISTEN 0 128 192.168.0.176:2010 *:* users:(("io.hm-rpc.1",pid=1712,fd=27)) tcp LISTEN 0 128 :::40972 :::* users:(("io.yahka.1",pid=2294,fd=26)) tcp LISTEN 0 128 :::111 :::* users:(("rpcbind",pid=443,fd=11)) tcp LISTEN 0 128 :::8081 :::* users:(("io.admin.0",pid=1489,fd=27)) tcp LISTEN 0 128 :::8082 :::* users:(("io.web.0",pid=1856,fd=27)) tcp LISTEN 0 128 :::22 :::* users:(("sshd",pid=857,fd=4)) [34;107m*** Log File - Last 25 Lines ***[0m 2024-01-20 12:00:44.991 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.58" greater than max "100" 2024-01-20 12:00:47.513 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:47.845 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:51.499 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:57.801 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:58.422 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:02.168 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.258 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.972 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:13.540 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:14.954 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.47" greater than max "100" 2024-01-20 12:01:18.555 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:19.303 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:20.258 - [32minfo[39m: admin.0 (1489) <== Disconnect system.user.admin from ::ffff:192.168.0.100 admin 2024-01-20 12:01:25.247 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.139 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.794 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:35.888 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:38.567 - [31merror[39m: shelly.0 (1781) [MQTT] (Shelly?) device unknown, configuration for client with id "shellypmmini-543204a97f50" does not exist! 2024-01-20 12:01:38.568 - [31merror[39m: shelly.0 (1781) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2024-01-20 12:01:38.605 - [32minfo[39m: shelly.0 (1781) [MQTT] Client Close: (shellypmmini / shellypmmini-543204a97f50 / undefined) (false) 2024-01-20 12:01:39.697 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:40.202 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:44.922 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.12" greater than max "100" 2024-01-20 12:01:46.455 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) [33m============ Mark until here for C&P =============[0m iob diag has finished. Press any key for a summary [3J[H[2JCopy text starting here: ======================= SUMMARY ======================= v.2023-10-25 Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: rlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 136 Pending iob updates: 20 Nodejs-Installation: /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 Recommended versions are nodejs 16.20.2 and npm 8.19.4 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 653M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G Active iob-Instances: 22 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 5463 States: 3094 Size of iob-Database: 23M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/objects.json.migrated 6.3M /opt/iobroker/iobroker-data/objects.json.bak.migrated 3.8M /opt/iobroker/iobroker-data/states.jsonl 1000K /opt/iobroker/iobroker-data/states.json.migrated 1000K /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== === Mark text until here for copying ===Mein Versionen:
pi@rock64:~$ type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
v14.21.3
v14.21.3
6.14.18
6.14.18Mein iobroker läuft sehr gut und stabil (backitup Adapter ausgenommen) ich kann nur einige wichtige Adapter nicht mehr updaten (u.a. Shelly) weil meine Versionen zu alt sind. Beim Updaten kommen dann diverse npm Fehlermeldungen.
Meine Idee war jetzt erstmal ein backup zu ziehen, ein neues System auf dem neuesten Stand aufzusetzen und das Backup wieder einzuspielen.
Achso, das ganze läuft auf einem ROCK64.
Danke an Thomas Braun. Das Diagnose Tool ist mega gut!!
Gruß Andy
Pending OS-Updates: 136 Pending iob updates: 20Die Kiste über Jahre versumpfen zu lassen funktioniert nachgewiesener Maßen nicht.
-
Hallo,
mir wurde in der Facebook "iobroker SmartHome und IoT" Gruppe schon ein wenig geholfen und ich wurde darum geben hier mein Diagnose Log rein zu stellen.Vielen Dank schon mal dafür. Ich hoffe das funktioniert mit dem angehängten log File.
[3J[H[2J*** iob diag is starting up, please wait *** [3J[H[2J [34;107m*** ioBroker Diagnosis ***[0m Please stretch the window of your terminal programm (puTTY) as wide as possible or switch to full screen The following checks may give hints to potential malconfigurations or errors, please post them in our forum: https://forum.iobroker.net Just copy and paste the Summary Page, including the ``` characters at start and end. It helps us to help you! Press any key to continue [3J[H[2J [33m======== Start marking the full check here =========[0m Skript v.2023-10-25 [34;107m*** BASE SYSTEM ***[0m Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 11:59:39 up 20:43, 1 user, load average: 1.35, 1.38, 0.98 CPU threads: 4 [34;107m*** Time and Time Zones ***[0m Local time: Sat 2024-01-20 11:59:39 CET Universal time: Sat 2024-01-20 10:59:39 UTC RTC time: Sat 2024-01-20 10:59:39 Time zone: Europe/Berlin (CET, +0100) Network time on: yes NTP synchronized: yes RTC in local TZ: no [34;107m*** User and Groups ***[0m pi /home/pi pi tty disk dialout sudo audio video plugdev games users systemd-journal input netdev ssh iobroker [34;107m*** X-Server-Setup ***[0m X-Server: false Desktop: Terminal: Boot Target: graphical.target [34;107m*** MEMORY ***[0m total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 651M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G 3988 M total memory 1347 M used memory 1556 M active memory 280 M inactive memory 2004 M free memory 77 M buffer memory 559 M swap cache 1023 M total swap 0 M used swap 1023 M free swap [34;107m*** FAILED SERVICES ***[0m 0 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. [34;107m*** FILESYSTEM ***[0m Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.0G 0 2.0G 0% /dev tmpfs tmpfs 399M 5.4M 394M 2% /run /dev/mmcblk0p1 ext4 15G 4.8G 9.2G 34% / tmpfs tmpfs 2.0G 0 2.0G 0% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs tmpfs 2.0G 636K 2.0G 1% /tmp /dev/zram0 ext4 49M 3.9M 42M 9% /var/log tmpfs tmpfs 399M 0 399M 0% /run/user/1000 [32mMessages concerning ext4 filesystem in dmesg:[0m [Fri Jan 19 15:16:20 2024] Kernel command line: earlycon=uart8250,mmio32,0xff130000 swiotlb=1 kpti=0 no_console_suspend=1 usbcore.autosuspend=-1 root=UUID=aadb45fc-8b8b-4b5b-ad50-7e6416a4e1c5 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=9dd9d2a5-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [Fri Jan 19 15:16:30 2024] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [Fri Jan 19 15:16:31 2024] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jan 20 11:55:20 2024] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm du: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jan 20 11:55:20 2024] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm du: path /var/log/lost+found: directory fails checksum at offset 12288 [32mShow mounted filesystems:[0m TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup tmpfs tmpfs ro,nosuid,nodev,noexec,mode=755 | | |-/sys/fs/cgroup/systemd cgroup cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd | | |-/sys/fs/cgroup/cpu,cpuacct cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct | | |-/sys/fs/cgroup/memory cgroup cgroup rw,nosuid,nodev,noexec,relatime,memory | | |-/sys/fs/cgroup/blkio cgroup cgroup rw,nosuid,nodev,noexec,relatime,blkio | | |-/sys/fs/cgroup/freezer cgroup cgroup rw,nosuid,nodev,noexec,relatime,freezer | | |-/sys/fs/cgroup/hugetlb cgroup cgroup rw,nosuid,nodev,noexec,relatime,hugetlb | | |-/sys/fs/cgroup/pids cgroup cgroup rw,nosuid,nodev,noexec,relatime,pids | | |-/sys/fs/cgroup/net_cls,net_prio cgroup cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio | | |-/sys/fs/cgroup/perf_event cgroup cgroup rw,nosuid,nodev,noexec,relatime,perf_event | | |-/sys/fs/cgroup/devices cgroup cgroup rw,nosuid,nodev,noexec,relatime,devices | | `-/sys/fs/cgroup/cpuset cgroup cgroup rw,nosuid,nodev,noexec,relatime,cpuset | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,relatime | | `-/sys/kernel/debug/tracing tracefs tracefs rw,relatime | |-/sys/kernel/config configfs configfs rw,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/dev udev devtmpfs rw,nosuid,relatime,size=2039432k,nr_inodes=509858,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/mqueue mqueue mqueue rw,relatime | `-/dev/hugepages hugetlbfs hugetlbfs rw,relatime |-/run tmpfs tmpfs rw,nosuid,noexec,relatime,size=408448k,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=408444k,mode=700,uid=1000,gid=1000 |-/tmp tmpfs tmpfs rw,nosuid,relatime |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600 `-/var/log /dev/zram0 ext4 rw,relatime,discard [32mFiles in neuralgic directories:[0m [32m/var:[0m 569M /var/ 286M /var/lib 274M /var/cache 269M /var/cache/apt 266M /var/lib/apt/lists Archived and active journals take up 4.9M in the file system. [32m/opt/iobroker/backups:[0m 71M /opt/iobroker/backups/ 43M /opt/iobroker/backups/Alt [32m/opt/iobroker/iobroker-data:[0m 357M /opt/iobroker/iobroker-data/ 234M /opt/iobroker/iobroker-data/files 83M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 51M /opt/iobroker/iobroker-data/files/javascript.admin [32mThe five largest files in iobroker-data are:[0m 23M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 8.2M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js [32mUSB-Devices by-id:[0m USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': [34;107m*** NodeJS-Installation ***[0m /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 nodejs: Installed: 14.21.3-1nodesource1 Candidate: 14.21.3-1nodesource1 Version table: *** 14.21.3-1nodesource1 500 500 https://deb.nodesource.com/node_14.x stretch/main arm64 Packages 100 /var/lib/dpkg/status 8.11.1~dfsg-2~bpo9+1 100 100 http://httpredir.debian.org/debian stretch-backports/main arm64 Packages 4.8.2~dfsg-1 500 500 http://httpredir.debian.org/debian stretch/main arm64 Packages [32mTemp directories causing npm8 problem:[0m 0 No problems detected Errors in npm tree: [34;107m*** ioBroker-Installation ***[0m [32mioBroker Status[0m iobroker is running on this host. Objects type: jsonl States type: jsonl [32mCore adapters versions[0m js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 Adapters from github: 3 [32mAdapter State[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : rock64 - disabled + system.adapter.bluelink.0 : bluelink : rock64 - enabled + system.adapter.discovery.0 : discovery : rock64 - enabled system.adapter.fronius.0 : fronius : rock64 - disabled + system.adapter.fronius.1 : fronius : rock64 - enabled + system.adapter.history.0 : history : rock64 - enabled + system.adapter.hm-rega.0 : hm-rega : rock64 - enabled + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.info.0 : info : rock64 - enabled + system.adapter.iot.0 : iot : rock64 - enabled + system.adapter.javascript.0 : javascript : rock64 - enabled system.adapter.midea.0 : midea : rock64 - disabled + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.pushover.0 : pushover : rock64 - enabled + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : rock64 - enabled + system.adapter.tr-064.0 : tr-064 : rock64 - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : rock64 - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : rock64 - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : rock64 - enabled system.adapter.vis.0 : vis : rock64 - enabled + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : rock64 - enabled + system.adapter.yahka.1 : yahka : rock64 - enabled + instance is alive [32mEnabled adapters with bindings[0m + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : rock64 - enabled, port: 0 + system.adapter.hue.0 : hue : rock64 - enabled, port: 443 + system.adapter.mihome.0 : mihome : rock64 - enabled, port: 9898, bind: 192.168.0.176 + system.adapter.shelly.0 : shelly : rock64 - enabled, port: 1882, bind: 192.168.0.176 + system.adapter.telegram.0 : telegram : rock64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin [32mioBroker-Repositories[0m stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable [32mInstalled ioBroker-Instances[0m Used repository: stable Adapter "admin" : 6.12.0 , installed 6.3.5 [Updatable] Adapter "backitup" : 2.9.8 , installed 2.8.1 [Updatable] Adapter "bluelink" : 2.3.6 , installed 2.3.2 [Updatable] Adapter "discovery" : 4.2.0 , installed 3.1.0 [Updatable] Adapter "fronius" : 2.0.2 , installed 2.0.2 Adapter "history" : 3.0.1 , installed 2.2.4 [Updatable] Adapter "hm-rega" : 4.0.0 , installed 3.0.46 [Updatable] Adapter "hm-rpc" : 1.15.19 , installed 1.15.16 [Updatable] Adapter "hue" : 3.10.1 , installed 3.7.1 [Updatable] Adapter "info" : 2.0.0 , installed 1.9.26 [Updatable] Adapter "iot" : 2.0.11 , installed 1.14.5 [Updatable] Adapter "javascript" : 7.1.6 , installed 6.1.4 [Updatable] Controller "js-controller": 5.0.17 , installed 4.0.24 [Updatable] Adapter "midea" : 0.0.7 , installed 0.0.7 Adapter "mihome" : 1.4.0 , installed 1.4.0 Adapter "pushover" : 3.0.6 , installed 3.0.3 [Updatable] Adapter "shelly" : 6.6.1 , installed 6.4.1 [Updatable] Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 4.2.0 [Updatable] Adapter "telegram" : 3.0.1 , installed 1.15.6 [Updatable] Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "vis" : 1.5.4 , installed 1.4.16 [Updatable] Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 6.1.10 , installed 4.3.0 [Updatable] Adapter "worx" : 2.3.4 , installed 2.3.2 [Updatable] Adapter "ws" : 2.5.8 , installed 1.3.0 [Updatable] Adapter "yahka" : 1.0.3 , installed 1.0.3 [32mObjects and States[0m Please stand by - This may take a while Objects: 5463 States: 3094 [34;107m*** OS-Repositories and Updates ***[0m Pending Updates: 136 [34;107m*** Listening Ports ***[0m Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port udp UNCONN 0 0 *:9898 *:* users:(("io.mihome.0",pid=1750,fd=27)) udp UNCONN 0 0 *:68 *:* users:(("dhclient",pid=906,fd=6)) udp UNCONN 0 0 *:111 *:* users:(("rpcbind",pid=443,fd=6)) udp UNCONN 0 0 192.168.0.176:123 *:* users:(("ntpd",pid=1481,fd=19)) udp UNCONN 0 0 127.0.0.1:123 *:* users:(("ntpd",pid=1481,fd=18)) udp UNCONN 0 0 *:123 *:* users:(("ntpd",pid=1481,fd=17)) udp UNCONN 0 0 *:619 *:* users:(("rpcbind",pid=443,fd=7)) udp UNCONN 0 0 *:5353 *:* users:(("io.yahka.1",pid=2294,fd=27)) udp UNCONN 0 0 :::111 :::* users:(("rpcbind",pid=443,fd=9)) udp UNCONN 0 0 fdad:a636:5c1e:ff4d:8907:c27d:dc5a:3529:123 :::* users:(("ntpd",pid=1481,fd=25)) udp UNCONN 0 0 fe80::f777:1c02:d801:d955%eth0:123 :::* users:(("ntpd",pid=1481,fd=21)) udp UNCONN 0 0 ::1:123 :::* users:(("ntpd",pid=1481,fd=20)) udp UNCONN 0 0 :::123 :::* users:(("ntpd",pid=1481,fd=16)) udp UNCONN 0 0 :::619 :::* users:(("rpcbind",pid=443,fd=10)) tcp LISTEN 0 128 127.0.0.1:9000 *:* users:(("iobroker.js-con",pid=838,fd=26)) tcp LISTEN 0 128 127.0.0.1:9001 *:* users:(("iobroker.js-con",pid=838,fd=20)) tcp LISTEN 0 128 *:111 *:* users:(("rpcbind",pid=443,fd=8)) tcp LISTEN 0 128 192.168.0.176:2001 *:* users:(("io.hm-rpc.0",pid=1684,fd=27)) tcp LISTEN 0 128 127.0.0.1:42836 *:* users:(("io.yahka.1",pid=2294,fd=30)) tcp LISTEN 0 128 *:22 *:* users:(("sshd",pid=857,fd=3)) tcp LISTEN 0 128 192.168.0.176:1882 *:* users:(("io.shelly.0",pid=1781,fd=27)) tcp LISTEN 0 128 192.168.0.176:2010 *:* users:(("io.hm-rpc.1",pid=1712,fd=27)) tcp LISTEN 0 128 :::40972 :::* users:(("io.yahka.1",pid=2294,fd=26)) tcp LISTEN 0 128 :::111 :::* users:(("rpcbind",pid=443,fd=11)) tcp LISTEN 0 128 :::8081 :::* users:(("io.admin.0",pid=1489,fd=27)) tcp LISTEN 0 128 :::8082 :::* users:(("io.web.0",pid=1856,fd=27)) tcp LISTEN 0 128 :::22 :::* users:(("sshd",pid=857,fd=4)) [34;107m*** Log File - Last 25 Lines ***[0m 2024-01-20 12:00:44.991 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.58" greater than max "100" 2024-01-20 12:00:47.513 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:47.845 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:51.499 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:57.801 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:00:58.422 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:02.168 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.258 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:08.972 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:13.540 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:14.954 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.47" greater than max "100" 2024-01-20 12:01:18.555 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:19.303 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:20.258 - [32minfo[39m: admin.0 (1489) <== Disconnect system.user.admin from ::ffff:192.168.0.100 admin 2024-01-20 12:01:25.247 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.139 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:29.794 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:35.888 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:38.567 - [31merror[39m: shelly.0 (1781) [MQTT] (Shelly?) device unknown, configuration for client with id "shellypmmini-543204a97f50" does not exist! 2024-01-20 12:01:38.568 - [31merror[39m: shelly.0 (1781) [MQTT] DO NOT CHANGE THE CLIENT-ID OF YOUR SHELLY DEVICES (see adapter documentation for details) 2024-01-20 12:01:38.605 - [32minfo[39m: shelly.0 (1781) [MQTT] Client Close: (shellypmmini / shellypmmini-543204a97f50 / undefined) (false) 2024-01-20 12:01:39.697 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.188 (shellydimmer / shellydimmer-D464FD / SHDM-1#D464FD#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:40.202 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.142 (shellydimmer / shellydimmer-D177F6 / SHDM-1#D177F6#1): This device is not protected via restricted login (see adapter documentation for details) 2024-01-20 12:01:44.922 - [33mwarn[39m: shelly.0 (1781) State value to set for "shelly.0.SHDM-1#D177F6#1.temperatureF" has value "102.12" greater than max "100" 2024-01-20 12:01:46.455 - [33mwarn[39m: shelly.0 (1781) [authEnabled] 192.168.0.116 (shelly1 / shelly1-B8F6B3 / SHSW-1#B8F6B3#1): This device is not protected via restricted login (see adapter documentation for details) [33m============ Mark until here for C&P =============[0m iob diag has finished. Press any key for a summary [3J[H[2JCopy text starting here: ======================= SUMMARY ======================= v.2023-10-25 Static hostname: rock64 Icon name: computer Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.4.192-rockchip64 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: rlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: graphical.target Pending OS-Updates: 136 Pending iob updates: 20 Nodejs-Installation: /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/bin/npx 6.14.18 /usr/bin/corepack 0.15.1 Recommended versions are nodejs 16.20.2 and npm 8.19.4 Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 4.1G 1.4G 2.1G 9.2M 653M 2.6G Swap: 1.0G 0B 1.0G Total: 5.1G 1.4G 3.1G Active iob-Instances: 22 Active repo(s): stable ioBroker Core: js-controller 4.0.24 admin 6.3.5 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : rock64 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : rock64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 5463 States: 3094 Size of iob-Database: 23M /opt/iobroker/iobroker-data/objects.jsonl 6.3M /opt/iobroker/iobroker-data/objects.json.migrated 6.3M /opt/iobroker/iobroker-data/objects.json.bak.migrated 3.8M /opt/iobroker/iobroker-data/states.jsonl 1000K /opt/iobroker/iobroker-data/states.json.migrated 1000K /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== === Mark text until here for copying ===Mein Versionen:
pi@rock64:~$ type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
/usr/bin/npx
v14.21.3
v14.21.3
6.14.18
6.14.18Mein iobroker läuft sehr gut und stabil (backitup Adapter ausgenommen) ich kann nur einige wichtige Adapter nicht mehr updaten (u.a. Shelly) weil meine Versionen zu alt sind. Beim Updaten kommen dann diverse npm Fehlermeldungen.
Meine Idee war jetzt erstmal ein backup zu ziehen, ein neues System auf dem neuesten Stand aufzusetzen und das Backup wieder einzuspielen.
Achso, das ganze läuft auf einem ROCK64.
Danke an Thomas Braun. Das Diagnose Tool ist mega gut!!
Gruß Andy
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
mit dem angehängten log File.
bitte als Text in code-tags posten.
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1
-
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
mit dem angehängten log File.
bitte als Text in code-tags posten.
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1
@homoran said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
mit dem angehängten log File.
bitte als Text in code-tags posten.
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1
Hab ich gemacht.
-
Da ist aber auch alles hoffnungslos veraltet...
Debian 9 'Stretch'...
Mittlerweile sind wir bei 12 und 10 ist auch bereits tot, 11 ist im Auslauf...Versuch mal:
iob stop iob fix iob nodejs-update 16@thomas-braun said in Fehlermeldungen beim Biobroker Update:
Da ist aber auch alles hoffnungslos veraltet...
Debian 9 'Stretch'...
Mittlerweile sind wir bei 12 und 10 ist auch bereits tot, 11 ist im Auslauf...Versuch mal:
iob stop iob fix iob nodejs-update 16Mir fehlte die Zeit und die Muße mich damit weiter zu beschäftigen. Seit dem Umstieg auf den Rock64 lief das System zu fehlerfrei... Das wird dann aber jetzt so langsam mal Zeit.
Der Befehl "iob nodejs-update 16" brachte folgende Ausgabe:
pi@rock64:~$ iob nodejs-update 16 iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]Erscheint den Befehl also nicht zu kennen.
Vielleicht ist es doch mal Zeit alles frisch und sauber aufzusetzen.
-
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
Da ist aber auch alles hoffnungslos veraltet...
Debian 9 'Stretch'...
Mittlerweile sind wir bei 12 und 10 ist auch bereits tot, 11 ist im Auslauf...Versuch mal:
iob stop iob fix iob nodejs-update 16Mir fehlte die Zeit und die Muße mich damit weiter zu beschäftigen. Seit dem Umstieg auf den Rock64 lief das System zu fehlerfrei... Das wird dann aber jetzt so langsam mal Zeit.
Der Befehl "iob nodejs-update 16" brachte folgende Ausgabe:
pi@rock64:~$ iob nodejs-update 16 iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]Erscheint den Befehl also nicht zu kennen.
Vielleicht ist es doch mal Zeit alles frisch und sauber aufzusetzen.
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
iob stop iob fix iob start ...warten... iob nodejs-update 16oder
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
alles frisch und sauber aufzusetzen.
-
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
Da ist aber auch alles hoffnungslos veraltet...
Debian 9 'Stretch'...
Mittlerweile sind wir bei 12 und 10 ist auch bereits tot, 11 ist im Auslauf...Versuch mal:
iob stop iob fix iob nodejs-update 16Mir fehlte die Zeit und die Muße mich damit weiter zu beschäftigen. Seit dem Umstieg auf den Rock64 lief das System zu fehlerfrei... Das wird dann aber jetzt so langsam mal Zeit.
Der Befehl "iob nodejs-update 16" brachte folgende Ausgabe:
pi@rock64:~$ iob nodejs-update 16 iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean]Erscheint den Befehl also nicht zu kennen.
Vielleicht ist es doch mal Zeit alles frisch und sauber aufzusetzen.
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
Du musst auch den fix zuvor ausführen... Wie ich geschrieben hatte...
-
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
Du musst auch den fix zuvor ausführen... Wie ich geschrieben hatte...
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
Du musst auch den fix zuvor ausführen... Wie ich geschrieben hatte...
Habe ich exakt in der Reihenfolge gemacht. Bei dem fix kommt nach einer Sekunde der Eingabe-Prompt.
pi@rock64:~$ iob stop pi@rock64:~$ iob fix pi@rock64:~$ iob nodejs-update 16 iobroker [command] -
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
iob stop iob fix iob start ...warten... iob nodejs-update 16oder
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
alles frisch und sauber aufzusetzen.
@homoran said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
iob stop iob fix iob start ...warten... iob nodejs-update 16oder
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
alles frisch und sauber aufzusetzen.
Es bleibt bei der gleichen Reaktion. iobroker listet mir möglich Optionen auf.
pi@rock64:~$ iob start pi@rock64:~$ iobroker stop pi@rock64:~$ iob fix pi@rock64:~$ iob start pi@rock64:~$ iob nodejs-update 16 iobroker [command] Commands: iobroker setup Setup ioBroker -
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Erscheint den Befehl also nicht zu kennen.
Du musst auch den fix zuvor ausführen... Wie ich geschrieben hatte...
Habe ich exakt in der Reihenfolge gemacht. Bei dem fix kommt nach einer Sekunde der Eingabe-Prompt.
pi@rock64:~$ iob stop pi@rock64:~$ iob fix pi@rock64:~$ iob nodejs-update 16 iobroker [command] -
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
curl -fsL https://iobroker.net/fix.sh | bash -
Soll iobroker dabei laufen? Also mit oder ohne
iob stop?
Danke nochmal!
-
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
curl -fsL https://iobroker.net/fix.sh | bash -
Soll iobroker dabei laufen? Also mit oder ohne
iob stop?
Danke nochmal!
@volleyhomer said in Fehlermeldungen beim Biobroker Update:
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
curl -fsL https://iobroker.net/fix.sh | bash -
Soll iobroker dabei laufen? Also mit oder ohne
iob stop?
Danke nochmal!
Hab gerade getestet. Result ist so oder so gleich. Seltsam
-
@volleyhomer said in Fehlermeldungen beim Biobroker Update:
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
curl -fsL https://iobroker.net/fix.sh | bash -
Soll iobroker dabei laufen? Also mit oder ohne
iob stop?
Danke nochmal!
Hab gerade getestet. Result ist so oder so gleich. Seltsam
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Result ist so oder so gleich.
Und wie lautet das gleiche Resultat?
-
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Result ist so oder so gleich.
Und wie lautet das gleiche Resultat?
@thomas-braun bei dem fix passiert gar nichts und der Eingabeprompt erscheint nach 1 Sekunde und wenn ich danach nodejs-16 Updaten will, listet er mir alle Optionen auf. Exakt gleich wie weiter oben beschrieben.
-
@thomas-braun bei dem fix passiert gar nichts und der Eingabeprompt erscheint nach 1 Sekunde und wenn ich danach nodejs-16 Updaten will, listet er mir alle Optionen auf. Exakt gleich wie weiter oben beschrieben.
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Exakt gleich wie weiter oben beschrieben.
Du sollst es auch nicht nacherzählen oder beschreiben sondern immer den Output im Terminal zeigen. Dann sehe ich was da passiert.
curl -L https://iobroker.net/fix.sh | bash - -
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Exakt gleich wie weiter oben beschrieben.
Du sollst es auch nicht nacherzählen oder beschreiben sondern immer den Output im Terminal zeigen. Dann sehe ich was da passiert.
curl -L https://iobroker.net/fix.sh | bash -@thomas-braun said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Exakt gleich wie weiter oben beschrieben.
Du sollst es auch nicht nacherzählen oder beschreiben sondern immer den Output im Terminal zeigen. Dann sehe ich was da passiert.
curl -L https://iobroker.net/fix.sh | bash -pi@rock64:~$ curl -L https://iobroker.net/fix.sh | bash - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. -
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Exakt gleich wie weiter oben beschrieben.
Du sollst es auch nicht nacherzählen oder beschreiben sondern immer den Output im Terminal zeigen. Dann sehe ich was da passiert.
curl -L https://iobroker.net/fix.sh | bash -pi@rock64:~$ curl -L https://iobroker.net/fix.sh | bash - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. -
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
Auch das ist eine Folge von deiner Update-Faulheit...
sudo apt updatepi@rock64:~$ sudo apt update [sudo] password for pi: Ign:1 http://httpredir.debian.org/debian stretch InRelease Ign:2 http://security.debian.org stretch/updates InRelease Err:3 http://security.debian.org stretch/updates Release 404 Not Found [IP: 146.75.122.132 80] Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease Err:6 http://httpredir.debian.org/debian stretch Release 404 Not Found [IP: 146.75.122.132 80] Err:7 http://httpredir.debian.org/debian stretch-updates Release 404 Not Found [IP: 146.75.122.132 80] Err:8 http://httpredir.debian.org/debian stretch-backports Release 404 Not Found [IP: 146.75.122.132 80] Ign:9 http://apt.armbian.com stretch InRelease Hit:10 https://deb.nodesource.com/node_14.x stretch InRelease Err:11 http://apt.armbian.com stretch Release 502 Bad Gateway [IP: 130.185.239.78 80] Reading package lists... Done E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://apt.armbian.com stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -
@thomas-braun said in Fehlermeldungen beim Biobroker Update:
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
Exakt gleich wie weiter oben beschrieben.
Du sollst es auch nicht nacherzählen oder beschreiben sondern immer den Output im Terminal zeigen. Dann sehe ich was da passiert.
curl -L https://iobroker.net/fix.sh | bash -pi@rock64:~$ curl -L https://iobroker.net/fix.sh | bash - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (60) SSL certificate problem: certificate has expired More details here: https://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option.@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
curl -kL https://iobroker.net/fix.sh | bash - -
@volleyhomer sagte in Fehlermeldungen beim Biobroker Update:
curl -kL https://iobroker.net/fix.sh | bash -@thomas-braun said in Fehlermeldungen beim Biobroker Update:
curl -kL https://iobroker.net/fix.sh | bash -
Das lief scheinbar durch.
pi@rock64:~$ curl -kL https://iobroker.net/fix.sh | bash - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 185 100 185 0 0 916 0 --:--:-- --:--:-- --:--:-- 915 100 39849 100 39849 0 0 59580 0 --:--:-- --:--:-- --:--:-- 59580 library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Ign:1 http://security.debian.org stretch/updates InRelease Ign:2 http://httpredir.debian.org/debian stretch InRelease Err:3 http://security.debian.org stretch/updates Release 404 Not Found [IP: 146.75.122.132 80] Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease Err:6 http://httpredir.debian.org/debian stretch Release 404 Not Found [IP: 146.75.122.132 80] Err:7 http://httpredir.debian.org/debian stretch-updates Release 404 Not Found [IP: 146.75.122.132 80] Err:8 http://httpredir.debian.org/debian stretch-backports Release 404 Not Found [IP: 146.75.122.132 80] Hit:10 https://deb.nodesource.com/node_14.x stretch InRelease Hit:9 http://fi.mirror.armbian.de/apt stretch InRelease Reading package lists... Done E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed libcairo2-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed libpango1.0-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed libjpeg-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed libgif-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed librsvg2-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed libpixman-1-dev E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file. E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file. Installed cmake ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! npx: installed 12 in 14.437s No path given, using /opt/iobroker/iobroker-data Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================
883
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge