[Gelöst] täglicher Trigger sendet Telegram Nachricht

[lethuer]

Hallo,

ich habe aktuell ein Problem, dass ich täglich mehrere Telegram Nachrichten zum gleichen Zeitpunkt von allen aktiven Skripten gesendet bekomme.
Scheint mir also ein täglich ausgelöster Trigger zu sein, die Uhrzeiten variieren jedoch.
Der tägliche Trigger von allen Adaptern ist deaktiviert (zu prüfen im Expertenmodus im Instanzen Reiter).
Der Trigger muss also durch irgendetwas anderes ausgelöst werden, nur durch was ?!

Hier mal der Log von heute, um 13:45 / 13:46 kamen dann 4 Nachrichten vom Telegram Adapter ausgelöst von meinen Skripten, sodass wohl auch der javascript Adapter neu startet:

2022-07-10 13:44:09.643 - info: admin.0 (487) Request actual repository...
2022-07-10 13:44:09.815 - info: host.ioBroker-RasPi Update repository "default" under "http://download.iobroker.net/sources-dist.json"
2022-07-10 13:44:11.489 - info: admin.0 (487) Repository received successfully.
2022-07-10 13:44:27.985 - warn: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated due to SIGKILL
2022-07-10 13:44:27.994 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code NaN ()
2022-07-10 13:44:27.995 - info: host.ioBroker-RasPi Restart adapter system.adapter.javascript.0 because enabled
2022-07-10 13:44:28.071 - warn: host.ioBroker-RasPi instance system.adapter.admin.0 terminated due to SIGKILL
2022-07-10 13:44:28.078 - info: host.ioBroker-RasPi instance system.adapter.admin.0 terminated with code NaN ()
2022-07-10 13:44:28.079 - info: host.ioBroker-RasPi Restart adapter system.adapter.admin.0 because enabled
2022-07-10 13:44:58.091 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 started with pid 8382
2022-07-10 13:44:58.170 - info: host.ioBroker-RasPi instance system.adapter.admin.0 started with pid 8383
2022-07-10 13:45:03.736 - info: javascript.0 (8382) starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v12.22.9, js-controller: 3.1.6
2022-07-10 13:45:03.797 - info: javascript.0 (8382) requesting all states
2022-07-10 13:45:03.803 - info: javascript.0 (8382) requesting all objects
2022-07-10 13:45:03.805 - warn: javascript.0 (8382) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2022-07-10 13:45:04.756 - info: javascript.0 (8382) received all states
2022-07-10 13:45:05.961 - info: admin.0 (8383) starting. Version 4.1.10 in /opt/iobroker/node_modules/iobroker.admin, node: v12.22.9, js-controller: 3.1.6
2022-07-10 13:45:06.020 - info: admin.0 (8383) requesting all states
2022-07-10 13:45:06.022 - info: admin.0 (8383) requesting all objects
2022-07-10 13:45:06.200 - info: javascript.0 (8382) received all objects
2022-07-10 13:45:06.208 - warn: javascript.0 (8382) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
2022-07-10 13:45:06.321 - info: javascript.0 (8382) Start javascript script.js.mySkript.TV_ein
2022-07-10 13:45:06.334 - info: javascript.0 (8382) script.js.mySkript.TV_ein: false
2022-07-10 13:45:06.338 - info: javascript.0 (8382) script.js.mySkript.TV_ein: registered 1 subscription and 0 schedules
2022-07-10 13:45:06.339 - info: javascript.0 (8382) Start javascript script.js.mySkript.TV_aus
2022-07-10 13:45:06.344 - info: javascript.0 (8382) script.js.mySkript.TV_aus: TV aus (erkannt von Tv aus)
2022-07-10 13:45:06.345 - info: javascript.0 (8382) script.js.mySkript.TV_aus: registered 0 subscriptions and 0 schedules
2022-07-10 13:45:06.346 - info: javascript.0 (8382) Start javascript script.js.mySkript.Telegram_Saugen
2022-07-10 13:45:06.353 - info: javascript.0 (8382) script.js.mySkript.Telegram_Saugen: registered 0 subscriptions and 0 schedules
2022-07-10 13:45:06.355 - info: javascript.0 (8382) Start javascript script.js.mySkript.Telegram_KatzenkloSaugen
2022-07-10 13:45:06.360 - info: javascript.0 (8382) script.js.mySkript.Telegram_KatzenkloSaugen: registered 0 subscriptions and 0 schedules
2022-07-10 13:45:21.820 - warn: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated due to SIGKILL
2022-07-10 13:45:21.846 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 terminated with code NaN ()
2022-07-10 13:45:21.848 - info: host.ioBroker-RasPi Restart adapter system.adapter.javascript.0 because enabled
2022-07-10 13:45:22.341 - info: admin.0 (8383) received all objects
2022-07-10 13:45:23.084 - info: admin.0 (8383) http server listening on port 8081
2022-07-10 13:45:23.085 - info: admin.0 (8383) Use link "http://localhost:8081" to configure.
2022-07-10 13:45:51.912 - error: host.ioBroker-RasPi Your system has only 45 MB RAM left available and an additional adapter process is started. Please check your system, settings and active instances to prevent swapping and Out-Of-Memory situations!
2022-07-10 13:45:51.915 - error: host.ioBroker-RasPi In future versions, the adapter might not be started!
2022-07-10 13:45:51.994 - info: host.ioBroker-RasPi instance system.adapter.javascript.0 started with pid 8457
2022-07-10 13:45:58.233 - info: javascript.0 (8457) starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v12.22.9, js-controller: 3.1.6
2022-07-10 13:45:58.400 - info: javascript.0 (8457) requesting all states
2022-07-10 13:45:58.404 - info: javascript.0 (8457) requesting all objects
2022-07-10 13:45:58.406 - warn: javascript.0 (8457) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2022-07-10 13:45:59.383 - info: javascript.0 (8457) received all states
2022-07-10 13:46:00.621 - info: javascript.0 (8457) received all objects
2022-07-10 13:46:00.629 - warn: javascript.0 (8457) adapter.objects.getObjectView is deprecated, and will be removed in the future. Please use adapter.getObjectView/Async. Report this to Developer!
2022-07-10 13:46:00.762 - info: javascript.0 (8457) Start javascript script.js.mySkript.TV_ein
2022-07-10 13:46:00.879 - info: javascript.0 (8457) script.js.mySkript.TV_ein: false
2022-07-10 13:46:00.882 - info: javascript.0 (8457) script.js.mySkript.TV_ein: registered 1 subscription and 0 schedules
2022-07-10 13:46:00.884 - info: javascript.0 (8457) Start javascript script.js.mySkript.TV_aus
2022-07-10 13:46:00.889 - info: javascript.0 (8457) script.js.mySkript.TV_aus: TV aus (erkannt von Tv aus)
2022-07-10 13:46:00.890 - info: javascript.0 (8457) script.js.mySkript.TV_aus: registered 0 subscriptions and 0 schedules
2022-07-10 13:46:00.891 - info: javascript.0 (8457) Start javascript script.js.mySkript.Telegram_Saugen
2022-07-10 13:46:00.898 - info: javascript.0 (8457) script.js.mySkript.Telegram_Saugen: registered 0 subscriptions and 0 schedules
2022-07-10 13:46:00.900 - info: javascript.0 (8457) Start javascript script.js.mySkript.Telegram_KatzenkloSaugen
2022-07-10 13:46:00.906 - info: javascript.0 (8457) script.js.mySkript.Telegram_KatzenkloSaugen: registered 0 subscriptions and 0 schedules

Als mögliche Ursache fällt mir im Log im besagten Zeitraum das auf:

2022-07-10 13:45:51.912 - error: host.ioBroker-RasPi Your system has only 45 MB RAM left available and an additional adapter process is started. Please check your system, settings and active instances to prevent swapping and Out-Of-Memory situations!
2022-07-10 13:45:51.915 - error: host.ioBroker-RasPi In future versions, the adapter might not be started!

"free -m -t" in der Kommandozeile liefert gerade beim Schreiben dieses Beitrages:

pi@ioBroker-RasPi:~$ free -m -t
total        used        free      shared  buff/cache   available
Mem:            926         764          57          21         103         120
Swap:            99          99           0
Total:         1026         864          57

Wie kann es also dazu kommen, dass gerade mal noch 48 MB RAM frei waren ?

[paul53]

@lethuer sagte: mehrere Telegram Nachrichten zum gleichen Zeitpunkt von allen aktiven Skripten

Ein Skript unter der Gruppe "global" (Expertenmodus aktivieren)?

[Thomas Braun]

@lethuer

node: v12.22.9, js-controller: 3.1.6

System auf Stand halten. Und 1GB ist halt auch keine üppige Grundausstattung an RAM.

[paul53]

@lethuer sagte: Wie kann es also dazu kommen, dass gerade mal noch 48 MB RAM frei waren ?

Zu viele aktive Instanzen für 1 GB RAM.
Wird eine Instanz per CRON gestartet?

[lethuer]

@paul53 tatsächlich waren es zu viele Instanzen parallel, ich hab jetzt ein paar deaktiviert die ich nicht wirklich brauchte.
Mal sehen ob das Abhilfe schafft.