Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Kann keine Adapter aktualisieren

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Kann keine Adapter aktualisieren

    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      Frank_y @Thomas Braun last edited by

      @thomas-braun sagte in Kann keine Adapter aktualisieren:

      sudo -H -u iobroker npm install iobroker.js-controller

      jetzt werden wieder Verzeichnisse angemeckert:

      npm ERR! code ENOTEMPTY
      npm ERR! syscall rename
      npm ERR! path /opt/iobroker/node_modules/aws4
      npm ERR! dest /opt/iobroker/node_modules/.aws4-3BmHzpIi
      npm ERR! errno -39
      npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/aws4' -> '/opt/iobroker/node_modules/.aws4-3BmHzpIi'
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /home/iobroker/.npm/_logs/2022-07-22T14_18_20_594Z-debug-0.log
      
      

      ich lösche mal weiter: rm -rf /opt/iobroker/node_modules/.aws4-3BmHzpIi

      F 1 Reply Last reply Reply Quote 0
      • F
        Frank_y @Frank_y last edited by

        @frank_y
        es sind wieder mehrere Verzeichnisse....bisher 6...sehr mühsam
        Woran liegt das denn. Es lief ja alles?

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

          @frank_y sagte in Kann keine Adapter aktualisieren:

          Woran liegt das denn. Es lief ja alles?

          Ich weiß es nicht. Wenn man sich im Netz umschaut passiert das überwiegend bei Aktionen im npm tree die mit root-Rechten und/oder global durchgeführt wurden. Kann auch geraume Zeit her sein, da schlummern dann halt immer Zeitbomben.

          Als ich auf npm8 gewechselt bin hatte ich solche Probleme jedenfalls nicht.

          F 1 Reply Last reply Reply Quote 0
          • F
            Frank_y @Thomas Braun last edited by

            @thomas-braun

            wenn ich den iobroker neu/frisch aufsetzte und dann per Backitup wiederherstelle, sollten die Probleme auch weg sein, oder?

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

              @frank_y

              Ich weiß es nicht genau. Die package-lock wird soweit ich weiß mit gesichert.

              grrfield F 2 Replies Last reply Reply Quote 0
              • grrfield
                grrfield @Thomas Braun last edited by

                @thomas-braun
                Ich habe bei mir mit

                cd /opt/iobroker/node_modules
                mkdir bak
                mv ./.* bak
                mv bak/.bin .
                mv  @*/.??* bak
                

                alle beanstandeten Verzeichnisse entfernt. Danach lief das Update los, es kamen einige "normale" Updatemeldungen und dann eine Unmenge an Fehlermeldungen; größtenteils npm ERR! Ich habe mal das Logfile angehängt; es lohnt sich aber nicht, das weiter zu verfolgen: putty.log Da muß wohl noch etwas anderes kaputt sein 😞 Ich werde das System neu aufsetzen und dann den letzten Backup einspielen.

                Trotzdem herzlichen Dank für Deine Hilfe!!!

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • F
                  Frank_y @Thomas Braun last edited by Frank_y

                  @thomas-braun
                  das Löschen kann nicht der richtige Weg sein:

                  Habe über

                  find /opt/iobroker/node_modules/ -name .*-* -print
                  

                  alle Dateien mit kryptischen Endungen herausgesucht und gelöscht (bestimmt 100 Stück)

                  sudo -H -u iobroker npm install iobroker.js-controller
                  

                  lief dann auch durch. Es wurden aber sehr viele Warnungen zu veralteten Versionen angezeigt.
                  Ich habe dann ein

                   sudo apt update && sudo apt upgrade
                  

                  durchgeführt. Danach sind alle gerade gelöschten Dateien/Ordner wieder da!?

                  Erneutes

                  sudo -H -u iobroker npm install iobroker.js-controller
                  

                  liefert die erste Fehlermeldung aus dem Versuch des Historie-Updates:

                  @iobrokerVM:/opt/iobroker$ sudo -H -u iobroker npm install iobroker.js-controller
                  npm ERR! code ENOTEMPTY
                  npm ERR! syscall rename
                  npm ERR! path /opt/iobroker/node_modules/abbrev
                  npm ERR! dest /opt/iobroker/node_modules/.abbrev-5eNud0FY
                  npm ERR! errno -39
                  npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abbrev' -> '/opt/iobroker/node_modules/.abbrev-5eNud0FY'
                  
                  npm ERR! A complete log of this run can be found in:
                  npm ERR!     /home/iobroker/.npm/_logs/2022-07-22T15_45_08_712Z-debug-0.log
                  
                  

                  Ich bin etwas ratlos?

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

                    @grrfield

                    Bei dir scheitert der Versuch sharp bzw. die libvips zu bauen.
                    Das ist bekanntermaßen etwas tricky.

                    npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
                    npm ERR! make: Entering directory '/opt/iobroker/node_modules/sharp/build'
                    
                    grrfield 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Frank_y last edited by

                      @frank_y sagte in Kann keine Adapter aktualisieren:

                      das Löschen kann nicht der richtige Weg sein:

                      Bei anderen Fällen war es das.

                      Dann mach die Roßkur à la @crunchip

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

                        @thomas-braun Geht das wieder, wenn ich nur ioBroker neu installiere?

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • grrfield
                          grrfield last edited by

                          Könnte ich das mit https://forum.iobroker.net/topic/32147/update-js-controller-und-node-js/74?_=1658508688254 beheben?

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

                            @grrfield sagte in Kann keine Adapter aktualisieren:

                            Geht das wieder, wenn ich nur ioBroker neu installiere?

                            sharp/libvips? Nee, das hat mit dem ioBroker nicht direkt zu tun. Da fehlen vielleicht devel-Pakete für die ganzen anderen libs die damit zusammenhängen. Ich meine aber, die würden mittlerweile alle 'auf Verdacht' schon vom

                            iobroker fix
                            

                            auf das System gespült. Hatten in der Vergangenheit zu viel Ärger damit, aber ich hab da schon länger nicht mehr aus der Ecke gesehen. Bis du mit deinem log ankommst... 🙂

                            1 Reply Last reply Reply Quote 0
                            • Negalein
                              Negalein Global Moderator @haselchen last edited by

                              @haselchen sagte in Kann keine Adapter aktualisieren:

                              Bitte zusammenführen

                              erledigt 🙂

                              1 Reply Last reply Reply Quote 1
                              • F
                                Fatmax last edited by Fatmax

                                Vielleicht ist das noch zur Lösungsfindung hilfreich:
                                Bei mir zumindest funktionieren die Adapterupdates im Admin mit dem Button wo alle Adapter mit Updates auf einmal aktualisiert werden können.
                                Nur bei den einzelnen Updates gibt es Probleme mit der Versionsüberprüfung.

                                ec36ddf0-da8a-4fc6-a64e-e31b30778c67-image.png

                                1 Reply Last reply Reply Quote 0
                                • grrfield
                                  grrfield last edited by

                                  Ich möchte nur nochmal Rückmeldung geben, falls andere das auch haben: Mein Problem war wohl ein defektes Dateisystem auf der eMMC in Folge eines von mir vor einiger Zeit verursachten Stromausfalls. Es gingen dann auch andre Standard-LINUX-Befehle nicht mehr. Nach Neuaufsetzen eines Linux-Images, Installation von ioBroker und Einspielen eines Backups läuft alles wieder.
                                  @thomas-braun Nochmals vielen Dank für die Hilfe!

                                  1 Reply Last reply Reply Quote 0
                                  • F
                                    Fatmax last edited by

                                    Bei mir hat sich das Thema von selbst erledigt.
                                    Nachdem ich einige male Updates mit der Variante aus meinem letzten Post eingespielt hatte, unter anderem auch mehrere Updates vom Admin-Adapter, ist der Fehler nun weg und die Versionsprüfung bei den einzelnen Adaptern funktioniert wieder einwandfrei.
                                    Auch ein Update einzelner Adapter ist nun wieder möglich.

                                    Danke jedenfalls bis dahin für die Hilfe.

                                    1 Reply Last reply Reply Quote 0
                                    • K K 2
                                      K K 2 last edited by

                                      Meine Adapter lassen sich nicht mehr aktualisieren.

                                      pi@nas:~ $ iobroker update
                                      Used repository: stable
                                      Adapter    "admin"        : 6.10.1   , installed 6.3.5  [Updatable]
                                      Adapter    "backitup"     : 2.8.1    , installed 2.6.19 [Updatable]
                                      Adapter    "ble"          : 0.13.4   , installed 0.13.0 [Updatable]
                                      Adapter    "daswetter"    : 3.1.10   , installed 3.1.8  [Updatable]
                                      Adapter    "discovery"    : 3.1.0    , installed 3.0.5  [Updatable]
                                      Adapter    "info"         : 2.0.0    , installed 1.9.19 [Updatable]
                                      Adapter    "javascript"   : 7.1.4    , installed 6.1.4  [Updatable]
                                      Controller "js-controller": 5.0.12   , installed 4.0.24 [Updatable]
                                      Adapter    "lgtv"         : 2.1.1    , installed 1.1.10 [Updatable]
                                      Adapter    "octoprint"    : 4.0.0    , installed 4.0.0
                                      Adapter    "ring"         : 3.2.2    , installed 3.4.1
                                      Adapter    "simple-api"   : 2.7.2    , installed 2.7.0  [Updatable]
                                      Adapter    "socketio"     : 6.5.5    , installed 4.2.0  [Updatable]
                                      Adapter    "telegram"     : 1.16.0   , installed 1.15.6 [Updatable]
                                      Adapter    "terminal"     : 1.0.0    , installed 1.0.0
                                      Adapter    "web"          : 6.1.2    , installed 4.3.0  [Updatable]
                                      Adapter    "ws"           : 2.5.5    , installed 1.3.0  [Updatable]
                                      Adapter    "yahka"        : 1.0.3    , installed 0.17.0 [Updatable]
                                      Adapter    "zigbee"       : 1.8.23   , installed 1.8.23
                                      

                                      Update/Upgrade:

                                      pi@nas:~ $ iobroker upgrade daswetter --debug
                                      
                                      This upgrade of "daswetter" will at least introduce the following changes:
                                      ==========================================================================
                                      -> 3.1.10:
                                      dependencies updated
                                      ==========================================================================
                                      
                                      Would you like to upgrade daswetter from @3.1.8 to @3.1.10 now? [(y)es, (n)o]: y
                                      Update daswetter from @3.1.8 to @3.1.10
                                      host.nas Adapter "system.adapter.daswetter.0" is stopped.
                                      NPM version: 9.8.1
                                      Installing iobroker.daswetter@3.1.10... (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 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! git dep preparation failed
                                      npm ERR! command /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/iobroker/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
                                      npm ERR! npm WARN using --force Recommended protections disabled.
                                      npm ERR! npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
                                      npm ERR! npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
                                      npm ERR! npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
                                      npm ERR! npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
                                      npm ERR! npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
                                      npm ERR! npm ERR! code 1
                                      npm ERR! npm ERR! path /home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp
                                      npm ERR! npm ERR! command failed
                                      npm ERR! npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
                                      npm ERR! npm ERR! sharp: Using cached /home/iobroker/.npm/_libvips/libvips-8.14.5-linux-armv7.tar.br
                                      npm ERR! npm ERR! sharp: Integrity check passed for linux-armv7
                                      npm ERR! npm ERR! make: Verzeichnis �/home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp/build� wird betreten
                                      npm ERR! npm ERR!   CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
                                      npm ERR! npm ERR! rm -f Release/obj.target/../node-addon-api/nothing.a Release/obj.target/../node-addon-api/nothing.a.ar-file-list; mkdir -p `dirname Release/obj.target/../node-addon-api/nothing.a`
                                      npm ERR! npm ERR! ar crs Release/obj.target/../node-addon-api/nothing.a @Release/obj.target/../node-addon-api/nothing.a.ar-file-list
                                      npm ERR! npm ERR!   COPY Release/nothing.a
                                      npm ERR! npm ERR!   TOUCH Release/obj.target/libvips-cpp.stamp
                                      npm ERR! npm ERR!   CXX(target) Release/obj.target/sharp-linux-armv7/src/common.o
                                      npm ERR! npm ERR! make: Verzeichnis �/home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp/build� wird verlassen
                                      npm ERR! npm ERR! prebuild-install warn install No prebuilt binaries found (target=7 runtime=napi arch=arm libc= platform=linux)
                                      npm ERR! npm ERR! gyp info it worked if it ends with ok
                                      npm ERR! npm ERR! gyp info using node-gyp@9.4.0
                                      npm ERR! npm ERR! gyp info using node@18.18.2 | linux | arm
                                      npm ERR! npm ERR! gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"
                                      npm ERR! npm ERR! gyp info spawn /usr/bin/python3
                                      npm ERR! npm ERR! gyp info spawn args [
                                      npm ERR! npm ERR! gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
                                      npm ERR! npm ERR! gyp info spawn args   'binding.gyp',
                                      npm ERR! npm ERR! gyp info spawn args   '-f',
                                      npm ERR! npm ERR! gyp info spawn args   'make',
                                      npm ERR! npm ERR! gyp info spawn args   '-I',
                                      npm ERR! npm ERR! gyp info spawn args   '/home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp/build/config.gypi',
                                      npm ERR! npm ERR! gyp info spawn args   '-I',
                                      npm ERR! npm ERR! gyp info spawn args   '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
                                      npm ERR! npm ERR! gyp info spawn args   '-I',
                                      npm ERR! npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.18.2/include/node/common.gypi',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dvisibility=default',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.18.2',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.18.2/<(target_arch)/node.lib',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp',
                                      npm ERR! npm ERR! gyp info spawn args   '-Dnode_engine=v8',
                                      npm ERR! npm ERR! gyp info spawn args   '--depth=.',
                                      npm ERR! npm ERR! gyp info spawn args   '--no-parallel',
                                      npm ERR! npm ERR! gyp info spawn args   '--generator-output',
                                      npm ERR! npm ERR! gyp info spawn args   'build',
                                      npm ERR! npm ERR! gyp info spawn args   '-Goutput_dir=.'
                                      npm ERR! npm ERR! gyp info spawn args ]
                                      npm ERR! npm ERR! gyp info spawn make
                                      npm ERR! npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                                      npm ERR! npm ERR! g++: error: unrecognized command line option '-std=gnu++17'
                                      npm ERR! npm ERR! make: *** [sharp-linux-armv7.target.mk:142: Release/obj.target/sharp-linux-armv7/src/common.o] Fehler 1
                                      npm ERR! npm ERR! gyp ERR! build error 
                                      npm ERR! npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
                                      npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
                                      npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
                                      npm ERR! npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
                                      npm ERR! npm ERR! gyp ERR! System Linux 5.10.103-v7l+
                                      npm ERR! npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                      npm ERR! npm ERR! gyp ERR! cwd /home/iobroker/.npm/_cacache/tmp/git-cloneUOuQIc/node_modules/sharp
                                      npm ERR! npm ERR! gyp ERR! node -v v18.18.2
                                      npm ERR! npm ERR! gyp ERR! node-gyp -v v9.4.0
                                      npm ERR! npm ERR! gyp ERR! not ok
                                      npm ERR! 
                                      npm ERR! npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-10-19T06_39_00_484Z-debug-0.log
                                      
                                      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-10-19T06_36_08_244Z-debug-0.log
                                      Update "system.adapter.daswetter.0"
                                      

                                      Unabhängig vom Adapter sieht es eigentlich immer wie gezeigt aus. Hat jemand eine Idee wie ich das Ding retten kann?

                                      mikeal created this issue in request/request

                                      open Request’s Past, Present and Future #3142

                                      Qix- created this issue in visionmedia/debug

                                      closed ReDos Vulnerability Regression Visibility Notice #797

                                      Qix- created this issue in visionmedia/debug

                                      closed ReDos Vulnerability Regression Visibility Notice #797

                                      Qix- created this issue in visionmedia/debug

                                      closed ReDos Vulnerability Regression Visibility Notice #797

                                      mikeal created this issue in request/request

                                      open Request’s Past, Present and Future #3142

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

                                        @k-k-2 sagte in Kann keine Adapter aktualisieren:

                                        usr/local/bin/node

                                        Nodejs falsch installiert. Mit

                                        iob nodejs-update
                                        

                                        gerade biegen.

                                        https://forum.iobroker.net/topic/69068/neuer-befehl-iob-nodejs-update

                                        K K 2 1 Reply Last reply Reply Quote 0
                                        • K K 2
                                          K K 2 @Thomas Braun last edited by

                                          @thomas-braun danke für die schnelle Antwort. ich habe es ausgeführt, aber leider ohne Erfolg

                                          iob diag

                                          ======================= SUMMARY =======================
                                                                  v.2023-10-10
                                          
                                          
                                             Static hostname: nas
                                                   Icon name: computer
                                            Operating System: Raspbian GNU/Linux 10 (buster)
                                                      Kernel: Linux 5.10.103-v7l+
                                                Architecture: arm
                                          
                                          Installation:           native
                                          Kernel:                 armv7l
                                          Userland:               armhf
                                          Timezone:               Europe/Berlin (CEST, +0200)
                                          User-ID:                1000
                                          X-Server:               true
                                          Boot Target:            graphical.target
                                          
                                          Pending OS-Updates:     0
                                          Pending iob updates:    15
                                          
                                          Nodejs-Installation:    /usr/bin/nodejs         v18.18.2
                                                                  /usr/bin/node           v18.18.2
                                                                  /usr/bin/npm            9.8.1
                                                                  /usr/bin/npx            9.8.1
                                                                  /usr/bin/corepack       0.19.0
                                          
                                          Recommended versions are nodejs  and npm 8.19.4
                                          Your nodejs installation is correct
                                          
                                          MEMORY: 
                                                        total        used        free      shared  buff/cache   available
                                          Mem:           3.8G        897M        1.7G         31M        1.3G        2.7G
                                          Swap:           99M        9.0M         90M
                                          Total:         3.9G        906M        1.8G
                                          
                                          Active iob-Instances:   14
                                          Active repo(s): stable
                                          
                                          ioBroker Core:          js-controller           4.0.24
                                                                  admin                   6.3.5
                                          
                                          ioBroker Status:        iobroker is running on this host.
                                          
                                          
                                          Objects type: jsonl
                                          States  type: jsonl
                                          
                                          Status admin and web instance:
                                          + system.adapter.admin.0                  : admin                 : nas                                      -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
                                          + system.adapter.web.0                    : web                   : nas                                      -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
                                          
                                          Objects:                5484
                                          States:                 4978
                                          
                                          Size of iob-Database:
                                          
                                          7.9M    /opt/iobroker/iobroker-data/objects.jsonl
                                          5.6M    /opt/iobroker/iobroker-data/objects.json.migrated
                                          5.6M    /opt/iobroker/iobroker-data/objects.json.bak.migrated
                                          7.5M    /opt/iobroker/iobroker-data/states.jsonl
                                          1.2M    /opt/iobroker/iobroker-data/states.json.migrated
                                          1.2M    /opt/iobroker/iobroker-data/states.json.bak.migrated
                                          
                                          
                                          
                                          =================== END OF SUMMARY ====================
                                          
                                          pi@nas:~ $ iobroker upgrade ble --debug
                                          
                                          This upgrade of "ble" will introduce the following changes:
                                          ==========================================================================
                                          -> 0.13.4:
                                          Very experimental support for scanning on a remote host (#793)
                                          Another attempt at updating `noble`. Hopefully this version works now...
                                          
                                          -> 0.13.3:
                                          Updated `noble` again. This should fix the automatic rebuild after Node.js upgrades and the previous performance issues.
                                          
                                          -> 0.13.2:
                                          Downgraded the `noble` dependency again because of performance issues
                                          
                                          -> 0.13.1:
                                          Updated the `noble` dependency. This should fix the automatic rebuild after Node.js upgrades.
                                          ==========================================================================
                                          
                                          Would you like to upgrade ble from @0.13.0 to @0.13.4 now? [(y)es, (n)o]: y
                                          Update ble from @0.13.0 to @0.13.4
                                          NPM version: 9.8.1
                                          Installing iobroker.ble@0.13.4... (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 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! git dep preparation failed
                                          npm ERR! command /usr/bin/node /usr/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/home/iobroker/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run
                                          npm ERR! npm WARN using --force Recommended protections disabled.
                                          npm ERR! npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
                                          npm ERR! npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
                                          npm ERR! npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
                                          npm ERR! npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
                                          npm ERR! npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
                                          npm ERR! npm ERR! code 1
                                          npm ERR! npm ERR! path /home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp
                                          npm ERR! npm ERR! command failed
                                          npm ERR! npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
                                          npm ERR! npm ERR! sharp: Using cached /home/iobroker/.npm/_libvips/libvips-8.14.5-linux-armv7.tar.br
                                          npm ERR! npm ERR! sharp: Integrity check passed for linux-armv7
                                          npm ERR! npm ERR! make: Verzeichnis �/home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp/build� wird betreten
                                          npm ERR! npm ERR!   CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
                                          npm ERR! npm ERR! rm -f Release/obj.target/../node-addon-api/nothing.a Release/obj.target/../node-addon-api/nothing.a.ar-file-list; mkdir -p `dirname Release/obj.target/../node-addon-api/nothing.a`
                                          npm ERR! npm ERR! ar crs Release/obj.target/../node-addon-api/nothing.a @Release/obj.target/../node-addon-api/nothing.a.ar-file-list
                                          npm ERR! npm ERR!   COPY Release/nothing.a
                                          npm ERR! npm ERR!   TOUCH Release/obj.target/libvips-cpp.stamp
                                          npm ERR! npm ERR!   CXX(target) Release/obj.target/sharp-linux-armv7/src/common.o
                                          npm ERR! npm ERR! make: Verzeichnis �/home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp/build� wird verlassen
                                          npm ERR! npm ERR! prebuild-install warn install No prebuilt binaries found (target=7 runtime=napi arch=arm libc= platform=linux)
                                          npm ERR! npm ERR! gyp info it worked if it ends with ok
                                          npm ERR! npm ERR! gyp info using node-gyp@9.4.0
                                          npm ERR! npm ERR! gyp info using node@18.18.2 | linux | arm
                                          npm ERR! npm ERR! gyp info find Python using Python version 3.7.3 found at "/usr/bin/python3"
                                          npm ERR! npm ERR! gyp info spawn /usr/bin/python3
                                          npm ERR! npm ERR! gyp info spawn args [
                                          npm ERR! npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
                                          npm ERR! npm ERR! gyp info spawn args   'binding.gyp',
                                          npm ERR! npm ERR! gyp info spawn args   '-f',
                                          npm ERR! npm ERR! gyp info spawn args   'make',
                                          npm ERR! npm ERR! gyp info spawn args   '-I',
                                          npm ERR! npm ERR! gyp info spawn args   '/home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp/build/config.gypi',
                                          npm ERR! npm ERR! gyp info spawn args   '-I',
                                          npm ERR! npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
                                          npm ERR! npm ERR! gyp info spawn args   '-I',
                                          npm ERR! npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.18.2/include/node/common.gypi',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dvisibility=default',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.18.2',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.18.2/<(target_arch)/node.lib',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp',
                                          npm ERR! npm ERR! gyp info spawn args   '-Dnode_engine=v8',
                                          npm ERR! npm ERR! gyp info spawn args   '--depth=.',
                                          npm ERR! npm ERR! gyp info spawn args   '--no-parallel',
                                          npm ERR! npm ERR! gyp info spawn args   '--generator-output',
                                          npm ERR! npm ERR! gyp info spawn args   'build',
                                          npm ERR! npm ERR! gyp info spawn args   '-Goutput_dir=.'
                                          npm ERR! npm ERR! gyp info spawn args ]
                                          npm ERR! npm ERR! gyp info spawn make
                                          npm ERR! npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
                                          npm ERR! npm ERR! g++: error: unrecognized command line option '-std=gnu++17'
                                          npm ERR! npm ERR! make: *** [sharp-linux-armv7.target.mk:142: Release/obj.target/sharp-linux-armv7/src/common.o] Fehler 1
                                          npm ERR! npm ERR! gyp ERR! build error 
                                          npm ERR! npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
                                          npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
                                          npm ERR! npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
                                          npm ERR! npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
                                          npm ERR! npm ERR! gyp ERR! System Linux 5.10.103-v7l+
                                          npm ERR! npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                          npm ERR! npm ERR! gyp ERR! cwd /home/iobroker/.npm/_cacache/tmp/git-cloner8Vyuj/node_modules/sharp
                                          npm ERR! npm ERR! gyp ERR! node -v v18.18.2
                                          npm ERR! npm ERR! gyp ERR! node-gyp -v v9.4.0
                                          npm ERR! npm ERR! gyp ERR! not ok
                                          npm ERR! 
                                          npm ERR! npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-10-19T08_50_52_112Z-debug-0.log
                                          
                                          npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-10-19T08_48_23_921Z-debug-0.log
                                          upload [5] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/.eslintrc.js .eslintrc.js application/javascript
                                          upload [4] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/ble.png ble.png image/png
                                          upload [3] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/build/index.js build/index.js application/javascript
                                          upload [2] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/build/index.js.map build/index.js.map application/json
                                          upload [1] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/index_m.html index_m.html text/html
                                          upload [0] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/style.css style.css text/css
                                          
                                          mikeal created this issue in request/request

                                          open Request’s Past, Present and Future #3142

                                          Qix- created this issue in visionmedia/debug

                                          closed ReDos Vulnerability Regression Visibility Notice #797

                                          Qix- created this issue in visionmedia/debug

                                          closed ReDos Vulnerability Regression Visibility Notice #797

                                          Qix- created this issue in visionmedia/debug

                                          closed ReDos Vulnerability Regression Visibility Notice #797

                                          mikeal created this issue in request/request

                                          open Request’s Past, Present and Future #3142

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

                                            @k-k-2

                                            Schalt den Desktop aus.
                                            Und lösche den npm Cache

                                            sudo -H -u iobrokee nom cache clear --force
                                            

                                            [Edit:]
                                            Ach, sehe ich ja gerade erst: buster
                                            Ist tot und muss ersetzt werden. Dann funktioniert vermutlich auch dein gcc wieder.
                                            Nawah tschaindsch ä runnink süstem...
                                            Mal wieder. Leute, haltet die Kisten auf einem aktuellen Stand!!

                                            K K 2 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

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

                                            941
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            14
                                            75
                                            7969
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo