Neues YouTube-Video: Visualisierung im Devices-Adapter

[hg6806]

Die Abstürze finden NICHT immer morgens um 6Uhr statt. Auch viel tagsüber.

Ich habe auch schon Stunden gewartet, das System fängt sich nicht wieder.

Wie geschrieben, kurz vor dem Freeze lag die CPU Load bei 1,7, nicht ansteigend

[hg6806]

@paul53
Ja, beide USB3 wird verwendet.
Daran ist die SSD angeschlossen, sowie ein USB2.0 Hub mit 3 USB2.0Sticks

[Homoran]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

beide USB3 wird verwendet.
Daran ist die SSD angeschlossen, sowie ein USB2.0 Hub mit 3 USB2.0Sticks

Abgesehen von der USB3-Problematik stellt sich dann die Frage ob die Spannungsversorgung für so viele Verbraucher reicht

[hg6806]

Ich habe nochmal nachgeschaut. Durch den RPI Adapter kann man das gut sehen, wann das System mal "weg" war.
Es ist grob 1x die Woche aber immer zu unterschiedlichen Uhrzeiten und Tageszeiten, deshalb würde ich einen zeitlichen Trigger hier ausschließen.

[hg6806]

@homoran
Hatte ich mir auch schon überlegt.
Ich habe ein 2,4A Meanwell Hutschienen-Netzteil dran, dass ich auf 5,25V eingestellt habe um evtl. Kabelverluste auszukompensieren, jedoch sind die Kabel recht dick.
An dem Pi sind neben einer SSD keine Stromfresser dran.
Zudem würde das ja vermehrt bei Last abstürzen was nicht der Fall ist.

Kann man in irgendeinem Log eine Unterspannung sehen?

[Homoran]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Ich habe ein 2,4A Meanwell Hutschienen-Netzteil dran

das reicht nicht! der Pi4 braucht viel Strom

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

An dem Pi sind neben einer SSD keine Stromfresser dran.

und was ist mit den USB-Sticks und dem Hub?

[hg6806]

@homoran
Verbrauchen nur wenige mA, deswegen sehe ich das nicht als Stromfresser.

OK, es sind noch zwei IR-USB-Leseköpfe für Stromzähler dran (Volkszähler)
Weiß jemand was so ein Teil an Strom zieht?

[Homoran]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Verbrauchen nur wenige mA

auch der Hub?

und selbst wenn es so wäre, es summiert sich

[paul53]

@hg6806 sagte: beide USB3 wird verwendet.

Der Anschluss von USB-3-Geräten kann einen so hohen Störpegel verursachen, dass das RPi OS abstürzt. Wechsle mal auf USB 2.

EDIT: Hat der RPi 4 ein abschirmendes Gehäuse?

[hg6806]

@homoran sagte in Sporadische Abstürtze Raspberry Pi4:

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Verbrauchen nur wenige mA

auch der Hub?

und selbst wenn es so wäre, es summiert sich

Ist ein passiver Hub. Die PowerConsumption von einem Hub-IC ist marginal gering.

OK, alles in Allem sollte ich doch mal ein gr. Netzteil nehmen, da halt immer sukzessive mehr dazugekommen ist.

[Homoran]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Ist ein passiver Hub

aktiv hätte ja eine eigene Spannungsversorgung und wäre somit besser.

du kannst aber mal im Syslog nach under-voltage suchen

[hg6806]

@paul53 sagte in Sporadische Abstürtze Raspberry Pi4:

@hg6806 sagte: beide USB3 wird verwendet.

Der Anschluss von USB-3-Geräten kann einen so hohen Störpegel verursachen, dass das RPi OS abstürzt. Wechsle mal auf USB 2.

EDIT: Hat der RPi 4 ein abschirmendes Gehäuse?

Habe ich jetzt das erst Mal davon gehört, dass es hier Störungen auf USB3 geben soll.
Nein, Gehäuse ist nicht geschirmt.

[hg6806]

@homoran sagte in Sporadische Abstürtze Raspberry Pi4:

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Ist ein passiver Hub

aktiv hätte ja eine eigene Spannungsversorgung und wäre somit besser.

du kannst aber mal im Syslog nach under-voltage suchen

Wo finde ich auf dem Pi das Syslog?

[hg6806]

Hier mal das Syslog vom Pi zu der Zeit, im Anhang auf Grund der Größe
Ab 6.00Uhr schient das System neu hochgefahren zu sein?

Und was sollen die häufigen Meldungen wie:

Oct  8 07:10:42 raspberrypi dhcpcd[510]: eth0: Router Advertisement from fe80::464e:6dff:fe3a:e01c
Oct  8 07:11:08 raspberrypi bash[548]: cat: /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: Keine Berechtigung

syslog_partial.txt

[Homoran]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Wo finde ich auf dem Pi das Syslog?

was sagt: tac /var/log/kern.log | grep -i under

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Ab 6.00Uhr schient das System neu hochgefahren zu sein?

das sieht man ja im iobroker log (zumindest dass iobroker da neu startet)

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

Und was sollen die häufigen Meldungen wie:

google sagt:
https://unix.stackexchange.com/questions/273818/can-i-stop-ipv6-router-advertisement-filling-syslog-without-disabling-ipv6

[hg6806]

So, habe jetzt ein 5V 6A Netzteil eingebaut und leider noch immer gelegentliche Abstürze.
@paul53 Wenn es wirklich ein Problem mit USB3 gäbe, würde man glaube ich mehr darüber lesen. Außerdem sollte doch, wenn das abschmiert, der Pi über die Konsole noch bedienbar sein.

Ist aber nur eine Vermutung, da ich von Pi + Linux nicht so viel Ahnung habe.

Aus dem Log werde ich auch nicht schlaub, auch warum diese zwei Zeitsprünge sind:

2021-11-20 14:19:46.823  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:19:46.823  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:19:52.259  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:19:56.768  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:19:56.769  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:19:56.769  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:19:57.813  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:20:00.121  - info: host.raspberrypi instance system.adapter.tvspielfilm.0 started with pid 32585
2021-11-20 14:20:02.319  - info: tvspielfilm.0 (32585) starting. Version 2.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v12.22.6, js-controller: 3.3.18
2021-11-20 14:20:02.990  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:04.413  - info: tvspielfilm.0 (32585) objects written
2021-11-20 14:20:06.564  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:06.828  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:06.829  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:08.248  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:20:11.503  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Soll_T_Raum_1" has to be type "string" but received type "number" 
2021-11-20 14:20:13.890  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:14.923  - info: tvspielfilm.0 (32585) Terminated (NO_ERROR): Without reason
2021-11-20 14:20:15.488  - info: host.raspberrypi instance system.adapter.tvspielfilm.0 terminated with code 0 (NO_ERROR)
2021-11-20 14:20:16.829  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:16.830  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:16.830  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:18.755  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:20:22.175  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Raumthermostat" has to be type "string" but received type "boolean" 
2021-11-20 14:20:24.726  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:26.773  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:26.774  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:26.775  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:30.546  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:20:35.485  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:36.565  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:36.857  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:36.858  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:42.086  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:20:46.105  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:46.821  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:46.822  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:46.822  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:50.249  - info: fhem.0 (28443) stateChange (out): fhem.0.info.Commands.sendFHEM | set fhem.0.alive on-for-timer 360 > set fhem.0.alive on-for-timer 360
2021-11-20 14:20:53.135  - info: smartmeter.0 (1501) Received 10 values, 5 updated
2021-11-20 14:20:56.587  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:20:56.681  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:20:56.730  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:20:56.730  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:20:58.730  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Wartezeit_BOH" has to be type "string" but received type "number" 
2021-11-20 14:21:03.880  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:21:05.314  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Betrieb_Kompressor" has to be type "string" but received type "boolean" 
2021-11-20 14:21:06.557  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:06.817  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:06.817  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:21:07.013  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:21:15.111  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:21:16.013  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Soll_T_Raum_1" has to be type "string" but received type "number" 
2021-11-20 14:21:16.696  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:16.787  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:16.790  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:21:17.468  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:21:22.485  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Raumthermostat" has to be type "string" but received type "boolean" 
2021-11-20 14:21:26.349  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:21:26.785  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:26.791  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:26.792  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:21:28.818  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:21:36.566  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:36.860  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:36.861  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:21:37.521  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:21:40.189  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:21:46.694  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:46.785  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:46.788  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:21:49.595  - warn: hm-rega.0 (8445) State value to set for "hm-rega.0.13675" has value "-7.1" less than min "0"
2021-11-20 14:21:49.690  - info: smartmeter.0 (1501) Received 10 values, 5 updated
2021-11-20 14:21:50.930  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Betrieb_UWPumpe" has to be type "string" but received type "boolean" 
2021-11-20 14:21:51.508  - info: smartmeter.1 (1596) Received 10 values, 5 updated
2021-11-20 14:21:54.477  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Betrieb_Kompressor" has to be type "string" but received type "boolean" 
2021-11-20 14:21:56.684  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:21:56.734  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:21:56.735  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:22:00.954  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:22:03.650  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:22:06.571  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:22:06.861  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:22:06.862  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:22:11.972  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:22:14.215  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:22:16.861  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:22:16.862  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:22:16.862  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:22:18.713  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Soll_T_Raum_1" has to be type "string" but received type "number" 
2021-11-20 14:22:22.645  - info: smartmeter.0 (1501) Received 10 values, 3 updated
2021-11-20 14:22:25.168  - info: fhem.0 (28443) State value to set for "fhem.0.myHPSU.HPSU~Raumthermostat" has to be type "string" but received type "boolean" 
2021-11-20 14:22:25.335  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:22:26.811  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
2021-11-20 14:22:26.812  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTDURATION" has to be type "number" but received type "string" 
2021-11-20 14:22:26.812  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.EVENTREMAINING" has to be type "number" but received type "string" 
2021-11-20 14:22:33.879  - info: smartmeter.0 (1501) Received 10 values, 5 updated
2021-11-20 14:22:35.954  - info: smartmeter.1 (1596) Received 10 values, 3 updated
2021-11-20 14:22:36.566  - info: enigma2.0 (24138) State value to set for "enigma2.0.enigma2.MESSAGE_ANSWER" has to be type "integer" but received type "string" 
                                                                                                                                                                                                                                                                                                                                                     2021-11-20 14:17:08.808  - info: host.raspberrypi iobroker.js-controller version 3.3.18 js-controller starting
2021-11-20 14:17:08.814  - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-11-20 14:17:08.815  - info: host.raspberrypi hostname: raspberrypi, node: v12.22.6
2021-11-20 14:17:08.816  - info: host.raspberrypi ip addresses: 
2021-11-20 14:17:09.829  - error: host.raspberrypi-Server Cannot load /opt/iobroker/iobroker-data/states.json: /opt/iobroker/iobroker-data/states.json: Unexpected end of JSON input. We try last Backup!
2021-11-20 14:17:10.503  - info: host.raspberrypi connected to Objects and States
2021-11-20 14:17:10.946  - info: host.raspberrypi added notifications configuration of host
2021-11-20 14:17:11.998  - info: host.raspberrypi 51 instances found
2021-11-20 14:17:12.121  - info: host.raspberrypi starting 30 instances
2021-11-20 14:17:12.329  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 889
2021-11-20 14:17:14.360  - error: admin.0 (889) admin.0 already running
2021-11-20 14:17:14.363  - warn: admin.0 (889) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:15.056  - error: host.raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:15.057  - info: host.raspberrypi Restart adapter system.adapter.admin.0 because enabled
2021-11-20 14:17:16.190  - info: host.raspberrypi instance system.adapter.email.0 started with pid 967
2021-11-20 14:17:17.681  - error: email.0 (967) email.0 already running
2021-11-20 14:17:17.684  - warn: email.0 (967) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:18.305  - error: host.raspberrypi instance system.adapter.email.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:18.306  - info: host.raspberrypi Restart adapter system.adapter.email.0 because enabled
2021-11-20 14:17:20.244  - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 1029
2021-11-20 14:17:23.663  - error: javascript.0 (1029) javascript.0 already running
2021-11-20 14:17:23.666  - warn: javascript.0 (1029) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:24.258  - info: host.raspberrypi instance system.adapter.scenes.0 started with pid 1098
2021-11-20 14:17:24.369  - error: host.raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:24.371  - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled
2021-11-20 14:17:25.580  - error: scenes.0 (1098) scenes.0 already running
2021-11-20 14:17:25.583  - warn: scenes.0 (1098) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:26.252  - error: host.raspberrypi instance system.adapter.scenes.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:26.252  - info: host.raspberrypi Restart adapter system.adapter.scenes.0 because enabled
2021-11-20 14:17:28.278  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 1109
2021-11-20 14:17:30.367  - error: telegram.0 (1109) telegram.0 already running
2021-11-20 14:17:30.369  - warn: telegram.0 (1109) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:30.995  - error: host.raspberrypi instance system.adapter.telegram.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:30.995  - info: host.raspberrypi Restart adapter system.adapter.telegram.0 because enabled
2021-11-20 14:17:32.186  - info: host.raspberrypi instance system.adapter.fhem.0 started with pid 1193
2021-11-20 14:17:33.444  - error: fhem.0 (1193) fhem.0 already running
2021-11-20 14:17:33.447  - warn: fhem.0 (1193) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:17:34.070  - error: host.raspberrypi instance system.adapter.fhem.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:17:34.070  - info: host.raspberrypi Restart adapter system.adapter.fhem.0 because enabled
2021-11-20 14:24:00.586  - info: host.raspberrypi instance system.adapter.hm-rega.0 started with pid 1205
2021-11-20 14:24:02.178  - error: hm-rega.0 (1205) hm-rega.0 already running
2021-11-20 14:24:02.182  - warn: hm-rega.0 (1205) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:24:02.841  - error: host.raspberrypi instance system.adapter.hm-rega.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:24:02.842  - info: host.raspberrypi Restart adapter system.adapter.hm-rega.0 because enabled
2021-11-20 14:24:04.541  - info: host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 1218
2021-11-20 14:24:05.779  - error: hm-rpc.0 (1218) hm-rpc.0 already running
2021-11-20 14:24:05.782  - warn: hm-rpc.0 (1218) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:24:06.471  - error: host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:24:06.471  - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
2021-11-20 14:24:08.584  - info: host.raspberrypi instance scheduled system.adapter.ical.0 */15 * * * *
2021-11-20 14:24:08.600  - info: host.raspberrypi instance system.adapter.ical.0 started with pid 1231
2021-11-20 14:24:09.388  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 1238
2021-11-20 14:24:11.233  - info: ical.0 (1231) starting. Version 1.11.5 in /opt/iobroker/node_modules/iobroker.ical, node: v12.22.6, js-controller: 3.3.18
2021-11-20 14:24:12.552  - info: host.raspberrypi instance system.adapter.modbus.0 started with pid 1257
2021-11-20 14:24:12.612  - info: admin.0 (1238) starting. Version 5.1.28 in /opt/iobroker/node_modules/iobroker.admin, node: v12.22.6, js-controller: 3.3.18
2021-11-20 14:24:12.645  - info: host.raspberrypi instance system.adapter.email.0 started with pid 1265
2021-11-20 14:24:12.679  - info: admin.0 (1238) requesting all states
2021-11-20 14:24:12.680  - info: admin.0 (1238) requesting all objects
2021-11-20 14:24:12.749  - info: ical.0 (1231) processing URL: Müll https://calendar.google.com/calendar/ical/s5vhoqogjjck1l2q6gslhoiht90p6cl1%40import.calendar.google.com/public/basic.ics
2021-11-20 14:24:13.029  - info: ical.0 (1231) processing URL: Sport Sommer https://calendar.google.com/calendar/ical/1e9sre2l68raqr1c7cm76t2dc4%40group.calendar.google.com/private-a244195aa7bcb903a03f42342e044b9e/basic.ics
2021-11-20 14:24:14.606  - info: ical.0 (1231) processing URL: Müll2021 https://calendar.google.com/calendar/embed?src=8la60lfbvo8avojen3ufm33uiejf93e7%40import.calendar.google.com&ctz=Europe%2FBerlin
2021-11-20 14:24:15.242  - error: modbus.0 (1257) modbus.0 already running
2021-11-20 14:24:15.246  - warn: modbus.0 (1257) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2021-11-20 14:24:15.858  - info: admin.0 (1238) received all objects
2021-11-20 14:24:15.898  - error: host.raspberrypi instance system.adapter.modbus.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2021-11-20 14:24:15.899  - info: host.raspberrypi Restart adapter system.adapter.modbus.0 because enabled
2021-11-20 14:24:15.972  - info: email.0 (1265) starting. Version 1.0.10 in /opt/iobroker/node_modules/iobroker.email, node: v12.22.6, js-controller: 3.3.18
2021-11-20 14:24:16.269  - info: admin.0 (1238) http server listening on port 8081
2021-11-20 14:24:16.270  - info: admin.0 (1238) Use link "http://localhost:8081" to configure.
2021-11-20 14:24:16.521  - info: host.raspberrypi instance system.adapter.mqtt.0 started with pid 1287
2021-11-20 14:24:17.729  - error: mqtt.0 (1287) mqtt.0 already running

[Thomas Braun]

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

@paul53 Wenn es wirklich ein Problem mit USB3 gäbe, würde man glaube ich mehr darüber lesen.

Dann musst du mehr lesen.

Aus dem Log werde ich auch nicht schlaub, auch warum diese zwei Zeitsprünge sind:

Da kommt wohl die Systemzeit aus dem Tritt. Überlastet?

[paul53]

@hg6806 sagte: Wenn es wirklich ein Problem mit USB3 gäbe, würde man glaube ich mehr darüber lesen.

Man liest eine Menge darüber.

@hg6806 sagte in Sporadische Abstürtze Raspberry Pi4:

wenn das abschmiert, der Pi über die Konsole noch bedienbar sein.

Wenn das OS schon nicht sauber geladen und gestartet wird, kommt man auch nicht über SSH auf den RasPi.

[hg6806]

@paul53 sagte in Sporadische Abstürtze Raspberry Pi4:

Wenn das OS schon nicht sauber geladen und gestartet wird, kommt man auch nicht über SSH auf den RasPi.

Es passiert ja immer wenn das System normal gestartet ist, aus heiterem Himmel.
Manchmal merke ich das erst nach Minuten/Stunden, wenn das Wandtablet nichts anzeigt.

[paul53]

@hg6806 sagte: aus heiterem Himmel.

Das ist das Wesen von Störstrahlung, dass sie zufällig die Elektronik durcheinander bringt. Es genügt, wenn 1 Bit auf dem Weg vom RAM zur CPU (oder umgekehrt) kippt.