So ich denke, ich habs sauber bekommen, auch wenn die Pakete keine Fehler erzeugt haben:
Iobroker gestoppt (iob stop)
Alle direkten "root"-Pakete aus der package.json rausgeschmissen:
pi@MWHome:/opt/iobroker $ cat package.json
{
"name": "iobroker.inst",
"version": "2.0.3",
"private": true,
"description": "Automation platform in node.js",
"scripts": {
"install": "node lib/checkVersions.js",
"postinstall": "node lib/install.js",
"test": "node node_modules/mocha/bin/mocha --exit"
},
"dependencies": {
"iobroker.admin": "5.4.9",
"iobroker.backitup": "2.4.9",
"iobroker.dwd": "2.8.3",
"iobroker.flot": "^1.10.7",
"iobroker.info": "^1.9.19",
"iobroker.javascript": "5.7.0",
"iobroker.js-controller": "4.0.23",
"iobroker.linux-control": "1.1.3",
"iobroker.mercedesme": "0.0.56",
"iobroker.mqtt": "4.0.7",
"iobroker.node-red": "3.3.1",
"iobroker.pi-hole": "^1.3.4",
"iobroker.ping": "1.5.3",
"iobroker.simple-api": "2.7.0",
"iobroker.socketio": "4.2.0",
"iobroker.sourceanalytix": "0.4.14",
"iobroker.sql": "2.1.7",
"iobroker.tr-064": "4.2.16",
"iobroker.vis": "1.4.15",
"iobroker.vis-hqwidgets": "1.2.0",
"iobroker.vis-materialdesign": "0.5.9",
"iobroker.web": "4.3.0",
"iobroker.yahka": "^0.13.1"
}
}
das iob rebuild durchgeführt:
pi@MWHome:/opt/iobroker $ iobroker rebuild self
Rebuilding native module "self" ...
rebuilt dependencies successfully
Rebuilding native modules done
Dann mit npm list kontrolliert:
pi@MWHome:/opt/iobroker $ npm list
iobroker.inst@2.0.3 /opt/iobroker
├── camelcase@3.0.0 extraneous
├── cliui@3.2.0 extraneous
├── code-point-at@1.1.0 extraneous
├── colors@1.4.0 extraneous
├── decamelize@1.2.0 extraneous
├── error-ex@1.3.2 extraneous
├── find-up@1.1.2 extraneous
├── fs-extra@7.0.1 extraneous
├── get-caller-file@1.0.3 extraneous
├── hosted-git-info@2.8.9 extraneous
├── invert-kv@1.0.0 extraneous
├── iobroker.admin@5.4.9
├── iobroker.backitup@2.4.9
├── iobroker.dwd@2.8.3
├── iobroker.flot@1.11.0
├── iobroker.info@1.9.19
├── iobroker.javascript@5.7.0
├── iobroker.js-controller@4.0.23
├── iobroker.linux-control@1.1.3
├── iobroker.mercedesme@0.0.56
├── iobroker.mqtt@4.0.7
├── iobroker.node-red@3.3.1
├── iobroker.pi-hole@1.3.4
├── iobroker.ping@1.5.3
├── iobroker.simple-api@2.7.0
├── iobroker.socketio@4.2.0
├── iobroker.sourceanalytix@0.4.14
├── iobroker.sql@2.1.7
├── iobroker.tr-064@4.2.16
├── iobroker.vis-hqwidgets@1.2.0
├── iobroker.vis-materialdesign@0.5.9
├── iobroker.vis@1.4.15
├── iobroker.web@4.3.0
├── iobroker.yahka@0.13.1
├── iobroker@2.0.3 extraneous
├── is-core-module@2.9.0 extraneous
├── jsonfile@4.0.0 extraneous
├── lcid@1.0.0 extraneous
├── load-json-file@1.1.0 extraneous
├── normalize-package-data@2.5.0 extraneous
├── number-is-nan@1.0.1 extraneous
├── os-locale@1.4.0 extraneous
├── parse-json@2.2.0 extraneous
├── path-exists@2.1.0 extraneous
├── path-parse@1.0.7 extraneous
├── path-type@1.1.0 extraneous
├── pify@2.3.0 extraneous
├── pinkie-promise@2.0.1 extraneous
├── pinkie@2.0.4 extraneous
├── read-pkg-up@1.0.1 extraneous
├── read-pkg@1.1.0 extraneous
├── require-main-filename@1.0.1 extraneous
├── resolve@1.22.1 extraneous
├── spdx-correct@3.1.1 extraneous
├── spdx-exceptions@2.3.0 extraneous
├── spdx-expression-parse@3.0.1 extraneous
├── spdx-license-ids@3.0.11 extraneous
├── supports-preserve-symlinks-flag@1.0.0 extraneous
├── validate-npm-package-license@3.0.4 extraneous
├── which-module@1.0.0 extraneous
├── wrap-ansi@2.1.0 extraneous
├── y18n@3.2.2 extraneous
├── yargs-parser@5.0.1 extraneous
└── yargs@7.1.2 extraneous
Kamen eine Menge extraneous Pakete.
npm prune durchgeführt
pi@MWHome:/opt/iobroker $ npm prune
removed 54 packages in 7s
102 packages are looking for funding
run `npm fund` for details
npm list - scheint nun sauber zu sein:
pi@MWHome:/opt/iobroker $ npm list
iobroker.inst@2.0.3 /opt/iobroker
├── iobroker.admin@5.4.9
├── iobroker.backitup@2.4.9
├── iobroker.dwd@2.8.3
├── iobroker.flot@1.11.0
├── iobroker.info@1.9.19
├── iobroker.javascript@5.7.0
├── iobroker.js-controller@4.0.23
├── iobroker.linux-control@1.1.3
├── iobroker.mercedesme@0.0.56
├── iobroker.mqtt@4.0.7
├── iobroker.node-red@3.3.1
├── iobroker.pi-hole@1.3.4
├── iobroker.ping@1.5.3
├── iobroker.simple-api@2.7.0
├── iobroker.socketio@4.2.0
├── iobroker.sourceanalytix@0.4.14
├── iobroker.sql@2.1.7
├── iobroker.tr-064@4.2.16
├── iobroker.vis-hqwidgets@1.2.0
├── iobroker.vis-materialdesign@0.5.9
├── iobroker.vis@1.4.15
├── iobroker.web@4.3.0
└── iobroker.yahka@0.13.1
Auch package-lock.json wird wieder fleißig mitgeschrieben:
pi@MWHome:/opt/iobroker $ ls -la
insgesamt 656
drwxrwxrwx+ 8 iobroker iobroker 4096 29. Jul 18:47 .
drwxr-xr-x 6 root root 4096 21. Feb 08:33 ..
lrwxrwxrwx 1 iobroker iobroker 21 20. Dez 2019 backups -> /data/backup/iobroker
drwxrwxrwx+ 2 iobroker iobroker 4096 20. Dez 2019 backups.org
-rwxrwxrwx+ 1 iobroker iobroker 1049 8. Sep 2019 CHANGELOG_FIXER_LINUX.md
-rwxrwxrwx+ 1 iobroker iobroker 3556 8. Sep 2019 CHANGELOG_INSTALLER_LINUX.md
-rwxrwxrwx+ 1 iobroker iobroker 23988 8. Sep 2019 fix_installation.sh
drwxrwxrwx+ 3 iobroker iobroker 4096 8. Sep 2019 install
-rwxrwxrwx+ 1 iobroker iobroker 1087 26. Apr 14:43 INSTALLER_INFO.txt
lrwxrwxrwx 1 iobroker iobroker 22 26. Apr 14:43 iob -> /opt/iobroker/iobroker
-rwxr-xr-x+ 1 iobroker iobroker 305 26. Apr 14:43 iobroker
drwxrwxrwx+ 10 iobroker iobroker 4096 29. Jul 18:49 iobroker-data
drwxrwxrwx+ 2 iobroker iobroker 4096 8. Sep 2019 lib
-rwxrwxrwx+ 1 iobroker iobroker 1137 8. Sep 2019 LICENSE
drwxrwxrwx+ 2 iobroker iobroker 4096 29. Jul 18:50 log
drwxrwxr-x+ 732 iobroker iobroker 69632 29. Jul 18:48 node_modules
-rwxrwxrwx+ 1 iobroker iobroker 175 29. Jul 13:35 .npmrc
-rwxrwxrwx+ 1 iobroker iobroker 1093 29. Jul 18:47 package.json
-rw-rw-r--+ 1 iobroker iobroker 498074 29. Jul 18:48 package-lock.json
-rwxrwxrwx+ 1 iobroker iobroker 6101 8. Sep 2019 README.md
-rwxrwxrwx+ 1 iobroker iobroker 5693 23. Dez 2021 reinstall.js
Alle Instanzen grün, keine Fehlermeldungen im Log.
Sorry @kBrausew, dass ich Deinen Thread etwas missbraucht habe. Aber ich würde Dich nach diesen Erfahrungen durchaus ermutigen, Dein node_module Verzeichnis neu aufzubauen, wie hier beschrieben: https://forum.iobroker.net/topic/56543/nach-nodejs-update-kein-adapter-mehr-updatebar/23?_=1658914381795
An alle anderen - vielen Dank für die direkte und indirekte Hilfe.
@Thomas-Braun Sorry fürs Nerven. 😉