@Homoran
@Thomas-Braun
Danke für die Unterstützung und Zuarbeit.
Ich werde alles von Grund auf neu installieren, und das Backup vom Dienstag einspielen.
Dann denke ich, wird es wieder laufen.

@Thomas-Braun
Schreiben sie gerne nochmal, wenn es ihre Zeit erlaubt.
Ich melde mich nun erstmal ab und schaue morgen nochmal hier vorbei.

@Thomas-Braun
Leider sagt mir das alles nicht so viel.
Zum Schluß sehe ich ein error. No connection to database.

@thomas-braun

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

```bash
Script v.2025-03-08

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

Model           : Raspberry Pi 5 Model B Rev 1.0
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 20:02:13 up 1 day,  7:54,  3 users,  load average: 0.14, 0.11, 0.04
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: Thu 2025-05-29 20:02:13 CEST
           Universal time: Thu 2025-05-29 18:02:13 UTC
                 RTC time: Thu 2025-05-29 18:02:13
                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':
Uwe
HOME=/home/Uwe
GROUPS=Uwe 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
Desktop:
Terminal:       tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:            8.5G        341M        7.5G        5.5M        670M        8.1G
Swap:           209M          0B        209M
Total:          8.7G        341M        7.7G

Active iob-Instances:   0

         8063 M total memory
          325 M used memory
          221 M active memory
          433 M inactive memory
         7182 M free memory
          107 M buffer memory
          531 M swap cache
          199 M total swap
            0 M used swap
          199 M free swap

*** top - Table Of Processes  ***
top - 20:02:13 up 1 day,  7:54,  3 users,  load average: 0.14, 0.11, 0.04
Tasks: 173 total,   1 running, 172 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,100.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   8063.7 total,   7181.7 free,    326.2 used,    639.3 buff/cache
MiB Swap:    200.0 total,    200.0 free,      0.0 used.   7737.5 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.9G     0  3.9G   0% /dev
tmpfs          tmpfs     807M  5.3M  802M   1% /run
/dev/mmcblk0p2 ext4      117G  5.6G  106G   5% /
tmpfs          tmpfs     4.0G     0  4.0G   0% /dev/shm
tmpfs          tmpfs     5.0M   48K  5.0M   1% /run/lock
/dev/mmcblk0p1 vfat      510M   66M  445M  13% /boot/firmware
tmpfs          tmpfs     807M     0  807M   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed May 28 12:07:56 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave  numa=fake=8 system_heap.max_order=0 smsc95xx.macaddr=2C:CF:67:32:63:A0 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=8e8d8989-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE
[Wed May 28 12:07:59 2025] EXT4-fs (mmcblk0p2): mounted filesystem 93c89e92-8f2e-4522-ad32-68faed883d2f ro with ordered data mode. Quota mode: none.
[Wed May 28 12:08:00 2025] EXT4-fs (mmcblk0p2): re-mounted 93c89e92-8f2e-4522-ad32-68faed883d2f r/w. Quota mode: none.

Show mounted filesystems:
TARGET           SOURCE         FSTYPE OPTIONS
/                /dev/mmcblk0p2 ext4   rw,noatime
`-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,er

Files in neuralgic directories:

/var:
1.1G    /var/
450M    /var/log/journal/7955a11edc2a4908be4e0376b1ccf614
450M    /var/log/journal
450M    /var/log
207M    /var/cache

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

/opt/iobroker/backups:
6.7M    /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
845M    /opt/iobroker/iobroker-data/
746M    /opt/iobroker/iobroker-data/files
617M    /opt/iobroker/iobroker-data/files/javascript.admin
560M    /opt/iobroker/iobroker-data/files/javascript.admin/static
558M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js

The five largest files in iobroker-data are:
43M     /opt/iobroker/iobroker-data/objects.jsonl
24M     /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map
9.3M    /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js
8.7M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map
8.6M    /opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.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':

No Devices found 'by-id'

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 arm64 Packages
        100 /var/lib/dpkg/status
     21.7.2-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.7.1-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.7.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.6.2-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.6.1-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.6.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.5.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.4.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.3.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.2.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.1.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     21.0.0-1nodesource1 600
        500 https://deb.nodesource.com/node_21.x nodistro/main arm64 Packages
     18.19.0+dfsg-6~deb12u2 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
     18.19.0+dfsg-6~deb12u1 500
        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

*** ioBroker-Installation ***

ioBroker Status
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!

Hosts:
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!

Core adapters versions
js-controller:  7.0.6
admin:          7.6.17
javascript:     "javascript" not found

nodejs modules from github:     0

Adapter State
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!

Enabled adapters with bindings

ioBroker-Repositories
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!

Installed ioBroker-Adapters
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!

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

*** OS-Repositories and Updates ***
W: Failed to fetch https://deb.nodesource.com/node_21.x/dists/nodistro/InRelease  Could not resolve 'proxy'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Ign:1 https://deb.nodesource.com/node_21.x nodistro InRelease
Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:5 http://deb.debian.org/debian bookworm-updates InRelease
Ign:1 https://deb.nodesource.com/node_21.x nodistro InRelease
Ign:1 https://deb.nodesource.com/node_21.x nodistro InRelease
Err:1 https://deb.nodesource.com/node_21.x nodistro InRelease
  Could not resolve 'proxy'
Reading package lists... Done
W: Failed to fetch https://deb.nodesource.com/node_21.x/dists/nodistro/InRelease  Could not resolve 'proxy'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Pending Updates: 1

*** 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          5579       793/sshd: /usr/sbin
tcp6       0      0 :::22                   :::*                    LISTEN      0          5581       793/sshd: /usr/sbin
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           104        6402       677/avahi-daemon: r
udp        0      0 0.0.0.0:56843           0.0.0.0:*                           104        6404       677/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                104        6403       677/avahi-daemon: r
udp6       0      0 fe80::9f5b:17ea:875:546 :::*                                0          1683       754/NetworkManager
udp6       0      0 :::33400                :::*                                104        6405       677/avahi-daemon: r

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

2025-05-29 20:03:38.051  - warn: host.raspberrypi5-Server Objects 127.0.0.1:56276 Error from InMemDB: Error: auth NOT SUPPORTED
    at RedisHandler._handleCommand (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:141:40)
    at Resp.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:59:45)
    at Resp.emit (node:events:519:28)
    at Resp.write (/opt/iobroker/node_modules/respjs/index.js:129:12)
    at Socket.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:69:23)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2025-05-29 20:03:38.359  - warn: host.raspberrypi5-Server Objects 127.0.0.1:56286 Error from InMemDB: Error: auth NOT SUPPORTED
    at RedisHandler._handleCommand (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:141:40)
    at Resp.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:59:45)
    at Resp.emit (node:events:519:28)
    at Resp.write (/opt/iobroker/node_modules/respjs/index.js:129:12)
    at Socket.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-base/build/esm/lib/redisHandler.js:69:23)
    at Socket.emit (node:events:519:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
2025-05-29 20:04:07.001  - error: host.raspberrypi5 No connection to databases possible, restart
2025-05-29 20:04:07.004  - info: host.raspberrypi5 iobroker _restart
2025-05-29 20:04:07.511  - info: host.raspberrypi5 iobroker Starting node restart.js

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

iob diag has finished.

Uwe@raspberrypi5:/home/iobroker $

@thomas-braun
Stimmt, mit:

iob nodejs-update 20

gibt es keine Reaktion.

@thomas-braun
Und wie, mit welchen Befehlen, legt man eine Quelle für nodejs20 an?

@thomas-braun

Uwe@raspberrypi5:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Get:2 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:3 http://archive.raspberrypi.com/debian bookworm InRelease [55.0 kB]
Get:4 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:5 http://deb.debian.org/debian-security bookworm-security/main armhf Packages [243 kB]
Get:6 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages [257 kB]
Get:7 http://deb.debian.org/debian-security bookworm-security/main Translation-en [157 kB]
Get:8 http://archive.raspberrypi.com/debian bookworm/main armhf Packages [539 kB]
Get:9 http://archive.raspberrypi.com/debian bookworm/main arm64 Packages [537 kB]
Ign:10 https://deb.nodesource.com/node_21.x nodistro InRelease
Ign:10 https://deb.nodesource.com/node_21.x nodistro InRelease
Ign:10 https://deb.nodesource.com/node_21.x nodistro InRelease
Err:10 https://deb.nodesource.com/node_21.x nodistro InRelease
  Could not resolve 'proxy'
Fetched 1,892 kB in 12s (156 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
W: Failed to fetch https://deb.nodesource.com/node_21.x/dists/nodistro/InRelease  Could not resolve 'proxy'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Uwe@raspberrypi5:~ $

Was ist denn mit: "Could not resolve 'proxy'?

@thomas-braun said in Keine Anmeldung mehr möglich:

iob start admin

Mit start admin

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu May 29 18:31:44 2025 from 2001:4dd1:72e3:0:8dc6:6635:1158:cbf7
Uwe@raspberrypi5:~ $ iob start admin
 Unable to increase LUA script timeout: Error auth NOT SUPPORTED
 Cannot determine Set feature status: Connection is closed.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/node_modules/iobroker.js-controller/admin/objects.jsonl"!
Uwe@raspberrypi5:~ $

@thomas-braun
Ergebnis

Uwe@raspberrypi5:~ $ df -h
systemctl status iobroker.service
Filesystem      Size  Used Avail Use% Mounted on
udev            3.9G     0  3.9G   0% /dev
tmpfs           807M  5.2M  802M   1% /run
/dev/mmcblk0p2  117G  5.6G  106G   5% /
tmpfs           4.0G     0  4.0G   0% /dev/shm
tmpfs           5.0M   48K  5.0M   1% /run/lock
/dev/mmcblk0p1  510M   66M  445M  13% /boot/firmware
tmpfs           807M     0  807M   0% /run/user/1000
● iobroker.service - ioBroker Server
     Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-05-29 18:31:53 CEST; 580ms ago
       Docs: http://iobroker.net
   Main PID: 98660 (iobroker.js-con)
      Tasks: 11 (limit: 9580)
        CPU: 706ms
     CGroup: /system.slice/iobroker.service
             └─98660 iobroker.js-controller

May 29 18:31:53 raspberrypi5 systemd[1]: Started iobroker.service - ioBroker Server.
Uwe@raspberrypi5:~ $

@thomas-braun
Sowohl

iob fix

als auch

curl -fsL https://iobroker.net/fix.sh | bash -

bringen kein Ergebnis, keine Ausgabe!
In der Powershell wartet der Cursor wieder auf eine Eingabe.
Mit:

curl -fL http://iobroker.net/fix.sh | bash -

erhalte ich das Ergebnis:

Uwe@raspberrypi5:~ $ curl -fL http://iobroker.net/fix.sh | bash -
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   169  100   169    0     0   3716      0 --:--:-- --:--:-- --:--:--  3755
100   169  100   169    0     0   1419      0 --:--:-- --:--:-- --:--:--  1419
curl: (5) Could not resolve proxy: proxy