Update von Adapter funktionieren nicht

[LJ-Mic]

Seit kurzem kann ich meine Adapter nicht Aktualisieren.
Leider bin ich mit meine Problem nicht fündig geworden, darum hier noch mal der Hilfeschrei.

Das sollte helfen:

pi@pi01:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v16.18.1
/usr/local/bin/node
v16.17.0
/usr/local/bin/npm
9.1.3
nodejs:
  Installiert:           16.18.1-deb-1nodesource1
  Installationskandidat: 16.18.1-deb-1nodesource1
  Versionstabelle:
 *** 16.18.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
pi@pi01:~ $ iobroker update
Used repository: stable
Adapter    "admin"        : 6.2.23   , installed 6.2.22 [Updatable]
Adapter    "alexa2"       : 3.23.2   , installed 3.19.9 [Updatable]
Adapter    "backitup"     : 2.5.4    , installed 2.4.10 [Updatable]
Adapter    "cloud"        : 4.2.2    , installed 4.2.2
Adapter    "discovery"    : 3.0.5    , installed 3.0.5
Adapter    "haier"        : 1.0.4    , installed 1.0.4
Adapter    "history"      : 2.2.0    , installed 2.2.0
Adapter    "hoover"       : 0.0.4    , installed 0.0.2  [Updatable]
Adapter    "info"         : 1.9.19   , installed 1.9.19
Adapter    "javascript"   : 6.0.3    , installed 6.0.0  [Updatable]
Controller "js-controller": 4.0.23   , installed 4.0.23
Adapter    "mqtt"         : 4.0.7    , installed 4.0.7
Adapter    "net-tools"    : 0.2.0    , installed 0.2.0
Adapter    "node-red"     : 4.0.0    , installed 4.0.0
Adapter    "ping"         : 1.5.3    , installed 1.5.3
Adapter    "plex"         : 0.9.1    , installed 0.9.1
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "sayit"        : 1.12.3   , installed 1.12.3
Adapter    "scenes"       : 2.3.9    , installed 2.3.9
Adapter    "simple-api"   : 2.7.0    , installed 2.7.0
Adapter    "socketio"     : 4.2.0    , installed 4.2.0
Adapter    "systeminfo"   : 0.3.1    , installed 0.3.1
Adapter    "telegram"     : 1.14.1   , installed 1.14.1
Adapter    "terminal"     : 0.2.6    , installed 0.2.6
Adapter    "text2command" : 2.2.2    , installed 2.2.2
Adapter    "vis"          : 1.4.15   , installed 1.4.15
Adapter    "web"          : 4.3.0    , installed 4.3.0
Adapter    "wifilight"    : 1.1.4    , installed 1.1.4
Adapter    "ws"           : 1.3.0    , installed 1.3.0
Adapter    "xterm"        : 0.3.2    , installed 0.3.2
Adapter    "yahka"        : 0.13.1   , installed 0.13.1
Adapter    "zigbee"       : 1.7.6    , installed 1.7.5  [Updatable]
pi@pi01:~ $ iobroker upgrade

This upgrade of "alexa2" will introduce the following changes:
==========================================================================
-> 3.23.2:
Prioritize real devices higher than app devices when serialnumbers overlap

-> 3.23.1:
Enhance checks when changing smart device values
Try to prevent Amazon rate limiting (again)

-> 3.21.0:
IMPORTANT: Because of rate limits by Amazon I decided to remove the update of smart home device values in intervals because it seems to produce too much load in Skills and Amazon systems.
Optimizes loading of smart home device states
Fixed issue with enabling/disabling of Alarms in combination with non-default music for the alarm
Prevented that Timers or Alarms that are long in the future to trigger their trigger state too early
Fixed deleting own user Messages state
Already request Notification updates when history registered a Notification action and do not wait for Push info to come in

-> 3.20.1:
make sure caching works correctly with multiple instances of the adapter

-> 3.20.0:
Increase minimum interval for requesting smart home device data to 15 minutes (900s) because of Amazon rate limits. Please do not try to work around it!
Cache Smart home device list and data to prevent too many requests when restarting adapter in short intervals and to prevent deleted smart home devices also on further rate limit issues

-> 3.19.10:
Fix issue in retry handling when rate limit exceeded is returned by Amazon
Do not clean up Smart Home Device objects for now - delete manually if you remove a device
==========================================================================

Would you like to upgrade alexa2 from @3.19.9 to @3.23.2 now? [(y)es, (n)o]: y
Update alexa2 from @3.19.9 to @3.23.2
NPM version: 9.1.3
Installing iobroker.alexa2@3.23.2... (System call)
host.pi01 Cannot install iobroker.alexa2@3.23.2: 217

Mach ich das Update per Browser/Admin kommt folgendes zum Beispiel bei Alexa:

$ iobroker upgrade alexa2@3.23.2 --debug
Update alexa2 from @3.19.9 to @3.23.2
NPM version: 9.1.3Installing iobroker.alexa2@3.23.2... (System call)
npm ERR! code ENOTEMPTY
npm ERR! syscall renamenpm ERR! path /opt/iobroker/node_modules/addressparsernpm ERR! dest /opt/iobroker/node_modules/.addressparser-qF9vtHFgnpm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/addressparser' -> '/opt/iobroker/node_modules/.addressparser-qF9vtHFg'
npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2022-12-05T23_02_53_757Z-debug-0.log
host.pi01 Cannot install iobroker.alexa2@3.23.2: 217
ERROR: Process exited with code 25

Danke

[crunchip]

@lj-mic sagte in Update von Adapter funktionieren nicht:

bin ich mit meine Problem nicht fündig geworden

man kann es schon gar nicht mehr zählen wie oft dieses Problem hier im Forum behandelt wurde

zum einen ist dein nodejs falsch installiert und zum anderen, steht code25 sogar angepinnt ganz oben im Forum, da muss man nicht mal suchen.

https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
https://forum.iobroker.net/topic/57337/fehler-25-oder-217-bei-adapter-install-update-mit-npm8

[Codierknecht]

@crunchip sagte in Update von Adapter funktionieren nicht:

zum einen ist dein nodejs falsch installiert

Und NPM ausnahmsweise mal zu neu statt zu alt