Protokoll 2 Rot, Protokoll-Liste leer
-
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
iob logs | grep error
da bin ich leider nicht Fit genug
läuft auf einem Docker im Container -
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
Ich würde da ja auch nicht debug oder gar silly als LogLevel laufen haben.
sondern?
-
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
Ich würde da ja auch nicht debug oder gar silly als LogLevel laufen haben.
sondern?
Im Normalbetrieb info oder warn oder error.
Je nachdem wie gesprächig die Adapter sind.
Du willst ja nicht jeden Mumpitz im Log sehen. -
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
iob logs | grep error
da bin ich leider nicht Fit genug
läuft auf einem Docker im Container@Maddin77 sagte in Protokoll 2 Rot, Protokoll-Liste leer:
da bin ich leider nicht Fit genug
Für eine Terminal-Session wird es ja wohl hoffentlich reichen. Ist ja absolutes Basis-Wissen.
-
@Maddin77 sagte in Protokoll 2 Rot, Protokoll-Liste leer:
da bin ich leider nicht Fit genug
Für eine Terminal-Session wird es ja wohl hoffentlich reichen. Ist ja absolutes Basis-Wissen.
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
@Maddin77 sagte in Protokoll 2 Rot, Protokoll-Liste leer:
da bin ich leider nicht Fit genug
Für eine Terminal-Session wird es ja wohl hoffentlich reichen. Ist ja absolutes Basis-Wissen.
tja, sorry
ich bekomme nicht mal das Terminal zum laufen im IOBroker, daher kann ich die Befehle nicht eingeben -
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
@Maddin77 sagte in Protokoll 2 Rot, Protokoll-Liste leer:
da bin ich leider nicht Fit genug
Für eine Terminal-Session wird es ja wohl hoffentlich reichen. Ist ja absolutes Basis-Wissen.
tja, sorry
ich bekomme nicht mal das Terminal zum laufen im IOBroker, daher kann ich die Befehle nicht eingebenMacht man ja auch eben nicht von 'im ioBroker' sondern mit einem Terminal von EXTERN.
Per puTTY oder PowerShell oder sonst einem Terminal.Irgendwie musste ja auch in deinen Container reinkommen?
-
Macht man ja auch eben nicht von 'im ioBroker' sondern mit einem Terminal von EXTERN.
Per puTTY oder PowerShell oder sonst einem Terminal.Irgendwie musste ja auch in deinen Container reinkommen?
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
Macht man ja auch eben nicht von 'im ioBroker' sondern mit einem Terminal von EXTERN.
Per puTTY oder PowerShell oder sonst einem Terminal.Irgendwie musste ja auch in deinen Container reinkommen?
über das Synology NAS läuft das alles
aber in dem Terminal fenster hab ich noch nichts gemacht -
@Thomas-Braun sagte in Protokoll 2 Rot, Protokoll-Liste leer:
Macht man ja auch eben nicht von 'im ioBroker' sondern mit einem Terminal von EXTERN.
Per puTTY oder PowerShell oder sonst einem Terminal.Irgendwie musste ja auch in deinen Container reinkommen?
über das Synology NAS läuft das alles
aber in dem Terminal fenster hab ich noch nichts gemacht -
@Maddin77 sagte: in dem Terminal fenster hab ich noch nichts gemacht
Wie hast du ioBroker installiert?
@paul53 sagte in Protokoll 2 Rot, Protokoll-Liste leer:
@Maddin77 sagte: in dem Terminal fenster hab ich noch nichts gemacht
Wie hast du ioBroker installiert?
über den Container vom Synology läuft das alles
in dem Terminal vom Container passiert aber nichts mit der Zeile -
Hallo
kann mir hier nochmal jemand weiter helfen
ich würde gerne Wissen wo die Fehler her kommen
wie gesagt, die Adapter laufen alle auf Fehler Alles
aber von den Adapter hat keiner einen Fehler der auf diese Rote Zahl eine Auswirkung hat.
aktuell läuft admin V7.7.22
IOBroker image auf dem Synology Docker ist von Gestern latest.
War aber schon davor und immer noch das Thema -
Hallo
kann mir hier nochmal jemand weiter helfen
ich würde gerne Wissen wo die Fehler her kommen
wie gesagt, die Adapter laufen alle auf Fehler Alles
aber von den Adapter hat keiner einen Fehler der auf diese Rote Zahl eine Auswirkung hat.
aktuell läuft admin V7.7.22
IOBroker image auf dem Synology Docker ist von Gestern latest.
War aber schon davor und immer noch das ThemaWir warten immer noch auf gescheite Ausgaben aus dem Terminal.
Z. B. voniob logs | grep error -
Wir warten immer noch auf gescheite Ausgaben aus dem Terminal.
Z. B. voniob logs | grep error -
Wir warten immer noch auf gescheite Ausgaben aus dem Terminal.
Z. B. voniob logs | grep errordas sollte ich soweit geschafft haben, sofern das richtig ist
Und keine Bildchen von Text...
Kopier das in CodeTags eingebettet hier rein.
Und auch einen Lauf voniob diag -
Und keine Bildchen von Text...
Kopier das in CodeTags eingebettet hier rein.
Und auch einen Lauf voniob diagUnd keine Bildchen von Text...
Kopier das in CodeTags eingebettet hier rein.
Und auch einen Lauf voniob diagjs controller not runnig ist rot
-
Und keine Bildchen von Text...
Kopier das in CodeTags eingebettet hier rein.
Und auch einen Lauf voniob diagjs controller not runnig ist rot
-
Und keine Bildchen von Text...
Kopier das in CodeTags eingebettet hier rein.
Und auch einen Lauf voniob diagjs controller not runnig ist rot
Du sollst den vollständigen Output hier reinkopieren...
-
Du sollst den vollständigen Output hier reinkopieren...
-
Start marking the full check here =========== ```bash Script v.2026-06-01 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64bit Docker : v11.1.0 Virtualization : Docker Kernel : x86_64 Userland : 64bit Installation date unknown (filesystem does not support birth time). Systemuptime and Load: 13:49:39 up 33 days, 3:43, 0 user, load average: 1.55, 2.52, 2.37 CPU threads : 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Jun 13 11:49:39 UTC 2026 Sat Jun 13 13:49:39 CEST 2026 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: System has not been booted with systemd as init system (P ID 1). Can't operate. Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 18G 4.2G 6.3G 91M 10G 14G Swap: 13G 853M 12G Total: 32G 5.1G 18G Active iob-Instances: 1 17836 M total memory 4031 M used memory 3206 M active memory 3269 M inactive memory 6043 M free memory 9 M buffer memory 9890 M swap cache 12751 M total swap 814 M used swap 11937 M free swap *** top - Table Of Processes *** top - 13:49:40 up 33 days, 3:43, 0 user, load average: 1.55, 2.52, 2.37 Tasks: 8 total, 1 running, 7 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 17836.1 total, 6042.3 free, 4032.8 used, 9900.2 buff/cache MiB Swap: 12751.9 total, 11937.6 free, 814.3 used. 13803.4 avail Mem *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 8.8G 0 8.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% /opt/iobroker /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% /etc/hosts Messages concerning filesystems in dmesg: sudo: unable to resolve host buanet-iobroker-10: Name or service not known [Sat Jun 13 12:20:45 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=460] [progress=0] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=460] [free_extent_called_cnt =32213] [reclaimed_extent_cnt=6253] [reclaimed_bytes=228802560] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=459] [progress=0] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=459] [free_extent_called_cnt =19286] [reclaimed_extent_cnt=1514] [reclaimed_bytes=24805376] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=448] [progress=0] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=448] [free_extent_called_cnt =19285] [reclaimed_extent_cnt=1512] [reclaimed_bytes=24772608] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=447] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=447] [free_extent_called_cnt =30862] [reclaimed_extent_cnt=29501] [reclaimed_bytes=1549664256] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=446] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=446] [free_extent_called_cnt =1351] [reclaimed_extent_cnt=125] [reclaimed_bytes=2048000] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=445] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=445] [free_extent_called_cnt =1352] [reclaimed_extent_cnt=133] [reclaimed_bytes=2142208] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=444] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=444] [free_extent_called_cnt =2850] [reclaimed_extent_cnt=2850] [reclaimed_bytes=84811776] Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/vg1/volume_1[/@syno/@docker/btrfs/subvolumes/43a974fc38db 15f975b91ba96caa43ab78f61b14e5ada776465c66010bdd8214] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=481,subvol=/@syno/@docker/btrfs/subvolumes/43a9 74fc38db15f975b91ba96caa43ab78f61b14e5ada776465c66010bdd8214 |-/opt/iobroker /dev/vg1/volume_1[/@syno/docker/iobroker_data_10] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=262,subvol=/@syno/docker |-/etc/resolv.conf /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/resolv.conf] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno |-/etc/hostname /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/hostname] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno `-/etc/hosts /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/hosts] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno Files in neuralgic directories: /var: sudo: unable to resolve host buanet-iobroker-10: Name or service not known 16M /var/ 14M /var/lib/dpkg 14M /var/lib 13M /var/lib/dpkg/info 1.9M /var/cache /opt/iobroker/backups: 199M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 540M /opt/iobroker/iobroker-data/ 333M /opt/iobroker/iobroker-data/files 133M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 40M /opt/iobroker/iobroker-data/states.jsonl 35M /opt/iobroker/iobroker-data/objects.jsonl 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41ce e985.js.map 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.j s.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------------------- ---------------------------- ------ zigbee.0 tcp://192.168.178.221:6638 - tcp ^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A *** NodeJS-Installation *** /usr/bin/nodejs v22.22.3 /usr/bin/node v22.22.3 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct ^[[A^[[A^[[Anodejs: Installed: 22.22.3-1nodesource1 Candidate: 22.22.3-1nodesource1 Version table: *** 22.22.3-1nodesource1 100 100 /var/lib/dpkg/status Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host buanet-iobroker-10: Name or service not known ioBroker Status iobroker is not running on this host. Objects type: jsonl States type: jsonl Hosts: ^[[Abuanet-iobroker-10 buanet-iobroker-10 (version: 7.1.2, hostname: buanet-iobr oker-10, dead, uptime: 4488) Core adapters versions^[[A js-controller: 7 admin: 7.7.22 javascript: 9.0.18 nodejs modules from github: 0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬─ ─────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼─ ─────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴─ ─────────────┘ Active repo(s): stable Upgrade policy: none ioBroker-Adapter Versions and update status Used repository: stable Adapter "admin" : 7.8.23 , installed 7.7.22 [Updatable] Adapter "backitup" : 3.3.17 , installed 3.3.14 [Updatable] Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 3.1.0 , installed 1.9.2 [Updatable] Adapter "evcc" : 0.2.4 , installed 0.2.4 Adapter "fb-checkpresence": 1.4.2 , installed 1.4.2 Adapter "go-e" : 1.0.41 , installed 1.0.41 Adapter "growatt" : 3.3.1 , installed 3.3.1 Adapter "gruenbeck" : 0.0.43 , installed 0.0.43 Adapter "hmip" : 1.27.0 , installed 1.27.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.1.2 , installed 7.1.2 Adapter "melcloud" : 3.0.4 , installed 3.0.3 [Updatable] Adapter "modbus" : 8.0.3 , installed 7.0.6 [Updatable] Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "oilfox" : 4.3.1 , installed 4.3.1 Adapter "openweathermap": 1.4.0 , installed 1.4.0 Adapter "pushover" : 5.0.0 , installed 5.0.0 Adapter "pvforecast" : 6.1.0 , installed 5.1.0 [Updatable] Adapter "sainlogic" : 1.2.3 , installed 1.2.3 Adapter "smartgarden" : 2.0.1 , installed 2.0.1 Adapter "socketio" : 7.1.3 , installed 7.0.8 [Updatable] Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-hqwidgets": 1.6.1 , installed 1.5.1 [Updatable] Adapter "vis-icontwo" : 2.11.3 , installed 2.11.1 [Updatable] Adapter "vis-inventwo" : 4.1.0 , installed 3.3.5 [Updatable] Adapter "vis-jqui-mfd" : 1.1.3 , installed 1.1.1 [Updatable] Adapter "vis-material" : 0.2.0 , installed 0.2.0 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 8.0.0 , installed 7.0.8 [Updatable] Adapter "ws" : 4.1.0 , installed 3.0.19 [Updatable] Adapter "zigbee" : 3.3.5 , installed 3.3.5 Objects and States Please stand by - This may take a while Objects: 22804 States: 21493 *** OS-Repositories and Updates *** sudo: unable to resolve host buanet-iobroker-10: Name or service not known sudo: unable to resolve host buanet-iobroker-10: Name or service not known Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Log File - Last 25 Lines *** 2026-06-13 13:49:05.970 - info: pushover.0 (263) terminating 2026-06-13 13:49:05.971 - debug: pushover.0 (263) Plugin sentry destroyed 2026-06-13 13:49:05.971 - info: pushover.0 (263) terminating 2026-06-13 13:49:05.972 - info: pushover.0 (263) Terminated (NO_ERROR): Without reason 2026-06-13 13:49:05.986 - info: modbus.0 (361) terminating 2026-06-13 13:49:05.987 - debug: modbus.0 (361) Plugin sentry destroyed 2026-06-13 13:49:05.987 - info: modbus.0 (361) terminating 2026-06-13 13:49:05.987 - info: modbus.0 (361) Terminated (NO_ERROR): Without re ason 2026-06-13 13:49:06.257 - info: tr-064.0 (475) terminating 2026-06-13 13:49:06.289 - info: javascript.0 (228) terminating 2026-06-13 13:49:06.291 - info: javascript.0 (228) terminating 2026-06-13 13:49:06.458 - info: influxdb.10 (200) terminating 2026-06-13 13:49:06.459 - debug: influxdb.10 (200) Plugin sentry destroyed 2026-06-13 13:49:06.459 - info: influxdb.10 (200) Terminated (NO_ERROR): Without reason 2026-06-13 13:49:06.800 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.803 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.861 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.891 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:06.897 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:06.899 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:14.491 - info: zigbee.0 (504) zigbecontroller stopped successfu lly 2026-06-13 13:49:14.491 - info: zigbee.0 (504) cleanup successful 2026-06-13 13:49:14.491 - info: zigbee.0 (504) terminating 2026-06-13 13:49:14.492 - debug: zigbee.0 (504) Plugin sentry destroyed 2026-06-13 13:49:14.492 - warn: zigbee.0 (504) Terminated (UNCAUGHT_EXCEPTION): Without reason ============= Mark until here for C&P ============= iob diag has finished. -
Start marking the full check here =========== ```bash Script v.2026-06-01 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : 64bit Docker : v11.1.0 Virtualization : Docker Kernel : x86_64 Userland : 64bit Installation date unknown (filesystem does not support birth time). Systemuptime and Load: 13:49:39 up 33 days, 3:43, 0 user, load average: 1.55, 2.52, 2.37 CPU threads : 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Sat Jun 13 11:49:39 UTC 2026 Sat Jun 13 13:49:39 CEST 2026 CEST +0200 Etc/UTC *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: Unknown Display-Manager: System has not been booted with systemd as init system (P ID 1). Can't operate. Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 18G 4.2G 6.3G 91M 10G 14G Swap: 13G 853M 12G Total: 32G 5.1G 18G Active iob-Instances: 1 17836 M total memory 4031 M used memory 3206 M active memory 3269 M inactive memory 6043 M free memory 9 M buffer memory 9890 M swap cache 12751 M total swap 814 M used swap 11937 M free swap *** top - Table Of Processes *** top - 13:49:40 up 33 days, 3:43, 0 user, load average: 1.55, 2.52, 2.37 Tasks: 8 total, 1 running, 7 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 17836.1 total, 6042.3 free, 4032.8 used, 9900.2 buff/cache MiB Swap: 12751.9 total, 11937.6 free, 814.3 used. 13803.4 avail Mem *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 8.8G 0 8.8G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% /opt/iobroker /dev/vg1/volume_1 btrfs 3.5T 630G 2.9T 18% /etc/hosts Messages concerning filesystems in dmesg: sudo: unable to resolve host buanet-iobroker-10: Name or service not known [Sat Jun 13 12:20:45 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=460] [progress=0] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=460] [free_extent_called_cnt =32213] [reclaimed_extent_cnt=6253] [reclaimed_bytes=228802560] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=459] [progress=0] [Sat Jun 13 12:21:16 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=459] [free_extent_called_cnt =19286] [reclaimed_extent_cnt=1514] [reclaimed_bytes=24805376] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=448] [progress=0] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=448] [free_extent_called_cnt =19285] [reclaimed_extent_cnt=1512] [reclaimed_bytes=24772608] [Sat Jun 13 12:21:30 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=447] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=447] [free_extent_called_cnt =30862] [reclaimed_extent_cnt=29501] [reclaimed_bytes=1549664256] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=446] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=446] [free_extent_called_cnt =1351] [reclaimed_extent_cnt=125] [reclaimed_bytes=2048000] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=445] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=445] [free_extent_called_cnt =1352] [reclaimed_extent_cnt=133] [reclaimed_bytes=2142208] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot started [fs_ id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=444] [progress=0] [Sat Jun 13 12:21:32 2026] BTRFS notice (device dm-1): Drop snapshot finished [fs _id=308b1cd3-85db-4ba3-bea6-87850a608e4a] [subvol_id=444] [free_extent_called_cnt =2850] [reclaimed_extent_cnt=2850] [reclaimed_bytes=84811776] Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/vg1/volume_1[/@syno/@docker/btrfs/subvolumes/43a974fc38db 15f975b91ba96caa43ab78f61b14e5ada776465c66010bdd8214] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=481,subvol=/@syno/@docker/btrfs/subvolumes/43a9 74fc38db15f975b91ba96caa43ab78f61b14e5ada776465c66010bdd8214 |-/opt/iobroker /dev/vg1/volume_1[/@syno/docker/iobroker_data_10] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=262,subvol=/@syno/docker |-/etc/resolv.conf /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/resolv.conf] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno |-/etc/hostname /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/hostname] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno `-/etc/hosts /dev/vg1/volume_1[/@syno/@docker/containers/8592f71120acd7f4c9 9606a75aa6591348b82441b01816da179e6ac031c2d24d/hosts] btrfs rw,nodev,relat ime,ssd,synoacl,space_cache=v2,auto_reclaim_space,metadata_ratio=50,block_group_c ache_tree,syno_allocator,subvolid=256,subvol=/@syno Files in neuralgic directories: /var: sudo: unable to resolve host buanet-iobroker-10: Name or service not known 16M /var/ 14M /var/lib/dpkg 14M /var/lib 13M /var/lib/dpkg/info 1.9M /var/cache /opt/iobroker/backups: 199M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 540M /opt/iobroker/iobroker-data/ 333M /opt/iobroker/iobroker-data/files 133M /opt/iobroker/iobroker-data/backup-objects 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 40M /opt/iobroker/iobroker-data/states.jsonl 35M /opt/iobroker/iobroker-data/objects.jsonl 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41ce e985.js.map 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.j s.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** ZigBee Settings *** ⚠ HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: tcp Zigbee Network Settings on your coordinator / in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** === ZigBee Port Overview === Instance Configured Port Available by-id Port Status -------- ---------------------------- ---------------------------- ------ zigbee.0 tcp://192.168.178.221:6638 - tcp ^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A *** NodeJS-Installation *** /usr/bin/nodejs v22.22.3 /usr/bin/node v22.22.3 /usr/bin/npm 10.9.8 /usr/bin/npx 10.9.8 ✓ Node.js installation is correct ^[[A^[[A^[[Anodejs: Installed: 22.22.3-1nodesource1 Candidate: 22.22.3-1nodesource1 Version table: *** 22.22.3-1nodesource1 100 100 /var/lib/dpkg/status Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: sudo: unable to resolve host buanet-iobroker-10: Name or service not known ioBroker Status iobroker is not running on this host. Objects type: jsonl States type: jsonl Hosts: ^[[Abuanet-iobroker-10 buanet-iobroker-10 (version: 7.1.2, hostname: buanet-iobr oker-10, dead, uptime: 4488) Core adapters versions^[[A js-controller: 7 admin: 7.7.22 javascript: 9.0.18 nodejs modules from github: 0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬─ ─────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼─ ─────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴─ ─────────────┘ Active repo(s): stable Upgrade policy: none ioBroker-Adapter Versions and update status Used repository: stable Adapter "admin" : 7.8.23 , installed 7.7.22 [Updatable] Adapter "backitup" : 3.3.17 , installed 3.3.14 [Updatable] Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 3.1.0 , installed 1.9.2 [Updatable] Adapter "evcc" : 0.2.4 , installed 0.2.4 Adapter "fb-checkpresence": 1.4.2 , installed 1.4.2 Adapter "go-e" : 1.0.41 , installed 1.0.41 Adapter "growatt" : 3.3.1 , installed 3.3.1 Adapter "gruenbeck" : 0.0.43 , installed 0.0.43 Adapter "hmip" : 1.27.0 , installed 1.27.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.1.2 , installed 7.1.2 Adapter "melcloud" : 3.0.4 , installed 3.0.3 [Updatable] Adapter "modbus" : 8.0.3 , installed 7.0.6 [Updatable] Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "oilfox" : 4.3.1 , installed 4.3.1 Adapter "openweathermap": 1.4.0 , installed 1.4.0 Adapter "pushover" : 5.0.0 , installed 5.0.0 Adapter "pvforecast" : 6.1.0 , installed 5.1.0 [Updatable] Adapter "sainlogic" : 1.2.3 , installed 1.2.3 Adapter "smartgarden" : 2.0.1 , installed 2.0.1 Adapter "socketio" : 7.1.3 , installed 7.0.8 [Updatable] Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-hqwidgets": 1.6.1 , installed 1.5.1 [Updatable] Adapter "vis-icontwo" : 2.11.3 , installed 2.11.1 [Updatable] Adapter "vis-inventwo" : 4.1.0 , installed 3.3.5 [Updatable] Adapter "vis-jqui-mfd" : 1.1.3 , installed 1.1.1 [Updatable] Adapter "vis-material" : 0.2.0 , installed 0.2.0 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 8.0.0 , installed 7.0.8 [Updatable] Adapter "ws" : 4.1.0 , installed 3.0.19 [Updatable] Adapter "zigbee" : 3.3.5 , installed 3.3.5 Objects and States Please stand by - This may take a while Objects: 22804 States: 21493 *** OS-Repositories and Updates *** sudo: unable to resolve host buanet-iobroker-10: Name or service not known sudo: unable to resolve host buanet-iobroker-10: Name or service not known Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending systemupdates: 0 *** Log File - Last 25 Lines *** 2026-06-13 13:49:05.970 - info: pushover.0 (263) terminating 2026-06-13 13:49:05.971 - debug: pushover.0 (263) Plugin sentry destroyed 2026-06-13 13:49:05.971 - info: pushover.0 (263) terminating 2026-06-13 13:49:05.972 - info: pushover.0 (263) Terminated (NO_ERROR): Without reason 2026-06-13 13:49:05.986 - info: modbus.0 (361) terminating 2026-06-13 13:49:05.987 - debug: modbus.0 (361) Plugin sentry destroyed 2026-06-13 13:49:05.987 - info: modbus.0 (361) terminating 2026-06-13 13:49:05.987 - info: modbus.0 (361) Terminated (NO_ERROR): Without re ason 2026-06-13 13:49:06.257 - info: tr-064.0 (475) terminating 2026-06-13 13:49:06.289 - info: javascript.0 (228) terminating 2026-06-13 13:49:06.291 - info: javascript.0 (228) terminating 2026-06-13 13:49:06.458 - info: influxdb.10 (200) terminating 2026-06-13 13:49:06.459 - debug: influxdb.10 (200) Plugin sentry destroyed 2026-06-13 13:49:06.459 - info: influxdb.10 (200) Terminated (NO_ERROR): Without reason 2026-06-13 13:49:06.800 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.803 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.861 - warn: zigbee.0 (504) Cannot connect/reconnect to state s DB. Stopping adapter. 2026-06-13 13:49:06.891 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:06.897 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:06.899 - warn: influxdb.10 (200) Cannot connect/reconnect to st ates DB. Stopping adapter. 2026-06-13 13:49:14.491 - info: zigbee.0 (504) zigbecontroller stopped successfu lly 2026-06-13 13:49:14.491 - info: zigbee.0 (504) cleanup successful 2026-06-13 13:49:14.491 - info: zigbee.0 (504) terminating 2026-06-13 13:49:14.492 - debug: zigbee.0 (504) Plugin sentry destroyed 2026-06-13 13:49:14.492 - warn: zigbee.0 (504) Terminated (UNCAUGHT_EXCEPTION): Without reason ============= Mark until here for C&P ============= iob diag has finished.Als erstes bringste mal die ganzen ioBroker-Adapter auf Stand
iob update iob upgrade all -yMIt welchem Treminalprogramm greifst du da zu? puTTY?
-
Als erstes bringste mal die ganzen ioBroker-Adapter auf Stand
iob update iob upgrade all -yMIt welchem Treminalprogramm greifst du da zu? puTTY?
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden653
Online33.0k
Benutzer83.2k
Themen1.3m
Beiträge