Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Nach Nodejs Update kein Adapter mehr updatebar

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Nach Nodejs Update kein Adapter mehr updatebar

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @tilly last edited by

      @tilly log dich nicht als root ein!
      nimm den normalen User

      wurde dir auch so bei der Grundinstallation gesagt

      T 1 Reply Last reply Reply Quote 0
      • T
        tilly @Homoran last edited by

        @homoran

        ok mit einem anderen User ändert sich aber nichts

        user@iobroker-ubuntu:/opt/iobroker$ npm ls | grep -E 'github|ERR'
        npm ERR! code ELSPROBLEMS
        npm ERR! invalid: iobroker.alexa2@3.18.5 /opt/iobroker/node_modules/iobroker.alexa2
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/user/.npm/_logs/2022-07-21T18_14_04_807Z-debug-0.log
        
        
        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 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!     /home/iobroker/.npm/_logs/2022-07-21T18_10_03_414Z-debug-0.log
        host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217
        
        Glasfaser Thomas Braun 3 Replies Last reply Reply Quote 0
        • Glasfaser
          Glasfaser @tilly last edited by

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

          ok mit einem anderen User ändert sich aber nichts

          Sollte auch nicht ...
          nur als Login root kann man viel kaputt machen

          Homoran 1 Reply Last reply Reply Quote 0
          • Glasfaser
            Glasfaser @tilly last edited by

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

            npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abab' -> '/opt/iobroker/node_modules/.abab-bvmibCm3'

            sudo rm -rf /opt/iobroker/node_modules/.abab-bvmibCm3
            
            1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @tilly last edited by

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

              rm -rf /opt/iobroker/node_modules/.abab-bvmibCm3
              

              Weitere Verzeichnisse mit kryptischen Endungen analog dazu auch löschen.

              1 Reply Last reply Reply Quote 0
              • Homoran
                Homoran Global Moderator Administrators @Glasfaser last edited by

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

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

                ok mit einem anderen User ändert sich aber nichts

                Sollte auch nicht ...
                nur als Login root kann man viel kaputt machen

                @tilly
                Vielleicht solltest du mal

                iobroker stop
                iobroker fix
                iobroker start 
                

                durchführen, um Rechteprobleme, die möglicherweise durch die Nutzung von root entstanden sind zu fixen.

                Wird an deinem momentanen Problem auch nichts ändern, und auch nicht unbedingt alle Schäden (wenn vorhanden) beheben.

                1 Reply Last reply Reply Quote 0
                • T
                  tilly last edited by

                  das sind so viele, kann ich die wirklich alle löschen?

                  70f29d78-b11e-4d86-8b56-22e5f4f90b71-image.png

                  iobroker stop
                  iobroker fix
                  iobroker start 
                  

                  habe ich gemacht

                  Glasfaser 1 Reply Last reply Reply Quote 0
                  • Glasfaser
                    Glasfaser @tilly last edited by Glasfaser

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

                    das sind so viele, kann ich die wirklich alle löschen?

                    Werden alle nach einem upgade Versuch angezeigt , was du da zeigst im Screenshot

                    npm ERR! ENOTEMPTY: directory not empty, rename
                    
                    T 1 Reply Last reply Reply Quote 0
                    • T
                      tilly @Glasfaser last edited by

                      @glasfaser

                      nein ich lösche ein Verzeichnis und versuche erneut einen Adapter upzudaten.
                      Dann kommt wieder ein Ordner etc.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @tilly last edited by

                        @tilly

                        In meinem System gibt es bis auf .bin keine Verzeichnisse, die mit Punkt anfangen. Ich vermute, die können dann alle weg.

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          tilly @Thomas Braun last edited by

                          @thomas-braun

                          ok dann sicher ich die Dateien mal und lösche dann alles

                          T 1 Reply Last reply Reply Quote 0
                          • T
                            tilly @tilly last edited by

                            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 Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @tilly last edited by

                              @tilly

                              Das selbe in Grün...

                              T 1 Reply Last reply Reply Quote 0
                              • T
                                tilly @Thomas Braun last edited by 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
                                
                                
                                mikeal created this issue in request/request

                                open Request’s Past, Present and Future #3142

                                mikeal created this issue in request/request

                                open Request’s Past, Present and Future #3142

                                Qix- created this issue in visionmedia/debug

                                closed ReDos Vulnerability Regression Visibility Notice #797

                                Qix- created this issue in visionmedia/debug

                                closed ReDos Vulnerability Regression Visibility Notice #797

                                Qix- created this issue in visionmedia/debug

                                closed ReDos Vulnerability Regression Visibility Notice #797

                                Qix- created this issue in visionmedia/debug

                                closed ReDos Vulnerability Regression Visibility Notice #797

                                mikeal created this issue in request/request

                                open Request’s Past, Present and Future #3142

                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @tilly last edited by

                                  @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 1 Reply Last reply Reply Quote 0
                                  • T
                                    tilly @Thomas Braun last edited by

                                    @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 Braun 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @tilly last edited by

                                      @tilly

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

                                      T 1 Reply Last reply Reply Quote 0
                                      • T
                                        tilly @Thomas Braun last edited by

                                        @thomas-braun

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

                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @tilly last edited by 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 1 Reply Last reply Reply Quote 0
                                          • T
                                            tilly @Thomas Braun last edited by

                                            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.
                                            
                                            mikeal created this issue in request/request

                                            open Request’s Past, Present and Future #3142

                                            mikeal created this issue in request/request

                                            open Request’s Past, Present and Future #3142

                                            Qix- created this issue in visionmedia/debug

                                            closed ReDos Vulnerability Regression Visibility Notice #797

                                            Qix- created this issue in visionmedia/debug

                                            closed ReDos Vulnerability Regression Visibility Notice #797

                                            Qix- created this issue in visionmedia/debug

                                            closed ReDos Vulnerability Regression Visibility Notice #797

                                            Qix- created this issue in visionmedia/debug

                                            closed ReDos Vulnerability Regression Visibility Notice #797

                                            mikeal created this issue in request/request

                                            open Request’s Past, Present and Future #3142

                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            405
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            nodejs update adaper update
                                            6
                                            67
                                            6044
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo