Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[Accu]

@thomas-braun ich habe jetzt mal meine Backup Speicherkarte vom System genommen, weil die andere Installation komplett zerschossen war.
Habe jetzt alle Updates gemacht und der iobroker läuft wieder.
Allerdings habe ich Probleme bei der Authentifizierung in den Adapter settings. Der Button lässt sich nicht drücken und erscheint ausgegraut. Auch in Firefox das gleiche. Liegt das evtl. an der veralteten Node Version. Gibt's da eine Möglichkeit noch aktuellere Versionen zu installieren ohne das bestehende Altsystem wieder zu Schrotten?

mein System sieht so aus:

Es gibt keine Nutzer-Sitzungen mit veralteten Prozessen.
pi@Raspi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v14.21.3
/usr/bin/node
v14.21.3
/usr/bin/npm
6.14.18
nodejs:
  Installiert:           14.21.3-deb-1nodesource1
  Installationskandidat: 14.21.3-deb-1nodesource1
  Versionstabelle:
 *** 14.21.3-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u3 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages

[Thomas Braun]

@accu

iob nodejs-update

[Accu]

@thomas-braun

ioBroker nodejs fixer 2023-10-13
No recommendation for a nodejs version found on your system. We recommend to install latest version from nodejs v18 tree.

Your current setup is:
/usr/bin/nodejs 	v14.21.3
/usr/bin/node 		v14.21.3
/usr/bin/npm 		6.14.18
/usr/local/bin/npx 		8.1.2
/usr/local/bin/corepack 	0.10.0

*** nodejs is NOT correctly installed ***
We found these nodejs versions available for installation:

nodejs:
  Installed: 14.21.3-deb-1nodesource1
  Candidate: 14.21.3-deb-1nodesource1
  Version table:
 *** 14.21.3-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u3 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages



Your nodejs-Installation seems to be faulty. Shall we try to fix it?
Press <y> to continue or any other key to quit

Fixing your nodejs setup
*** Deleting /usr/local/bin/npx ***
*** Deleting /usr/local/bin/corepack ***

Wrong paths have been fixed. Run 'iob diag' or 'iob node-fix' again to check if your installation is fine now

You are running nodejs v14.21.3. Do you want to install latest version from nodejs v.18 tree? 

Press <y> to continue or any other key to quit
Trying to update your installation now. Please be patient.
Waiting for ioBroker to shut down - Give me a minute...
############################################################

*** These repos are active on your system:
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists... Done

*** Installing ca-certificates, curl and gnupg, just in case they are missing.

*** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source

deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
Package: nodejs
Pin: origin deb.nodesource.com
Pin-Priority: 1001

*** These repos are active after the adjustments:
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease              
Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB]   
Get:4 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [6272 B]
Fetched 18.4 kB in 4s (5030 B/s)   
Reading package lists... Done

Installing the recommended nodejs version now!

Exact recommended version unknown, installing a fallback!
(Reading database ... 144794 files and directories currently installed.)
Preparing to unpack .../nodejs_18.0.0-1nodesource1_armhf.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.0.0-1nodesource1) over (14.21.3-deb-1nodesource1) ...
Setting up nodejs (18.0.0-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
Scanning processes...                                                                                                                     
Scanning candidates...                                                                                                                    
Scanning linux images...                                                                                                                  

Failed to check for processor microcode upgrades.

Restarting services...
 systemctl restart pm2.service

No containers need to be restarted.

No user sessions are running outdated binaries.

Updating fallback to latest nodejs v18 release
(Reading database ... 145600 files and directories currently installed.)
Preparing to unpack .../nodejs_18.19.0-1nodesource1_armhf.deb ...
Detected old npm client, removing...
Unpacking nodejs (18.19.0-1nodesource1) over (18.0.0-1nodesource1) ...
Setting up nodejs (18.19.0-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
Scanning processes...                                                                                                                     
Scanning candidates...                                                                                                                    
Scanning linux images...                                                                                                                  

Failed to check for processor microcode upgrades.

Restarting services...
 systemctl restart pm2.service

No containers need to be restarted.

No user sessions are running outdated binaries.
v18.19.0 has been installed! You are using the latest version now!
Installing the recommended nodejs version!

We tried our best to fix your nodejs. Please run iob diag again to verify.

*** RESTARTING ioBroker NOW! *** 
 Please refresh or restart your browser in a few moments.

[Thomas Braun]

@accu

Schau mit

iob diag

nach, ob das jetzt richtig installiert wurde.

[Accu]

@thomas-braun leider ist der Netatmo Authenticate Button immer noch ausgegraut :(

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


   Static hostname: Raspi
         Icon name: computer
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 6.1.64-v7+
      Architecture: arm

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

Pending OS-Updates: 	0
Pending iob updates: 	32

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:           922M        650M        109M        1.0M        162M        209M
Swap:           99M         99M        0.0K
Total:         1.0G        750M        109M

Active iob-Instances: 	11
Active repo: stable

ioBroker Core: 		js-controller 		3.3.22
			admin 			5.2.3

ioBroker Status: 	iobroker is running on this host.


Objects type: file
States  type: file

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

Objects: 		28472
States: 		14139

Size of iob-Database:

20M	/opt/iobroker/iobroker-data/objects.json.bak
20M	/opt/iobroker/iobroker-data/objects.json
17M	/opt/iobroker/iobroker-data/objects.json.broken
12K	/opt/iobroker/iobroker-data/objects.json.old
2.8M	/opt/iobroker/iobroker-data/states.json.bak
2.8M	/opt/iobroker/iobroker-data/states.json
1.9M	/opt/iobroker/iobroker-data/states.json.old
0	/opt/iobroker/iobroker-data/states.json.broken



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

[Thomas Braun]

@accu sagte in Adapter werden nicht mehr geupdated:

Pending iob updates: 32

Und 1 GB RAM ist zu wenig.

[Accu]

@thomas-braun wie gesagt die updates macht er nicht bzw. läuft durch bei den updates aber bietet diese dann wieder zum update an

[Thomas Braun]

@accu

Zeigen...

iob update
iob upgrade all

[Accu]

@thomas-braun glaube meine sicherungskopie hat es jetzt auch hinter sich:

Last login: Sun Dec 10 10:20:16 on console
accu@iMac ~ % ssh pi@192.168.1.13
pi@192.168.1.13's password: 
Linux Raspi 6.1.64-v7+ #1702 SMP Wed Nov 29 14:16:46 GMT 2023 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Dec 10 08:29:18 2023
pi@Raspi:~ $ iob status
node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.0
pi@Raspi:~ $ iob upgrade all
node:internal/modules/cjs/loader:1137
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15)
    at Module._load (node:internal/modules/cjs/loader:975:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.19.0
pi@Raspi:~ $ 

[Accu]

@thomas-braun
ich installiere jetzt mal die Bookworm Version auf ner anderen Speicherkarte und berichte ...

[Thomas Braun]

@accu

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

[Accu]

@thomas-braun ich hoffe er läuft diesmal durch. Musste nach 4h letztens abbrechen, weil er eingeforen ist.

pi@Raspi:~ $ cd /opt/iobroker
pi@Raspi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated passport.socketio@3.7.0: Please check the workaround in https://github.com/jfromaniello/passport.socketio/issues/148
npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated bcrypt@3.0.8: versions < v5.0.0 do not handle NUL in passwords properly
npm WARN deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm.
npm WARN deprecated node-pre-gyp@0.12.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated node-pre-gyp@0.14.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
(##################) ⠹ reify:iobroker.admin: http fetch GET 200 https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.4.9.tgz 923762ms (cache miss)

[Accu]

@thomas-braun installation ist erfolgreich durchgelaufen und der neu ioBroker installiert gerade die Instanzen.
Was schmerzt sind, dass ich meine skripte aus dem alten ioB nicht mehr habe.

Die speicherkarte mit der geschrotteten iob instanz habe ich noch. Gibts da irgendeine chance die Blockly Skripte rauszuextrahieren?

[Thomas Braun]

@accu

Hast du kein gescheites Backup extern liegen?

[Accu]

@thomas-braun leider nein - ich hatte nur immer backups auf der gleichen Speicherkarte gemacht.
andere Frage: es gab doch mal unter Buster einen Befahl wo man den Speicher für die ioBroker optimieren konnte. Wie hieß der gleich nochmal?

[Thomas Braun]

@accu sagte in Adapter werden nicht mehr geupdated:

es gab doch mal unter Buster einen Befahl wo man den Speicher für die ioBroker optimieren konnte. Wie hieß der gleich nochmal?

Keine Ahnung was du meinst.

[Accu]

@thomas-braun ich finde den Post leider nicht mehr. Ich hatte damals schon gepostet, dass ich zu wenig Speicher frei habe.
Du hattest mir mal einen Befehl genannt wo man (leihenhafte Wiedergabe) den Speicher für alle Adapter konsolidieren kann mit dem Nachteil, wenn ein Adapter dann abstürzt alle runtergerissen werden.

[Thomas Braun]

@accu

Vermutlich meinst du den Kompakt-Modus des iobroker.
Ich weiß aber so aus dem Kopf nicht wo der einzustellen ist.

Aber ich würde dringend zu einem größeren Rechner raten. Mit 1 GB reißt du nix mehr.

[Codierknecht]

@accu sagte in Adapter werden nicht mehr geupdated:

Gibts da irgendeine chance die Blockly Skripte rauszuextrahieren?

Hast Du noch irgendwo das JavaScript davon rumliegen?
Dann hilft das hier: https://forum.iobroker.net/topic/70930/backup-von-scripten-wiederherstellen-json-xml/2

Edit
Es gibt auch ein Script, um Blockly aus Sicherungen wiederherzustellen.
Musst Du hier im Forum mal suchen ...

[Accu]

@thomas-braun ja genau das war es. Das hatte eigentlich gut funktioniert. Habs gefunden:

pi@raspberrypi:~ $ iob compact enable

Compact mode for this host is now enabled

Please restart ioBroker for this change to take effect!
pi@raspberrypi:~ $ 

bzgl. neuen Rechner hatte ich gesehen, dass es jetzt ja schon einen Raspberry 5 gibt. Was würdest du empfehlen? 4er oder 5er? (ich würde eigentlich gerne vermeiden wollen dass ich alles neu kaufen muss und würde mein Gehäuse gerne weiter nutzen wollen. Beim 5er braucht man wohl extra Kühlkörper ..
Ich nutze den Raspi, wie gesagt nur für ein paar Adapter die ganzen features mit schnelleren USB Ports etc. brauche ich eigentlich nicht wirklich.