@codierknecht
Ich versuche es mal morgen. Ich hoffe die Infos genügen. Bin Anfänger und mache alles über portainer.io
Danke auf jeden Fall.
M
Latest posts made by mjohn
-
RE: IoBroker und Docker auf dem selben Piposted in ioBroker Allgemein
-
RE: IoBroker und Docker auf dem selben Piposted in ioBroker Allgemein
@codierknecht
Ich habe den Container als 'host' eingerichtet.Wie mappe ich den Port. Zu hoch für meine Linuxkenntnisse.
Danke schon mal.
-
RE: IoBroker und Docker auf dem selben Piposted in ioBroker Allgemein
Dürfte ich auf die Themenstellung zurück kommen.
Ich habe eine neue iobroker Installation auf einem RasPi4 8Gb RAM und größerer M.2 SSD. Läuft soweit gut.
Jetzt habe ich auf dem gleichen RasPi4 Docker mit dem iobroker Container [buanet/ioBroker.docker] installiert.
-
Frage: der Status wird direkt nach der Installation von als 'unhealthy' angezeigt.
Kann ich da was fixen? -
Sollte sich der Status ändern (s.o.) oder auch so sicher zu betreiben sein stellt sich die Frage, wie kann ich iobroker starten? Der RasPi hat ja die gleiche IP Adresse, wie der iobroker Container auf dem PasPi und beide den gleichen Port:8081.
Jetzt schon mal vielen Dank.
-
-
RE: IOB Migration von Rock64 auf RasPi4posted in Installation
@thomas-braun
Hi Thomas,
danke für die schnelle Antwort.Hat soweit geklappt. Zumindest sieht es aus wie früher
Jetzt noch neuer Zigbee Koordinator, dann is gut für den Anfang.Vielen Dank.
-
IOB Migration von Rock64 auf RasPi4posted in Installation
Liebe Gemeinde,
Wahrscheinlich wurde dieses oder ein vergleichbares Thema schon mehrfach diskutiert, ich konnte jedoch keine 'Umzugshilfe' oder Empfehlung finden.
Wie im Thema geschrieben wollte ich mein System von Rock64 auf RasPi4 'umziehen', ohne alles neu aufsetzen zu müssen. Über die Zeit sammelt sich doch einiges an Anpassungen (Skripte, Userdata, Kommandos etc.)an, die ich nicht erneut aufsetzen wollte.
Das Rock64 System meldet sich an mitDebian Armbian 23.8.1 bullsey with Armbian Linux 4.4.192-rockchip64Rock64 läuft und Debian sowie IOB ist auf dem neuesten Stand. Derzeit mit 2x Zigbee (Texas_Instruments_TI_CC2531, SONOFF_Zigbee_3.0_USB_Dongle_Plus (E)_V2 an USB Ports)
Das PasPi4 System (Argon ONE M.2 mit SD Karte und M.2 SSD) liegt unbespielt noch vor mir.
Dort sollte dann der SONOFF_Zigbee_3.0_USB_Dongle_Plus-P angeschlossen werden.Welcher Weg wird empfohlen? Gibt es dafür eine Anleitung für 'Dummies'?
Würde das Klonen des Rock64 SD beim Rock64 laufen?Jetzt schon einmal mehr vielen Dank für jegliche Hilfe. Ich nehme alles, was ich bekomme...
-
RE: Probleme mit zRam auf Rock64posted in Off Topic
@thomas-braun sagte in Probleme mit zRam auf Rock64:
iob diag
Gerne, hier die Langversion
======== Start marking the full check here ========= Skript v.2023-04-16 *** BASE SYSTEM *** Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 13:37:41 up 10 days, 18:05, 1 user, load average: 0.39, 0.43, 0.45 CPU threads: 4 *** Time and Time Zones *** Local time: Sat 2023-08-12 13:37:41 CEST Universal time: Sat 2023-08-12 11:37:41 UTC RTC time: Sat 2023-08-12 11:37:42 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: n/a RTC in local TZ: no *** User and Groups *** pi /home/pi pi dialout sudo audio video plugdev systemd-journal input netdev ssh iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 4.0G 1.8G 1.5G 43M 702M 2.0G Swap: 1.0G 0B 1.0G Total: 5.0G 1.8G 2.5G 3988 M total memory 1819 M used memory 2184 M active memory 211 M inactive memory 1466 M free memory 201 M buffer memory 501 M swap cache 1023 M total swap 0 M used swap 1023 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 2.0G 0 2.0G 0% /dev tmpfs tmpfs 399M 41M 359M 11% /run /dev/mmcblk0p1 ext4 56G 5.8G 48G 11% / 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% /tmp /dev/zram0 ext4 49M 48M 0 100% /var/log tmpfs tmpfs 399M 0 399M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Aug 12 13:15:27 2023] EXT4-fs warning: 2 callbacks suppressed [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error: 2 callbacks suppressed [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:15:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:15:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:30:27 2023] EXT4-fs warning: 2 callbacks suppressed [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error: 2 callbacks suppressed [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Aug 12 13:30:27 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Aug 12 13:30:27 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p1 ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600,data=ordered |-/var/log.hdd /dev/mmcblk0p1[/var/log] ext4 rw,noatime,nodiratime,errors=remount-ro,commit=600,data=ordered `-/var/log /dev/zram0 ext4 rw,relatime,discard Files in neuralgic directories: /var: 1.5G /var/ 1.1G /var/cache/apt 1.1G /var/cache 937M /var/cache/apt/archives 358M /var/lib Journal file /var/log/journal/f2f10dbdc16b4a0c88d6af121e6d1d50/system.journal is truncated, ignoring file. Archived and active journals take up 87.2M in the file system. /opt/iobroker/backups: 27M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 233M /opt/iobroker/iobroker-data/ 196M /opt/iobroker/iobroker-data/files 72M /opt/iobroker/iobroker-data/files/telegram.admin 52M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/telegram.admin/custom/static/js The five largest files in iobroker-data are: 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.0M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js 7.2M /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 6.9M /opt/iobroker/iobroker-data/files/telegram.admin/custom/static/js/vendors-node_modules_mui_icons-material_esm_index_js.8fdf8cb7.chunk.js.map *** NodeJS-Installation *** /usr/bin/nodejs v18.17.0 /usr/bin/node v18.17.0 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 nodejs: Installed: 18.17.0-deb-1nodesource1 Candidate: 18.17.0-deb-1nodesource1 Version table: *** 18.17.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 7.0.3 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : ioBroker-Rock - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.backitup.0 : backitup : ioBroker-Rock - enabled + system.adapter.cloud.0 : cloud : ioBroker-Rock - enabled + system.adapter.discovery.0 : discovery : ioBroker-Rock - enabled + system.adapter.history.0 : history : ioBroker-Rock - enabled system.adapter.ical.0 : ical : ioBroker-Rock - enabled + system.adapter.javascript.0 : javascript : ioBroker-Rock - enabled + system.adapter.modbus.0 : modbus : ioBroker-Rock - enabled + system.adapter.ping.0 : ping : ioBroker-Rock - enabled + system.adapter.pvforecast.0 : pvforecast : ioBroker-Rock - enabled + system.adapter.pvforecast.1 : pvforecast : ioBroker-Rock - enabled + system.adapter.signal-cmb.0 : signal-cmb : ioBroker-Rock - enabled + system.adapter.signal-cmb.1 : signal-cmb : ioBroker-Rock - enabled system.adapter.smartmeter.0 : smartmeter : ioBroker-Rock - disabled + system.adapter.socketio.0 : socketio : ioBroker-Rock - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.telegram.0 : telegram : ioBroker-Rock - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : ioBroker-Rock - enabled + system.adapter.trashschedule.0 : trashschedule : ioBroker-Rock - enabled + system.adapter.tuya.0 : tuya : ioBroker-Rock - enabled + system.adapter.web.0 : web : ioBroker-Rock - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : ioBroker-Rock - enabled + system.adapter.whatsapp-cmb.1 : whatsapp-cmb : ioBroker-Rock - enabled + system.adapter.zigbee.0 : zigbee : ioBroker-Rock - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ECE257-if00 + system.adapter.zigbee.1 : zigbee : ioBroker-Rock - enabled, port: /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220708080640-if00 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : ioBroker-Rock - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.socketio.0 : socketio : ioBroker-Rock - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.telegram.0 : telegram : ioBroker-Rock - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : ioBroker-Rock - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : ioBroker-Rock - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ECE257-if00 + system.adapter.zigbee.1 : zigbee : ioBroker-Rock - enabled, port: /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220708080640-if00 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "backitup" : 2.6.23 , installed 2.6.23 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "ical" : 1.13.3 , installed 1.13.3 Adapter "javascript" : 7.0.3 , installed 7.0.3 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "modbus" : 5.0.11 , installed 5.0.11 Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "pushover" : 3.0.3 , installed 3.0.3 Adapter "pvforecast" : 2.7.1 , installed 2.7.1 Adapter "signal-cmb" : 0.3.0 , installed 0.3.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "smartmeter" : 3.3.4 , installed 3.3.4 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "telegram" : 1.16.0 , installed 1.16.0 Adapter "text2command" : 3.0.2 , installed 3.0.2 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "tuya" : 3.14.2 , installed 3.14.2 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.23 , installed 1.8.16 [Updatable] Objects and States Please stand by - This may take a while Objects: 1467 States: 1148 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://deb.nodesource.com/node_18.x bullseye InRelease Hit:5 http://mirrors.xtom.de/armbian bullseye InRelease Reading package lists... Pending Updates: 9 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 15328 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 19840 910/sshd: /usr/sbin tcp 0 0 127.0.0.1:1883 0.0.0.0:* LISTEN 110 18892 905/mosquitto tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 21771 848/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 19074 848/iobroker.js-con tcp6 0 0 :::111 :::* LISTEN 0 15330 1/init tcp6 0 0 :::8081 :::* LISTEN 1001 20123 1169/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 20371 1516/io.web.0 tcp6 0 0 :::8084 :::* LISTEN 1001 20405 1532/io.socketio.0 tcp6 0 0 :::22 :::* LISTEN 0 19851 910/sshd: /usr/sbin tcp6 0 0 ::1:1883 :::* LISTEN 110 18893 905/mosquitto udp 0 0 0.0.0.0:111 0.0.0.0:* 0 15329 1/init udp 0 0 192.168.178.45:123 0.0.0.0:* 0 20935 1258/ntpd udp 0 0 127.0.0.1:123 0.0.0.0:* 0 20933 1258/ntpd udp 0 0 0.0.0.0:123 0.0.0.0:* 0 20929 1258/ntpd udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 22209 1415/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 22210 1415/io.tuya.0 udp6 0 0 :::111 :::* 0 15331 1/init udp6 0 0 fe80::8d9b:2c4a:d7d:123 :::* 0 20939 1258/ntpd udp6 0 0 ::1:123 :::* 0 20937 1258/ntpd udp6 0 0 :::123 :::* 0 20926 1258/ntpd *** Log File - Last 25 Lines *** 2023-08-12 09:14:23.440 - warn: javascript.0 (319772) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:2757:34) 2023-08-12 09:14:23.441 - warn: javascript.0 (319772) at listOnTimeout (node:internal/timers:569:17) 2023-08-12 09:14:23.441 - warn: javascript.0 (319772) at processTimers (node:internal/timers:512:7) 2023-08-12 09:14:23.453 - info: javascript.0 (319772) State value to set for "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" has to be type "string" but received type "boolean" 2023-08-12 11:50:36.937 - error: cloud.0 (1501) Ping timeout 2023-08-12 11:51:37.184 - info: cloud.0 (1501) Trying to connect as system.user.admin to cloud 2023-08-12 11:51:37.391 - info: cloud.0 (1501) Connection changed: connect 2023-08-12 12:28:26.788 - warn: javascript.0 (319772) You are assigning a boolean to the state "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" which expects a string. Please fix your code to use a string or change the state type to boolean. This warning might become an error in future versions. 2023-08-12 12:28:26.795 - warn: javascript.0 (319772) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1730:20) 2023-08-12 12:28:26.796 - warn: javascript.0 (319772) at Object.<anonymous> (script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_wieder_ZU:9:7) 2023-08-12 12:28:26.798 - warn: javascript.0 (319772) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:2757:34) 2023-08-12 12:28:26.804 - warn: javascript.0 (319772) at listOnTimeout (node:internal/timers:569:17) 2023-08-12 12:28:26.805 - warn: javascript.0 (319772) at processTimers (node:internal/timers:512:7) 2023-08-12 12:28:27.146 - info: javascript.0 (319772) State value to set for "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" has to be type "string" but received type "boolean" 2023-08-12 12:52:58.470 - warn: javascript.0 (319772) You are assigning a boolean to the state "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" which expects a string. Please fix your code to use a string or change the state type to boolean. This warning might become an error in future versions. 2023-08-12 12:52:58.477 - warn: javascript.0 (319772) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1730:20) 2023-08-12 12:52:58.478 - warn: javascript.0 (319772) at Object.<anonymous> (script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_wieder_ZU:9:7) 2023-08-12 12:52:58.479 - warn: javascript.0 (319772) at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:2757:34) 2023-08-12 12:52:58.479 - warn: javascript.0 (319772) at listOnTimeout (node:internal/timers:569:17) 2023-08-12 12:52:58.480 - warn: javascript.0 (319772) at processTimers (node:internal/timers:512:7) 2023-08-12 12:52:58.492 - info: javascript.0 (319772) State value to set for "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" has to be type "string" but received type "boolean" 2023-08-12 13:12:29.628 - info: admin.0 (1169) ==> Connected system.user.admin from ::ffff:192.168.178.137 2023-08-12 13:13:09.449 - info: admin.0 (1169) ==> Connected system.user.admin from ::ffff:192.168.178.137 2023-08-12 13:13:26.343 - info: admin.0 (1169) <== Disconnect system.user.admin from ::ffff:192.168.178.137 admin 2023-08-12 13:13:26.347 - info: admin.0 (1169) <== Disconnect system.user.admin from ::ffff:192.168.178.137 javascript ============ Mark until here for C&P ============= iob diag has finished.Zur Fehlermeldung
2023-08-12 12:52:58.492 - info: javascript.0 (319772) State value to set for "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min" has to be type "string" but received type "boolean"Dies sind die Objektdaten von
0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min{ "common": { "name": "Garagentor offen > 15Min", "desc": "Manuell erzeugt", "role": "state", "type": "string", "read": true, "write": true, "def": "" }, "type": "state", "native": {}, "from": "system.adapter.admin.0", "user": "system.user.admin", "ts": 1691235156599, "_id": "0_userdata.0.Datenpunkte.Statusänderung.Türen/Fenster.Garagentor_offen___15Min", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" } }Ich habe beide Javaskripte gestoppt und neu gestartet, danach kam keine Fehlermeldung (auch nicht im Skript selbst
12.8.2023, 13:56:24.749 [info ]: javascript.0 (319772) Stop script script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:26.357 [info ]: javascript.0 (319772) Start javascript script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:26.409 [info ]: javascript.0 (319772) script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 12.8.2023, 13:56:31.602 [info ]: javascript.0 (319772) Stop script script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:43.158 [info ]: javascript.0 (319772) Start javascript script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:43.210 [info ]: javascript.0 (319772) script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptions 12.8.2023, 13:56:57.793 [info ]: javascript.0 (319772) Stop script script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:59.948 [info ]: javascript.0 (319772) Start javascript script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min 12.8.2023, 13:56:59.961 [info ]: javascript.0 (319772) script.js.common.allg__Skripte.Status_Fenster_Türen.Garagentor_offen___15Min: registered 1 subscription, 0 schedules, 0 messages, 0 logs and 0 file subscriptionsIch hoffe, das hilft etwas weiter.
Jetzt schon mal DANKE -
RE: Probleme mit zRam auf Rock64posted in Off Topic
Leider ist immer noch zram0 voll
pi@ioBroker-Rock:~$ df -h Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf udev 2,0G 0 2,0G 0% /dev tmpfs 399M 41M 359M 11% /run /dev/mmcblk0p1 56G 5,9G 48G 11% / tmpfs 2,0G 0 2,0G 0% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 2,0G 0 2,0G 0% /tmp /dev/zram0 49M 48M 0 100% /var/log tmpfs 399M 0 399M 0% /run/user/0 tmpfs 399M 0 399M 0% /run/user/1000Irgend eine Idee, wie ich mehr Speicher zuweisen kann, um die 'Füllgeschwindigkeit' zu überwachen?
Ist es notwendig, diesen zram0 überhaupt zu haben? Kann ich ihne ohne Probleme deaktivieren? Deinstallieren?
-
RE: Probleme mit zRam auf Rock64posted in Off Topic
@Homoran
Danke für das Verschieben. Nimmt etwas die Spannung aus der Kommunikation. -
RE: Probleme mit zRam auf Rock64posted in Off Topic
@djmarc75
und insbesondere
@special_bEs tut mir leid, dass es so aussieht, ich hätte einen Beitrag gekapert. Das war sicher nicht meine Absicht. Da ich nicht weiß, wie ich einen Moderator kontaktiere, der meine Beiträge von hier in einen neuen Thread überführt, werde ich einen Neuen mit Header zram aufmachen.
@Homoran
Ja, es ist kein MacMini, sondern ein Rock64Sorry, mein Fehler,
LG -
RE: Probleme mit zRam auf Rock64posted in Off Topic
@dp20eic
Nachdf -hfolgendes ausgeworfen. Also läuft das log voll...
pi@ioBroker-Rock:~$ df -h Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf udev 2,0G 0 2,0G 0% /dev tmpfs 399M 41M 359M 11% /run /dev/mmcblk0p1 56G 5,8G 48G 11% / tmpfs 2,0G 0 2,0G 0% /dev/shm tmpfs 5,0M 4,0K 5,0M 1% /run/lock tmpfs 2,0G 0 2,0G 0% /tmp /dev/zram0 49M 48M 0 100% /var/log tmpfs 399M 0 399M 0% /run/user/0 tmpfs 399M 0 399M 0% /run/user/1000Nach
iob diagGibt es folglich wieder bergeweise Fehler
[Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 8192 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 12288 [Sat Jul 22 12:45:12 2023] EXT4-fs warning (device zram0): ext4_dirent_csum_verify:353: inode #11: comm find: No space for directory leaf checksum. Please run e2fsck -D. [Sat Jul 22 12:45:12 2023] EXT4-fs error (device zram0): ext4_readdir:189: inode #11: comm find: path /var/log/lost+found: directory fails checksum at offset 4096eigentlich ist ja mein System von der Stange, da mir die Expertise einfach fehlt, selbst kreativ zu werden. Wie der zram sich hier und auch in welcher Größe einnisten konnte entzieht sich meiner Kenntnis.
Hier noch ein paar Ergebnisse der gegebenen Befehle:
pi@ioBroker-Rock:~$ sudo du -kx /var/log | sort -nk1,1 4 /var/log/apt 4 /var/log/mosquitto 4 /var/log/ntpstats 4 /var/log/private 4 /var/log/runit/ssh 4 /var/log/sysstat 4 /var/log/unattended-upgrades 8 /var/log/runit 16 /var/log/lost+found 48476 /var/log/journal/f2f10dbdc16b4a0c88d6af121e6d1d50 48480 /var/log/journal 48532 /var/logpi@ioBroker-Rock:~$ sudo ncdu / 1,9 GiB [##########] /opt 1,5 GiB [######## ] /usr 1,5 GiB [####### ] /var 324,0 MiB [# ] /home 287,1 MiB [# ] /root 153,9 MiB [ ] /lib 45,5 MiB [ ] /boot 40,8 MiB [ ] /run 14,6 MiB [ ] /bin 12,1 MiB [ ] /sbin 4,1 MiB [ ] /etc 12,0 KiB [ ] /media e 4,0 KiB [ ] /srv e 4,0 KiB [ ] /selinux e 4,0 KiB [ ] /mnt e 4,0 KiB [ ] /lost+found 0,0 B [ ] /sys . 0,0 B [ ] /proc 0,0 B [ ] /dev 0,0 B [ ] /tmppi@ioBroker-Rock:~$ sudo journalctl [sudo] Passwort für pi: Journal file /var/log/journal/f2f10dbdc16b4a0c88d6af121e6d1d50/user-1001@000600c 4682b6de0-aef09967e6f9ec74.journal~ is truncated, ignoring file. -- Journal begins at Fri 2022-10-14 17:35:20 CEST, ends at Sat 2023-07-22 13:35>nach
pi@ioBroker-Rock:~$ sudo journalctl --flush --rotate --vacuum-time=1h [sudo] Passwort für pi: Journal file /var/log/journal/f2f10dbdc16b4a0c88d6af121e6d1d50/user-1001@000600c 4682b6de0-aef09967e6f9ec74.journal~ is truncated, ignoring file. Vacuuming done, freed 0B of archived journals from /var/log/journal. Vacuuming done, freed 0B of archived journals from /run/log/journal.danach
pi@ioBroker-Rock:~$ sudo journalctl Journal file /var/log/journal/f2f10dbdc16b4a0c88d6af121e6d1d50/system.journal is truncated, ignoring file. -- Journal begins at Sat 2023-07-22 12:41:34 CEST, ends at Sat 2023-07-22 14:30:09 CEST. -- Jul 22 12:41:34 ioBroker-Rock rsyslogd[617]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/> Jul 22 12:41:34 ioBroker-Rock rsyslogd[617]: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ] Jul 22 12:41:34 ioBroker-Rock rsyslogd[617]: action 'action-1-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2102.0 try https://www.rsyslog.com/e/> Jul 22 12:41:34 ioBroker-Rock rsyslogd[617]: file '/var/log/syslog'[8] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2102.0 try https://www.rsyslog.com/e/2027 ]wieder bergeweise diese error Zeilen
Ist mir viel zu komplex für ein System, das mit etwas Linux Kenntnissen einfach laufen sollte. Ich weiss nicht weiter, was mit dem zram schief läuft, und warum /var/log ständig voll ist.....
