Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]
-
@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57
Was für ein Key?Ich meine, ich hätte mal beim Wechsel der SD Karte eine ähnliche Aufforderung bekommen. Kann sein, dass ich Blödsinn rede. Also Aufsetzen und Backitup und schon habe ich eine Sicherheit!!
-
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
ich hätte mal beim Wechsel der SD Karte eine ähnliche Aufforderung bekommen
in putty?
-
@homoran said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
ich hätte mal beim Wechsel der SD Karte eine ähnliche Aufforderung bekommen
in putty?
Ich glaube ja.
-
@searcher57 das ist die Meldung, dass unter der Ip jetzt nicht mehr der selbe Rechner zu erreichen ist wie bisher.
Wenn du selber nichts geändert hast sollst du gewarnt werden, dass sich da ggf. jemand fremdes versucht einzuklinken.Da du aber neu aufgesetzt hast, kannst du der Verbindung vertrauen
-
@homoran said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57 das ist die Meldung, dass unter der Ip jetzt nicht mehr der selbe Rechner zu erreichen ist wie bisher.
Wenn du selber nichts geändert hast sollst du gewarnt werden, dass sich da ggf. jemand fremdes versucht einzuklinken.Da du aber neu aufgesetzt hast, kannst du der Verbindung vertrauen
Ok schon wieder was gelernt! Ein guter Tag!!
So alter Mann muss in die Heia! Danke! -
@searcher57 said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Hallo!
Seit einigen Tagen stürzt mein ioBroker täglich ab. Ich habe dann auch keinen Zugang mehr über SSH auf den Raspi. Dann hilft nur noch ein Hardware-Reset (Ein- und Ausschalten)!
Die letzten Log-Einträge vor dem Crash heute:2023-05-14 16:17:13.274 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest" 2023-05-14 16:17:13.344 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext" 2023-05-14 16:17:13.408 - info: host.raspberrypi Some obsolete host states deleted. 2023-05-14 16:17:15.188 - error: admin.0 (666) admin.0 already running 2023-05-14 16:17:15.193 - warn: admin.0 (666) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 16:17:15.787 - error: host.raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 16:17:15.788 - info: host.raspberrypi Restart adapter system.adapter.admin.0 because enabled 2023-05-14 16:17:17.020 - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 826 2023-05-14 16:17:20.284 - error: javascript.0 (826) javascript.0 already running 2023-05-14 16:17:20.287 - warn: javascript.0 (826) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 16:17:20.878 - error: host.raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 16:17:20.879 - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled 2023-05-14 16:17:21.019 - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 838 2023-05-14 16:17:23.485 - error: telegram.0 (838) telegram.0 already running 2023-05-14 16:17:23.490 - warn: telegram.0 (838) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 16:17:24.070 - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 16:17:24.071 - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled 2023-05-14 16:17:25.256 - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 849 2023-05-14 16:17:25.327 - info: host.raspberrypi instance system.adapter.history.0 started with pid 856 2023-05-14 16:17:27.183 - error: history.0 (856) history.0 already running 2023-05-14 16:17:27.189 - warn: history.0 (856) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 16:17:27.793 - error: host.raspberrypi instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 16:17:27.794 - info: host.raspberrypi Restart adapter system.adapter.history.0 because enabled 2023-05-14 16:17:28.358 - info: telegram.0 (849) starting. Version 1.15.2 in /opt/iobroker/node_modules/iobroker.telegram, node: v18.16.0, js-controller: 4.0.24 2023-05-14 16:17:29.019 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 875 2023-05-14 16:17:30.692 - error: alexa2.0 (875) alexa2.0 already running 2023-05-14 16:17:30.697 - warn: alexa2.0 (875) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 16:17:31.271 - error: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 16:17:31.271 - info: host.raspberrypi Restart adapter system.adapter.alexa2.0 because enabled 2023-05-14 16:17:33.013 - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 886 2023-05-14 18:07:48.687 - error: hm-rega.0 (886) hm-rega.0 already running 2023-05-14 18:07:48.691 - warn: hm-rega.0 (886) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 18:07:49.268 - error: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 18:07:49.268 - info: host.raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled 2023-05-14 18:07:50.819 - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 897 2023-05-14 18:07:52.359 - error: hm-rpc.0 (897) hm-rpc.0 already running 2023-05-14 18:07:52.363 - warn: hm-rpc.0 (897) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 18:07:52.936 - error: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 18:07:52.937 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled 2023-05-14 18:07:54.810 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 908 2023-05-14 18:07:56.331 - error: hm-rpc.1 (908) hm-rpc.1 already running 2023-05-14 18:07:56.335 - warn: hm-rpc.1 (908) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 18:07:56.964 - error: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 18:07:56.965 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled 2023-05-14 18:07:58.826 - info: host.raspberrypi instance system.adapter.shelly.0 started with pid 923 2023-05-14 18:07:59.657 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 930 2023-05-14 18:08:00.997 - error: shelly.0 (923) shelly.0 already running 2023-05-14 18:08:01.002 - warn: shelly.0 (923) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2023-05-14 18:08:01.605 - error: host.raspberrypi instance system.adapter.shelly.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2023-05-14 18:08:01.606 - info: host.raspberrypi Restart adapter system.adapter.shelly.0 because enabled 2023-05-14 18:08:02.218 - info: admin.0 (930) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-14 18:08:02.275 - info: admin.0 (930) requesting all states 2023-05-14 18:08:02.276 - info: admin.0 (930) requesting all objectsHängt das eventuell mit meinem Doorbird Adapter, den ich im Beta-Respositorie installiert habe zusammen? Die Instanz habe ich gestern gestoppt, trotzdem war heute der Crash.
Meine Daten:
Plattform: linux
Betriebssystem: linux
Architektur: arm64
CPUs: 4
Geschwindigkeit: 1800 MHz
Modell: Cortex-A72
RAM: 1.8 GB
System-Betriebszeit: 00:35:46
Node.js: v18.16.0
time: 1684082577496
timeOffset: -120
Adapter-Anzahl: 473
NPM: v9.5.1
Datenträgergröße: 29.0 GB
Freier Festplattenspeicher: 23.2 GB
Betriebszeit: 02:25:50
Aktive Instanzen: 17
Pfad: /opt/iobroker/
aktiv:Ich bitte um Hilfe an einen Laien, der wenig Linux-Erfahrung hat und kaum englische Hinweise versteht.
Vielen Dank im voraus
Rainer -
-
@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
[erledigt]
Inwiefern?
Das wollte ich gerade schreiben!
Die neue SD Karte und ein neues Aufsetzen incl. Restore hat zum Erfolg geführt! Bitte teil mir nochmal mit, wie ich das ordnungsgemäß abschliesse.
Danke nochmal! -
Den ersten Eintrag entsprechend bearbeiten.
BTW: Ich bin gerade dabei bei mir eine neue USV einzurichten. Um sowas zu vermeiden.
-
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Bitte teil mir nochmal mit, wie ich das ordnungsgemäß abschliesse
du hast deinen Beitrag zitiert anstatt bearbeitet
du musst den ersten Beitrag bearbeiten und da in der Überschrift das [Gelöst] setzen -
@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Den ersten Eintrag entsprechend bearbeiten.
BTW: Ich bin gerade dabei bei mir eine neue USV einzurichten. Um sowas zu vermeiden.
Ich habe mich auch schon informiert. Bin jetzt erst mal für 5 Wochen im Urlaub, danach gehe ich die Baustelle an.,
-
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Bitte teil mir nochmal mit, wie ich das ordnungsgemäß abschliesse.
Den Titel ändern mit [gelöst]
Im Startbeitrag gehen und bei den 3 Punkten kannst du es ändern
.
. -
@crunchip said in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Bitte teil mir nochmal mit, wie ich das ordnungsgemäß abschliesse
du hast deinen Beitrag zitiert anstatt bearbeitet
du musst den ersten Beitrag bearbeiten und da in der Überschrift das [Gelöst] setzenOk, danke für den Hinweis!
-
@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
[erledigt]
Inwiefern?
Hallo Thomas und Helfer,
zu früh gefreut! Ich habe das Ganze nochmal über Tage hinweg beobachtet. Leider stürzt der Raspi auch mit der neu aufgesetzten SD Karte ab. Was mir auffällt, dass das meistens kurz nach 14 Uhr, während ich im ioBroker arbeite, passiert. Bitte fragt mich nicht, was das mit der Tageszeit zu tun hat. Beide LED's leuchten durch. Kein Kontakt über SSH mehr möglich. Ich hänge nochmal ein Protokoll an, aber ich denke das hilft Euch wenig, weil es nach dem Hardware-Reset neu gestartet ist. Wäre schön, wenn Ihr mir nochmal helft diesen Fehler heraus zu finden.host.raspberrypi 2023-05-24 14:19:44.918 error instance system.adapter.text2command.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) alexa2.0 2023-05-24 14:19:44.845 info Initialize all Device states ... hm-rega.0 2023-05-24 14:19:44.792 info renamed hm-rpc.0.00115BE9956D53.4.SECTION_STATUS to "Rollo Aktor Markise:4.SECTION_STATUS" hm-rega.0 2023-05-24 14:19:44.776 info renamed hm-rpc.0.00115BE9956D53.4.SECTION to "Rollo Aktor Markise:4.SECTION" hm-rega.0 2023-05-24 14:19:44.758 info renamed hm-rpc.0.00115BE9956D53.4.PROCESS to "Rollo Aktor Markise:4.PROCESS" hm-rega.0 2023-05-24 14:19:44.739 info renamed hm-rpc.0.00115BE9956D53.4.LEVEL_STATUS to "Rollo Aktor Markise:4.LEVEL_STATUS" hm-rega.0 2023-05-24 14:19:44.699 info renamed hm-rpc.0.00115BE9956D53.4.LEVEL to "Rollo Aktor Markise:4.LEVEL" hm-rega.0 2023-05-24 14:19:44.682 info renamed hm-rpc.0.00115BE9956D53.4.ACTIVITY_STATE to "Rollo Aktor Markise:4.ACTIVITY_STATE" hm-rega.0 2023-05-24 14:19:44.673 info renamed hm-rpc.0.00115BE9956D53.4 to "Rollo Aktor Markise:4" hm-rega.0 2023-05-24 14:19:44.665 info renamed hm-rpc.0.00115BE9956D53.3.SECTION_STATUS to "Rollo Aktor Markise:3.SECTION_STATUS" hm-rega.0 2023-05-24 14:19:44.655 info renamed hm-rpc.0.00115BE9956D53.3.SECTION to "Rollo Aktor Markise:3.SECTION" hm-rega.0 2023-05-24 14:19:44.645 info renamed hm-rpc.0.00115BE9956D53.3.PROCESS to "Rollo Aktor Markise:3.PROCESS" hm-rega.0 2023-05-24 14:19:44.630 info renamed hm-rpc.0.00115BE9956D53.3.LEVEL_STATUS to "Rollo Aktor Markise:3.LEVEL_STATUS" hm-rega.0 2023-05-24 14:19:44.615 info renamed hm-rpc.0.00115BE9956D53.3.LEVEL to "Rollo Aktor Markise:3.LEVEL" hm-rega.0 2023-05-24 14:19:44.598 info renamed hm-rpc.0.00115BE9956D53.3.ACTIVITY_STATE to "Rollo Aktor Markise:3.ACTIVITY_STATE" hm-rega.0 2023-05-24 14:19:44.552 info renamed hm-rpc.0.00115BE9956D53.3 to "Rollo Aktor Markise:3" hm-rega.0 2023-05-24 14:19:44.539 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_SHORT to "Rollo AktorMarkise:1.PRESS_SHORT" hm-rega.0 2023-05-24 14:19:44.524 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG_START to "Rollo AktorMarkise:1.PRESS_LONG_START" hm-rega.0 2023-05-24 14:19:44.508 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG_RELEASE to "Rollo AktorMarkise:1.PRESS_LONG_RELEASE" hm-rega.0 2023-05-24 14:19:44.490 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG to "Rollo AktorMarkise:1.PRESS_LONG" hm-rega.0 2023-05-24 14:19:44.471 info renamed hm-rpc.0.00115BE9956D53.1 to "Rollo AktorMarkise:1" hm-rega.0 2023-05-24 14:19:44.442 info renamed hm-rpc.0.00115BE9956D53.0.UPDATE_PENDING_ALARM to "Rollo Aktor Markise:0.UPDATE_PENDING_ALARM" hm-rega.0 2023-05-24 14:19:44.423 info renamed hm-rpc.0.00115BE9956D53.0.UPDATE_PENDING to "Rollo Aktor Markise:0.UPDATE_PENDING" hm-rega.0 2023-05-24 14:19:44.415 info renamed hm-rpc.0.00115BE9956D53.0.UNREACH_ALARM to "Rollo Aktor Markise:0.UNREACH_ALARM" hm-rega.0 2023-05-24 14:19:44.402 info renamed hm-rpc.0.00115BE9956D53.0.UNREACH to "Rollo Aktor Markise:0.UNREACH" hm-rega.0 2023-05-24 14:19:44.389 info renamed hm-rpc.0.00115BE9956D53.0.RSSI_PEER to "Rollo Aktor Markise:0.RSSI_PEER" hm-rega.0 2023-05-24 14:19:44.381 info renamed hm-rpc.0.00115BE9956D53.0.RSSI_DEVICE to "Rollo Aktor Markise:0.RSSI_DEVICE" hm-rega.0 2023-05-24 14:19:44.358 info renamed hm-rpc.0.00115BE9956D53.0.OPERATING_VOLTAGE_STATUS to "Rollo Aktor Markise:0.OPERATING_VOLTAGE_STATUS" hm-rega.0 2023-05-24 14:19:44.339 info renamed hm-rpc.0.00115BE9956D53.0.OPERATING_VOLTAGE to "Rollo Aktor Markise:0.OPERATING_VOLTAGE" hm-rega.0 2023-05-24 14:19:44.325 info renamed hm-rpc.0.00115BE9956D53.0.INSTALL_TEST to "Rollo Aktor Markise:0.INSTALL_TEST" hm-rega.0 2023-05-24 14:19:44.312 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_OVERHEAT_ALARM to "Rollo Aktor Markise:0.ERROR_OVERHEAT_ALARM" hm-rega.0 2023-05-24 14:19:44.297 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_OVERHEAT to "Rollo Aktor Markise:0.ERROR_OVERHEAT" hm-rega.0 2023-05-24 14:19:44.282 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_CODE to "Rollo Aktor Markise:0.ERROR_CODE" hm-rega.0 2023-05-24 14:19:44.260 info renamed hm-rpc.0.00115BE9956D53.0.DUTY_CYCLE to "Rollo Aktor Markise:0.DUTY_CYCLE" text2command.0 2023-05-24 14:19:44.242 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason text2command.0 2023-05-24 14:19:44.234 error text2command.0 already running hm-rega.0 2023-05-24 14:19:44.203 info renamed hm-rpc.0.00115BE9956D53.0.CONFIG_PENDING_ALARM to "Rollo Aktor Markise:0.CONFIG_PENDING_ALARM" hm-rega.0 2023-05-24 14:19:44.185 info renamed hm-rpc.0.00115BE9956D53.0.CONFIG_PENDING to "Rollo Aktor Markise:0.CONFIG_PENDING" hm-rega.0 2023-05-24 14:19:44.171 info renamed hm-rpc.0.00115BE9956D53.0.ACTUAL_TEMPERATURE_STATUS to "Rollo Aktor Markise:0.ACTUAL_TEMPERATURE_STATUS" hm-rega.0 2023-05-24 14:19:44.156 info renamed hm-rpc.0.00115BE9956D53.0.ACTUAL_TEMPERATURE to "Rollo Aktor Markise:0.ACTUAL_TEMPERATURE" hm-rega.0 2023-05-24 14:19:44.091 info renamed hm-rpc.0.00115BE9956D53.0 to "Rollo Aktor Markise:0" hm-rega.0 2023-05-24 14:19:44.066 info renamed hm-rpc.0.00115BE9956D53 to "Rollo Aktor Markise" hm-rpc.1 2023-05-24 14:19:43.029 info Connected hm-rpc.1 2023-05-24 14:19:42.967 info xmlrpc -> 81 devices hm-rpc.1 2023-05-24 14:19:42.879 info xmlrpc <- listDevices ["raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.848 info xmlrpc <- system.listMethods ["raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.754 info xmlrpc client is trying to connect to 192.168.178.27:2001/ with ["http://192.168.178.38:2001","raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.752 info xmlrpc server is trying to listen on 192.168.178.38:2001 hm-rpc.1 2023-05-24 14:19:42.338 info starting. Version 1.15.16 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:42.102 info instance system.adapter.shelly.0 started with pid 1199 host.raspberrypi 2023-05-24 14:19:41.621 info Restart adapter system.adapter.tankerkoenig.0 because enabled host.raspberrypi 2023-05-24 14:19:41.620 error instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) alexa2.0 2023-05-24 14:19:41.475 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2023-05-24 14:19:41.212 info starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:40.971 info instance system.adapter.text2command.0 started with pid 1188 tankerkoenig.0 2023-05-24 14:19:40.906 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason tankerkoenig.0 2023-05-24 14:19:40.898 error tankerkoenig.0 already running hm-rpc.0 2023-05-24 14:19:38.135 info Connected hm-rpc.0 2023-05-24 14:19:37.979 info xmlrpc client is trying to connect to 192.168.178.27:2010/ with ["http://192.168.178.27:2010","raspberrypi:hm-rpc.0:17bdd2f8a472b64d206b06fac798b358"] hm-rpc.0 2023-05-24 14:19:37.966 info xmlrpc server is trying to listen on 0.0.0.0:2010 host.raspberrypi 2023-05-24 14:19:37.318 info instance system.adapter.hm-rpc.1 started with pid 1166 hm-rpc.0 2023-05-24 14:19:37.240 info starting. Version 1.15.16 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:36.966 info instance system.adapter.tankerkoenig.0 started with pid 1158 host.raspberrypi 2023-05-24 14:19:36.331 info Restart adapter system.adapter.simple-api.0 because enabled host.raspberrypi 2023-05-24 14:19:36.330 error instance system.adapter.simple-api.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.raspberrypi 2023-05-24 14:19:35.979 info instance system.adapter.alexa2.0 started with pid 1151 simple-api.0 2023-05-24 14:19:35.669 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason simple-api.0 2023-05-24 14:19:35.662 error simple-api.0 already running hm-rega.0 2023-05-24 14:19:34.326 info time difference local-ccu 0s hm-rega.0 2023-05-24 14:19:33.953 info ReGaHSS 192.168.178.27 up hm-rega.0 2023-05-24 14:19:33.858 info subscribe hm-rpc.1.BidCoS-RF.50.PRESS_SHORT host.raspberrypi 2023-05-24 14:19:33.613 info instance system.adapter.alexa2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) hm-rega.0 2023-05-24 14:19:33.336 info starting. Version 3.0.46 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:33.263 info instance system.adapter.hm-rpc.0 started with pid 1132 host.raspberrypi 2023-05-24 14:19:32.953 info instance system.adapter.simple-api.0 started with pid 1125 alexa2.0 2023-05-24 14:19:32.890 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason alexa2.0 2023-05-24 14:19:32.884 info terminating host.raspberrypi 2023-05-24 14:19:32.884 info stopInstance system.adapter.alexa2.0 send kill signal alexa2.0 2023-05-24 14:19:32.882 info Got terminate signal TERMINATE_YOURSELF host.raspberrypi 2023-05-24 14:19:32.873 info stopInstance system.adapter.alexa2.0 (force=false, process=true) -
@searcher57 said in Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]:
@thomas-braun said in Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
[erledigt]
Inwiefern?
Hallo Thomas und Helfer,
zu früh gefreut! Ich habe das Ganze nochmal über Tage hinweg beobachtet. Leider stürzt der Raspi auch mit der neu aufgesetzten SD Karte ab. Was mir auffällt, dass das meistens kurz nach 14 Uhr, während ich im ioBroker arbeite, passiert. Bitte fragt mich nicht, was das mit der Tageszeit zu tun hat. Beide LED's leuchten durch. Kein Kontakt über SSH mehr möglich. Ich hänge nochmal ein Protokoll an, aber ich denke das hilft Euch wenig, weil es nach dem Hardware-Reset neu gestartet ist. Wäre schön, wenn Ihr mir nochmal helft diesen Fehler heraus zu finden.host.raspberrypi 2023-05-24 14:19:44.918 error instance system.adapter.text2command.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) alexa2.0 2023-05-24 14:19:44.845 info Initialize all Device states ... hm-rega.0 2023-05-24 14:19:44.792 info renamed hm-rpc.0.00115BE9956D53.4.SECTION_STATUS to "Rollo Aktor Markise:4.SECTION_STATUS" hm-rega.0 2023-05-24 14:19:44.776 info renamed hm-rpc.0.00115BE9956D53.4.SECTION to "Rollo Aktor Markise:4.SECTION" hm-rega.0 2023-05-24 14:19:44.758 info renamed hm-rpc.0.00115BE9956D53.4.PROCESS to "Rollo Aktor Markise:4.PROCESS" hm-rega.0 2023-05-24 14:19:44.739 info renamed hm-rpc.0.00115BE9956D53.4.LEVEL_STATUS to "Rollo Aktor Markise:4.LEVEL_STATUS" hm-rega.0 2023-05-24 14:19:44.699 info renamed hm-rpc.0.00115BE9956D53.4.LEVEL to "Rollo Aktor Markise:4.LEVEL" hm-rega.0 2023-05-24 14:19:44.682 info renamed hm-rpc.0.00115BE9956D53.4.ACTIVITY_STATE to "Rollo Aktor Markise:4.ACTIVITY_STATE" hm-rega.0 2023-05-24 14:19:44.673 info renamed hm-rpc.0.00115BE9956D53.4 to "Rollo Aktor Markise:4" hm-rega.0 2023-05-24 14:19:44.665 info renamed hm-rpc.0.00115BE9956D53.3.SECTION_STATUS to "Rollo Aktor Markise:3.SECTION_STATUS" hm-rega.0 2023-05-24 14:19:44.655 info renamed hm-rpc.0.00115BE9956D53.3.SECTION to "Rollo Aktor Markise:3.SECTION" hm-rega.0 2023-05-24 14:19:44.645 info renamed hm-rpc.0.00115BE9956D53.3.PROCESS to "Rollo Aktor Markise:3.PROCESS" hm-rega.0 2023-05-24 14:19:44.630 info renamed hm-rpc.0.00115BE9956D53.3.LEVEL_STATUS to "Rollo Aktor Markise:3.LEVEL_STATUS" hm-rega.0 2023-05-24 14:19:44.615 info renamed hm-rpc.0.00115BE9956D53.3.LEVEL to "Rollo Aktor Markise:3.LEVEL" hm-rega.0 2023-05-24 14:19:44.598 info renamed hm-rpc.0.00115BE9956D53.3.ACTIVITY_STATE to "Rollo Aktor Markise:3.ACTIVITY_STATE" hm-rega.0 2023-05-24 14:19:44.552 info renamed hm-rpc.0.00115BE9956D53.3 to "Rollo Aktor Markise:3" hm-rega.0 2023-05-24 14:19:44.539 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_SHORT to "Rollo AktorMarkise:1.PRESS_SHORT" hm-rega.0 2023-05-24 14:19:44.524 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG_START to "Rollo AktorMarkise:1.PRESS_LONG_START" hm-rega.0 2023-05-24 14:19:44.508 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG_RELEASE to "Rollo AktorMarkise:1.PRESS_LONG_RELEASE" hm-rega.0 2023-05-24 14:19:44.490 info renamed hm-rpc.0.00115BE9956D53.1.PRESS_LONG to "Rollo AktorMarkise:1.PRESS_LONG" hm-rega.0 2023-05-24 14:19:44.471 info renamed hm-rpc.0.00115BE9956D53.1 to "Rollo AktorMarkise:1" hm-rega.0 2023-05-24 14:19:44.442 info renamed hm-rpc.0.00115BE9956D53.0.UPDATE_PENDING_ALARM to "Rollo Aktor Markise:0.UPDATE_PENDING_ALARM" hm-rega.0 2023-05-24 14:19:44.423 info renamed hm-rpc.0.00115BE9956D53.0.UPDATE_PENDING to "Rollo Aktor Markise:0.UPDATE_PENDING" hm-rega.0 2023-05-24 14:19:44.415 info renamed hm-rpc.0.00115BE9956D53.0.UNREACH_ALARM to "Rollo Aktor Markise:0.UNREACH_ALARM" hm-rega.0 2023-05-24 14:19:44.402 info renamed hm-rpc.0.00115BE9956D53.0.UNREACH to "Rollo Aktor Markise:0.UNREACH" hm-rega.0 2023-05-24 14:19:44.389 info renamed hm-rpc.0.00115BE9956D53.0.RSSI_PEER to "Rollo Aktor Markise:0.RSSI_PEER" hm-rega.0 2023-05-24 14:19:44.381 info renamed hm-rpc.0.00115BE9956D53.0.RSSI_DEVICE to "Rollo Aktor Markise:0.RSSI_DEVICE" hm-rega.0 2023-05-24 14:19:44.358 info renamed hm-rpc.0.00115BE9956D53.0.OPERATING_VOLTAGE_STATUS to "Rollo Aktor Markise:0.OPERATING_VOLTAGE_STATUS" hm-rega.0 2023-05-24 14:19:44.339 info renamed hm-rpc.0.00115BE9956D53.0.OPERATING_VOLTAGE to "Rollo Aktor Markise:0.OPERATING_VOLTAGE" hm-rega.0 2023-05-24 14:19:44.325 info renamed hm-rpc.0.00115BE9956D53.0.INSTALL_TEST to "Rollo Aktor Markise:0.INSTALL_TEST" hm-rega.0 2023-05-24 14:19:44.312 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_OVERHEAT_ALARM to "Rollo Aktor Markise:0.ERROR_OVERHEAT_ALARM" hm-rega.0 2023-05-24 14:19:44.297 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_OVERHEAT to "Rollo Aktor Markise:0.ERROR_OVERHEAT" hm-rega.0 2023-05-24 14:19:44.282 info renamed hm-rpc.0.00115BE9956D53.0.ERROR_CODE to "Rollo Aktor Markise:0.ERROR_CODE" hm-rega.0 2023-05-24 14:19:44.260 info renamed hm-rpc.0.00115BE9956D53.0.DUTY_CYCLE to "Rollo Aktor Markise:0.DUTY_CYCLE" text2command.0 2023-05-24 14:19:44.242 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason text2command.0 2023-05-24 14:19:44.234 error text2command.0 already running hm-rega.0 2023-05-24 14:19:44.203 info renamed hm-rpc.0.00115BE9956D53.0.CONFIG_PENDING_ALARM to "Rollo Aktor Markise:0.CONFIG_PENDING_ALARM" hm-rega.0 2023-05-24 14:19:44.185 info renamed hm-rpc.0.00115BE9956D53.0.CONFIG_PENDING to "Rollo Aktor Markise:0.CONFIG_PENDING" hm-rega.0 2023-05-24 14:19:44.171 info renamed hm-rpc.0.00115BE9956D53.0.ACTUAL_TEMPERATURE_STATUS to "Rollo Aktor Markise:0.ACTUAL_TEMPERATURE_STATUS" hm-rega.0 2023-05-24 14:19:44.156 info renamed hm-rpc.0.00115BE9956D53.0.ACTUAL_TEMPERATURE to "Rollo Aktor Markise:0.ACTUAL_TEMPERATURE" hm-rega.0 2023-05-24 14:19:44.091 info renamed hm-rpc.0.00115BE9956D53.0 to "Rollo Aktor Markise:0" hm-rega.0 2023-05-24 14:19:44.066 info renamed hm-rpc.0.00115BE9956D53 to "Rollo Aktor Markise" hm-rpc.1 2023-05-24 14:19:43.029 info Connected hm-rpc.1 2023-05-24 14:19:42.967 info xmlrpc -> 81 devices hm-rpc.1 2023-05-24 14:19:42.879 info xmlrpc <- listDevices ["raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.848 info xmlrpc <- system.listMethods ["raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.754 info xmlrpc client is trying to connect to 192.168.178.27:2001/ with ["http://192.168.178.38:2001","raspberrypi:hm-rpc.1:4c7900ff95869fdf13a684fb18ec40d1"] hm-rpc.1 2023-05-24 14:19:42.752 info xmlrpc server is trying to listen on 192.168.178.38:2001 hm-rpc.1 2023-05-24 14:19:42.338 info starting. Version 1.15.16 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:42.102 info instance system.adapter.shelly.0 started with pid 1199 host.raspberrypi 2023-05-24 14:19:41.621 info Restart adapter system.adapter.tankerkoenig.0 because enabled host.raspberrypi 2023-05-24 14:19:41.620 error instance system.adapter.tankerkoenig.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) alexa2.0 2023-05-24 14:19:41.475 info Starting Alexa2 adapter ... it can take several minutes to initialize all data. Please be patient! A done message is logged. alexa2.0 2023-05-24 14:19:41.212 info starting. Version 3.23.2 in /opt/iobroker/node_modules/iobroker.alexa2, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:40.971 info instance system.adapter.text2command.0 started with pid 1188 tankerkoenig.0 2023-05-24 14:19:40.906 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason tankerkoenig.0 2023-05-24 14:19:40.898 error tankerkoenig.0 already running hm-rpc.0 2023-05-24 14:19:38.135 info Connected hm-rpc.0 2023-05-24 14:19:37.979 info xmlrpc client is trying to connect to 192.168.178.27:2010/ with ["http://192.168.178.27:2010","raspberrypi:hm-rpc.0:17bdd2f8a472b64d206b06fac798b358"] hm-rpc.0 2023-05-24 14:19:37.966 info xmlrpc server is trying to listen on 0.0.0.0:2010 host.raspberrypi 2023-05-24 14:19:37.318 info instance system.adapter.hm-rpc.1 started with pid 1166 hm-rpc.0 2023-05-24 14:19:37.240 info starting. Version 1.15.16 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v18.16.0, js-controller: 4.0.24 host.raspberrypi 2023-05-24 14:19:36.966 info instance system.adapter.tankerkoenig.0 started with pid 1158 host.raspberrypi 2023-05-24 14:19:36.331 info Restart adapter system.adapter.simple-api.0 because enabled host.raspberrypi 2023-05-24 14:19:36.330 error instance system.adapter.simple-api.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) host.raspberrypi 2023-05-24 14:19:35.979 info instance system.adapter.alexa2.0 started with pid 1151 simple-api.0 2023-05-24 14:19:35.669 warn Terminated (ADAPTER_ALREADY_RUNNING): Without reason simple-api.0 2023-05-24 14:19:35.662 error simple-api.0 already running hm-rega.0 2023-05-24 14:19:34.326 info time difference local-ccu 0s hm-rega.0 2023-05-24 14:19:33.953 info ReGaHSS 192.168.178.27 up hm-rega.0 2023-05-24 14:19:33.858 info subscribe hm-rpc.1.BidCoS-RF.50.PRESS_SHORT host.raspberrypiUnd hier nochmal die Ausgabe von iob diag:
Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.4 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Systemuptime and Load: 15:14:57 up 56 min, 1 user, load average: 0.65, 0.49, 0.34 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=49.6'C volt=0.9360V *** Time and Time Zones *** Local time: Wed 2023-05-24 15:14:58 CEST Universal time: Wed 2023-05-24 13:14:58 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev gp io i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 1.8G 1.5G 68M 0.0K 298M 299M Swap: 99M 9.0M 90M Total: 1.9G 1.5G 159M 1849 M total memory 1481 M used memory 1516 M active memory 145 M inactive memory 69 M free memory 5 M buffer memory 292 M swap cache 99 M total swap 9 M used swap 90 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 3.7G 25G 14% / devtmpfs devtmpfs 667M 0 667M 0% /dev tmpfs tmpfs 925M 0 925M 0% /dev/shm tmpfs tmpfs 370M 1.1M 369M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot /dev/sda1 exfat 29G 91M 29G 1% /mnt/usb0 tmpfs tmpfs 185M 0 185M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed May 24 14:18:19 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.ena ble_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:15:C8:D1 vc_mem. mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty 1 root=PARTUUID=b5d4b387-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed May 24 14:18:20 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on reado nly filesystem [Wed May 24 14:18:20 2023] EXT4-fs (mmcblk0p2): write access will be enabled dur ing recovery [Wed May 24 14:18:21 2023] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Wed May 24 14:18:21 2023] EXT4-fs (mmcblk0p2): 7 orphan inodes deleted [Wed May 24 14:18:21 2023] EXT4-fs (mmcblk0p2): recovery complete [Wed May 24 14:18:21 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed May 24 14:18:21 2023] VFS: Mounted root (ext4 filesystem) readonly on devic e 179:2. [Wed May 24 14:18:23 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437 ,iocharset=ascii,shortname=mixed,errors=remount-ro `-/mnt/usb0 /dev/sda1 exfat rw,nosuid,nodev,noexec,relatime,fmask=0000,dma sk=0000,allow_utime=0022,iocharset=utf8,errors=remount-ro Files in neuralgic directories: /var: 612M /var/ 179M /var/cache 177M /var/log 174M /var/cache/apt 161M /var/log/journal/330ce8f5ef974364b1563dcde1ee3ca3 Archived and active journals take up 160.0M in the file system. /opt/iobroker/backups: 43M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 324M /opt/iobroker/iobroker-data/ 264M /opt/iobroker/iobroker-data/files 51M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/telegram.admin 42M /opt/iobroker/iobroker-data/files/devices.admin The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.10538062. js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.904d455f.js.m ap 18M /opt/iobroker/iobroker-data/objects.jsonl 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors -node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modu les_io-1d9f06.44fe4a3f.chunk.js.map 9.7M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.bbfe b1bf.js.map *** NodeJS-Installation *** /usr/bin/nodejs v18.16.0 /usr/bin/node v18.16.0 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.0-deb-1nodesource1 Candidate: 18.16.0-deb-1nodesource1 Version table: *** 18.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages 12.22.12~dfsg-1~deb11u3 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 6.1.4 Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled system.adapter.alias-manager.0 : alias-manager : raspberrypi - disabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled + system.adapter.broadlink2.0 : broadlink2 : raspberrypi - enabled system.adapter.devices.0 : devices : raspberrypi - enabled + system.adapter.discovery.0 : discovery : raspberrypi - enabled + system.adapter.echarts.0 : echarts : raspberrypi - enabled + system.adapter.hm-rega.0 : hm-rega : raspberrypi - enabled + system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yr.0 : yr : raspberrypi - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : raspberrypi - enabled, port: 8086 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : raspberrypi - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alexa2" : 3.23.2 , installed 3.23.2 Adapter "alias-manager": 1.2.4 , installed 1.2.4 Adapter "backitup" : 2.6.19 , installed 2.6.19 Adapter "broadlink2" : 2.1.5 , installed 2.1.5 Adapter "devices" : 1.1.2 , installed 1.1.2 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "hm-rega" : 3.0.46 , installed 3.0.46 Adapter "hm-rpc" : 1.15.16 , installed 1.15.16 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Adapter "iot" : 1.14.2 , installed 1.14.2 Adapter "javascript" : 6.1.4 , installed 6.1.4 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "sbfspot" : 4.1.4 , installed 4.1.4 Adapter "shelly" : 6.3.1 , installed 6.3.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 6.3.1 Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7 Adapter "telegram" : 1.15.2 , installed 1.15.2 Adapter "text2command" : 2.3.0 , installed 2.3.0 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "web" : 4.3.0 , installed 5.3.1 Adapter "ws" : 1.3.0 , installed 2.3.1 Adapter "yr" : 5.3.0 , installed 5.3.0 Objects and States Please stand by - This may take a while Objects: 8972 States: 7462 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 12141 535/sshd: /usr/sbin tcp 0 0 192.168.178.38:2001 0.0.0.0:* LISTEN 1001 16784 1166/io.hm-rpc.1 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 12804 587/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 14571 587/iobroker.js-con tcp 0 0 0.0.0.0:2010 0.0.0.0:* LISTEN 1001 16736 1132/io.hm-rpc.0 tcp6 0 0 :::22 :::* LISTEN 0 12143 535/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 15553 978/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 17643 1375/io.web.0 tcp6 0 0 :::8087 :::* LISTEN 1001 15894 1326/io.simple-api. tcp6 0 0 :::8086 :::* LISTEN 999 14552 393/influxd udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 16833 1199/io.shelly.0 udp 0 0 0.0.0.0:39487 0.0.0.0:* 108 3726 337/avahi-daemon: r udp 0 0 0.0.0.0:15001 0.0.0.0:* 1001 15858 1292/io.broadlink2. udp 0 0 0.0.0.0:34575 0.0.0.0:* 1001 16980 1292/io.broadlink2. udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12744 758/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 3724 337/avahi-daemon: r udp6 0 0 :::546 :::* 0 12755 758/dhcpcd udp6 0 0 :::50218 :::* 108 3727 337/avahi-daemon: r udp6 0 0 :::5353 :::* 108 3725 337/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-05-24 14:20:31.238 - info: echarts.0 (1386) starting. Version 1.0.12 in /opt/iobroker/node_modules/iobroker.echarts, node: v18.16.0, js-controller: 4.0.24 2023-05-24 14:20:32.167 - info: alexa2.0 (1151) No smart home devices to query 2023-05-24 14:20:34.186 - info: alexa2.0 (1151) Subscribing to states... 2023-05-24 14:20:35.724 - info: alexa2.0 (1151) Alexa-Push-Connection (macDms = true) established. Disable Polling 2023-05-24 14:20:36.026 - info: alexa2.0 (1151) Initialization Done ... 2023-05-24 14:20:36.604 - info: tankerkoenig.0 (1341) Start first request 2023-05-24 14:27:59.714 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:30:00.052 - info: javascript.0 (1012) script.js.downloads.Shelly-Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 5 | Reboots korrigiert: 0 | Unveränderte Werte: 7 2023-05-24 14:31:45.286 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 admin 2023-05-24 14:31:45.737 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:31:48.194 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 admin 2023-05-24 14:35:00.071 - info: host.raspberrypi instance system.adapter.yr.0 started with pid 1488 2023-05-24 14:35:22.415 - info: host.raspberrypi instance system.adapter.yr.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-24 14:45:00.050 - info: javascript.0 (1012) script.js.downloads.Shelly-Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 5 | Reboots korrigiert: 0 | Unveränderte Werte: 7 2023-05-24 14:51:38.229 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:51:45.079 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:51:47.355 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:51:49.031 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 echarts-show 2023-05-24 14:51:57.035 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:53:04.255 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 echarts-show 2023-05-24 14:53:04.258 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 echarts 2023-05-24 14:53:06.482 - info: admin.0 (978) ==> Connected system.user.admin from ::ffff:192.168.178.30 2023-05-24 14:53:12.980 - info: admin.0 (978) <== Disconnect system.user.admin from ::ffff:192.168.178.30 devices 2023-05-24 15:00:00.031 - info: javascript.0 (1012) script.js.downloads.Shelly-Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 5 | Reboots korrigiert: 0 | Unveränderte Werte: 7 2023-05-24 15:15:00.053 - info: javascript.0 (1012) script.js.downloads.Shelly-Verbrauch: Shelly Verbrauch: Verbrauchswerte aktualisiert: 5 | Reboots korrigiert: 0 | Unveränderte Werte: 7 -
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Was mir auffällt, dass das meistens kurz nach 14 Uhr, während ich im ioBroker arbeite, passiert.
Naja, in dem Moment wo du den iobroker aufrufst verbraucht der Admin auch mehr an Ram.
Wenn dann das ein oder andere noch dazu kommt kann es mit dem Speicher eng werden.Ich hab z.b den backitup Adapter(~100mb) nicht mehr kontinuierlich laufen, sondern starte/stoppe per script kurz bevor das backup erstellt wird und leg in dann wieder schlafen
-
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
7 orphan inodes deleted
Das sind alles verwaiste Einträge in den inodes. Kann gut sein, dass die Kiste die aber ansprechen will, ins Leere schaut und dann beleidigt den Betrieb einstellt.
Und beim RAM tänzelst du halt an der Kante.
-
@crunchip said in Täglicher Absturz ioBroker + Zugriff auf Raspi [gelöst]:
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
Was mir auffällt, dass das meistens kurz nach 14 Uhr, während ich im ioBroker arbeite, passiert.
Naja, in dem Moment wo du den iobroker aufrufst verbraucht der Admin auch mehr an Ram.
Wenn dann das ein oder andere noch dazu kommt kann es mit dem Speicher eng werden.Ich hab z.b den backitup Adapter(~100mb) nicht mehr kontinuierlich laufen, sondern starte/stoppe per script kurz bevor das backup erstellt wird und leg in dann wieder schlafen
Ok, das werde ich dann auch mal ändern. Danke!
-
@thomas-braun
Werde die Einstellung vom backitup mal ändern!
Melde mich wieder, wenn es besser geworden ist! -
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
15:14:57 up 56 min,
@searcher57 sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
*** MEMORY ***
total used free shared buff/cache available
Mem: 1.8G 1.5G 68M 0.0K 298M 299MWas mich Wunder , schon nach 56 min hast du kein Arbeitsspeicher mehr.
Aber das ist mir schon ganz am Anfang aufgefallen !
@glasfaser sagte in Täglicher Absturz ioBroker + Zugriff auf Raspi:
@searcher57Du hast ja alles neu gemacht ...
Ich "vermute" ein javascript Programm läuft bei dir Amok ,sehe wir später mal nach .
