Keine Updates nach Nodejs Update
-
@markusp sagte in Keine Updates nach Nodejs Update:
Jetzt habe ich aktuell von Node JS 14 auf 16 upgedatet
Jetzt erst ?
Aktuell ist 18 !!!
Wahrscheinlich auch mal wieder ein Fall von "ncars"
Komplette Ausgabe von
iob diagbitte zeigen
-
Betriebssystem: Mac OS High Sierra
Da funktioniert 'iob diag' nur ganz rudimentär. Das ist ja auf ein (Debian)-Linux ausgelegt.
-
... dann kommt das. Werden ja nur mögliche Commands angezeigt oder?
ioBrokerHost-2:iobroker ioBroker$ ./iob diag iobroker [command] Commands: iobroker setup Setup ioBroker iobroker start [all|<adapter>.<instance>] Starts the js-controller or a specified adapter instance iobroker stop [<adapter>.<instance>] stops the js-controller or a specified adapter instance iobroker restart [<adapter>.<instance>] Restarts js-controller or a specified adapter instance [aliases: r] iobroker debug <adapter>[.<instance>] Starts a Node.js debugging session for the adapter instance iobroker info Shows the host info iobroker logs [<adapter>] Monitor log iobroker add <adapter> [desiredNumber] Add instance of adapter [aliases: a] iobroker install <adapter> Installs a specified adapter [aliases: i] iobroker rebuild [<module>] Rebuild all native modules or path iobroker url <url> [<name>] Install adapter from specified url, e.g. GitHub iobroker del <adapter> Remove adapter and all instances from this host [aliases: delete] iobroker del <adapter>.<instance> Remove adapter instance [aliases: delete] iobroker update [<repositoryUrl>] Update repository and list adapters iobroker upgrade Upgrade management iobroker upload [all|<adapter>] Upload management [aliases: u] iobroker object Object management [aliases: o] iobroker state State management [aliases: s] iobroker message <adapter>[.instance] <command> [<message>] Send message to adapter instance/s iobroker list <type> [<filter>] List all entries, like objects iobroker chmod <mode> <file> Change file rights iobroker chown <user> <group> <file> Change file ownership iobroker touch <file> Touch file iobroker rm <file> Remove file iobroker file File management iobroker user User commands iobroker group group management iobroker host <hostname> Set host to given hostname iobroker set <adapter>.<instance> Change settings of adapter config iobroker license <license.file or license.text> Update license by given file iobroker cert Certificate management iobroker clean <yes> Clears all objects and states iobroker backup Create backup iobroker restore <backup name or path> Restore a specified backup iobroker validate <backup name or path> Validate a specified backup iobroker status [all|<adapter>.<instance>] Status of ioBroker or adapter instance [aliases: isrun] iobroker repo [<name>] Show repo information iobroker uuid Show uuid of the installation [aliases: id] iobroker unsetup Reset license, installation secret and language iobroker fix Execute the installation fixer script, this updates your ioBroker installation iobroker multihost Multihost management iobroker compact compact group management iobroker plugin Plugin management iobroker version [<adapter>] Show version of js-controller or specified adapter [aliases: v] Options: --help Show help [boolean] -
Ja, habe länger nichts mehr an Upadtes gemacht. Gehe erstmal auf 16, da 18 auf os HighSierra nicht läuft und höher als High Sierra kann ich mit dem alten Mac leider nicht gehen.
-
Habe hier mal versucht den Alexa-Adapter upzudaten:
Would you like to upgrade alexa2 from @3.24.1 to @3.25.2 now? [(y)es, (n)o]: y Update alexa2 from @3.24.1 to @3.25.2 NPM version: 8.19.4 Installing iobroker.alexa2@3.25.2... (System call) npm WARN tar zlib: incorrect data check npm WARN tarball cached data for node-red-node-email@https://registry.npmjs.org/node-red-node-email/-/node-red-node-email-1.18.4.tgz (sha512-Qu5r/g+g91UBmVBz8aSyof9v79PTvUNqa7KDgoPPJSb6ZwZtswV7orQil2Oio9ZChaejp3GG63LoLyqaPeU53Q==) seems to be corrupted. Refreshing cache. npm WARN tarball tarball data for node-red-node-email@https://registry.npmjs.org/node-red-node-email/-/node-red-node-email-1.18.4.tgz (sha512-Qu5r/g+g91UBmVBz8aSyof9v79PTvUNqa7KDgoPPJSb6ZwZtswV7orQil2Oio9ZChaejp3GG63LoLyqaPeU53Q==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.scenes@https://registry.npmjs.org/iobroker.scenes/-/iobroker.scenes-2.3.9.tgz (sha512-81ONrG/7FK31NxZmojaDcdwKpkaLutHKMpcvODydcWVoJEJosIatoP4nBaTAqqC76BB55J9g1v94RhU5YYwhbg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.icons-mfd-png@https://registry.npmjs.org/iobroker.icons-mfd-png/-/iobroker.icons-mfd-png-1.1.0.tgz (sha512-TSp3FT7T5dAvfwKFRnzi0si6SHoxI1b3DfT0qmsL1FYQ8DXFpdNnhVm/M/vfyo4/7MogkwKGRbEq9qvnK9vRZA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.cloud@https://registry.npmjs.org/iobroker.cloud/-/iobroker.cloud-4.3.0.tgz (sha512-GZqj38EmaqwhYoi0dNn2a/eCv78Aeueh6PPbd5HeGqXiyI5MJ5q7Wh8zOoDfhZvycJzdVlfLWeaWJ+dmLfuQ1w==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for bson@https://registry.npmjs.org/bson/-/bson-4.7.2.tgz (sha512-Ry9wCtIZ5kGqkJoi6aD8KjxFZEx78guTQDnpXWiNthsxzrxAK/i8E6pCHAIZTbaEFWcOCvbecMukfK7XUvyLpQ==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for moment-timezone@https://registry.npmjs.org/moment-timezone/-/moment-timezone-0.5.34.tgz (sha512-3zAEHh2hKUs3EXLESx/wsgw6IQdusOT8Bxm3D9UrHPQR7zlMmzwybC8zHEM1tQ4LJwP7fcxrWr8tuBg05fFCbg==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Refreshing cache. npm WARN tar zlib: incorrect data check npm WARN tarball cached data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Refreshing cache. 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 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 json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. 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 tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN deprecated multer@1.4.4: 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 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 tarball tarball data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.scenes@https://registry.npmjs.org/iobroker.scenes/-/iobroker.scenes-2.3.9.tgz (sha512-81ONrG/7FK31NxZmojaDcdwKpkaLutHKMpcvODydcWVoJEJosIatoP4nBaTAqqC76BB55J9g1v94RhU5YYwhbg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.icons-mfd-png@https://registry.npmjs.org/iobroker.icons-mfd-png/-/iobroker.icons-mfd-png-1.1.0.tgz (sha512-TSp3FT7T5dAvfwKFRnzi0si6SHoxI1b3DfT0qmsL1FYQ8DXFpdNnhVm/M/vfyo4/7MogkwKGRbEq9qvnK9vRZA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.cloud@https://registry.npmjs.org/iobroker.cloud/-/iobroker.cloud-4.3.0.tgz (sha512-GZqj38EmaqwhYoi0dNn2a/eCv78Aeueh6PPbd5HeGqXiyI5MJ5q7Wh8zOoDfhZvycJzdVlfLWeaWJ+dmLfuQ1w==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Trying again. npm WARN tarball tarball data for bson@https://registry.npmjs.org/bson/-/bson-4.7.2.tgz (sha512-Ry9wCtIZ5kGqkJoi6aD8KjxFZEx78guTQDnpXWiNthsxzrxAK/i8E6pCHAIZTbaEFWcOCvbecMukfK7XUvyLpQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for moment-timezone@https://registry.npmjs.org/moment-timezone/-/moment-timezone-0.5.34.tgz (sha512-3zAEHh2hKUs3EXLESx/wsgw6IQdusOT8Bxm3D9UrHPQR7zlMmzwybC8zHEM1tQ4LJwP7fcxrWr8tuBg05fFCbg==) seems to be corrupted. Trying again. npm WARN tarball tarball data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for rrule@https://registry.npmjs.org/rrule/-/rrule-2.6.4.tgz (sha512-sLdnh4lmjUqq8liFiOUXD5kWp/FcnbDLPwq5YAc/RrN6120XOPb86Ae5zxF7ttBVq8O3LxjjORMEit1baluahA==) 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 tar zlib: incorrect data check npm WARN tarball tarball data for @aws-crypto/sha256-js@https://registry.npmjs.org/@aws-crypto/sha256-js/-/sha256-js-3.0.0.tgz (sha512-PnNN7os0+yd1XvXAy23CFOmTbMaDxgxXtTKHybrJ39Y8kGzBATgBFibWJKH6BhytLI/Zyszs87xCOBNyBig6vQ==) seems to be corrupted. Trying again. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure npm WARN tar TAR_ENTRY_INVALID checksum failure 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 coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for sax@https://registry.npmjs.org/sax/-/sax-0.4.3.tgz (sha512-WvnHpLKMuEsJFV3LXuvxKY4sLdKev2tIeUxn+ljlQAhpx4ZEmJOW+nEa0uERX7XvfxoimvXvEqeo94p2jXoL6g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.nanoleaf-lightpanels@https://registry.npmjs.org/iobroker.nanoleaf-lightpanels/-/iobroker.nanoleaf-lightpanels-1.3.1.tgz (sha512-ebRlnutlmQE/U0KhBJwPHJxRIZGb3gRmdlLPh9V6HZI+l5Szz5ERgxaRrpimyAiqMWiPjOLimrxPX/v7p4Q2pw==) seems to be corrupted. Trying again. npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size npm WARN tarball tarball data for sax@https://registry.npmjs.org/sax/-/sax-0.4.3.tgz (sha512-WvnHpLKMuEsJFV3LXuvxKY4sLdKev2tIeUxn+ljlQAhpx4ZEmJOW+nEa0uERX7XvfxoimvXvEqeo94p2jXoL6g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.device-reminder@https://registry.npmjs.org/iobroker.device-reminder/-/iobroker.device-reminder-1.2.9.tgz (sha512-WeDmGm9R1DGw8E1g04MYVCmHahTVN/q1LUC4aFtFnznHB/CK6es5sX4jG1ydEKARtmWd+Z2mmhxCWe1xy+gh+g==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.nanoleaf-lightpanels@https://registry.npmjs.org/iobroker.nanoleaf-lightpanels/-/iobroker.nanoleaf-lightpanels-1.3.1.tgz (sha512-ebRlnutlmQE/U0KhBJwPHJxRIZGb3gRmdlLPh9V6HZI+l5Szz5ERgxaRrpimyAiqMWiPjOLimrxPX/v7p4Q2pw==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.paw@https://registry.npmjs.org/iobroker.paw/-/iobroker.paw-0.3.2.tgz (sha512-clqAMP/An8cXXQsJbFRQ+bCqhSX/I+4bF7i1phWX87iUCO8rfWDBvLF9u4HyRsUqwM51GOe77QlNzvIT6ArTIQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for @sentry/utils@https://registry.npmjs.org/@sentry/utils/-/utils-6.19.7.tgz (sha512-z95ECmE3i9pbWoXQrD/7PgkBAzJYR+iXtPuTkpBjDKs86O3mT+PXOT3BAn79w2wkn7/i3vOGD2xVr1uiMl26dA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.flot@https://registry.npmjs.org/iobroker.flot/-/iobroker.flot-1.11.0.tgz (sha512-8g2LG9M3TMCdo8KpjPriYhsuhC9x2oYVrcK4NnGQMtoG+IosJQN+tnHkOOJluWOYqVaoqu1Udc+6Gvxnx1gkjg==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.paw@https://registry.npmjs.org/iobroker.paw/-/iobroker.paw-0.3.2.tgz (sha512-clqAMP/An8cXXQsJbFRQ+bCqhSX/I+4bF7i1phWX87iUCO8rfWDBvLF9u4HyRsUqwM51GOe77QlNzvIT6ArTIQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for @zxing/text-encoding@https://registry.npmjs.org/@zxing/text-encoding/-/text-encoding-0.9.0.tgz (sha512-U/4aVJ2mxI0aDNI8Uq0wEhMgY+u4CNtEb0om3+y3+niDAsoTCOB33UF0sxpzqzdqXLqmvc+vZyAt4O8pPdfkwA==) seems to be corrupted. Trying again. npm WARN tarball tarball data for @zxing/text-encoding@https://registry.npmjs.org/@zxing/text-encoding/-/text-encoding-0.9.0.tgz (sha512-U/4aVJ2mxI0aDNI8Uq0wEhMgY+u4CNtEb0om3+y3+niDAsoTCOB33UF0sxpzqzdqXLqmvc+vZyAt4O8pPdfkwA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.daswetter@https://registry.npmjs.org/iobroker.daswetter/-/iobroker.daswetter-3.1.10.tgz (sha512-9ERjjR8FH7B2CQidvv1K0fN5cotD+lUhgODqDU7UdiymXhQ1TJRCSmrXaawbmIgFaAoWOc5k1Qu8fTwhgJKQJQ==) seems to be corrupted. Trying again. npm WARN tarball tarball data for iobroker.daswetter@https://registry.npmjs.org/iobroker.daswetter/-/iobroker.daswetter-3.1.10.tgz (sha512-9ERjjR8FH7B2CQidvv1K0fN5cotD+lUhgODqDU7UdiymXhQ1TJRCSmrXaawbmIgFaAoWOc5k1Qu8fTwhgJKQJQ==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.iot@https://registry.npmjs.org/iobroker.iot/-/iobroker.iot-1.14.2.tgz (sha512-dtkyMR0x+MSw1UUMVhlwjjMXjNIa39Q5wjiSxcZlspgrQSlDxo4mjLk4xYLLNpK7AtV4kD0rF/k2gzLzfGpdJw==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.javascript@https://registry.npmjs.org/iobroker.javascript/-/iobroker.javascript-5.7.0.tgz (sha512-otJGEYWrPmGPci+pRJfK2k0ahwLoI9Rc/+5skuAPQ/8Mr00eZuwWpRZ/gMy1flBG76erKHLkeLq2tmnlpm/8aA==) seems to be corrupted. Trying again. npm WARN tar zlib: incorrect data check npm WARN tarball tarball data for iobroker.admin@https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.3.8.tgz (sha512-2Cs/p9fjRf8jyVwY7fU+ESqLfc+8MCvy5fkX7wk4UVLssHCtpujhpQcgwiepDwN/qLzbu3Mvpc2qhAlmLXZ2pw==) seems to be corrupted. Trying again. npm ERR! code ENOENT npm ERR! syscall stat npm ERR! path /Users/ioBroker/.npm/_cacache/content-v2/sha512/5a/f9/c7a4b28cb84b09155dcb5eebf1298e2c2dd29ebf6b48794c67fa58e5400869c78644989396fa711ad2e1115fb5ef7f1a229af5ef12a7a8f78a768d7a0bea npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, stat '/Users/ioBroker/.npm/_cacache/content-v2/sha512/5a/f9/c7a4b28cb84b09155dcb5eebf1298e2c2dd29ebf6b48794c67fa58e5400869c78644989396fa711ad2e1115fb5ef7f1a229af5ef12a7a8f78a768d7a0bea' 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: npm ERR! /Users/ioBroker/.npm/_logs/2023-10-20T11_44_10_607Z-debug-0.log host.ioBrokerHost-2.fritz.box Cannot install iobroker.alexa2@3.25.2: 254 ioBrokerHost-2:iobroker ioBroker$open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
Installier nodejs@18 und lösche den npm Cache.
-
Habe nun 18 installiert. Jetzt startet der ioBroker nicht mehr:
ioBrokerHost-2:iobroker ioBroker$ ./iobroker start dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin Referenced from: /usr/local/bin/node (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib dyld: Symbol not found: ____chkstk_darwin Referenced from: /usr/local/bin/node (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib ./iobroker: line 1: 435 Abort trap: 6 node node_modules/iobroker.js-controller/iobroker.js $1 $2 $3 $4 $5Scheint erst mit Mac OS X 10.15 zu laufen. Habe aber 10.13. Höher geht mit dem Mac nicht.
-
Ach du warst das mit dem MacOS.
Hatte ich übersehen. Sorry.
Keine Ahnung von Fallobst.Ich würde auf die Kiste wohl ein aktuelles Linux knallen, wenn das geht.
-
ich habe jetzt mal über das Wochenende den ioBroker auf einen aktuelleren Mac mini mit OSX 10.15 gezogen und Node 18 installiert. Leider kann ich aber noch immer keine Adapter aktualisieren. Diesmal wird der Prozess mit Code 1 beendet:
$ iobroker upgrade admin@6.10.1 node:internal/bootstrap/switches/does_own_process_state:126 cachedCwd = rawMethods.cwd(); ^Error: ENOENT: no such file or directory, uv_cwd at process.wrappedCwd (node:internal/bootstrap/switches/does_own_process_state:126:28) at process.cwd (/Users/ioBroker/Documents/iobroker/node_modules/graceful-fs/polyfills.js:10:19) at ue.Yargs (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/build/index.cjs:1:61943) at Argv (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/index.cjs:12:16) at Object.<anonymous> (/Users/ioBroker/Documents/iobroker/node_modules/iobroker.js-controller/node_modules/yargs/index.cjs:7:1) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Module._load (node:internal/modules/cjs/loader:960:12) at Module .require (node:internal/modules/cjs/loader:1143:19) { errno: -2, code: 'ENOENT', syscall: 'uv_cwd'}Node.js v18.18.2 ERROR: Process exited with code 1 -
@markusp sagte in Keine Updates nach Nodejs Update:
Zu macOS kann ich nix sagen, die Pfade sehen aber schräg aus.
