NEWS
Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl
ioBroker Allgemein
15
Beiträge
3
Kommentatoren
1.1k
Aufrufe
3
Watching
-
cd /opt/iobroker && npm ls iobroker.type-detector@thomas-braun said in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
npm ls iobroker.type-detector
iobroker.inst@1.3.1 /opt/iobroker └─┬ iobroker.iot@1.14.5 └── iobroker.type-detector@1.1.2 -
@thomas-braun said in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
npm ls iobroker.type-detector
iobroker.inst@1.3.1 /opt/iobroker └─┬ iobroker.iot@1.14.5 └── iobroker.type-detector@1.1.2@masterg87 sagte in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
iobroker.iot
Installier den nochmal drüber.
-
@masterg87 sagte in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
iobroker.iot
Installier den nochmal drüber.
@thomas-braun
Bin mir leider nicht ganz sicher wie man drüber installiert. Habe es jetzt so gemacht und folgenden Fehler. Hast du folgenden Befehl gemeint?npm install iobroker.iot
npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. 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 hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@4.2.1: this library is no longer supported npm WARN deprecated node-pre-gyp@0.6.39: 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 hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 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. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /opt/iobroker/iobroker.ws.server/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/iobroker.ws.server/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-09-05T19_12_40_374Z-debug-0.log -
@thomas-braun
Bin mir leider nicht ganz sicher wie man drüber installiert. Habe es jetzt so gemacht und folgenden Fehler. Hast du folgenden Befehl gemeint?npm install iobroker.iot
npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. 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 hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@4.2.1: this library is no longer supported npm WARN deprecated node-pre-gyp@0.6.39: 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 hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 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. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /opt/iobroker/iobroker.ws.server/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/iobroker.ws.server/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-09-05T19_12_40_374Z-debug-0.logFinger weg von direkten npm-Kommandos.
Und immer vollständige Ein- wie Ausgaben zeigen. Bei einigen Befehlen ist es wichtig wo man gerade im Dateisystem herumsteht. Bei npm z. B....iob upgrade iobroker.iot@1.14.5 --debugist dein Freund.
-
@thomas-braun
Danke für die Aufklärung. Ich habe den Server auch mal wieder aufs letzte Backup zurückgesetzt, da ich so einiges mit npm direkt gerade selbst probiert habe.Auf dem zurückgespielten Backup habe ich im Ordner /opt/iobroker folgenden Befehl ausgeführt:
iob upgrade iobroker.iot@1.14.5 --debugOutput davon ist:
Would you like to reinstall version 1.14.5 of iot now? [(y)es, (n)o]: y Update iot from @1.14.5 to @1.14.5 host.Iobroker Adapter "system.adapter.iot.0" is stopped. NPM version: 9.6.7 Installing iobroker.iot@1.14.5... (System call) npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. 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 cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated node-pre-gyp@0.6.39: 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 request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@4.2.1: this library is no longer supported npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated appium-logger@2.1.0: Moved into appium-support npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 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. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /opt/iobroker/iobroker.type-detector/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/iobroker.type-detector/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-09-05T20_32_46_906Z-debug-0.log host.Iobroker Cannot install iobroker.iot@1.14.5: 254Der Output von deinem vorherigen Tipp war:
username@Iobroker:/opt/iobroker$ npm ls iobroker.type-detectoriobroker.inst@1.3.1 /opt/iobroker └─┬ iobroker.iot@1.14.5 └── iobroker.type-detector@1.1.2Irgendwie bekomme ich diese npm Warnings und Fehler nicht weg :-(
-
@thomas-braun
Danke für die Aufklärung. Ich habe den Server auch mal wieder aufs letzte Backup zurückgesetzt, da ich so einiges mit npm direkt gerade selbst probiert habe.Auf dem zurückgespielten Backup habe ich im Ordner /opt/iobroker folgenden Befehl ausgeführt:
iob upgrade iobroker.iot@1.14.5 --debugOutput davon ist:
Would you like to reinstall version 1.14.5 of iot now? [(y)es, (n)o]: y Update iot from @1.14.5 to @1.14.5 host.Iobroker Adapter "system.adapter.iot.0" is stopped. NPM version: 9.6.7 Installing iobroker.iot@1.14.5... (System call) npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.type-detector@file:iobroker.type-detector (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.objects-redis@file:iobroker.objects-redis (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker-react-components@file:iobroker-react-components (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws@file:iobroker.ws (null) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.ws.server@file:iobroker.ws.server (null) seems to be corrupted. Trying again. 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 cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated node-pre-gyp@0.6.39: 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 request@2.81.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@4.2.1: this library is no longer supported npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial). npm WARN deprecated appium-logger@2.1.0: Moved into appium-support npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 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. npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /opt/iobroker/iobroker.type-detector/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/opt/iobroker/iobroker.type-detector/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-09-05T20_32_46_906Z-debug-0.log host.Iobroker Cannot install iobroker.iot@1.14.5: 254Der Output von deinem vorherigen Tipp war:
username@Iobroker:/opt/iobroker$ npm ls iobroker.type-detectoriobroker.inst@1.3.1 /opt/iobroker └─┬ iobroker.iot@1.14.5 └── iobroker.type-detector@1.1.2Irgendwie bekomme ich diese npm Warnings und Fehler nicht weg :-(
Noch ein kleiner Nachtrag:
Ich habe noch folgenden Befehl ausgeführt:
username@Iobroker:/opt/iobroker$ npm lsund folgenden Output bekommen:
npm ERR! code ELSPROBLEMS npm ERR! missing: @abandonware/bluetooth-hci-socket@^0.5.3-4, required by iobroker.inst@1.3.1 npm ERR! missing: @abandonware/noble@^1.9.2-6, required by iobroker.inst@1.3.1 npm ERR! missing: bluetooth-hci-socket@git+https://github.com/jrobeson/node-bluetooth-hci-socket.git#fix-builds-for-node-10, required by iobroker.inst@1.3.1 npm ERR! missing: colors@^1.3.2, required by iobroker.inst@1.3.1 npm ERR! missing: fs-extra@^7.0.0, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker-react-components@file:node_modules/iobroker-react-components, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.objects-redis@file:node_modules/iobroker.objects-redis, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.samsung@0.5.8, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.type-detector@file:node_modules/iobroker.type-detector, required by iobroker.inst@1.3.1 npm ERR! invalid: iobroker.ws.server@ /opt/iobroker/node_modules/iobroker.ws.server npm ERR! invalid: iobroker.ws@ /opt/iobroker/node_modules/iobroker.ws npm ERR! missing: mocha@^9.0.0, required by iobroker.inst@1.3.1 npm ERR! missing: node-mihome@0.0.32, required by iobroker.inst@1.3.1 npm ERR! missing: pcap@^3.1.0, required by iobroker.inst@1.3.1 npm ERR! missing: semver@^5.5.0, required by iobroker.inst@1.3.1 npm ERR! missing: yargs@^7.0.2, required by iobroker.inst@1.3.1 iobroker.inst@1.3.1 /opt/iobroker ├── UNMET DEPENDENCY @abandonware/bluetooth-hci-socket@^0.5.3-4 ├── UNMET DEPENDENCY @abandonware/noble@^1.9.2-6 ├── @iobroker/types@5.0.12 ├── UNMET DEPENDENCY bluetooth-hci-socket@git+https://github.com/jrobeson/node-bluetooth-hci-socket.git#fix-builds-for-node-10 ├── UNMET DEPENDENCY colors@^1.3.2 ├── UNMET DEPENDENCY fs-extra@^7.0.0 ├── UNMET DEPENDENCY iobroker-react-components@file:node_modules/iobroker-react-components ├── iobroker.admin@6.3.5 ├── iobroker.alexa@0.0.36 ├── iobroker.alexa2@3.24.1 ├── iobroker.amazon-dash@1.2.0 ├── iobroker.backitup@2.6.23 ├── iobroker.ble@0.13.4 ├── iobroker.cloud@4.4.1 ├── iobroker.daswetter@3.1.10 ├── iobroker.discovery@3.1.0 ├── iobroker.dwd@2.8.5 ├── iobroker.fakeroku@0.2.2 ├── iobroker.geofency@1.2.4 ├── iobroker.harmony@1.2.2 ├── iobroker.history@2.2.6 ├── iobroker.hmip@1.20.0 ├── iobroker.hs100@2.1.2 ├── iobroker.hue@3.9.5 ├── iobroker.ical@1.13.3 ├── iobroker.icons-mfd-png@1.1.0 ├── iobroker.icons-mfd-svg@1.1.0 ├── iobroker.info@1.9.26 ├── iobroker.iot@1.14.5 ├── iobroker.javascript@7.0.3 ├── iobroker.js-controller@4.0.24 ├── iobroker.mihome-vacuum@3.11.0 ├── iobroker.mihome@1.4.0 ├── UNMET DEPENDENCY iobroker.objects-redis@file:node_modules/iobroker.objects-redis ├── iobroker.ping@1.6.2 ├── iobroker.radar@1.2.1 ├── iobroker.rpi2@1.3.2 ├── UNMET DEPENDENCY iobroker.samsung@0.5.8 ├── iobroker.scenes@2.3.9 ├── iobroker.simple-api@2.7.2 ├── iobroker.snmp@2.4.11 ├── iobroker.socketio@6.5.2 ├── iobroker.spotify-premium@1.2.2 ├── iobroker.telegram@1.16.0 ├── iobroker.terminal@1.0.0 ├── iobroker.text2command@3.0.2 ├── iobroker.tr-064-community@0.0.1-security ├── iobroker.tr-064@4.2.18 ├── iobroker.tuya@3.14.2 ├── UNMET DEPENDENCY iobroker.type-detector@file:node_modules/iobroker.type-detector ├── iobroker.vis-bars@0.1.4 ├── iobroker.vis-canvas-gauges@1.0.1 ├── iobroker.vis-colorpicker@2.0.3 ├── iobroker.vis-fancyswitch@1.1.0 ├── iobroker.vis-history@1.0.0 ├── iobroker.vis-hqwidgets@1.4.0 ├── iobroker.vis-jqui-mfd@1.0.12 ├── iobroker.vis-justgage@1.0.2 ├── iobroker.vis-metro@1.2.0 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-timeandweather@1.2.2 ├── iobroker.vis-weather@2.5.6 ├── iobroker.vis@1.4.16 ├── iobroker.web@6.1.0 ├── iobroker.ws.server@ invalid: "file:node_modules/iobroker.ws.server" from the root project ├── iobroker.ws@ invalid: "file:node_modules/iobroker.ws" from the root project ├── UNMET DEPENDENCY mocha@^9.0.0 ├── UNMET DEPENDENCY node-mihome@0.0.32 ├── UNMET DEPENDENCY pcap@^3.1.0 ├── UNMET DEPENDENCY semver@^5.5.0 ├── typescript@4.7.4 └── UNMET DEPENDENCY yargs@^7.0.2Da ist wohl einiges durcheinander. Gibts da eine Möglichkeit das wieder zu richten?
-
Noch ein kleiner Nachtrag:
Ich habe noch folgenden Befehl ausgeführt:
username@Iobroker:/opt/iobroker$ npm lsund folgenden Output bekommen:
npm ERR! code ELSPROBLEMS npm ERR! missing: @abandonware/bluetooth-hci-socket@^0.5.3-4, required by iobroker.inst@1.3.1 npm ERR! missing: @abandonware/noble@^1.9.2-6, required by iobroker.inst@1.3.1 npm ERR! missing: bluetooth-hci-socket@git+https://github.com/jrobeson/node-bluetooth-hci-socket.git#fix-builds-for-node-10, required by iobroker.inst@1.3.1 npm ERR! missing: colors@^1.3.2, required by iobroker.inst@1.3.1 npm ERR! missing: fs-extra@^7.0.0, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker-react-components@file:node_modules/iobroker-react-components, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.objects-redis@file:node_modules/iobroker.objects-redis, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.samsung@0.5.8, required by iobroker.inst@1.3.1 npm ERR! missing: iobroker.type-detector@file:node_modules/iobroker.type-detector, required by iobroker.inst@1.3.1 npm ERR! invalid: iobroker.ws.server@ /opt/iobroker/node_modules/iobroker.ws.server npm ERR! invalid: iobroker.ws@ /opt/iobroker/node_modules/iobroker.ws npm ERR! missing: mocha@^9.0.0, required by iobroker.inst@1.3.1 npm ERR! missing: node-mihome@0.0.32, required by iobroker.inst@1.3.1 npm ERR! missing: pcap@^3.1.0, required by iobroker.inst@1.3.1 npm ERR! missing: semver@^5.5.0, required by iobroker.inst@1.3.1 npm ERR! missing: yargs@^7.0.2, required by iobroker.inst@1.3.1 iobroker.inst@1.3.1 /opt/iobroker ├── UNMET DEPENDENCY @abandonware/bluetooth-hci-socket@^0.5.3-4 ├── UNMET DEPENDENCY @abandonware/noble@^1.9.2-6 ├── @iobroker/types@5.0.12 ├── UNMET DEPENDENCY bluetooth-hci-socket@git+https://github.com/jrobeson/node-bluetooth-hci-socket.git#fix-builds-for-node-10 ├── UNMET DEPENDENCY colors@^1.3.2 ├── UNMET DEPENDENCY fs-extra@^7.0.0 ├── UNMET DEPENDENCY iobroker-react-components@file:node_modules/iobroker-react-components ├── iobroker.admin@6.3.5 ├── iobroker.alexa@0.0.36 ├── iobroker.alexa2@3.24.1 ├── iobroker.amazon-dash@1.2.0 ├── iobroker.backitup@2.6.23 ├── iobroker.ble@0.13.4 ├── iobroker.cloud@4.4.1 ├── iobroker.daswetter@3.1.10 ├── iobroker.discovery@3.1.0 ├── iobroker.dwd@2.8.5 ├── iobroker.fakeroku@0.2.2 ├── iobroker.geofency@1.2.4 ├── iobroker.harmony@1.2.2 ├── iobroker.history@2.2.6 ├── iobroker.hmip@1.20.0 ├── iobroker.hs100@2.1.2 ├── iobroker.hue@3.9.5 ├── iobroker.ical@1.13.3 ├── iobroker.icons-mfd-png@1.1.0 ├── iobroker.icons-mfd-svg@1.1.0 ├── iobroker.info@1.9.26 ├── iobroker.iot@1.14.5 ├── iobroker.javascript@7.0.3 ├── iobroker.js-controller@4.0.24 ├── iobroker.mihome-vacuum@3.11.0 ├── iobroker.mihome@1.4.0 ├── UNMET DEPENDENCY iobroker.objects-redis@file:node_modules/iobroker.objects-redis ├── iobroker.ping@1.6.2 ├── iobroker.radar@1.2.1 ├── iobroker.rpi2@1.3.2 ├── UNMET DEPENDENCY iobroker.samsung@0.5.8 ├── iobroker.scenes@2.3.9 ├── iobroker.simple-api@2.7.2 ├── iobroker.snmp@2.4.11 ├── iobroker.socketio@6.5.2 ├── iobroker.spotify-premium@1.2.2 ├── iobroker.telegram@1.16.0 ├── iobroker.terminal@1.0.0 ├── iobroker.text2command@3.0.2 ├── iobroker.tr-064-community@0.0.1-security ├── iobroker.tr-064@4.2.18 ├── iobroker.tuya@3.14.2 ├── UNMET DEPENDENCY iobroker.type-detector@file:node_modules/iobroker.type-detector ├── iobroker.vis-bars@0.1.4 ├── iobroker.vis-canvas-gauges@1.0.1 ├── iobroker.vis-colorpicker@2.0.3 ├── iobroker.vis-fancyswitch@1.1.0 ├── iobroker.vis-history@1.0.0 ├── iobroker.vis-hqwidgets@1.4.0 ├── iobroker.vis-jqui-mfd@1.0.12 ├── iobroker.vis-justgage@1.0.2 ├── iobroker.vis-metro@1.2.0 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-timeandweather@1.2.2 ├── iobroker.vis-weather@2.5.6 ├── iobroker.vis@1.4.16 ├── iobroker.web@6.1.0 ├── iobroker.ws.server@ invalid: "file:node_modules/iobroker.ws.server" from the root project ├── iobroker.ws@ invalid: "file:node_modules/iobroker.ws" from the root project ├── UNMET DEPENDENCY mocha@^9.0.0 ├── UNMET DEPENDENCY node-mihome@0.0.32 ├── UNMET DEPENDENCY pcap@^3.1.0 ├── UNMET DEPENDENCY semver@^5.5.0 ├── typescript@4.7.4 └── UNMET DEPENDENCY yargs@^7.0.2Da ist wohl einiges durcheinander. Gibts da eine Möglichkeit das wieder zu richten?
@masterg87 sagte in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
Gibts da eine Möglichkeit das wieder zu richten?
Wo fängt man an, wo hört man auf?
-
@masterg87 sagte in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
Gibts da eine Möglichkeit das wieder zu richten?
Wo fängt man an, wo hört man auf?
-
@thomas-braun neue VM und iobroker backup einspielen z.b.:wink:
Ich wollt's nicht sagen.
-
Ihr hattet Recht und danke für eure super schnelle Hilfe.
Nach Neuaufsetzen der VM und Neuinstalltion des Iobroker war der Fehler behoben. Musste dann noch das Backup wiederherstellen und ein paar Sachen manuell in den Skripten und Co nacharbeiten, die nicht mehr aktuell waren. Jetzt läuft es aber wie vorher. Hat aber schon einige Stunden gedauert. Hoffe jetzt habe ich ein paar Jahre wieder Ruhe ;-) -
Ihr hattet Recht und danke für eure super schnelle Hilfe.
Nach Neuaufsetzen der VM und Neuinstalltion des Iobroker war der Fehler behoben. Musste dann noch das Backup wiederherstellen und ein paar Sachen manuell in den Skripten und Co nacharbeiten, die nicht mehr aktuell waren. Jetzt läuft es aber wie vorher. Hat aber schon einige Stunden gedauert. Hoffe jetzt habe ich ein paar Jahre wieder Ruhe ;-)@masterg87 sagte in Admin Adapter Upgrade von 6.3 -> 6.8 schlägt fehl:
Hoffe jetzt habe ich ein paar Jahre wieder Ruhe
In den Jahren regelmäßig das System pflegen und nicht nach x-Jahren einen großen Satz versuchen. Geht meist in die Hose.
384
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge