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

  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Nach Nodejs Update kein Adapter mehr updatebar

NEWS

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.5k

Nach Nodejs Update kein Adapter mehr updatebar

Geplant Angeheftet Gesperrt Verschoben Error/Bug
nodejs update adaper update
67 Beiträge 6 Kommentatoren 10.4k Aufrufe 6 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.
  • T tilly

    jetzt tauchen noch mehr komische Verzeichnisse auf

    npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/has-binary2/node_modules/isarray' -> '/opt/iobroker/node_modules/has-binary2/node_modules/.isarray-z8HzvEK7'

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

    @tilly

    Das selbe in Grün...

    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

    T 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @tilly

      Das selbe in Grün...

      T Offline
      T Offline
      tilly
      schrieb am zuletzt editiert von tilly
      #25

      @thomas-braun

      hab nun alle Dateien in @verzeichnissen mit kryptischen Endungen gelöscht
      jetzt folgendes

      user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade cloud --debug
      
      This upgrade of "cloud" will introduce the following changes:
      ==========================================================================
      -> 4.2.1:
      Used new version of socket library.
      ==========================================================================
      
      Would you like to upgrade cloud from @4.2.0 to @4.2.1 now? [(y)es, (n)o]: y
      Update cloud from @4.2.0 to @4.2.1
      NPM version: 8.11.0
      Installing iobroker.cloud@4.2.1... (System call)
      npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
      npm WARN deprecated 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 one that's built-in.
      npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js
      npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
      npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
      npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js
      npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
      npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
      npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
      npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
      npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client
      npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
      npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
      npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
      npm ERR! code ENOTEMPTY
      npm ERR! syscall rename
      npm ERR! path /opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src
      npm ERR! dest /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
      npm ERR! errno -39
      npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src' -> '/opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src'
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /home/iobroker/.npm/_logs/2022-07-21T19_54_23_300Z-debug-0.log
      host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217
      
      
      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • T tilly

        @thomas-braun

        hab nun alle Dateien in @verzeichnissen mit kryptischen Endungen gelöscht
        jetzt folgendes

        user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade cloud --debug
        
        This upgrade of "cloud" will introduce the following changes:
        ==========================================================================
        -> 4.2.1:
        Used new version of socket library.
        ==========================================================================
        
        Would you like to upgrade cloud from @4.2.0 to @4.2.1 now? [(y)es, (n)o]: y
        Update cloud from @4.2.0 to @4.2.1
        NPM version: 8.11.0
        Installing iobroker.cloud@4.2.1... (System call)
        npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
        npm WARN deprecated 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 one that's built-in.
        npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js
        npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
        npm WARN deprecated har-validator@5.1.5: this library is no longer supported
        npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
        npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js
        npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
        npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
        npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
        npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
        npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
        npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
        npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
        npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
        npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
        npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
        npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client
        npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
        npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
        npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
        npm ERR! code ENOTEMPTY
        npm ERR! syscall rename
        npm ERR! path /opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src
        npm ERR! dest /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
        npm ERR! errno -39
        npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src' -> '/opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src'
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/iobroker/.npm/_logs/2022-07-21T19_54_23_300Z-debug-0.log
        host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217
        
        
        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #26

        @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

        rm -rf /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
        

        Das Spiel kennst du ja schon.

        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

        T 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

          rm -rf /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
          

          Das Spiel kennst du ja schon.

          T Offline
          T Offline
          tilly
          schrieb am zuletzt editiert von
          #27

          @thomas-braun

          ich wollte gerade Feierabend machen, starte iobroker und wollte morgen weiter machen.
          auf einmal sind die ganzen gelöschten Dateien(z.B. /opt/iobroker/node_modules/.abbrev-5eNud0FY) wieder da?

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • T tilly

            @thomas-braun

            ich wollte gerade Feierabend machen, starte iobroker und wollte morgen weiter machen.
            auf einmal sind die ganzen gelöschten Dateien(z.B. /opt/iobroker/node_modules/.abbrev-5eNud0FY) wieder da?

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

            @tilly

            Lief der iobroker eigentlich die ganze Zeit? Knips den aus, wenn du am npm tree bastelst.

            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

            T 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @tilly

              Lief der iobroker eigentlich die ganze Zeit? Knips den aus, wenn du am npm tree bastelst.

              T Offline
              T Offline
              tilly
              schrieb am zuletzt editiert von
              #29

              @thomas-braun

              nein der war die ganze Zeit aus, wollte den nur bis morgen wieder an machen wenn ich weiter mache.

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • T tilly

                @thomas-braun

                nein der war die ganze Zeit aus, wollte den nur bis morgen wieder an machen wenn ich weiter mache.

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

                @tilly

                Beim iobroker Start werden Module neukompiliert.

                Ich vermute stark, da ist in der Vergangenheit mal mit sudo oder gar vollem root was installiert worden und jetzt ist da einiges verbogen.

                Edit: Gerade nochmal hochgescrollt... Du warst ja tatsächlich als root unterwegs. Würde meine Vermutung stützen.

                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

                T 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @tilly

                  Beim iobroker Start werden Module neukompiliert.

                  Ich vermute stark, da ist in der Vergangenheit mal mit sudo oder gar vollem root was installiert worden und jetzt ist da einiges verbogen.

                  Edit: Gerade nochmal hochgescrollt... Du warst ja tatsächlich als root unterwegs. Würde meine Vermutung stützen.

                  T Offline
                  T Offline
                  tilly
                  schrieb am zuletzt editiert von
                  #31

                  so habe iobroker gestoppt, alle Dateien mit kryptischen Endungen gelöscht und versucht alexa2 upzudaten.

                  user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade alexa2 --debug
                  
                  This upgrade of "alexa2" will introduce the following changes:
                  ==========================================================================
                  -> 3.18.6:
                  Fix deviceStop sequence command
                  
                  -> 3.18.5:
                  Fix crash case reported by Sentry
                  Add image for Fire Cube
                  
                  -> 3.18.3:
                  Fix doNotDisturb and doNotDisturb for All devices
                  Update do not disturb status after set for all devices
                  preserve a changed name for a "This device" device object
                  
                  -> 3.18.2:
                  Enable commands again for Apps with type A2TF17PFR55MTB - will only work sometimes as it seems
                  ==========================================================================
                  
                  Would you like to upgrade alexa2 from @3.18.1 to @3.18.6 now? [(y)es, (n)o]: y
                  Update alexa2 from @3.18.1 to @3.18.6
                  NPM version: 8.11.0
                  Installing iobroker.alexa2@3.18.6... (System call)
                  npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
                  npm WARN deprecated 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 one that's built-in.
                  npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js
                  npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                  npm WARN deprecated har-validator@5.1.5: this library is no longer supported
                  npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                  npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js
                  npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                  npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                  npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
                  npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
                  npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                  npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                  npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                  npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                  npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                  npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                  npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                  npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                  npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                  npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                  npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
                  npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client
                  npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
                  npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
                  npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
                  npm ERR! code 1
                  npm ERR! path /opt/iobroker/node_modules/openzwave-shared
                  npm ERR! command failed
                  npm ERR! command sh -c node-gyp rebuild
                  npm ERR! make: Entering directory '/opt/iobroker/node_modules/openzwave-shared/build'
                  npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
                  npm ERR! openzwave_shared.target.mk:150: recipe for target 'Release/obj.target/openzwave_shared/src/callbacks.o' failed
                  npm ERR! make: Leaving directory '/opt/iobroker/node_modules/openzwave-shared/build'
                  npm ERR! gyp info it worked if it ends with ok
                  npm ERR! gyp info using node-gyp@8.4.1
                  npm ERR! gyp info using node@16.16.0 | linux | x64
                  npm ERR! gyp info find Python using Python version 3.6.9 found at "/usr/bin/python3"
                  npm ERR! gyp info spawn /usr/bin/python3
                  npm ERR! gyp info spawn args [
                  npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
                  npm ERR! gyp info spawn args   'binding.gyp',
                  npm ERR! gyp info spawn args   '-f',
                  npm ERR! gyp info spawn args   'make',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/openzwave-shared/build/config.gypi',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/16.16.0/include/node/common.gypi',
                  npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
                  npm ERR! gyp info spawn args   '-Dvisibility=default',
                  npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/16.16.0',
                  npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
                  npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.16.0/<(target_arch)/node.lib',
                  npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/openzwave-shared',
                  npm ERR! gyp info spawn args   '-Dnode_engine=v8',
                  npm ERR! gyp info spawn args   '--depth=.',
                  npm ERR! gyp info spawn args   '--no-parallel',
                  npm ERR! gyp info spawn args   '--generator-output',
                  npm ERR! gyp info spawn args   'build',
                  npm ERR! gyp info spawn args   '-Goutput_dir=.'
                  npm ERR! gyp info spawn args ]
                  npm ERR! gyp info spawn make
                  npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                  npm ERR! In file included from /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8.h:30:0,
                  npm ERR!                  from ../src/openzwave.hpp:27,
                  npm ERR!                  from ../src/callbacks.cc:18:
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                       ^~~~~~~~~~~
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                       ^~~~~~~~~~~
                  npm ERR!                                       remove_cv
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                       ^~~~~~~~~~~
                  npm ERR!                                       remove_cv
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:50: error: template argument 2 is invalid
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                                   ^
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                                                ^~~~~~~
                  npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: note: suggested alternative: ‘perror’
                  npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                  npm ERR!                                                                ^~~~~~~
                  npm ERR!                                                                perror
                  npm ERR! make: *** [Release/obj.target/openzwave_shared/src/callbacks.o] Error 1
                  npm ERR! gyp ERR! build error
                  npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
                  npm ERR! gyp ERR! stack     at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)
                  npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
                  npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                  npm ERR! gyp ERR! System Linux 4.15.0-189-generic
                  npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
                  npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
                  npm ERR! gyp ERR! node -v v16.16.0
                  npm ERR! gyp ERR! node-gyp -v v8.4.1
                  npm ERR! gyp ERR! not ok
                  
                  npm ERR! A complete log of this run can be found in:
                  npm ERR!     /home/iobroker/.npm/_logs/2022-07-22T08_24_18_272Z-debug-0.log
                  upload [27] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/alexa.png alexa.png image/png
                  upload [20] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot3.png icons/echo_dot3.png image/png
                  upload [19] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot4.png icons/echo_dot4.png image/png
                  upload [18] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_flex.png icons/echo_flex.png image/png
                  upload [17] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_plus2.png icons/echo_plus2.png image/png
                  upload [16] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show.png icons/echo_show.png image/png
                  upload [15] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show2.png icons/echo_show2.png image/png
                  upload [14] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show5.png icons/echo_show5.png image/png
                  upload [13] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_studio.png icons/echo_studio.png image/png
                  upload [12] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_sub.png icons/echo_sub.png image/png
                  upload [11] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetab.png icons/firetab.png image/png
                  upload [10] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetv.png icons/firetv.png image/png
                  upload [9] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/microphone.png icons/microphone.png image/png
                  upload [8] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/multiroom.png icons/multiroom.png image/png
                  upload [7] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/raspi.png icons/raspi.png image/png
                  upload [6] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/reverb.png icons/reverb.png image/png
                  upload [5] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/sonos.png icons/sonos.png image/png
                  upload [4] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/spot.png icons/spot.png image/png
                  upload [3] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/index_m.html index_m.html text/html
                  upload [2] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/info.png info.png image/png
                  upload [1] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/warning.png warning.png image/png
                  upload [0] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/words.js words.js application/javascript^[Sorry, try again.
                  
                  Thomas BraunT 1 Antwort Letzte Antwort
                  0
                  • T tilly

                    so habe iobroker gestoppt, alle Dateien mit kryptischen Endungen gelöscht und versucht alexa2 upzudaten.

                    user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade alexa2 --debug
                    
                    This upgrade of "alexa2" will introduce the following changes:
                    ==========================================================================
                    -> 3.18.6:
                    Fix deviceStop sequence command
                    
                    -> 3.18.5:
                    Fix crash case reported by Sentry
                    Add image for Fire Cube
                    
                    -> 3.18.3:
                    Fix doNotDisturb and doNotDisturb for All devices
                    Update do not disturb status after set for all devices
                    preserve a changed name for a "This device" device object
                    
                    -> 3.18.2:
                    Enable commands again for Apps with type A2TF17PFR55MTB - will only work sometimes as it seems
                    ==========================================================================
                    
                    Would you like to upgrade alexa2 from @3.18.1 to @3.18.6 now? [(y)es, (n)o]: y
                    Update alexa2 from @3.18.1 to @3.18.6
                    NPM version: 8.11.0
                    Installing iobroker.alexa2@3.18.6... (System call)
                    npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
                    npm WARN deprecated 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 one that's built-in.
                    npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js
                    npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                    npm WARN deprecated har-validator@5.1.5: this library is no longer supported
                    npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
                    npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js
                    npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                    npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                    npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
                    npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
                    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
                    npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                    npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                    npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
                    npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                    npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
                    npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                    npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
                    npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client
                    npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
                    npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
                    npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
                    npm ERR! code 1
                    npm ERR! path /opt/iobroker/node_modules/openzwave-shared
                    npm ERR! command failed
                    npm ERR! command sh -c node-gyp rebuild
                    npm ERR! make: Entering directory '/opt/iobroker/node_modules/openzwave-shared/build'
                    npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
                    npm ERR! openzwave_shared.target.mk:150: recipe for target 'Release/obj.target/openzwave_shared/src/callbacks.o' failed
                    npm ERR! make: Leaving directory '/opt/iobroker/node_modules/openzwave-shared/build'
                    npm ERR! gyp info it worked if it ends with ok
                    npm ERR! gyp info using node-gyp@8.4.1
                    npm ERR! gyp info using node@16.16.0 | linux | x64
                    npm ERR! gyp info find Python using Python version 3.6.9 found at "/usr/bin/python3"
                    npm ERR! gyp info spawn /usr/bin/python3
                    npm ERR! gyp info spawn args [
                    npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
                    npm ERR! gyp info spawn args   'binding.gyp',
                    npm ERR! gyp info spawn args   '-f',
                    npm ERR! gyp info spawn args   'make',
                    npm ERR! gyp info spawn args   '-I',
                    npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/openzwave-shared/build/config.gypi',
                    npm ERR! gyp info spawn args   '-I',
                    npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
                    npm ERR! gyp info spawn args   '-I',
                    npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/16.16.0/include/node/common.gypi',
                    npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
                    npm ERR! gyp info spawn args   '-Dvisibility=default',
                    npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/16.16.0',
                    npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
                    npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.16.0/<(target_arch)/node.lib',
                    npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/openzwave-shared',
                    npm ERR! gyp info spawn args   '-Dnode_engine=v8',
                    npm ERR! gyp info spawn args   '--depth=.',
                    npm ERR! gyp info spawn args   '--no-parallel',
                    npm ERR! gyp info spawn args   '--generator-output',
                    npm ERR! gyp info spawn args   'build',
                    npm ERR! gyp info spawn args   '-Goutput_dir=.'
                    npm ERR! gyp info spawn args ]
                    npm ERR! gyp info spawn make
                    npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                    npm ERR! In file included from /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8.h:30:0,
                    npm ERR!                  from ../src/openzwave.hpp:27,
                    npm ERR!                  from ../src/callbacks.cc:18:
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                       ^~~~~~~~~~~
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                       ^~~~~~~~~~~
                    npm ERR!                                       remove_cv
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:38: note: suggested alternative: ‘remove_cv’
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                       ^~~~~~~~~~~
                    npm ERR!                                       remove_cv
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:50: error: template argument 2 is invalid
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                                   ^
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                                                ^~~~~~~
                    npm ERR! /home/iobroker/.cache/node-gyp/16.16.0/include/node/v8-internal.h:492:63: note: suggested alternative: ‘perror’
                    npm ERR!              !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                    npm ERR!                                                                ^~~~~~~
                    npm ERR!                                                                perror
                    npm ERR! make: *** [Release/obj.target/openzwave_shared/src/callbacks.o] Error 1
                    npm ERR! gyp ERR! build error
                    npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
                    npm ERR! gyp ERR! stack     at ChildProcess.onExit (/opt/iobroker/node_modules/node-gyp/lib/build.js:194:23)
                    npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
                    npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                    npm ERR! gyp ERR! System Linux 4.15.0-189-generic
                    npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
                    npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
                    npm ERR! gyp ERR! node -v v16.16.0
                    npm ERR! gyp ERR! node-gyp -v v8.4.1
                    npm ERR! gyp ERR! not ok
                    
                    npm ERR! A complete log of this run can be found in:
                    npm ERR!     /home/iobroker/.npm/_logs/2022-07-22T08_24_18_272Z-debug-0.log
                    upload [27] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/alexa.png alexa.png image/png
                    upload [20] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot3.png icons/echo_dot3.png image/png
                    upload [19] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_dot4.png icons/echo_dot4.png image/png
                    upload [18] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_flex.png icons/echo_flex.png image/png
                    upload [17] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_plus2.png icons/echo_plus2.png image/png
                    upload [16] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show.png icons/echo_show.png image/png
                    upload [15] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show2.png icons/echo_show2.png image/png
                    upload [14] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_show5.png icons/echo_show5.png image/png
                    upload [13] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_studio.png icons/echo_studio.png image/png
                    upload [12] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/echo_sub.png icons/echo_sub.png image/png
                    upload [11] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetab.png icons/firetab.png image/png
                    upload [10] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/firetv.png icons/firetv.png image/png
                    upload [9] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/microphone.png icons/microphone.png image/png
                    upload [8] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/multiroom.png icons/multiroom.png image/png
                    upload [7] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/raspi.png icons/raspi.png image/png
                    upload [6] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/reverb.png icons/reverb.png image/png
                    upload [5] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/sonos.png icons/sonos.png image/png
                    upload [4] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/icons/spot.png icons/spot.png image/png
                    upload [3] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/index_m.html index_m.html text/html
                    upload [2] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/info.png info.png image/png
                    upload [1] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/warning.png warning.png image/png
                    upload [0] alexa2.admin /opt/iobroker/node_modules/iobroker.alexa2/admin/words.js words.js application/javascript^[Sorry, try again.
                    
                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von
                    #32

                    @tilly

                    Ist 'build-essential' installiert?

                    apt policy build-essential
                    

                    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

                    T 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @tilly

                      Ist 'build-essential' installiert?

                      apt policy build-essential
                      
                      T Offline
                      T Offline
                      tilly
                      schrieb am zuletzt editiert von
                      #33

                      @thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:

                      apt policy build-essential

                      ja

                      user@iobroker-ubuntu:/opt/iobroker$ apt policy build-essential
                      build-essential:
                        Installiert:           12.4ubuntu1
                        Installationskandidat: 12.4ubuntu1
                        Versionstabelle:
                       *** 12.4ubuntu1 500
                              500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
                              100 /var/lib/dpkg/status
                      
                      
                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • T tilly

                        @thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:

                        apt policy build-essential

                        ja

                        user@iobroker-ubuntu:/opt/iobroker$ apt policy build-essential
                        build-essential:
                          Installiert:           12.4ubuntu1
                          Installationskandidat: 12.4ubuntu1
                          Versionstabelle:
                         *** 12.4ubuntu1 500
                                500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
                                100 /var/lib/dpkg/status
                        
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #34

                        @tilly

                        Dann lösch den cache mal.

                        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

                        T 1 Antwort Letzte Antwort
                        0
                        • Thomas BraunT Thomas Braun

                          @tilly

                          Dann lösch den cache mal.

                          T Offline
                          T Offline
                          tilly
                          schrieb am zuletzt editiert von
                          #35

                          @thomas-braun

                          so?

                          sudo apt-get clean 
                          
                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • T tilly

                            @thomas-braun

                            so?

                            sudo apt-get clean 
                            
                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #36

                            @tilly

                            Nein, den npm cache

                            cd /opt/iobroker
                            sudo -u iobroker npm cache clear --force
                            

                            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

                            T 1 Antwort Letzte Antwort
                            0
                            • Thomas BraunT Thomas Braun

                              @tilly

                              Nein, den npm cache

                              cd /opt/iobroker
                              sudo -u iobroker npm cache clear --force
                              
                              T Offline
                              T Offline
                              tilly
                              schrieb am zuletzt editiert von
                              #37

                              @thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:

                              sudo -u iobroker npm cache clear --force

                              user@iobroker-ubuntu:/opt/iobroker$ sudo -u iobroker npm cache clear --force
                              npm WARN logfile could not be created: Error: EACCES: permission denied, open '/home/user/.npm/_logs/2022-07-22T09_05_23_231Z-debug-0.log'
                              npm WARN using --force Recommended protections disabled.
                              
                              
                              Thomas BraunT 1 Antwort Letzte Antwort
                              0
                              • T tilly

                                @thomas-braun said in Nach Nodejs Update kein Adapter mehr updatebar:

                                sudo -u iobroker npm cache clear --force

                                user@iobroker-ubuntu:/opt/iobroker$ sudo -u iobroker npm cache clear --force
                                npm WARN logfile could not be created: Error: EACCES: permission denied, open '/home/user/.npm/_logs/2022-07-22T09_05_23_231Z-debug-0.log'
                                npm WARN using --force Recommended protections disabled.
                                
                                
                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                schrieb am zuletzt editiert von
                                #38

                                @tilly

                                sudo -H -u iobroker npm cache clear --force
                                

                                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

                                T 1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @tilly

                                  sudo -H -u iobroker npm cache clear --force
                                  
                                  T Offline
                                  T Offline
                                  tilly
                                  schrieb am zuletzt editiert von
                                  #39

                                  @thomas-braun

                                  user@iobroker-ubuntu:/opt/iobroker$ sudo -H -u iobroker npm cache clear --force
                                  npm WARN using --force Recommended protections disabled.
                                  
                                  

                                  und jetzt nochmal versuchen alexa2 upzudaten?

                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • T tilly

                                    @thomas-braun

                                    user@iobroker-ubuntu:/opt/iobroker$ sudo -H -u iobroker npm cache clear --force
                                    npm WARN using --force Recommended protections disabled.
                                    
                                    

                                    und jetzt nochmal versuchen alexa2 upzudaten?

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

                                    @tilly

                                    Nein, der Show Stopper liegt bei openzwave-shared.
                                    Das Modul bzw. den zugehörigen Adapter nochmal sauber installieren/rebuilden.

                                    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

                                    T 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @tilly

                                      Nein, der Show Stopper liegt bei openzwave-shared.
                                      Das Modul bzw. den zugehörigen Adapter nochmal sauber installieren/rebuilden.

                                      T Offline
                                      T Offline
                                      tilly
                                      schrieb am zuletzt editiert von
                                      #41

                                      @thomas-braun

                                      möchte jetzt iobroker nicht starten, daher würde ich den Adapter(wird nicht mehr benötigt) über die Konsole löschen.
                                      So?

                                      iobroker del openzwave-shared
                                      
                                      Thomas BraunT 1 Antwort Letzte Antwort
                                      0
                                      • T tilly

                                        @thomas-braun

                                        möchte jetzt iobroker nicht starten, daher würde ich den Adapter(wird nicht mehr benötigt) über die Konsole löschen.
                                        So?

                                        iobroker del openzwave-shared
                                        
                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #42

                                        @tilly

                                        Ich vermute der kommt als Dependency aus einem Adapter. Ich würde den ganzen Adapter rauswerfen.
                                        Schau wo openzwave-shared hängt:

                                        cd /opt/iobroker 
                                        npm ls openzwave-shared
                                        

                                        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

                                        T 1 Antwort Letzte Antwort
                                        0
                                        • mickymM Offline
                                          mickymM Offline
                                          mickym
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #43

                                          Ich hätte ja das ganze node-modules Verzeichnis gelöscht, inkl. package-lock.json und dann mit npm install neu aufbauen lassen. Wenn du eh eine Datensicherung hast, solltest du ja auch auf den Stand zurückkehren können. Bei mir hat diese Radikalkur jedenfalls geholfen, einen fehlerfreien Baum zu bekommen.

                                          Jeder Flow bzw. jedes Script, das ich hier poste implementiert jeder auf eigene Gefahr. Flows und Scripts können Fehler aufweisen und weder der Seitenbetreiber noch ich persönlich können hierfür haftbar gemacht werden. Das gleiche gilt für Empfehlungen aller Art.

                                          T 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

                                          716

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          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