Weiter zum Inhalt
  • Home
  • Aktuell
  • Tags
  • 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. Raspi4 2GB / ioBroker startet jeden Tag neu ?

NEWS

  • Neuer ioBroker-Blog online: Monatsrückblick März/April 2026
    BluefoxB
    Bluefox
    8
    1
    1.7k

  • Verwendung von KI bitte immer deutlich kennzeichnen
    HomoranH
    Homoran
    10
    1
    712

  • Monatsrückblick Januar/Februar 2026 ist online!
    BluefoxB
    Bluefox
    18
    1
    1.2k

Raspi4 2GB / ioBroker startet jeden Tag neu ?

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
41 Beiträge 9 Kommentatoren 1.3k Aufrufe 6 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.
  • HumidorH Humidor

    Hallo Gemeinde,

    könnt ihr aus dem Log da was erkennen?
    es fängt an mit ECONNRESET und dann sind die DB closed, irgendwann gibt er auf und startet neu.


    2022-11-05 22:58:11.742 - error: go-e.0 (144279) Objects database error: write ECONNRESET
    2022-11-05 22:58:11.748 - error: life360.0 (155077) States database error: write ECONNRESET
    2022-11-05 22:58:11.848 - error: backitup.0 (144084) States database error: read ECONNRESET
    2022-11-05 22:58:11.767 - error: go-e.0 (144279) States database error: write ECONNRESET
    2022-11-05 22:58:11.950 - error: fronius.0 (153864) States database error: write ECONNRESET
    2022-11-05 22:58:12.021 - info: life360.0 (155077) cleaned everything up...
    2022-11-05 22:58:12.017 - info: backitup.0 (144084) cleaned everything up...
    2022-11-05 22:58:12.090 - error: renault.0 (144298) States database error: read ECONNRESET
    2022-11-05 22:58:11.729 - error: echarts.0 (144348) States database error: write ECONNRESET
    2022-11-05 22:58:11.731 - error: vis-inventwo.0 (144253) States database error: write ECONNRESET
    2022-11-05 22:58:11.730 - error: time-switch.0 (144359) States database error: write ECONNRESET
    2022-11-05 22:58:12.308 - error: modbus.1 (143976) States database error: write ECONNRESET
    2022-11-05 22:58:12.324 - error: kecontact.0 (144333) Objects database error: write ECONNRESET
    2022-11-05 22:58:12.326 - error: javascript.0 (143862) Objects database error: write ECONNRESET
    2022-11-05 22:58:11.928 - error: fritzdect.0 (144317) Objects database error: write ECONNRESET
    2022-11-05 22:58:12.251 - error: fritzdect.0 (144317) States database error: write ECONNRESET
    2022-11-05 22:58:12.339 - info: vis-inventwo.0 (144253) cleaned everything up...
    2022-11-05 22:58:12.213 - error: modbus.0 (164056) States database error: write ECONNRESET
    2022-11-05 22:12:46.131 - info: cloud.0 (143910) Connection changed: disconnect
    2022-11-05 22:58:12.376 - error: cloud.0 (143910) States database error: write ECONNRESET
    2022-11-05 22:58:12.374 - error: vis-inventwo.0 (144253) uncaught exception: write EPIPE
    2022-11-05 22:58:12.377 - error: vis-inventwo.0 (144253) Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:874:11)
    at Socket._write (node:net:886:8)
    at writeOrBuffer (node:internal/streams/writable:391:12)
    at _write (node:internal/streams/writable:332:10)
    at Socket.Writable.write (node:internal/streams/writable:336:10)
    at console.value (node:internal/console/constructor:299:16)
    at console.warn (node:internal/console/constructor:381:26)
    at /opt/iobroker/node_modules/pidusage/lib/helpers/cpu.js:45:17
    2022-11-05 22:58:12.392 - error: vis-inventwo.0 (144253) Exception-Code: EPIPE: write EPIPE
    2022-11-05 22:58:12.319 - error: shelly.0 (144069) Objects database error: write EPIPE
    2022-11-05 22:58:12.469 - error: modbus.1 (143976) Objects database error: read ECONNRESET
    2022-11-05 22:58:12.333 - error: iot.0 (154615) States database error: write ECONNRESET
    2022-11-05 22:58:12.513 - info: iot.0 (154615) Connection changed: disconnect
    2022-11-05 22:58:12.515 - info: iot.0 (154615) Connection lost
    2022-11-05 22:58:12.254 - error: s7.0 (144032) States database error: write ECONNRESET
    2022-11-05 22:58:12.527 - error: s7.0 (144032) Objects database error: write ECONNRESET
    2022-11-05 22:58:12.366 - error: modbus.0 (164056) Objects database error: read ECONNRESET
    2022-11-05 22:58:12.454 - info: fritzdect.0 (144317) cleaned everything up...
    2022-11-05 22:58:12.461 - info: time-switch.0 (144359) cleaning everything up...
    2022-11-05 22:58:12.618 - error: modbus.1 (143976) Socket Error
    2022-11-05 22:58:12.610 - error: kecontact.0 (144333) States database error: write ECONNRESET
    2022-11-05 22:58:12.228 - error: web.0 (144106) States database error: write ECONNRESET
    2022-11-05 22:58:12.619 - error: modbus.1 (143976) Client in error state.
    2022-11-05 22:58:12.524 - error: admin.0 (143804) States database error: write ECONNRESET
    2022-11-05 22:58:12.624 - error: ws.0 (144379) States database error: write ECONNRESET
    2022-11-05 22:58:12.758 - info: renault.0 (144298) battery-status receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:12.479 - error: shelly.0 (144069) States database error: write ECONNRESET
    2022-11-05 22:58:12.846 - error: mqtt.0 (144006) Objects database error: write ECONNRESET
    2022-11-05 22:58:12.905 - error: mqtt.0 (144006) States database error: write ECONNRESET
    2022-11-05 22:58:13.011 - info: renault.0 (144298) battery-inhibition-status receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:13.137 - error: telegram.0 (143890) States database error: write ECONNRESET
    2022-11-05 22:58:13.261 - info: renault.0 (144298) cockpit receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:13.520 - info: renault.0 (144298) cockpitv2 receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:13.541 - info: fronius.0 (153864) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.524 - info: go-e.0 (144279) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.537 - info: backitup.0 (144084) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.541 - info: life360.0 (155077) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.627 - error: javascript.0 (143862) States database error: write ECONNRESET
    2022-11-05 22:58:13.658 - info: javascript.0 (143862) Stop script script.js.common.AMIS_Fronius
    2022-11-05 22:58:13.660 - info: javascript.0 (143862) Stop script script.js.common.AMIS_Home
    2022-11-05 22:58:13.661 - info: javascript.0 (143862) Stop script script.js.common.C35
    2022-11-05 22:58:13.662 - info: javascript.0 (143862) Stop script script.js.common.SE_Power
    2022-11-05 22:58:13.663 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Ladung_Ziel
    2022-11-05 22:58:13.666 - info: javascript.0 (143862) Stop script script.js.common.ZOE_MIN_Ladung
    2022-11-05 22:58:13.667 - info: javascript.0 (143862) Stop script script.js.common.go-E_Error
    2022-11-05 22:58:13.668 - info: javascript.0 (143862) Stop script script.js.common.go-E_Limits
    2022-11-05 22:58:13.668 - info: javascript.0 (143862) Stop script script.js.common.go-E_Verriegelung
    2022-11-05 22:58:13.669 - info: javascript.0 (143862) Stop script script.js.common.ZOE_GridOffset
    2022-11-05 22:58:13.669 - info: javascript.0 (143862) Stop script script.js.common.ZOE_MinMax
    2022-11-05 22:58:13.670 - info: javascript.0 (143862) Stop script script.js.common.go-E_Control
    2022-11-05 22:58:13.671 - info: javascript.0 (143862) Stop script script.js.common.go-E_GridOffset
    2022-11-05 22:58:13.672 - info: javascript.0 (143862) Stop script script.js.common.Pool_Steuerung
    2022-11-05 22:58:13.672 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Phasen
    2022-11-05 22:58:13.673 - info: javascript.0 (143862) Stop script script.js.common.go-E_Init
    2022-11-05 22:58:13.673 - info: javascript.0 (143862) Stop script script.js.common.go-E_Überschuss
    2022-11-05 22:58:13.674 - info: javascript.0 (143862) Stop script script.js.common.go-E_Überwachung
    2022-11-05 22:58:13.674 - info: javascript.0 (143862) Stop script script.js.common.Grid-PV
    2022-11-05 22:58:13.676 - info: javascript.0 (143862) Stop script script.js.common.Grid-PVFronius
    2022-11-05 22:58:13.677 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Debug
    2022-11-05 22:58:13.678 - info: javascript.0 (143862) Stop script script.js.common.go-E_Phasen
    2022-11-05 22:58:13.679 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Regelung
    2022-11-05 22:58:13.679 - info: javascript.0 (143862) Stop script script.js.common.Pool
    2022-11-05 22:58:13.680 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Steuerung
    2022-11-05 22:58:13.680 - info: javascript.0 (143862) Stop script script.js.common.go-E_Charger
    2022-11-05 22:58:13.681 - info: javascript.0 (143862) Stop script script.js.common.Garage
    2022-11-05 22:58:13.682 - info: javascript.0 (143862) Stop script script.js.common.ZOE_Init
    2022-11-05 22:58:13.682 - info: javascript.0 (143862) Stop script script.js.common.Adapter_Blockly
    2022-11-05 22:58:13.712 - info: echarts.0 (144348) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.772 - info: renault.0 (144298) charge-mode receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:13.817 - info: renault.0 (144298) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.843 - info: vis-inventwo.0 (144253) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.919 - info: cloud.0 (143910) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.966 - info: time-switch.0 (144359) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.973 - info: daswetter.0 (164348) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:13.989 - info: fritzdect.0 (144317) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:14.007 - info: iot.0 (154615) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:14.008 - info: renault.0 (144298) hvac-status receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:14.075 - info: s7.0 (144032) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:14.182 - info: kecontact.0 (144333) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:14.244 - info: renault.0 (144298) hvac-settings receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:14.492 - info: shelly.0 (144069) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:14.518 - info: renault.0 (144298) charging-settings receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:14.756 - info: renault.0 (144298) charges receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:14.996 - info: renault.0 (144298) location receive 401 error. Refresh Token in 60 seconds
    2022-11-05 22:58:15.162 - info: javascript.0 (143862) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:16.770 - error: go-e.0 (144279) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:16.796 - error: life360.0 (155077) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:16.804 - warn: life360.0 (155077) get state error: Connection is closed.
    2022-11-05 22:58:16.806 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.806 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.807 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.807 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.808 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.809 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.809 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.810 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.811 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.812 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.812 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.813 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.814 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.814 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.815 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.816 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.816 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.817 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.817 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.818 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.819 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.820 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.820 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.820 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.821 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.821 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.821 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.822 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.822 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.822 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.822 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.823 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.824 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.824 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.824 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.824 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.825 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.825 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.825 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.826 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.826 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.827 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.827 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.828 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.828 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.828 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.829 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.829 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.829 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.829 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.830 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.830 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.830 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.830 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.831 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.831 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.831 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.832 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.832 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.832 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.832 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.833 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.833 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.833 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.833 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.834 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.834 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.834 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.834 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.835 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.835 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.835 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.840 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.840 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.840 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.841 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.841 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.841 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.841 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.842 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.842 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.842 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.842 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.843 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.843 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.843 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.843 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.844 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.844 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.844 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.844 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.845 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.845 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.845 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.845 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.846 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.846 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.846 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.846 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.847 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.847 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.847 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.847 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.848 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.848 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.848 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.848 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.849 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.850 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.850 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.851 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.851 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.852 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.852 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.852 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.852 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.853 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.853 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.853 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.853 - warn: life360.0 (155077) get state error: DB closed
    2022-11-05 22:58:16.882 - warn: backitup.0 (144084) get state error: DB closed
    2022-11-05 22:58:16.888 - warn: go-e.0 (144279) get state error: Connection is closed.
    2022-11-05 22:58:16.889 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.889 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.890 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.890 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.890 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.890 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.890 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.891 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.891 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.891 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.891 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.892 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.892 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.892 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.892 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.898 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.898 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.898 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.898 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.902 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.902 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.902 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.903 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.903 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.903 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.903 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.903 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.904 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.904 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.904 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.904 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.904 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.905 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.906 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.906 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.906 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.906 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.906 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.907 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.907 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.909 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.909 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.910 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.910 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.910 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.910 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.910 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.911 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.912 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.912 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.912 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.912 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.913 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.913 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.913 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.913 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:16.913 - warn: go-e.0 (144279) get state error: DB closed
    2022-11-05 22:58:17.010 - error: fronius.0 (153864) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.218 - error: fritzdect.0 (144317) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.225 - error: echarts.0 (144348) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.347 - error: javascript.0 (143862) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.365 - error: vis-inventwo.0 (144253) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.403 - warn: renault.0 (144298) get state error: Connection is closed.
    2022-11-05 22:58:17.413 - warn: cloud.0 (143910) get state error: Connection is closed.
    2022-11-05 22:58:17.404 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.405 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.405 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.406 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.406 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.407 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.407 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.407 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.408 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.409 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.409 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.413 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.413 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.414 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.414 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.415 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.415 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.415 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.416 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.416 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.416 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.417 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.417 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.417 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.418 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.418 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.418 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.419 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.419 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.420 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.420 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.420 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.421 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.421 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.421 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.422 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.422 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.422 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.423 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.423 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.423 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.424 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.424 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.424 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.425 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.425 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.425 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.426 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.426 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.426 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.427 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.427 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.428 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.428 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.428 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.429 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.429 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.429 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.430 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.430 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.431 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.431 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.431 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.432 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.432 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.432 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.433 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.433 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.433 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.434 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.434 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.434 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.435 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.435 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.436 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.436 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.437 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.437 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.438 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.438 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.439 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.440 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.440 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.441 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.441 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.442 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.442 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.443 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.443 - warn: renault.0 (144298) get state error: DB closed
    2022-11-05 22:58:17.448 - error: kecontact.0 (144333) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.482 - error: shelly.0 (144069) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.526 - error: modbus.0 (164056) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.554 - error: modbus.1 (143976) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.560 - error: s7.0 (144032) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.563 - warn: iot.0 (154615) get state error: Connection is closed.
    2022-11-05 22:58:17.582 - warn: time-switch.0 (144359) get state error: Connection is closed.
    2022-11-05 22:58:17.566 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.568 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.569 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.570 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.572 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.573 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.574 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.578 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.581 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.582 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.584 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.585 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.586 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.587 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.589 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.590 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.591 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.592 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.593 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.595 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.596 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.597 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.598 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.599 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.600 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.601 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.602 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.603 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.603 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.604 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.605 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.606 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.607 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.607 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.608 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.609 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.609 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.610 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.611 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.612 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.612 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.618 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.619 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.620 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.621 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.621 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.622 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.622 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.623 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.623 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.624 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.624 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.625 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.625 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.625 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.626 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.626 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.627 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.627 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.628 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.628 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.629 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.629 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.630 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.630 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.631 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.631 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.632 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.632 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.633 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.633 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.633 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.634 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.634 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.635 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.635 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.636 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.636 - warn: iot.0 (154615) get state error: DB closed
    2022-11-05 22:58:17.673 - warn: fritzdect.0 (144317) get state error: Connection is closed.
    2022-11-05 22:58:17.695 - warn: kecontact.0 (144333) get state error: Connection is closed.
    2022-11-05 22:58:17.690 - warn: daswetter.0 (164348) get state error: Connection is closed.
    2022-11-05 22:58:17.781 - error: ws.0 (144379) States database error: connect ECONNREFUSED 127.0.0.1:9000
    2022-11-05 22:58:17.790 - error: ws.0 (144379) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:17.700 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.700 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.701 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.701 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.702 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.702 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.702 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.703 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.705 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.706 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.706 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.707 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.707 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.708 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.708 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.709 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.709 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.709 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.710 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.734 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.735 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.735 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.736 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.741 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.742 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.771 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.771 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.772 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.772 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.773 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.773 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.773 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.774 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.774 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.775 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.775 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.776 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.776 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.776 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.777 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.777 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.777 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.778 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.793 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.793 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.794 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.794 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.795 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.796 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.796 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.797 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.797 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.798 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.799 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.799 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.800 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.803 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.803 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.803 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.804 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.804 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.804 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.804 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.804 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.805 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.805 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.805 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.805 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.805 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.806 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.806 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.807 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.808 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.809 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.810 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.810 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.810 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.810 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.810 - warn: kecontact.0 (144333) get state error: DB closed
    2022-11-05 22:58:17.910 - error: mqtt.0 (144006) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:18.001 - warn: shelly.0 (144069) get state error: Connection is closed.
    2022-11-05 22:58:18.003 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.003 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.003 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.004 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.005 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.005 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.006 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.008 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#8044C6#1.firmware, error - DB closed
    2022-11-05 22:58:18.009 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#EED8F9#1.firmware, error - DB closed
    2022-11-05 22:58:18.010 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#BC6DEB#1.firmware, error - DB closed
    2022-11-05 22:58:18.010 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#DCCD03#1.firmware, error - DB closed
    2022-11-05 22:58:18.011 - warn: shelly.0 (144069) redis get shelly.0.SHSW-25#483FDA8241A8#1.firmware, error - DB closed
    2022-11-05 22:58:18.011 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.011 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#DCCD03#1.Relay0.Timer, error - DB closed
    2022-11-05 22:58:18.011 - warn: shelly.0 (144069) redis get shelly.0.SHSW-25#483FDA8241A8#1.Relay0.Timer, error - DB closed
    2022-11-05 22:58:18.012 - warn: shelly.0 (144069) redis get shelly.0.SHPLG-S#8044C6#1.Relay0.Timer, error - DB closed
    2022-11-05 22:58:18.012 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.013 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.013 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.016 - warn: shelly.0 (144069) get state error: DB closed
    2022-11-05 22:58:18.030 - warn: shelly.0 (144069) redis get shelly.0.SHSW-25#483FDA8241A8#1.Relay1.Timer, error - Connection is closed.
    2022-11-05 22:58:18.037 - warn: shelly.0 (144069) redis get shelly.0.SHSW-25#483FDA8241A8#1.Shutter.Duration, error - Connection is closed.
    2022-11-05 22:58:12.374 - error: history.0 (143831) States database error: write EPIPE
    2022-11-05 22:58:18.695 - warn: javascript.0 (143862) get state error: Connection is closed.
    2022-11-05 22:58:18.696 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.697 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.698 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.698 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.698 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.698 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.698 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.699 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.699 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.699 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.699 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.699 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.700 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.701 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.705 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.706 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.706 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.707 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.708 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.708 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.709 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.709 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.709 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.709 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.710 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.710 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.710 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.715 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.715 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.715 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.715 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.716 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.716 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.716 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.717 - warn: javascript.0 (143862) redis get javascript.0.variables.isDayTime, error - DB closed
    2022-11-05 22:58:18.717 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.717 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.717 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.718 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.718 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.719 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.720 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.720 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.720 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.721 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.721 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.721 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.721 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.722 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.723 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.724 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.725 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.726 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:18.727 - warn: javascript.0 (143862) get state error: DB closed
    2022-11-05 22:58:22.496 - error: shelly.0 (144069) Cannot find view "system" for search "device" : DB closed
    2022-11-05 22:58:22.810 - error: ws.0 (144379) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:29.223 - error: history.0 (143831) States database error: connect ECONNREFUSED 127.0.0.1:9000
    2022-11-05 22:58:29.273 - error: history.0 (143831) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:34.231 - error: history.0 (143831) States database error: connect ECONNREFUSED 127.0.0.1:9000
    2022-11-05 22:58:34.296 - error: history.0 (143831) Objects database error: connect ECONNREFUSED 127.0.0.1:9001
    2022-11-05 22:58:35.193 - info: history.0 (143831) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
    2022-11-05 22:58:39.251 - warn: history.0 (143831) get state error: Connection is closed.
    2022-11-05 22:58:44.929 - info: host.raspberrypi iobroker.js-controller version 4.0.23 js-controller starting
    2022-11-05 22:58:44.936 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
    2022-11-05 22:58:44.937 - info: host.raspberrypi hostname: raspberrypi, node: v16.17.1
    2022-11-05 22:58:44.938 - info: host.raspberrypi ip addresses: 192.168.0.92 fe80::8511:91de:53a6:d2db 192.168.0.93 fe80::4e06:c2e7:21eb:13ec
    2022-11-05 22:58:46.521 - info: host.raspberrypi connected to Objects and States
    2022-11-05 22:58:46.590 - info: host.raspberrypi added notifications configuration of host
    2022-11-05 22:58:47.359 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeCurrent"
    2022-11-05 22:58:47.361 - info: host.raspberrypi 35 instances found
    2022-11-05 22:58:47.437 - info: host.raspberrypi starting 28 instances
    2022-11-05 22:58:47.623 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewest"
    2022-11-05 22:58:47.694 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 164478
    2022-11-05 22:58:47.711 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewestNext"
    2022-11-05 22:58:47.768 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmCurrent"
    2022-11-05 22:58:47.827 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest"
    2022-11-05 22:58:47.888 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext"
    2022-11-05 22:58:47.949 - info: host.raspberrypi Some obsolete host states deleted.
    2022-11-05 22:58:49.727 - error: admin.0 (164478) admin.0 already running
    2022-11-05 22:58:50.321 - error: host.raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:58:50.322 - info: host.raspberrypi Restart adapter system.adapter.admin.0 because enabled
    2022-11-05 22:58:51.505 - info: host.raspberrypi instance system.adapter.history.0 started with pid 164489
    2022-11-05 22:58:52.937 - error: history.0 (164489) history.0 already running
    2022-11-05 22:58:52.942 - warn: history.0 (164489) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2022-11-05 22:58:53.577 - error: host.raspberrypi instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:58:53.578 - info: host.raspberrypi Restart adapter system.adapter.history.0 because enabled
    2022-11-05 22:58:55.508 - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 164500
    2022-11-05 22:58:58.813 - error: javascript.0 (164500) javascript.0 already running
    2022-11-05 22:58:58.817 - warn: javascript.0 (164500) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2022-11-05 22:58:59.412 - error: host.raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:58:59.413 - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled
    2022-11-05 22:58:59.513 - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 164511
    2022-11-05 22:59:01.967 - error: telegram.0 (164511) telegram.0 already running
    2022-11-05 22:59:02.549 - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:02.549 - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
    2022-11-05 22:59:03.501 - info: host.raspberrypi instance system.adapter.cloud.0 started with pid 164522
    2022-11-05 22:59:05.084 - error: cloud.0 (164522) cloud.0 already running
    2022-11-05 22:59:05.089 - warn: cloud.0 (164522) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2022-11-05 22:59:05.664 - error: host.raspberrypi instance system.adapter.cloud.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:05.665 - info: host.raspberrypi Restart adapter system.adapter.cloud.0 because enabled
    2022-11-05 22:59:07.528 - info: host.raspberrypi instance system.adapter.modbus.0 started with pid 164533
    2022-11-05 22:59:09.032 - error: modbus.0 (164533) modbus.0 already running
    2022-11-05 22:59:09.609 - error: host.raspberrypi instance system.adapter.modbus.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:09.609 - info: host.raspberrypi Restart adapter system.adapter.modbus.0 because enabled
    2022-11-05 22:59:11.517 - info: host.raspberrypi instance system.adapter.modbus.1 started with pid 164544
    2022-11-05 22:59:12.945 - error: modbus.1 (164544) modbus.1 already running
    2022-11-05 22:59:13.528 - error: host.raspberrypi instance system.adapter.modbus.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:13.528 - info: host.raspberrypi Restart adapter system.adapter.modbus.1 because enabled
    2022-11-05 22:59:15.573 - info: host.raspberrypi instance system.adapter.mqtt.0 started with pid 164555
    2022-11-05 22:59:16.977 - error: mqtt.0 (164555) mqtt.0 already running
    2022-11-05 22:59:17.555 - error: host.raspberrypi instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:17.556 - info: host.raspberrypi Restart adapter system.adapter.mqtt.0 because enabled
    2022-11-05 22:59:19.522 - info: host.raspberrypi instance system.adapter.s7.0 started with pid 164566
    2022-11-05 22:59:20.392 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 164573
    2022-11-05 22:59:21.118 - error: s7.0 (164566) s7.0 already running
    2022-11-05 22:59:21.124 - warn: s7.0 (164566) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
    2022-11-05 22:59:21.704 - error: host.raspberrypi instance system.adapter.s7.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
    2022-11-05 22:59:21.705 - info: host.raspberrypi Restart adapter system.adapter.s7.0 because enabled
    2022-11-05 22:59:23.871 - info: host.raspberrypi instance system.adapter.history.0 started with pid 164600
    2022-11-05 22:59:23.933 - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 164606
    2022-11-05 22:59:25.807 - info: host.raspberrypi Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
    2022-11-05 22:59:26.825 - info: history.0 (164600) starting. Version 2.2.0 in /opt/iobroker/node_modules/iobroker.history, node: v16.17.1, js-controller: 4.0.23
    2022-11-05 22:59:27.079 - info: history.0 (164600) enabled logging of fronius.0.inverter.1.PAC (Count=1), Alias=false
    2022-11-05 22:59:27.081 - info: history.0 (164600) enabled logging of go-e.0.amperePV (Count=2), Alias=false
    2022-11-05 22:59:27.083 - info: history.0 (164600) enabled logging of go-e.0.allow_charging (Count=3), Alias=false
    2022-11-05 22:59:27.0

    CodierknechtC Offline
    CodierknechtC Offline
    Codierknecht
    Developer Most Active
    schrieb am zuletzt editiert von
    #4

    @humidor
    Hmmmm, ich betreibe den Broker zwar nicht auf 'nem Raspi, aber bei 2GB würde ich eher die RAM-Ausstattung als den Plattenplatz im Verdacht haben. Insbesondere bei der Anzahl der Adapter die im Log zu sehen sind.

    "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

    Proxmox 9.1.1 LXC|8 GB|Core i7-6700
    HmIP|ZigBee|Tasmota|Unifi
    Zabbix Certified Specialist
    Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

    crunchipC 1 Antwort Letzte Antwort
    0
    • CodierknechtC Codierknecht

      @humidor
      Hmmmm, ich betreibe den Broker zwar nicht auf 'nem Raspi, aber bei 2GB würde ich eher die RAM-Ausstattung als den Plattenplatz im Verdacht haben. Insbesondere bei der Anzahl der Adapter die im Log zu sehen sind.

      crunchipC Abwesend
      crunchipC Abwesend
      crunchip
      Forum Testing Most Active Developer
      schrieb am zuletzt editiert von
      #5

      @codierknecht allerdings

      @humidor sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

      2022-11-05 22:58:47.361 - info: host.raspberrypi 35 instances found
      2022-11-05 22:58:47.437 - info: host.raspberrypi starting 28 instances

      umgestiegen von Proxmox auf Unraid

      HumidorH 1 Antwort Letzte Antwort
      0
      • crunchipC crunchip

        @codierknecht allerdings

        @humidor sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

        2022-11-05 22:58:47.361 - info: host.raspberrypi 35 instances found
        2022-11-05 22:58:47.437 - info: host.raspberrypi starting 28 instances

        HumidorH Offline
        HumidorH Offline
        Humidor
        schrieb am zuletzt editiert von
        #6

        @crunchip der RAM ist durchaus ein Kandidat, aber was füllt ihn auf ?
        Bildschirmfoto 2022-11-07 um 12.41.22.png

        BG

        CodierknechtC 1 Antwort Letzte Antwort
        0
        • HumidorH Humidor

          @crunchip der RAM ist durchaus ein Kandidat, aber was füllt ihn auf ?
          Bildschirmfoto 2022-11-07 um 12.41.22.png

          CodierknechtC Offline
          CodierknechtC Offline
          Codierknecht
          Developer Most Active
          schrieb am zuletzt editiert von
          #7

          @humidor
          Die 24 laufenden Prozesse?
          Jeder Prozess braucht Speicher ... und irgendwann ist einfach Ende Gelände ;-)

          "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

          Proxmox 9.1.1 LXC|8 GB|Core i7-6700
          HmIP|ZigBee|Tasmota|Unifi
          Zabbix Certified Specialist
          Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

          HumidorH 1 Antwort Letzte Antwort
          0
          • CodierknechtC Codierknecht

            @humidor
            Die 24 laufenden Prozesse?
            Jeder Prozess braucht Speicher ... und irgendwann ist einfach Ende Gelände ;-)

            HumidorH Offline
            HumidorH Offline
            Humidor
            schrieb am zuletzt editiert von
            #8

            @codierknecht schon klar, aber der Ram verbraucht sich nach Zeit, dh. mind. ein Adapter müllt den zu

            BG

            CodierknechtC 1 Antwort Letzte Antwort
            0
            • HumidorH Humidor

              @codierknecht schon klar, aber der Ram verbraucht sich nach Zeit, dh. mind. ein Adapter müllt den zu

              CodierknechtC Offline
              CodierknechtC Offline
              Codierknecht
              Developer Most Active
              schrieb am zuletzt editiert von
              #9

              @humidor
              https://www.howtoforge.de/anleitung/wie-man-laufende-prozesse-unter-linux-anzeigt/

              iobroker@iobroker:/opt/iobroker# top
              

              Da müsste sich dann nach Deiner Annahme ein Prozess mit massivem Speicherverbrauch finden lassen ...

              "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

              Proxmox 9.1.1 LXC|8 GB|Core i7-6700
              HmIP|ZigBee|Tasmota|Unifi
              Zabbix Certified Specialist
              Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

              HumidorH 1 Antwort Letzte Antwort
              0
              • CodierknechtC Codierknecht

                @humidor
                https://www.howtoforge.de/anleitung/wie-man-laufende-prozesse-unter-linux-anzeigt/

                iobroker@iobroker:/opt/iobroker# top
                

                Da müsste sich dann nach Deiner Annahme ein Prozess mit massivem Speicherverbrauch finden lassen ...

                HumidorH Offline
                HumidorH Offline
                Humidor
                schrieb am zuletzt editiert von
                #10

                @codierknecht danke, dh wer da unter %Mem wächst, der ist ein Kandidat
                Bildschirmfoto 2022-11-07 um 13.40.09.png

                BG

                CodierknechtC 1 Antwort Letzte Antwort
                0
                • HumidorH Humidor

                  @codierknecht danke, dh wer da unter %Mem wächst, der ist ein Kandidat
                  Bildschirmfoto 2022-11-07 um 13.40.09.png

                  CodierknechtC Offline
                  CodierknechtC Offline
                  Codierknecht
                  Developer Most Active
                  schrieb am zuletzt editiert von
                  #11

                  @humidor
                  Ich glaube kaum, dass damit ein einzelner Prozess als Übeltäter auszumachen ist.
                  Die brauchen ja alle nicht wirklich übermäßig viel von dem beschränkt verfügbaren Speicher.
                  Rechne mal zusammen ... da bleibt nicht viel übrig.

                  So sieht das bei mir aus:

                    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                          
                    428 iobroker  20   0 1143060 194184  10500 S   5,0   2,4   2897:30 iobroker.js-con                                                  
                  26204 iobroker  20   0  952836  87472  10272 R   4,7   1,1   2630:18 io.lupusec.1                                                     
                  23996 iobroker  20   0   10,9g  58036  10392 S   1,7   0,7 688:48.62 io.synology.0                                                    
                    512 iobroker  20   0  794024  56916   9780 S   1,0   0,7 397:39.29 io.sql.0                                                         
                  10544 iobroker  20   0  690032  51988  12240 S   1,0   0,6 107:09.94 io.tr-064.0                                                      
                    470 iobroker  20   0 1042160 100412  10580 S   0,7   1,3 492:16.04 io.javascript.0                                                  
                  20017 iobroker  20   0  696652  28880  12280 S   0,7   0,4  86:54.05 io.mqtt.0                                                        
                  32356 iobroker  20   0  688316  49128  10404 S   0,7   0,6  89:13.86 io.hue.0                                                         
                    742 iobroker  20   0  669376  25020   8272 S   0,3   0,3 182:53.43 io.denon.0                                                       
                    804 iobroker  20   0  970812  63944  10452 S   0,3   0,8  49:58.56 io.web.0                                                         
                  31324 iobroker  20   0  955932  46816  14984 S   0,3   0,6   3:04.95 io.backitup.0                                                    
                      1 root      20   0    7292    276    276 S   0,0   0,0   0:00.05 iobroker_startu                                                  
                    497 iobroker  20   0  674128  36300   8760 S   0,0   0,5  22:37.28 io.scenes.0                                                      
                    569 iobroker  20   0  687240  45776   8328 S   0,0   0,6  32:30.00 io.hm-rega.0                                                     
                    702 iobroker  20   0  666092  37144   8580 S   0,0   0,5  32:37.74 io.fritzdect.0                                                   
                    789 iobroker  20   0  652328  30376   7968 S   0,0   0,4  20:23.24 io.discovery.0                                                   
                    876 iobroker  20   0  681208  36336   9272 S   0,0   0,5  66:10.17 io.lgtv.0                                                        
                   6996 iobroker  20   0  679736  40840  12128 S   0,0   0,5  18:37.62 io.device-watch                                                  
                   8549 iobroker  20   0 1022408 105700  14904 S   0,0   1,3  17:09.28 io.admin.1                                                       
                  16843 iobroker  20   0  671308  36264  11100 S   0,0   0,5  10:14.03 io.snmp.0                                                        
                  18582 root      20   0    7424   2276   1752 S   0,0   0,0   0:00.01 bash                                                             
                  19878 iobroker  20   0  954592  52120  14228 S   0,0   0,6  23:36.28 io.tapo.0                                                        
                  20056 iobroker  20   0  763180  59196  13144 S   0,0   0,7  12:07.57 io.yahka.0                                                       
                  20150 iobroker  20   0  693836  53480  12720 S   0,0   0,7 158:22.58 io.unifi.0                                                       
                  20951 iobroker  20   0  665796  49520  18884 S   0,0   0,6   0:01.77 io.trashschedul                                                  
                  21061 iobroker  20   0  962476  74528  13044 S   0,0   0,9   7:47.59 io.sourceanalyt                                                  
                  21157 iobroker  20   0  686920  46008  11120 S   0,0   0,6  26:06.42 io.hm-rpc.0                                                      
                  21498 root      20   0   10256   1924   1416 R   0,0   0,0   0:00.00 top                                                              
                  22130 iobroker  20   0  960560  65460  14420 S   0,0   0,8  45:01.08 io.meross.0                                                      
                  

                  Das sind insgesamt knapp 20% oder 1,6 GB.

                  "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                  Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                  HmIP|ZigBee|Tasmota|Unifi
                  Zabbix Certified Specialist
                  Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                  HumidorH HomoranH 2 Antworten Letzte Antwort
                  0
                  • CodierknechtC Codierknecht

                    @humidor
                    Ich glaube kaum, dass damit ein einzelner Prozess als Übeltäter auszumachen ist.
                    Die brauchen ja alle nicht wirklich übermäßig viel von dem beschränkt verfügbaren Speicher.
                    Rechne mal zusammen ... da bleibt nicht viel übrig.

                    So sieht das bei mir aus:

                      PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND                                                          
                      428 iobroker  20   0 1143060 194184  10500 S   5,0   2,4   2897:30 iobroker.js-con                                                  
                    26204 iobroker  20   0  952836  87472  10272 R   4,7   1,1   2630:18 io.lupusec.1                                                     
                    23996 iobroker  20   0   10,9g  58036  10392 S   1,7   0,7 688:48.62 io.synology.0                                                    
                      512 iobroker  20   0  794024  56916   9780 S   1,0   0,7 397:39.29 io.sql.0                                                         
                    10544 iobroker  20   0  690032  51988  12240 S   1,0   0,6 107:09.94 io.tr-064.0                                                      
                      470 iobroker  20   0 1042160 100412  10580 S   0,7   1,3 492:16.04 io.javascript.0                                                  
                    20017 iobroker  20   0  696652  28880  12280 S   0,7   0,4  86:54.05 io.mqtt.0                                                        
                    32356 iobroker  20   0  688316  49128  10404 S   0,7   0,6  89:13.86 io.hue.0                                                         
                      742 iobroker  20   0  669376  25020   8272 S   0,3   0,3 182:53.43 io.denon.0                                                       
                      804 iobroker  20   0  970812  63944  10452 S   0,3   0,8  49:58.56 io.web.0                                                         
                    31324 iobroker  20   0  955932  46816  14984 S   0,3   0,6   3:04.95 io.backitup.0                                                    
                        1 root      20   0    7292    276    276 S   0,0   0,0   0:00.05 iobroker_startu                                                  
                      497 iobroker  20   0  674128  36300   8760 S   0,0   0,5  22:37.28 io.scenes.0                                                      
                      569 iobroker  20   0  687240  45776   8328 S   0,0   0,6  32:30.00 io.hm-rega.0                                                     
                      702 iobroker  20   0  666092  37144   8580 S   0,0   0,5  32:37.74 io.fritzdect.0                                                   
                      789 iobroker  20   0  652328  30376   7968 S   0,0   0,4  20:23.24 io.discovery.0                                                   
                      876 iobroker  20   0  681208  36336   9272 S   0,0   0,5  66:10.17 io.lgtv.0                                                        
                     6996 iobroker  20   0  679736  40840  12128 S   0,0   0,5  18:37.62 io.device-watch                                                  
                     8549 iobroker  20   0 1022408 105700  14904 S   0,0   1,3  17:09.28 io.admin.1                                                       
                    16843 iobroker  20   0  671308  36264  11100 S   0,0   0,5  10:14.03 io.snmp.0                                                        
                    18582 root      20   0    7424   2276   1752 S   0,0   0,0   0:00.01 bash                                                             
                    19878 iobroker  20   0  954592  52120  14228 S   0,0   0,6  23:36.28 io.tapo.0                                                        
                    20056 iobroker  20   0  763180  59196  13144 S   0,0   0,7  12:07.57 io.yahka.0                                                       
                    20150 iobroker  20   0  693836  53480  12720 S   0,0   0,7 158:22.58 io.unifi.0                                                       
                    20951 iobroker  20   0  665796  49520  18884 S   0,0   0,6   0:01.77 io.trashschedul                                                  
                    21061 iobroker  20   0  962476  74528  13044 S   0,0   0,9   7:47.59 io.sourceanalyt                                                  
                    21157 iobroker  20   0  686920  46008  11120 S   0,0   0,6  26:06.42 io.hm-rpc.0                                                      
                    21498 root      20   0   10256   1924   1416 R   0,0   0,0   0:00.00 top                                                              
                    22130 iobroker  20   0  960560  65460  14420 S   0,0   0,8  45:01.08 io.meross.0                                                      
                    

                    Das sind insgesamt knapp 20% oder 1,6 GB.

                    HumidorH Offline
                    HumidorH Offline
                    Humidor
                    schrieb am zuletzt editiert von
                    #12

                    @codierknecht 1,6GB sind ja auch bei mir benutzt, 126MB frei
                    wenn man was macht, wie ein Blockly erstellen, dann gehts auf 0
                    wenn man ihn völlig in Ruhe lässt, scheint er durchzulaufen
                    dh wenn man etwas tut, verbraucht es Ram, ist ja auch klar, aber da ist dann ein Raspi4 mit 2GB schon an der Grenze, überhaupt sinnvoll eingesetzt zu werden
                    ev. sollte hier die Doku darauf hinweisen, wenn sie das nicht schon tut.

                    BG

                    Thomas BraunT CodierknechtC crunchipC 3 Antworten Letzte Antwort
                    0
                    • HumidorH Humidor

                      @codierknecht 1,6GB sind ja auch bei mir benutzt, 126MB frei
                      wenn man was macht, wie ein Blockly erstellen, dann gehts auf 0
                      wenn man ihn völlig in Ruhe lässt, scheint er durchzulaufen
                      dh wenn man etwas tut, verbraucht es Ram, ist ja auch klar, aber da ist dann ein Raspi4 mit 2GB schon an der Grenze, überhaupt sinnvoll eingesetzt zu werden
                      ev. sollte hier die Doku darauf hinweisen, wenn sie das nicht schon tut.

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

                      @humidor

                      free -ht --mega
                      

                      sagt?

                      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

                      HumidorH 1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @humidor

                        free -ht --mega
                        

                        sagt?

                        HumidorH Offline
                        HumidorH Offline
                        Humidor
                        schrieb am zuletzt editiert von
                        #14

                        @thomas-braun sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

                        free -ht --mega

                                       total        used        free      shared  buff/cache   available
                        Mem:            1.8G        1.6G        113M        0.0K        134M        169M
                        Swap:            99M         99M          0B
                        Total:          1.9G        1.7G        113M
                        

                        BG

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • HumidorH Humidor

                          @thomas-braun sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

                          free -ht --mega

                                         total        used        free      shared  buff/cache   available
                          Mem:            1.8G        1.6G        113M        0.0K        134M        169M
                          Swap:            99M         99M          0B
                          Total:          1.9G        1.7G        113M
                          
                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #15

                          @humidor

                          Das Ding läuft im Roten Bereich.

                          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

                          HumidorH 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @humidor

                            Das Ding läuft im Roten Bereich.

                            HumidorH Offline
                            HumidorH Offline
                            Humidor
                            schrieb am zuletzt editiert von
                            #16

                            @thomas-braun dh für 24 Prozesse sind 2GB zu wenig

                            BG

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • HumidorH Humidor

                              @thomas-braun dh für 24 Prozesse sind 2GB zu wenig

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

                              @humidor

                              Das hängt (auch) damit zusammen was das für Instanzen (du meinst nicht Prozesse, da laufen wesentlich mehr auf deiner Kiste) sind.

                              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

                              HumidorH 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @humidor

                                Das hängt (auch) damit zusammen was das für Instanzen (du meinst nicht Prozesse, da laufen wesentlich mehr auf deiner Kiste) sind.

                                HumidorH Offline
                                HumidorH Offline
                                Humidor
                                schrieb am zuletzt editiert von
                                #18

                                @thomas-braun richtig, Prozesse, ist aber nicht wirklich viel was ich mache, die grundlegende ioBroker Struktur benötigt ja auch schon ein paar Prozesse....

                                BG

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • HumidorH Humidor

                                  @thomas-braun richtig, Prozesse, ist aber nicht wirklich viel was ich mache, die grundlegende ioBroker Struktur benötigt ja auch schon ein paar Prozesse....

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

                                  @humidor

                                  ps -e | wc -l
                                  

                                  Da siehst du wieviele Prozesse laufen.

                                  Bzw. genauer:

                                  ps -e --no-headers | wc -l
                                  

                                  Aber grundsätzlich finde ich das 2GB RAM die unterste Grenze ist, wenn da ein 'Standard'-Iobroker laufen soll.

                                  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

                                  HumidorH 1 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @humidor

                                    ps -e | wc -l
                                    

                                    Da siehst du wieviele Prozesse laufen.

                                    Bzw. genauer:

                                    ps -e --no-headers | wc -l
                                    

                                    Aber grundsätzlich finde ich das 2GB RAM die unterste Grenze ist, wenn da ein 'Standard'-Iobroker laufen soll.

                                    HumidorH Offline
                                    HumidorH Offline
                                    Humidor
                                    schrieb am zuletzt editiert von
                                    #20

                                    @thomas-braun sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

                                    ps -e --no-headers | wc -l

                                    173 😬

                                    BG

                                    1 Antwort Letzte Antwort
                                    0
                                    • HumidorH Humidor

                                      @codierknecht 1,6GB sind ja auch bei mir benutzt, 126MB frei
                                      wenn man was macht, wie ein Blockly erstellen, dann gehts auf 0
                                      wenn man ihn völlig in Ruhe lässt, scheint er durchzulaufen
                                      dh wenn man etwas tut, verbraucht es Ram, ist ja auch klar, aber da ist dann ein Raspi4 mit 2GB schon an der Grenze, überhaupt sinnvoll eingesetzt zu werden
                                      ev. sollte hier die Doku darauf hinweisen, wenn sie das nicht schon tut.

                                      CodierknechtC Offline
                                      CodierknechtC Offline
                                      Codierknecht
                                      Developer Most Active
                                      schrieb am zuletzt editiert von
                                      #21

                                      @humidor sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

                                      aber da ist dann ein Raspi4 mit 2GB schon an der Grenze, überhaupt sinnvoll eingesetzt zu werden
                                      ev. sollte hier die Doku darauf hinweisen, wenn sie das nicht schon tut.

                                      Da ich das Ganze nicht auf 'nem Raspi laufen habe, habe ich mich damit noch nie befasst.
                                      Aber wenn man hier so ein bisschen kreuz und quer liest stellt man fest, dass unter 4 GB wohl niemand was am Start hat und in der Regel mindesten 8 GB empfohlen werden.

                                      "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                                      Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                                      HmIP|ZigBee|Tasmota|Unifi
                                      Zabbix Certified Specialist
                                      Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                                      HumidorH 1 Antwort Letzte Antwort
                                      0
                                      • CodierknechtC Codierknecht

                                        @humidor sagte in Raspi4 2GB / ioBroker startet jeden Tag neu ?:

                                        aber da ist dann ein Raspi4 mit 2GB schon an der Grenze, überhaupt sinnvoll eingesetzt zu werden
                                        ev. sollte hier die Doku darauf hinweisen, wenn sie das nicht schon tut.

                                        Da ich das Ganze nicht auf 'nem Raspi laufen habe, habe ich mich damit noch nie befasst.
                                        Aber wenn man hier so ein bisschen kreuz und quer liest stellt man fest, dass unter 4 GB wohl niemand was am Start hat und in der Regel mindesten 8 GB empfohlen werden.

                                        HumidorH Offline
                                        HumidorH Offline
                                        Humidor
                                        schrieb am zuletzt editiert von
                                        #22

                                        @codierknecht Ja ist OK, aber dann braucht man mit Rapi 2/3 gar nicht anfangen, wo iobroker ja auch laufen soll... egal, für einen Dauereinsatz dann mind. 4GB
                                        (wollte nur keinen neuen kaufen müssen)

                                        BG

                                        CodierknechtC 1 Antwort Letzte Antwort
                                        0
                                        • HumidorH Humidor

                                          @codierknecht Ja ist OK, aber dann braucht man mit Rapi 2/3 gar nicht anfangen, wo iobroker ja auch laufen soll... egal, für einen Dauereinsatz dann mind. 4GB
                                          (wollte nur keinen neuen kaufen müssen)

                                          CodierknechtC Offline
                                          CodierknechtC Offline
                                          Codierknecht
                                          Developer Most Active
                                          schrieb am zuletzt editiert von
                                          #23

                                          @humidor
                                          Darum wird wohl auch allenthalben von Beschaffungsproblemen berichtet.
                                          2GB Versionen des Raspi sind AFAIK noch relativ problemlos zu besorgen, aber ab 4 GB sieht's dann schon düster aus.

                                          Falls Du ein halbwegs potentes NAS (z.B. Synology, QNap) zur Verfügung hast, könnte ioB auch darauf als Container laufen.
                                          So hab' ich's bei mir eingerichtet. Das NAS läuft ja eh 24/7 - also soll es auch mal was tun für sein Geld 😁
                                          OK, ist bei mir keine "echte" Syno-Hardware, aber es gibt wohl genügend Anwender die damit zufrieden sind.
                                          Also nur, wenn Du eh eines rumfliegen hast und das Ding sich langweilen sollte ...

                                          Einen Raspi zu finden scheint nicht so einfach: https://rpilocator.com/

                                          "Any fool can write code that a computer can understand. Good programmers write code that humans can understand." (Martin Fowler, "Refactoring")

                                          Proxmox 9.1.1 LXC|8 GB|Core i7-6700
                                          HmIP|ZigBee|Tasmota|Unifi
                                          Zabbix Certified Specialist
                                          Konnte ich Dir helfen? Dann benutze bitte das Voting unten rechts im Beitrag

                                          HomoranH 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

                                          502

                                          Online

                                          32.9k

                                          Benutzer

                                          83.0k

                                          Themen

                                          1.3m

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

                                          • Du hast noch kein Konto? Registrieren

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