Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      EndofPi last edited by

      Hallo, ich bin der Neue!

      Ich habe versucht den Node-Red Adapter über die Admin-GUI zu aktualisieren und
      leider keine Idee, was hier das Problem lösen könnte.

      • Adaptername: node-red
      • Link zu Adapterrepository: http://download.iobroker.net/sources-dist.json
      • Adapterversion: 4.0.3 -> 5.2.1
      • js-controller Version: 7.0.6
      • Admin Version: 7.4.10
      • Hardwaresystem: Pi3
      • Arbeitsspeicher: 8 GB
      • Festplattenart: SD-Karte
      • Betriebssystem: Raspbian GNU/Linux 11 (bullseye)
      • Nodejs-Version: 20.18.1
      • NPM-Version: 10.8.2
      • Installationsart: Skript
      • Image, Docker genutzt: Nein
      • Ort, Name der Imagedatei: ...
      $ iobroker upgrade node-red@5.2.1 --debug
      Update node-red from @4.0.3 to @5.2.1
      NPM version: 10.8.2Installing iobroker.node-red@5.2.1... (System call)
      > bcrypt@5.1.1 install> node-pre-gyp install --fallback-to-build
      node-pre-gyp info using node-pre-gyp@1.0.11node-pre-gyp info using node@18.20.5 | linux | arm
      node-pre-gyp info check checked for "/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node" (not found)
      node-pre-gyp http GET https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.1.1/bcrypt_lib-v5.1.1-napi-v3-linux-arm-glibc.tar.gz
      node-pre-gyp WARN Pre-built binaries not installable for bcrypt@5.1.1 and node@18.20.5 (node-v108 ABI, glibc) (falling back to source compile with node-gyp) node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.1.1/bcrypt_lib-v5.1.1-napi-v3-linux-arm-glibc.tar.gz 
      gyp info it worked if it ends with okgyp info using node-gyp@10.1.0gyp info using node@18.20.5 | linux | arm
      gyp info ok 
      gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
      gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',gyp info spawn args 'binding.gyp',gyp info spawn args '-f',gyp info spawn args 'make',gyp info spawn args '-I',gyp info spawn args '/opt/iobroker/node_modules/bcrypt/build/config.gypi',gyp info spawn args '-I',gyp info spawn args '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',gyp info spawn args '-I',gyp info spawn args '/home/iobroker/.cache/node-gyp/18.20.5/include/node/common.gypi',gyp info spawn args '-Dlibrary=shared_library',gyp info spawn args '-Dvisibility=default',gyp info spawn args '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.20.5',gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',gyp info spawn args '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.20.5/<(target_arch)/node.lib',gyp info spawn args '-Dmodule_root_dir=/opt/iobroker/node_modules/bcrypt',gyp info spawn args '-Dnode_engine=v8',gyp info spawn args '--depth=.',gyp info spawn args '--no-parallel',gyp info spawn args '--generator-output',gyp info spawn args 'build',gyp info spawn args '-Goutput_dir=.'gyp info spawn args ]
      gyp info ok 
      gyp info it worked if it ends with ok
      gyp info using node-gyp@10.1.0gyp info using node@18.20.5 | linux | arm
      gyp info spawn make
      gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
      make: Verzeichnis „/opt/iobroker/node_modules/bcrypt/build“ wird betreten
      CC(target) Release/obj.target/nothing/../node-addon-api/nothing.o
      make: cc: Keine Berechtigung
      make: *** [../node-addon-api/nothing.target.mk:107: Release/obj.target/nothing/../node-addon-api/nothing.o] Fehler 127make: Verzeichnis „/opt/iobroker/node_modules/bcrypt/build“ wird verlassen
      gyp ERR! build error 
      gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:209:23)
      gyp ERR! System Linux 6.1.21-v8+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node" "--module_name=bcrypt_lib" "--module_path=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3" "--napi_version=9" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"gyp ERR! cwd /opt/iobroker/node_modules/bcryptgyp ERR! node -v v18.20.5gyp ERR! node-gyp -v v10.1.0gyp ERR! not ok 
      node-pre-gyp ERR! build error 
      node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3 --napi_version=9 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/opt/iobroker/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)node-pre-gyp ERR! stack at ChildProcess.emit (node:events:517:28)node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1098:16)node-pre-gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:303:5)
      node-pre-gyp ERR! System Linux 6.1.21-v8+node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/bcryptnode-pre-gyp ERR! node -v v18.20.5node-pre-gyp ERR! node-pre-gyp -v v1.0.11node-pre-gyp ERR! not ok Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/opt/iobroker/node_modules/bcrypt/lib/binding/napi-v3 --napi_version=9 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
      npm error code 1
      npm error path /opt/iobroker/node_modules/bcryptnpm error command failednpm error command sh -c node-pre-gyp install --fallback-to-build
      npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-01-18T09_32_23_658Z-debug-0.log
      Updating objects from io-package.json for adapter "node-red" with version "4.0.3"
      upload [15] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/bcrypt.min.js bcrypt.min.js application/javascript
      upload [14] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/de/translations.json i18n/de/translations.json application/j
      son
      upload [13] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/en/translations.json i18n/en/translations.json application/json
      upload [12] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/es/translations.json i18n/es/translations.json application/json
      upload [11] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
      upload [10] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/it/translations.json i18n/it/translations.json application/json
      upload [9] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
      upload [8] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
      upload [2] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/index_m.html index_m.html text/html
      upload [1] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/node-red.png node-red.png image/png
      upload [0] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/words.js words.js application/javascript
      Process exited with code 0
      
      
      Homoran mickym 2 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @EndofPi last edited by Homoran

        @endofpi ob das ein Bug ist werden wir sehen.

        Auf jeden Fall passt schon mal

        @endofpi sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

        Nodejs-Version: 20.18.1

        nicht zu

        @endofpi sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

        info using node@18.20.5

        bitte iob diag in der Langfassung posten

        EDIT:
        Da du einen Raspi verwendest bitte dafür diese drei Befehle nutzen

        curl https://raw.githubusercontent.com/Grothesk242/ioBroker/refs/heads/Raspbian/diag.sh > iob_diag.sh
        chmod 744 iob_diag.sh
        ./iob_diag.sh
        
        1 Reply Last reply Reply Quote 0
        • E
          EndofPi last edited by

          Hallo Homoran,

          die manuell eingetragene Versionsinfo zu Nodejs-Version hatte ich aus dem hosts-Reiter von iobroker abgeschrieben, der Unterschied zum Update-Script ist mir aber nicht aufgefallen.

          Bildschirmfoto 2025-01-19 um 17.11.11.png

          Nachfolgend die Zusammenfassung aus dem Shellscript:

          ======================= SUMMARY =======================
          			v.2024-12-09 Raspbian+zigbee diag+masking
          
          
             Static hostname: iobroker
                   Icon name: computer
            Operating System: Raspbian GNU/Linux 11 (bullseye)
                      Kernel: Linux 6.1.21-v8+
                Architecture: arm64
          
          Installation: 		native
          Kernel: 		aarch64
          Userland: 		32 bit
          Timezone: 		Europe/Berlin (CET, +0100)
          User-ID: 		1000
          Display-Server: 	false
          Boot Target: 		multi-user.target
          
          Pending OS-Updates: 	0
          Pending iob updates: 	1
          
          Nodejs-Installation:
          /usr/bin/nodejs 	v20.18.1
          /usr/bin/node 		v20.18.1
          /usr/bin/npm 		10.8.2
          /usr/bin/npx 		10.8.2
          /usr/bin/corepack 	0.29.4
          
          Recommended versions are nodejs 20.18.1 and npm 10.8.2
          nodeJS installation is correct
          
          MEMORY: 
                         total        used        free      shared  buff/cache   available
          Mem:            7.8G        520M        3.1G        1.0M        4.2G        7.2G
          Swap:            99M          0B         99M
          Total:          7.9G        520M        3.2G
          
          Active iob-Instances: 	8
          Upgrade policy: none
          
          ioBroker Core: 		js-controller 		7.0.6
          			admin 			7.4.10
          
          ioBroker Status: 	iobroker is running on this host.
          
          
          Objects type: jsonl
          States  type: jsonl
          
          Status admin and web instance:
          + system.adapter.admin.0                  : admin                 : iobroker                                 -  enabled, port: 8081, bind: 192.168.178.44 (SSL), run as: admin
            system.adapter.web.0                    : web                   : iobroker                                 - disabled, port: 8082, bind: 192.168.178.44, run as: admin
          
          Objects: 		2169
          States: 		1710
          
          Size of iob-Database:
          
          12M	/opt/iobroker/iobroker-data/objects.jsonl
          9.8M	/opt/iobroker/iobroker-data/states.jsonl
          
          
          Debian 'bullseye' is the current oldstable version. Please upgrade to the latest stable release 'bookworm' in due time!
          
          =================== END OF SUMMARY ====================
          
          1 Reply Last reply Reply Quote 0
          • mcm1957
            mcm1957 last edited by

            @endofpi

            Homoran schrieb:

            bitte iob diag in der Langfassung posten

            Komisch ist dass er offensichtlich nicht auf den cc Kompiler zugreifen kann:

            make: cc: Keine Berechtigung

            (in Zeile 20)

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

              @mcm1957 sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

              Komisch ist dass er offensichtlich nicht auf den cc Kompiler zugreifen kann:

              ist nicht meine Kragenweite, hab ich geflissentlich ignoriert.

              Da mehrfach node v18 im log erwähnt wird, ist sowieso anscheinend einiges schief.
              Bestenfalls zwei node Installationen parallel

              1 Reply Last reply Reply Quote 1
              • E
                EndofPi last edited by

                18.20.5 dürfte die default-version aus Raspbian sein.

                Auf Grund des Fehlers mit Node-Red habe ich versucht durch ein manuelles Upgrade mittels

                iob nodejs-update 
                

                das Problem zu lösen. Das Problem mit dem Adapter bestand aber auch vorher.

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

                  @endofpi sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

                  18.20.5 dürfte die default-version aus Raspbian sein.

                  Raspbian sollte kein eigenes nodejs mitbringen!

                  @endofpi sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

                  habe ich versucht durch ein manuelles Upgrade mittels

                  d.h. wir bekommen keine Langfassung von iob diag mehr, die den Zeitpunkt des logs widerspiegelt?

                  bitte lesen:
                  https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1

                  1 Reply Last reply Reply Quote 0
                  • mickym
                    mickym Most Active @EndofPi last edited by

                    @endofpi sagte in Update Node-Red 4.03 -> 5.2.1 auf RaspPi funktioniert nicht:

                    upload [1] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/node-red.png node-red.png image/png upload [0] node-red.admin /opt/iobroker/node_modules/iobroker.node-red/admin/words.js words.js application/javascript Process exited with code 0

                    Mal blöd gefragt - bist Du Dir denn sicher, dass das nicht funktioniert hat. - Vielleicht nur ein Browserrefresh. Der Prozess endet mit RC = 0 und das heißt, dass alles geklappt hat.

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

                    Support us

                    ioBroker
                    Community Adapters
                    Donate

                    806
                    Online

                    31.8k
                    Users

                    80.0k
                    Topics

                    1.3m
                    Posts

                    4
                    8
                    173
                    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