Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller lässt sich nicht updaten...

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.8k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    723

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    1.2k

js-controller lässt sich nicht updaten...

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
35 Beiträge 3 Kommentatoren 2.8k Aufrufe 3 Beobachtet
  • Ä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.
  • Mr. BurnsM Mr. Burns

    Guten Abend,

    nach einem update von node v14 auf v16 und npm v6 auf v8.15 läßt sich der js-controler (4.0.21 -->4.0.23) nicht updaten.
    Den fixer hab ich schon ein paar mal drüber laufen lassen, neu gestartet sowie den Befehl:

    for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done
    

    im Verzeichnis /opt/iobroker/node_modules ausgeführt.
    Nachfolgend hab ich den Ausdruck des debug modus angehängt.

    Für einen Hinweis wäre ich dankbar.

    pi@ioBroker:/opt/iobroker/node_modules $ iobroker upgrade self --debug
    Update js-controller from @4.0.21 to @4.0.23
    Stopped Objects DB
    Stopped States DB
    NPM version: 8.15.0
    Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
    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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
    npm ERR! code 1
    npm ERR! path /opt/iobroker/node_modules/openzwave-shared
    npm ERR! command failed
    npm ERR! command sh /tmp/install-fb22f918.sh
    npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird betreten
    npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
    npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird verlassen
    npm ERR! gyp info it worked if it ends with ok
    npm ERR! gyp info using node-gyp@9.0.0
    npm ERR! gyp info using node@16.17.1 | linux | arm
    npm ERR! gyp info find Python using Python version 3.7.3 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   '/usr/lib/node_modules/npm/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   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
    npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
    npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(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.17.1/include/node/v8.h:30,
    npm ERR!                  from ../src/openzwave.hpp:27,
    npm ERR!                  from ../src/callbacks.cc:18:
    npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
    npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/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.17.1/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.17.1/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.17.1/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.17.1/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.17.1/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.17.1/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: *** [openzwave_shared.target.mk:148: Release/obj.target/openzwave_shared/src/callbacks.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
    npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
    npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    npm ERR! gyp ERR! System Linux 5.10.103-v7l+
    npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
    npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
    npm ERR! gyp ERR! node -v v16.17.1
    npm ERR! gyp ERR! node-gyp -v v9.0.0
    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-09-24T19_39_48_428Z-debug-0.log
    

    Gruß

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

    @mr-burns
    Das hat mit dem rebuild von openzwave zu tun, nicht mit dem js-controller.

    sudo ln -s /usr/bin/node /usr/bin/nodejs
    uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
    cd /opt/iobroker
    sudo -H -u iobroker npm cache clean --force
    apt policy python-dev-is-python3 python-is-python3 libudev-dev libopenzwave*
    

    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

    Mr. BurnsM 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @mr-burns
      Das hat mit dem rebuild von openzwave zu tun, nicht mit dem js-controller.

      sudo ln -s /usr/bin/node /usr/bin/nodejs
      uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
      cd /opt/iobroker
      sudo -H -u iobroker npm cache clean --force
      apt policy python-dev-is-python3 python-is-python3 libudev-dev libopenzwave*
      
      Mr. BurnsM Offline
      Mr. BurnsM Offline
      Mr. Burns
      schrieb am zuletzt editiert von
      #3

      @thomas-braun das ist das Ergebnis der Abfragen:

      pi@ioBroker:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
      armv7l
      /usr/bin/nodejs
      /usr/bin/node
      /usr/bin/npm
      v16.17.1
      v16.17.1
      8.19.2
      4.0.21
      pi
      pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
      /home/pi
      OK:1 http://archive.raspberrypi.org/debian buster InRelease
      OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease                                                                                                                
      OK:3 https://repos.influxdata.com/debian stretch InRelease                                                                                                                    
      OK:4 https://phoscon.de/apt/deconz buster InRelease                                                                                                   
      OK:5 https://deb.nodesource.com/node_16.x buster InRelease                   
      Paketlisten werden gelesen... Fertig                 
      Abhängigkeitsbaum wird aufgebaut.       
      Statusinformationen werden eingelesen.... Fertig
      Alle Pakete sind aktuell.
      nodejs:
       Installiert:           16.17.1-deb-1nodesource1
       Installationskandidat: 16.17.1-deb-1nodesource1
       Versionstabelle:
      *** 16.17.1-deb-1nodesource1 500
             500 https://deb.nodesource.com/node_16.x buster/main armhf Packages
             100 /var/lib/dpkg/status
          10.24.0~dfsg-1~deb10u1 500
             500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
      pi@ioBroker:~ $ cd /opt/iobroker
      pi@ioBroker:/opt/iobroker $ sudo -H -u iobroker npm cache clean --force
      npm WARN using --force Recommended protections disabled.
      pi@ioBroker:/opt/iobroker $ apt policy python-dev-is-python3 python-is-python3 libudev-dev libopenzwave*
      libudev-dev:
       Installiert:           241-7~deb10u8+rpi1
       Installationskandidat: 241-7~deb10u8+rpi1
       Versionstabelle:
      *** 241-7~deb10u8+rpi1 500
             500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
             100 /var/lib/dpkg/status
      libopenzwave1.5-dev:
       Installiert:           (keine)
       Installationskandidat: 1.5+ds-6
       Versionstabelle:
          1.5+ds-6 500
             500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
      libopenzwave1.5:
       Installiert:           1.5+ds-6
       Installationskandidat: 1.5+ds-6
       Versionstabelle:
      *** 1.5+ds-6 500
             500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
             100 /var/lib/dpkg/status
      libopenzwave-doc:
       Installiert:           (keine)
       Installationskandidat: 1.5+ds-6
       Versionstabelle:
          1.5+ds-6 500
             500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
      N: Paket python-dev-is-python3 kann nicht gefunden werden.
      N: Paket python-is-python3 kann nicht gefunden werden.
      

      Hilft das weiter?

      Gruß

      DJMarc75D Thomas BraunT 2 Antworten Letzte Antwort
      0
      • Mr. BurnsM Mr. Burns

        @thomas-braun das ist das Ergebnis der Abfragen:

        pi@ioBroker:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
        armv7l
        /usr/bin/nodejs
        /usr/bin/node
        /usr/bin/npm
        v16.17.1
        v16.17.1
        8.19.2
        4.0.21
        pi
        pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
        /home/pi
        OK:1 http://archive.raspberrypi.org/debian buster InRelease
        OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease                                                                                                                
        OK:3 https://repos.influxdata.com/debian stretch InRelease                                                                                                                    
        OK:4 https://phoscon.de/apt/deconz buster InRelease                                                                                                   
        OK:5 https://deb.nodesource.com/node_16.x buster InRelease                   
        Paketlisten werden gelesen... Fertig                 
        Abhängigkeitsbaum wird aufgebaut.       
        Statusinformationen werden eingelesen.... Fertig
        Alle Pakete sind aktuell.
        nodejs:
         Installiert:           16.17.1-deb-1nodesource1
         Installationskandidat: 16.17.1-deb-1nodesource1
         Versionstabelle:
        *** 16.17.1-deb-1nodesource1 500
               500 https://deb.nodesource.com/node_16.x buster/main armhf Packages
               100 /var/lib/dpkg/status
            10.24.0~dfsg-1~deb10u1 500
               500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        pi@ioBroker:~ $ cd /opt/iobroker
        pi@ioBroker:/opt/iobroker $ sudo -H -u iobroker npm cache clean --force
        npm WARN using --force Recommended protections disabled.
        pi@ioBroker:/opt/iobroker $ apt policy python-dev-is-python3 python-is-python3 libudev-dev libopenzwave*
        libudev-dev:
         Installiert:           241-7~deb10u8+rpi1
         Installationskandidat: 241-7~deb10u8+rpi1
         Versionstabelle:
        *** 241-7~deb10u8+rpi1 500
               500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
               100 /var/lib/dpkg/status
        libopenzwave1.5-dev:
         Installiert:           (keine)
         Installationskandidat: 1.5+ds-6
         Versionstabelle:
            1.5+ds-6 500
               500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        libopenzwave1.5:
         Installiert:           1.5+ds-6
         Installationskandidat: 1.5+ds-6
         Versionstabelle:
        *** 1.5+ds-6 500
               500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
               100 /var/lib/dpkg/status
        libopenzwave-doc:
         Installiert:           (keine)
         Installationskandidat: 1.5+ds-6
         Versionstabelle:
            1.5+ds-6 500
               500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
        N: Paket python-dev-is-python3 kann nicht gefunden werden.
        N: Paket python-is-python3 kann nicht gefunden werden.
        

        Hilft das weiter?

        Gruß

        DJMarc75D Offline
        DJMarc75D Offline
        DJMarc75
        schrieb am zuletzt editiert von
        #4

        @mr-burns strech ... buster... alles nicht aktuell !

        Lehrling seit 1975 !!!
        Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
        https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

        1 Antwort Letzte Antwort
        0
        • Mr. BurnsM Mr. Burns

          @thomas-braun das ist das Ergebnis der Abfragen:

          pi@ioBroker:~ $ uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
          armv7l
          /usr/bin/nodejs
          /usr/bin/node
          /usr/bin/npm
          v16.17.1
          v16.17.1
          8.19.2
          4.0.21
          pi
          pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
          /home/pi
          OK:1 http://archive.raspberrypi.org/debian buster InRelease
          OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease                                                                                                                
          OK:3 https://repos.influxdata.com/debian stretch InRelease                                                                                                                    
          OK:4 https://phoscon.de/apt/deconz buster InRelease                                                                                                   
          OK:5 https://deb.nodesource.com/node_16.x buster InRelease                   
          Paketlisten werden gelesen... Fertig                 
          Abhängigkeitsbaum wird aufgebaut.       
          Statusinformationen werden eingelesen.... Fertig
          Alle Pakete sind aktuell.
          nodejs:
           Installiert:           16.17.1-deb-1nodesource1
           Installationskandidat: 16.17.1-deb-1nodesource1
           Versionstabelle:
          *** 16.17.1-deb-1nodesource1 500
                 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages
                 100 /var/lib/dpkg/status
              10.24.0~dfsg-1~deb10u1 500
                 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
          pi@ioBroker:~ $ cd /opt/iobroker
          pi@ioBroker:/opt/iobroker $ sudo -H -u iobroker npm cache clean --force
          npm WARN using --force Recommended protections disabled.
          pi@ioBroker:/opt/iobroker $ apt policy python-dev-is-python3 python-is-python3 libudev-dev libopenzwave*
          libudev-dev:
           Installiert:           241-7~deb10u8+rpi1
           Installationskandidat: 241-7~deb10u8+rpi1
           Versionstabelle:
          *** 241-7~deb10u8+rpi1 500
                 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                 100 /var/lib/dpkg/status
          libopenzwave1.5-dev:
           Installiert:           (keine)
           Installationskandidat: 1.5+ds-6
           Versionstabelle:
              1.5+ds-6 500
                 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
          libopenzwave1.5:
           Installiert:           1.5+ds-6
           Installationskandidat: 1.5+ds-6
           Versionstabelle:
          *** 1.5+ds-6 500
                 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                 100 /var/lib/dpkg/status
          libopenzwave-doc:
           Installiert:           (keine)
           Installationskandidat: 1.5+ds-6
           Versionstabelle:
              1.5+ds-6 500
                 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
          N: Paket python-dev-is-python3 kann nicht gefunden werden.
          N: Paket python-is-python3 kann nicht gefunden werden.
          

          Hilft das weiter?

          Gruß

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

          @mr-burns

          sudo apt install libopenzwave1.5-dev
          

          Und pass das influx-Repo an.

          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

          Mr. BurnsM 1 Antwort Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @mr-burns

            sudo apt install libopenzwave1.5-dev
            

            Und pass das influx-Repo an.

            Mr. BurnsM Offline
            Mr. BurnsM Offline
            Mr. Burns
            schrieb am zuletzt editiert von
            #6

            @thomas-braun hat was gedauert. Nach dem update war der raspi nicht mehr erreichbar und es hat ein paar Tage gedauert, bis der micro HDMI adapter angekommen ist.

            Netzwerkkarte wieder aktiviert, System läuft wieder aber leider funktioniert es immer noch nicht:

            sudo apt install libopenzwave1.5-dev
            Paketlisten werden gelesen… Fertig
            Abhängigkeitsbaum wird aufgebaut… Fertig
            Statusinformationen werden eingelesen… Fertig
            E: Paket libopenzwave1.5-dev kann nicht gefunden werden.
            E: Mittels des Musters »libopenzwave1.5-dev« konnte kein Paket gefunden werden.
            
            
            Thomas BraunT 1 Antwort Letzte Antwort
            0
            • Mr. BurnsM Mr. Burns

              @thomas-braun hat was gedauert. Nach dem update war der raspi nicht mehr erreichbar und es hat ein paar Tage gedauert, bis der micro HDMI adapter angekommen ist.

              Netzwerkkarte wieder aktiviert, System läuft wieder aber leider funktioniert es immer noch nicht:

              sudo apt install libopenzwave1.5-dev
              Paketlisten werden gelesen… Fertig
              Abhängigkeitsbaum wird aufgebaut… Fertig
              Statusinformationen werden eingelesen… Fertig
              E: Paket libopenzwave1.5-dev kann nicht gefunden werden.
              E: Mittels des Musters »libopenzwave1.5-dev« konnte kein Paket gefunden werden.
              
              
              Thomas BraunT Online
              Thomas BraunT Online
              Thomas Braun
              Most Active
              schrieb am zuletzt editiert von
              #7

              @mr-burns
              Okay, was wird denn da bei dir dann angeboten?

              sudo apt update
              apt policy libopenzwave*
              

              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

              Mr. BurnsM 2 Antworten Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @mr-burns
                Okay, was wird denn da bei dir dann angeboten?

                sudo apt update
                apt policy libopenzwave*
                
                Mr. BurnsM Offline
                Mr. BurnsM Offline
                Mr. Burns
                schrieb am zuletzt editiert von
                #8

                @thomas-braun Das bekomme ich zurück:

                sudo apt update
                apt policy libopenzwave*
                OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
                OK:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                                                             
                OK:3 https://repos.influxdata.com/debian bullseye InRelease                                                                                                               
                OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                                      
                OK:5 https://phoscon.de/apt/deconz bullseye InRelease                
                Paketlisten werden gelesen… Fertig           
                Abhängigkeitsbaum wird aufgebaut… Fertig
                Statusinformationen werden eingelesen… Fertig
                Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                libopenzwave1.6-dev:
                 Installiert:           (keine)
                 Installationskandidat: 1.6.1545+ds-2
                 Versionstabelle:
                    1.6.1545+ds-2 500
                       500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                libopenzwave1.5:
                 Installiert:           1.5+ds-6
                 Installationskandidat: 1.5+ds-6
                 Versionstabelle:
                *** 1.5+ds-6 100
                       100 /var/lib/dpkg/status
                libopenzwave1.6:
                 Installiert:           (keine)
                 Installationskandidat: 1.6.1545+ds-2
                 Versionstabelle:
                    1.6.1545+ds-2 500
                       500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                libopenzwave-doc:
                 Installiert:           (keine)
                 Installationskandidat: 1.6.1545+ds-2
                 Versionstabelle:
                    1.6.1545+ds-2 500
                       500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                

                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @mr-burns
                  Okay, was wird denn da bei dir dann angeboten?

                  sudo apt update
                  apt policy libopenzwave*
                  
                  Mr. BurnsM Offline
                  Mr. BurnsM Offline
                  Mr. Burns
                  schrieb am zuletzt editiert von
                  #9

                  @thomas-braun

                  Ich hab mal die v1.6 installiert. Leider kann der js-controller immer noch nicht aktualisiert werden...

                  iobroker upgrade self --debug
                  Update js-controller from @4.0.21 to @4.0.23
                  Stopped Objects DB
                  Stopped States DB
                  NPM version: 8.19.2
                  Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                  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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                  npm ERR! code 1
                  npm ERR! path /opt/iobroker/node_modules/pcap
                  npm ERR! command failed
                  npm ERR! command sh -c -- node-gyp rebuild
                  npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird betreten
                  npm ERR!   CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
                  npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird verlassen
                  npm ERR! gyp info it worked if it ends with ok
                  npm ERR! gyp info using node-gyp@9.1.0
                  npm ERR! gyp info using node@16.17.1 | linux | arm
                  npm ERR! gyp info find Python using Python version 3.9.2 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   '/usr/lib/node_modules/npm/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/pcap/build/config.gypi',
                  npm ERR! gyp info spawn args   '-I',
                  npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
                  npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                  npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(target_arch)/node.lib',
                  npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/pcap',
                  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! ../pcap_binding.cc:2:10: fatal error: pcap/pcap.h: Datei oder Verzeichnis nicht gefunden
                  npm ERR!     2 | #include <pcap/pcap.h>
                  npm ERR!       |          ^~~~~~~~~~~~~
                  npm ERR! compilation terminated.
                  npm ERR! make: *** [pcap_binding.target.mk:112: Release/obj.target/pcap_binding/pcap_binding.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
                  npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
                  npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                  npm ERR! gyp ERR! System Linux 5.15.61-v7l+
                  npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                  npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/pcap
                  npm ERR! gyp ERR! node -v v16.17.1
                  npm ERR! gyp ERR! node-gyp -v v9.1.0
                  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-09-30T15_32_29_851Z-debug-0.log
                  ``
                  [/s]
                  DJMarc75D 1 Antwort Letzte Antwort
                  0
                  • Mr. BurnsM Mr. Burns

                    @thomas-braun Das bekomme ich zurück:

                    sudo apt update
                    apt policy libopenzwave*
                    OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
                    OK:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                                                             
                    OK:3 https://repos.influxdata.com/debian bullseye InRelease                                                                                                               
                    OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                                                                      
                    OK:5 https://phoscon.de/apt/deconz bullseye InRelease                
                    Paketlisten werden gelesen… Fertig           
                    Abhängigkeitsbaum wird aufgebaut… Fertig
                    Statusinformationen werden eingelesen… Fertig
                    Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                    libopenzwave1.6-dev:
                     Installiert:           (keine)
                     Installationskandidat: 1.6.1545+ds-2
                     Versionstabelle:
                        1.6.1545+ds-2 500
                           500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                    libopenzwave1.5:
                     Installiert:           1.5+ds-6
                     Installationskandidat: 1.5+ds-6
                     Versionstabelle:
                    *** 1.5+ds-6 100
                           100 /var/lib/dpkg/status
                    libopenzwave1.6:
                     Installiert:           (keine)
                     Installationskandidat: 1.6.1545+ds-2
                     Versionstabelle:
                        1.6.1545+ds-2 500
                           500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                    libopenzwave-doc:
                     Installiert:           (keine)
                     Installationskandidat: 1.6.1545+ds-2
                     Versionstabelle:
                        1.6.1545+ds-2 500
                           500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                    

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

                    @mr-burns

                    sudo apt install libpcap0.8-dev
                    

                    Und was genau hast du da jetzt installiert?

                    sudo apt update
                    apt policy libopenzwave*
                    

                    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

                    Mr. BurnsM 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @mr-burns

                      sudo apt install libpcap0.8-dev
                      

                      Und was genau hast du da jetzt installiert?

                      sudo apt update
                      apt policy libopenzwave*
                      
                      Mr. BurnsM Offline
                      Mr. BurnsM Offline
                      Mr. Burns
                      schrieb am zuletzt editiert von
                      #11

                      @thomas-braun

                      sudo apt-get install libopenzwave1.6-dev
                      
                      Thomas BraunT 1 Antwort Letzte Antwort
                      0
                      • Mr. BurnsM Mr. Burns

                        @thomas-braun

                        sudo apt-get install libopenzwave1.6-dev
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #12

                        @mr-burns

                        apt policy libopenzwave*

                        Ausgaben zeigen...

                        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

                        Mr. BurnsM 1 Antwort Letzte Antwort
                        0
                        • Thomas BraunT Thomas Braun

                          @mr-burns

                          apt policy libopenzwave*

                          Ausgaben zeigen...

                          Mr. BurnsM Offline
                          Mr. BurnsM Offline
                          Mr. Burns
                          schrieb am zuletzt editiert von
                          #13

                          @thomas-braun

                          apt policy libopenzwave*
                          libopenzwave1.6-dev:
                            Installiert:           1.6.1545+ds-2
                            Installationskandidat: 1.6.1545+ds-2
                            Versionstabelle:
                           *** 1.6.1545+ds-2 500
                                  500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                  100 /var/lib/dpkg/status
                          libopenzwave1.5:
                            Installiert:           (keine)
                            Installationskandidat: (keine)
                            Versionstabelle:
                               1.5+ds-6 -1
                                  100 /var/lib/dpkg/status
                          libopenzwave1.6:
                            Installiert:           1.6.1545+ds-2
                            Installationskandidat: 1.6.1545+ds-2
                            Versionstabelle:
                           *** 1.6.1545+ds-2 500
                                  500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                  100 /var/lib/dpkg/status
                          libopenzwave-doc:
                            Installiert:           (keine)
                            Installationskandidat: 1.6.1545+ds-2
                            Versionstabelle:
                               1.6.1545+ds-2 500
                                  500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                          
                          Thomas BraunT 1 Antwort Letzte Antwort
                          0
                          • Mr. BurnsM Mr. Burns

                            @thomas-braun

                            apt policy libopenzwave*
                            libopenzwave1.6-dev:
                              Installiert:           1.6.1545+ds-2
                              Installationskandidat: 1.6.1545+ds-2
                              Versionstabelle:
                             *** 1.6.1545+ds-2 500
                                    500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                    100 /var/lib/dpkg/status
                            libopenzwave1.5:
                              Installiert:           (keine)
                              Installationskandidat: (keine)
                              Versionstabelle:
                                 1.5+ds-6 -1
                                    100 /var/lib/dpkg/status
                            libopenzwave1.6:
                              Installiert:           1.6.1545+ds-2
                              Installationskandidat: 1.6.1545+ds-2
                              Versionstabelle:
                             *** 1.6.1545+ds-2 500
                                    500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                    100 /var/lib/dpkg/status
                            libopenzwave-doc:
                              Installiert:           (keine)
                              Installationskandidat: 1.6.1545+ds-2
                              Versionstabelle:
                                 1.6.1545+ds-2 500
                                    500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                            
                            Thomas BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            schrieb am zuletzt editiert von
                            #14

                            @mr-burns

                            libopenzwave sollte passen. Die libpcap0.8-dev ist auch installiert?

                            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

                            Mr. BurnsM 1 Antwort Letzte Antwort
                            0
                            • Mr. BurnsM Mr. Burns

                              @thomas-braun

                              Ich hab mal die v1.6 installiert. Leider kann der js-controller immer noch nicht aktualisiert werden...

                              iobroker upgrade self --debug
                              Update js-controller from @4.0.21 to @4.0.23
                              Stopped Objects DB
                              Stopped States DB
                              NPM version: 8.19.2
                              Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                              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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                              npm ERR! code 1
                              npm ERR! path /opt/iobroker/node_modules/pcap
                              npm ERR! command failed
                              npm ERR! command sh -c -- node-gyp rebuild
                              npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird betreten
                              npm ERR!   CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
                              npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/pcap/build“ wird verlassen
                              npm ERR! gyp info it worked if it ends with ok
                              npm ERR! gyp info using node-gyp@9.1.0
                              npm ERR! gyp info using node@16.17.1 | linux | arm
                              npm ERR! gyp info find Python using Python version 3.9.2 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   '/usr/lib/node_modules/npm/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/pcap/build/config.gypi',
                              npm ERR! gyp info spawn args   '-I',
                              npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
                              npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                              npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(target_arch)/node.lib',
                              npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/pcap',
                              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! ../pcap_binding.cc:2:10: fatal error: pcap/pcap.h: Datei oder Verzeichnis nicht gefunden
                              npm ERR!     2 | #include <pcap/pcap.h>
                              npm ERR!       |          ^~~~~~~~~~~~~
                              npm ERR! compilation terminated.
                              npm ERR! make: *** [pcap_binding.target.mk:112: Release/obj.target/pcap_binding/pcap_binding.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
                              npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
                              npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                              npm ERR! gyp ERR! System Linux 5.15.61-v7l+
                              npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                              npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/pcap
                              npm ERR! gyp ERR! node -v v16.17.1
                              npm ERR! gyp ERR! node-gyp -v v9.1.0
                              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-09-30T15_32_29_851Z-debug-0.log
                              ``
                              [/s]
                              DJMarc75D Offline
                              DJMarc75D Offline
                              DJMarc75
                              schrieb am zuletzt editiert von
                              #15

                              @mr-burns sagte in js-controller lässt sich nicht updaten...:

                              NPM version: 8.19.2

                              Seh ich das richtig dass da immer noch was krumm ist ?

                              Lehrling seit 1975 !!!
                              Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
                              https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

                              Mr. BurnsM Thomas BraunT 2 Antworten Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @mr-burns

                                libopenzwave sollte passen. Die libpcap0.8-dev ist auch installiert?

                                Mr. BurnsM Offline
                                Mr. BurnsM Offline
                                Mr. Burns
                                schrieb am zuletzt editiert von
                                #16

                                @thomas-braun ja, ist installiert. versuche gerade noch einmal...

                                1 Antwort Letzte Antwort
                                0
                                • DJMarc75D DJMarc75

                                  @mr-burns sagte in js-controller lässt sich nicht updaten...:

                                  NPM version: 8.19.2

                                  Seh ich das richtig dass da immer noch was krumm ist ?

                                  Mr. BurnsM Offline
                                  Mr. BurnsM Offline
                                  Mr. Burns
                                  schrieb am zuletzt editiert von Mr. Burns
                                  #17

                                  @djmarc75 das kann ich nicht beantworten. Aber im iobroker gehen 2 wichtige adapter nicht:#
                                  s7 und javascript...aber vielleicht mit dem update welches ich gerade durchgeführt habe.

                                  1 Antwort Letzte Antwort
                                  0
                                  • DJMarc75D DJMarc75

                                    @mr-burns sagte in js-controller lässt sich nicht updaten...:

                                    NPM version: 8.19.2

                                    Seh ich das richtig dass da immer noch was krumm ist ?

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

                                    @djmarc75 sagte in js-controller lässt sich nicht updaten...:

                                    Seh ich das richtig dass da immer noch was krumm ist ?

                                    Siehst du richtig.

                                    @Mr-Burns

                                    sudo ln -s /usr/bin/node /usr/bin/nodejs
                                    uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                    

                                    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

                                    Mr. BurnsM 1 Antwort Letzte Antwort
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @djmarc75 sagte in js-controller lässt sich nicht updaten...:

                                      Seh ich das richtig dass da immer noch was krumm ist ?

                                      Siehst du richtig.

                                      @Mr-Burns

                                      sudo ln -s /usr/bin/node /usr/bin/nodejs
                                      uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                      
                                      Mr. BurnsM Offline
                                      Mr. BurnsM Offline
                                      Mr. Burns
                                      schrieb am zuletzt editiert von Mr. Burns
                                      #19

                                      @thomas-braun

                                      Das Ergebnis des update Versuchs vor dem neuen update:

                                      iobroker upgrade self --debug
                                      Update js-controller from @4.0.21 to @4.0.23
                                      Stopped Objects DB
                                      Stopped States DB
                                      NPM version: 8.19.2
                                      Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                                      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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                      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: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird betreten
                                      npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
                                      npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird verlassen
                                      npm ERR! gyp info it worked if it ends with ok
                                      npm ERR! gyp info using node-gyp@9.1.0
                                      npm ERR! gyp info using node@16.17.1 | linux | arm
                                      npm ERR! gyp info find Python using Python version 3.9.2 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   '/usr/lib/node_modules/npm/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   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
                                      npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                                      npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(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.17.1/include/node/v8.h:30,
                                      npm ERR!                  from ../src/openzwave.hpp:27,
                                      npm ERR!                  from ../src/callbacks.cc:18:
                                      npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
                                      npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                      npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                      npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:50: error: template argument 2 is invalid
                                      npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                      npm ERR!       |                                                  ^
                                      npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared
                                      npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                      npm ERR!       |                                                               ^~~~~~~
                                      npm ERR! make: *** [openzwave_shared.target.mk:148: Release/obj.target/openzwave_shared/src/callbacks.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
                                      npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
                                      npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                                      npm ERR! gyp ERR! System Linux 5.15.61-v7l+
                                      npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                      npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
                                      npm ERR! gyp ERR! node -v v16.17.1
                                      npm ERR! gyp ERR! node-gyp -v v9.1.0
                                      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-09-30T16_58_37_038Z-debug-0.log
                                      

                                      Teil 2:

                                      uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                      armv7l
                                      /usr/bin/nodejs
                                      /usr/bin/node
                                      /usr/bin/npm
                                      v16.17.1
                                      v16.17.1
                                      8.19.2
                                      4.0.21
                                      pi
                                      pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
                                      /home
                                      OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
                                      OK:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                                                               
                                      OK:3 https://repos.influxdata.com/debian bullseye InRelease                                                                                                                 
                                      OK:4 https://phoscon.de/apt/deconz bullseye InRelease                                                                   
                                      OK:5 https://deb.nodesource.com/node_16.x bullseye InRelease                                    
                                      Paketlisten werden gelesen… Fertig
                                      Abhängigkeitsbaum wird aufgebaut… Fertig
                                      Statusinformationen werden eingelesen… Fertig
                                      Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                                      nodejs:
                                       Installiert:           16.17.1-deb-1nodesource1
                                       Installationskandidat: 16.17.1-deb-1nodesource1
                                       Versionstabelle:
                                      *** 16.17.1-deb-1nodesource1 500
                                             500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
                                             100 /var/lib/dpkg/status
                                          12.22.12~dfsg-1~deb11u1 500
                                             500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                      ``
                                      [/s]
                                      Thomas BraunT 3 Antworten Letzte Antwort
                                      0
                                      • Mr. BurnsM Mr. Burns

                                        @thomas-braun

                                        Das Ergebnis des update Versuchs vor dem neuen update:

                                        iobroker upgrade self --debug
                                        Update js-controller from @4.0.21 to @4.0.23
                                        Stopped Objects DB
                                        Stopped States DB
                                        NPM version: 8.19.2
                                        Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                                        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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                        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: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird betreten
                                        npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
                                        npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird verlassen
                                        npm ERR! gyp info it worked if it ends with ok
                                        npm ERR! gyp info using node-gyp@9.1.0
                                        npm ERR! gyp info using node@16.17.1 | linux | arm
                                        npm ERR! gyp info find Python using Python version 3.9.2 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   '/usr/lib/node_modules/npm/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   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
                                        npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                                        npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(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.17.1/include/node/v8.h:30,
                                        npm ERR!                  from ../src/openzwave.hpp:27,
                                        npm ERR!                  from ../src/callbacks.cc:18:
                                        npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
                                        npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                        npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                        npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:50: error: template argument 2 is invalid
                                        npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                        npm ERR!       |                                                  ^
                                        npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared
                                        npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                        npm ERR!       |                                                               ^~~~~~~
                                        npm ERR! make: *** [openzwave_shared.target.mk:148: Release/obj.target/openzwave_shared/src/callbacks.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
                                        npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
                                        npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                                        npm ERR! gyp ERR! System Linux 5.15.61-v7l+
                                        npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                        npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
                                        npm ERR! gyp ERR! node -v v16.17.1
                                        npm ERR! gyp ERR! node-gyp -v v9.1.0
                                        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-09-30T16_58_37_038Z-debug-0.log
                                        

                                        Teil 2:

                                        uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                        armv7l
                                        /usr/bin/nodejs
                                        /usr/bin/node
                                        /usr/bin/npm
                                        v16.17.1
                                        v16.17.1
                                        8.19.2
                                        4.0.21
                                        pi
                                        pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
                                        /home
                                        OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
                                        OK:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                                                               
                                        OK:3 https://repos.influxdata.com/debian bullseye InRelease                                                                                                                 
                                        OK:4 https://phoscon.de/apt/deconz bullseye InRelease                                                                   
                                        OK:5 https://deb.nodesource.com/node_16.x bullseye InRelease                                    
                                        Paketlisten werden gelesen… Fertig
                                        Abhängigkeitsbaum wird aufgebaut… Fertig
                                        Statusinformationen werden eingelesen… Fertig
                                        Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                                        nodejs:
                                         Installiert:           16.17.1-deb-1nodesource1
                                         Installationskandidat: 16.17.1-deb-1nodesource1
                                         Versionstabelle:
                                        *** 16.17.1-deb-1nodesource1 500
                                               500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
                                               100 /var/lib/dpkg/status
                                            12.22.12~dfsg-1~deb11u1 500
                                               500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                        ``
                                        [/s]
                                        Thomas BraunT Online
                                        Thomas BraunT Online
                                        Thomas Braun
                                        Most Active
                                        schrieb am zuletzt editiert von
                                        #20

                                        @mr-burns

                                        Interessanter wäre:

                                        sudo ln -s /usr/bin/node /usr/bin/nodejs
                                        uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                        

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

                                        1 Antwort Letzte Antwort
                                        0
                                        • Mr. BurnsM Mr. Burns

                                          @thomas-braun

                                          Das Ergebnis des update Versuchs vor dem neuen update:

                                          iobroker upgrade self --debug
                                          Update js-controller from @4.0.21 to @4.0.23
                                          Stopped Objects DB
                                          Stopped States DB
                                          NPM version: 8.19.2
                                          Installing iobroker.js-controller@4.0.23... (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 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 appdirectory@0.1.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
                                          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 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 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 request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                          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: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird betreten
                                          npm ERR!   CXX(target) Release/obj.target/openzwave_shared/src/callbacks.o
                                          npm ERR! make: Verzeichnis „/opt/iobroker/node_modules/openzwave-shared/build“ wird verlassen
                                          npm ERR! gyp info it worked if it ends with ok
                                          npm ERR! gyp info using node-gyp@9.1.0
                                          npm ERR! gyp info using node@16.17.1 | linux | arm
                                          npm ERR! gyp info find Python using Python version 3.9.2 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   '/usr/lib/node_modules/npm/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   '/usr/lib/node_modules/npm/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.17.1/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.17.1',
                                          npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                                          npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/16.17.1/<(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.17.1/include/node/v8.h:30,
                                          npm ERR!                  from ../src/openzwave.hpp:27,
                                          npm ERR!                  from ../src/callbacks.cc:18:
                                          npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h: In function ‘void v8::internal::PerformCastCheck(T*)’:
                                          npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                          npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:38: error: ‘remove_cv_t’ is not a member of ‘std’; did you mean ‘remove_cv’?
                                          npm ERR!   492 |             !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.17.1/include/node/v8-internal.h:492:50: error: template argument 2 is invalid
                                          npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                          npm ERR!       |                                                  ^
                                          npm ERR! /home/iobroker/.cache/node-gyp/16.17.1/include/node/v8-internal.h:492:63: error: ‘::Perform’ has not been declared
                                          npm ERR!   492 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
                                          npm ERR!       |                                                               ^~~~~~~
                                          npm ERR! make: *** [openzwave_shared.target.mk:148: Release/obj.target/openzwave_shared/src/callbacks.o] Fehler 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 (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
                                          npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
                                          npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
                                          npm ERR! gyp ERR! System Linux 5.15.61-v7l+
                                          npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                          npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/openzwave-shared
                                          npm ERR! gyp ERR! node -v v16.17.1
                                          npm ERR! gyp ERR! node-gyp -v v9.1.0
                                          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-09-30T16_58_37_038Z-debug-0.log
                                          

                                          Teil 2:

                                          uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                                          armv7l
                                          /usr/bin/nodejs
                                          /usr/bin/node
                                          /usr/bin/npm
                                          v16.17.1
                                          v16.17.1
                                          8.19.2
                                          4.0.21
                                          pi
                                          pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
                                          /home
                                          OK:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
                                          OK:2 http://archive.raspberrypi.org/debian bullseye InRelease                                                                                                               
                                          OK:3 https://repos.influxdata.com/debian bullseye InRelease                                                                                                                 
                                          OK:4 https://phoscon.de/apt/deconz bullseye InRelease                                                                   
                                          OK:5 https://deb.nodesource.com/node_16.x bullseye InRelease                                    
                                          Paketlisten werden gelesen… Fertig
                                          Abhängigkeitsbaum wird aufgebaut… Fertig
                                          Statusinformationen werden eingelesen… Fertig
                                          Aktualisierung für 4 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                                          nodejs:
                                           Installiert:           16.17.1-deb-1nodesource1
                                           Installationskandidat: 16.17.1-deb-1nodesource1
                                           Versionstabelle:
                                          *** 16.17.1-deb-1nodesource1 500
                                                 500 https://deb.nodesource.com/node_16.x bullseye/main armhf Packages
                                                 100 /var/lib/dpkg/status
                                              12.22.12~dfsg-1~deb11u1 500
                                                 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages
                                          ``
                                          [/s]
                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #21

                                          @mr-burns sagte in js-controller lässt sich nicht updaten...:

                                          Lass die Finger von individuellen Updates von npm. Egal ob das irgendwo empfohlen wird.

                                          iobroker stop
                                          sudo apt update
                                          sudo apt full-upgrade
                                          sudo apt install --reinstall nodejs
                                          cd /opt/iobroker 
                                          sudo -H -u iobroker npm cache clear --force
                                          sudo reboot
                                          

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

                                          1 Antwort Letzte Antwort
                                          0

                                          Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                          Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                          Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                          Registrieren Anmelden
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          350

                                          Online

                                          32.9k

                                          Benutzer

                                          83.0k

                                          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