Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 4.0.x jetzt für alle User im STABLE!

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

js-controller 4.0.x jetzt für alle User im STABLE!

Scheduled Pinned Locked Moved ioBroker Allgemein
501 Posts 83 Posters 154.6k Views 58 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • andiko2A andiko2

    @apollon77 was ist Post '#1? Bin nicht so der Forumkenner. Wenn möglich Link.

    apollon77A Online
    apollon77A Online
    apollon77
    wrote on last edited by
    #56

    @andiko2 Der erste Post in diesem Thread? Einfach gaaaaaaaaaaaaaaaaaaaanz nach oben Scrollen. Dort im Abschnitt "VOR der Installation"

    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
    1 Reply Last reply
    0
    • andiko2A andiko2

      @apollon77 was ist Post '#1? Bin nicht so der Forumkenner. Wenn möglich Link.

      T Online
      T Online
      tobrog
      wrote on last edited by tobrog
      #57

      @andiko2 Einfach in der Datei /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js in Zeile 44 von"adapter.objects.getObjectList" zu "adapter.getObjectList" ändern.

      andiko2A 1 Reply Last reply
      1
      • T Offline
        T Offline
        TDCroPower
        wrote on last edited by
        #58

        Update des js-controllers auf dem Docker Image von buanet ist durch, lediglich der rebuild vom BLE Adapter läuft bei 3 Versuchen nicht durch und im Log sieht man jetzt folgendes...

        host.helios64
        2022-02-26 12:48:17.793	info	Rebuild for adapter system.adapter.ble.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
        host.helios64
        2022-02-26 12:48:17.792	info	instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
        

        wenn ich den Befehl in der Konsole eingebe kommt folgendes...

        root@helios64:/opt/iobroker# npm install --production
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents):
        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
        
        removed 3 packages and updated 1 package in 34.934s
        
        137 packages are looking for funding
          run `npm fund` for details
        
        root@helios64:/opt/iobroker#
        

        was nun !?

        apollon77A 1 Reply Last reply
        0
        • T tobrog

          @andiko2 Einfach in der Datei /opt/iobroker/node_modules/iobroker.systeminfo/myAdapter.js in Zeile 44 von"adapter.objects.getObjectList" zu "adapter.getObjectList" ändern.

          andiko2A Online
          andiko2A Online
          andiko2
          wrote on last edited by
          #59

          @tobrog said in js-controller 4.0.x jetzt für alle User im STABLE!:

          adapter.getObjectList

          Dankeschön. Genau diese Info hat geholfen.

          1 Reply Last reply
          0
          • T TDCroPower

            Update des js-controllers auf dem Docker Image von buanet ist durch, lediglich der rebuild vom BLE Adapter läuft bei 3 Versuchen nicht durch und im Log sieht man jetzt folgendes...

            host.helios64
            2022-02-26 12:48:17.793	info	Rebuild for adapter system.adapter.ble.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually.
            host.helios64
            2022-02-26 12:48:17.792	info	instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
            

            wenn ich den Befehl in der Konsole eingebe kommt folgendes...

            root@helios64:/opt/iobroker# npm install --production
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.7 (node_modules/osx-temperature-sensor):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/zigbee-herdsman/node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
            
            removed 3 packages and updated 1 package in 34.934s
            
            137 packages are looking for funding
              run `npm fund` for details
            
            root@helios64:/opt/iobroker#
            

            was nun !?

            apollon77A Online
            apollon77A Online
            apollon77
            wrote on last edited by
            #60

            @tdcropower Naja du solltest den "npm install" in einem bestimmten Verzeichnis ausführen - steht an sich in den Anweisungen im Log. Du hast es im iobroker "root" verzeichnis ausgeführt. Das hilft nicht, ja.
            Du musst es in /opt/iobroker/node_modules/iobroker.ble ausführen

            Und ja leider ist der BLE Adapter bze eine Library davon gerade nicht rebuild-fähig. Wir haben dort schon eine Änderung eingereicht, die ist aber noch nicht released.

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            T 1 Reply Last reply
            0
            • apollon77A apollon77

              @tdcropower Naja du solltest den "npm install" in einem bestimmten Verzeichnis ausführen - steht an sich in den Anweisungen im Log. Du hast es im iobroker "root" verzeichnis ausgeführt. Das hilft nicht, ja.
              Du musst es in /opt/iobroker/node_modules/iobroker.ble ausführen

              Und ja leider ist der BLE Adapter bze eine Library davon gerade nicht rebuild-fähig. Wir haben dort schon eine Änderung eingereicht, die ist aber noch nicht released.

              T Offline
              T Offline
              TDCroPower
              wrote on last edited by
              #61

              @apollon77 danke habe es eben auch im Issue bei git gelesen.
              Leider fehlt der Hinweis auf das Verzeichnis in der Log Nachricht, wobei "adapter directory" es eigentlich sagt.

              Naja, jetzt hat es funktioniert...

              root@helios64:/opt/iobroker# cd node_modules/iobroker.ble/
              root@helios64:/opt/iobroker/node_modules/iobroker.ble# npm install -- production
              npm WARN deprecated request@2.12.0: request has been deprecated, see https://github.com/request/request/issues/3142
              
              > deasync@0.1.24 install /opt/iobroker/node_modules/iobroker.ble/node_modules/deasync
              > node ./build.js
              
              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                CXX(target) Release/obj.target/deasync/src/deasync.o
                SOLINK_MODULE(target) Release/obj.target/deasync.node
                COPY Release/deasync.node
              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
              Installed in `/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/bin/linux-arm64-node-14/deasync.node`
              
              > usb@1.9.2 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
              > node-gyp-build
              
              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                CC(target) Release/obj.target/libusb/libusb/libusb/core.o
                CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
                CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
                CC(target) Release/obj.target/libusb/libusb/libusb/io.o
                CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
                CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
                CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
                CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
                CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
                CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
                AR(target) Release/obj.target/usb.a
                COPY Release/usb.a
                CXX(target) Release/obj.target/usb_bindings/src/node_usb.o
              ../src/node_usb.cc: In function ‘Napi::Value SetDebugLevel(const Napi::CallbackInfo&)’:
              ../src/node_usb.cc:118:71: warning: ‘void libusb_set_debug(libusb_context*, int)’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations]
                118 |  libusb_set_debug(usb_context, info[0].As<Napi::Number>().Int32Value());
                    |                                                                       ^
              In file included from ../src/node_usb.h:11,
                               from ../src/node_usb.cc:1:
              ../libusb/libusb/libusb.h:1325:18: note: declared here
               1325 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level);
                    |                  ^~~~~~~~~~~~~~~~
                CXX(target) Release/obj.target/usb_bindings/src/device.o
                CXX(target) Release/obj.target/usb_bindings/src/transfer.o
                SOLINK_MODULE(target) Release/obj.target/usb_bindings.node
                COPY Release/usb_bindings.node
              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
              
              > @abandonware/bluetooth-hci-socket@0.5.3-8 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
              > node-pre-gyp install --fallback-to-build
              
              node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
              node-pre-gyp WARN Pre-built binaries not installable for @abandonware/bluetooth-hci-socket@0.5.3-8 and node@14.18.2 (node-v83 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/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                CXX(target) Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o
              In file included from /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node_buffer.h:25,
                               from ../src/BluetoothHciSocket.cpp:7:
              /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                787 |       (node::addon_register_func) (regfunc),                          \
                    |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expansion of macro ‘NODE_MODULE_X’
                821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                    |   ^~~~~~~~~~~~~
              ../src/BluetoothHciSocket.cpp:635:1: note: in expansion of macro ‘NODE_MODULE’
                635 | NODE_MODULE(binding, BluetoothHciSocket::Init);
                    | ^~~~~~~~~~~
              ../src/BluetoothHciSocket.cpp: In member function ‘int BluetoothHciSocket::kernelDisconnectWorkArounds(int, char*)’:
              ../src/BluetoothHciSocket.cpp:401:1: warning: control reaches end of non-void function [-Wreturn-type]
                401 | }
                    | ^
                SOLINK_MODULE(target) Release/obj.target/bluetooth_hci_socket.node
                COPY Release/bluetooth_hci_socket.node
                COPY /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node
                TOUCH Release/obj.target/action_after_build.stamp
              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
              
              > @abandonware/noble@1.9.2-15 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
              > node-gyp rebuild
              
              make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                SOLINK_MODULE(target) Release/obj.target/noble.node
                COPY Release/noble.node
              make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
              
              > core-js@2.6.12 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/core-js
              > node -e "try{require('./postinstall')}catch(e){}"
              
              Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
              
              The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
              > https://opencollective.com/core-js 
              > https://www.patreon.com/zloirock 
              
              Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
              
              
              > parcel-bundler@1.12.5 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/parcel-bundler
              > node -e "console.log('\u001b[35m\u001b[1mLove Parcel? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/parcel/donate\u001b[0m')"
              
              Love Parcel? You can now donate to our open collective:
               > https://opencollective.com/parcel/donate
              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/glob-watcher/node_modules/fsevents):
              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/@parcel/watcher/node_modules/fsevents):
              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
              npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
              
              + production@0.0.2
              added 1489 packages from 1205 contributors in 146.424s
              
              109 packages are looking for funding
                run `npm fund` for details
              
              root@helios64:/opt/iobroker/node_modules/iobroker.ble#
              

              .. danach nur noch den Adapter neustarten und er ist wieder Grün!

              ? apollon77A 2 Replies Last reply
              1
              • T TDCroPower

                @apollon77 danke habe es eben auch im Issue bei git gelesen.
                Leider fehlt der Hinweis auf das Verzeichnis in der Log Nachricht, wobei "adapter directory" es eigentlich sagt.

                Naja, jetzt hat es funktioniert...

                root@helios64:/opt/iobroker# cd node_modules/iobroker.ble/
                root@helios64:/opt/iobroker/node_modules/iobroker.ble# npm install -- production
                npm WARN deprecated request@2.12.0: request has been deprecated, see https://github.com/request/request/issues/3142
                
                > deasync@0.1.24 install /opt/iobroker/node_modules/iobroker.ble/node_modules/deasync
                > node ./build.js
                
                make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                  CXX(target) Release/obj.target/deasync/src/deasync.o
                  SOLINK_MODULE(target) Release/obj.target/deasync.node
                  COPY Release/deasync.node
                make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                Installed in `/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/bin/linux-arm64-node-14/deasync.node`
                
                > usb@1.9.2 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
                > node-gyp-build
                
                make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                  CC(target) Release/obj.target/libusb/libusb/libusb/core.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/io.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
                  CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
                  AR(target) Release/obj.target/usb.a
                  COPY Release/usb.a
                  CXX(target) Release/obj.target/usb_bindings/src/node_usb.o
                ../src/node_usb.cc: In function ‘Napi::Value SetDebugLevel(const Napi::CallbackInfo&)’:
                ../src/node_usb.cc:118:71: warning: ‘void libusb_set_debug(libusb_context*, int)’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations]
                  118 |  libusb_set_debug(usb_context, info[0].As<Napi::Number>().Int32Value());
                      |                                                                       ^
                In file included from ../src/node_usb.h:11,
                                 from ../src/node_usb.cc:1:
                ../libusb/libusb/libusb.h:1325:18: note: declared here
                 1325 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level);
                      |                  ^~~~~~~~~~~~~~~~
                  CXX(target) Release/obj.target/usb_bindings/src/device.o
                  CXX(target) Release/obj.target/usb_bindings/src/transfer.o
                  SOLINK_MODULE(target) Release/obj.target/usb_bindings.node
                  COPY Release/usb_bindings.node
                make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                
                > @abandonware/bluetooth-hci-socket@0.5.3-8 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
                > node-pre-gyp install --fallback-to-build
                
                node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                node-pre-gyp WARN Pre-built binaries not installable for @abandonware/bluetooth-hci-socket@0.5.3-8 and node@14.18.2 (node-v83 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/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                  CXX(target) Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o
                In file included from /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node_buffer.h:25,
                                 from ../src/BluetoothHciSocket.cpp:7:
                /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                  787 |       (node::addon_register_func) (regfunc),                          \
                      |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expansion of macro ‘NODE_MODULE_X’
                  821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                      |   ^~~~~~~~~~~~~
                ../src/BluetoothHciSocket.cpp:635:1: note: in expansion of macro ‘NODE_MODULE’
                  635 | NODE_MODULE(binding, BluetoothHciSocket::Init);
                      | ^~~~~~~~~~~
                ../src/BluetoothHciSocket.cpp: In member function ‘int BluetoothHciSocket::kernelDisconnectWorkArounds(int, char*)’:
                ../src/BluetoothHciSocket.cpp:401:1: warning: control reaches end of non-void function [-Wreturn-type]
                  401 | }
                      | ^
                  SOLINK_MODULE(target) Release/obj.target/bluetooth_hci_socket.node
                  COPY Release/bluetooth_hci_socket.node
                  COPY /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node
                  TOUCH Release/obj.target/action_after_build.stamp
                make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                
                > @abandonware/noble@1.9.2-15 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
                > node-gyp rebuild
                
                make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                  SOLINK_MODULE(target) Release/obj.target/noble.node
                  COPY Release/noble.node
                make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                
                > core-js@2.6.12 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/core-js
                > node -e "try{require('./postinstall')}catch(e){}"
                
                Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                
                The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
                > https://opencollective.com/core-js 
                > https://www.patreon.com/zloirock 
                
                Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                
                
                > parcel-bundler@1.12.5 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/parcel-bundler
                > node -e "console.log('\u001b[35m\u001b[1mLove Parcel? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/parcel/donate\u001b[0m')"
                
                Love Parcel? You can now donate to our open collective:
                 > https://opencollective.com/parcel/donate
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/glob-watcher/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/@parcel/watcher/node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                
                + production@0.0.2
                added 1489 packages from 1205 contributors in 146.424s
                
                109 packages are looking for funding
                  run `npm fund` for details
                
                root@helios64:/opt/iobroker/node_modules/iobroker.ble#
                

                .. danach nur noch den Adapter neustarten und er ist wieder Grün!

                ? Offline
                ? Offline
                A Former User
                wrote on last edited by
                #62

                @tdcropower

                mit root geht es mit nodejs nicht gut!

                1 Reply Last reply
                1
                • T TDCroPower

                  @apollon77 danke habe es eben auch im Issue bei git gelesen.
                  Leider fehlt der Hinweis auf das Verzeichnis in der Log Nachricht, wobei "adapter directory" es eigentlich sagt.

                  Naja, jetzt hat es funktioniert...

                  root@helios64:/opt/iobroker# cd node_modules/iobroker.ble/
                  root@helios64:/opt/iobroker/node_modules/iobroker.ble# npm install -- production
                  npm WARN deprecated request@2.12.0: request has been deprecated, see https://github.com/request/request/issues/3142
                  
                  > deasync@0.1.24 install /opt/iobroker/node_modules/iobroker.ble/node_modules/deasync
                  > node ./build.js
                  
                  make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                    CXX(target) Release/obj.target/deasync/src/deasync.o
                    SOLINK_MODULE(target) Release/obj.target/deasync.node
                    COPY Release/deasync.node
                  make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/build'
                  Installed in `/opt/iobroker/node_modules/iobroker.ble/node_modules/deasync/bin/linux-arm64-node-14/deasync.node`
                  
                  > usb@1.9.2 install /opt/iobroker/node_modules/iobroker.ble/node_modules/usb
                  > node-gyp-build
                  
                  make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                    CC(target) Release/obj.target/libusb/libusb/libusb/core.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/descriptor.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/hotplug.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/io.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/strerror.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/sync.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/os/poll_posix.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/os/threads_posix.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o
                    CC(target) Release/obj.target/libusb/libusb/libusb/os/linux_udev.o
                    AR(target) Release/obj.target/usb.a
                    COPY Release/usb.a
                    CXX(target) Release/obj.target/usb_bindings/src/node_usb.o
                  ../src/node_usb.cc: In function ‘Napi::Value SetDebugLevel(const Napi::CallbackInfo&)’:
                  ../src/node_usb.cc:118:71: warning: ‘void libusb_set_debug(libusb_context*, int)’ is deprecated: Use libusb_set_option instead [-Wdeprecated-declarations]
                    118 |  libusb_set_debug(usb_context, info[0].As<Napi::Number>().Int32Value());
                        |                                                                       ^
                  In file included from ../src/node_usb.h:11,
                                   from ../src/node_usb.cc:1:
                  ../libusb/libusb/libusb.h:1325:18: note: declared here
                   1325 | void LIBUSB_CALL libusb_set_debug(libusb_context *ctx, int level);
                        |                  ^~~~~~~~~~~~~~~~
                    CXX(target) Release/obj.target/usb_bindings/src/device.o
                    CXX(target) Release/obj.target/usb_bindings/src/transfer.o
                    SOLINK_MODULE(target) Release/obj.target/usb_bindings.node
                    COPY Release/usb_bindings.node
                  make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/usb/build'
                  
                  > @abandonware/bluetooth-hci-socket@0.5.3-8 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket
                  > node-pre-gyp install --fallback-to-build
                  
                  node-pre-gyp ERR! install response status 404 Not Found on https://github.com/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                  node-pre-gyp WARN Pre-built binaries not installable for @abandonware/bluetooth-hci-socket@0.5.3-8 and node@14.18.2 (node-v83 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/abandonware/node-bluetooth-hci-socket/releases/download/0.5.3-8/bluetooth_hci_socket-0.5.3-8-node-v83-linux-arm64.tar.gz 
                  make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                    CXX(target) Release/obj.target/bluetooth_hci_socket/src/BluetoothHciSocket.o
                  In file included from /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node_buffer.h:25,
                                   from ../src/BluetoothHciSocket.cpp:7:
                  /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:787:7: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                    787 |       (node::addon_register_func) (regfunc),                          \
                        |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  /opt/iobroker/.cache/node-gyp/14.18.2/include/node/node.h:821:3: note: in expansion of macro ‘NODE_MODULE_X’
                    821 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                        |   ^~~~~~~~~~~~~
                  ../src/BluetoothHciSocket.cpp:635:1: note: in expansion of macro ‘NODE_MODULE’
                    635 | NODE_MODULE(binding, BluetoothHciSocket::Init);
                        | ^~~~~~~~~~~
                  ../src/BluetoothHciSocket.cpp: In member function ‘int BluetoothHciSocket::kernelDisconnectWorkArounds(int, char*)’:
                  ../src/BluetoothHciSocket.cpp:401:1: warning: control reaches end of non-void function [-Wreturn-type]
                    401 | }
                        | ^
                    SOLINK_MODULE(target) Release/obj.target/bluetooth_hci_socket.node
                    COPY Release/bluetooth_hci_socket.node
                    COPY /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node
                    TOUCH Release/obj.target/action_after_build.stamp
                  make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/bluetooth-hci-socket/build'
                  
                  > @abandonware/noble@1.9.2-15 install /opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble
                  > node-gyp rebuild
                  
                  make: Entering directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                    SOLINK_MODULE(target) Release/obj.target/noble.node
                    COPY Release/noble.node
                  make: Leaving directory '/opt/iobroker/node_modules/iobroker.ble/node_modules/@abandonware/noble/build'
                  
                  > core-js@2.6.12 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/core-js
                  > node -e "try{require('./postinstall')}catch(e){}"
                  
                  Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
                  
                  The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
                  > https://opencollective.com/core-js 
                  > https://www.patreon.com/zloirock 
                  
                  Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
                  
                  
                  > parcel-bundler@1.12.5 postinstall /opt/iobroker/node_modules/iobroker.ble/node_modules/parcel-bundler
                  > node -e "console.log('\u001b[35m\u001b[1mLove Parcel? You can now donate to our open collective:\u001b[22m\u001b[39m\n > \u001b[34mhttps://opencollective.com/parcel/donate\u001b[0m')"
                  
                  Love Parcel? You can now donate to our open collective:
                   > https://opencollective.com/parcel/donate
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/glob-watcher/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules/@parcel/watcher/node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                  
                  + production@0.0.2
                  added 1489 packages from 1205 contributors in 146.424s
                  
                  109 packages are looking for funding
                    run `npm fund` for details
                  
                  root@helios64:/opt/iobroker/node_modules/iobroker.ble#
                  

                  .. danach nur noch den Adapter neustarten und er ist wieder Grün!

                  apollon77A Online
                  apollon77A Online
                  apollon77
                  wrote on last edited by
                  #63

                  @tdcropower Jupp. Jetzt am besten ein „iob fix“ hinterher und dann am besten nicht mehr mit root

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  T 1 Reply Last reply
                  0
                  • apollon77A apollon77

                    @tdcropower Jupp. Jetzt am besten ein „iob fix“ hinterher und dann am besten nicht mehr mit root

                    T Offline
                    T Offline
                    TDCroPower
                    wrote on last edited by
                    #64

                    @apollon77 ihr habt Recht, im Docker Image gibt es noch einen iobroker user auf dem iobroker installiert wurde.

                    iobroker@helios64:~$ ls -l
                    total 1132
                    drwxrwxr-x+   3 iobroker iobroker    4096 Feb 26 02:30 backups
                    -rwxrwxrwx+   1 iobroker iobroker     233 Nov 23 16:15 INSTALLER_INFO.txt
                    lrwxrwxrwx    1 iobroker iobroker      22 Nov 23 16:15 iob -> /opt/iobroker/iobroker
                    -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:56 iobroker
                    -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:40 iobroker.bak
                    drwxrwxr-x+  10 iobroker iobroker    4096 Feb 26 14:20 iobroker-data
                    drwxrwxr-x+   2 iobroker iobroker    4096 Feb 26 13:30 log
                    drwxrwxr-x+ 621 iobroker iobroker   20480 Feb 26 12:51 node_modules
                    -rw-rwxr--+   1 iobroker iobroker     864 Feb 26 12:39 package.json
                    -rw-rwxr--+   1 iobroker iobroker 1098042 Feb 26 12:51 package-lock.json
                    -rw-rwxr--+   1 iobroker iobroker    5693 Dez 23 01:16 reinstall.js
                    iobroker@helios64:~$
                    

                    Dann bleibt der default Portainer User root wieder weg.

                    apollon77A 1 Reply Last reply
                    0
                    • E Offline
                      E Offline
                      Etbron
                      wrote on last edited by
                      #65

                      Ich habe gerade das Update nach Anleitung gemacht. Leider ist wohl ein Fehler aufgetreten, jetzt scheint mein ioBroker tot zu sein. Da ich Linux-mäßig leider Laie bin, fehlt mir jetzt ehrlich gesagt die Idee, wie ich am besten mit einer Reparatur anfangen kann.

                      tlettschmidt@iobroker:~$ iob upgrade self
                      Update js-controller from @3.3.22 to @4.0.15
                      NPM version: 6.14.16
                      npm install iobroker.js-controller@4.0.15 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                      In file included from ../../nan/nan.h:58,
                                       from ../src/unix_dgram.cc:5:
                      /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                        793 |       (node::addon_register_func) (regfunc),                          \
                            |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                      /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                        827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                            |   ^~~~~~~~~~~~~
                      ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                        404 | NODE_MODULE(unix_dgram, Initialize)
                            | ^~~~~~~~~~~
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                      Server States 127.0.0.1:56264 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                      Server States 127.0.0.1:56268 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                      Server Objects 127.0.0.1:41698 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                      Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                      

                      Bin für jede Anregung und jeden Tipp dankbar.

                      E 1 Reply Last reply
                      0
                      • E Etbron

                        Ich habe gerade das Update nach Anleitung gemacht. Leider ist wohl ein Fehler aufgetreten, jetzt scheint mein ioBroker tot zu sein. Da ich Linux-mäßig leider Laie bin, fehlt mir jetzt ehrlich gesagt die Idee, wie ich am besten mit einer Reparatur anfangen kann.

                        tlettschmidt@iobroker:~$ iob upgrade self
                        Update js-controller from @3.3.22 to @4.0.15
                        NPM version: 6.14.16
                        npm install iobroker.js-controller@4.0.15 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call)
                        In file included from ../../nan/nan.h:58,
                                         from ../src/unix_dgram.cc:5:
                        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:7: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                          793 |       (node::addon_register_func) (regfunc),                          \
                              |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:827:3: note: in expansion of macro ‘NODE_MODULE_X’
                          827 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                              |   ^~~~~~~~~~~~~
                        ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                          404 | NODE_MODULE(unix_dgram, Initialize)
                              | ^~~~~~~~~~~
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets"]
                        Server States 127.0.0.1:56264 Error from InMemDB: Error: GET-UNSUPPORTED for namespace meta.: Data=["meta.states.protocolVersion"]
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: GET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.protocolVersion"]
                        Server States 127.0.0.1:56268 Error from InMemDB: Error: PSUBSCRIBE-UNSUPPORTED for namespace meta.: Data=["meta.*"]
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: Unknown LUA script load
                        Server Objects 127.0.0.1:41698 Error from InMemDB: Error: SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                        Could not migrate objects to corresponding sets: Error SET-UNSUPPORTED for namespace cfg.: Data=["meta.objects.features.useSets",{"type":"Buffer","data":[49]}]
                        

                        Bin für jede Anregung und jeden Tipp dankbar.

                        E Offline
                        E Offline
                        Etbron
                        wrote on last edited by
                        #66

                        Schnappatmung hat sich ein wenig beruhigt. Ich habe ihn nochmal gestoppt, nochmal gestartet und scheinbar läuft er jetzt. Trotzdem wäre es schön, wenn sich jemand den Fehler anschauen würde und mir ein kurzes Feedback geben könnte, ob ich jetzt ein problem habe bzw. bekommen werde.

                        apollon77A 1 Reply Last reply
                        1
                        • T TDCroPower

                          @apollon77 ihr habt Recht, im Docker Image gibt es noch einen iobroker user auf dem iobroker installiert wurde.

                          iobroker@helios64:~$ ls -l
                          total 1132
                          drwxrwxr-x+   3 iobroker iobroker    4096 Feb 26 02:30 backups
                          -rwxrwxrwx+   1 iobroker iobroker     233 Nov 23 16:15 INSTALLER_INFO.txt
                          lrwxrwxrwx    1 iobroker iobroker      22 Nov 23 16:15 iob -> /opt/iobroker/iobroker
                          -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:56 iobroker
                          -rwxr-xr-x+   1 iobroker iobroker     178 Feb 26 12:40 iobroker.bak
                          drwxrwxr-x+  10 iobroker iobroker    4096 Feb 26 14:20 iobroker-data
                          drwxrwxr-x+   2 iobroker iobroker    4096 Feb 26 13:30 log
                          drwxrwxr-x+ 621 iobroker iobroker   20480 Feb 26 12:51 node_modules
                          -rw-rwxr--+   1 iobroker iobroker     864 Feb 26 12:39 package.json
                          -rw-rwxr--+   1 iobroker iobroker 1098042 Feb 26 12:51 package-lock.json
                          -rw-rwxr--+   1 iobroker iobroker    5693 Dez 23 01:16 reinstall.js
                          iobroker@helios64:~$
                          

                          Dann bleibt der default Portainer User root wieder weg.

                          apollon77A Online
                          apollon77A Online
                          apollon77
                          wrote on last edited by
                          #67

                          @tdcropower ok da bin ich ehrlich. Keine Ahnung. An sich sollte man nicht mit dem iobroker User arbeiten. @andre ?! Wie ist das bei Docker am besten?!

                          Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                          • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                          • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                          1 Reply Last reply
                          0
                          • E Etbron

                            Schnappatmung hat sich ein wenig beruhigt. Ich habe ihn nochmal gestoppt, nochmal gestartet und scheinbar läuft er jetzt. Trotzdem wäre es schön, wenn sich jemand den Fehler anschauen würde und mir ein kurzes Feedback geben könnte, ob ich jetzt ein problem habe bzw. bekommen werde.

                            apollon77A Online
                            apollon77A Online
                            apollon77
                            wrote on last edited by
                            #68

                            @etbron das ist alles ok. Ließ doch mal gaaaaanz oben im ersten post. Da steht alles drin. Diese Meldungen sind erwartet gewesen und daher voll normal. Jaaaanz ruhig

                            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                            E 1 Reply Last reply
                            1
                            • apollon77A apollon77

                              @etbron das ist alles ok. Ließ doch mal gaaaaanz oben im ersten post. Da steht alles drin. Diese Meldungen sind erwartet gewesen und daher voll normal. Jaaaanz ruhig

                              E Offline
                              E Offline
                              Etbron
                              wrote on last edited by
                              #69

                              @apollon77 Danke. Die Ich hatte das Post gesehen - und hätte mir auch keine Sorgen gemacht, wenn der ioBroker nach dem Update direkt wieder erreichbar gewesen wäre. Vielen Dank für die schnelle Antwort und beruhigenden Worte 🙂

                              1 Reply Last reply
                              0
                              • E Offline
                                E Offline
                                erfggi
                                wrote on last edited by
                                #70

                                Mein Update war erfolgreich auf dem Master (Proxmox VM) und auf dem Slave (RaspberryPi4 mit Deconz2 UsbStick) Läuft alles seit 4h ohne Probleme.

                                1 Reply Last reply
                                1
                                • Rene55R Offline
                                  Rene55R Offline
                                  Rene55
                                  wrote on last edited by
                                  #71

                                  Mein ioBroker läuft als Docker-Container. Beim Aufruf des 'iob upgrade self' bekomme ich den Fehler 'sudo: unable to execute /usr/bin/node: Operation not permitted'. Gibt es für Docker-User hier was besonderes zu beachten?

                                  Host: Fujitsu Intel(R) Pentium(R) CPU G4560T, 32 GB RAM, Proxmox 8.x + lxc Ubuntu 22.04
                                  ioBroker (8 GB RAM) Node.js: 20.19.1, NPM: 10.8.2, js-Controller: 7.0.6, Admin: 7.6.3
                                  Wetterstation: Froggit WH3000SE V1.6.6

                                  Ben1983B apollon77A 2 Replies Last reply
                                  0
                                  • Rene55R Rene55

                                    Mein ioBroker läuft als Docker-Container. Beim Aufruf des 'iob upgrade self' bekomme ich den Fehler 'sudo: unable to execute /usr/bin/node: Operation not permitted'. Gibt es für Docker-User hier was besonderes zu beachten?

                                    Ben1983B Offline
                                    Ben1983B Offline
                                    Ben1983
                                    wrote on last edited by
                                    #72

                                    @rene55 mein iobroker läuft unter Windows.
                                    Muss mal hier wirklich den installer eine neue Instanz installieren lassen, oder lediglich in der console ein upgrade Self ausführen?
                                    Kann mir jemand beschreiben, wie ich das ubter Windows hoch ziehe? Stehe komplett im dunklen.

                                    apollon77A 1 Reply Last reply
                                    0
                                    • Ben1983B Ben1983

                                      @rene55 mein iobroker läuft unter Windows.
                                      Muss mal hier wirklich den installer eine neue Instanz installieren lassen, oder lediglich in der console ein upgrade Self ausführen?
                                      Kann mir jemand beschreiben, wie ich das ubter Windows hoch ziehe? Stehe komplett im dunklen.

                                      apollon77A Online
                                      apollon77A Online
                                      apollon77
                                      wrote on last edited by
                                      #73

                                      @ben1983 zu Windows am besten im ersten post schauen. Da ist ein link zu einer Anleitung von @sigi234 … ggf dann dort bitte fragen.

                                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                      Ben1983B 1 Reply Last reply
                                      0
                                      • Rene55R Rene55

                                        Mein ioBroker läuft als Docker-Container. Beim Aufruf des 'iob upgrade self' bekomme ich den Fehler 'sudo: unable to execute /usr/bin/node: Operation not permitted'. Gibt es für Docker-User hier was besonderes zu beachten?

                                        apollon77A Online
                                        apollon77A Online
                                        apollon77
                                        wrote on last edited by
                                        #74

                                        @rene55 @andre an advice? Danke. An sich sollte das doch direkt tun….

                                        Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                        • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                        • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                        Rene55R 1 Reply Last reply
                                        0
                                        • apollon77A apollon77

                                          @liv-in-sky ließ mal in der faq. Du hast ne alte mongodb lib wohl von nem node-red. Liegt eher an nodejs 14+ als am Controller.

                                          LatziL Online
                                          LatziL Online
                                          Latzi
                                          wrote on last edited by
                                          #75

                                          @apollon77 sagte in js-controller 4.0.x jetzt für alle User im STABLE!:

                                          Du hast ne alte mongodb lib wohl von nem node-red. Liegt eher an nodejs 14+ als am Controller.

                                          @apollon77 ich bekomm die mongodb lib nicht weg, gibt es noch einen anderen Weg oder hab ich da was falsch gemacht?

                                          pi@Pi4-Server:/opt/iobroker $ npm uninstall mongodb
                                          npm ERR! code ELOOP
                                          npm ERR! syscall open
                                          npm ERR! path /opt/iobroker/node_modules/xml2js/package.json
                                          npm ERR! errno -40
                                          npm ERR! ELOOP: too many symbolic links encountered, open '/opt/iobroker/node_modules/xml2js/package.json'
                                          
                                          
                                          apollon77A 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

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

                                          441

                                          Online

                                          32.4k

                                          Users

                                          81.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe