@ilovegym
hier der diag output:
======================= SUMMARY =======================
v.2024-10-19
Static hostname: iobroker
Icon name: computer-container
Chassis: container ☐
Virtualization: lxc
Operating System: Debian GNU/Linux 12 (bookworm)
Kernel: Linux 6.8.4-2-pve
Architecture: x86-64
Installation: lxc
Kernel: x86_64
Userland: 64 bit
Timezone: Europe/Berlin (CET, +0100)
User-ID: 0
Display-Server: false
Boot Target: graphical.target
Pending OS-Updates: 0
Pending iob updates: 0
Nodejs-Installation:
/usr/bin/nodejs v20.18.0
/usr/bin/node v20.18.0
/usr/bin/npm 10.8.2
/usr/bin/npx 10.8.2
/usr/bin/corepack 0.29.3
Recommended versions are nodejs
***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now. and npm
***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now.
nodeJS installation is correct
MEMORY:
total used free shared buff/cache available
Mem: 2.1G 309M 1.5G 102K 345M 1.8G
Swap: 536M 0B 536M
Total: 2.7G 309M 2.0G
Active iob-Instances: 0
Please note that this option may be disabled in the future, so please change your setup accordingly now.
ioBroker Core: js-controller
***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now.
admin
***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now.
ioBroker Status:
***For security reasons ioBroker should not be run or administrated as root.***
By default only a user that is member of iobroker group can execute ioBroker commands.
Please read the Documentation on how to set up such a user, if not done yet.
Only in very special cases you can run iobroker commands by adding the --allow-root option at the end of the command line.
Please note that this option may be disabled in the future, so please change your setup accordingly now.
Status admin and web instance:
***For security reasons ioBroker should not be run or administrated as root.***
Objects: 6
States: 6
Size of iob-Database:
5.0M /opt/iobroker/iobroker-data/objects.jsonl
48K /opt/iobroker/iobroker-data/states.jsonl
Unknown release codenamed ''. Please check yourself if the Operating System is actively maintained.
=================== END OF SUMMARY ====================
habe vorher den iobroker beendet und "iobroker fix" aufgerufen. bekam folgende ausgabe: "By default only a user that is member of iobroker group can execute ioBroker commands".
Das kannte ich so noch nicht von meinem raspberry. Habe das command mit --allow-root ausgeführt und einen neuen user "admin" angelegt (root und iobroker ging ja nicht). Der user ist nun angelegt. Das fix command habe ich trotzdem mit root ausgeführt:
