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

[Belei]

Moin,

ich hab jetzt einige Zeit mein iobroker nicht mehr upgedatet, ca seit Anfang des Jahres.
Jetzt wollt ich mal paar Updates fahren aber es hagelt bei alles Adapter Updates, folgende Fehler.

root@ioBrokerNuc:~# iob upgrade self --allow-root
Update js-controller from @5.0.17 to @6.0.11
Stopped Objects DB
Stopped States DB
NPM version: 10.2.3
Installing iobroker.js-controller@6.0.11... (System call)
Try to solve ENOTEMPTY error automatically
host.ioBrokerNuc deleted npm temp directory: ".diskusage-SbL2R1mm")
Installing iobroker.js-controller@6.0.11... (System call)
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket
npm ERR! dest /opt/iobroker/node_modules/@abandonware/.bluetooth-hci-socket-0H6suKAo
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket' -> '/opt/iobroker/node_modules/@abandonware/.bluetooth-hci-socket-0H6suKAo'

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-10-24T19_07_16_614Z-debug-0.log
host.ioBrokerNuc Cannot install iobroker.js-controller@6.0.11: 217

Ich 2x den iob fix durchlaufen lassen, erstmal ohne neuen User und weiterhin mit GUDesktop.
Aber leider ohne Erfolg.

Adapter    "admin"        : 7.1.5    , installed 6.12.0 [Updatable]
Adapter    "alexa2"       : 3.26.5   , installed 3.26.4 [Updatable]
Adapter    "amazon-dash"  : 1.2.0    , installed 1.2.0
Adapter    "backitup"     : 3.0.25   , installed 2.9.8  [Updatable]
Adapter    "ble"          : 0.14.0   , installed 0.13.4 [Updatable]
Adapter    "cloud"        : 5.0.1    , installed 4.4.1  [Updatable]
Adapter    "discovery"    : 5.0.0    , installed 4.2.0  [Updatable]
Adapter    "fb-checkpresence": 1.2.5 , installed 1.2.2  [Updatable]
Adapter    "feiertage"    : 1.2.0    , installed 1.1.4  [Updatable]
Adapter    "fhem"         : 3.0.0    , installed 2.0.5  [Updatable]
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "fritzdect"    : 2.5.11   , installed 2.5.9  [Updatable]
Adapter    "history"      : 3.0.1    , installed 3.0.1
Adapter    "hm-rega"      : 5.1.0    , installed 4.0.0  [Updatable]
Adapter    "hm-rpc"       : 2.0.2    , installed 1.16.0 [Updatable]
Adapter    "hue"          : 3.12.0   , installed 3.10.1 [Updatable]
Adapter    "iot"          : 3.3.0    , installed 2.0.11 [Updatable]
Adapter    "iqontrol"     : 2.3.0    , installed 2.3.0
Adapter    "javascript"   : 8.8.3    , installed 7.1.6  [Updatable]
Controller "js-controller": 6.0.11   , installed 5.0.17 [Updatable]
Adapter    "lovelace"     : 4.1.10   , installed 3.0.1  [Updatable]
Adapter    "mihome-vacuum": 4.2.0    , installed 4.1.0  [Updatable]
Adapter    "mobile"       : 1.0.1    , installed 1.0.1
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "pushover"     : 4.1.0    , installed 3.0.6  [Updatable]
Adapter    "rflink"       : 2.1.12   , installed 2.1.6  [Updatable]
Adapter    "scenes"       : 3.2.3    , installed 2.3.9  [Updatable]
Adapter    "shelly"       : 8.2.1    , installed 6.6.1  [Updatable]
Adapter    "simple-api"   : 2.8.0    , installed 2.7.2  [Updatable]
Adapter    "socketio"     : 6.7.1    , installed 6.6.0  [Updatable]
Adapter    "tr-064"       : 4.3.0    , installed 4.2.18 [Updatable]
Adapter    "vis"          : 1.5.6    , installed 1.5.4  [Updatable]
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "weatherunderground": 3.7.0, installed 3.6.0 [Updatable]
Adapter    "web"          : 6.2.5    , installed 6.1.10 [Updatable]
Adapter    "weishaupt-wem": 0.0.15   , installed 0.0.15
Adapter    "ws"           : 2.6.2    , installed 2.5.8  [Updatable]
Adapter    "zigbee"       : 1.10.3   , installed 1.9.7  [Updatable]
root@ioBrokerNuc:~# iob upgrade self --allow-root

======================= SUMMARY =======================
                        v.2024-10-19


   Static hostname: ioBrokerNuc
         Icon name: computer-vm
           Chassis: vm
    Virtualization: kvm
  Operating System: Debian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.0-25-amd64
      Architecture: x86-64

Installation:           kvm
Kernel:                 x86_64
Userland:               64 bit
Timezone:               Europe/Berlin (CEST, +0200)
User-ID:                0
Display-Server:         false
Boot Target:            graphical.target

Pending OS-Updates:     74
Pending iob updates:    0

Nodejs-Installation:
/usr/bin/nodejs         v18.19.0
/usr/bin/node           v18.19.0
/usr/bin/npm            10.2.3
/usr/bin/npx            10.2.3
/usr/bin/corepack       0.22.0

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.0G         82M        1.5G        0.0K        451M        1.8G
Swap:          2.0G         47M        2.0G
Total:         4.0G        129M        3.5G

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:

16M     /opt/iobroker/iobroker-data/objects.jsonl
108K    /opt/iobroker/iobroker-data/objects.json.migrated
68K     /opt/iobroker/iobroker-data/objects.json.bak.migrated
8.0K    /opt/iobroker/iobroker-data/states.json.bak
8.0K    /opt/iobroker/iobroker-data/states.json


**********************************************************************
Some problems detected, please run iob fix and try to have them fixed
**********************************************************************

2 CRITICAL ERRORS DETECTED!
Check 'sudo dmesg --level=emerg,alert,crit -T' for details
Debian Release codenamed 'buster' reached its END OF LIFE and needs to be updated to the latest stable release 'bookworm' NOW!

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

Kann jmd helfen?

[Thomas Braun]

@belei sagte in Update Fehler - ENOTEMPTY:

Debian GNU/Linux 10 (buster)

Zu alt.
Du hampelst als root herum.

[Belei]

@thomas-braun

Danke erstmal für deine Reaktion.

Dann muss ich wohl als User? erst auf Bullseye updaten dann auf Bookworm, denk ich?

Hast du einen Link wo das sicher beschrieben wird?

[Thomas Braun]

@belei

Installier es neu. Geht am schnellsten. Und dann gleich ohne graphische Umgebung.

[Thomas Braun]

@belei

Durch die Neuinstallation merzt du vermutlich auch die beiden kritischen Fehler aus:

2 CRITICAL ERRORS DETECTED!

Check 'sudo dmesg --level=emerg,alert,crit -T' for details

[Belei]

@thomas-braun

heut nicht mehr :-) Ich mach morgen weiter. Danke erstmal.