Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme

    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

    ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme

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

      @thomas-braun
      Merci - ist dann aber wohl kein gutes Zeichen, weil ich immer noch nicht den ble zum laufen bekomme nach Backitup rückspielung. 😰

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

        @gismoh

        iob stop
iob fix
cd /home/iobroker
sudo -u iobroker npm cache clear --force
cd
iobroker upgrade ble@0.13.4
        G 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @Thomas Braun last edited by

          @thomas-braun sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:

          In meiner Version steht da nämlich:

          in der einen ja, ich hab da beide
          7cebbb7b-504a-469c-873a-c9e26d7638b4-image.png

          und die Fehlermeldung spuckt ja auch aus

          npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFile
npm ERR!     build_file_contents = open(build_file_path, "rU").read()
npm ERR!                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gyp
          1 Reply Last reply Reply Quote 1
          • G
            Gismoh @Thomas Braun last edited by

            @thomas-braun

            idash@ioBrokerVM:/home/iobroker$ sudo -u iobroker npm cache clear --force
npm WARN using --force Recommended protections disabled.
npm ERR! code ENOTEMPTY
npm ERR! syscall rmdir
npm ERR! path /home/iobroker/.npm/_cacache
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rmdir '/home/iobroker/.npm/_cacache'

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-08T22_45_40_333Z-debug-0.log

            denke, es sollte anders aussehen?

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

              @gismoh

              Ja, das sollte so aussehen:

              echad@chet:/home/iobroker $ sudo -u iobroker npm cache clear --force
npm WARN using --force Recommended protections disabled.
echad@chet:/home/iobroker $

              ls -lah /home/iobroker/.npm/_cacache

              sagt?

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

                @thomas-braun

                idash@ioBrokerVM:/home/iobroker$ ls -lah /home/iobroker/.npm/_cacache
insgesamt 12K
drwxr-xr-x 3 iobroker iobroker 4,0K  8. Nov 23:45 .
drwxr-xr-x 7 iobroker iobroker 4,0K  8. Nov 22:10 ..
drwxr-xr-x 2 iobroker iobroker 4,0K  8. Nov 23:45 tmp
                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Gismoh last edited by

                  @gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:

                  rm -rf /home/iobroker/.npm/_cacache/tmp
                  G 1 Reply Last reply Reply Quote 0
                  • G
                    Gismoh @Thomas Braun last edited by

                    @thomas-braun

                    rm: das Entfernen von '/home/iobroker/.npm/_cacache/tmp/d411385f' ist nicht möglich: Keine Berechtigung
                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Gismoh last edited by

                      @gismoh

                      sudo -u iobroker rm -rf /home/iobroker/.npm/_cacache/tmp
                      G 1 Reply Last reply Reply Quote 0
                      • G
                        Gismoh @Thomas Braun last edited by

                        @thomas-braun

                        idash@ioBrokerVM:/home/iobroker$ sudo -u iobroker npm cache clear --force
npm WARN using --force Recommended protections disabled.
idash@ioBrokerVM:/home/iobroker$ cd
idash@ioBrokerVM:~$ iobroker upgrade ble@0.13.4
Adapter "ble"            is not installed.
                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Gismoh last edited by

                          @gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:

                          iobroker add ble@0.13.4 --debug
                          G 1 Reply Last reply Reply Quote 0
                          • G
                            Gismoh @Thomas Braun last edited by

                            @thomas-braun

                            idash@ioBrokerVM:~$ iobroker add ble@0.13.4 --debug
NPM version: 9.8.1
Installing iobroker.ble@0.13.4... (System call)
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
npm ERR! command failed
npm ERR! command sh -c node-gyp-build
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@18.18.2 | linux | x64
npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
npm ERR! (node:6399) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.18.2/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/18.18.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.18.2/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble',
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! Traceback (most recent call last):
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>
npm ERR!     sys.exit(gyp.script_main())
npm ERR!              ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_main
npm ERR!     return main(sys.argv[1:])
npm ERR!            ^^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in main
npm ERR!     return gyp_main(args)
npm ERR!            ^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_main
npm ERR!     [generator, flat_list, targets, data] = Load(
npm ERR!                                             ^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Load
npm ERR!     result = gyp.input.Load(
npm ERR!              ^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Load
npm ERR!     LoadTargetBuildFile(
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFile
npm ERR!     build_file_data = LoadOneBuildFile(
npm ERR!                       ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFile
npm ERR!     build_file_contents = open(build_file_path, "rU").read()
npm ERR!                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gyp
npm ERR! gyp ERR! configure error 
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
npm ERR! gyp ERR! System Linux 6.1.0-13-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
npm ERR! gyp ERR! node -v v18.18.2
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-08T22_56_29_824Z-debug-0.log
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
npm ERR! command failed
npm ERR! command sh -c node-gyp-build
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@18.18.2 | linux | x64
npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
npm ERR! (node:6399) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.18.2/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/18.18.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.18.2/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble',
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! Traceback (most recent call last):
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>
npm ERR!     sys.exit(gyp.script_main())
npm ERR!              ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_main
npm ERR!     return main(sys.argv[1:])
npm ERR!            ^^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in main
npm ERR!     return gyp_main(args)
npm ERR!            ^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_main
npm ERR!     [generator, flat_list, targets, data] = Load(
npm ERR!                                             ^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Load
npm ERR!     result = gyp.input.Load(
npm ERR!              ^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Load
npm ERR!     LoadTargetBuildFile(
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFile
npm ERR!     build_file_data = LoadOneBuildFile(
npm ERR!                       ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFile
npm ERR!     build_file_contents = open(build_file_path, "rU").read()
npm ERR!                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gyp
npm ERR! gyp ERR! configure error 
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
npm ERR! gyp ERR! System Linux 6.1.0-13-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
npm ERR! gyp ERR! node -v v18.18.2
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-08T22_56_29_824Z-debug-0.log
host.ioBrokerVM Cannot install iobroker.ble@0.13.4: 1
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Gismoh last edited by

                              @gismoh

                              sudo apt update
apt policy node-gyp
                              G 2 Replies Last reply Reply Quote 1
                              • G
                                Gismoh @Thomas Braun last edited by

                                @thomas-braun

                                idash@ioBrokerVM:~$ sudo apt update
OK:1 http://deb.debian.org/debian bookworm InRelease
OK:2 http://security.debian.org/debian-security bookworm-security InRelease    
OK:3 http://deb.debian.org/debian bookworm-updates InRelease                   
OK:4 https://repos.influxdata.com/debian stable InRelease                      
OK:5 https://deb.nodesource.com/node_18.x nodistro InRelease                   
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Alle Pakete sind aktuell.
idash@ioBrokerVM:~$ apt policy node-gyp
node-gyp:
  Installiert:           (keine)
  Installationskandidat: 9.3.0-2
  Versionstabelle:
     9.3.0-2 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
                                1 Reply Last reply Reply Quote 0
                                • G
                                  Gismoh @Thomas Braun last edited by

                                  @thomas-braun
                                  soll ich?:

                                  sudo npm install -g node-gyp
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Gismoh last edited by Thomas Braun

                                    @gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:

                                    sudo npm install -g node-gyp

                                    NEIN!
                                    Hast du das in der Vergangenheit schon mal gemacht?
                                    Oder mit 'npm' schon mal gemacht?

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

                                      @thomas-braun
                                      nein, hatte erst gerade eben danach gesucht
                                      npm vermutlich auch nicht, es sei denn es ist mir weiter oben (HEUTE) so angeraten wurden - meine aber nicht. Habe dieses Backup (der VM) erst heute eingespielt und dann das Backup (iobroker) aufgespielt.

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

                                        @gismoh
                                        Vergiss irgendwelche npm-Befehle, die ein -g beinhalten.
                                        Irgendwo zieht die Kiste ein altes node-gyp her.

                                        type -p node-gyp
                                        G 1 Reply Last reply Reply Quote 0
                                        • G
                                          Gismoh @Thomas Braun last edited by Gismoh

                                          @thomas-braun
                                          kam keine Ausgabe:

                                          idash@ioBrokerVM:~$ type -p node-gyp
idash@ioBrokerVM:~$

                                          Was macht das backitup nur, das es mir den ble zerschießt?
                                          Davor hat es ja funktioniert.

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

                                            @gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:

                                            Was macht das backitup nur, das es mir den ble zerschießt?

                                            Nichts.

                                            iobroker rebuild iobroker.ble
                                            G 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            455
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            8
                                            267
                                            23687
                                            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