Backitup stört LAN Verbindung

Laser

Habe seit den letzten Updates (System aktuell) das Problem, daß nach etwa 13 Minuten nach Start von BackItup iObroker nicht mehr im Netz erreichbar ist. Das System selbst - Scripte etc. scheint aber weiter zu arbeiten. Habe jetzt 4 verschiedene Zeiten getestet. Beim automatischen Start von BackItup passiert das. Beim manuellen Start läuft das System durch. Nur ein Aus/Einschalten des Raspi hilft.
Hat jemand dieses gleiche Problem?

Meister Mopper

@Laser

Klingt nach zuwenig RAM. Was sagt iob diag ?

Laser

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

```bash
Script v.2026-01-31

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: neuheizung
       Icon name: computer
          Kernel: Linux 6.18.29+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:06:11 up 32 min,  1 user,  load average: 0.72, 0.82, 0.82
CPU threads: 4


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

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

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Mon 2026-05-25 11:06:11 CEST
           Universal time: Mon 2026-05-25 09:06:11 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

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

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
SUDO_HOME=/home/otto
GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c

*** 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        2.8G        4.3G         14M        1.1G        5.3G
Swap:           209M          0B        209M
Total:          8.4G        2.8G        4.5G

Active iob-Instances:   27

         7818 M total memory
         2717 M used memory
         3119 M active memory
          387 M inactive memory
         4127 M free memory
          113 M buffer memory
          965 M swap cache
          199 M total swap
            0 M used swap
          199 M free swap

*** top - Table Of Processes  ***
top - 11:06:12 up 32 min,  1 user,  load average: 0.72, 0.82, 0.82
Tasks: 205 total,   1 running, 204 sleeping,   0 stopped,   0 zombie
%Cpu(s): 24.4 us,  6.7 sy,  0.0 ni, 66.7 id,  0.0 wa,  0.0 hi,  2.2 si,  0.0 st
MiB Mem :   7818.8 total,   4127.4 free,   2717.7 used,   1079.2 buff/cache
MiB Swap:    200.0 total,    200.0 free,      0.0 used.   5101.1 avail Mem

*** FAILED SERVICES ***

  UNIT LOAD ACTIVE SUB DESCRIPTION

0 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  3.6G     0  3.6G   0% /dev
tmpfs          tmpfs     1.6G   12M  1.6G   1% /run
/dev/sda2      ext4      110G   25G   80G  24% /
tmpfs          tmpfs     3.9G     0  3.9G   0% /dev/shm
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
tmpfs          tmpfs     3.9G  2.8M  3.9G   1% /tmp
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/sda1      vfat      510M   75M  436M  15% /boot/firmware
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     782M  8.0K  782M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Mon May 25 10:34:08 2026] EXT4-fs (sda2): mounted filesystem 6835594d-a5f3-459f-a244-318060e7e0ab ro with ordered data mode. Quota mode: none.
[Mon May 25 10:34:10 2026] EXT4-fs (sda2): re-mounted 6835594d-a5f3-459f-a244-318060e7e0ab r/w.

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:
3.5G    /var/
1.9G    /var/lib
1.7G    /var/lib/influxdb/engine/data/7b6dd0929a6bb818/autogen
1.7G    /var/lib/influxdb/engine/data/7b6dd0929a6bb818
1.7G    /var/lib/influxdb/engine/data

Archived and active journals take up 1009.6M in the file system.

/opt/iobroker/backups:
4.4G    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
8.4G    /opt/iobroker/iobroker-data/
7.9G    /opt/iobroker/iobroker-data/history
374M    /opt/iobroker/iobroker-data/files
176M    /opt/iobroker/iobroker-data/files/vis-2
141M    /opt/iobroker/iobroker-data/files/vis-2/assets

The five largest files in iobroker-data are:
34M     /opt/iobroker/iobroker-data/files/vis-2/assets/index-DqJdyjgH.js.map
34M     /opt/iobroker/iobroker-data/files/vis-2/assets/index-CrLrNq4s.js.map
29M     /opt/iobroker/iobroker-data/objects.jsonl
13M     /opt/iobroker/iobroker-data/files/vis-2/assets/index-BsqTzvub.js.map
9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json

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-VictronEnergy_BV_VE_Direct_cable_VE82E1IJ-if00-port0
/dev/serial/by-id/usb-1a86_USB2.0-Ser_-if00-port0

*** ZigBee Settings ***

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         v22.22.0
/usr/bin/node           v22.22.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4

✓ Node.js installation is correct

nodejs:
  Installed: 22.22.0-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
        100 /var/lib/dpkg/status
     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.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.6-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.5-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.4-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.3-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.2+dfsg-1+deb13u2 500
        500 http://deb.debian.org/debian trixie/main arm64 Packages
        500 http://deb.debian.org/debian-security trixie-security/main arm64 Packages
     20.19.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.3-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.2-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
     20.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_20.x nodistro/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 (v22.22.0) is vulnerable to the following CVEs:

CVE-2026-21637(high): A flaw in Node.js TLS error handling leaves `SNICallback` invocations unprotected against synchronous exceptions, while the equivalent ALPN and PSK callbacks were already addressed in CVE-2026-21637. This represents an incomplete fix of that prior vulnerability.

When an `SNICallback` throws synchronously on unexpected input the exception bypasses TLS error handlers and propagates as an uncaught exception, crashing the Node.js process.

* This vulnerability affects all Node.js versions that received the CVE-2026-21637 fix, including **20.x, 22.x, 24.x, and 25.x**, on any TLS server where `SNICallback` may throw on unexpected `servername` input.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21710(high): A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`.

When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`.

* This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21713(medium): A flaw in Node.js HMAC verification uses a non-constant-time comparison when validating user-provided signatures, potentially leaking timing information proportional to the number of matching bytes. Under certain threat models where high-resolution timing measurements are possible, this behavior could be exploited as a timing oracle to infer HMAC values.

Node.js already provides timing-safe comparison primitives used elsewhere in the codebase, indicating this is an oversight rather than an intentional design decision.

This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21714(medium): A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up.

This vulnerability affects HTTP2 users on Node.js 20, 22, 24 and 25.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21715(low): A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync.native()` without the required read permission checks, while all comparable filesystem functions correctly enforce them.

As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync.native()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.

This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-read` is intentionally restricted.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21716(low): An incomplete fix for CVE-2024-36137 leaves `FileHandle.chmod()` and `FileHandle.chown()` in the promises API without the required permission checks, while their callback-based equivalents (`fs.fchmod()`, `fs.fchown()`) were correctly patched.

As a result, code running under `--permission` with restricted `--allow-fs-write` can still use promise-based `FileHandle` methods to modify file permissions and ownership on already-open file descriptors, bypassing the intended write restrictions.

This vulnerability affects **20.x, 22.x, 24.x, and 25.x** processes using the Permission Model where `--allow-fs-write` is intentionally restricted.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

CVE-2026-21717(medium): A flaw in V8's string hashing mechanism causes integer-like strings to be hashed to their numeric value, making hash collisions trivially predictable. By crafting a request that causes many such collisions in V8's internal string table, an attacker can significantly degrade performance of the Node.js process.

The most common trigger is any endpoint that calls `JSON.parse()` on attacker-controlled input, as JSON parsing automatically internalizes short strings into the affected hash table.

This vulnerability affects **20.x, 22.x, 24.x, and 25.x**.
Patched versions: ^20.20.2 || ^22.22.2 || ^24.14.1 || ^25.8.2
=

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Hosts:
debian11            debian11 (version: 4.0.24, hostname: debian11      , dead, uptime: 198)
neuheizung          neuheizung (version: 7.0.7, hostname: neuheizung    , alive, uptime: 1919)

Core adapters versions
js-controller:  7.0.7
admin:          7.8.23
javascript:     9.0.18

nodejs modules from github:     1
+-- iobroker.vedirect@0.3.3 (git+ssh://git@github.com/DrozmotiX/ioBroker.vedirect.git#0a83b8b987ee94d0c49f2ee7299bbb8d5d329dde)

Adapter State
+ system.adapter.admin.1                  : admin                 : neuheizung                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.alias-manager.0          : alias-manager         : neuheizung                               - disabled
+ system.adapter.backitup.0               : backitup              : neuheizung                               -  enabled
+ system.adapter.discovery.0              : discovery             : neuheizung                               -  enabled
+ system.adapter.echarts.0                : echarts               : neuheizung                               -  enabled
+ system.adapter.email.0                  : email                 : neuheizung                               -  enabled
  system.adapter.flot.0                   : flot                  : neuheizung                               - disabled
+ system.adapter.history.0                : history               : neuheizung                               -  enabled
+ system.adapter.hm-rega.0                : hm-rega               : neuheizung                               -  enabled
+ system.adapter.hm-rpc.0                 : hm-rpc                : neuheizung                               -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : neuheizung                               -  enabled, port: 0
  system.adapter.i2c.0                    : i2c                   : neuheizung                               - disabled
+ system.adapter.influxdb.0               : influxdb              : neuheizung                               -  enabled, port: 8086
+ system.adapter.javascript.0             : javascript            : neuheizung                               -  enabled
+ system.adapter.modbus.0                 : modbus                : neuheizung                               -  enabled
+ system.adapter.mqtt.0                   : mqtt                  : neuheizung                               -  enabled, port: 1886, bind: 0.0.0.0
+ system.adapter.opendtu.0                : opendtu               : neuheizung                               -  enabled
+ system.adapter.opendtu.1                : opendtu               : neuheizung                               -  enabled
+ system.adapter.opendtu.2                : opendtu               : neuheizung                               -  enabled
+ system.adapter.owfs.0                   : owfs                  : neuheizung                               -  enabled, port: 4304
+ system.adapter.rpi2.0                   : rpi2                  : neuheizung                               -  enabled
+ system.adapter.shelly.0                 : shelly                : neuheizung                               -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.shelly.1                 : shelly                : neuheizung                               -  enabled, port: 1884, bind: 0.0.0.0
+ system.adapter.shuttercontrol.0         : shuttercontrol        : neuheizung                               -  enabled
+ system.adapter.simple-api.0             : simple-api            : neuheizung                               -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sourceanalytix.0         : sourceanalytix        : neuheizung                               -  enabled
+ system.adapter.vedirect.0               : vedirect              : neuheizung                               -  enabled
+ system.adapter.vis-2.0                  : vis-2                 : neuheizung                               -  enabled
  system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : neuheizung                               -  enabled
  system.adapter.vis-material.0           : vis-material          : neuheizung                               - disabled
  system.adapter.vis-metro.0              : vis-metro             : neuheizung                               -  enabled
+ system.adapter.web.0                    : web                   : neuheizung                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

+ instance is alive

Enabled adapters with bindings
+ system.adapter.admin.1                  : admin                 : neuheizung                               -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.hm-rpc.0                 : hm-rpc                : neuheizung                               -  enabled, port: 0
+ system.adapter.hm-rpc.1                 : hm-rpc                : neuheizung                               -  enabled, port: 0
+ system.adapter.influxdb.0               : influxdb              : neuheizung                               -  enabled, port: 8086
+ system.adapter.mqtt.0                   : mqtt                  : neuheizung                               -  enabled, port: 1886, bind: 0.0.0.0
+ system.adapter.owfs.0                   : owfs                  : neuheizung                               -  enabled, port: 4304
+ system.adapter.shelly.0                 : shelly                : neuheizung                               -  enabled, port: 1882, bind: 0.0.0.0
+ system.adapter.shelly.1                 : shelly                : neuheizung                               -  enabled, port: 1884, bind: 0.0.0.0
+ system.adapter.simple-api.0             : simple-api            : neuheizung                               -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0                    : web                   : neuheizung                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin

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

Installed ioBroker-Adapters
Used repository: stable
Adapter    "admin"        : 7.8.23   , installed 7.8.23
Adapter    "alias-manager": 2.1.0    , installed 2.1.0
Adapter    "backitup"     : 3.3.14   , installed 3.3.14
Adapter    "discovery"    : 5.0.0    , installed 5.0.0
Adapter    "echarts"      : 3.1.0    , installed 3.1.0
Adapter    "email"        : 2.0.4    , installed 2.0.4
Adapter    "history"      : 4.0.0    , installed 4.0.0
Adapter    "hm-rega"      : 5.1.0    , installed 5.1.0
Adapter    "hm-rpc"       : 3.0.1    , installed 3.0.1
Adapter    "i2c"          : 1.2.1    , installed 1.2.1
Adapter    "influxdb"     : 4.0.2    , installed 4.0.2
Adapter    "javascript"   : 9.0.18   , installed 9.0.18
Controller "js-controller": 7.0.7    , installed 7.0.7
Adapter    "modbus"       : 8.0.3    , installed 8.0.3
Adapter    "mqtt"         : 6.1.4    , installed 6.1.4
Adapter    "opendtu"      : 3.1.0    , installed 3.1.0
Adapter    "owfs"         : 0.7.0    , installed 0.7.0
Adapter    "rpi2"         : 3.0.2    , installed 3.0.2
Adapter    "shelly"       : 10.6.1   , installed 10.6.1
Adapter    "shuttercontrol": 2.0.12  , installed 2.0.12
Adapter    "simple-api"   : 3.0.7    , installed 3.0.7
Adapter    "socketio"     : 7.1.3    , installed 7.1.3
Adapter    "vis"          : 1.5.6    , installed 1.5.6
Adapter    "vis-2"        : 2.13.8   , installed 2.13.17
Adapter    "vis-colorpicker": 2.1.0  , installed 2.1.0
Adapter    "vis-hqwidgets": 1.6.1    , installed 1.6.1
Adapter    "vis-material" : 0.2.0    , installed 0.2.0
Adapter    "vis-metro"    : 1.2.0    , installed 1.2.0
Adapter    "web"          : 8.0.0    , installed 8.0.0
Adapter    "ws"           : 4.0.0    , installed 4.0.0

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

*** OS-Repositories and Updates ***
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:36:57Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_20.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:44:55Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:36:57Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:44:55Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Some index files failed to download. They have been ignored, or old ones used instead.
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian-security trixie-security InRelease
Hit:3 http://archive.raspberrypi.com/debian trixie InRelease
Hit:4 http://deb.debian.org/debian trixie-updates InRelease
Hit:5 https://apt.grafana.com stable InRelease
Get:6 https://deb.nodesource.com/node_22.x nodistro InRelease [12.1 kB]
Err:6 https://deb.nodesource.com/node_22.x nodistro InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:36:57Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Get:7 https://deb.nodesource.com/node_20.x nodistro InRelease [12.1 kB]
Err:7 https://deb.nodesource.com/node_20.x nodistro InRelease
  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:44:55Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Get:8 https://repos.influxdata.com/debian stable InRelease [6922 B]
Fetched 6922 B in 0s (14.6 kB/s)
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:36:57Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_20.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:44:55Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:36:57Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Failed to fetch https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease  Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-04-30T12:44:55Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
W: Some index files failed to download. They have been ignored, or old ones used instead.
Pending systemupdates: 5

*** 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 192.168.2.32:2001       0.0.0.0:*               LISTEN      1001       11605      1607/io.hm-rpc.1
tcp        0      0 192.168.2.32:2010       0.0.0.0:*               LISTEN      1001       8293       1301/io.hm-rpc.0
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          5927       1100/exim4
tcp        0      0 0.0.0.0:1882            0.0.0.0:*               LISTEN      1001       10005      1851/io.shelly.0
tcp        0      0 0.0.0.0:1886            0.0.0.0:*               LISTEN      1001       10043      1976/io.mqtt.0
tcp        0      0 0.0.0.0:1884            0.0.0.0:*               LISTEN      1001       8906       1938/io.shelly.1
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          7017       840/sshd: /usr/sbin
tcp        0      0 0.0.0.0:9001            0.0.0.0:*               LISTEN      1001       8039       1166/iobroker.js-co
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      1001       8200       1166/iobroker.js-co
tcp6       0      0 :::8082                 :::*                    LISTEN      1001       10111      2059/io.web.0
tcp6       0      0 :::8081                 :::*                    LISTEN      1001       8459       1334/io.admin.1
tcp6       0      0 :::8087                 :::*                    LISTEN      1001       8986       2021/io.simple-api.
tcp6       0      0 :::8086                 :::*                    LISTEN      999        5947       855/influxd
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          5928       1100/exim4
tcp6       0      0 :::3000                 :::*                    LISTEN      106        8060       1165/grafana
tcp6       0      0 :::22                   :::*                    LISTEN      0          7019       840/sshd: /usr/sbin
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        4704       604/avahi-daemon: r
udp        0      0 0.0.0.0:48242           0.0.0.0:*                           104        4706       604/avahi-daemon: r
udp6       0      0 fe80::75d1:70aa:4ea:546 :::*                                0          7967       734/NetworkManager
udp6       0      0 :::5353                 :::*                                104        4705       604/avahi-daemon: r
udp6       0      0 :::52008                :::*                                104        4707       604/avahi-daemon: r

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

2026-05-25 11:01:26.089  - warn: modbus.0 (8448) [DevID_1/holdingRegs] Block 0-2: {}
2026-05-25 11:01:35.359  - info: javascript.0 (1514) script.js.Solar.Hoymiles-Limit260: start JavaScript (Javascript/js)
2026-05-25 11:01:35.382  - info: javascript.0 (1514) script.js.Solar.Hoymiles-Limit260: registered 0 subscriptions, 0 schedules, 0 messages, 0 logs and 0 file subscriptions
2026-05-25 11:02:05.460  - info: javascript.0 (1514) script.js.Solar.Hoymiles-Limit260: Stopping script
2026-05-25 11:02:32.101  - warn: modbus.0 (8448) Error: undefined
2026-05-25 11:02:32.102  - error: modbus.0 (8448) Request timed out.
2026-05-25 11:02:32.103  - warn: modbus.0 (8448) Can not write value 19000: Error: timeout
2026-05-25 11:02:48.555  - info: admin.1 (1334) <== Disconnect system.user.admin from ::ffff:192.168.2.5 admin
2026-05-25 11:02:48.560  - info: admin.1 (1334) <== Disconnect system.user.admin from ::ffff:192.168.2.5 admin
2026-05-25 11:02:48.902  - info: admin.1 (1334) ==> Connected system.user.admin from ::ffff:192.168.2.5
2026-05-25 11:02:49.109  - info: admin.1 (1334) ==> Connected system.user.admin from ::ffff:192.168.2.5
2026-05-25 11:03:38.112  - warn: modbus.0 (8448) Error: undefined
2026-05-25 11:03:38.113  - error: modbus.0 (8448) Request timed out.
2026-05-25 11:03:38.114  - warn: modbus.0 (8448) Can not write value 19000: Error: timeout
2026-05-25 11:04:44.121  - warn: modbus.0 (8448) Error: undefined
2026-05-25 11:04:44.121  - error: modbus.0 (8448) Request timed out.
2026-05-25 11:04:44.122  - warn: modbus.0 (8448) Can not write value 19000: Error: timeout
2026-05-25 11:05:50.132  - warn: modbus.0 (8448) Error: undefined
2026-05-25 11:05:50.133  - error: modbus.0 (8448) Request timed out.
2026-05-25 11:05:50.133  - warn: modbus.0 (8448) Can not write value 19000: Error: timeout
2026-05-25 11:06:56.140  - warn: modbus.0 (8448) Error: undefined
2026-05-25 11:06:56.142  - error: modbus.0 (8448) Request timed out.
2026-05-25 11:06:56.142  - warn: modbus.0 (8448) Can not write value 19000: Error: timeout
2026-05-25 11:07:08.130  - warn: host.neuheizung "system.host.debian11" is offline
2026-05-25 11:07:08.361  - warn: host.neuheizung "system.host.debian11" is offline

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


Debian11 ist nur ein Testsystem- nicht angeschlossen. Anlage läuft störungsfrei über Monate. Bis jetzt.

Homoran

@Laser sagte:

Systemuptime and Load:
11:06:11 up 32 min

Wie kommst du auf die Idee, dass backup dein LAN Verbindung stören könnte?

Dein Server ist vor 32 Minuten neu gestartet.

@Laser sagte:

Nur ein Aus/Einschalten des Raspi hilft.

Wie "schaltest" du aus?
Wobei "hilft" das ausschalten?
was heisst iobroker sei nicht mehr zu erreichen?

Thomas Braun

@Laser

Zunächst bringst du das Ding auf einen aktuellen Stand...

iob nodejs-update 22

und die Rückfragen bejahen. Dann

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

Laser

Ich schalte verbotenerweise durch Abziehen der Stromversorgung aus.
Das "Ausschalten" hilft mir (!) , IObroker wieder über das Netzwerk zu erreichen.
Nicht erreichen heißt, kein Ping auf die IP möglich, in FritzBox Ansicht nicht zu sehen.
Werde jetzt ein "Full-upgrade machen. Danach noch mal automatisches Backup starten.

Thomas Braun

@Laser sagte:

Das "Ausschalten" hilft mir (!) , IObroker wieder über das Netzwerk zu erreichen.

Das hilft dir höchstens dabei, das System komplett zu zerdeppern.

Am Rande: Was willst du denn eigentlich mit

Debian11 ist nur ein Testsystem

testen? Das Ding ist ja komplett abgesoffen, da testest du gar nichts sinnvolles mehr drauf.

Laser

Hast Du einen anderen Vorschlag, wie ich das System wieder erreiche?
"Testsystem" -damit habe ich eben verschiedene Dinge getestet. Abgetrennt seit ca.
2 Jahren ohne Probleme.

Thomas Braun

@Laser sagte:

Hast Du einen anderen Vorschlag, wie ich das System wieder erreiche?

Vorher eine Verbindung per SSH aufbauen oder abwarten, bis der Hobel wieder erreichbar ist.

Laser

Wenn ich über SSH draufkommen würde, müßte ich die Spannungsversorgung nicht unterbrechen...

Thomas Braun

@Laser

Deswegen ja vorher per SSH einloggen. Die Verbindung wird als allerletztes gekappt, wenn es eng wird.

Wie groß sind die einzelen Backups? Bei

/opt/iobroker/backups:
4.4G    /opt/iobroker/backups/

muss da ja einiges drin eingebacken werden.

Laser

So, jetzt ist das Backup wieder gestartet worden und die Kiste ist wieder nicht zu erreichen. Was kann ich tun?
Das Backup ist groß. Aber schon über längere Zeit ohne Probleme. Es war schon sehr viel größer.

Thomas Braun

@Laser sagte:

Das Backup ist groß.

Das vermute ich.

Aber schon über längere Zeit ohne Probleme.

Jetzt aber nicht mehr.

Thomas Braun

@Laser sagte:

Was kann ich tun?

Abwarten, bis das Backup erledigt ist.

Thomas Braun

@Laser

Was sagt denn

ls -lh /opt/iobroker/backups/

Laser

Reichen 5++ Stunden? Als das Backup um 2 Uhr gestartet wurde und ich 9 Uhr nachgesehen hatte, war das System nicht zu erreichen...
ls -lh /opt/iobroker/backups/ - ich komme ja nicht über SSH drauf!

Thomas Braun

@Laser

Dann mach dir vorher eine SSH-Session auf und schau da z. B. in

sudo dmesg -wT

was der Kernel meldet, wenn das Backup ausgelöst wird.

Laser

tto@neuheizung:~ $ ls -lh /opt/iobroker/backups/
total 4.4G
-rw-rw-r--+ 1 iobroker iobroker  28K Feb 11 02:14 grafana_2026_02_11-02_14_22_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  26K Feb 22 02:14 grafana_2026_02_22-02_14_42_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  28K Feb 23 02:14 grafana_2026_02_23-02_14_30_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  28K Feb 23 16:07 grafana_2026_02_23-16_07_40_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  29K May 24 10:17 grafana_2026_05_24-10_17_04_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 509M Feb 22 02:14 historyDB_2026_02_22-02_06_53_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker    0 Feb 22 16:47 historyDB_2026_02_22-16_47_42_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 509M Feb 23 02:14 historyDB_2026_02_23-02_06_45_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 510M Feb 23 16:07 historyDB_2026_02_23-16_00_02_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 549M May 24 10:17 historyDB_2026_05_24-10_07_39_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 778M Feb 11 02:06 influxDB_2026_02_11-02_00_28_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 794M Feb 22 02:06 influxDB_2026_02_22-02_00_28_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 797M Feb 23 02:06 influxDB_2026_02_23-02_00_29_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 4.2M Feb 11 02:00 iobroker_2026_02_11-02_00_20_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 4.2M Feb 22 02:00 iobroker_2026_02_22-02_00_20_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 4.2M Feb 22 16:45 iobroker_2026_02_22-16_45_08_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker 4.2M Feb 23 02:00 iobroker_2026_02_23-02_00_20_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  19K Feb 11 02:14 javascripts_2026_02_11-02_14_28_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  19K Feb 22 02:14 javascripts_2026_02_22-02_14_48_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  19K Feb 23 02:14 javascripts_2026_02_23-02_14_36_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  19K Feb 23 16:07 javascripts_2026_02_23-16_07_45_backupiobroker.tar.gz
-rw-rw-r--+ 1 iobroker iobroker  19K May 24 10:17 javascripts_2026_05_24-10_17_10_backupiobroker.tar.gz

12 Uhr wird Backup noch mal gestartet...
Anhang:

[Mon May 25 11:52:44 2026] bcmgenet fd580000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[Mon May 25 11:54:14 2026] netfs: FS-Cache loaded
[Mon May 25 11:54:14 2026] Key type cifs.spnego registered
[Mon May 25 11:54:14 2026] Key type cifs.idmap registered
[Mon May 25 11:54:14 2026] CIFS: Attempting to mount //192.168.2.10/backup
[Mon May 25 11:56:35 2026] CIFS: Attempting to mount //192.168.2.10/backup
[Mon May 25 12:00:20 2026] CIFS: Attempting to mount //192.168.2.10/backup

Thomas Braun

@Laser

Ich würd ja schauen, dass du die history und die influxDB kleiner bekommst.

Klammer die mal bei einem Backup aus. Ich vermute, das ist einfach 'too much Zeug'.

Du mountest da also per CIFS was in /opt/iobroker/backups rein. Ist der mount-Punkt leer, wenn das Datei-System gerade nicht gemountet ist?

Laser

Wenn das Backup bis zur "Störung" gekommen ist, sehe ich mal nach, ob der Mountpoint leer ist.
Die Influx ist groß. Habe ich aber schon enorm verkleinert...

Community Forum

NEWS

Backitup stört LAN Verbindung

Support us

566

32.9k

83.0k

1.3m