Weiter zum Inhalt
  • Home
  • Aktuell
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Hell
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dunkel
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. unregelmäßig Unmotivierter Neustart aller Instanzen

NEWS

  • Monatsrückblick Juli / August 2026 ist online!
    BluefoxB
    Bluefox
    10
    1
    723

  • Der neue Monatsrückblick für Mai und Juni 2026 ist online!
    BluefoxB
    Bluefox
    8
    1
    1.4k

  • wichtiges UPDATE für controller 7.2.2 im stable
    HomoranH
    Homoran
    10
    1
    3.9k

unregelmäßig Unmotivierter Neustart aller Instanzen

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
45 Beiträge 9 Kommentatoren 769 Aufrufe 9 Beobachtet
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • OliverIOO OliverIO

    @reutli

    Zeigen die Logs genau den Zeitpunkt eines Absturzes?
    Oder ist es nur beispielhaft für die Art der Fehler, die du siehst?

    Versuche mal ungefähr den Zeitpunkt des Absturzes zu ermitteln und suche die Stelle, an der dann vermehrt die Fehler auftauchen.
    Der Zeitpunkt des Absturzes plus sagen wir mal 10-20 Sekunden davor und 10 Sekunden danach sind interessant.

    Zusätzlich wäre gut, den RAM Verbrauch zu tracken.
    Im Experten Modus in den Objekten, gibt es dann den Systemdatenpunkt. Darunter findest du datenpunkte bei denen der ioBroker das regelmäßig schreibt, da einen historisieren.
    Das sieht man zum einen, wann wirklich ein Absturz war und zum Ende kann man sich das schön grafisch darstellen lassen.

    Weitere Ursachen, könnten Netzteil oder System Hardware generell sein.

    R Offline
    R Offline
    reutli
    schrieb am zuletzt editiert von
    #23

    @OliverIO sagte:

    @reutli

    Zeigen die Logs genau den Zeitpunkt eines Absturzes?

    Ja

    Oder ist es nur beispielhaft für die Art der Fehler, die du siehst?

    Nein

    Im Log sieht man exakt, wann die ersten Ausfälle beginnen und dann starten auf dem Master alle Adapter der Reihe nach neu.

    Versuche mal ungefähr den Zeitpunkt des Absturzes zu ermitteln und suche die Stelle, an der dann vermehrt die Fehler auftauchen.
    Der Zeitpunkt des Absturzes plus sagen wir mal 10-20 Sekunden davor und 10 Sekunden danach sind interessant.

    Absturz fängt um 2026-08-25 14:53:22.828 an:

    2026-08-25 14:53:13.086 - info: admin.1 (242092) Request actual repository...
    2026-08-25 14:53:13.323 - info: host.iobroker-master Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
    2026-08-25 14:53:13.688 - info: admin.0 (242044) Request actual repository...
    2026-08-25 14:53:16.446 - info: admin.1 (242092) Repository received successfully.
    2026-08-25 14:53:16.661 - info: admin.0 (242044) Repository received successfully.
    2026-08-25 14:53:22.828 - error: javascript.0 (242257) States database error: read ECONNRESET
    2026-08-25 14:53:22.841 - error: admin.1 (242092) Objects database error: read ECONNRESET
    2026-08-25 14:53:22.833 - error: backitup.0 (242406) States database error: read ECONNRESET
    2026-08-25 14:53:22.856 - info: smartgarden.0 (243199) 1/ cleaned everything up...
    2026-08-25 14:53:22.863 - error: jarvis.0 (243143) States database error: write ECONNRESET
    2026-08-25 14:53:22.837 - error: javascript.0 (242257) Objects database error: read ECONNRESET
    2026-08-25 14:53:22.876 - info: admin.1 (242092) terminating http server on port 8089
    2026-08-25 14:53:22.908 - info: backitup.0 (242406) cleaned everything up...
    2026-08-25 14:53:22.841 - error: history.0 (242184) States database error: read ECONNRESET
    2026-08-25 14:53:22.829 - error: unifi-network.0 (243341) States database error: read ECONNRESET
    2026-08-25 14:53:22.929 - error: unifi-network.0 (243341) Objects database error: read ECONNRESET
    2026-08-25 14:53:22.842 - error: shelly.1 (242834) Objects database error: read ECONNRESET
    2026-08-25 14:53:22.930 - error: ring.0 (242993) States database error: write EPIPE
    2026-08-25 14:53:22.850 - error: zigbee.0 (242951) States database error: read ECONNRESET
    2026-08-25 14:53:22.844 - error: mqtt.0 (242706) States database error: read ECONNRESET
    2026-08-25 14:53:22.947 - error: mqtt.0 (242706) Objects database error: read ECONNRESET
    2026-08-25 14:53:22.829 - error: panasonic-viera.0 (242764) States database error: read ECONNRESET
    2026-08-25 14:53:22.846 - error: hm-rpc.2 (242665) States database error: read ECONNRESET
    2026-08-25 14:53:22.988 - error: linkeddevices.0 (243198) States database error: write EPIPE
    2026-08-25 14:53:23.056 - error: admin.0 (242044) States database error: write ECONNRESET
    2026-08-25 14:53:23.089 - error: scenes.0 (242319) States database error: write ECONNRESET
    2026-08-25 14:53:23.108 - error: sonoff.0 (242863) States database error: write ECONNRESET
    2026-08-25 14:53:23.137 - error: terminal.0 (243221) States database error: write ECONNRESET
    2026-08-25 14:53:23.110 - error: shelly.0 (242805) Objects database error: write ECONNRESET
    2026-08-25 14:53:23.159 - error: shelly.0 (242805) States database error: write EPIPE
    2026-08-25 14:53:23.146 - error: text2command.0 (243210) States database error: write EPIPE
    2026-08-25 14:53:23.138 - info: followthesun.0 (306405) cleaned everything up...
    

    Dann ist DB connect wieder da und iob versucht die Instanzen neu zu starten (warum?)

    2026-08-25 14:53:27.624 - info: host.iobroker-master iobroker.js-controller version 7.2.2 js-controller starting
    2026-08-25 14:53:27.625 - info: host.iobroker-master Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
    2026-08-25 14:53:27.625 - info: host.iobroker-master hostname: iobroker-master, node: v22.23.2
    2026-08-25 14:53:27.625 - info: host.iobroker-master ip addresses: 192.168.13.25 fe80::18dc:e7ff:fe85:6b85
    2026-08-25 14:53:27.633 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
    2026-08-25 14:53:28.181 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
    2026-08-25 14:53:28.360 - info: host.iobroker-master connected to Objects and States
    2026-08-25 14:53:28.368 - info: host.iobroker-master added notifications configuration of host
    2026-08-25 14:53:29.387 - info: host.iobroker-master 52 instances found
    2026-08-25 14:53:29.414 - info: host.iobroker-master starting 45 instances
    2026-08-25 14:53:29.547 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.nodeCurrent"
    2026-08-25 14:53:29.626 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.nodeNewest"
    2026-08-25 14:53:29.666 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.nodeNewestNext"
    2026-08-25 14:53:29.672 - info: host.iobroker-master instance system.adapter.admin.0 in version "7.8.23" started with pid 323879
    2026-08-25 14:53:29.674 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.npmCurrent"
    2026-08-25 14:53:29.718 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.npmNewest"
    2026-08-25 14:53:29.762 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.npmNewestNext"
    2026-08-25 14:53:29.806 - info: host.iobroker-master Some obsolete host states deleted.
    2026-08-25 14:53:31.093 - error: admin.0 (323879) admin.0 already running
    2026-08-25 14:53:31.094 - warn: admin.0 (323879) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2026-08-25 14:53:31.659 - error: host.iobroker-master instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2026-08-25 14:53:31.659 - info: host.iobroker-master Restart adapter system.adapter.admin.0 because enabled
    2026-08-25 14:53:33.654 - info: host.iobroker-master instance system.adapter.admin.1 in version "7.8.23" started with pid 323891
    2026-08-25 14:53:34.412 - error: admin.1 (323891) admin.1 already running
    2026-08-25 14:53:34.413 - warn: admin.1 (323891) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2026-08-25 14:53:34.962 - error: host.iobroker-master instance system.adapter.admin.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2026-08-25 14:53:34.962 - info: host.iobroker-master Restart adapter system.adapter.admin.1 because enabled
    2026-08-25 14:53:37.635 - info: host.iobroker-master instance system.adapter.email.0 in version "2.0.4" started with pid 323903
    2026-08-25 14:53:38.148 - error: email.0 (323903) email.0 already running
    2026-08-25 14:53:38.149 - warn: email.0 (323903) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2026-08-25 14:53:38.697 - error: host.iobroker-master instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    
    

    Zusätzlich wäre gut, den RAM Verbrauch zu tracken.
    Im Experten Modus in den Objekten, gibt es dann den Systemdatenpunkt. Darunter findest du datenpunkte bei denen der ioBroker das regelmäßig schreibt, da einen historisieren.
    Das sieht man zum einen, wann wirklich ein Absturz war und zum Ende kann man sich das schön grafisch darstellen lassen.

    Kann ich machen, habe aber an der Stelle bisher nie etwas Verdächtiges gefunden...

    Weitere Ursachen, könnten Netzteil oder System Hardware generell sein.

    unwahrscheinlich...
    Master ist in einer VM auf Proxmox.... Proxmox - Host i.O, soweit man das testen kann.
    Slave (eher nciht das Problem): RPi 3 mit Originalnetzteil

    iobroker in Debian-VM auf Proxmox Server (Ryzen 7 / 32GB / 1TB NVMe SSD) als Master - mehrere Raspberry Pis (3+4) als Slaves. InfluxDB V2 und Grafana auf LXC.

    *Wer freundlich ist, dem wird freundlich geholfen *

    1 Antwort Letzte Antwort
    0
    • MartinPM Online
      MartinPM Online
      MartinP
      schrieb am zuletzt editiert von
      #24

      Die States müssen ja zwischen Master und Slave abgeglichen werden.
      Wenn die Verbindung zwischen Master und Slave nicht steht, kann das nicht erfolgen.
      Wenn aber ein abgeschmierter Slave-Host einen Master gleich mit in den Abgrund zieht, wäre das schon eine Überraschung ...

      Intel(R) Celeron(R) CPU N3000 @1.04GHz 8G RAM 480G SSD * Virtualization : unprivileged lxc container on Proxmox * 6 GByte RAM für den iobroker Container * Remote-Access über Wireguard meiner Fritzbox

      OliverIOO 1 Antwort Letzte Antwort
      0
      • MartinPM MartinP

        Die States müssen ja zwischen Master und Slave abgeglichen werden.
        Wenn die Verbindung zwischen Master und Slave nicht steht, kann das nicht erfolgen.
        Wenn aber ein abgeschmierter Slave-Host einen Master gleich mit in den Abgrund zieht, wäre das schon eine Überraschung ...

        OliverIOO Offline
        OliverIOO Offline
        OliverIO
        schrieb am zuletzt editiert von
        #25

        @MartinP

        hatte ich auch schon vermutet.
        wenn der master/slave abgleich tief im innern von iobroker statt findet
        und der slave nicht zeitnah antwortet, dann bindet das ressourcen bis der timeout abgelaufen ist. wenn dann sehr viel kommt könnte es das erklären.
        ist aber leider in den logs nicht zu sehen. aber evtl gibt es da auch kein mechanismus im code der das abfängt oder zumindest meldet.

        Meine Adapter und Widgets
        TVProgram, SqueezeboxRPC, OpenLiga, RSSFeed, MyTime,, pi-hole2, vis-json-template, skiinfo, vis-mapwidgets, vis-2-widgets-rssfeed
        Links im Profil

        1 Antwort Letzte Antwort
        0
        • R Offline
          R Offline
          reutli
          schrieb am zuletzt editiert von
          #26

          Gerade eben wieder ein solcher "Absturz".
          Auffällig: Es passiert immer direkt nachdem die Repos abgefragt werden?!

          Irgendwas bekannt hierzu???

          2026-08-28 11:17:40.439 - info: admin.1 (324035) Request actual repository...
          2026-08-28 11:17:40.505 - info: admin.0 (323983) Request actual repository...
          2026-08-28 11:17:40.651 - info: host.iobroker-master Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
          2026-08-28 11:17:43.608 - info: admin.1 (324035) Repository received successfully.
          2026-08-28 11:17:43.847 - info: admin.0 (323983) Repository received successfully.
          2026-08-28 11:17:47.181 - info: admin.0 (323983) terminating http server on port 8081
          2026-08-28 11:17:47.182 - error: admin.1 (324035) States database error: read ECONNRESET
          2026-08-28 11:17:47.192 - info: device-watcher.0 (324422) cleaned everything up...
          2026-08-28 11:17:47.194 - error: admin.1 (324035) Objects database error: read ECONNRESET
          2026-08-28 11:17:47.219 - info: smartgarden.0 (325157) 1/ cleaned everything up...
          2026-08-28 11:17:47.207 - info: backitup.0 (324349) cleaned everything up...
          2026-08-28 11:17:47.219 - error: signal-cmb.0 (325259) States database error: read ECONNRESET
          2026-08-28 11:17:47.197 - error: unifi-network.0 (325301) Objects database error: read ECONNRESET
          2026-08-28 11:17:47.308 - info: jarvis.0 (325114) Adapter stopped und unloaded.
          2026-08-28 11:17:47.189 - error: hm-rpc.0 (324550) States database error: read ECONNRESET
          2026-08-28 11:17:47.249 - error: discovery.0 (324968) States database error: read ECONNRESET
          2026-08-28 11:17:47.365 - info: javascript.0 (324200) script.js.Allgemein.Ferien_setzen: Stopping script
          2026-08-28 11:17:51.798 - info: host.iobroker-master iobroker.js-controller version 7.2.2 js-controller starting
          2026-08-28 11:17:51.799 - info: host.iobroker-master Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
          2026-08-28 11:17:51.799 - info: host.iobroker-master hostname: iobroker-master, node: v22.23.2
          2026-08-28 11:17:51.799 - info: host.iobroker-master ip addresses: 192.168.13.25 fe80::18dc:e7ff:fe85:6b85
          2026-08-28 11:17:51.809 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
          2026-08-28 11:17:52.395 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
          2026-08-28 11:17:52.664 - info: host.iobroker-master connected to Objects and States
          2026-08-28 11:17:52.671 - info: host.iobroker-master added notifications configuration of host
          2026-08-28 11:17:53.731 - info: host.iobroker-master 53 instances found
          2026-08-28 11:17:53.750 - info: host.iobroker-master starting 45 instances
          2026-08-28 11:17:53.941 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.nodeCurrent"
          

          iobroker in Debian-VM auf Proxmox Server (Ryzen 7 / 32GB / 1TB NVMe SSD) als Master - mehrere Raspberry Pis (3+4) als Slaves. InfluxDB V2 und Grafana auf LXC.

          *Wer freundlich ist, dem wird freundlich geholfen *

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • R reutli

            Gerade eben wieder ein solcher "Absturz".
            Auffällig: Es passiert immer direkt nachdem die Repos abgefragt werden?!

            Irgendwas bekannt hierzu???

            2026-08-28 11:17:40.439 - info: admin.1 (324035) Request actual repository...
            2026-08-28 11:17:40.505 - info: admin.0 (323983) Request actual repository...
            2026-08-28 11:17:40.651 - info: host.iobroker-master Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
            2026-08-28 11:17:43.608 - info: admin.1 (324035) Repository received successfully.
            2026-08-28 11:17:43.847 - info: admin.0 (323983) Repository received successfully.
            2026-08-28 11:17:47.181 - info: admin.0 (323983) terminating http server on port 8081
            2026-08-28 11:17:47.182 - error: admin.1 (324035) States database error: read ECONNRESET
            2026-08-28 11:17:47.192 - info: device-watcher.0 (324422) cleaned everything up...
            2026-08-28 11:17:47.194 - error: admin.1 (324035) Objects database error: read ECONNRESET
            2026-08-28 11:17:47.219 - info: smartgarden.0 (325157) 1/ cleaned everything up...
            2026-08-28 11:17:47.207 - info: backitup.0 (324349) cleaned everything up...
            2026-08-28 11:17:47.219 - error: signal-cmb.0 (325259) States database error: read ECONNRESET
            2026-08-28 11:17:47.197 - error: unifi-network.0 (325301) Objects database error: read ECONNRESET
            2026-08-28 11:17:47.308 - info: jarvis.0 (325114) Adapter stopped und unloaded.
            2026-08-28 11:17:47.189 - error: hm-rpc.0 (324550) States database error: read ECONNRESET
            2026-08-28 11:17:47.249 - error: discovery.0 (324968) States database error: read ECONNRESET
            2026-08-28 11:17:47.365 - info: javascript.0 (324200) script.js.Allgemein.Ferien_setzen: Stopping script
            2026-08-28 11:17:51.798 - info: host.iobroker-master iobroker.js-controller version 7.2.2 js-controller starting
            2026-08-28 11:17:51.799 - info: host.iobroker-master Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
            2026-08-28 11:17:51.799 - info: host.iobroker-master hostname: iobroker-master, node: v22.23.2
            2026-08-28 11:17:51.799 - info: host.iobroker-master ip addresses: 192.168.13.25 fe80::18dc:e7ff:fe85:6b85
            2026-08-28 11:17:51.809 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
            2026-08-28 11:17:52.395 - warn: host.iobroker-master-Server Configured backup period 7200000 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
            2026-08-28 11:17:52.664 - info: host.iobroker-master connected to Objects and States
            2026-08-28 11:17:52.671 - info: host.iobroker-master added notifications configuration of host
            2026-08-28 11:17:53.731 - info: host.iobroker-master 53 instances found
            2026-08-28 11:17:53.750 - info: host.iobroker-master starting 45 instances
            2026-08-28 11:17:53.941 - info: host.iobroker-master Delete state "system.host.iobroker-master.versions.nodeCurrent"
            
            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #27

            @reutli

            Active iob-Instances: 	46
             
                      905 M total memory
            

            Wird viel zu viel sein.

            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

            R 1 Antwort Letzte Antwort
            1
            • Thomas BraunT Thomas Braun

              @reutli

              Active iob-Instances: 	46
               
                        905 M total memory
              

              Wird viel zu viel sein.

              R Offline
              R Offline
              reutli
              schrieb am zuletzt editiert von
              #28

              @Thomas-Braun sagte:

              Wird viel zu viel sein.

              So wenig Speicher habe ich nur auf dem SLAVE (PI3) und soviele Instanzen nur auf dem Master. Keine Ahnung was Dein diag da ausgibt 😊 , aber:

              Bildschirmfoto 2026-08-28 um 12.50.00.png

              iobroker in Debian-VM auf Proxmox Server (Ryzen 7 / 32GB / 1TB NVMe SSD) als Master - mehrere Raspberry Pis (3+4) als Slaves. InfluxDB V2 und Grafana auf LXC.

              *Wer freundlich ist, dem wird freundlich geholfen *

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • R reutli

                @Thomas-Braun sagte:

                Wird viel zu viel sein.

                So wenig Speicher habe ich nur auf dem SLAVE (PI3) und soviele Instanzen nur auf dem Master. Keine Ahnung was Dein diag da ausgibt 😊 , aber:

                Bildschirmfoto 2026-08-28 um 12.50.00.png

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #29

                @reutli sagte:

                Keine Ahnung was Dein diag da ausgibt

                Die Gesamtzahl der laufenden Instanzen 'über alles'.
                Das ist ja nicht falsch.
                Weiter unten sieht man dann die Instanzen, die auf den jeweiligen Hosts laufen. Das sind in der Tat für den Host 'iobroker' nur 3 oder 4, allerdings mit node-red ggfls. ein 'Schwergewicht'.

                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

                R 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @reutli sagte:

                  Keine Ahnung was Dein diag da ausgibt

                  Die Gesamtzahl der laufenden Instanzen 'über alles'.
                  Das ist ja nicht falsch.
                  Weiter unten sieht man dann die Instanzen, die auf den jeweiligen Hosts laufen. Das sind in der Tat für den Host 'iobroker' nur 3 oder 4, allerdings mit node-red ggfls. ein 'Schwergewicht'.

                  R Offline
                  R Offline
                  reutli
                  schrieb am zuletzt editiert von
                  #30

                  @Thomas-Braun sagte:

                  allerdings mit node-red ggfls. ein 'Schwergewicht'.

                  Der sollte aber nicht das Problem darstellen. Der ist seit Uhrzeiten drauf und macht nur ienen Pull auf eine serielle Schnittselle.

                  Warum aber der Absturz im beim Repo Abgleich stattfindet, fine ich ncoht interessanter (das letzte Mail diese Woche sah es im LOG genau gleich aus:
                  Erst Repo Abgleich, dann Absturz

                  iobroker in Debian-VM auf Proxmox Server (Ryzen 7 / 32GB / 1TB NVMe SSD) als Master - mehrere Raspberry Pis (3+4) als Slaves. InfluxDB V2 und Grafana auf LXC.

                  *Wer freundlich ist, dem wird freundlich geholfen *

                  1 Antwort Letzte Antwort
                  0
                  • P Offline
                    P Offline
                    peterfido
                    schrieb am zuletzt editiert von peterfido
                    #31

                    Hallo Leute,

                    mein ioBroker hat diese Woche, wo ich natürlich im Urlaub war, das gleiche Verhalten gezeigt:

                    2026-08-25 17:06:49.777 - info: admin.0 (1126) Repository received successfully.
                    2026-08-25 17:06:52.544 - error: admin.0 (1126) Objects database error: read ECONNRESET
                    2026-08-25 17:06:52.517 - info: ws.0 (2134) terminating http server on port 8084
                    2026-08-25 17:06:52.546 - error: javascript.0 (1242) Objects database error: read ECONNRESET
                    2026-08-25 17:06:52.539 - error: jeelink.0 (1923) Objects database error: read ECONNRESET
                    2026-08-25 17:06:52.513 - info: socketio.0 (1961) terminating http server on port 8088
                    2026-08-25 17:06:52.521 - info: simple-api.0 (1942) terminating http server on port 8087
                    2026-08-25 17:06:52.553 - error: sourceanalytix.0 (2298) Objects database error: read ECONNRESET
                    2026-08-25 17:06:52.550 - info: admin.0 (1126) terminating http server on port 8081
                    2026-08-25 17:06:52.550 - info: admin.0 (1126) <== Disconnect system.user.admin from ::ffff:192.168.56.93 NodeRED-104
                    2026-08-25 17:06:52.610 - info: sourceanalytix.0 (2298) SourceAnalytix stopped, now you have to calculate by yourself :'( ...
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Alexa.Alexas: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Alexa.Freddie: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Alexa.Technik: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Beleuchtung.Licht: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Beleuchtung.Terrasse: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Beleuchtung.Urlaubsbeleuchtung: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.Heizmodus: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.HzgEsszimmer: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.HzgKueche: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.HzgWohnzimmer: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.Stromzaehler: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Heizung.USRIOTHzg: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Scripte.Ausschalten: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Scripte.CronJobs: Stopping script
                    2026-08-25 17:06:52.569 - info: javascript.0 (1242) script.js.Scripte.Easy: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Helligkeit: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Main: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.NUC: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Pioneer: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Synology: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.USBSticks: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.USV: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Unifi: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.Uptime: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.WatchDogs: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Scripte.vis: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.Alarm: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.Anwesenheit: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.Kamerabild: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.Klingel: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.UnifiProtect: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.Verschluss.Verschluss: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.HMIP_Steckdosen: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Steckdose1: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Steckdose2: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Steckdose3: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Steckdose4: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Steckdose5: Stopping script
                    2026-08-25 17:06:52.572 - info: javascript.0 (1242) script.js.steckdosen.Tasmota: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Heizung.Temperaturen: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Kalender: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Wallbox: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.steckdosen.Schaltuhr: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Beleuchtung.Beleuchtung: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Heizung.HzgFrauke: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Beleuchtung.LichtTelegram0: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.NSPanels: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Verbrauchskosten: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Skripte.Unifi_Alarm_Manager: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Beleuchtung.Lichterkette: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Verschluss.FullyAlarm: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Heizung.HzgPeter: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Heizung.HzgSchlafenOben: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Verschluss.Klingelbild_2025: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Abfall: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Beleuchtung.Schlafen_oben: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Skripte.VIS_Haus: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Markise: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Easy_Watchdogs: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZEVU: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZGas: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZHerd: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZPV: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZSchlafenOben: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZWaschmaschine: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZWasser: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZArbeitszimmer: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.ZPumpeKeller: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.common.Wetter_com_4: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Zaehler.Z_Klima: Stopping script
                    2026-08-25 17:06:52.573 - info: javascript.0 (1242) script.js.Scripte.Wettersymbole: Stopping script
                    2026-08-25 17:06:52.568 - info: hm-rpc.2 (1681) xmlrpc -> 192.168.2.28:2010/ init ["http://192.168.2.24:12010",""]
                    2026-08-25 17:06:52.664 - info: hm-rpc.2 (1681) Disconnected
                    2026-08-25 17:06:52.534 - info: socketio.1 (1981) terminating http server on port 8085
                    2026-08-25 17:06:57.512 - error: philips-tv.0 (2197) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:06:57.517 - error: philips-tv.0 (2197) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:06:57.517 - error: tankerkoenig.0 (2175) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:06:57.521 - error: tankerkoenig.0 (2175) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:06:57.527 - error: philips-tv.1 (2349) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:06:57.529 - error: hm-rpc.2 (1681) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:06:57.528 - error: philips-tv.1 (2349) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:06:57.528 - error: nspanel-lovelace-ui.0 (2400) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    

                    Dann noch ganz viel Rotes im Log und irgendwann ein Neustart der Adapter.

                    2026-08-25 17:08:22.563 - error: philips-tv.1 (2349) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.564 - warn: ❌ hm-rpc.2 (1681) Objects database disconnected
                    2026-08-25 17:08:22.564 - error: philips-tv.1 (2349) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.564 - warn: ❌ philips-tv.1 (2349) Objects database disconnected
                    2026-08-25 17:08:22.565 - warn: ❌ philips-tv.1 (2349) States database disconnected
                    2026-08-25 17:08:22.565 - warn: philips-tv.1 (2349) get state error: Connection is closed.
                    2026-08-25 17:08:22.565 - info: philips-tv.1 (2349) terminating
                    2026-08-25 17:08:22.566 - info: philips-tv.1 (2349) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.566 - info: philips-tv.1 (2349) terminating
                    2026-08-25 17:08:22.567 - warn: philips-tv.1 (2349) get state error: Connection is closed.
                    2026-08-25 17:08:22.567 - info: philips-tv.1 (2349) terminating
                    2026-08-25 17:08:22.565 - error: tankerkoenig.0 (2175) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.569 - error: s7.1 (1815) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.570 - error: nspanel-lovelace-ui.0 (2400) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.566 - error: tankerkoenig.0 (2175) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.567 - warn: ❌ tankerkoenig.0 (2175) Objects database disconnected
                    2026-08-25 17:08:22.567 - warn: ❌ tankerkoenig.0 (2175) States database disconnected
                    2026-08-25 17:08:22.567 - warn: tankerkoenig.0 (2175) get state error: Connection is closed.
                    2026-08-25 17:08:22.567 - warn: tankerkoenig.0 (2175) get state error: DB closed
                    2026-08-25 17:08:22.568 - info: tankerkoenig.0 (2175) terminating
                    2026-08-25 17:08:22.568 - info: tankerkoenig.0 (2175) terminating
                    2026-08-25 17:08:22.568 - info: tankerkoenig.0 (2175) terminating
                    2026-08-25 17:08:22.568 - info: tankerkoenig.0 (2175) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.567 - error: hm-rpc.2 (1681) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.568 - warn: ❌ hm-rpc.2 (1681) States database disconnected
                    2026-08-25 17:08:22.568 - warn: hm-rpc.2 (1681) get state error: Connection is closed.
                    2026-08-25 17:08:22.568 - warn: hm-rpc.2 (1681) get state error: DB closed
                    2026-08-25 17:08:22.568 - info: hm-rpc.2 (1681) terminating
                    2026-08-25 17:08:22.570 - info: hm-rpc.2 (1681) terminating
                    2026-08-25 17:08:22.570 - info: hm-rpc.2 (1681) terminating
                    2026-08-25 17:08:22.571 - info: hm-rpc.2 (1681) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.570 - error: nspanel-lovelace-ui.0 (2400) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.570 - warn: ❌ nspanel-lovelace-ui.0 (2400) States database disconnected
                    2026-08-25 17:08:22.571 - warn: nspanel-lovelace-ui.0 (2400) get state error: Connection is closed.
                    2026-08-25 17:08:22.571 - info: nspanel-lovelace-ui.0 (2400) terminating
                    2026-08-25 17:08:22.571 - info: nspanel-lovelace-ui.0 (2400) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.571 - info: nspanel-lovelace-ui.0 (2400) terminating
                    2026-08-25 17:08:22.572 - warn: ❌ nspanel-lovelace-ui.0 (2400) Objects database disconnected
                    2026-08-25 17:08:22.564 - error: philips-tv.0 (2197) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.566 - warn: ❌ philips-tv.0 (2197) States database disconnected
                    2026-08-25 17:08:22.566 - warn: philips-tv.0 (2197) get state error: Connection is closed.
                    2026-08-25 17:08:22.566 - info: philips-tv.0 (2197) terminating
                    2026-08-25 17:08:22.567 - info: philips-tv.0 (2197) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.568 - info: philips-tv.0 (2197) terminating
                    2026-08-25 17:08:22.572 - warn: ❌ philips-tv.0 (2197) Objects database disconnected
                    2026-08-25 17:08:22.573 - warn: philips-tv.0 (2197) get state error: Connection is closed.
                    2026-08-25 17:08:22.573 - info: philips-tv.0 (2197) terminating
                    2026-08-25 17:08:22.570 - error: s7.1 (1815) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.570 - warn: ❌ s7.1 (1815) States database disconnected
                    2026-08-25 17:08:22.570 - warn: s7.1 (1815) get state error: Connection is closed.
                    2026-08-25 17:08:22.571 - warn: s7.1 (1815) get state error: DB closed
                    2026-08-25 17:08:22.571 - warn: s7.1 (1815) get state error: DB closed
                    2026-08-25 17:08:22.571 - info: s7.1 (1815) terminating
                    2026-08-25 17:08:22.571 - info: s7.1 (1815) terminating
                    2026-08-25 17:08:22.571 - info: s7.1 (1815) terminating
                    2026-08-25 17:08:22.571 - info: s7.1 (1815) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.572 - warn: ❌ s7.1 (1815) Objects database disconnected
                    2026-08-25 17:08:22.573 - warn: nspanel-lovelace-ui.0 (2400) get state error: Connection is closed.
                    2026-08-25 17:08:22.573 - info: nspanel-lovelace-ui.0 (2400) terminating
                    2026-08-25 17:08:22.579 - error: vis-2.0 (2254) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.579 - error: vis-2.0 (2254) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.579 - warn: ❌ vis-2.0 (2254) Objects database disconnected
                    2026-08-25 17:08:22.579 - warn: ❌ vis-2.0 (2254) States database disconnected
                    2026-08-25 17:08:22.580 - warn: vis-2.0 (2254) get state error: Connection is closed.
                    2026-08-25 17:08:22.580 - warn: vis-2.0 (2254) get state error: DB closed
                    2026-08-25 17:08:22.580 - info: vis-2.0 (2254) terminating
                    2026-08-25 17:08:22.580 - info: vis-2.0 (2254) terminating
                    2026-08-25 17:08:22.580 - info: vis-2.0 (2254) terminating
                    2026-08-25 17:08:22.580 - info: vis-2.0 (2254) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.581 - error: hue.0 (1467) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.582 - error: telegram.1 (2214918) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.582 - warn: ❌ hue.0 (1467) Objects database disconnected
                    2026-08-25 17:08:22.583 - error: socketio.1 (1981) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.583 - warn: ❌ socketio.1 (1981) Objects database disconnected
                    2026-08-25 17:08:22.584 - error: socketio.1 (1981) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.585 - warn: ❌ socketio.1 (1981) States database disconnected
                    2026-08-25 17:08:22.585 - warn: socketio.1 (1981) get state error: Connection is closed.
                    2026-08-25 17:08:22.585 - warn: socketio.1 (1981) get state error: DB closed
                    2026-08-25 17:08:22.585 - info: socketio.1 (1981) terminating
                    2026-08-25 17:08:22.585 - info: socketio.1 (1981) terminating
                    2026-08-25 17:08:22.585 - info: socketio.1 (1981) terminating
                    2026-08-25 17:08:22.585 - info: socketio.1 (1981) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.582 - error: telegram.1 (2214918) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.583 - warn: ❌ telegram.1 (2214918) Objects database disconnected
                    2026-08-25 17:08:22.584 - warn: ❌ telegram.1 (2214918) States database disconnected
                    2026-08-25 17:08:22.584 - warn: telegram.1 (2214918) get state error: Connection is closed.
                    2026-08-25 17:08:22.584 - info: telegram.1 (2214918) terminating
                    2026-08-25 17:08:22.585 - info: telegram.1 (2214918) terminating
                    2026-08-25 17:08:22.585 - info: telegram.1 (2214918) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.593 - error: hue.0 (1467) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.594 - warn: ❌ hue.0 (1467) States database disconnected
                    2026-08-25 17:08:22.594 - warn: hue.0 (1467) get state error: Connection is closed.
                    2026-08-25 17:08:22.594 - warn: hue.0 (1467) get state error: DB closed
                    2026-08-25 17:08:22.594 - info: hue.0 (1467) terminating
                    2026-08-25 17:08:22.595 - info: hue.0 (1467) terminating
                    2026-08-25 17:08:22.595 - info: hue.0 (1467) terminating
                    2026-08-25 17:08:22.595 - info: hue.0 (1467) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.602 - error: nut.0 (1524) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.602 - error: nut.0 (1524) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.603 - warn: ❌ nut.0 (1524) States database disconnected
                    2026-08-25 17:08:22.604 - warn: nut.0 (1524) get state error: Connection is closed.
                    2026-08-25 17:08:22.604 - warn: nut.0 (1524) get state error: DB closed
                    2026-08-25 17:08:22.605 - info: nut.0 (1524) terminating
                    2026-08-25 17:08:22.607 - info: nut.0 (1524) terminating
                    2026-08-25 17:08:22.607 - info: nut.0 (1524) terminating
                    2026-08-25 17:08:22.608 - info: nut.0 (1524) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.608 - warn: ❌ nut.0 (1524) Objects database disconnected
                    2026-08-25 17:08:22.610 - error: nut.0 (1524) Can not update connected state: Error: DB closed
                    2026-08-25 17:08:22.628 - error: jeelink.0 (1923) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.629 - error: jeelink.0 (1923) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.630 - warn: ❌ jeelink.0 (1923) States database disconnected
                    2026-08-25 17:08:22.630 - warn: jeelink.0 (1923) get state error: Connection is closed.
                    2026-08-25 17:08:22.630 - warn: jeelink.0 (1923) get state error: DB closed
                    2026-08-25 17:08:22.630 - info: jeelink.0 (1923) terminating
                    2026-08-25 17:08:22.630 - info: jeelink.0 (1923) terminating
                    2026-08-25 17:08:22.631 - info: jeelink.0 (1923) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.631 - info: jeelink.0 (1923) terminating
                    2026-08-25 17:08:22.631 - warn: ❌ jeelink.0 (1923) Objects database disconnected
                    2026-08-25 17:08:22.632 - warn: jeelink.0 (1923) Could not perform strict object check of state jeelink.0.LaCrosse_1.newBatt: DB closed
                    2026-08-25 17:08:22.632 - warn: jeelink.0 (1923) get state error: Connection is closed.
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.633 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.634 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.635 - error: jeelink.0 (1923) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    2026-08-25 17:08:22.636 - error: jeelink.0 (1923) 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().
                    2026-08-25 17:08:22.636 - error: chromecast.0 (1715) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.636 - error: jeelink.0 (1923) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.636 - error: jeelink.0 (1923) Error: DB closed
                    at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                    at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/objectsInRedisClient.js:2366:37)
                    at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/objectsInRedisClient.js:2407:29)
                    at process.processImmediate (node:internal/timers:486:21)
                    2026-08-25 17:08:22.638 - error: chromecast.0 (1715) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.640 - error: s7.0 (1698) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.640 - error: s7.0 (1698) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.641 - warn: ❌ s7.0 (1698) Objects database disconnected
                    2026-08-25 17:08:22.641 - warn: ❌ s7.0 (1698) States database disconnected
                    2026-08-25 17:08:22.641 - warn: s7.0 (1698) get state error: Connection is closed.
                    2026-08-25 17:08:22.641 - warn: s7.0 (1698) get state error: DB closed
                    2026-08-25 17:08:22.641 - info: s7.0 (1698) terminating
                    2026-08-25 17:08:22.642 - info: s7.0 (1698) terminating
                    2026-08-25 17:08:22.642 - info: s7.0 (1698) terminating
                    2026-08-25 17:08:22.642 - info: s7.0 (1698) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.644 - error: simple-api.0 (1942) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.645 - warn: ❌ simple-api.0 (1942) States database disconnected
                    2026-08-25 17:08:22.645 - warn: simple-api.0 (1942) get state error: Connection is closed.
                    2026-08-25 17:08:22.645 - warn: simple-api.0 (1942) get state error: DB closed
                    2026-08-25 17:08:22.645 - info: simple-api.0 (1942) terminating
                    2026-08-25 17:08:22.645 - info: simple-api.0 (1942) terminating
                    2026-08-25 17:08:22.645 - info: simple-api.0 (1942) terminating
                    2026-08-25 17:08:22.645 - info: simple-api.0 (1942) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.646 - error: admin.0 (1126) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.647 - warn: ❌ admin.0 (1126) States database disconnected
                    2026-08-25 17:08:22.647 - warn: admin.0 (1126) get state error: Connection is closed.
                    2026-08-25 17:08:22.647 - warn: admin.0 (1126) get state error: DB closed
                    2026-08-25 17:08:22.647 - info: admin.0 (1126) terminating
                    2026-08-25 17:08:22.648 - info: admin.0 (1126) terminating
                    2026-08-25 17:08:22.648 - info: admin.0 (1126) terminating
                    2026-08-25 17:08:22.648 - info: admin.0 (1126) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.651 - error: sourceanalytix.0 (2298) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.649 - error: socketio.0 (1961) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.649 - error: simple-api.0 (1942) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.650 - warn: ❌ simple-api.0 (1942) Objects database disconnected
                    2026-08-25 17:08:22.650 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.650 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.651 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.651 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.651 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.651 - error: simple-api.0 (1942) Cannot get state: Error: DB closed
                    2026-08-25 17:08:22.649 - warn: ❌ socketio.0 (1961) Objects database disconnected
                    2026-08-25 17:08:22.650 - error: socketio.0 (1961) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.650 - warn: ❌ socketio.0 (1961) States database disconnected
                    2026-08-25 17:08:22.650 - warn: socketio.0 (1961) get state error: Connection is closed.
                    2026-08-25 17:08:22.650 - warn: socketio.0 (1961) get state error: DB closed
                    2026-08-25 17:08:22.650 - info: socketio.0 (1961) terminating
                    2026-08-25 17:08:22.650 - info: socketio.0 (1961) terminating
                    2026-08-25 17:08:22.651 - info: socketio.0 (1961) terminating
                    2026-08-25 17:08:22.651 - info: socketio.0 (1961) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.651 - error: sourceanalytix.0 (2298) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.652 - warn: ❌ sourceanalytix.0 (2298) Objects database disconnected
                    2026-08-25 17:08:22.652 - warn: ❌ sourceanalytix.0 (2298) States database disconnected
                    2026-08-25 17:08:22.652 - warn: sourceanalytix.0 (2298) get state error: Connection is closed.
                    2026-08-25 17:08:22.652 - warn: sourceanalytix.0 (2298) get state error: DB closed
                    2026-08-25 17:08:22.652 - info: sourceanalytix.0 (2298) terminating
                    2026-08-25 17:08:22.652 - info: sourceanalytix.0 (2298) terminating
                    2026-08-25 17:08:22.652 - info: sourceanalytix.0 (2298) terminating
                    2026-08-25 17:08:22.652 - info: sourceanalytix.0 (2298) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:22.662 - error: admin.0 (1126) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.662 - warn: ❌ admin.0 (1126) Objects database disconnected
                    2026-08-25 17:08:22.663 - error: admin.0 (1126) Cannot add repository read timestamp: Error: DB closed
                    2026-08-25 17:08:22.638 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.639 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.639 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.657 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.657 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.658 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.659 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.659 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.659 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.659 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.659 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.660 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) 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().
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) unhandled promise rejection: DB closed
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) 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:160:20)
                    at Object.onceWrapper (node:events:634:26)
                    at Socket.emit (node:events:519:28)
                    at TCP. (node:net:347:12)
                    at TCP.callbackTrampoline (node:internal/async_hooks:130:17)
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) uncaught exception: write EPIPE
                    2026-08-25 17:08:22.661 - error: chromecast.0 (1715) Error: write EPIPE
                    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
                    at writeGeneric (node:internal/stream_base_commons:150:3)
                    at Socket._writeGeneric (node:net:967:11)
                    at Socket._write (node:net:979:8)
                    at writeOrBuffer (node:internal/streams/writable:572:12)
                    at _write (node:internal/streams/writable:501:10)
                    at Socket.Writable.write (node:internal/streams/writable:510:10)
                    at console.value (node:internal/console/constructor:303:16)
                    at console.warn (node:internal/console/constructor:426:26)
                    at file:///opt/iobroker/node_modules/@sentry/node-core/src/integrations/onunhandledrejection.ts:142:15
                    2026-08-25 17:08:22.666 - error: admin.0 (1126) Cannot find view "system" for search "instance" : Connection is closed.
                    2026-08-25 17:08:22.666 - error: admin.0 (1126) Cannot check revoked versions: Error: Cannot find view "system"
                    2026-08-25 17:08:22.668 - error: javascript.0 (1242) States database error: connect ECONNREFUSED 127.0.0.1:9000
                    2026-08-25 17:08:22.669 - error: javascript.0 (1242) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
                    2026-08-25 17:08:22.669 - warn: ❌ javascript.0 (1242) Objects database disconnected
                    2026-08-25 17:08:22.676 - warn: ❌ javascript.0 (1242) States database disconnected
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: Connection is closed.
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: DB closed
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: DB closed
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: DB closed
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: DB closed
                    2026-08-25 17:08:22.676 - warn: javascript.0 (1242) get state error: DB closed
                    2026-08-25 17:08:22.676 - info: javascript.0 (1242) terminating
                    2026-08-25 17:08:22.677 - info: javascript.0 (1242) terminating
                    2026-08-25 17:08:22.678 - info: javascript.0 (1242) Terminated (NO_ERROR): Without reason
                    2026-08-25 17:08:26.659 - info: host.iob iobroker.js-controller version 7.2.2 js-controller starting
                    2026-08-25 17:08:26.660 - info: host.iob Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
                    2026-08-25 17:08:26.660 - info: host.iob hostname: iob, node: v22.23.2
                    2026-08-25 17:08:26.660 - info: host.iob ip addresses: 192.168.2.24 fe80::7832:49ff:fe74:fc81 192.168.56.24 2a00:6020:9058:4bf3:4e4:39ff:fe99:756f fe80::4e4:39ff:fe99:756f 192.168.12.24 fe80::be24:11ff:fe4c:17ca
                    2026-08-25 17:08:27.674 - info: host.iob connected to Objects and States
                    2026-08-25 17:08:27.685 - info: host.iob added notifications configuration of host
                    2026-08-25 17:08:28.465 - info: host.iob 99 instances found
                    2026-08-25 17:08:28.483 - info: host.iob starting 60 instances
                    2026-08-25 17:08:28.671 - info: host.iob Delete state "system.host.iob.versions.nodeCurrent"
                    2026-08-25 17:08:28.706 - info: host.iob Delete state "system.host.iob.versions.nodeNewest"
                    2026-08-25 17:08:28.707 - info: host.iob Delete state "system.host.iob.versions.nodeNewestNext"
                    2026-08-25 17:08:28.707 - info: host.iob Delete state "system.host.iob.versions.npmCurrent"
                    2026-08-25 17:08:28.708 - info: host.iob Delete state "system.host.iob.versions.npmNewest"
                    2026-08-25 17:08:28.714 - info: host.iob instance system.adapter.admin.0 in version "7.8.23" started with pid 2345373
                    2026-08-25 17:08:28.753 - info: host.iob Delete state "system.host.iob.versions.npmNewestNext"
                    2026-08-25 17:08:28.754 - info: host.iob Some obsolete host states deleted.
                    2026-08-25 17:08:29.785 - error: admin.0 (2345373) admin.0 already running
                    2026-08-25 17:08:29.787 - warn: admin.0 (2345373) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:30.342 - error: host.iob instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:30.342 - info: host.iob Restart adapter system.adapter.admin.0 because enabled
                    2026-08-25 17:08:32.700 - info: host.iob instance system.adapter.influxdb.0 in version "4.0.2" started with pid 2345385
                    2026-08-25 17:08:33.228 - error: influxdb.0 (2345385) influxdb.0 already running
                    2026-08-25 17:08:33.230 - warn: influxdb.0 (2345385) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:33.775 - error: host.iob instance system.adapter.influxdb.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:33.776 - info: host.iob Restart adapter system.adapter.influxdb.0 because enabled
                    2026-08-25 17:08:36.700 - info: host.iob instance system.adapter.node-red.0 in version "6.0.7" started with pid 2345397
                    2026-08-25 17:08:37.171 - error: node-red.0 (2345397) node-red.0 already running
                    2026-08-25 17:08:37.172 - warn: node-red.0 (2345397) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:37.716 - error: host.iob instance system.adapter.node-red.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:37.716 - info: host.iob Restart adapter system.adapter.node-red.0 because enabled
                    2026-08-25 17:08:40.693 - info: host.iob instance system.adapter.javascript.0 in version "9.0.18" started with pid 2345410
                    2026-08-25 17:08:41.380 - error: javascript.0 (2345410) javascript.0 already running
                    2026-08-25 17:08:41.382 - warn: javascript.0 (2345410) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:41.930 - error: host.iob instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:41.930 - info: host.iob Restart adapter system.adapter.javascript.0 because enabled
                    2026-08-25 17:08:44.696 - info: host.iob instance system.adapter.pushover.0 in version "5.0.0" started with pid 2345422
                    2026-08-25 17:08:45.135 - error: pushover.0 (2345422) pushover.0 already running
                    2026-08-25 17:08:45.137 - warn: pushover.0 (2345422) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:45.682 - error: host.iob instance system.adapter.pushover.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:45.682 - info: host.iob Restart adapter system.adapter.pushover.0 because enabled
                    2026-08-25 17:08:48.689 - info: host.iob instance system.adapter.telegram.0 in version "4.1.0" started with pid 2345434
                    2026-08-25 17:08:49.317 - error: telegram.0 (2345434) telegram.0 already running
                    2026-08-25 17:08:49.319 - warn: telegram.0 (2345434) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:49.867 - error: host.iob instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:49.867 - info: host.iob Restart adapter system.adapter.telegram.0 because enabled
                    2026-08-25 17:08:51.070 - info: host.iob instance system.adapter.telegram.0 in version "4.1.0" started with pid 2345446
                    2026-08-25 17:08:52.054 - info: telegram.0 (2345446) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v22.23.2, js-controller: 7.2.2
                    2026-08-25 17:08:52.679 - info: host.iob instance system.adapter.telegram.1 in version "4.1.0" started with pid 2345463
                    2026-08-25 17:08:53.224 - error: telegram.1 (2345463) telegram.1 already running
                    2026-08-25 17:08:53.225 - warn: telegram.1 (2345463) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:53.773 - error: host.iob instance system.adapter.telegram.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:53.773 - info: host.iob Restart adapter system.adapter.telegram.1 because enabled
                    2026-08-25 17:08:54.985 - info: host.iob instance system.adapter.telegram.1 in version "4.1.0" started with pid 2345475
                    2026-08-25 17:08:55.912 - info: telegram.1 (2345475) starting. Version 4.1.0 in /opt/iobroker/node_modules/iobroker.telegram, node: v22.23.2, js-controller: 7.2.2
                    2026-08-25 17:08:56.688 - info: host.iob instance system.adapter.history.0 in version "4.0.0" started with pid 2345492
                    2026-08-25 17:08:57.117 - error: history.0 (2345492) history.0 already running
                    2026-08-25 17:08:57.118 - warn: history.0 (2345492) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:08:57.666 - error: host.iob instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:08:57.666 - info: host.iob Restart adapter system.adapter.history.0 because enabled
                    2026-08-25 17:09:00.733 - info: host.iob instance system.adapter.admin.0 in version "7.8.23" started with pid 2345504
                    2026-08-25 17:09:00.783 - info: host.iob instance system.adapter.influxdb.1 in version "4.0.2" started with pid 2345512
                    2026-08-25 17:09:01.323 - error: influxdb.1 (2345512) influxdb.1 already running
                    2026-08-25 17:09:01.323 - warn: influxdb.1 (2345512) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
                    2026-08-25 17:09:01.875 - error: host.iob instance system.adapter.influxdb.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
                    2026-08-25 17:09:01.875 - info: host.iob Restart adapter system.adapter.influxdb.1 because enabled
                    2026-08-25 17:09:01.910 - info: admin.0 (2345504) starting. Version 7.8.23 in /opt/iobroker/node_modules/iobroker.admin, node: v22.23.2, js-controller: 7.2.2
                    2026-08-25 17:09:01.924 - info: admin.0 (2345504) requesting all objects
                    2026-08-25 17:09:02.703 - info: admin.0 (2345504) received all objects
                    2026-08-25 17:09:02.851 - info: admin.0 (2345504) Request actual repository...
                    2026-08-25 17:09:02.858 - info: admin.0 (2345504) socket.io server listening on port 8081
                    2026-08-25 17:09:02.859 - info: admin.0 (2345504) http server listening on port 8081
                    2026-08-25 17:09:02.859 - info: admin.0 (2345504) Use link "http://127.0.0.1:8081" to configure.
                    2026-08-25 17:09:03.531 - info: host.iob Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
                    2026-08-25 17:09:03.967 - info: host.iob instance system.adapter.influxdb.0 in version "4.0.2" started with pid 2345579
                    2026-08-25 17:09:05.807 - info: admin.0 (2345504) Repository received successfully.
                    2026-08-25 17:09:06.124 - info: host.iob instance system.adapter.hue.0 in version "3.16.2" started with pid 2345612
                    2026-08-25 17:09:07.314 - info: influxdb.0 (2345579) starting. Version 4.0.2 in /opt/iobroker/node_modules/iobroker.influxdb, node: v22.23.2, js-controller: 7.2.2
                    2026-08-25 17:09:07.323 - info: influxdb.0 (2345579) No stored data from last exit found
                    2026-08-25 17:09:07.323 - info: influxdb.0 (2345579) Connecting http://192.168.2.26:8086/ ...
                    2026-08-25 17:09:07.323 - info: influxdb.0 (2345579) Influx DB Version used: 2.x
                    2026-08-25 17:09:07.336 - info: influxdb.0 (2345579) Applying retention policy for iobroker to infinity. Shard Group Duration (calculated): 604800 seconds
                    2026-08-25 17:09:07.374 - info: influxdb.0 (2345579) Connected!
                    2026-08-25 17:09:07.495 - info: influxdb.0 (2345579) enabled logging of nut.0.battery.charge, Alias=false, 1 points now activated
                    2026-08-25 17:09:07.496 - info: influxdb.0 (2345579) enabled logging of tankerkoenig.0.stations.0.e5.feed, Alias=false, 2 points now activated
                    2026-08-25 17:09:07.496 - info: influxdb.0 (2345579) enabled logging of tankerkoenig.0.stations.1.e5.feed, Alias=false, 3 points now activated
                    

                    Die VM hat 8 GB RAM, welches nicht vollgelaufen war:
                    5e8884bb-5ce8-46d2-b371-e2fdf106507f-image.jpeg

                    Bei mir gibt es nur einen Host.

                    PlatformBetriebssystem:linux
                    Architektur:x64
                    CPUs:4
                    Geschwindigkeit:0 MHz
                    Modell:12th Gen Intel(R) Core(TM) i5-1240P
                    RAM:7.7 GB
                    System-Betriebszeit:00:45:41
                    Node.js:v22.23.2
                    Zeit:1788094784836
                    Zeitversatz:-120
                    NPM:10.9.8
                    Adapter-Anzahl:649
                    Datenträgergröße:30.4 GB
                    Freier Festplattenspeicher:17.0 GB
                    Aktive Instanzen:44
                    Pfad:/opt/iobroker/
                    Betriebszeit:-1 T. 0-2:0-15:0-23
                    aktiv:true
                    _nodeCurrent:22.23.2
                    _nodeNewest:22.23.2
                    _nodeNewestNext:22.23.2
                    _npmCurrent:10.9.8
                    _npmNewest:10.9.8
                    _npmNewestNext:10.9.8
                    

                    Gruß

                    Peterfido

                    1 Antwort Letzte Antwort
                    0
                    • P Offline
                      P Offline
                      peterfido
                      schrieb am zuletzt editiert von peterfido
                      #32

                      Am 16.08. hatte ich Updates durchgeführt. Am 18.08. ging der RAM-Verbrauch höher, aber auch wieder runter, ab 24.08. scheint der RAM-Bedarf stetig gestiegen zu sein, bis am 25.08. dann das Problem aufgetreten war. Die RAM-Grenze wurde jedoch nicht erreicht.

                      ed548f4e-77c2-4783-973b-ee6ad2bf8cbc-image.jpeg

                      Gruß

                      Peterfido

                      HomoranH 1 Antwort Letzte Antwort
                      0
                      • P peterfido

                        Am 16.08. hatte ich Updates durchgeführt. Am 18.08. ging der RAM-Verbrauch höher, aber auch wieder runter, ab 24.08. scheint der RAM-Bedarf stetig gestiegen zu sein, bis am 25.08. dann das Problem aufgetreten war. Die RAM-Grenze wurde jedoch nicht erreicht.

                        ed548f4e-77c2-4783-973b-ee6ad2bf8cbc-image.jpeg

                        HomoranH Nicht stören
                        HomoranH Nicht stören
                        Homoran
                        schrieb am zuletzt editiert von
                        #33

                        @peterfido das passt ungefähr zu meinem Problem
                        https://forum.iobroker.net/post/1352534

                        Weisst du noch was du upgedatet hattest?

                        kein Support per PN! - Fragen im Forum stellen - Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
                        der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                        Thomas BraunT P 2 Antworten Letzte Antwort
                        0
                        • HomoranH Homoran

                          @peterfido das passt ungefähr zu meinem Problem
                          https://forum.iobroker.net/post/1352534

                          Weisst du noch was du upgedatet hattest?

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #34

                          Hab gerade mal in meinem System geschaut. Hier genehmigt sich der js-controller ein Drittel des RAMs (8GB auf einem RPi4) im Dauerlauf. Mir fehlen Vergleiche zur jüngeren Vergangenheit, aber ich meine das sei 'früher' weniger gewesen.

                          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 Antwort Letzte Antwort
                          1
                          • HomoranH Homoran

                            @peterfido das passt ungefähr zu meinem Problem
                            https://forum.iobroker.net/post/1352534

                            Weisst du noch was du upgedatet hattest?

                            P Offline
                            P Offline
                            peterfido
                            schrieb am zuletzt editiert von
                            #35

                            @Homoran Nein, leider nicht. Die Logs reichen auch nicht weit genug zurück.

                            Gruß

                            Peterfido

                            1 Antwort Letzte Antwort
                            0
                            • P Offline
                              P Offline
                              peterfido
                              schrieb am zuletzt editiert von
                              #36

                              Ich spiele gerade das Backup vom 29.07. in eine neue VM und schaue mal, welche Versionsnummern die Adapter so haben.

                              Gruß

                              Peterfido

                              1 Antwort Letzte Antwort
                              0
                              • Michael SchmittM Online
                                Michael SchmittM Online
                                Michael Schmitt
                                schrieb am zuletzt editiert von
                                #37

                                @thomas-braun (falls nützlich) Pi4 4gb vor ca 3 Std reboot

                                marvman67@Raspberry:~ $ ps aux --sort=-%mem | head -n 11
                                USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                                iobroker     954  8.4 11.6 12186424 452084 ?     Ssl  14:39  15:29 iobroker.js-controller
                                iobroker    1021  0.7  7.1 22536616 276292 ?     Sl   14:39   1:22 io.admin.0
                                iobroker    1045  1.7  6.7 12031240 262256 ?     Sl   14:40   3:07 io.javascript.0
                                iobroker    1317  0.7  5.6 11994932 218108 ?     Sl   14:40   1:20 io.matter.0
                                iobroker    1410  0.2  4.5 11953160 175936 ?     Sl   14:41   0:31 io.web.0
                                iobroker    1400  0.3  4.2 11939364 165068 ?     Sl   14:41   0:38 io.alexa2.0
                                iobroker    1066  0.2  4.1 11938520 162704 ?     Sl   14:40   0:29 io.telegram.0
                                iobroker    1361  0.2  4.0 11736980 156764 ?     Sl   14:40   0:23 io.socketio.0
                                iobroker    1105  0.2  4.0 11738704 156044 ?     Sl   14:40   0:24 io.backitup.0
                                iobroker    1333  0.2  3.9 11733720 153784 ?     Sl   14:40   0:23 io.simple-api.0
                                
                                Ro75R 1 Antwort Letzte Antwort
                                0
                                • P Offline
                                  P Offline
                                  peterfido
                                  schrieb am zuletzt editiert von peterfido
                                  #38

                                  Für diese gibt es Updates:

                                  4667d8be-c160-489a-8b21-39a62b66120e-image.jpeg

                                  Und halt das System selbst.

                                  Gruß

                                  Peterfido

                                  HomoranH 1 Antwort Letzte Antwort
                                  0
                                  • P peterfido

                                    Für diese gibt es Updates:

                                    4667d8be-c160-489a-8b21-39a62b66120e-image.jpeg

                                    Und halt das System selbst.

                                    HomoranH Nicht stören
                                    HomoranH Nicht stören
                                    Homoran
                                    schrieb am zuletzt editiert von Homoran
                                    #39

                                    @peterfido sagte:

                                    Für diese gibt es Updates:

                                    Danke!
                                    Ich hatte noch ical, matter und go-e charger im kopf
                                    Zigbee hab ich nicht upgedated
                                    Harmony kam bei mir erst gerade eben mit breaking changes.
                                    Die tue ich mir im Moment nicht an

                                    kein Support per PN! - Fragen im Forum stellen - Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                                    Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
                                    der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

                                    1 Antwort Letzte Antwort
                                    0
                                    • P Offline
                                      P Offline
                                      peterfido
                                      schrieb am zuletzt editiert von
                                      #40

                                      apt list --upgradable zeigt Folgende Updates an:

                                      base-files/stable 13.8+deb13u6 amd64 [upgradable from: 13.8+deb13u5]
                                      bind9-dnsutils/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bind9-host/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bind9-libs/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bsdextrautils/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      bsdutils/stable-security 1:2.41.5-0+deb13u1 amd64 [upgradable from: 1:2.41-5]
                                      chromium-common/stable-security 151.0.7922.173-1~deb13u1 amd64 [upgradable from: 149.0.7827.114-1~deb13u1]
                                      chromium-sandbox/stable-security 151.0.7922.173-1~deb13u1 amd64 [upgradable from: 149.0.7827.114-1~deb13u1]
                                      curl/stable 8.14.1-2+deb13u4 amd64 [upgradable from: 8.14.1-2+deb13u3]
                                      dirmngr/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      eject/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      exim4-base/stable-security 4.98.2-1+deb13u4 amd64 [upgradable from: 4.98.2-1+deb13u3]
                                      exim4-config/stable-security 4.98.2-1+deb13u4 all [upgradable from: 4.98.2-1+deb13u3]
                                      exim4-daemon-light/stable-security 4.98.2-1+deb13u4 amd64 [upgradable from: 4.98.2-1+deb13u3]
                                      fdisk/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      gnupg-utils/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-agent/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-wks-client/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-wks-server/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpgconf/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      base-files/stable 13.8+deb13u6 amd64 [upgradable from: 13.8+deb13u5]
                                      bind9-dnsutils/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bind9-host/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bind9-libs/stable-security 1:9.20.26-1~deb13u1 amd64 [upgradable from: 1:9.20.23-1~deb13u1]
                                      bsdextrautils/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      bsdutils/stable-security 1:2.41.5-0+deb13u1 amd64 [upgradable from: 1:2.41-5]
                                      chromium-common/stable-security 151.0.7922.173-1~deb13u1 amd64 [upgradable from: 149.0.7827.114-1~deb13u1]
                                      chromium-sandbox/stable-security 151.0.7922.173-1~deb13u1 amd64 [upgradable from: 149.0.7827.114-1~deb13u1]
                                      curl/stable 8.14.1-2+deb13u4 amd64 [upgradable from: 8.14.1-2+deb13u3]
                                      dirmngr/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      eject/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      exim4-base/stable-security 4.98.2-1+deb13u4 amd64 [upgradable from: 4.98.2-1+deb13u3]
                                      exim4-config/stable-security 4.98.2-1+deb13u4 all [upgradable from: 4.98.2-1+deb13u3]
                                      exim4-daemon-light/stable-security 4.98.2-1+deb13u4 amd64 [upgradable from: 4.98.2-1+deb13u3]
                                      fdisk/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      gnupg-utils/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-agent/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-wks-client/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg-wks-server/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpg/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpgconf/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpgsm/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      gpgv/stable 2.4.7-21+deb13u1+b4 amd64 [upgradable from: 2.4.7-21+deb13u1+b3]
                                      libblkid-dev/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libblkid1/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libcurl3t64-gnutls/stable 8.14.1-2+deb13u4 amd64 [upgradable from: 8.14.1-2+deb13u3]
                                      libcurl4t64/stable 8.14.1-2+deb13u4 amd64 [upgradable from: 8.14.1-2+deb13u3]
                                      libegl-mesa0/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      libexpat1-dev/stable-security 2.8.3-1~deb13u1 amd64 [upgradable from: 2.7.1-2]
                                      libexpat1/stable-security 2.8.3-1~deb13u1 amd64 [upgradable from: 2.7.1-2]
                                      libfdisk1/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libgbm1/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      libgif-dev/stable 5.2.2-1+deb13u1 amd64 [upgradable from: 5.2.2-1+b1]
                                      libgif7/stable 5.2.2-1+deb13u1 amd64 [upgradable from: 5.2.2-1+b1]
                                      libgl1-mesa-dri/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      libglx-mesa0/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      libgraphite2-3/stable 1.3.14-2+deb13u1 amd64 [upgradable from: 1.3.14-2+b1]
                                      libgraphite2-dev/stable 1.3.14-2+deb13u1 amd64 [upgradable from: 1.3.14-2+b1]
                                      libhtml-parser-perl/stable 3.83-2~deb13u1 amd64 [upgradable from: 3.83-1+b2]
                                      libhttp-daemon-perl/stable,stable-security 6.16-1+deb13u1 all [upgradable from: 6.16-1]
                                      liblastlog2-2/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libldb2/stable-security 2:2.11.0+samba4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:2.11.0+samba4.22.8+dfsg-0+deb13u2]
                                      liblzma-dev/stable 5.8.1-1+deb13u1 amd64 [upgradable from: 5.8.1-1]
                                      liblzma5/stable 5.8.1-1+deb13u1 amd64 [upgradable from: 5.8.1-1]
                                      libmount-dev/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libmount1/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libnss3/stable-security 2:3.110-1+deb13u4 amd64 [upgradable from: 2:3.110-1+deb13u2]
                                      libpython3.13-minimal/stable-updates 3.13.5-2+deb13u4 amd64 [upgradable from: 3.13.5-2+deb13u2]
                                      libpython3.13-stdlib/stable-updates 3.13.5-2+deb13u4 amd64 [upgradable from: 3.13.5-2+deb13u2]
                                      libsmartcols1/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libsmbclient0/stable-security 2:4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:4.22.8+dfsg-0+deb13u2]
                                      libssh2-1t64/stable,stable-security 1.11.1-1+deb13u1 amd64 [upgradable from: 1.11.1-1]
                                      libssl3t64/stable-security 3.5.7-1~deb13u2 amd64 [upgradable from: 3.5.6-1~deb13u2]
                                      libtalloc2/stable-security 2:2.4.3+samba4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:2.4.3+samba4.22.8+dfsg-0+deb13u2]
                                      libtasn1-6/stable 4.20.0-2+deb13u1 amd64 [upgradable from: 4.20.0-2]
                                      libtdb1/stable-security 2:1.4.13+samba4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:1.4.13+samba4.22.8+dfsg-0+deb13u2]
                                      libtevent0t64/stable-security 2:0.16.2+samba4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:0.16.2+samba4.22.8+dfsg-0+deb13u2]
                                      libtiff-dev/stable-security 4.7.0-3+deb13u3 amd64 [upgradable from: 4.7.0-3+deb13u2]
                                      libtiff6/stable-security 4.7.0-3+deb13u3 amd64 [upgradable from: 4.7.0-3+deb13u2]
                                      libtiffxx6/stable-security 4.7.0-3+deb13u3 amd64 [upgradable from: 4.7.0-3+deb13u2]
                                      libuuid1/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      libwbclient0/stable-security 2:4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:4.22.8+dfsg-0+deb13u2]
                                      libxml2-dev/stable 2.12.7+dfsg+really2.9.14-2.1+deb13u3 amd64 [upgradable from: 2.12.7+dfsg+really2.9.14-2.1+deb13u2]
                                      libxml2/stable 2.12.7+dfsg+really2.9.14-2.1+deb13u3 amd64 [upgradable from: 2.12.7+dfsg+really2.9.14-2.1+deb13u2]
                                      libxpm4/stable 1:3.5.17-1+deb13u1 amd64 [upgradable from: 1:3.5.17-1+b3]
                                      linux-image-amd64/stable-security 6.12.107-1 amd64 [upgradable from: 6.12.90-2]
                                      linux-libc-dev/stable-security 6.12.107-1 all [upgradable from: 6.12.90-2]
                                      login/stable-security 1:4.16.0-2+really2.41.5-0+deb13u1 amd64 [upgradable from: 1:4.16.0-2+really2.41-5]
                                      mesa-libgallium/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      mesa-vulkan-drivers/stable 25.0.7-2+deb13u1 amd64 [upgradable from: 25.0.7-2]
                                      mount/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      nodejs/nodistro 22.23.2-1nodesource1 amd64 [upgradable from: 22.23.0-1nodesource1]
                                      openssl-provider-legacy/stable-security 3.5.7-1~deb13u2 amd64 [upgradable from: 3.5.6-1~deb13u2]
                                      openssl/stable-security 3.5.7-1~deb13u2 amd64 [upgradable from: 3.5.6-1~deb13u2]
                                      python3-idna/stable 3.10-1+deb13u1 all [upgradable from: 3.10-1]
                                      python3-urllib3/stable,stable-security 2.3.0-3+deb13u2 all [upgradable from: 2.3.0-3+deb13u1]
                                      python3.13-minimal/stable-updates 3.13.5-2+deb13u4 amd64 [upgradable from: 3.13.5-2+deb13u2]
                                      python3.13/stable-updates 3.13.5-2+deb13u4 amd64 [upgradable from: 3.13.5-2+deb13u2]
                                      qemu-guest-agent/stable 1:10.0.11+ds-0+deb13u1 amd64 [upgradable from: 1:10.0.8+ds-0+deb13u1+b2]
                                      samba-libs/stable-security 2:4.22.10+dfsg-0+deb13u2 amd64 [upgradable from: 2:4.22.8+dfsg-0+deb13u2]
                                      unzip/stable-security 6.0-29+deb13u1 amd64 [upgradable from: 6.0-29]
                                      util-linux-extra/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      util-linux/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      uuid-dev/stable-security 2.41.5-0+deb13u1 amd64 [upgradable from: 2.41-5]
                                      xz-utils/stable 5.8.1-1+deb13u1 amd64 [upgradable from: 5.8.1-1]
                                      
                                      

                                      Gruß

                                      Peterfido

                                      1 Antwort Letzte Antwort
                                      0
                                      • Michael SchmittM Michael Schmitt

                                        @thomas-braun (falls nützlich) Pi4 4gb vor ca 3 Std reboot

                                        marvman67@Raspberry:~ $ ps aux --sort=-%mem | head -n 11
                                        USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
                                        iobroker     954  8.4 11.6 12186424 452084 ?     Ssl  14:39  15:29 iobroker.js-controller
                                        iobroker    1021  0.7  7.1 22536616 276292 ?     Sl   14:39   1:22 io.admin.0
                                        iobroker    1045  1.7  6.7 12031240 262256 ?     Sl   14:40   3:07 io.javascript.0
                                        iobroker    1317  0.7  5.6 11994932 218108 ?     Sl   14:40   1:20 io.matter.0
                                        iobroker    1410  0.2  4.5 11953160 175936 ?     Sl   14:41   0:31 io.web.0
                                        iobroker    1400  0.3  4.2 11939364 165068 ?     Sl   14:41   0:38 io.alexa2.0
                                        iobroker    1066  0.2  4.1 11938520 162704 ?     Sl   14:40   0:29 io.telegram.0
                                        iobroker    1361  0.2  4.0 11736980 156764 ?     Sl   14:40   0:23 io.socketio.0
                                        iobroker    1105  0.2  4.0 11738704 156044 ?     Sl   14:40   0:24 io.backitup.0
                                        iobroker    1333  0.2  3.9 11733720 153784 ?     Sl   14:40   0:23 io.simple-api.0
                                        
                                        Ro75R Online
                                        Ro75R Online
                                        Ro75
                                        schrieb am zuletzt editiert von
                                        #41

                                        @Michael-Schmitt @thomas-braun

                                        Da ja möglichweise was mit der Speicherveraltung oder einem Update klemmt. Ubuntu 22.04.5 LTS - läuft seit 42 Tagen, N5105 mit 16 GB RAM.

                                            PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     ZEIT+ BEFEHL
                                        3287865 iobroker  20   0   12,0g 224512  22576 S  15,8   1,4   1307:25 io.web.0
                                        3288925 iobroker  20   0   12,6g 804896  25456 S   9,9   5,0   1737:45 io.javascript.0
                                         434432 iobroker  20   0   11,7g 116764  21324 S   2,6   0,7 419:43.07 io.hue.0
                                        3884311 iobroker  20   0   12,0g 196388  18956 S   2,0   1,2   2204:08 io.sql.0
                                        3368243 iobroker  20   0   21,7g 138832  56148 S   1,0   0,9   2:23.29 io.linux-contro
                                        3883571 iobroker  20   0   22,1g 286824  22620 S   0,7   1,8 109:46.45 io.admin.0
                                        3884784 iobroker  20   0   11,9g 111968  19912 S   0,7   0,7 703:44.45 io.zigbee.0
                                         663399 iobroker  20   0   11,9g 119176  33124 S   0,0   0,7   4:04.96 io.alexa2.0
                                         797716 iobroker  20   0   11,9g 175312  33344 S   0,0   1,1  42:33.53 io.parcel.0
                                        1166049 iobroker  20   0   11,3g  99628  31892 S   0,0   0,6   1:58.15 io.backitup.0
                                        1685378 iobroker  20   0   11,3g  65616  20028 S   0,0   0,4  35:57.01 io.vesync.0
                                        3074220 iobroker  20   0   11,9g 141296  53196 S   0,0   0,9   0:38.19 io.homeconnect.
                                        3124703 iobroker  20   0   12,7g 318456  67880 S   0,0   2,0   9:17.80 io.roborock.0
                                        3609322 iobroker  20   0   11,4g 156428  20532 S   0,0   1,0   1528:49 io.public-trans
                                        3883527 iobroker  20   0   12,0g 162576  21652 S   0,0   1,0  77:31.98 iobroker.js-con
                                        3884379 iobroker  20   0   21,8g 143348  19188 S   0,0   0,9 100:14.18 io.owntracks.0
                                        3884407 iobroker  20   0   11,7g  82976  18108 S   0,0   0,5  45:53.16 io.sonoff.0
                                        

                                        Ro75.

                                        SERVER = Beelink U59 16GB DDR4 RAM 512GB SSD, FB 7490, FritzDect 200+301+440, ConBee II, Zigbee Aqara Sensoren + NOUS A1Z, NOUS A1T, Philips Hue ** ioBroker, REDIS, influxdb2, Grafana, PiHole, Plex-Mediaserver, paperless-ngx (Docker), MariaDB + phpmyadmin *** VIS-Runtime = Intel NUC 8GB RAM 128GB SSD + 24" Touchscreen

                                        Thomas BraunT 1 Antwort Letzte Antwort
                                        0
                                        • Ro75R Ro75

                                          @Michael-Schmitt @thomas-braun

                                          Da ja möglichweise was mit der Speicherveraltung oder einem Update klemmt. Ubuntu 22.04.5 LTS - läuft seit 42 Tagen, N5105 mit 16 GB RAM.

                                              PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     ZEIT+ BEFEHL
                                          3287865 iobroker  20   0   12,0g 224512  22576 S  15,8   1,4   1307:25 io.web.0
                                          3288925 iobroker  20   0   12,6g 804896  25456 S   9,9   5,0   1737:45 io.javascript.0
                                           434432 iobroker  20   0   11,7g 116764  21324 S   2,6   0,7 419:43.07 io.hue.0
                                          3884311 iobroker  20   0   12,0g 196388  18956 S   2,0   1,2   2204:08 io.sql.0
                                          3368243 iobroker  20   0   21,7g 138832  56148 S   1,0   0,9   2:23.29 io.linux-contro
                                          3883571 iobroker  20   0   22,1g 286824  22620 S   0,7   1,8 109:46.45 io.admin.0
                                          3884784 iobroker  20   0   11,9g 111968  19912 S   0,7   0,7 703:44.45 io.zigbee.0
                                           663399 iobroker  20   0   11,9g 119176  33124 S   0,0   0,7   4:04.96 io.alexa2.0
                                           797716 iobroker  20   0   11,9g 175312  33344 S   0,0   1,1  42:33.53 io.parcel.0
                                          1166049 iobroker  20   0   11,3g  99628  31892 S   0,0   0,6   1:58.15 io.backitup.0
                                          1685378 iobroker  20   0   11,3g  65616  20028 S   0,0   0,4  35:57.01 io.vesync.0
                                          3074220 iobroker  20   0   11,9g 141296  53196 S   0,0   0,9   0:38.19 io.homeconnect.
                                          3124703 iobroker  20   0   12,7g 318456  67880 S   0,0   2,0   9:17.80 io.roborock.0
                                          3609322 iobroker  20   0   11,4g 156428  20532 S   0,0   1,0   1528:49 io.public-trans
                                          3883527 iobroker  20   0   12,0g 162576  21652 S   0,0   1,0  77:31.98 iobroker.js-con
                                          3884379 iobroker  20   0   21,8g 143348  19188 S   0,0   0,9 100:14.18 io.owntracks.0
                                          3884407 iobroker  20   0   11,7g  82976  18108 S   0,0   0,5  45:53.16 io.sonoff.0
                                          

                                          Ro75.

                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von
                                          #42

                                          @Ro75

                                          Welche Version des js-controllers läuft da?

                                          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

                                          Ro75R 1 Antwort Letzte Antwort
                                          0

                                          Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.

                                          Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.

                                          Mit deinem Input könnte dieser Beitrag noch besser werden 💗

                                          Registrieren Anmelden
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

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

                                          294

                                          Online

                                          33.0k

                                          Benutzende

                                          83.7k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2026
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe