ERROR: Process exited with code 1 / keine Updates möglich

Belei

Moin,

Meinst System läuft in einer VM auf Proxmox. Leider hab ich einige Zeit updates versäumt und somit ziemlich stau gehabt, auch in den Abhängigkeiten.

-Erst hab ich meine Stretch auf Buster upgedatet
-Dann hab ich node upgedatet und den fix script durchlaufen lassen
-jetzt bekomme ich bei allen adapter updates den fehler code 1 in der gui

root@ioBrokerNuc:~# node -v
v16.20.2
root@ioBrokerNuc:~# npm -v
8.19.4

Bsp.

root@ioBrokerNuc:~# iobroker upgrade backitup --debug

Would you like to upgrade backitup from @2.6.19 to @2.9.8 now? [(y)es, (n)o]: y
Update backitup from @2.6.19 to @2.9.8
NPM version: 8.19.4
Installing iobroker.backitup@2.9.8... (System call)
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/abab
npm ERR! dest /opt/iobroker/node_modules/.abab-bvmibCm3
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abab' -> '/opt/iobroker/node_modules/.abab-bvmibCm3'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2024-01-06T19_42_16_764Z-debug-0.log
host.ioBrokerNuc Cannot install iobroker.backitup@2.9.8: 217

Dann hab ich das angemeckerte VS umbenannt

root@ioBrokerNuc:~# mv /opt/iobroker/node_modules/abab /opt/iobroker/node_modules/.abab-bvmibCm3

Dann macht er das

Would you like to upgrade backitup from @2.6.19 to @2.9.8 now? [(y)es, (n)o]: y                                                                     Update backitup from @2.6.19 to @2.9.8
NPM version: 8.19.4
Installing iobroker.backitup@2.9.8... (System call)
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/abbrev
npm ERR! dest /opt/iobroker/node_modules/.abbrev-5eNud0FY
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abbrev' -> '/opt/iobroker/node_modules/.abbrev-5eNud0FY'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2024-01-06T19_49_54_685Z-debug-0.log
host.ioBrokerNuc Cannot install iobroker.backitup@2.9.8: 217

Momentan weiss ich nicht weiter.... kann jmd helfen?

Hier noch mal paar Infos:

root@ioBrokerNuc:~# iob list adapters
system.adapter.admin                   : admin          - v6.12.0
system.adapter.alexa2                  : alexa2         - v3.26.3
system.adapter.amazon-dash             : amazon-dash    - v1.2.0
system.adapter.backitup                : backitup       - v2.6.19
system.adapter.ble                     : ble            - v0.13.0
system.adapter.cloud                   : cloud          - v4.4.1
system.adapter.discovery               : discovery      - v3.1.0
system.adapter.fb-checkpresence        : fb-checkpresence - v1.1.25
system.adapter.feiertage               : feiertage      - v1.1.0
system.adapter.flot                    : flot           - v1.11.0
system.adapter.fritzdect               : fritzdect      - v2.2.6
system.adapter.history                 : history        - v2.2.4
system.adapter.hm-rega                 : hm-rega        - v1.7.1
system.adapter.hm-rpc                  : hm-rpc         - v1.15.16
system.adapter.hue                     : hue            - v3.7.1
system.adapter.hue-extended            : hue-extended   - v2.0.0
system.adapter.icons-ultimate-png      : icons-ultimate-png - v1.0.1
system.adapter.info                    : info           - v1.9.19
system.adapter.iot                     : iot            - v2.0.11
system.adapter.iqontrol                : iqontrol       - v2.1.0
system.adapter.javascript              : javascript     - v6.1.4
system.adapter.lovelace                : lovelace       - v3.0.1
system.adapter.mihome-vacuum           : mihome-vacuum  - v3.11.0
system.adapter.mobile                  : mobile         - v1.0.1
system.adapter.ping                    : ping           - v1.5.3
system.adapter.proxmox                 : proxmox        - v1.3.4
system.adapter.pushover                : pushover       - v3.0.3
system.adapter.radar                   : radar          - v1.1.3
system.adapter.radar2                  : radar2         - v2.0.3
system.adapter.rflink                  : rflink         - v2.1.6
system.adapter.scenes                  : scenes         - v2.3.9
system.adapter.shelly                  : shelly         - v6.4.1
system.adapter.shuttercontrol          : shuttercontrol - v1.4.18
system.adapter.simple-api              : simple-api     - v2.7.2
system.adapter.socketio                : socketio       - v4.2.0
system.adapter.tr-064                  : tr-064         - v4.2.17
system.adapter.vis                     : vis            - v1.4.15
system.adapter.vis-timeandweather      : vis-timeandweather - v1.2.2
system.adapter.weatherunderground      : weatherunderground - v3.4.2
system.adapter.web                     : web            - v4.3.0
system.adapter.web-speedy              : web-speedy     - v0.2.0
system.adapter.weishaupt-wem           : weishaupt-wem  - v0.0.15
system.adapter.zigbee                  : zigbee         - v1.8.10

Thomas Braun

@belei Immer noch alles zu alt...
Backitup benötigt mittlerweile nodejs@18.
Und ein Sprung auf Buster geht ins Leere, ist auch abgekündigt.

Versuch per

iob stop 
iob fix
iob start
iob nodejs-update
iob stop
iob update
iob upgrade all
iob upgrade self
iob start

Zumindest den ioBroker in die Gegenwart zu katapultieren. Davon dann ein Backup und dann würde ich da ein neues aktuelles Debian installieren und dort das Backup einspielen.

Thomas Braun

@belei

Und das Ganzen natürlich OHNE root shell!!!!!11111

Glasfaser

@belei sagte in ERROR: Process exited with code 1 / keine Updates möglich:

Meinst System läuft in einer VM auf Proxmox.

dann aber nicht als

root@ioBrokerNuc:

sondern als User

dann :

Erst hab ich meine Stretch auf Buster upgedatet

warum "sehr alt" auf alt ...

Dann hab ich node upgedatet

da ist 16 ... ist auch alt , aktuell ist 18

Belei

@thomas-braun

Ich wollte bevor ich weiter update erstmal das es wieder stabil läuft...
Aber gut ^^

Bin jetzt mittendrin

Hat alles soweit geklappt, ich muste zwar den iobroker anders stoppen und auch der fix ging nur mit einem anderen Befehl aber die sind durch. Erst ist jetzt bei upgrade all, hat jetzt z.b. für den zigbee adapter 5 minuten gebraucht aber lief durch danach fragt er dann ob ich den nächsten aktualisieren will etc.

gestoppt mit

sudo systemctl stop iobroker

Fix mit

curl -sL https://iobroker.net/fix.sh | bash -

Would you like to upgrade zigbee from @1.8.10 to @1.9.5 now? [(y)es, (n)o]: y
Update zigbee from @1.8.10 to @1.9.5
host.ioBrokerNuc Adapter "system.adapter.zigbee.0" is stopped.
NPM version: 10.2.3
Installing iobroker.zigbee@1.9.5... (System call)

added 39 packages, removed 1 package, and changed 1346 packages in 6m

127 packages are looking for funding
  run `npm fund` for details
Update "system.adapter.zigbee.0"
upload [323] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/adapter-settings.js adapter-settings.js application/javascript
upload [300] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/DGNWG05LM.png img/DGNWG05LM.png image/png
upload [250] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/bitron_motion.png img/bitron_motion.png image/png
upload [200] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/hive.png img/hive.png image/png
upload [150] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/lh_32Zb.png img/lh_32Zb.png image/png
upload [100] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_amaze.png img/philips_amaze.png image/png
upload [90] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_ambiance.png img/philips_hue_ambiance.png image/png
upload [80] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_e27_ambiance.png img/philips_hue_e27_ambiance.png image/png
upload [70] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_ltc021.png img/philips_hue_ltc021.png image/png
upload [60] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/plug.png img/plug.png image/png
upload [50] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/sensor_philipshue.png img/sensor_philipshue.png image/png
upload [40] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/smartthings_motion.png img/smartthings_motion.png image/png
upload [30] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ts0203.png img/ts0203.png image/png
upload [20] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/tuya_tyzs1l.png img/tuya_tyzs1l.png image/png
upload [19] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unavailable.png img/unavailable.png image/png
upload [18] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unknown.png img/unknown.png image/png
upload [17] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/wemo.png img/wemo.png image/png
upload [16] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_plug_eu.png img/xiaomi_plug_eu.png image/png
upload [15] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_wireless_switch.png img/xiaomi_wireless_switch.png image/png
upload [14] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27.png img/zbt_e27.png image/png
upload [13] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27_rgbw.png img/zbt_e27_rgbw.png image/png
upload [12] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_led_panel.png img/zbt_led_panel.png image/png
upload [11] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_smart_switch.png img/zbt_smart_switch.png image/png
upload [10] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zemismart_sw2.png img/zemismart_sw2.png image/png
upload [9] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index.html index.html text/html
upload [8] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index_m.html index_m.html text/html
upload [7] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/moment.min.js moment.min.js application/javascript
upload [6] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/shuffle.min.js shuffle.min.js application/javascript
upload [5] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/tab_m.html tab_m.html text/html
upload [4] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.css vis-network.min.css text/css
upload [3] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.js vis-network.min.js application/javascript
upload [2] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/words.js words.js application/javascript
upload [1] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.png zigbee.png image/png
upload [0] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.svg zigbee.svg image/svg+xml
host.ioBrokerNuc Adapter "system.adapter.zigbee.0" is started

This upgrade of "ws" will at least introduce the following changes:
==========================================================================
-> 2.5.8:
Corrected adapter termination if the alias has no target

-> 2.5.7:
upgraded socket-classes to fix vis problems

-> 2.5.6:
upgraded socket-classes to correct the error by unsubscribing on client disconnect

-> 2.5.5:
upgraded socket-classes to fix crash cases

-> 2.5.4:
added missing node16 requirement

-> 2.5.3:
Added the subscribing on the specific instance messages

-> 2.4.0:
(bluefox) extended the getObjects function with the possibility to read the list of IDs
==========================================================================

BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES!
Would you like to upgrade ws from @1.3.0 to @2.5.8 now? [(y)es, (n)o]:

Thomas Braun

@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...

Belei

@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

Thomas Braun

@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

Belei

@thomas-braun

Zeile 5
host.ioBrokerNuc Cannot install iobroker.tr-064@4.2.18: 244

Zeile 37

Belei

@thomas-braun

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

Thomas Braun


iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug

Homoran · `iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug`

@thomas-braun :grin:

Belei · `iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug`

@thomas-braun

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

Homoran

@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.

Thomas Braun

@belei

Schmeiß ein

iob fix

ein.

Belei

@thomas-braun

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?

Homoran

@belei dann versuch noch ein update
ggf. solltest du vorher nodejs auf die aktuell empfohlene Verdion 18.xxx bringen

Thomas Braun

@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... ;-)

Thomas Braun

@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.

Belei

@thomas-braun

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

Community Forum

NEWS

ERROR: Process exited with code 1 / keine Updates möglich

Support us

787

32.5k

81.7k

1.3m