UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[13patrick37]

Habe oben soweit alles ausgefüllt. js-controller und Admin Version weiß ich leider nicht.

iob diag habe ich versucht, kommt folgende Meldung:

*** iob diag is starting up, please wait ***
iob diag needs to be updated. Please execute 'iobroker fix' first.

Auch wenn ich iobroker fix ausführe, komme ich immer wieder bei der Meldung heraus.

[mcm1957]

Vorab mal node 21 ist eine TEST / BETA Version. Du solltest nur gerade nodejs versionen verwenden.

@Thomas-Braun
Kannst du bitte das Workaround für iob diag posten, ich vergess es von einem aufs nächste mal ...

[Homoran]

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

Habe oben soweit alles ausgefüllt

bitte nichts nachträglich ändern, das liest niemand mehr, der da schon war.
Für andere passt dann der Rest nicht mehr

siehe
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

@mcm1957 sagte in ioBroker offline/Installation broken-nach Adapter:

Workaround für iob diag

curl https://raw.githubusercontent.com/Grothesk242/ioBroker/refs/heads/Raspbian/diag.sh > iob_diag.sh
chmod 744 iob_diag.sh
./iob_diag.sh

das sind drei einzelne Befehle!!

[13patrick37]

So, da ist der Log:

Copy text starting here:

```bash
======================= SUMMARY =======================
                        v.2024-12-09 Raspbian+zigbee diag+masking


   Static hostname: raspberrypi
         Icon name: computer
  Operating System: Raspbian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.6.72-v8+
      Architecture: arm64

Installation:           native
Kernel:                 aarch64
Userland:               32 bit
Timezone:               Europe/Berlin (CET, +0100)
User-ID:                1000
Display-Server:         false
Boot Target:            multi-user.target

Pending OS-Updates:     192
Installation broken or unknown states type: file configured.
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v21.7.3
/usr/bin/node           v21.7.3
/usr/bin/npm            10.5.0
/usr/bin/npx            10.5.0
/usr/bin/corepack       0.25.2

Recommended versions are nodejs  and npm
nodeJS installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:            1.8G        103M        1.0G        0.0K        697M        1.7G
Swap:            99M          0B         99M
Total:          1.9G        103M        1.1G

Active iob-Instances:   0
Installation broken or unknown states type: file configured.

ioBroker Core:          js-controller           3.3.22
                        admin                   6.3.5

Installation broken or unknown states type: file configured.
ioBroker Status:

Status admin and web instance:

Objects:                0
States:                 0

Size of iob-Database:

12M     /opt/iobroker/iobroker-data/objects.json.bak
12M     /opt/iobroker/iobroker-data/objects.json
0       /opt/iobroker/iobroker-data/objects.json.broken
1.6M    /opt/iobroker/iobroker-data/states.json.bak
1.6M    /opt/iobroker/iobroker-data/states.json
0       /opt/iobroker/iobroker-data/states.json.broken


Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be updated to the latest stable release '' NOW!

=================== END OF SUMMARY ====================

Macht für mich den Eindruck ob wäre alles weg ..

[Homoran]

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

da ist der Log:

Aber nur das

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

SUMMARY

bitte die Langfassung

EDIT:
@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

usr/bin/nodejs v21.7.3

ist nicht unterstützt

und das Betriebssystem ist versumpft

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

Pending OS-Updates: 192

[13patrick37]

@homoran

Hast du Lösungsansätze oder hilft nur die Neu-Installation?

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

```bash
Script v.2024-12-09 Raspbian+zigbee diag+masking

*** BASE SYSTEM ***
   Static hostname: raspberrypi
         Icon name: computer
  Operating System: Raspbian GNU/Linux 11 (bullseye)
            Kernel: Linux 6.6.72-v8+
      Architecture: arm64
OS is similar to: debian

Model           : Raspberry Pi 4 Model B Rev 1.4
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 32 bit

Systemuptime and Load:
 11:07:02 up  1:32,  1 user,  load average: 0.24, 0.22, 0.27
CPU threads: 4


*** LIFE CYCLE STATUS ***
Debian Release codenamed 'bullseye' reached its END OF LIFE and needs to be upda                                                                                                                                                                             ted to the latest stable release '' NOW!

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

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Sun 2025-01-19 11:07:02 CET
           Universal time: Sun 2025-01-19 10:07:02 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 netdev gp                                                                                                                                                                             io i2c spi iobroker

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

*** DISPLAY-SERVER SETUP ***
Display-Server: false
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            1.8G        109M        1.0G        0.0K        706M        1.7G
Swap:            99M          0B         99M
Total:          1.9G        109M        1.1G

Active iob-Instances:   0

         1846 M total memory
          110 M used memory
          234 M active memory
          345 M inactive memory
         1029 M free memory
          147 M buffer memory
          558 M swap cache
           99 M total swap
            0 M used swap
           99 M free swap

*** top - Table Of Processes  ***
top - 11:07:03 up  1:32,  1 user,  load average: 0.24, 0.22, 0.27
Tasks: 171 total,   2 running, 169 sleeping,   0 stopped,   0 zombie
%Cpu(s): 27.3 us,  1.5 sy,  0.0 ni, 71.2 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   1846.8 total,   1029.2 free,    110.9 used,    706.8 buff/cache
MiB Swap:    100.0 total,    100.0 free,      0.0 used.   1667.0 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
/dev/root      ext4       29G  6.2G   22G  22% /
devtmpfs       devtmpfs  666M     0  666M   0% /dev
tmpfs          tmpfs     924M     0  924M   0% /dev/shm
tmpfs          tmpfs     370M  868K  369M   1% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      253M   54M  199M  22% /boot
tmpfs          tmpfs     185M     0  185M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Sun Jan 19 09:34:57 2025] Kernel command line: coherent_pool=1M 8250.nr_uarts=0                                                                                                                                                                              snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave sn                                                                                                                                                                             d_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=                                                                                                                                                                             0  smsc95xx.macaddr=E4:5F:01:7F:44:7B vc_mem.mem_base=0x3ec00000 vc_mem.mem_size                                                                                                                                                                             =0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=7479d47b-02 rootfst                                                                                                                                                                             ype=ext4 fsck.repair=yes rootwait
[Sun Jan 19 09:34:57 2025] EXT4-fs (mmcblk0p2): mounted filesystem 568caafd-bab1                                                                                                                                                                             -46cb-921b-cd257b61f505 ro with ordered data mode. Quota mode: none.
[Sun Jan 19 09:34:57 2025] VFS: Mounted root (ext4 filesystem) readonly on devic                                                                                                                                                                             e 179:2.
[Sun Jan 19 09:34:59 2025] EXT4-fs (mmcblk0p2): re-mounted 568caafd-bab1-46cb-92                                                                                                                                                                             1b-cd257b61f505 r/w. Quota mode: none.

Show mounted filesystems:
TARGET  SOURCE         FSTYPE OPTIONS
/       /dev/mmcblk0p2 ext4   rw,noatime
`-/boot /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,ioc

Files in neuralgic directories:

/var:
2.4G    /var/
1.6G    /var/log/journal/3e23e34d17484a28b9473f69f7d9d21c
1.6G    /var/log/journal
1.6G    /var/log
580M    /var/cache

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

/opt/iobroker/backups:
57M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
260M    /opt/iobroker/iobroker-data/
99M     /opt/iobroker/iobroker-data/files
75M     /opt/iobroker/iobroker-data/zigbee_0
66M     /opt/iobroker/iobroker-data/files/javascript.admin
61M     /opt/iobroker/iobroker-data/backup-objects

The five largest files in iobroker-data are:
12M     /opt/iobroker/iobroker-data/objects.json.bak
12M     /opt/iobroker/iobroker-data/objects.json
9.8M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.f6fd0e72.                                                                                                                                                                             chunk.js.map
6.9M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.de0231c                                                                                                                                                                             9.chunk.js.map
6.3M    /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-n                                                                                                                                                                             ode_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_                                                                                                                                                                             iobr-99c23e.847b8ad9.chunk.js.map

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please alw                                                                                                                                                                             ays prefer the links 'by-id':

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE24694                                                                                                                                                                             58-if00

*** 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         v21.7.3
/usr/bin/node           v21.7.3
/usr/bin/npm            10.5.0
/usr/bin/npx            10.5.0
/usr/bin/corepack       0.25.2

nodejs:
  Installed: 21.7.3-1nodesource1
  Candidate: 21.7.3-1nodesource1
  Version table:
 *** 21.7.3-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
        100 /var/lib/dpkg/status
     21.7.2-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.7.1-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.7.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.6.2-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.6.1-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.6.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.5.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.4.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.3.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.2.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.1.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     21.0.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main armhf Packages
     12.22.12~dfsg-1~deb11u5 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Package                                                                                                                                                                             s

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

*** ioBroker-Installation ***

ioBroker Status
Installation broken or unknown states type: file configured.

Hosts:
Installation broken or unknown states type: file configured.

Core adapters versions
js-controller:  3.3.22
admin:          6.3.5
javascript:     6.1.4

nodejs modules from github:     3
+-- iobroker.iot@1.9.2 (git+ssh://git@github.com/ioBroker/ioBroker.iot.git#4ba0b7ef61bb3fd0444dbadff54b941ccf72db15)
| `-- syno@3.0.0 (git+https://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0)
+-- iobroker.zigbee@1.6.13 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#6fff38cf64a4e4333a6df43057e79720ef7b1d3d)

Adapter State


Enabled adapters with bindings

ioBroker-Repositories
Installation broken or unknown states type: file configured.

Installed ioBroker-Instances
Installation broken or unknown states type: file configured.

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

*** OS-Repositories and Updates ***
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://phoscon.de/apt/deconz bullseye InRelease
Hit:4 https://deb.nodesource.com/node_21.x nodistro InRelease
Reading package lists... Done
Pending Updates: 192

*** 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:443             0.0.0.0:*               LISTEN      1000       6468       388/deCONZ
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1000       1628       388/deCONZ
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          6442       555/sshd: /usr/sbin
tcp6       0      0 :::22                   :::*                    LISTEN      0          6444       555/sshd: /usr/sbin
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           1000       6471       388/deCONZ
udp        0      0 0.0.0.0:51099           0.0.0.0:*                           108        5972       382/avahi-daemon: r
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          6111       769/dhcpcd
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        5970       382/avahi-daemon: r
udp6       0      0 :::39976                :::*                                108        5973       382/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                108        5971       382/avahi-daemon: r
udp6       0      0 :::546                  :::*                                0          80546      769/dhcpcd

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

2025-01-19 08:48:32.732  - info: bshb.0 (3795) Check if client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 is already paired.
2025-01-19 08:48:35.741  - info: bshb.0 (3795) Client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 was not paired yet.
2025-01-19 08:48:35.742  - info: bshb.0 (3795) Start pairing. Activate pairing on Bosch Smart Home Controller by pressing button until flashing.
2025-01-19 08:48:38.748  - warn: bshb.0 (3795) Could not pair client. Did you press the paring button on Bosch Smart Home Controller? Error details: undefined
2025-01-19 08:48:39.935  - warn: tahoma.0 (3321) error during request: Error: connect ECONNREFUSED 192.168.178.36:8443, request path: setup/gateways with payload:{}
2025-01-19 08:48:48.749  - info: bshb.0 (3795) Check if client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 is already paired.
2025-01-19 08:48:51.758  - info: bshb.0 (3795) Client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 was not paired yet.
2025-01-19 08:48:51.758  - info: bshb.0 (3795) Start pairing. Activate pairing on Bosch Smart Home Controller by pressing button until flashing.
2025-01-19 08:48:54.768  - warn: bshb.0 (3795) Could not pair client. Did you press the paring button on Bosch Smart Home Controller? Error details: undefined
2025-01-19 08:48:59.520  - info: host.raspberrypi iobroker add homeconnect --host raspberrypi
2025-01-19 08:49:03.433  - error: host.raspberrypi iobroker (node:616) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.(Use `node --trace-deprecation ...` to show where the warning was created)
2025-01-19 08:49:04.769  - info: bshb.0 (3795) Check if client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 is already paired.
2025-01-19 08:49:04.924  - info: host.raspberrypi iobroker NPM version: 10.5.0
2025-01-19 08:49:04.928  - info: host.raspberrypi iobroker npm install iobroker.homeconnect@1.4.3 --loglevel error --prefix "/opt/iobroker" (System call)
2025-01-19 08:49:07.778  - info: bshb.0 (3795) Client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 was not paired yet.
2025-01-19 08:49:07.778  - info: bshb.0 (3795) Start pairing. Activate pairing on Bosch Smart Home Controller by pressing button until flashing.
2025-01-19 08:49:09.945  - warn: tahoma.0 (3321) error during request: Error: connect ECONNREFUSED 192.168.178.36:8443, request path: setup/gateways with payload:{}
2025-01-19 08:49:10.782  - warn: bshb.0 (3795) Could not pair client. Did you press the paring button on Bosch Smart Home Controller? Error details: undefined
2025-01-19 08:49:20.782  - info: bshb.0 (3795) Check if client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 is already paired.
2025-01-19 08:49:23.793  - info: bshb.0 (3795) Client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 was not paired yet.
2025-01-19 08:49:23.794  - info: bshb.0 (3795) Start pairing. Activate pairing on Bosch Smart Home Controller by pressing button until flashing.
2025-01-19 08:49:26.798  - warn: bshb.0 (3795) Could not pair client. Did you press the paring button on Bosch Smart Home Controller? Error details: undefined
2025-01-19 08:49:39.025  - info: bshb.0 (3795) Check if client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 is already paired.
2025-01-19 08:49:43.844  - warn: tahoma.0 (3321) error during request: Error: connect ECONNREFUSED 192.168.178.36:8443, request path: setup/gateways with payload:{}
2025-01-19 08:50:20.512  - info: bshb.0 (3795) Client with identifier: ioBroker.bshb_c035acdd-5f03-4979-ac21-4e96459271c9 was not paired yet.

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

[Thomas Braun]

@13patrick37

Installier da NEU das aktuelle Release 'Debian 12 - Bookworm'.
Diesmal in der 64Bit-Lite-Version.
ioBroker leer installieren, Backup einspielen, fertig.

Edit:
js-controller: 3.3.22

Ernsthaft?

[Homoran]

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

Hast du Lösungsansätze

ich fürchte

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

Installation broken or unknown states type: file configured.

es hat drine Objects und/oder states DB zerschossen.
Dafür gibt es interne Backups.
Die existieren aber nur noch, wenn du nicht mehr als 10x dran rumgespielt hast.

Ist ewig her, dass es das zum letzten mal gab.
Hab nicht mehr im Kopf wie das Vorgehen war

[13patrick37]

Backup habe ich über winSCP schon gesichert. War zum Glück relativ aktuell.

Also wie @Thomas-Braun sagte, komplett neu installieren und Backup einspielen.

[Homoran]

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

Backup habe ich über winSCP schon gesichert.

das meinte ich nicht.
es gibt interne Backups der Systemdatenbanken.

Aber ein backitup Backup ist natürlich auch sinnvoll, wenn die Objectdatenbank darin nicht schon defekt ist.

[13patrick37]

@homoran said in ioBroker offline/Installation broken-nach Adapter:

es gibt interne Backups der Systemdatenbanken.

Hast du dazu eine Doku? Oder wie gehe ich das an? Ein Versuch ist es wert bevor ich alles neu mache.

Frage ist, wodurch ist mein ioBroker abgeschmiert? An der veralteten js-controller Version?

[Thomas Braun]

@13patrick37 sagte in ioBroker offline/Installation broken-nach Adapter:

bevor ich alles neu mache.

Das musst du ohnehin alles neu aufsetzen.

[mcm1957]

@13patrick37

Ist das dein Ersnt?

Core adapters versions
js-controller:  3.3.22
admin:          6.3.5
javascript:     6.1.4
 
nodejs modules from github:     3
+-- iobroker.iot@1.9.2 (git+ssh://git@github.com/ioBroker/ioBroker.iot.git#4ba0b7ef61bb3fd0444dbadff54b941ccf72db15)
| `-- syno@3.0.0 (git+https://git@github.com/MeisterTR/syno.git#0104a973d33fe332aa6b1ab5be7fe8c57d3c68b0)
+-- iobroker.zigbee@1.6.13 (git+ssh://git@github.com/ioBroker/ioBroker.zigbee.git#6fff38cf64a4e4333a6df43057e79720ef7b1d3d)

js-controller 3.x.x ist ja icht nur veraltet sondern schon verwest. Sorry aber der aktuelle js-controller ist 7.x.x. Wundert mich dass du da irgendwelche Updates noch reingebracht hast. Oder ziehst du immer via Github ? iot von Github? zigbee von Github?

Wie hast du da homeconnect installiert? Der Adapter verlangt js-controller 5.0.19. Damit kann eine Installation via adminUI und via commandline nicht funktioniert haben.

ODER hast du - ohne es bisher zu erwähnen - versucht den js-controller zu aktualisisern. Ev. gar von 3 auf 7 ohne Zwischenstationen ?

Ich glaub da ist alles andere als eine komplette Neuinstallation vergebliche Liebesmühe.

[13patrick37]

@mcm1957 said in ioBroker offline/Installation broken-nach Adapter:

ODER hast du - ohne es bisher zu erwähnen - versucht den js-controller zu aktualisisern. Ev. gar von 3 auf 7 ohne Zwischenstationen ?

Tatsächlich nicht, war lediglich die Adapter Installation.

Ich habe nun ioBroker gelöscht und neu installiert. Ist jetzt die riesen Frage ob es das Backup nimmt? Aufgrund der alten js-controller Version.

[mcm1957]

@13patrick37

Hast du gleich auf die aktuelle O/S Version (bookworm) aktualisisert?
Und node auf 20 gebracht?

Sonst machst das in 2 Monaten wieder ...