[gelöst] Hohe Schreibaktivitäten am iobroker
-
Hallo zusammen,
ich habe seit 31.12.2024 hohe Schreibaktivitäten am iobroker System. Wo kann man nachschauen welcher Dienst dafür verantworlich ist?Script v.2024-10-19 *** BASE SYSTEM *** Static hostname: BU02SMART02-iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Ubuntu 24.04.1 LTS Kernel: Linux 6.8.12-2-pve Architecture: x86-64 OS is similar to: debian model name : Intel(R) Core(TM) i3-5010U CPU @ 2.10GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 15:53:40 up 20:52, 4 users, load average: 7.82, 5.97, 4.87 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Ubuntu LTS release codenamed 'noble'! *** TIME AND TIMEZONES *** Local time: Sun 2025-01-05 15:53:40 CET Universal time: Sun 2025-01-05 14:53:40 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': mario HOME=/home/mario GROUPS=mario sudo iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev redis *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.6G 3.9G 3.3G 98K 1.3G 4.7G Swap: 8.1G 1.0G 7.1G Total: 16G 5.0G 10G Active iob-Instances: 37 8192 M total memory 3756 M used memory 3016 M active memory 1715 M inactive memory 3162 M free memory 0 M buffer memory 1273 M swap cache 7759 M total swap 966 M used swap 6793 M free swap *** top - Table Of Processes *** top - 15:53:41 up 20:52, 4 users, load average: 7.75, 5.99, 4.88 Tasks: 77 total, 6 running, 70 sleeping, 0 stopped, 1 zombie %Cpu(s): 50.0 us, 42.0 sy, 0.0 ni, 4.0 id, 0.0 wa, 0.0 hi, 4.0 si, 0.0 st MiB Mem : 8192.0 total, 3159.7 free, 3759.1 used, 1273.3 buff/cache MiB Swap: 7760.0 total, 6793.4 free, 966.6 used. 4432.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * apparmor.service loaded failed failed Load AppArmor profiles Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--566--disk--0 ext4 40G 26G 12G 69% / none tmpfs 492K 4.0K 488K 1% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs tmpfs 3.1G 188K 3.1G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 1.6G 8.0K 1.6G 1% /run/user/1001 Messages concerning ext4 filesystem in dmesg: [Thu Dec 26 02:01:32 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Thu Dec 26 02:01:33 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Thu Dec 26 02:01:34 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Thu Dec 26 02:08:09 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Thu Dec 26 02:08:10 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Thu Dec 26 02:08:11 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Fri Dec 27 01:31:22 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Fri Dec 27 01:31:22 2024] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Fri Dec 27 01:40:11 2024] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Fri Dec 27 02:01:37 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Fri Dec 27 02:01:37 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Fri Dec 27 02:01:39 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Fri Dec 27 02:08:26 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Fri Dec 27 02:08:28 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Fri Dec 27 02:08:28 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sat Dec 28 01:31:38 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sat Dec 28 01:31:38 2024] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Sat Dec 28 01:41:16 2024] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sat Dec 28 02:01:52 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Sat Dec 28 02:01:52 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sat Dec 28 02:01:53 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sat Dec 28 02:08:14 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sat Dec 28 02:08:16 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sat Dec 28 02:08:16 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sun Dec 29 01:31:57 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Dec 29 01:31:57 2024] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Sun Dec 29 01:41:25 2024] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sun Dec 29 02:01:46 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Dec 29 02:01:46 2024] EXT4-fs (dm-22): mounted filesystem 0b201620-47d9-424a-98f7-0eef827b7602 ro without journal. Quota mode: none. [Sun Dec 29 02:16:09 2024] EXT4-fs (dm-22): unmounting filesystem 0b201620-47d9-424a-98f7-0eef827b7602. [Sun Dec 29 02:16:23 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Sun Dec 29 02:16:23 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sun Dec 29 02:16:24 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sun Dec 29 02:23:16 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sun Dec 29 02:23:18 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sun Dec 29 02:23:18 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sun Dec 29 03:02:06 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Dec 29 03:02:06 2024] EXT4-fs (dm-22): mounted filesystem 97e4bf13-aa6a-490a-9084-0ef966e27059 ro without journal. Quota mode: none. [Sun Dec 29 03:04:30 2024] EXT4-fs (dm-22): unmounting filesystem 97e4bf13-aa6a-490a-9084-0ef966e27059. [Sun Dec 29 03:04:31 2024] EXT4-fs (dm-22): mounted filesystem ae35cdaa-1a62-4b98-a296-ba8f12f56ddf ro without journal. Quota mode: none. [Sun Dec 29 03:05:37 2024] EXT4-fs (dm-22): unmounting filesystem ae35cdaa-1a62-4b98-a296-ba8f12f56ddf. [Sun Dec 29 03:05:38 2024] EXT4-fs (dm-22): mounted filesystem f869841f-36e0-4558-9733-9c048981acb7 ro without journal. Quota mode: none. [Sun Dec 29 03:06:52 2024] EXT4-fs (dm-22): unmounting filesystem f869841f-36e0-4558-9733-9c048981acb7. [Sun Dec 29 03:06:53 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Dec 29 03:06:53 2024] EXT4-fs (dm-22): mounted filesystem 4d085891-c3dd-4cfa-befe-7a06a81ff97f ro without journal. Quota mode: none. [Sun Dec 29 03:07:32 2024] EXT4-fs (dm-22): unmounting filesystem 4d085891-c3dd-4cfa-befe-7a06a81ff97f. [Mon Dec 30 01:32:08 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Mon Dec 30 01:32:08 2024] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Mon Dec 30 01:41:17 2024] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Mon Dec 30 02:02:18 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Mon Dec 30 02:02:18 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Mon Dec 30 02:02:19 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Mon Dec 30 02:08:37 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Mon Dec 30 02:08:39 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Mon Dec 30 02:08:39 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Tue Dec 31 01:32:25 2024] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Tue Dec 31 01:32:25 2024] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Tue Dec 31 01:43:48 2024] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Tue Dec 31 02:02:38 2024] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Tue Dec 31 02:02:39 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Tue Dec 31 02:02:40 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Tue Dec 31 02:08:43 2024] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Tue Dec 31 02:08:45 2024] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Tue Dec 31 02:08:45 2024] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Wed Jan 1 01:32:29 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Wed Jan 1 01:32:29 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Wed Jan 1 01:40:23 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Wed Jan 1 02:02:42 2025] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Wed Jan 1 02:02:42 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Wed Jan 1 02:02:43 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Wed Jan 1 02:08:22 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Wed Jan 1 02:08:24 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Wed Jan 1 02:08:24 2025] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Thu Jan 2 01:32:42 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Thu Jan 2 01:32:42 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Thu Jan 2 01:41:22 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Thu Jan 2 02:03:01 2025] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Thu Jan 2 02:03:01 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Thu Jan 2 02:03:02 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Thu Jan 2 02:09:09 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Thu Jan 2 02:09:11 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Thu Jan 2 02:09:11 2025] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Fri Jan 3 01:32:52 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Fri Jan 3 01:32:52 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Fri Jan 3 01:41:09 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Fri Jan 3 02:03:13 2025] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Fri Jan 3 02:03:14 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Fri Jan 3 02:03:14 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Fri Jan 3 02:09:02 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Fri Jan 3 02:09:03 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Fri Jan 3 02:09:03 2025] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sat Jan 4 01:33:12 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sat Jan 4 01:33:12 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Sat Jan 4 01:42:19 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sat Jan 4 02:03:26 2025] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Sat Jan 4 02:03:26 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sat Jan 4 02:03:27 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sat Jan 4 02:09:30 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sat Jan 4 02:09:32 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sat Jan 4 02:09:32 2025] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sat Jan 4 18:26:48 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sat Jan 4 18:26:48 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Sat Jan 4 18:36:46 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sat Jan 4 19:04:10 2025] EXT4-fs (dm-20): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sat Jan 4 19:04:12 2025] EXT4-fs (dm-20): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 r/w with ordered data mode. Quota mode: none. [Sun Jan 5 01:33:14 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Jan 5 01:33:14 2025] EXT4-fs (dm-22): mounted filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9 ro without journal. Quota mode: none. [Sun Jan 5 01:41:36 2025] EXT4-fs (dm-22): unmounting filesystem 74b0caa6-c920-47dd-a380-8fcf95cbc8d9. [Sun Jan 5 02:03:16 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Jan 5 02:03:16 2025] EXT4-fs (dm-22): mounted filesystem 0b201620-47d9-424a-98f7-0eef827b7602 ro without journal. Quota mode: none. [Sun Jan 5 02:20:06 2025] EXT4-fs (dm-22): unmounting filesystem 0b201620-47d9-424a-98f7-0eef827b7602. [Sun Jan 5 02:20:21 2025] EXT4-fs (dm-17): unmounting filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6. [Sun Jan 5 02:20:21 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sun Jan 5 02:20:22 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sun Jan 5 02:26:26 2025] EXT4-fs (dm-16): unmounting filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49. [Sun Jan 5 02:26:28 2025] EXT4-fs (dm-16): mounted filesystem 0ff95afb-f745-4aa4-a51f-d73f68adef49 r/w with ordered data mode. Quota mode: none. [Sun Jan 5 02:26:28 2025] EXT4-fs (dm-17): mounted filesystem 54635ccf-accc-4c8b-bfcb-843eb62defd6 r/w with ordered data mode. Quota mode: none. [Sun Jan 5 03:03:17 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Jan 5 03:03:17 2025] EXT4-fs (dm-22): mounted filesystem 97e4bf13-aa6a-490a-9084-0ef966e27059 ro without journal. Quota mode: none. [Sun Jan 5 03:05:38 2025] EXT4-fs (dm-22): unmounting filesystem 97e4bf13-aa6a-490a-9084-0ef966e27059. [Sun Jan 5 03:05:39 2025] EXT4-fs (dm-22): mounted filesystem ae35cdaa-1a62-4b98-a296-ba8f12f56ddf ro without journal. Quota mode: none. [Sun Jan 5 03:06:50 2025] EXT4-fs (dm-22): unmounting filesystem ae35cdaa-1a62-4b98-a296-ba8f12f56ddf. [Sun Jan 5 03:06:51 2025] EXT4-fs (dm-22): mounted filesystem f869841f-36e0-4558-9733-9c048981acb7 ro without journal. Quota mode: none. [Sun Jan 5 03:07:47 2025] EXT4-fs (dm-22): unmounting filesystem f869841f-36e0-4558-9733-9c048981acb7. [Sun Jan 5 03:07:48 2025] EXT4-fs (dm-22): write access unavailable, skipping orphan cleanup [Sun Jan 5 03:07:48 2025] EXT4-fs (dm-22): mounted filesystem 4d085891-c3dd-4cfa-befe-7a06a81ff97f ro without journal. Quota mode: none. [Sun Jan 5 03:08:20 2025] EXT4-fs (dm-22): unmounting filesystem 4d085891-c3dd-4cfa-befe-7a06a81ff97f. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--566--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 5.5G /var/ 4.0G /var/log/journal/a4cc250a83fe4944adccd8462a307fa7 4.0G /var/log/journal 4.0G /var/log 792M /var/lib Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 51.5M in the file system. /opt/iobroker/backups: 777M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 9.9G /opt/iobroker/iobroker-data/ 7.4G /opt/iobroker/iobroker-data/history 1.4G /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static The five largest files in iobroker-data are: 98M /opt/iobroker/iobroker-data/objects.json.migrated 98M /opt/iobroker/iobroker-data/objects.json.bak.migrated 71M /opt/iobroker/iobroker-data/objects.jsonl 43M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.c9e0f545.js.map 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_d653ffa49dc9eb11ade6914f1d69213e-if00-port0 HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyUSB0 *** NodeJS-Installation *** /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 nodejs: Installed: 20.18.1-1nodesource1 Candidate: 20.18.1-1nodesource1 Version table: *** 20.18.1-1nodesource1 100 100 /var/lib/dpkg/status 18.19.1+dfsg-6ubuntu5 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: redis Hosts: BU02SMART02-iobroker BU02SMART02-iobroker (version: 7.0.6, hostname: BU02SMART02-iobroker, alive, uptime: 75155) Core adapters versions js-controller: 7.0.6 admin: 7.2.6 javascript: 8.8.3 nodejs modules from github: 1 | +-- samsungtv@0.0.0 (git+https://git@github.com/luca-saggese/samsungtv.git#7fc20107455414e2afb94022682e0787e8635550) Adapter State + system.adapter.admin.0 : admin : BU02SMART02-iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alarm.0 : alarm : BU02SMART02-iobroker - enabled + system.adapter.alexa2.0 : alexa2 : BU02SMART02-iobroker - enabled system.adapter.bosesoundtouch.0 : bosesoundtouch : BU02SMART02-iobroker - disabled + system.adapter.daikin.0 : daikin : BU02SMART02-iobroker - enabled + system.adapter.device-reminder.0 : device-reminder : BU02SMART02-iobroker - enabled + system.adapter.device-watcher.1 : device-watcher : BU02SMART02-iobroker - enabled + system.adapter.discovery.0 : discovery : BU02SMART02-iobroker - enabled system.adapter.dwd.0 : dwd : BU02SMART02-iobroker - enabled system.adapter.ecovacs-deebot.0 : ecovacs-deebot : BU02SMART02-iobroker - disabled + system.adapter.ems-esp.0 : ems-esp : BU02SMART02-iobroker - enabled + system.adapter.energiefluss.0 : energiefluss : BU02SMART02-iobroker - enabled + system.adapter.energiefluss.1 : energiefluss : BU02SMART02-iobroker - enabled system.adapter.feiertage.0 : feiertage : BU02SMART02-iobroker - enabled system.adapter.flot.0 : flot : BU02SMART02-iobroker - enabled + system.adapter.followthesun.0 : followthesun : BU02SMART02-iobroker - enabled + system.adapter.hass-mqtt.0 : hass-mqtt : BU02SMART02-iobroker - enabled + system.adapter.history.0 : history : BU02SMART02-iobroker - enabled + system.adapter.homeconnect.0 : homeconnect : BU02SMART02-iobroker - enabled system.adapter.ical.0 : ical : BU02SMART02-iobroker - enabled system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: BU02SMART02-iobroker - enabled system.adapter.icons-icons8.0 : icons-icons8 : BU02SMART02-iobroker - enabled system.adapter.icons-material-png.0 : icons-material-png : BU02SMART02-iobroker - enabled system.adapter.icons-material-svg.0 : icons-material-svg : BU02SMART02-iobroker - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : BU02SMART02-iobroker - enabled system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: BU02SMART02-iobroker - enabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : BU02SMART02-iobroker - enabled + system.adapter.influxdb.0 : influxdb : BU02SMART02-iobroker - enabled, port: 8086 + system.adapter.iot.0 : iot : BU02SMART02-iobroker - enabled + system.adapter.javascript.0 : javascript : BU02SMART02-iobroker - enabled + system.adapter.linkeddevices.0 : linkeddevices : BU02SMART02-iobroker - enabled system.adapter.material.0 : material : BU02SMART02-iobroker - enabled system.adapter.mercedesme.0 : mercedesme : BU02SMART02-iobroker - disabled system.adapter.mqtt-client.0 : mqtt-client : BU02SMART02-iobroker - disabled, port: 1892 + system.adapter.mqtt.0 : mqtt : BU02SMART02-iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : BU02SMART02-iobroker - enabled, port: 1891, bind: 192.168.2.166 + system.adapter.net-tools.0 : net-tools : BU02SMART02-iobroker - enabled system.adapter.netatmo-crawler.0 : netatmo-crawler : BU02SMART02-iobroker - enabled system.adapter.openweathermap.0 : openweathermap : BU02SMART02-iobroker - enabled + system.adapter.ping.0 : ping : BU02SMART02-iobroker - enabled + system.adapter.pvforecast.0 : pvforecast : BU02SMART02-iobroker - enabled system.adapter.ring.0 : ring : BU02SMART02-iobroker - disabled + system.adapter.samsung.0 : samsung : BU02SMART02-iobroker - enabled + system.adapter.shelly.0 : shelly : BU02SMART02-iobroker - enabled, port: 1890, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : BU02SMART02-iobroker - enabled, port: 1890, bind: 192.168.2.166 + system.adapter.slideshow.0 : slideshow : BU02SMART02-iobroker - enabled + system.adapter.smartthings.0 : smartthings : BU02SMART02-iobroker - enabled system.adapter.socketio.0 : socketio : BU02SMART02-iobroker - disabled, port: 8084, bind: 192.168.2.166, run as: admin + system.adapter.sourceanalytix.0 : sourceanalytix : BU02SMART02-iobroker - enabled + system.adapter.telegram.0 : telegram : BU02SMART02-iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tuya.0 : tuya : BU02SMART02-iobroker - enabled + system.adapter.virtualpowermeter.0 : virtualpowermeter : BU02SMART02-iobroker - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : BU02SMART02-iobroker - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : BU02SMART02-iobroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: BU02SMART02-iobroker - enabled system.adapter.vis-2.0 : vis-2 : BU02SMART02-iobroker - disabled system.adapter.vis-bars.0 : vis-bars : BU02SMART02-iobroker - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : BU02SMART02-iobroker - enabled system.adapter.vis-colorpicker.0 : vis-colorpicker : BU02SMART02-iobroker - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : BU02SMART02-iobroker - enabled system.adapter.vis-history.0 : vis-history : BU02SMART02-iobroker - enabled system.adapter.vis-homekittiles.0 : vis-homekittiles : BU02SMART02-iobroker - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : BU02SMART02-iobroker - enabled system.adapter.vis-icontwo.0 : vis-icontwo : BU02SMART02-iobroker - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : BU02SMART02-iobroker - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : BU02SMART02-iobroker - enabled system.adapter.vis-justgage.0 : vis-justgage : BU02SMART02-iobroker - enabled system.adapter.vis-lcars.0 : vis-lcars : BU02SMART02-iobroker - enabled system.adapter.vis-material-advanced.0 : vis-material-advanced : BU02SMART02-iobroker - enabled system.adapter.vis-material.0 : vis-material : BU02SMART02-iobroker - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : BU02SMART02-iobroker - enabled system.adapter.vis-plumb.0 : vis-plumb : BU02SMART02-iobroker - enabled system.adapter.vis-rgraph.0 : vis-rgraph : BU02SMART02-iobroker - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : BU02SMART02-iobroker - enabled system.adapter.vis-weather.0 : vis-weather : BU02SMART02-iobroker - enabled system.adapter.vis.0 : vis : BU02SMART02-iobroker - enabled system.adapter.vw-connect.0 : vw-connect : BU02SMART02-iobroker - disabled + system.adapter.web.0 : web : BU02SMART02-iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.yahka.0 : yahka : BU02SMART02-iobroker - enabled system.adapter.yahka.1 : yahka : BU02SMART02-iobroker - disabled + system.adapter.zigbee.0 : zigbee : BU02SMART02-iobroker - enabled, port: /dev/ttyUSB0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : BU02SMART02-iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : BU02SMART02-iobroker - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : BU02SMART02-iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.mqtt.1 : mqtt : BU02SMART02-iobroker - enabled, port: 1891, bind: 192.168.2.166 + system.adapter.shelly.0 : shelly : BU02SMART02-iobroker - enabled, port: 1890, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : BU02SMART02-iobroker - enabled, port: 1890, bind: 192.168.2.166 + system.adapter.telegram.0 : telegram : BU02SMART02-iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : BU02SMART02-iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : BU02SMART02-iobroker - enabled, port: /dev/ttyUSB0 ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Stable (default) Upgrade policy: none Installed ioBroker-Instances Used repository: Stable (default) Adapter "admin" : 7.1.5 , installed 7.2.6 Adapter "alarm" : 3.6.7 , installed 3.6.4 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.26.7 Adapter "bosesoundtouch": 0.11.1 , installed 0.11.1 Adapter "daikin" : 1.4.2 , installed 1.4.2 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "device-watcher": 2.12.1 , installed 2.12.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "ecovacs-deebot": 1.4.15 , installed 1.4.15 Adapter "ems-esp" : 5.0.6 , installed 5.1.1 Adapter "energiefluss" : 3.6.2 , installed 3.6.1 [Updatable] Adapter "feiertage" : 1.2.0 , installed 1.2.0 Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "followthesun" : 0.5.1 , installed 0.5.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "homeconnect" : 1.4.3 , installed 1.4.3 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-material-svg": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "icons-open-icon-library-png": 0.1.2, installed 0.1.3 Adapter "icons-ultimate-png": 1.0.1, installed 1.0.1 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iot" : 3.3.0 , installed 3.4.2 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "linkeddevices": 1.5.5 , installed 1.5.5 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "megaesp" : 0.1.0 , installed 0.1.0 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "mqtt-client" : 2.1.0 , installed 2.0.0 [Updatable] Adapter "net-tools" : 1.0.11 , installed 1.0.11 Adapter "netatmo-crawler": 0.8.1 , installed 0.8.1 Adapter "openweathermap": 1.1.2 , installed 1.1.2 Adapter "ping" : 1.6.2 , installed 1.7.9 Adapter "pvforecast" : 4.1.0 , installed 4.1.0 Adapter "ring" : 6.3.0 , installed 6.2.1 [Updatable] Adapter "samsung" : 0.6.1 , installed 0.6.1 Adapter "shelly" : 8.2.1 , installed 8.5.1 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "statistics" : 2.4.0 , installed 2.4.0 Adapter "telegram" : 3.9.0 , installed 3.9.0 Adapter "tuya" : 3.16.0 , installed 3.16.0 Adapter "virtualpowermeter": 1.5.0, installed 1.4.6 [Updatable] Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.9.64 , installed 2.9.64 Adapter "vis-2-widgets-energy": 1.0.2, installed 1.0.2 Adapter "vis-2-widgets-gauges": 1.1.0, installed 1.1.1 Adapter "vis-2-widgets-material": 1.4.10, installed 1.4.10 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-colorpicker": 2.0.3 , installed 2.0.3 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-homekittiles": 0.3.2 , installed 0.3.1 [Updatable] Adapter "vis-hqwidgets": 1.5.1 , installed 1.5.1 Adapter "vis-icontwo" : 1.5.0 , installed 1.5.0 Adapter "vis-inventwo" : 3.3.4 , installed 3.3.4 Adapter "vis-jqui-mfd" : 1.1.1 , installed 1.1.1 Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-lcars" : 1.1.1 , installed 1.1.1 Adapter "vis-material" : 0.1.3 , installed 0.1.3 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.9 , installed 2.5.9 Adapter "web" : 6.2.5 , installed 6.3.1 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.0.3 , installed 1.0.9 Adapter "zigbee" : 1.10.14 , installed 1.10.3 [Updatable] Objects and States Please stand by - This may take a while Objects: 40799 States: 37909 *** OS-Repositories and Updates *** Hit:1 http://archive.ubuntu.com/ubuntu noble InRelease Hit:2 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 151268540 424/master tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 151270643 441/iobroker.js-con tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 106 151267750 215/systemd-resolve tcp 0 0 127.0.0.1:38239 0.0.0.0:* LISTEN 1000 151280948 932/io.yahka.0 tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 106 151267752 215/systemd-resolve tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN 1001 160612688 166587/sshd: mario@ tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 113 151267862 241/redis-server 12 tcp 0 0 192.168.2.166:1890 0.0.0.0:* LISTEN 1000 156039839 80889/io.shelly.1 tcp 0 0 192.168.2.166:1891 0.0.0.0:* LISTEN 1000 151276441 805/io.mqtt.1 tcp 0 0 127.0.0.1:39377 0.0.0.0:* LISTEN 1000 159206900 932/io.yahka.0 tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1000 151276165 790/io.mqtt.0 tcp 0 0 0.0.0.0:42501 0.0.0.0:* LISTEN 1000 151284998 932/io.yahka.0 tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 151266620 1/init tcp6 0 0 :::8082 :::* LISTEN 1000 151298150 1438/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 151271024 476/io.admin.0 tcp6 0 0 ::1:6379 :::* LISTEN 113 151267863 241/redis-server 12 tcp6 0 0 ::1:6011 :::* LISTEN 1001 160612687 166587/sshd: mario@ tcp6 0 0 :::3000 :::* LISTEN 112 151269730 246/grafana tcp6 0 0 :::22 :::* LISTEN 0 151267763 1/init tcp6 0 0 :::111 :::* LISTEN 0 151266621 1/init tcp6 0 0 ::1:25 :::* LISTEN 0 151268541 424/master udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 151285003 932/io.yahka.0 udp 0 0 0.0.0.0:5353 0.0.0.0:* 1000 151285002 932/io.yahka.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 151292381 900/io.shelly.0 udp 0 0 0.0.0.0:6666 0.0.0.0:* 1000 151298055 917/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1000 151298056 917/io.tuya.0 udp 0 0 127.0.0.54:53 0.0.0.0:* 106 151267751 215/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 106 151267749 215/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 151264210 1/init udp 0 0 0.0.0.0:41660 0.0.0.0:* 1000 151292383 900/io.shelly.0 udp6 0 0 :::111 :::* 0 151264215 1/init *** Log File - Last 25 Lines *** 2025-01-05 13:59:17.781 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:00:18.311 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:04:20.584 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:05:21.337 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:09:22.910 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:27:30.382 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:28:30.782 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:30:31.987 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:33:33.360 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:39:36.044 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:46:39.160 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 14:54:44.000 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:02:47.300 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:04:48.157 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:12:52.483 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:17:54.589 - error: daikin.0 (696) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:33:36.140 - info: vis.0 (160203) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.18.1, js-controller: 7.0.6 2025-01-05 15:33:39.545 - info: vis.0 (160203) Changes in index.html detected => update cache.manifest 2025-01-05 15:33:39.568 - info: vis.0 (160203) Upload vis anew, while changes detected... 2025-01-05 15:33:47.680 - warn: host.BU02SMART02-iobroker instance system.adapter.vis.0 already running with pid 160203 2025-01-05 15:34:12.046 - info: vis.0 (160203) Uploaded. 0 2025-01-05 15:34:12.549 - info: vis.0 (160203) Terminated (NO_ERROR): Without reason 2025-01-05 15:38:05.650 - error: daikin.0 (160290) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:48:11.175 - error: daikin.0 (160290) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET 2025-01-05 15:49:11.692 - error: daikin.0 (160290) Error updating data: Error occured: Error while communicating with Daikin device: ECONNRESET======================= SUMMARY ======================= v.2024-10-19 Static hostname: BU02SMART02-iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Ubuntu 24.04.1 LTS Kernel: Linux 6.8.12-2-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CET, +0100) User-ID: 1001 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 7 Nodejs-Installation: /usr/bin/nodejs v20.18.1 /usr/bin/node v20.18.1 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.4 Recommended versions are nodejs 20.18.1 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 8.6G 4.0G 3.3G 98K 1.3G 4.6G Swap: 8.1G 1.0G 7.1G Total: 16G 5.0G 10G Active iob-Instances: 37 Upgrade policy: none ioBroker Core: js-controller 7.0.6 admin 7.2.6 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: redis Status admin and web instance: + system.adapter.admin.0 : admin : BU02SMART02-iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : BU02SMART02-iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 40799 States: 37909 Size of iob-Database: 98M /opt/iobroker/iobroker-data/objects.json.migrated 98M /opt/iobroker/iobroker-data/objects.json.bak.migrated 71M /opt/iobroker/iobroker-data/objects.jsonl 28M /opt/iobroker/iobroker-data/states.jsonl Operating System is the current Ubuntu LTS release codenamed 'noble'! =================== END OF SUMMARY ====================
-
Was zeigt dir
top? Da kann man vielleicht sehen, was da rödelt. -
@m-schalk du hast viele Meldungen zum Thema
Messages concerning ext4 filesystem in dmesg:
Ich kann dir leider nicht sagen, was die Meldungen als Ursache haben.Dein history Ordner ist 7 GB groß und auch das var/log vom Betriebssystem ist mit 4gb sehr groß.
Deaktiviere Mal den history adapter und schau wie sich das System verhält. Prüfe auch deine Datenpunkte was du in welchem Intervall loggst.
Wo liegt die influx Datenbank? Auf dem gleichen system?
-
@feuersturm said in Hohe Schreibaktivitäten am iobroker:
@m-schalk du hast viele Meldungen zum Thema
Messages concerning ext4 filesystem in dmesg:
Ich kann dir leider nicht sagen, was die Meldungen als Ursache haben.Dein history Ordner ist 7 GB groß und auch das var/log vom Betriebssystem ist mit 4gb sehr groß.
Deaktiviere Mal den history adapter und schau wie sich das System verhält. Prüfe auch deine Datenpunkte was du in welchem Intervall loggst.
Wo liegt die influx Datenbank? Auf dem gleichen system?
Die Influx liegt wo anders, den History Adapter räume ich mal auf, allederings hat es bisher keinen Einfluß auf die Schreibtätigkeit.
Sonst noch Ideen?
-
@m-schalk sagte in Hohe Schreibaktivitäten am iobroker:
Sonst noch Ideen?
Wie auch, hast ja das Ergebnis von
topnoch immer nicht gezeigt. -
@meister-mopper said in Hohe Schreibaktivitäten am iobroker:
@m-schalk sagte in Hohe Schreibaktivitäten am iobroker:
Sonst noch Ideen?
Wie auch, hast ja das Ergebnis von
topnoch immer nicht gezeigt.Hallo Meister-mopper, anbei der TOP Auszug.
top - 08:05:43 up 13:06, 1 user, load average: 7.72, 4.88, 3.53 Tasks: 60 total, 1 running, 59 sleeping, 0 stopped, 0 zombie %Cpu(s): 30.9 us, 12.8 sy, 0.0 ni, 50.3 id, 4.7 wa, 0.0 hi, 1.3 si, 0.0 st MiB Mem : 8192.0 total, 3783.4 free, 3773.8 used, 634.9 buff/cache MiB Swap: 7760.0 total, 7227.8 free, 532.2 used. 4418.2 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1226 iobroker 20 0 21.4g 220468 46848 S 15.9 2.6 133:56.97 io.web.0 808 iobroker 20 0 21.1g 159384 50048 S 10.6 1.9 157:09.64 io.shelly.0 426 iobroker 20 0 21.6g 474444 50816 D 8.6 5.7 205:08.63 iobroker.js-con 235 redis 20 0 939884 187004 9344 S 6.3 2.2 68:53.92 redis-server 77999 iobroker 20 0 21.1g 143324 50432 S 5.3 1.7 7:09.31 io.shelly.1 535 iobroker 20 0 21.3g 414704 50048 S 3.0 4.9 38:42.61 io.javascript.0 500 iobroker 20 0 21.1g 141500 45312 S 2.7 1.7 28:42.33 io.influxdb.0 474 iobroker 20 0 21.0g 95884 44672 S 2.3 1.1 24:34.54 io.history.0 844 iobroker 20 0 21.3g 147084 51456 S 1.0 1.8 1:09.11 io.tuya.0 696 iobroker 20 0 21.0g 92612 44800 S 0.7 1.1 1:46.87 io.mqtt.0 232 grafana 20 0 1621988 75456 23680 S 0.3 0.9 1:12.34 grafana 614 iobroker 20 0 21.0g 96740 49792 S 0.3 1.2 3:11.49 io.device-watch 860 iobroker 20 0 21.0g 107276 45440 S 0.3 1.3 3:08.22 io.yahka.0 936 iobroker 20 0 21.0g 81820 44928 S 0.3 1.0 2:57.40 io.energiefluss 958 iobroker 20 0 21.0g 77588 44800 S 0.3 0.9 2:02.99 io.energiefluss 1011 iobroker 20 0 21.1g 100212 46080 S 0.3 1.2 0:24.12 io.iot.0 1031 iobroker 20 0 21.1g 122148 51200 S 0.3 1.5 4:12.21 io.linkeddevice 1096 iobroker 20 0 21.2g 89032 46592 S 0.3 1.1 0:49.04 io.slideshow.0 1136 iobroker 20 0 21.0g 91580 43904 S 0.3 1.1 12:17.99 io.sourceanalyt 99840 mario 20 0 8940 5248 3200 R 0.3 0.1 0:00.03 top 1 root 20 0 21500 12160 9088 S 0.0 0.1 0:00.68 systemd 49 root 19 -1 83788 25192 23920 S 0.0 0.3 0:12.12 systemd-journal 99 systemd+ 20 0 18852 7296 7040 S 0.0 0.1 0:00.12 systemd-network 132 _rpc 20 0 7968 3712 3456 S 0.0 0.0 0:00.05 rpcbind 136 systemd+ 20 0 21456 11520 9984 S 0.0 0.1 0:00.30 systemd-resolve 229 root 20 0 3808 2176 2048 S 0.0 0.0 0:00.10 cron 230 message+ 20 0 9532 4864 4480 S 0.0 0.1 0:00.06 dbus-daemon 233 root 20 0 29416 5504 5248 S 0.0 0.1 0:00.24 networkd-dispat 240 root 20 0 17880 8064 7552 S 0.0 0.1 0:00.15 systemd-logind 244 root 20 0 2732 1536 1536 S 0.0 0.0 0:00.00 agetty 245 root 20 0 6956 4412 3840 S 0.0 0.1 0:00.11 login 254 root 20 0 2732 1664 1664 S 0.0 0.0 0:00.00 agetty 267 syslog 20 0 222508 4736 3840 S 0.0 0.1 0:02.54 rsyslogd 412 root 20 0 42856 4500 4224 S 0.0 0.1 0:00.16 master 414 postfix 20 0 43344 7424 6912 S 0.0 0.1 0:00.03 qmgr 458 iobroker 20 0 21.4g 243488 51456 S 0.0 2.9 5:42.57 io.admin.0 565 iobroker 20 0 21.0g 84344 50176 S 0.0 1.0 0:19.61 io.alarm.0 -
Keine Ahnung, was da los ist.
CPU ist gemäß den dargestellten Prozessen nicht großartig belastet, allerdings zeigt der load etwas anderes.
-
Ich hatte auch Probleme, bei mir lag es daran, dass zu oft Daten an influx geschickt wurden
-
@meister-mopper es gibt ein linux tool namens "iotop" - da funktioniert aber in der Regel nicht in LXC-Containern.... aus der Hypervisor shell aber schon - da sieht man dann auch die Prozesse der Container
https://www.thomas-krenn.com/de/wiki/Linux_I/O_Performance_Messungen_mit_iotop
root@pve:~# iotop -o -b -n 1 Total DISK READ: 0.00 B/s | Total DISK WRITE: 34.93 K/s Current DISK READ: 0.00 B/s | Current DISK WRITE: 104.80 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND 3903119 be/4 root 0.00 B/s 17.47 K/s ?unavailable? dockerd -H fd:// --containerd=/run/containerd/containerd.sock 3904116 be/4 root 0.00 B/s 17.47 K/s ?unavailable? node index.js -
@martinp said in Hohe Schreibaktivitäten am iobroker:
@meister-mopper es gibt ein linux tool namens "iotop" - da funktioniert aber in der Regel nicht in LXC-Containern.... aus der Hypervisor shell aber schon - da sieht man dann auch die Prozesse der Container
https://www.thomas-krenn.com/de/wiki/Linux_I/O_Performance_Messungen_mit_iotop
root@pve:~# iotop -o -b -n 1 Total DISK READ: 0.00 B/s | Total DISK WRITE: 34.93 K/s Current DISK READ: 0.00 B/s | Current DISK WRITE: 104.80 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO COMMAND 3903119 be/4 root 0.00 B/s 17.47 K/s ?unavailable? dockerd -H fd:// --containerd=/run/containerd/containerd.sock 3904116 be/4 root 0.00 B/s 17.47 K/s ?unavailable? node index.jsHallo zusammen
hier mal die Auswertung, liegt am iobroker.js-controller dauerhaft über 3 M/s
Was tun?
Total DISK READ: 0.00 B/s | Total DISK WRITE: 5.98 M/s Current DISK READ: 5.42 K/s | Current DISK WRITE: 6.12 M/s TID PRIO USER DISK READ DISK WRITE> COMMAND 2717 be/4 1000 0.00 B/s 5.89 M/s iobroker.js-controller 8449 be/4 100108 0.00 B/s 24.37 K/s bin/mongod --dbpath /usr/lib/unifi/data/db --port 27117~id --wiredTigerEngineConfigString=cache_size=256M [ftdc] 2183 be/3 root 0.00 B/s 18.96 K/s [jbd2/dm-19-8] 4719 be/4 100000 0.00 B/s 10.83 K/s systemd-journald 9089 be/4 100999 0.00 B/s 8.12 K/s influxd 1104 be/4 root 0.00 B/s 5.42 K/s pmxcfs 1111 be/4 root 0.00 B/s 5.42 K/s pmxcfs 1953 be/4 root 0.00 B/s 5.42 K/s pmxcfs 1747 be/4 100998 0.00 B/s 2.71 K/s pihole-FTL -f 5284 be/4 100000 0.00 B/s 2.71 K/s nmbd --foreground --no-process-group -
@m-schalk schalte doch einmal sukzessive deine Instanzen alle ab. Z.b im ersten Schritt die ersten 50% und schaue ob sich etwas ändert. Den Javascript Adapter würde ich zuerst abschalten.
Was steht denn so im ioBroker log? Läuft eine Instanz im debug oder gar silly log level?
-
@feuersturm @meister-mopper @martinp
Danke für die Hilfestellung, ich habe den "Fehler" gefunden. In der Shelly Instanz hatte ich das "HTTP-Antworten speichern (zum Debuggen)" aktiviert, weil ich probleme hatte Shelly über ipsec zu abzufragen. Man sollte solchen Sachen nicht kurz vor Neujahr aktivieren.
-
... nicht kurz vor Neujahr ...
@m-schalk Teile des Gedächtnisses mit Feuerzangenbowle gelöscht?
-
@m-schalk Danke für die Rückmeldung. Bitte setze noch ein "[gelöst]" in den Titel von deinem ersten Beitrag, dann sieht man, das das Thema abgeschlossen ist.
