Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[arteck]

@theophilus sagte in Raspi hängt sich 2x täglich auf:

Das macht der Raspi ganz von alleine!

von alleine passiert erstmal nix..

wie hast du den iobroker installiert ? und wir brauchen das LOG vor dem aufhängen nicht danach

[Theophilus]

@arteck nach der Anleitung hier im Forum

[Theophilus]

@arteck Davor ist erstmal 20 Minuten lang nix passiert:

2023-05-31 00:00:00.056 - info: sourceanalytix.0 (811) Reset start values for : 0_userdata.0.Stromkasten.Verbrauch_Total
2023-05-31 00:00:00.097 - info: sourceanalytix.0 (811) Memory values before reset : {"stateDetails":{"consumption":true,"deviceName":"0_userdata__0__Stromkasten__Verbrauch_Total","financialCategory":"earnings","headCategory":"delivered","meter_values":true,"stateType":"ElectricityDelivery","stateUnit":"kWh","useUnit":"kWh","deviceResetLogicEnabled":true,"threshold":1},"calcValues":{"cumulativeValue":11694.8968,"start_day":11678,"start_month":11389,"start_quarter":0,"start_week":11678,"start_year":9777,"valueAtDeviceReset":0,"valueAtDeviceInit":null},"prices":{"basicPrice":"15","unitPrice":"0.17"}}
2023-05-31 00:00:00.149 - info: sourceanalytix.0 (811) Memory values after reset : {"stateDetails":{"consumption":true,"deviceName":"0_userdata__0__Stromkasten__Verbrauch_Total","financialCategory":"earnings","headCategory":"delivered","meter_values":true,"stateType":"ElectricityDelivery","stateUnit":"kWh","useUnit":"kWh","deviceResetLogicEnabled":true,"threshold":1},"calcValues":{"start_day":11694.8968,"start_month":11389,"start_quarter":0,"start_week":11678,"start_year":9777,"valueAtDeviceInit":null,"valueAtDeviceReset":0,"cumulativeValue":11694.8968},"prices":{"basicPrice":"15","unitPrice":"0.17"}}
2023-05-31 00:00:00.150 - info: sourceanalytix.0 (811) Reset start values for : 0_userdata.0.Stromkasten.Einspeisung_Total
2023-05-31 00:00:00.151 - info: sourceanalytix.0 (811) Memory values before reset : {"stateDetails":{"consumption":true,"deviceName":"0_userdata__0__Stromkasten__Einspeisung_Total","financialCategory":"earnings","headCategory":"delivered","meter_values":true,"stateType":"ElectricityDelivery","stateUnit":"kWh","useUnit":"kWh","deviceResetLogicEnabled":true,"threshold":1},"calcValues":{"cumulativeValue":103.0017,"start_day":101,"start_month":53,"start_quarter":16,"start_week":98,"start_year":0,"valueAtDeviceReset":0,"valueAtDeviceInit":null},"prices":{"basicPrice":"15","unitPrice":"0.17"}}
2023-05-31 00:00:00.175 - info: sourceanalytix.0 (811) Memory values after reset : {"stateDetails":{"consumption":true,"deviceName":"0_userdata__0__Stromkasten__Einspeisung_Total","financialCategory":"earnings","headCategory":"delivered","meter_values":true,"stateType":"ElectricityDelivery","stateUnit":"kWh","useUnit":"kWh","deviceResetLogicEnabled":true,"threshold":1},"calcValues":{"start_day":103.0017,"start_month":53,"start_quarter":16,"start_week":98,"start_year":0,"valueAtDeviceInit":null,"valueAtDeviceReset":0,"cumulativeValue":103.0017},"prices":{"basicPrice":"15","unitPrice":"0.17"}}
2023-05-31 02:02:04.727 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (1): connection timed out
2023-05-31 02:02:29.769 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (3): connection timed out
2023-05-31 02:03:14.773 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (5): connection timed out
2023-05-31 02:04:19.776 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (7): connection timed out
2023-05-31 02:04:20.689 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Connect locally to device
2023-05-31 02:04:20.690 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt Init with IP=192.168.178.122, Key=2149e76c6ae6295f, Version=3.3
2023-05-31 02:04:25.698 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (1): connection timed out
2023-05-31 02:04:50.700 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (3): connection timed out
2023-05-31 02:05:35.704 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (5): connection timed out
2023-05-31 02:06:40.708 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (7): connection timed out
2023-05-31 02:06:45.642 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Connect locally to device
2023-05-31 02:06:45.644 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt Init with IP=192.168.178.122, Key=2149e76c6ae6295f, Version=3.3
2023-05-31 02:06:50.648 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (1): connection timed out
2023-05-31 02:07:15.651 - info: tuya.0 (776) bf00d6e8fdadd39fd2bemt: Error on Reconnect (3): connection timed out

[Theophilus]

@theophilus Gestern 14.17

2023-05-30 13:29:30.562 - info: admin.0 (831) ==> Connected system.user.admin from ::ffff:192.168.178.42
2023-05-30 13:42:55.653 - info: admin.0 (831) <== Disconnect system.user.admin from ::ffff:192.168.178.42 admin
2023-05-30 14:18:26.657 - info: admin.0 (831) Request actual repository...
2023-05-30 14:18:28.004 - info: host.raspberrypi Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
2023-05-30 14:17:14.307 - info: host.raspberrypi iobroker.js-controller version 4.0.24 js-controller starting
2023-05-30 14:17:14.322 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-05-30 14:17:14.325 - info: host.raspberrypi hostname: raspberrypi, node: v18.16.0
2023-05-30 14:17:14.326 - info: host.raspberrypi ip addresses: fe80::4d0d:5036:a3d5:2263
2023-05-30 14:17:17.489 - info: host.raspberrypi connected to Objects and States
2023-05-30 14:17:17.566 - info: host.raspberrypi added notifications configuration of host
2023-05-30 14:17:18.525 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeCurrent"
2023-05-30 14:17:18.539 - info: host.raspberrypi 8 instances found
2023-05-30 14:17:18.576 - info: host.raspberrypi starting 8 instances
2023-05-30 14:17:18.695 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewest"
2023-05-30 14:17:18.724 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewestNext"
2023-05-30 14:17:18.761 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 626
2023-05-30 14:17:18.847 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmCurrent"
2023-05-30 14:17:18.920 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest"
2023-05-30 14:17:18.994 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext"
2023-05-30 14:17:19.066 - info: host.raspberrypi Some obsolete host states deleted.
2023-05-30 14:17:22.683 - info: host.raspberrypi instance system.adapter.history.0 started with pid 633
2023-05-30 14:17:23.253 - error: admin.0 (626) admin.0 already running
2023-05-30 14:17:23.262 - warn: admin.0 (626) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-30 14:17:23.907 - error: host.raspberrypi instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-30 14:17:23.909 - info: host.raspberrypi Restart adapter system.adapter.admin.0 because enabled
2023-05-30 14:17:26.052 - error: history.0 (633) history.0 already running
2023-05-30 14:17:26.061 - warn: history.0 (633) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-30 14:17:26.679 - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 648
2023-05-30 14:17:26.725 - error: host.raspberrypi instance system.adapter.history.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-30 14:17:26.727 - info: host.raspberrypi Restart adapter system.adapter.history.0 because enabled
2023-05-30 14:17:30.698 - info: host.raspberrypi instance system.adapter.mqtt.0 started with pid 655
2023-05-30 14:17:34.002 - error: javascript.0 (648) javascript.0 already running
2023-05-30 14:17:34.009 - warn: javascript.0 (648) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-30 14:17:34.213 - error: mqtt.0 (655) mqtt.0 already running
2023-05-30 14:17:34.222 - warn: mqtt.0 (655) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2023-05-30 14:17:34.669 - error: host.raspberrypi instance system.adapter.javascript.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-30 14:17:34.670 - info: host.raspberrypi Restart adapter system.adapter.javascript.0 because enabled
2023-05-30 14:17:34.808 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 670
2023-05-30 14:17:34.855 - error: host.raspberrypi instance system.adapter.mqtt.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2023-05-30 14:17:34.857 - info: host.raspberrypi Restart adapter system.adapter.mqtt.0 because enabled

[arteck]

@theophilus sagte in Raspi hängt sich 2x täglich auf:

2023-05-30 14:17:23.253 - error: admin.0 (626) admin.0 already running

hier wird probiert alles nochmal zu starten...

machst du da backup vielleicht.. und das geht in die hose..

[Ein ehemaliger Benutzer]

@theophilus sagte in Raspi hängt sich 2x täglich auf:

Davor ist erstmal 20 Minuten lang nix passiert:

Moin,

ich ehe einfach mal davon aus, dass Dir der Speicher bei irgendeiner Aktion ausgeht und das System crasht.

MEMORY: 

               total        used        free      shared  buff/cache   available
Mem:            909M        632M        120M        0.0K        156M        218M
Swap:            99M         89M         10M
Total:          1.0G        721M        131M

Wie viele Adapter hast Du denn installiert und wie viele sind aktiv?

Zeig doch mal die Langfassung von iob diag und aus dem journal die Einträge zur Zeit der Abstürze, hier mal Beispiele:
Vor 1 Stunde bis jetzt

$ journalctl --since "1 hour ago"

Von vor 2 Tagen bis jetzt

$ journalctl --since "2 days ago"

Zwischen zwei Zeiten*

$ journalctl --since "2015-06-26 23:15:00" --until "2015-06-26 23:20:00"

Oder schau mal, ob Du oom, kill im Log hast

$ journalctl | grep -iE 'oom|kill'

VG
Bernd

[Thomas Braun]

@theophilus

Gib mal die Langfassung von iob diag
Und schau zu den Zeiten in das Journal rein.

Edit: Zu langsam und zu ungenau gewesen... :-)

[Thomas Braun]

@dp20eic

Active iob-Instances: 9

Könnte für 1GB RAM schon zu viel sein.

[Theophilus]

@arteck sagte in Raspi hängt sich 2x täglich auf:

@theophilus sagte in Raspi hängt sich 2x täglich auf:

wir brauchen das LOG vor dem aufhängen nicht danach

Das Log entstand unmittelbar vor dem Aufhängen. Es waren quasi seine letzten Lebenszeichen.

[Ein ehemaliger Benutzer]

@thomas-braun sagte in Raspi hängt sich 2x täglich auf:

Active iob-Instances: 9

Moin,

oh, danke, war wohl zu früh oder ich brauche doch eine Brille, wenn ich am Laptop arbeite :)

VG
Bernd

P.S.: also Betriebssystem, nodejs, iobroker, adapter, mir schwebt da eine Aussage vor den Augen, dass da so zwischen 60 - 100 MB pro Adapter zu veranschlagen ist, dann vielleicht noch Backup oder Scripte die da etwas machen, dann kann es eng werden.

[Theophilus]

@thomas-braun Erweitern kann man beim Raspi nichts, oder?

[DJMarc75]

@theophilus sagte in Raspi hängt sich 2x täglich auf:

Erweitern kann man beim Raspi nichts, oder?

RAM ? Natürlich nicht

[Thomas Braun]

@djmarc75

Der McGiver-Ansatz:

https://www.pcgameshardware.de/Raspberry-Pi-Hardware-257637/News/4-RAM-Chip-16-GB-Upgrade-1418168/

[DJMarc75]

@thomas-braun sagte in Raspi hängt sich 2x täglich auf:

Der McGiver-Ansatz:

ein Streicholz und ein Kaugummipapier :joy:
konnte damit schon viele LinuxProbleme lösen :grinning: :+1:

[Thomas Braun]

@djmarc75

Ja, die universell einsetzbaren libmatches und libbubblegum

[Theophilus]

Heute nachmittag hat er sich nicht aufgehängt. War wohl Zufall, dass es gestern 2 Uhr und 14 Uhr war.

[Theophilus]

@theophilus Er bleibt bei. Alles läuft super, dann kommt dieser ominöse Neustart und der Raspi hängt sich auf.

2023-06-05 07:17:15.426 - info: host.raspberrypi iobroker.js-controller version 4.0.24 js-controller starting
2023-06-05 07:17:15.439 - info: host.raspberrypi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-06-05 07:17:15.441 - info: host.raspberrypi hostname: raspberrypi, node: v18.16.0
2023-06-05 07:17:15.443 - info: host.raspberrypi ip addresses: fe80::4d0d:5036:a3d5:2263
2023-06-05 07:17:19.097 - info: host.raspberrypi connected to Objects and States
2023-06-05 07:17:19.194 - info: host.raspberrypi added notifications configuration of host
2023-06-05 07:17:20.208 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeCurrent"
2023-06-05 07:17:20.221 - info: host.raspberrypi 9 instances found
2023-06-05 07:17:20.262 - info: host.raspberrypi starting 9 instances
2023-06-05 07:17:20.399 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewest"
2023-06-05 07:17:20.436 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.nodeNewestNext"
2023-06-05 07:17:20.475 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 632
2023-06-05 07:17:20.509 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmCurrent"
2023-06-05 07:17:20.543 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewest"
2023-06-05 07:17:20.617 - info: host.raspberrypi Delete state "system.host.raspberrypi.versions.npmNewestNext"
2023-06-05 07:17:20.646 - info: host.raspberrypi Some obsolete host states deleted.
2023-06-05 07:17:24.495 - info: host.raspberrypi instance system.adapter.history.0 started with pid 639
2023-06-05 07:17:25.903 - info: admin.0 (632) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24
2023-06-05 07:17:26.028 - info: admin.0 (632) requesting all states
2023-06-05 07:17:26.030 - info: admin.0 (632) requesting all objects
2023-06-05 07:17:28.610 - info: host.raspberrypi instance system.adapter.javascript.0 started with pid 666
2023-06-05 07:17:29.621 - info: admin.0 (632) received all objects
2023-06-05 07:17:30.198 - info: history.0 (639) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.history, node: v18.16.0, js-controller: 4.0.24
2023-06-05 07:17:30.369 - info: history.0 (639) enabled logging of 0_userdata.0.Solar.Solar_Aktuell (Count=1), Alias=false
2023-06-05 07:17:30.372 - info: history.0 (639) enabled logging of 0_userdata.0.Stromkasten.Verbrauch_Aktuell (Count=2), Alias=false
2023-06-05 07:17:30.375 - info: history.0 (639) enabled logging of 0_userdata.0.Stromkasten.Verbrauch_Total (Count=3), Alias=false
2023-06-05 07:17:30.377 - info: history.0 (639) enabled logging of 0_userdata.0.Stromkasten.Einspeisung_Total (Count=4), Alias=false
2023-06-05 07:17:31.502 - info: admin.0 (632) Request actual repository...
2023-06-05 07:17:31.655 - info: admin.0 (632) http server listening on port 8081
2023-06-05 07:17:31.658 - info: admin.0 (632) Use link "http://localhost:8081" to configure.
2023-06-05 07:17:31.703 - info: admin.0 (632) socket.io server listening on port 8081
2023-06-05 07:17:33.587 - info: host.raspberrypi Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2023-06-05 07:17:33.770 - info: host.raspberrypi instance system.adapter.mqtt.0 started with pid 681
2023-06-05 07:17:35.155 - info: admin.0 (632) failed connection to socket.io from ::ffff:192.168.178.42: Passport was not initialized
2023-06-05 07:17:35.438 - info: admin.0 (632) failed connection to socket.io from ::ffff:192.168.178.42: Passport was not initialized
2023-06-05 07:17:36.396 - info: host.raspberrypi instance system.adapter.tuya.0 started with pid 688

[Thomas Braun]

@theophilus

Schau in dein Journal.

[Theophilus]

@thomas-braun Das Merkwürdige ist, dass die iobroker-Instanz zu dieser Zeit gestoppt war. Da ich in den nächsten Tagen viel unterwegs bin und sich der Raspi immer wieder aufhängt und mir dann über Tage hinweg die Stromdaten fehlen, war mein Plan, den Raspi jeweils um 2:00 Uhr nachts neu zu starten. 1.Versuch: per Cron-Job und wenn das nichts bringt, brutal per Zeitschaltuhr und kappen der Stromzufuhr.
Heute nacht also Cronjob. Der hat geklappt (nur beim Reboot habe ich einen Fehler gemacht.) Journal:

un 05 02:00:01 raspberrypi CRON[2510]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jun 05 02:00:01 raspberrypi CRON[2511]: (root) CMD (iobroker stop)
Jun 05 02:00:01 raspberrypi sudo[2516]:     root : PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl stop iobroker
Jun 05 02:00:01 raspberrypi sudo[2516]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Jun 05 02:00:01 raspberrypi systemd[1]: Stopping ioBroker Server...
Jun 05 02:00:03 raspberrypi bash[488]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
Jun 05 02:00:03 raspberrypi bash[488]: ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]
Jun 05 02:00:03 raspberrypi bash[488]: ================================== > LOG REDIRECT system.adapter.javascript.0 => false [Process stopped]
Jun 05 02:00:03 raspberrypi bash[488]: ================================== > LOG REDIRECT system.adapter.javascript.0 => false [system.adapter.javascript.0.logging]
Jun 05 02:00:06 raspberrypi systemd[1]: iobroker.service: Main process exited, code=exited, status=1/FAILURE
Jun 05 02:00:06 raspberrypi systemd[1]: iobroker.service: Failed with result 'exit-code'.
Jun 05 02:00:06 raspberrypi systemd[1]: Stopped ioBroker Server.
Jun 05 02:00:06 raspberrypi systemd[1]: iobroker.service: Consumed 38min 33.182s CPU time.
Jun 05 02:00:06 raspberrypi sudo[2516]: pam_unix(sudo:session): session closed for user root
Ju

So ganz verstehe ich aber nicht, was die angezeigte Fehlermeldung bedeutet ...

[crunchip]

@theophilus sagte in Raspi hängt sich 2x täglich auf:

brutal per Zeitschaltuhr und kappen der Stromzufuhr.

das wäre ein dummer und tödlicher Prozess