@thomas-braun sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

@sonnenfreund

Dann versuch einen 4er-js-controller zu installieren.

Nach
iobroker update
iobroker fix

gleiches Problem bei iobroker upgrade self:

pi@raspberrypi4-iob:/home $ iobroker upgrade self
Update js-controller from @3.1.6 to @5.0.16
NPM version: 10.2.3
npm install iobroker.js-controller@5.0.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
 Objects 127.0.0.1:59744 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["SET","lua-time-limit","10000"]
 States 127.0.0.1:37004 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["SET","notify-keyspace-events","Exe"]
 Objects 127.0.0.1:59744 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
 States 127.0.0.1:37004 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
 Objects 127.0.0.1:59744 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
 Objects 127.0.0.1:59744 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! Unable to increase LUA script timeout: Error CONFIG-UNSUPPORTED for ["SET","lua-time-limit","10000"]
npm ERR!  Unable to enable Expiry Keyspace events from Redis Server: Error CONFIG-UNSUPPORTED for ["SET","notify-keyspace-events","Exe"]
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 process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
npm ERR!   command: {
npm ERR!     name: 'scan',
npm ERR!     args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
npm ERR!   }
npm ERR! }
npm ERR!
npm ERR! Node.js v18.19.0

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-07T20_23_32_051Z-debug-0.log
Starting node restart.js
pi@raspberrypi4-iob:/home $

@thomas-braun sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

@sonnenfreund

Generell hast du es nicht so mit Updates, oder?

sei doch nicht so streng

cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller

hab ich grad gemacht und komme folgende Meldungen:

pi@raspberrypi4-iob:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
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! Unable to increase LUA script timeout: Error CONFIG-UNSUPPORTED for ["SET","lua-time-limit","10000"]
npm ERR!  Unable to enable Expiry Keyspace events from Redis Server: Error CONFIG-UNSUPPORTED for ["SET","notify-keyspace-events","Exe"]
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 process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
npm ERR!   command: {
npm ERR!     name: 'scan',
npm ERR!     args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
npm ERR!   }
npm ERR! }
npm ERR!
npm ERR! Node.js v18.19.0

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-07T20_09_35_513Z-debug-0.log
pi@raspberrypi4-iob:/opt/iobroker $

@thomas-braun

Copy text starting here:

======================= SUMMARY =======================
                        v.2023-10-10


   Static hostname: raspberrypi4-iob
         Icon name: computer
  Operating System: Raspbian GNU/Linux 11 (bullseye)
            Kernel: Linux 5.10.103-v7l+
      Architecture: arm

Installation:           native
Kernel:                 armv7l
Userland:               armhf
Timezone:               Europe/Berlin (CET, +0100)
User-ID:                1000
X-Server:               false
Boot Target:            graphical.target

Pending OS-Updates:     0
Pending iob updates:    21

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  and npm
Your nodejs installation is correct

MEMORY:
               total        used        free      shared  buff/cache   available
Mem:            1.9G        446M        645M        0.0K        780M        1.3G
Swap:            99M          0B         99M
Total:          2.0G        446M        745M

Active iob-Instances:   8
Active repo: default

ioBroker Core:          js-controller           3.1.6
                        admin                   4.2.1

ioBroker Status:        iobroker is running on this host.

At least one iobroker host is running.

Objects type: file
States  type: file

Status admin and web instance:
  system.adapter.admin.0                 : admin                 - disabled, port: 8081, bind: 0.0.0.0, run as: admin
+ system.adapter.admin.1                 : admin                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.web.0                   : web                   - disabled, port: 8082, bind: 0.0.0.0, run as: admin

Objects:                1968
States:                 2764

Size of iob-Database:

5.5M    /opt/iobroker/iobroker-data/objects.json.bak
5.5M    /opt/iobroker/iobroker-data/objects.json
700K    /opt/iobroker/iobroker-data/states.json.bak
700K    /opt/iobroker/iobroker-data/states.json



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

=== Mark text until here for copying ===

@foxriver76 sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

Wer sich unsicher ist, ob ein Fehler vorliegt, sollte am besten hier im Thread das Problem beschreiben. So können wir alle versuchen, das Problem nachzuvollziehen und ggf. einzugrenzen.

Hallo zusammen,
wollte nun endlich mal meinen uralten js controller aktualisieren.

Habe die Schritte

• iobroker stop
• cd /opt/iobroker

abgearbeitet.

Leider läuft aber iob upgrade self nicht durch.
Es kommen folgende Fehlermeldungen. Woran kann das liegen / wie kann ich das lösen?

pi@raspberrypi4-iob:/ $ iobroker upgrade self
Update js-controller from @3.1.6 to @5.0.16
NPM version: 10.2.3
npm install iobroker.js-controller@5.0.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
 Objects 127.0.0.1:58398 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["SET","lua-time-limit","10000"]
 States 127.0.0.1:35658 Error from InMemDB: Error: CONFIG-UNSUPPORTED for ["SET","notify-keyspace-events","Exe"]
 Objects 127.0.0.1:58398 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
 States 127.0.0.1:35658 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
 Objects 127.0.0.1:58398 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
 Objects 127.0.0.1:58398 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! Unable to increase LUA script timeout: Error CONFIG-UNSUPPORTED for ["SET","lua-time-limit","10000"]
npm ERR!  Unable to enable Expiry Keyspace events from Redis Server: Error CONFIG-UNSUPPORTED for ["SET","notify-keyspace-events","Exe"]
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 process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
npm ERR!   command: {
npm ERR!     name: 'scan',
npm ERR!     args: [ '0', 'MATCH', 'cfg.o.system.host.*', 'COUNT', '250' ]
npm ERR!   }
npm ERR! }
npm ERR!
npm ERR! Node.js v18.19.0

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-07T19_37_56_146Z-debug-0.log
Starting node restart.js
pi@raspberrypi4-iob:/ $