Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[mattle1957]

Bitte in der nachfolgenden Übersicht die mit ... bzw x gekennzeichneten Felder ausfüllen und im Anschluss an die Tabelle auf Linux Systemen den Output des Commands iob diag einfügen.

Hinweis: Das Eröffnen eines Issues hier ersetzt NICHT das Anlegen eine Issues im Repository des Adapters. Fehlerbehebungen werden ausschließlich über Issues getrackt.

DANKE

Bitte ausfüllen:

• Adaptername: iobroker
• Link zu Adapterrepository: www.github.com...
• Adapterversion: ...
• js-controller Version: ...
• Admin Version: ...
• Hardwaresystem: NUC, Pi4 ...
• Arbeitsspeicher: 8xGB
• Festplattenart: SD-Karte, SSD, HDD, ...
• Betriebssystem: ...
• Nodejs-Version: v20.19.1
• NPM-Version: 10.8.2
• Installationsart: Skript oder Manuell ?
• Image, Docker genutzt: Ja - Nein
• Ort, Name der Imagedatei: ...

========== Start marking the full check here ===========

Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 12 (bookworm)
 Static hostname: martinpi
       Icon name: computer
          Kernel: Linux 6.12.25+rpt-rpi-v8
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.5
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 11:54:36 up 1 day, 21:39,  2 users,  load average: 0.76, 0.71, 0.51
CPU threads: 4


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'bookworm'!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Wed 2026-01-28 11:54:37 CET
           Universal time: Wed 2026-01-28 10:54:37 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker

User that is running 'js-controller':
js-controller is not running

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Unit display-manager.service could not be found.
Display-Manager:
Desktop:
Session:                tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.2G        274M        6.8G        1.2M        1.2G        7.9G
Swap:           536M          0B        536M
Total:          8.7G        274M        7.3G

Active iob-Instances:   0

         7808 M total memory
          262 M used memory
          489 M active memory
          599 M inactive memory
         6481 M free memory
          154 M buffer memory
         1033 M swap cache
          511 M total swap
            0 M used swap
          511 M free swap

*** top - Table Of Processes  ***
top - 11:54:37 up 1 day, 21:39,  2 users,  load average: 0.76, 0.71, 0.51
Tasks: 172 total,   1 running, 171 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us, 20.0 sy,  0.0 ni, 80.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   7808.4 total,   6481.2 free,    262.0 used,   1188.5 buff/cache
MiB Swap:    512.0 total,    512.0 free,      0.0 used.   7546.4 avail Mem

*** FAILED SERVICES ***

  UNIT           LOAD   ACTIVE SUB    DESCRIPTION
* man-db.service loaded failed failed Daily man-db regeneration

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 ***
3 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for details

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  3.6G     0  3.6G   0% /dev
tmpfs          tmpfs     781M  1.2M  780M   1% /run
/dev/sda2      ext4       56G  8.0G   46G  15% /
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
/dev/sda1      vfat      510M   56M  455M  11% /boot/firmware
tmpfs          tmpfs     781M     0  781M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Mon Jan 26 14:15:01 2026] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  smsc95xx.macaddr=D8:3A:DD:37:EA:4C vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=ttyS0,115200 console=tty1 root=PARTUUID=d619ff03-02 rootfstype=ext4 fsck.repair=yes rootwait
[Mon Jan 26 14:15:11 2026] EXT4-fs (sda2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none.
[Mon Jan 26 14:15:12 2026] EXT4-fs (sda2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. Quota mode: none.
[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2): ext4_get_inode_loc:4548: inode #257337: block 1048787: comm npm ls: unable to read itable block
[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2) in ext4_reserve_inode_write:5829: IO failure
[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2): ext4_ext_tree_init:882: inode #257337: comm npm ls: mark_inode_dirty error

Show mounted filesystems:
TARGET           SOURCE    FSTYPE OPTIONS
/                /dev/sda2 ext4   rw,noatime
`-/boot/firmware /dev/sda1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
2.4G    /var/
1.1G    /var/log/journal/0f704d1235fb4698b0f678460c992efd
1.1G    /var/log/journal
1.1G    /var/log
665M    /var/cache

Archived and active journals take up 1.0G in the file system.

/opt/iobroker/backups:
126M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
286M    /opt/iobroker/iobroker-data/
172M    /opt/iobroker/iobroker-data/files
59M     /opt/iobroker/iobroker-data/backup-objects
47M     /opt/iobroker/iobroker-data/files/admin.admin
46M     /opt/iobroker/iobroker-data/files/admin.admin/custom/assets

The five largest files in iobroker-data are:
24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
11M     /opt/iobroker/iobroker-data/objects.jsonl
9.3M    /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js
8.1M    /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-Djx0nwYT.js
7.2M    /opt/iobroker/iobroker-data/files/ham.admin/static/js/main.8080bc0b.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-FTDI_FT230X_Basic_UART_D200ZYDG-if00-port0

Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v20.19.1
/usr/bin/node           v20.19.1
/usr/bin/npm            10.8.2
/usr/bin/npx            10.8.2
/usr/bin/corepack       0.31.0

nodejs:
  Installed: 20.19.1-1nodesource1
  Candidate: 22.22.0-1nodesource1
  Version table:
     22.22.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.21.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
 *** 20.19.1-1nodesource1 100
        100 /var/lib/dpkg/status
     18.20.4+dfsg-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


██████   █████  ███    ██  ██████  ███████ ███████
██   ██ ██   ██ ████   ██ ██       ██      ██   ██
██   ██ ███████ ██ ██  ██ ██   ███ █████   ███████
██   ██ ██   ██ ██  ██ ██ ██    ██ ██      ██   ██
██████  ██   ██ ██   ████  ██████  ███████ ██   ██


The current Node.js version (v20.19.1) is vulnerable to the following CVEs:

CVE-2025-23166(high):  The C++ method SignTraits::DeriveBits() may incorrectly call ThrowException() based on user-supplied inputs when executing in a background thread, crashing the Node.js process. Such cryptographic operations are commonly applied to untrusted inputs. Thus, this mechanism potentially allows an adversary to remotely crash a Node.js runtime.
Patched versions: ^20.19.2 || ^22.15.1 || ^23.11.1 || ^24.0.2
=

CVE-2025-23167(medium): A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.
This inconsistency enables request smuggling, allowing attackers to bypass proxy-based access controls and submit unauthorized requests.

The issue was resolved by upgrading `llhttp` to version 9, which enforces correct header termination.

Impact:
* This vulnerability affects only Node.js 20.x users prior to the `llhttp` v9 upgrade.

Patched versions: ^20.19.2
=

CVE-2025-55130(high): A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise.
This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

CVE-2025-55131(high): A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.
Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

CVE-2025-55132(low): A flaw in Node.js's permission model allows a file's access and modification timestamps to be changed via `futimes()` even when the process has only read permissions. Unlike `utimes()`, `futimes()` does not apply the expected write-permission checks, which means file metadata can be modified in read-only directories. This behavior could be used to alter timestamps in ways that obscure activity, reducing the reliability of logs. This vulnerability affects users of the permission model on Node.js v20,  v22,  v24, and v25.
Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

CVE-2025-59465(high): A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example:

server.on('secureConnection', socket => {
socket.on('error', err => {
console.log(err)
})
})

Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

CVE-2025-59466(medium): We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.
Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

CVE-2026-21637(medium): A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.
Patched versions: ^20.20.0 || ^22.22.0 || ^24.13.0 || ^25.3.0
=

*** ioBroker-Installation ***

ioBroker Status
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1

Hosts:
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1

Core adapters versions
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1
js-controller:
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1
admin:
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1
javascript:

nodejs modules from github:     1
+-- homebridge-petkit-pet-feeder@3.2.2 (git+ssh://git@github.com/jubepue/homebridge-petkit-pet-feeder.git#83fd5ab0f5bca904898fb7d673264283c5c697db)

Adapter State


Enabled adapters with bindings

ioBroker-Repositories
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1

Installed ioBroker-Adapters
/opt/iobroker/node_modules/yargs-parser/build/index.cjs:796
            else if (o[key] === undefined && i


SyntaxError: Invalid or unexpected token
    at wrapSafe (node:internal/modules/cjs/loader:1472:18)
    at Module._compile (node:internal/modules/cjs/loader:1501:20)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
    at Module.load (node:internal/modules/cjs/loader:1275:32)
    at Module._load (node:internal/modules/cjs/loader:1096:12)
    at Module.require (node:internal/modules/cjs/loader:1298:19)
    at require (node:internal/modules/helpers:182:18)
    at Object.<anonymous> (/opt/iobroker/node_modules/yargs/build/index.cjs:1:60570)
    at Module._compile (node:internal/modules/cjs/loader:1529:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)

Node.js v20.19.1

Objects and States
Please stand by - This may take a while
Objects:        0
States:         0

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Pending Updates: 168

*** 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:22              0.0.0.0:*               LISTEN      0          5705       633/sshd: /usr/sbin
tcp6       0      0 :::22                   :::*                    LISTEN      0          5707       633/sshd: /usr/sbin
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        5673       495/avahi-daemon: r
udp        0      0 0.0.0.0:54654           0.0.0.0:*                           104        5675       495/avahi-daemon: r
udp6       0      0 :::49276                :::*                                104        5676       495/avahi-daemon: r
udp6       0      0 fe80::d507:604:f21e:546 :::*                                0          1006       576/NetworkManager
udp6       0      0 :::5353                 :::*                                104        5674       495/avahi-daemon: r

*** Log File - Last 25 Lines ***

2026-01-24 12:03:15.443  - error: host.martinpi Caught by controller[1]: Error by sending: Error: No reply in 247 seconds.
2026-01-24 12:03:15.443  - info: host.martinpi instance system.adapter.philips-air.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.443  - info: host.martinpi instance system.adapter.ham.1 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.444  - info: host.martinpi instance system.adapter.sonoff.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.444  - info: host.martinpi instance system.adapter.radar2.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.444  - info: host.martinpi instance system.adapter.discovery.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.497  - info: host.martinpi instance system.adapter.energiefluss-erweitert.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.497  - info: host.martinpi instance system.adapter.fiat.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.498  - info: host.martinpi instance system.adapter.fritzdect.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.498  - info: host.martinpi instance system.adapter.go-e.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.498  - info: host.martinpi instance system.adapter.pvforecast.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.498  - warn: host.martinpi instance system.adapter.alpha-ess.0 terminated due to SIGKILL
2026-01-24 12:03:15.498  - info: host.martinpi instance system.adapter.alpha-ess.0 terminated with code null ()
2026-01-24 12:03:15.498  - warn: host.martinpi instance system.adapter.modbus.0 terminated due to SIGKILL
2026-01-24 12:03:15.498  - info: host.martinpi instance system.adapter.modbus.0 terminated with code null ()
2026-01-24 12:03:15.521  - warn: host.martinpi instance system.adapter.web.0 terminated due to SIGKILL
2026-01-24 12:03:15.521  - info: host.martinpi instance system.adapter.web.0 terminated with code null ()
2026-01-24 12:03:15.523  - warn: host.martinpi instance system.adapter.javascript.0 terminated due to SIGKILL
2026-01-24 12:03:15.523  - info: host.martinpi instance system.adapter.javascript.0 terminated with code null ()
2026-01-24 12:03:15.524  - info: host.martinpi instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:15.894  - info: tuya.0 (620274) terminating
2026-01-24 12:03:15.895  - info: tuya.0 (620274) Terminated (NO_ERROR): Without reason
2026-01-24 12:03:16.493  - info: host.martinpi instance system.adapter.tuya.0 terminated with code 0 (NO_ERROR)
2026-01-24 12:03:16.493  - info: host.martinpi All instances are stopped.
2026-01-24 12:03:16.540  - info: host.martinpi terminated

============ Mark until here for C&P =============

[Homoran]

@mattle1957

Gibt es noch irgendwelche weiterführenden Informationen, Beschreibungen o.ä.?

Laut Threadtitel läuft "der Adapter" nicht mehr.
Welcher?

Die entsprechende Tabelle direkt zu Beginn ist nicht ausgefüllt.

Allerdings

@mattle1957 sagte in Adapter läuft nicht mehr:

js-controller is not running

läuft zur Zeit gar nichts.

@mattle1957 sagte in Adapter läuft nicht mehr:

3 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for details

hast du da nachgesehen?

@mattle1957 sagte in Adapter läuft nicht mehr:

Node.js v20.19.1

ist veraltet

die Aussage

@mattle1957 sagte in Adapter läuft nicht mehr:

Operating System is the current Debian stable version codenamed 'bookworm'!

ist auch falsch!
wahrscheinlich auch der checker veraltet.

bei

@mattle1957 sagte in Adapter läuft nicht mehr:

Pending Updates: 168

kein Wunder

[Thomas Braun]

@Homoran sagte in Adapter läuft nicht mehr:

ist auch falsch!
wahrscheinlich auch der checker veraltet.

Jein, der Checker verlässt sich auf die Termine aus dem entsprechenden Paket (dist-info-data (oder so ähnlich)). Aber wenn die nie aktualisiert werden (siehe Pending Updates: 168) bekommst du da eine falsche Aussage, bzw. eine, die auf einem alten Stand beruht.

@mattle1957
Dringend die Kiste komplett auf Stand bringen.

iob stop
sudo apt update
sudo apt full-upgrade
sudo reboot

Dann im frisch gestarteten System:

iob stop 
iob fix
iob start
~~iob nodejs-update~~ <- Nicht erforderlich, die Quelle für 22 ist angelegt, es wurde aber nie das Paket eingespielt. 

Und dann mit dem sanierten Setup nochmal ein

iob diag

[Thomas Braun]

@mattle1957 sagte in Adapter läuft nicht mehr:

Der eigentliche Grund für dein Problem ist aber:

[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2): ext4_get_inode_loc:4548: inode #257337: block 1048787: comm npm ls: unable to read itable block
[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2) in ext4_reserve_inode_write:5829: IO failure
[Wed Jan 28 11:54:26 2026] EXT4-fs error (device sda2): ext4_ext_tree_init:882: inode #257337: comm npm ls: mark_inode_dirty error

Dateisystem gegrillt.
Neuen Datenträger, neues System (RaspberryOS 13 'Trixie') drauf, ioBroker 'leer' installieren, Backup einspielen, fertig.