ERROR: Process exited with code 1 / keine Updates möglich
-
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
Ich wollte bevor ich weiter update erstmal das es wieder stabil läuft...
Um es stabil laufen zu haben musst du updaten...
-
@thomas-braun
Bin dabei.Nach 4-5 Adaptern kommen jetzt wieder Fehler:
Would you like to upgrade tr-064 from @4.2.17 to @4.2.18 now? [(y)es, (n)o]: y Update tr-064 from @4.2.17 to @4.2.18 NPM version: 10.2.3 Installing iobroker.tr-064@4.2.18... (System call) host.ioBrokerNuc Cannot install iobroker.tr-064@4.2.18: 244 root@ioBrokerNuc:~# iob upgrade all This upgrade of "socketio" will at least introduce the following changes: ========================================================================== -> 6.6.0: Corrected adapter termination if the alias has no target -> 6.5.7: upgrade socket-classes to fix error with vis subscriptions -> 6.5.6: upgraded socket-classes to correct the error by unsubscribing on client disconnect -> 6.5.5: upgrade socket-classes to fix crash cases -> 6.5.4: upgrade socket-classes to fix crash cases -> 6.5.3: added missing node16 requirement -> 6.5.2: Added the subscribing on the specific instance messages ========================================================================== BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES! Would you like to upgrade socketio from @4.2.0 to @6.6.0 now? [(y)es, (n)o]: y Update socketio from @4.2.0 to @6.6.0 NPM version: 10.2.3 Installing iobroker.socketio@6.6.0... (System call) host.ioBrokerNuc Cannot install iobroker.socketio@6.6.0: 217 -
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
kommen jetzt wieder Fehler:
Wo siehst du da Fehler?
Edit:
iobroker upgrade tr-064@4.2.18 --debug -
-
root@ioBrokerNuc:~# iobroker upgrade tr-064@4.2.18 --debug Would you like to reinstall version 4.2.18 of tr-064 now? [(y)es, (n)o]: y Update tr-064 from @4.2.18 to @4.2.18 NPM version: 10.2.3 Installing iobroker.tr-064@4.2.18... (System call) npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/JSV npm ERR! dest /opt/iobroker/node_modules/.JSV-Lv4q8JLo npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/JSV' -> '/opt/iobroker/node_modules/.JSV-Lv4q8JLo' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-06T21_16_06_713Z-debug-0.log host.ioBrokerNuc Cannot install iobroker.tr-064@4.2.18: 217 -
iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug -
-
root@ioBrokerNuc:~# iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug Would you like to reinstall version 4.2.18 of tr-064 now? [(y)es, (n)o]: y Update tr-064 from @4.2.18 to @4.2.18 NPM version: 10.2.3 Installing iobroker.tr-064@4.2.18... (System call) npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/JSV npm ERR! dest /opt/iobroker/node_modules/.JSV-Lv4q8JLo npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/JSV' -> '/opt/iobroker/node_modules/.JSV-Lv4q8JLo' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-06T21_20_55_945Z-debug-0.log host.ioBrokerNuc Cannot install iobroker.tr-064@4.2.18: 217 -
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
NPM version: 8.19.4
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
npm ERR! code ENOTEMPTY
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
host.ioBrokerNuc Cannot install iobroker.backitup@2.9.8: 217
alles vorhanden!
die Lösung sollte in dem Thread stehen.
-
-
Hat er gemacht.
iob fix library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://security.debian.org/debian-security buster/updates InRelease OK:2 http://ftp.de.debian.org/debian buster InRelease OK:3 http://ftp.de.debian.org/debian buster-updates InRelease OK:4 https://deb.nodesource.com/node_18.x nodistro InRelease Paketlisten werden gelesen... Fertig ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! No relevant JSONL files found to compress, skip ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Was nun?
iobroker starten oder upgrade? -
@belei dann versuch noch ein update
ggf. solltest du vorher nodejs auf die aktuell empfohlene Verdion 18.xxx bringen -
@homoran sagte in ERROR: Process exited with code 1 / keine Updates möglich:
ggf. solltest du vorher nodejs auf die aktuell empfohlene Verdion 18.xxx bringen
Schon passiert...
-
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
iobroker starten oder upgrade?
Weiter updates reinschaufeln. Bis da nix mehr gemeldet wird.
-
Jetzt wird er geschwätzich, hat er es jetzt re-installiert?
root@ioBrokerNuc:~# iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug Would you like to reinstall version 4.2.18 of tr-064 now? [(y)es, (n)o]: y Update tr-064 from @4.2.18 to @4.2.18 NPM version: 10.2.3 Installing iobroker.tr-064@4.2.18... (System call) npm WARN skipping integrity check for git dependency ssh://git@github.com/noopka t/browser-serialport.git npm WARN deprecated dgram@1.0.1: npm is holding this package for security reason s. 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 crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the o ne that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provide s its own type definitions, so you do not need this installed. 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 b ecause it extends the now deprecated request package, see https://github.com/req uest/request/issues/3142 npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() met hods instead npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JS ON 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 domexception@4.0.0: Use your platform's native DOMException 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 deprecated jscs-preset-wikimedia@1.0.1: No longer maintained. We recomm ent migrating to ESLint with eslint-config-wikimedia. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@n pmjs.com for more info. npm WARN deprecated uuid@2.0.3: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated jscs@3.0.7: JSCS has merged with ESLint! See - https://mediu m.com/@markelog/jscs-end-of-the-line-bc9bf0b3fdb2 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 10 0x even if nothing is polyfilled. Some versions have web compatibility issues. P lease, upgrade your dependencies to the actual version of core-js. changed 1382 packages in 7m 127 packages are looking for funding run `npm fund` for details Update "system.adapter.tr-064.0" upload [2] tr-064.admin /opt/iobroker/node_modules/iobroker.tr-064/admin/index_m.html index_m.html text/html upload [1] tr-064.admin /opt/iobroker/node_modules/iobroker.tr-064/admin/tr-064.png tr-064.png image/png upload [0] tr-064.admin /opt/iobroker/node_modules/iobroker.tr-064/admin/words.js words.js application/javascript -
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
Jetzt wird er geschwätzich,
Ist nur Werbung
-
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
hat er es jetzt re-installiert?
Ja.
Am Rande: Zieh das Fenster von deinem puTTY breiter. Das schwindelige Ding fabriziert da komische Zeilenumbrüche.
-
@glasfaser
npm fund ?? Spendenanfrage oder was? -
@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:
Spendenanfrage oder was?
Ja.
-
