@crunchip Den iobroker hatte ich vorher per iob stop gestoppt.
iob diag sieht bei mir wie folgt aus:
======================= SUMMARY =======================
v.2023-04-16
Operatingsystem: Raspbian GNU/Linux 10 (buster)
Kernel: 5.10.103-v7l+
Installation: Native
Timezone: Europe/Berlin (CEST, +0200)
User-ID: 1000
X-Server: false
Boot Target: graphical.target
Pending OS-Updates: 0
Pending iob updates: 4
Nodejs-Installation: /usr/bin/nodejs v18.17.1
/usr/bin/node v18.17.1
/usr/bin/npm 9.6.7
/usr/bin/npx 9.6.7
Recommended versions are nodejs 18.x.y and npm 9.x.y
Your nodejs installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 3.8G 1.2G 1.8G 8.0M 826M 2.5G
Swap: 99M 0B 99M
Total: 3.9G 1.2G 1.9G
Active iob-Instances: 28
Active repo(s): stable
ioBroker Core: js-controller 4.0.24
admin 6.8.0
ioBroker Status: iobroker is running on this host.
Objects type: jsonl
States type: redis
Status admin and web instance:
system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin
Objects: 9681
States: 10090
Size of iob-Database:
13M /opt/iobroker/iobroker-data/objects.jsonl
7.9M /opt/iobroker/iobroker-data/objects.json.migrated
7.9M /opt/iobroker/iobroker-data/objects.json.bak.migrated
0 /opt/iobroker/iobroker-data/objects.json.broken
144K /opt/iobroker/iobroker-data/states.json.bak
144K /opt/iobroker/iobroker-data/states.json
=================== END OF SUMMARY ====================
Hilft Dir das Summary oder soll ich lieber den ganzen Report mal schicken?