Skip to content
  • Home
  • 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
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 4.0 jetzt im BETA/LATEST!

NEWS

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    16
    1
    238

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    4.5k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.3k

js-controller 4.0 jetzt im BETA/LATEST!

Scheduled Pinned Locked Moved ioBroker Allgemein
747 Posts 70 Posters 240.0k Views 60 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.
  • Thomas BraunT Thomas Braun

    @jabba_the_hutt sagte in js-controller 4.0 jetzt im BETA/LATEST!:

    Welche node.js darfs denn sein?

    Eins mit 'ner anderen ABI als dein jetziges. 😀

    Jabba_the_HuttJ Offline
    Jabba_the_HuttJ Offline
    Jabba_the_Hutt
    wrote on last edited by
    #355

    @thomas-braun

    :D v16 wollte ich eh schon lange ggg

    1 Reply Last reply
    0
    • Thomas BraunT Thomas Braun

      @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

      (na, mag nochmal jemand Node.js upgraden oder so? ;-)) )

      Kein Problem. Node-Versionswechsel ist ja schnell gemacht.

      Wobei die letzten Wechsel der nodejs-Installation bei den von mir eingesetzten Adaptern schon sauber weggebügelt wurden. Da erwarte ich also keine Verbesserung.

      apollon77A Offline
      apollon77A Offline
      apollon77
      wrote on last edited by
      #356

      @thomas-braun Am Ende eins was "bluetooth" kram drin hat (ble adapter) und/oder canvas ... die sind zickig und ja die werden nicht automatisch rebuild gehen (weil da fixes bei den libs fehlen) aber ich würde am Log sehen das unsere versuche alle richtig laufen :-)

      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
      Jabba_the_HuttJ Thomas BraunT 2 Replies Last reply
      0
      • apollon77A apollon77

        @thomas-braun Am Ende eins was "bluetooth" kram drin hat (ble adapter) und/oder canvas ... die sind zickig und ja die werden nicht automatisch rebuild gehen (weil da fixes bei den libs fehlen) aber ich würde am Log sehen das unsere versuche alle richtig laufen :-)

        Jabba_the_HuttJ Offline
        Jabba_the_HuttJ Offline
        Jabba_the_Hutt
        wrote on last edited by
        #357

        @apollon77

        ble adapter kann ich dann austesten ... log stell ich dann online.

        1 Reply Last reply
        1
        • apollon77A apollon77

          @thomas-braun Am Ende eins was "bluetooth" kram drin hat (ble adapter) und/oder canvas ... die sind zickig und ja die werden nicht automatisch rebuild gehen (weil da fixes bei den libs fehlen) aber ich würde am Log sehen das unsere versuche alle richtig laufen :-)

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          wrote on last edited by Thomas Braun
          #358

          @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

          weil da fixes bei den libs fehlen

          Den für canvas hab ich aber drin. Du erinnerst dich?
          Den ble installier ich gerade mal flugs.

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

          apollon77A 1 Reply Last reply
          1
          • Thomas BraunT Thomas Braun

            @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

            weil da fixes bei den libs fehlen

            Den für canvas hab ich aber drin. Du erinnerst dich?
            Den ble installier ich gerade mal flugs.

            apollon77A Offline
            apollon77A Offline
            apollon77
            wrote on last edited by
            #359

            @thomas-braun ja da bist du die Ausnahme. Der sollte dann direkt beim „ grossen“ rebuild mit gehen.

            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
            Thomas BraunT 1 Reply Last reply
            0
            • apollon77A apollon77

              hallo,

              mit dem Feedback der letzten tage habe ich heute den js-controller 4.0.10, aka Stable-RC2 für Euch. Enthalten ist:

              4.0.10 (2022-02-15)

              • (foxriver76) Fix module specific rebuild command
              • (foxriver76) allow null for object.states also for extend calls for now
              • (foxriver76) enable sets on migration to redis if allowed
              • (Apollon77) Make sure adapters that are stopped on update are not enabled too early
              • (Apollon77) Optimize some special cases on adapter start

              @crunchip Dein backitup upgrade Problem sollte damit gelöst sein und die Module-spezifischen Rebuilds bei Node-JS updates sollten auch besser tun (na, mag nochmal jemand Node.js upgraden oder so? ;-)) )

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

              @apollon77 Hier ist js-controller 4.0.10 absolut unauffaellig auf multihost:
              lxc debian 10, node 14, npm 6
              und 3x auf lxc debian 11, node 16, npm 8,
              auf armv6 (raspi-zero) debian 10, node 14, npm 6,
              auf armv7 debian 11, node 14, npm 6.

              Es sind insgesamt 61 Adapter auf 6 Hosts aufgeteilt im Einsatz.
              Datenbank redis/redis ( die schaufelt sich bei mir tot, aber das ist ein anderes topic..hab mal ausgemistet, nur noch ca. 60000 States..)

              1 Reply Last reply
              1
              • crunchipC Away
                crunchipC Away
                crunchip
                Forum Testing Most Active
                wrote on last edited by crunchip
                #361

                hab auch gerade gesehen, das die CPU erhöht ist
                was hatte ich gestern Mittag gemacht

                • testweise backitup eine Version zurück und wieder hoch
                  danach
                • die gestrigen anstehenden Adapter update's (welche es alle waren, kann ich nicht mehr genau sagen)
                  Log ist unauffällig
                  js-controller noch 4.0.9

                werde ioBroker mal neu starten und beobachten wie es sich dann verhält
                5074dd62-0d92-415e-8ede-b930ff91156a-image.png 63f42558-501a-4caa-8e39-c0aae7f53ba6-image.png

                umgestiegen von Proxmox auf Unraid

                apollon77A 1 Reply Last reply
                0
                • crunchipC crunchip

                  hab auch gerade gesehen, das die CPU erhöht ist
                  was hatte ich gestern Mittag gemacht

                  • testweise backitup eine Version zurück und wieder hoch
                    danach
                  • die gestrigen anstehenden Adapter update's (welche es alle waren, kann ich nicht mehr genau sagen)
                    Log ist unauffällig
                    js-controller noch 4.0.9

                  werde ioBroker mal neu starten und beobachten wie es sich dann verhält
                  5074dd62-0d92-415e-8ede-b930ff91156a-image.png 63f42558-501a-4caa-8e39-c0aae7f53ba6-image.png

                  apollon77A Offline
                  apollon77A Offline
                  apollon77
                  wrote on last edited by
                  #362

                  @crunchip Jarvis mit 50% CPU? Krass ... ist das "stabil" so? Dann würde ich da mal anfangen weil es der höchste ausreisser ist - vor allem falls es da gestern ein Update gab?

                  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
                  crunchipC 1 Reply Last reply
                  0
                  • apollon77A apollon77

                    @thomas-braun ja da bist du die Ausnahme. Der sollte dann direkt beim „ grossen“ rebuild mit gehen.

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    wrote on last edited by
                    #363

                    @apollon77

                    nodejs von 16 auf 17 gehoben, rebuilds sehen so aus:

                    parcels:

                    2022-02-16 09:03:06.052  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                    2022-02-16 09:03:06.088  - info: host.chet iobroker npm-rebuild:
                    2022-02-16 09:03:06.089  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                    2022-02-16 09:03:07.102  - info: host.chet iobroker npm-rebuild: exit 0
                    2022-02-16 09:03:07.268  - info: host.chet instance system.adapter.parcel.0 started with pid 122219
                    2022-02-16 09:03:10.567  - info: parcel.0 (122219) starting. Version 0.0.2 (non-npm: TA2k/ioBroker.parcel#ad3587a3ea6d5d80cfe97e27ceff87767057a4a7) in /opt/iobroker/node_modules/iobroker.parcel, node: v17.5.0, js-controller: 4.0.10
                    

                    zigbee:
                    Musste gar nicht neugebaut werden, ist direkt gestartet:

                    2022-02-16 09:05:55.867  - info: host.chet "system.adapter.zigbee.0" enabled
                    2022-02-16 09:05:56.083  - info: host.chet instance system.adapter.zigbee.0 started with pid 122335
                    2022-02-16 09:05:59.651  - info: zigbee.0 (122335) starting. Version 1.6.15 in /opt/iobroker/node_modules/iobroker.zigbee, node: v17.5.0, js-controller: 4.0.10
                    2022-02-16 09:05:59.755  - info: zigbee.0 (122335) Starting Zigbee  npm ...
                    2022-02-16 09:06:00.236  - info: zigbee.0 (122335) Installed Version: iobroker.zigbee@1.6.15
                    2022-02-16 09:06:11.226  - info: zigbee.0 (122335) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220103}}
                    2022-02-16 09:06:11.235  - info: zigbee.0 (122335) Unable to disable LED, unsupported function.
                    2022-02-16 09:06:11.248  - info: zigbee.0 (122335)   --> transmitPower : normal
                    2022-02-16 09:06:11.257  - info: zigbee.0 (122335) Currently no devices.
                    2022-02-16 09:06:11.258  - info: zigbee.0 (122335) Zigbee started
                    

                    ble:
                    Baut nicht.

                    2022-02-16 09:08:01.036  - info: host.chet "system.adapter.ble.0" enabled
                    2022-02-16 09:08:01.239  - info: host.chet instance system.adapter.ble.0 started with pid 122373
                    2022-02-16 09:08:02.703  - info: ble.0 (122373) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                    2022-02-16 09:08:02.772  - info: ble.0 (122373) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                    2022-02-16 09:08:02.774  - info: ble.0 (122373) enabled plugins: _default
                    2022-02-16 09:08:02.776  - info: ble.0 (122373) monitored services:
                    2022-02-16 09:08:02.779  - info: ble.0 (122373) starting scanner process...
                    2022-02-16 09:08:03.217  - error: ble.0 (122373) Terminating because A dependency requires a rebuild.
                    2022-02-16 09:08:03.342  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                    2022-02-16 09:08:03.342  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                    2022-02-16 09:08:03.343  - info: host.chet system.adapter.ble.0 will be rebuilt
                    2022-02-16 09:08:03.343  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt
                    2022-02-16 09:08:03.344  - info: host.chet iobroker rebuild
                    2022-02-16 09:08:04.303  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                    2022-02-16 09:09:43.510  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                    2022-02-16 09:09:43.546  - info: host.chet iobroker npm-rebuild:
                    2022-02-16 09:09:43.547  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                    2022-02-16 09:09:44.562  - info: host.chet iobroker npm-rebuild: exit 0
                    2022-02-16 09:09:44.688  - info: host.chet instance system.adapter.ble.0 started with pid 123582
                    2022-02-16 09:09:46.203  - info: ble.0 (123582) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                    2022-02-16 09:09:46.274  - info: ble.0 (123582) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                    2022-02-16 09:09:46.276  - info: ble.0 (123582) enabled plugins: _default
                    2022-02-16 09:09:46.279  - info: ble.0 (123582) monitored services:
                    2022-02-16 09:09:46.282  - info: ble.0 (123582) starting scanner process...
                    2022-02-16 09:09:46.702  - error: ble.0 (123582) Terminating because A dependency requires a rebuild.
                    2022-02-16 09:09:46.793  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                    2022-02-16 09:09:46.794  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                    2022-02-16 09:09:46.795  - info: host.chet system.adapter.ble.0 will be rebuilt
                    2022-02-16 09:09:46.795  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt
                    2022-02-16 09:09:46.796  - info: host.chet iobroker rebuild
                    2022-02-16 09:09:47.804  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                    2022-02-16 09:11:27.627  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                    2022-02-16 09:11:27.663  - info: host.chet iobroker npm-rebuild:
                    2022-02-16 09:11:27.665  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                    2022-02-16 09:11:28.677  - info: host.chet iobroker npm-rebuild: exit 0
                    2022-02-16 09:11:28.824  - info: host.chet instance system.adapter.ble.0 started with pid 124791
                    2022-02-16 09:11:30.315  - info: ble.0 (124791) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                    2022-02-16 09:11:30.384  - info: ble.0 (124791) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                    2022-02-16 09:11:30.386  - info: ble.0 (124791) enabled plugins: _default
                    2022-02-16 09:11:30.389  - info: ble.0 (124791) monitored services:
                    2022-02-16 09:11:30.392  - info: ble.0 (124791) starting scanner process...
                    2022-02-16 09:11:30.827  - error: ble.0 (124791) Terminating because A dependency requires a rebuild.
                    2022-02-16 09:11:30.947  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                    2022-02-16 09:11:30.948  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                    2022-02-16 09:11:30.949  - info: host.chet system.adapter.ble.0 will be rebuilt
                    2022-02-16 09:11:30.949  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt
                    2022-02-16 09:11:30.950  - info: host.chet iobroker rebuild
                    2022-02-16 09:11:31.909  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                    2022-02-16 09:13:10.557  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                    2022-02-16 09:13:10.598  - info: host.chet iobroker npm-rebuild:
                    2022-02-16 09:13:10.599  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                    2022-02-16 09:13:11.613  - info: host.chet iobroker npm-rebuild: exit 0
                    2022-02-16 09:13:11.739  - info: host.chet instance system.adapter.ble.0 started with pid 125988
                    2022-02-16 09:13:13.276  - info: ble.0 (125988) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                    2022-02-16 09:13:13.355  - info: ble.0 (125988) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                    2022-02-16 09:13:13.356  - info: ble.0 (125988) enabled plugins: _default
                    2022-02-16 09:13:13.359  - info: ble.0 (125988) monitored services:
                    2022-02-16 09:13:13.362  - info: ble.0 (125988) starting scanner process...
                    2022-02-16 09:13:13.793  - error: ble.0 (125988) Terminating because A dependency requires a rebuild.
                    2022-02-16 09:13:13.926  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                    2022-02-16 09:13:13.934  - info: host.chet 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.
                    

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

                    1 Reply Last reply
                    0
                    • apollon77A apollon77

                      @crunchip Jarvis mit 50% CPU? Krass ... ist das "stabil" so? Dann würde ich da mal anfangen weil es der höchste ausreisser ist - vor allem falls es da gestern ein Update gab?

                      crunchipC Away
                      crunchipC Away
                      crunchip
                      Forum Testing Most Active
                      wrote on last edited by
                      #364

                      @apollon77 ne jarvis war nicht dabei bei den update's.
                      Nach dem iob Neustart hat sich das nun wieder normalisiert.
                      Ich hatte das schonmal, das nach ein paar update's die Cpu so hoch ging und auch so geblieben ist, jedoch nicht weiter darauf geachtet, was dies verursachte.
                      Kann es sein, das dies die Ursache sein kann, wenn man mehrere Adapter Update's hintereinander reinballert?

                      umgestiegen von Proxmox auf Unraid

                      apollon77A 1 Reply Last reply
                      0
                      • crunchipC crunchip

                        @apollon77 ne jarvis war nicht dabei bei den update's.
                        Nach dem iob Neustart hat sich das nun wieder normalisiert.
                        Ich hatte das schonmal, das nach ein paar update's die Cpu so hoch ging und auch so geblieben ist, jedoch nicht weiter darauf geachtet, was dies verursachte.
                        Kann es sein, das dies die Ursache sein kann, wenn man mehrere Adapter Update's hintereinander reinballert?

                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        wrote on last edited by
                        #365

                        @crunchip sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                        Kann es sein, das dies die Ursache sein kann, wenn man mehrere Adapter Update's hintereinander reinballert?

                        Wüsste nicht wie ... Adapter werden dabei Restartet, das wars aber an sich.

                        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
                        • apollon77A apollon77

                          hallo,

                          mit dem Feedback der letzten tage habe ich heute den js-controller 4.0.10, aka Stable-RC2 für Euch. Enthalten ist:

                          4.0.10 (2022-02-15)

                          • (foxriver76) Fix module specific rebuild command
                          • (foxriver76) allow null for object.states also for extend calls for now
                          • (foxriver76) enable sets on migration to redis if allowed
                          • (Apollon77) Make sure adapters that are stopped on update are not enabled too early
                          • (Apollon77) Optimize some special cases on adapter start

                          @crunchip Dein backitup upgrade Problem sollte damit gelöst sein und die Module-spezifischen Rebuilds bei Node-JS updates sollten auch besser tun (na, mag nochmal jemand Node.js upgraden oder so? ;-)) )

                          DiginixD Offline
                          DiginixD Offline
                          Diginix
                          wrote on last edited by
                          #366

                          @apollon77 Update von 4.0.9 auf 4.0.10 unauffällig.
                          Was hat es mit dieser "redis" Zeile eigentlich auf sich auch wenn jsonl verwendet wird?

                          Successfully migrated 18606 objects to Redis Sets

                          ..:: So long! Tom ::..

                          NUC7i3 (Ubuntu Proxmox VM) | Echo Dots 2+3. Gen | Xiaomi Sensoren | Mi Robot 1S | Yeelight | Sonoff | Shelly | H801 RGB | Gosund SP1 | NodeMCU+ESP32 | Kostal Plenticore PV+BYD | openWB

                          foxriver76F apollon77A 2 Replies Last reply
                          0
                          • DiginixD Diginix

                            @apollon77 Update von 4.0.9 auf 4.0.10 unauffällig.
                            Was hat es mit dieser "redis" Zeile eigentlich auf sich auch wenn jsonl verwendet wird?

                            Successfully migrated 18606 objects to Redis Sets

                            foxriver76F Offline
                            foxriver76F Offline
                            foxriver76
                            Developer
                            wrote on last edited by
                            #367

                            @diginix Aktuell nichts. Der Client weiß nicht ob er mit JSONL/File oder echtem Redis Server sprich

                            Videotutorials & mehr

                            Hier könnt ihr mich unterstützen.

                            1 Reply Last reply
                            1
                            • DiginixD Diginix

                              @apollon77 Update von 4.0.9 auf 4.0.10 unauffällig.
                              Was hat es mit dieser "redis" Zeile eigentlich auf sich auch wenn jsonl verwendet wird?

                              Successfully migrated 18606 objects to Redis Sets

                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              wrote on last edited by
                              #368

                              @diginix Die Datenbank arbeitet generisch - die weiss also nicht ob ein echter Redis auf der gegenseite ist oder nur der "iobroker DB Server" (der Redis simuliert). Und der Simulator tut einfach so als ob er die Sets Migration mitmacht ... Von daher ... ignorieren

                              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
                              crunchipC Thomas BraunT 2 Replies Last reply
                              1
                              • apollon77A apollon77

                                @diginix Die Datenbank arbeitet generisch - die weiss also nicht ob ein echter Redis auf der gegenseite ist oder nur der "iobroker DB Server" (der Redis simuliert). Und der Simulator tut einfach so als ob er die Sets Migration mitmacht ... Von daher ... ignorieren

                                crunchipC Away
                                crunchipC Away
                                crunchip
                                Forum Testing Most Active
                                wrote on last edited by crunchip
                                #369

                                @apollon77 ist mir gerade eingefallen, der redis Server läuft noch in meiner VM, da ich aber vor langer Zeit auf jsonl umgestellt habe, wird dieser doch nicht mehr benötigt, oder?
                                unter anderem bin ich soeben auf v4.0.10

                                2022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed
                                2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed.
                                2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed.
                                2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
                                2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
                                2022-02-16 10:00:45.897 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM
                                2022-02-16 10:00:45.962 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.139 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM
                                2022-02-16 10:00:46.313 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.314 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.374 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.485 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.634 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.635 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.736 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.803 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                                2022-02-16 10:00:46.804 - error: host.IoBroker Caught by controller[0]: Error: DB closed
                                2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Object.onceWrapper (events.js:520:26)
                                2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Socket.emit (events.js:400:28)
                                2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at Socket.emit (domain.js:475:12)
                                2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at TCP. (net.js:686:12)
                                2022-02-16 10:00:46.808 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.977 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM
                                2022-02-16 10:00:46.978 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM
                                2022-02-16 10:00:47.077 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM
                                2022-02-16 10:00:47.182 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM
                                2022-02-16 10:00:47.332 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM
                                2022-02-16 10:00:47.334 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM
                                2022-02-16 10:00:47.405 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM
                                2022-02-16 10:00:48.164 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM
                                

                                umgestiegen von Proxmox auf Unraid

                                apollon77A 1 Reply Last reply
                                0
                                • crunchipC crunchip

                                  @apollon77 ist mir gerade eingefallen, der redis Server läuft noch in meiner VM, da ich aber vor langer Zeit auf jsonl umgestellt habe, wird dieser doch nicht mehr benötigt, oder?
                                  unter anderem bin ich soeben auf v4.0.10

                                  2022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                  2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed
                                  2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                  2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed.
                                  2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                  2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed.
                                  2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
                                  2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
                                  2022-02-16 10:00:45.897 - warn: host.IoBroker instance system.adapter.admin.0 terminated due to SIGTERM
                                  2022-02-16 10:00:45.962 - warn: host.IoBroker instance system.adapter.email.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.139 - warn: host.IoBroker instance system.adapter.telegram.1 terminated due to SIGTERM
                                  2022-02-16 10:00:46.313 - warn: host.IoBroker instance system.adapter.sonoff.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.314 - warn: host.IoBroker instance system.adapter.zigbee.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.374 - warn: host.IoBroker instance system.adapter.nut.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.485 - warn: host.IoBroker instance system.adapter.ble.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.634 - warn: host.IoBroker instance system.adapter.echarts.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.635 - warn: host.IoBroker instance system.adapter.mihome.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.736 - warn: host.IoBroker instance system.adapter.telegram.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.803 - error: host.IoBroker Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                                  2022-02-16 10:00:46.804 - error: host.IoBroker Caught by controller[0]: Error: DB closed
                                  2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                  2022-02-16 10:00:46.805 - error: host.IoBroker Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                  2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Object.onceWrapper (events.js:520:26)
                                  2022-02-16 10:00:46.806 - error: host.IoBroker Caught by controller[0]: at Socket.emit (events.js:400:28)
                                  2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at Socket.emit (domain.js:475:12)
                                  2022-02-16 10:00:46.807 - error: host.IoBroker Caught by controller[0]: at TCP. (net.js:686:12)
                                  2022-02-16 10:00:46.808 - warn: host.IoBroker instance system.adapter.shelly.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.977 - warn: host.IoBroker instance system.adapter.tr-064.0 terminated due to SIGTERM
                                  2022-02-16 10:00:46.978 - warn: host.IoBroker instance system.adapter.virtualpowermeter.0 terminated due to SIGTERM
                                  2022-02-16 10:00:47.077 - warn: host.IoBroker instance system.adapter.backitup.0 terminated due to SIGTERM
                                  2022-02-16 10:00:47.182 - warn: host.IoBroker instance system.adapter.broadlink2.0 terminated due to SIGTERM
                                  2022-02-16 10:00:47.332 - warn: host.IoBroker instance system.adapter.chromecast.0 terminated due to SIGTERM
                                  2022-02-16 10:00:47.334 - warn: host.IoBroker instance system.adapter.fully-tablet-control.0 terminated due to SIGTERM
                                  2022-02-16 10:00:47.405 - warn: host.IoBroker instance system.adapter.info.0 terminated due to SIGTERM
                                  2022-02-16 10:00:48.164 - warn: host.IoBroker instance system.adapter.iot.0 terminated due to SIGTERM
                                  
                                  apollon77A Offline
                                  apollon77A Offline
                                  apollon77
                                  wrote on last edited by
                                  #370

                                  @crunchip Alaso der Fehler hier mit "DB Closed" liegt wohl eher daran das der sonoff Adapter noch Dinge abarbeitet obwohl er schon damit hätte aufhören sollen weil er gestoppt wird. Das ist ein Adapter-Issue wert.

                                  Ob Du jetzt Redis oder jsonl hast musst Du wissen ... aber wenn da ein Redis ist der nicht genutzt wird dann sollte der zwar RAM brauchen aber sich sonst mega langweilen

                                  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
                                  crunchipC 1 Reply Last reply
                                  0
                                  • apollon77A apollon77

                                    @diginix Die Datenbank arbeitet generisch - die weiss also nicht ob ein echter Redis auf der gegenseite ist oder nur der "iobroker DB Server" (der Redis simuliert). Und der Simulator tut einfach so als ob er die Sets Migration mitmacht ... Von daher ... ignorieren

                                    Thomas BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    wrote on last edited by
                                    #371

                                    @apollon77

                                    ble-build

                                    main.js auf

                                    else if (/NODE_MODULE_VERSION/.test(err.message) && ((_a = adapter.supportsFeature) === null || _a === void 0 ? void 0 : _a.call(adapter, "CONTROLLER_NPM_AUTO_REBUILD"))) {
                                            console.error(err.message);
                                            terminate("A dependency requires a rebuild.", 13);
                                        }
                                    

                                    geändert. Rebuild schaut nun so aus:

                                    2022-02-16 10:29:20.525  - info: ble.0 (133617) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                    2022-02-16 10:29:20.625  - info: ble.0 (133617) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                    2022-02-16 10:29:20.627  - info: ble.0 (133617) enabled plugins: _default
                                    2022-02-16 10:29:20.629  - info: ble.0 (133617) monitored services:
                                    2022-02-16 10:29:20.632  - info: ble.0 (133617) starting scanner process...
                                    2022-02-16 10:29:21.052  - error: ble.0 (133617) Terminating because A dependency requires a rebuild.
                                    2022-02-16 10:29:21.138  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                    2022-02-16 10:29:21.139  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                    2022-02-16 10:29:21.139  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                    2022-02-16 10:29:21.140  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                    2022-02-16 10:29:21.140  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                    2022-02-16 10:29:21.141  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                    2022-02-16 10:29:21.141  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                                    2022-02-16 10:29:21.146  - info: host.chet system.adapter.ble.0 will be rebuilt
                                    2022-02-16 10:29:21.148  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt
                                    2022-02-16 10:29:21.148  - info: host.chet iobroker rebuild
                                    2022-02-16 10:29:22.218  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                                    2022-02-16 10:31:07.465  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                    2022-02-16 10:31:07.500  - info: host.chet iobroker npm-rebuild:
                                    2022-02-16 10:31:07.502  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                    2022-02-16 10:31:08.515  - info: host.chet iobroker npm-rebuild: exit 0
                                    2022-02-16 10:31:08.770  - info: host.chet instance system.adapter.ble.0 started with pid 134847
                                    2022-02-16 10:31:10.403  - info: ble.0 (134847) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                    2022-02-16 10:31:10.474  - info: ble.0 (134847) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                    2022-02-16 10:31:10.476  - info: ble.0 (134847) enabled plugins: _default
                                    2022-02-16 10:31:10.478  - info: ble.0 (134847) monitored services:
                                    2022-02-16 10:31:10.482  - info: ble.0 (134847) starting scanner process...
                                    2022-02-16 10:31:10.929  - error: ble.0 (134847) Terminating because A dependency requires a rebuild.
                                    2022-02-16 10:31:11.016  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                    2022-02-16 10:31:11.017  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                    2022-02-16 10:31:11.017  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                    2022-02-16 10:31:11.018  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                    2022-02-16 10:31:11.018  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                    2022-02-16 10:31:11.018  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                    2022-02-16 10:31:11.019  - info: host.chet Adapter system.adapter.ble.0 needs rebuild of @abandonware/bluetooth-hci-socket and will be restarted afterwards.
                                    2022-02-16 10:31:11.020  - info: host.chet system.adapter.ble.0 will be rebuilt (Args: {"path":"/opt/iobroker/node_modules/@abandonware","module":"@abandonware/bluetooth-hci-socket","version":"0.5.3-8"})
                                    2022-02-16 10:31:11.020  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt
                                    2022-02-16 10:31:11.021  - info: host.chet iobroker rebuild @abandonware/bluetooth-hci-socket@0.5.3-8 --path /opt/iobroker/node_modules/@abandonware
                                    2022-02-16 10:31:12.014  - info: host.chet iobroker npm-rebuild: Rebuilding native module "@abandonware/bluetooth-hci-socket@0.5.3-8" in /opt/iobroker/node_modules/@abandonware ...
                                    2022-02-16 10:31:22.338  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                    2022-02-16 10:31:22.384  - info: host.chet iobroker npm-rebuild:
                                    2022-02-16 10:31:22.385  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                    2022-02-16 10:31:23.401  - info: host.chet iobroker npm-rebuild: exit 0
                                    2022-02-16 10:31:23.561  - info: host.chet instance system.adapter.ble.0 started with pid 134906
                                    2022-02-16 10:31:25.124  - info: ble.0 (134906) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                    2022-02-16 10:31:25.195  - info: ble.0 (134906) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                    2022-02-16 10:31:25.197  - info: ble.0 (134906) enabled plugins: _default
                                    2022-02-16 10:31:25.199  - info: ble.0 (134906) monitored services:
                                    2022-02-16 10:31:25.202  - info: ble.0 (134906) starting scanner process...
                                    2022-02-16 10:31:25.641  - error: ble.0 (134906) Terminating because A dependency requires a rebuild.
                                    2022-02-16 10:31:25.729  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                    2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                    2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                    2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                    2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                    2022-02-16 10:31:25.731  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                    2022-02-16 10:31:25.731  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                                    2022-02-16 10:31:25.731  - info: host.chet system.adapter.ble.0 will be rebuilt
                                    2022-02-16 10:31:25.732  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt
                                    2022-02-16 10:31:25.732  - info: host.chet iobroker rebuild
                                    2022-02-16 10:31:26.713  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                                    2022-02-16 10:33:07.966  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                    2022-02-16 10:33:08.004  - info: host.chet iobroker npm-rebuild:
                                    2022-02-16 10:33:08.005  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                    2022-02-16 10:33:09.020  - info: host.chet iobroker npm-rebuild: exit 0
                                    2022-02-16 10:33:09.190  - info: host.chet instance system.adapter.ble.0 started with pid 136127
                                    2022-02-16 10:33:10.749  - info: ble.0 (136127) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                    2022-02-16 10:33:10.842  - info: ble.0 (136127) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                    2022-02-16 10:33:10.843  - info: ble.0 (136127) enabled plugins: _default
                                    2022-02-16 10:33:10.845  - info: ble.0 (136127) monitored services:
                                    2022-02-16 10:33:10.849  - info: ble.0 (136127) starting scanner process...
                                    2022-02-16 10:33:11.293  - error: ble.0 (136127) Terminating because A dependency requires a rebuild.
                                    2022-02-16 10:33:11.387  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                    2022-02-16 10:33:11.388  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                    2022-02-16 10:33:11.388  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                    2022-02-16 10:33:11.389  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                    2022-02-16 10:33:11.389  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                    2022-02-16 10:33:11.389  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                    2022-02-16 10:33:11.389  - info: host.chet 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.
                                    

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

                                    apollon77A 1 Reply Last reply
                                    0
                                    • Thomas BraunT Thomas Braun

                                      @apollon77

                                      ble-build

                                      main.js auf

                                      else if (/NODE_MODULE_VERSION/.test(err.message) && ((_a = adapter.supportsFeature) === null || _a === void 0 ? void 0 : _a.call(adapter, "CONTROLLER_NPM_AUTO_REBUILD"))) {
                                              console.error(err.message);
                                              terminate("A dependency requires a rebuild.", 13);
                                          }
                                      

                                      geändert. Rebuild schaut nun so aus:

                                      2022-02-16 10:29:20.525  - info: ble.0 (133617) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                      2022-02-16 10:29:20.625  - info: ble.0 (133617) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                      2022-02-16 10:29:20.627  - info: ble.0 (133617) enabled plugins: _default
                                      2022-02-16 10:29:20.629  - info: ble.0 (133617) monitored services:
                                      2022-02-16 10:29:20.632  - info: ble.0 (133617) starting scanner process...
                                      2022-02-16 10:29:21.052  - error: ble.0 (133617) Terminating because A dependency requires a rebuild.
                                      2022-02-16 10:29:21.138  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                      2022-02-16 10:29:21.139  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                      2022-02-16 10:29:21.139  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                      2022-02-16 10:29:21.140  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                      2022-02-16 10:29:21.140  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                      2022-02-16 10:29:21.141  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                      2022-02-16 10:29:21.141  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                                      2022-02-16 10:29:21.146  - info: host.chet system.adapter.ble.0 will be rebuilt
                                      2022-02-16 10:29:21.148  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 1 attempt
                                      2022-02-16 10:29:21.148  - info: host.chet iobroker rebuild
                                      2022-02-16 10:29:22.218  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                                      2022-02-16 10:31:07.465  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                      2022-02-16 10:31:07.500  - info: host.chet iobroker npm-rebuild:
                                      2022-02-16 10:31:07.502  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                      2022-02-16 10:31:08.515  - info: host.chet iobroker npm-rebuild: exit 0
                                      2022-02-16 10:31:08.770  - info: host.chet instance system.adapter.ble.0 started with pid 134847
                                      2022-02-16 10:31:10.403  - info: ble.0 (134847) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                      2022-02-16 10:31:10.474  - info: ble.0 (134847) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                      2022-02-16 10:31:10.476  - info: ble.0 (134847) enabled plugins: _default
                                      2022-02-16 10:31:10.478  - info: ble.0 (134847) monitored services:
                                      2022-02-16 10:31:10.482  - info: ble.0 (134847) starting scanner process...
                                      2022-02-16 10:31:10.929  - error: ble.0 (134847) Terminating because A dependency requires a rebuild.
                                      2022-02-16 10:31:11.016  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                      2022-02-16 10:31:11.017  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                      2022-02-16 10:31:11.017  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                      2022-02-16 10:31:11.018  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                      2022-02-16 10:31:11.018  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                      2022-02-16 10:31:11.018  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                      2022-02-16 10:31:11.019  - info: host.chet Adapter system.adapter.ble.0 needs rebuild of @abandonware/bluetooth-hci-socket and will be restarted afterwards.
                                      2022-02-16 10:31:11.020  - info: host.chet system.adapter.ble.0 will be rebuilt (Args: {"path":"/opt/iobroker/node_modules/@abandonware","module":"@abandonware/bluetooth-hci-socket","version":"0.5.3-8"})
                                      2022-02-16 10:31:11.020  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 2 attempt
                                      2022-02-16 10:31:11.021  - info: host.chet iobroker rebuild @abandonware/bluetooth-hci-socket@0.5.3-8 --path /opt/iobroker/node_modules/@abandonware
                                      2022-02-16 10:31:12.014  - info: host.chet iobroker npm-rebuild: Rebuilding native module "@abandonware/bluetooth-hci-socket@0.5.3-8" in /opt/iobroker/node_modules/@abandonware ...
                                      2022-02-16 10:31:22.338  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                      2022-02-16 10:31:22.384  - info: host.chet iobroker npm-rebuild:
                                      2022-02-16 10:31:22.385  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                      2022-02-16 10:31:23.401  - info: host.chet iobroker npm-rebuild: exit 0
                                      2022-02-16 10:31:23.561  - info: host.chet instance system.adapter.ble.0 started with pid 134906
                                      2022-02-16 10:31:25.124  - info: ble.0 (134906) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                      2022-02-16 10:31:25.195  - info: ble.0 (134906) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                      2022-02-16 10:31:25.197  - info: ble.0 (134906) enabled plugins: _default
                                      2022-02-16 10:31:25.199  - info: ble.0 (134906) monitored services:
                                      2022-02-16 10:31:25.202  - info: ble.0 (134906) starting scanner process...
                                      2022-02-16 10:31:25.641  - error: ble.0 (134906) Terminating because A dependency requires a rebuild.
                                      2022-02-16 10:31:25.729  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                      2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                      2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                      2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                      2022-02-16 10:31:25.730  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                      2022-02-16 10:31:25.731  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                      2022-02-16 10:31:25.731  - info: host.chet Adapter system.adapter.ble.0 needs rebuild and will be restarted afterwards.
                                      2022-02-16 10:31:25.731  - info: host.chet system.adapter.ble.0 will be rebuilt
                                      2022-02-16 10:31:25.732  - warn: host.chet adapter "ble" seems to be installed for a different version of Node.js. Trying to rebuild it... 3 attempt
                                      2022-02-16 10:31:25.732  - info: host.chet iobroker rebuild
                                      2022-02-16 10:31:26.713  - info: host.chet iobroker npm-rebuild: Rebuilding native modules ...
                                      2022-02-16 10:33:07.966  - info: host.chet iobroker npm-rebuild: rebuilt dependencies successfully
                                      2022-02-16 10:33:08.004  - info: host.chet iobroker npm-rebuild:
                                      2022-02-16 10:33:08.005  - info: host.chet iobroker npm-rebuild: Rebuilding native modules done
                                      2022-02-16 10:33:09.020  - info: host.chet iobroker npm-rebuild: exit 0
                                      2022-02-16 10:33:09.190  - info: host.chet instance system.adapter.ble.0 started with pid 136127
                                      2022-02-16 10:33:10.749  - info: ble.0 (136127) starting. Version 0.12.0 in /opt/iobroker/node_modules/iobroker.ble, node: v17.5.0, js-controller: 4.0.10
                                      2022-02-16 10:33:10.842  - info: ble.0 (136127) loaded plugins: Xiaomi, mi-flora, ruuvi-tag, _default
                                      2022-02-16 10:33:10.843  - info: ble.0 (136127) enabled plugins: _default
                                      2022-02-16 10:33:10.845  - info: ble.0 (136127) monitored services:
                                      2022-02-16 10:33:10.849  - info: ble.0 (136127) starting scanner process...
                                      2022-02-16 10:33:11.293  - error: ble.0 (136127) Terminating because A dependency requires a rebuild.
                                      2022-02-16 10:33:11.387  - error: host.chet Caught by controller[0]: The module '/opt/iobroker/node_modules/@abandonware/bluetooth-hci-socket/lib/binding/bluetooth_hci_socket.node'
                                      2022-02-16 10:33:11.388  - error: host.chet Caught by controller[0]: was compiled against a different Node.js version using
                                      2022-02-16 10:33:11.388  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
                                      2022-02-16 10:33:11.389  - error: host.chet Caught by controller[0]: NODE_MODULE_VERSION 102. Please try re-compiling or re-installing
                                      2022-02-16 10:33:11.389  - error: host.chet Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
                                      2022-02-16 10:33:11.389  - info: host.chet instance system.adapter.ble.0 requested a rebuild of its dependencies and will be restarted after that is done.
                                      2022-02-16 10:33:11.389  - info: host.chet 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.
                                      
                                      apollon77A Offline
                                      apollon77A Offline
                                      apollon77
                                      wrote on last edited by
                                      #372

                                      @thomas-braun sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                      2022-02-16 10:31:11.021 - info: host.chet iobroker rebuild @abandonware/bluetooth-hci-socket@0.5.3-8 --path /opt/iobroker/node_modules/@abandonware

                                      Die zeile wollte ich sehen ... cooollll. Danke

                                      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
                                      • apollon77A apollon77

                                        @crunchip Alaso der Fehler hier mit "DB Closed" liegt wohl eher daran das der sonoff Adapter noch Dinge abarbeitet obwohl er schon damit hätte aufhören sollen weil er gestoppt wird. Das ist ein Adapter-Issue wert.

                                        Ob Du jetzt Redis oder jsonl hast musst Du wissen ... aber wenn da ein Redis ist der nicht genutzt wird dann sollte der zwar RAM brauchen aber sich sonst mega langweilen

                                        crunchipC Away
                                        crunchipC Away
                                        crunchip
                                        Forum Testing Most Active
                                        wrote on last edited by
                                        #373

                                        @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                        Ob Du jetzt Redis oder jsonl hast musst Du wissen

                                        ich schrieb ja, ich verwende jsonl, deswegen verwirren die redis Meldungen etwas. Dachte vllt es hat in irgendeiner Weise Einfluss, wenn der Redis Server zusätzlich läuft.
                                        ging eher um die error Meldungen vom Host

                                        issue für sonoff kann ich erstellen,
                                        für shelly werd ich wohl auch eins erstellen müssen, dieser wirft auch Fehler beim beenden.

                                        2022-02-16 10:00:38.419 - error: shelly.0 (24062) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                        2022-02-16 10:00:38.439 - info: virtualpowermeter.0 (26009) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.420 - error: shelly.0 (24062) unhandled promise rejection: DB closed
                                        2022-02-16 10:00:38.441 - error: shelly.0 (24062) Error: DB closed
                                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                        at Object.onceWrapper (events.js:520:26)
                                        at Socket.emit (events.js:400:28)
                                        at Socket.emit (domain.js:475:12)
                                        at TCP. (net.js:686:12)
                                        2022-02-16 10:00:38.442 - error: shelly.0 (24062) DB closed
                                        2022-02-16 10:00:38.460 - info: zigbee.0 (24311) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.464 - info: echarts.0 (24809) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                        2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed
                                        2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                        2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed.
                                        2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                        2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed.
                                        2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
                                        2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
                                        

                                        umgestiegen von Proxmox auf Unraid

                                        apollon77A 1 Reply Last reply
                                        0
                                        • crunchipC crunchip

                                          @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

                                          Ob Du jetzt Redis oder jsonl hast musst Du wissen

                                          ich schrieb ja, ich verwende jsonl, deswegen verwirren die redis Meldungen etwas. Dachte vllt es hat in irgendeiner Weise Einfluss, wenn der Redis Server zusätzlich läuft.
                                          ging eher um die error Meldungen vom Host

                                          issue für sonoff kann ich erstellen,
                                          für shelly werd ich wohl auch eins erstellen müssen, dieser wirft auch Fehler beim beenden.

                                          2022-02-16 10:00:38.419 - error: shelly.0 (24062) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                                          2022-02-16 10:00:38.439 - info: virtualpowermeter.0 (26009) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.420 - error: shelly.0 (24062) unhandled promise rejection: DB closed
                                          2022-02-16 10:00:38.441 - error: shelly.0 (24062) Error: DB closed
                                          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                          at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                          at Object.onceWrapper (events.js:520:26)
                                          at Socket.emit (events.js:400:28)
                                          at Socket.emit (domain.js:475:12)
                                          at TCP. (net.js:686:12)
                                          2022-02-16 10:00:38.442 - error: shelly.0 (24062) DB closed
                                          2022-02-16 10:00:38.460 - info: zigbee.0 (24311) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.464 - info: echarts.0 (24809) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.466 - info: telegram.0 (23965) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.463 - info: telegram.1 (23984) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.468 - info: web.0 (26298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:38.466 - info: text2command.0 (25980) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                                          2022-02-16 10:00:39.190 - warn: sonoff.0 (24255) get state error: DB closed
                                          2022-02-16 10:00:39.296 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                          2022-02-16 10:00:39.324 - warn: sonoff.0 (24255) redis get sonoff.0.Kaffeeautomat.alive, error - Connection is closed.
                                          2022-02-16 10:00:39.347 - warn: sonoff.0 (24255) redis get sonoff.0.PC-Server.alive, error - Connection is closed.
                                          2022-02-16 10:00:39.511 - warn: sonoff.0 (24255) get state error: Connection is closed.
                                          2022-02-16 10:00:39.814 - warn: host.IoBroker instance system.adapter.milight-smart-light.0 terminated due to SIGTERM
                                          2022-02-16 10:00:40.460 - warn: host.IoBroker instance system.adapter.sayit.0 terminated due to SIGTERM
                                          
                                          apollon77A Offline
                                          apollon77A Offline
                                          apollon77
                                          wrote on last edited by
                                          #374

                                          @crunchip Ja bitte issues wenn es keine gibt. Am Ende ist es so: Wir nutzen das Redis Protokoll zur Kommunikation mit der DB ... egal ob echter oder unserer eigenen DB ...

                                          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
                                          crunchipC 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

                                          580

                                          Online

                                          32.7k

                                          Users

                                          82.5k

                                          Topics

                                          1.3m

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

                                          • Don't have an account? Register

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