NEWS
Adapter Update nicht möglich (Synology Docker)
-
Also,
habe jetzt alles händisch bereinigt.
root@ioBroker:/opt/iobroker# npm ls sudo: unable to resolve host ioBroker: Name or service not known iobroker.inst@3.0.0 /opt/iobroker ├── iobroker.admin@5.4.9 ├── iobroker.alexa2@3.11.2 invalid: "3.18.6" from the root project ├── iobroker.alias-manager@1.2.4 ├── iobroker.backitup@2.4.9 invalid: "2.4.10" from the root project ├── iobroker.cloud@4.1.1 ├── iobroker.denon@1.13.4 ├── iobroker.devices@1.0.12 ├── iobroker.discovery@3.0.5 ├── iobroker.dwd@2.8.3 ├── iobroker.echarts@1.0.12 ├── iobroker.enigma2@1.3.4 (git+ssh://git@github.com/Matten-Matten/ioBroker.enigma2.git#4198fa2049f66bb5eb274a24ae64f4fa3149065f) ├── iobroker.feiertage@1.1.0 ├── iobroker.flot@1.11.0 ├── iobroker.fritzbox@0.5.0 ├── iobroker.fullybrowser@2.1.2 ├── iobroker.geofency@1.1.1 ├── iobroker.harmony@1.2.2 ├── iobroker.heizoel@1.0.3 ├── iobroker.history@2.2.0 ├── iobroker.hm-rega@3.0.40 ├── iobroker.hm-rpc@1.15.12 ├── iobroker.hue@3.7.0 ├── iobroker.ical@1.13.1 ├── iobroker.icons-addictive-flavour-png@0.1.0 ├── iobroker.icons-fatcow-hosting@0.1.0 ├── iobroker.icons-icons8@0.0.1 ├── iobroker.icons-material-png@0.1.0 ├── iobroker.icons-mfd-png@1.1.0 ├── iobroker.icons-mfd-svg@1.1.0 ├── iobroker.icons-open-icon-library-png@0.1.2 ├── iobroker.icons-ultimate-png@1.0.1 ├── iobroker.info@1.9.19 ├── iobroker.iot@1.11.8 ├── iobroker.javascript@6.0.0 ├── iobroker.js-controller@4.0.23 ├── iobroker.linkeddevices@1.5.5 ├── iobroker.midea@0.0.7 ├── iobroker.mihome-vacuum@3.4.2 ├── iobroker.nut@1.5.1 ├── iobroker.octoprint@4.0.0 ├── iobroker.oilfox@4.1.2 ├── iobroker.openweathermap@0.2.5 ├── iobroker.powerfox2@0.0.12 ├── iobroker.ring@1.2.8 ├── iobroker.scenes@2.3.9 ├── iobroker.shelly@5.3.2 ├── iobroker.simple-api@2.7.0 ├── iobroker.snmp@1.0.0 ├── iobroker.socketio@4.2.0 ├── iobroker.spotify-premium@1.2.2 ├── iobroker.synology@2.1.9 ├── iobroker.telegram@1.13.0 ├── iobroker.text2command@2.2.1 ├── iobroker.vis-bars@0.1.4 ├── iobroker.vis-colorpicker@1.2.0 ├── iobroker.vis-fancyswitch@1.1.0 ├── iobroker.vis-google-fonts@1.0.3 ├── iobroker.vis-history@1.0.0 ├── iobroker.vis-hqwidgets@1.2.0 ├── iobroker.vis-icontwo@0.87.0 ├── iobroker.vis-inventwo@3.3.1 ├── iobroker.vis-jqui-mfd@1.0.12 ├── iobroker.vis-justgage@1.0.2 ├── iobroker.vis-keyboard@0.0.2 ├── iobroker.vis-map@1.0.4 ├── iobroker.vis-materialdesign@0.5.75 (git+ssh://git@github.com/Scrounger/ioBroker.vis-materialdesign.git#edc0a76f299981322c2c369e00f671e4123d791b) ├── iobroker.vis-metro@1.2.0 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-plumb@1.0.2 ├── iobroker.vis-timeandweather@1.1.7 ├── iobroker.vis-weather@2.5.5 ├── iobroker.vis@1.4.15 ├── iobroker.vw-connect@0.0.51 ├── iobroker.web@4.3.0 ├── iobroker.wled@0.6.7 └── iobroker.ws@1.3.0
Wenn ich jetzt updaten will gehts aber weiter:
root@ioBroker:/opt/iobroker# iobroker upgrade backitup --debug This upgrade of "backitup" will introduce the following changes: ========================================================================== -> 2.4.10: Code cleaning dependencies updated Disclaimer added Travis Support removed Fix backup-download with ssl ========================================================================== Would you like to upgrade backitup from @2.4.9 to @2.4.10 now? [(y)es, (n)o]: y Update backitup from @2.4.9 to @2.4.10 NPM version: 8.11.0 Installing iobroker.backitup@2.4.10... (System call) npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/iobroker.javascript/node_modules/cheerio npm ERR! dest /opt/iobroker/node_modules/iobroker.javascript/node_modules/.cheerio-o2N1P1df npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/iobroker.javascript/node_modules/cheerio' -> '/opt/iobroker/node_modules/iobroker.javascript/node_modules/.cheerio-o2N1P1df' npm ERR! A complete log of this run can be found in: npm ERR! /opt/iobroker/.npm/_logs/2022-08-14T10_21_10_218Z-debug-0.log host.ioBroker Cannot install iobroker.backitup@2.4.10: 217
Kann ich mir irgendwie anzeigen lassen, welche Ordner alle gelöscht werden müssen? Bzw. sie automatisch löschen lassen?
-
Dann gleiche Übung in den jetzt aufpoppenden Verzeichnissen.
-
@thomas-braun
ok. das wird dauern. -
Möglich.
-
Jetzt läuft der ioBroke rgar nicht mehr
root@ioBroker:/opt/iobroker# iobroker status node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'follow-redirects' Require stack: - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/adapters/http.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/defaults.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/transformData.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/dispatchRequest.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/Axios.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/axios.js - /opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/index.js - /opt/iobroker/node_modules/@alcalzone/pak/build/lib/package-managers/npm/index.js - /opt/iobroker/node_modules/@alcalzone/pak/build/lib/pak.js - /opt/iobroker/node_modules/@alcalzone/pak/build/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at Object.<anonymous> (/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/adapters/http.js:9:18) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Module.require (node:internal/modules/cjs/loader:1005:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/adapters/http.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/defaults.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/transformData.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/dispatchRequest.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/core/Axios.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/lib/axios.js', '/opt/iobroker/node_modules/@alcalzone/pak/node_modules/axios/index.js', '/opt/iobroker/node_modules/@alcalzone/pak/build/lib/package-managers/npm/index.js', '/opt/iobroker/node_modules/@alcalzone/pak/build/lib/pak.js', '/opt/iobroker/node_modules/@alcalzone/pak/build/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ]
follow-redirects sollte ich löschen. Danach ging nichts mehr
-
@huettmaster sagte in Adapter Update nicht möglich (Synology Docker):
follow-redirects sollte ich löschen.
Das denke ich nicht. Die zu löschenden Verzeichnisse heißen alle .modulname-kasdhfs oder ähnlich.
Was hast du eigentlich für komische Versionen da installiert?
Das ist weder Fisch (stable) noch Fleisch (beta).├── iobroker.admin@5.4.9 ├── iobroker.alexa2@3.11.2 invalid: "3.18.6" from the root project ├── iobroker.backitup@2.4.9 invalid: "2.4.10" from the root project
-
Die zu löschenden Verzeichnisse wurden mir so angezeigt. Inklusive des follow-redirects.
npm ERR! path /opt/iobroker/node_modules/iobroker.javascript/node_modules/assertion-error npm ERR! dest /opt/iobroker/node_modules/iobroker.javascript/node_modules/.assertion-error-BzhHkLQk
Die Versionen der Adapter wurden mir so angezeigt zum Update...
Ich werde jetzt erstmal das Filesystem wieder auf den Stand von gestern Abend bringen und von vorn anfangen. So funktioniert es jedenfalls nicht. Muss ich den Ordner im unter Pfad oder dem oberen Pfad löschen?
-
@huettmaster sagte in Adapter Update nicht möglich (Synology Docker):
.assertion-error-BzhHkLQk
wäre dann zu löschen, analog da dann ein
Verzeichnis.follow-redirects-GNnuPflM
oder wie auch immer das Suffix genau aussähe. Die Löschung ist aber für die Laufzeit des ioBrokers unerheblich.Kurz: Hast ja einen Docker, installier es neu.
-
@thomas-braun ok. Danke schonmal.
-
habe den Container neu aufgesetzt und per Backitup das Backup drüberlaufen lassen. Jetzt funzt alles.