Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. ERROR: Process exited with code 1 / keine Updates möglich

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    11
    1
    524

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.7k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.6k

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

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
41 Beiträge 4 Kommentatoren 3.6k Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • Thomas BraunT Thomas Braun
    
    iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug
    
    HomoranH Nicht stören
    HomoranH Nicht stören
    Homoran
    Global Moderator Administrators
    schrieb am zuletzt editiert von Homoran
    #12

    @thomas-braun Screenshot_20240106-222238_Firefox.jpg :grin:

    kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

    1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun
      
      iobroker upgrade tr-064@4.2.18 --host ioBrokerNuc --debug
      
      B Offline
      B Offline
      Belei
      schrieb am zuletzt editiert von
      #13

      @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
      
      
      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • B 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
        
        HomoranH Nicht stören
        HomoranH Nicht stören
        Homoran
        Global Moderator Administrators
        schrieb am zuletzt editiert von Homoran
        #14

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

        Screenshot_20240106-222238_Firefox.jpg

        die Lösung sollte in dem Thread stehen.

        kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

        Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

        1 Antwort Letzte Antwort
        1
        • B Belei

          @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
          
          
          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #15

          @belei

          Schmeiß ein

          iob fix
          

          ein.

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          B 1 Antwort Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @belei

            Schmeiß ein

            iob fix
            

            ein.

            B Offline
            B Offline
            Belei
            schrieb am zuletzt editiert von Belei
            #16

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

            HomoranH Thomas BraunT 2 Antworten Letzte Antwort
            0
            • B 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?

              HomoranH Nicht stören
              HomoranH Nicht stören
              Homoran
              Global Moderator Administrators
              schrieb am zuletzt editiert von Homoran
              #17

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

              kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • HomoranH Homoran

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

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #18

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

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                1 Antwort Letzte Antwort
                0
                • B 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?

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #19

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

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  B 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT 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.

                    B Offline
                    B Offline
                    Belei
                    schrieb am zuletzt editiert von Belei
                    #20

                    @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
                    
                    
                    GlasfaserG Thomas BraunT 2 Antworten Letzte Antwort
                    0
                    • B 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
                      
                      
                      GlasfaserG Offline
                      GlasfaserG Offline
                      Glasfaser
                      schrieb am zuletzt editiert von
                      #21

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

                      Jetzt wird er geschwätzich,

                      Ist nur Werbung :)

                      Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                      B 1 Antwort Letzte Antwort
                      0
                      • B 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
                        
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #22

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

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        1 Antwort Letzte Antwort
                        0
                        • GlasfaserG Glasfaser

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

                          Jetzt wird er geschwätzich,

                          Ist nur Werbung :)

                          B Offline
                          B Offline
                          Belei
                          schrieb am zuletzt editiert von
                          #23

                          @glasfaser
                          npm fund ?? Spendenanfrage oder was? :-)

                          Thomas BraunT 2 Antworten Letzte Antwort
                          0
                          • B Belei

                            @glasfaser
                            npm fund ?? Spendenanfrage oder was? :-)

                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #24

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

                            Spendenanfrage oder was?

                            Ja.

                            Linux-Werkzeugkasten:
                            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                            NodeJS Fixer Skript:
                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                            1 Antwort Letzte Antwort
                            0
                            • B Belei

                              @glasfaser
                              npm fund ?? Spendenanfrage oder was? :-)

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #25

                              @belei

                              Wie schaut es bei

                              iob update
                              

                              aus?

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              B 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @belei

                                Wie schaut es bei

                                iob update
                                

                                aus?

                                B Offline
                                B Offline
                                Belei
                                schrieb am zuletzt editiert von
                                #26

                                @thomas-braun

                                Sind noch paar... Aber es geht voran. Wundert mich nur das jeder einzel abgefragt wird und es pro Adapter im mindestens 5 minuten braucht.

                                
                                Used repository: stable
                                Adapter    "admin"        : 6.12.0   , installed 6.12.0
                                Adapter    "alexa2"       : 3.26.3   , installed 3.26.3
                                Adapter    "amazon-dash"  : 1.2.0    , installed 1.2.0
                                Adapter    "backitup"     : 2.9.8    , installed 2.6.19 [Updatable]
                                Adapter    "ble"          : 0.13.4   , installed 0.13.0 [Updatable]
                                Adapter    "cloud"        : 4.4.1    , installed 4.4.1
                                Adapter    "discovery"    : 4.2.0    , installed 3.1.0  [Updatable]
                                Adapter    "fb-checkpresence": 1.2.2 , installed 1.1.25 [Updatable]
                                Adapter    "feiertage"    : 1.1.4    , installed 1.1.4
                                Adapter    "flot"         : 1.12.0   , installed 1.11.0 [Updatable]
                                Adapter    "fritzdect"    : 2.5.9    , installed 2.2.6  [Updatable]
                                Adapter    "history"      : 3.0.1    , installed 2.2.4  [Updatable]
                                Adapter    "hm-rega"      : 4.0.0    , installed 3.0.46 [Updatable]
                                Adapter    "hm-rpc"       : 1.15.19  , installed 1.15.16 [Updatable]
                                Adapter    "hue"          : 3.10.1   , installed 3.7.1  [Updatable]
                                Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
                                Adapter    "info"         : 2.0.0    , installed 1.9.26 [Updatable]
                                Adapter    "iot"          : 2.0.11   , installed 2.0.11
                                Adapter    "iqontrol"     : 2.3.0    , installed 2.1.0  [Updatable]
                                Adapter    "javascript"   : 7.1.6    , installed 6.1.4  [Updatable]
                                Controller "js-controller": 5.0.17   , installed 4.0.24 [Updatable]
                                Adapter    "lovelace"     : 3.0.1    , installed 3.0.1
                                Adapter    "mihome-vacuum": 4.1.0    , installed 3.11.0 [Updatable]
                                Adapter    "mobile"       : 1.0.1    , installed 1.0.1
                                Adapter    "ping"         : 1.6.2    , installed 1.6.2
                                Adapter    "proxmox"      : 2.2.2    , installed 1.3.5  [Updatable]
                                Adapter    "pushover"     : 3.0.6    , installed 3.0.3  [Updatable]
                                Adapter    "radar2"       : 2.1.0    , installed 2.1.0
                                Adapter    "rflink"       : 2.1.6    , installed 2.1.6
                                Adapter    "scenes"       : 2.3.9    , installed 2.3.9
                                Adapter    "shelly"       : 6.6.1    , installed 6.6.1
                                Adapter    "shuttercontrol": 1.6.3   , installed 1.6.3
                                Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
                                Adapter    "socketio"     : 6.6.0    , installed 6.6.0
                                Adapter    "tr-064"       : 4.2.18   , installed 4.2.18
                                Adapter    "vis"          : 1.5.4    , installed 1.5.4
                                Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
                                Adapter    "weatherunderground": 3.6.0, installed 3.6.0
                                Adapter    "web"          : 6.1.10   , installed 6.1.10
                                Adapter    "weishaupt-wem": 0.0.15   , installed 0.0.15
                                Adapter    "ws"           : 2.5.8    , installed 2.5.8
                                Adapter    "zigbee"       : 1.9.5    , installed 1.9.5
                                
                                
                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • B Belei

                                  @thomas-braun

                                  Sind noch paar... Aber es geht voran. Wundert mich nur das jeder einzel abgefragt wird und es pro Adapter im mindestens 5 minuten braucht.

                                  
                                  Used repository: stable
                                  Adapter    "admin"        : 6.12.0   , installed 6.12.0
                                  Adapter    "alexa2"       : 3.26.3   , installed 3.26.3
                                  Adapter    "amazon-dash"  : 1.2.0    , installed 1.2.0
                                  Adapter    "backitup"     : 2.9.8    , installed 2.6.19 [Updatable]
                                  Adapter    "ble"          : 0.13.4   , installed 0.13.0 [Updatable]
                                  Adapter    "cloud"        : 4.4.1    , installed 4.4.1
                                  Adapter    "discovery"    : 4.2.0    , installed 3.1.0  [Updatable]
                                  Adapter    "fb-checkpresence": 1.2.2 , installed 1.1.25 [Updatable]
                                  Adapter    "feiertage"    : 1.1.4    , installed 1.1.4
                                  Adapter    "flot"         : 1.12.0   , installed 1.11.0 [Updatable]
                                  Adapter    "fritzdect"    : 2.5.9    , installed 2.2.6  [Updatable]
                                  Adapter    "history"      : 3.0.1    , installed 2.2.4  [Updatable]
                                  Adapter    "hm-rega"      : 4.0.0    , installed 3.0.46 [Updatable]
                                  Adapter    "hm-rpc"       : 1.15.19  , installed 1.15.16 [Updatable]
                                  Adapter    "hue"          : 3.10.1   , installed 3.7.1  [Updatable]
                                  Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
                                  Adapter    "info"         : 2.0.0    , installed 1.9.26 [Updatable]
                                  Adapter    "iot"          : 2.0.11   , installed 2.0.11
                                  Adapter    "iqontrol"     : 2.3.0    , installed 2.1.0  [Updatable]
                                  Adapter    "javascript"   : 7.1.6    , installed 6.1.4  [Updatable]
                                  Controller "js-controller": 5.0.17   , installed 4.0.24 [Updatable]
                                  Adapter    "lovelace"     : 3.0.1    , installed 3.0.1
                                  Adapter    "mihome-vacuum": 4.1.0    , installed 3.11.0 [Updatable]
                                  Adapter    "mobile"       : 1.0.1    , installed 1.0.1
                                  Adapter    "ping"         : 1.6.2    , installed 1.6.2
                                  Adapter    "proxmox"      : 2.2.2    , installed 1.3.5  [Updatable]
                                  Adapter    "pushover"     : 3.0.6    , installed 3.0.3  [Updatable]
                                  Adapter    "radar2"       : 2.1.0    , installed 2.1.0
                                  Adapter    "rflink"       : 2.1.6    , installed 2.1.6
                                  Adapter    "scenes"       : 2.3.9    , installed 2.3.9
                                  Adapter    "shelly"       : 6.6.1    , installed 6.6.1
                                  Adapter    "shuttercontrol": 1.6.3   , installed 1.6.3
                                  Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
                                  Adapter    "socketio"     : 6.6.0    , installed 6.6.0
                                  Adapter    "tr-064"       : 4.2.18   , installed 4.2.18
                                  Adapter    "vis"          : 1.5.4    , installed 1.5.4
                                  Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
                                  Adapter    "weatherunderground": 3.6.0, installed 3.6.0
                                  Adapter    "web"          : 6.1.10   , installed 6.1.10
                                  Adapter    "weishaupt-wem": 0.0.15   , installed 0.0.15
                                  Adapter    "ws"           : 2.5.8    , installed 2.5.8
                                  Adapter    "zigbee"       : 1.9.5    , installed 1.9.5
                                  
                                  
                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #27

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

                                  Wundert mich nur das jeder einzel abgefragt wird

                                  Mit

                                  iob upgrade all -y
                                  

                                  fragt die Kiste nicht mehr bei jedem Adapter.

                                  Linux-Werkzeugkasten:
                                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                  NodeJS Fixer Skript:
                                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                  B 1 Antwort Letzte Antwort
                                  1
                                  • Thomas BraunT Thomas Braun

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

                                    Wundert mich nur das jeder einzel abgefragt wird

                                    Mit

                                    iob upgrade all -y
                                    

                                    fragt die Kiste nicht mehr bei jedem Adapter.

                                    B Offline
                                    B Offline
                                    Belei
                                    schrieb am zuletzt editiert von
                                    #28

                                    @thomas-braun

                                    Erstmal vielen Dank für die super kompetente schnelle Hilfe hier von allen!! :+1: :clap:
                                    Die gute Nachricht ist, es ist alles durchgeupdatet und iob wieder gestartet.

                                    Die schlechte ist, es kam der einrichtungsassistent und nun sind nur 3 Instanzen aktiv statt über 20.
                                    Die korekten Adapter stehen aber noch unter Adapter. Es fehlt auch der Punkte Scripte im Menü.
                                    Habe Scripte mal als Instanz aktiviert, die Scripte sind auch wech.....

                                    Thomas BraunT 1 Antwort Letzte Antwort
                                    0
                                    • B Belei

                                      @thomas-braun

                                      Erstmal vielen Dank für die super kompetente schnelle Hilfe hier von allen!! :+1: :clap:
                                      Die gute Nachricht ist, es ist alles durchgeupdatet und iob wieder gestartet.

                                      Die schlechte ist, es kam der einrichtungsassistent und nun sind nur 3 Instanzen aktiv statt über 20.
                                      Die korekten Adapter stehen aber noch unter Adapter. Es fehlt auch der Punkte Scripte im Menü.
                                      Habe Scripte mal als Instanz aktiviert, die Scripte sind auch wech.....

                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #29

                                      @belei

                                      iob diag
                                      

                                      sagt?

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      B 2 Antworten Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @belei

                                        iob diag
                                        

                                        sagt?

                                        B Offline
                                        B Offline
                                        Belei
                                        schrieb am zuletzt editiert von Belei
                                        #30

                                        @thomas-braun said in ERROR: Process exited with code 1 / keine Updates möglich:

                                        iob diag

                                        Wenn ich den als root ausführe sagt er, mach nicht als root.
                                        Wenn ich ihn mit einem standard User ausführe sagt er:

                                        [sudo] Passwort für benni:
                                        Leider darf der Benutzer benni »/usr/bin/curl -sLf https://iobroker.net/diag.sh --output /home/iobroker/.diag.sh« als iobroker auf ioBrokerNuc nicht ausführen  
                                        

                                        EDIT:
                                        Hab ihm jetzt in die sudo Gruppe gepackt

                                        1 Antwort Letzte Antwort
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @belei

                                          iob diag
                                          

                                          sagt?

                                          B Offline
                                          B Offline
                                          Belei
                                          schrieb am zuletzt editiert von
                                          #31

                                          @thomas-braun

                                          ======================= SUMMARY =======================
                                                                  v.2023-10-10
                                          
                                          
                                             Static hostname: ioBrokerNuc
                                                   Icon name: computer-vm
                                                     Chassis: vm
                                              Virtualization: kvm
                                            Operating System: Debian GNU/Linux 10 (buster)
                                                      Kernel: Linux 4.19.0-25-amd64
                                                Architecture: x86-64
                                          
                                          Installation:           kvm
                                          Kernel:                 x86_64
                                          Userland:               amd64
                                          Timezone:               Europe/Berlin (CET, +0100)
                                          User-ID:                1000
                                          X-Server:               false
                                          Boot Target:            graphical.target
                                          
                                          Pending OS-Updates:     0
                                          Pending iob updates:    0
                                          
                                          Nodejs-Installation:    /usr/bin/nodejs         v18.19.0
                                                                  /usr/bin/node           v18.19.0
                                                                  /usr/bin/npm            10.2.3
                                                                  /usr/bin/npx            10.2.3
                                                                  /usr/bin/corepack       0.22.0
                                          
                                          Recommended versions are nodejs 18.19.0 and npm 10.2.3
                                          Your nodejs installation is correct
                                          
                                          MEMORY:
                                                        total        used        free      shared  buff/cache   available
                                          Mem:           2.0G        972M        312M        1.0M        709M        856M
                                          Swap:          2.0G         29M        2.0G
                                          Total:         4.0G        1.0G        2.3G
                                          
                                          Active iob-Instances:   6
                                          Active repo(s): stable
                                          
                                          ioBroker Core:          js-controller           5.0.17
                                                                  admin                   6.12.0
                                          
                                          ioBroker Status:        iobroker is running on this host.
                                          
                                          
                                          Objects type: jsonl
                                          States  type: redis
                                          
                                          Status admin and web instance:
                                          + system.adapter.admin.0                  : admin                 : ioBrokerNuc                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                          
                                          Objects:                198
                                          States:                 7866
                                          
                                          Size of iob-Database:
                                          
                                          4.1M    /opt/iobroker/iobroker-data/objects.jsonl
                                          108K    /opt/iobroker/iobroker-data/objects.json.migrated
                                          68K     /opt/iobroker/iobroker-data/objects.json.bak.migrated
                                          8.0K    /opt/iobroker/iobroker-data/states.json.bak
                                          8.0K    /opt/iobroker/iobroker-data/states.json
                                          
                                          
                                          
                                          =================== END OF SUMMARY ====================
                                          

                                          === Mark text until here for copying ===

                                          Thomas BraunT 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          897

                                          Online

                                          32.5k

                                          Benutzer

                                          81.8k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe