ERROR: Update js-controller from @3.1.6 to @4.0.23

[ChristianG]

Hat jemand eine Idee wie ich dieses Problem lösen kann? Keiner der Beiträge oder FIX Lösungen aus dem Forum funktioniert. Danke

iobroker stop
iobroker update
iobroker upgrade
iobroker upgrade self
iobroker start

Dies hat leider nicht geklappt:

Update js-controller from @3.1.6 to @4.0.23
NPM version: 9.1.2
npm install iobroker.js-controller@4.0.23 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
 Objects 127.0.0.1:53688 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
 States 127.0.0.1:34532 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
 Objects 127.0.0.1:53688 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
 Objects 127.0.0.1:53688 Error from InMemDB: Error: scan NOT SUPPORTED
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! command failed
npm ERR! command sh -c node iobroker.js setup first
npm ERR! /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
npm ERR!         throw e;
npm ERR!         ^
npm ERR! 
npm ERR! ReplyError: Error scan NOT SUPPORTED
npm ERR!     at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
npm ERR!     at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
npm ERR! Emitted 'error' event on ScanStream instance at:
npm ERR!     at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
npm ERR!     at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
npm ERR!     at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
npm ERR!     at processTicksAndRejections (node:internal/process/task_queues:96:5) {
npm ERR!   command: {
npm ERR!     name: 'scan',
npm ERR!     args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
npm ERR!   }
npm ERR! }

[Thomas Braun]

@christiang

NPM version: 9.1.2

Verfummelte nodejs-Installation.

Bieg das wieder richtig hin. Siehe meine Signatur.

[ChristianG]

Habs irgendwie geschafft danke

[Thomas Braun]

@christiang

Vermutlich mit einer gescheiten Installation von nodeJS.

Wie schaut's da nun aus?