ich habe ein Programm, welches mich über neu Neustart des ioBrokers informiert. Das läuft seit längerer Zeit Amok, aber ich komme erst jetzt dazu mir das mal im Detail anzuschauen.
Immer zu jener Zeit, wenn ich Mail über den Neustart erhalte habe ich die folgende Meldung im Log:
"warn: host.ioBroker-Pi instance system.adapter.javascript.0 terminated due to SIGKILL"
Hier noch ein größerer Ausschnitt:
2019-12-06 20:56:09.796 - info: host.ioBroker-Pi instance system.adapter.tvspielfilm.0 terminated with code 0 (NO_ERROR)
2019-12-06 20:58:35.218 - warn: hm-rpc.0 (835) xmlrpc <- undefined method updateDevice ["hm-rpc.0","OEQ0651045:5",1]
2019-12-06 20:58:35.284 - warn: hm-rpc.0 (835) xmlrpc <- undefined method updateDevice ["hm-rpc.0","OEQ0651045:6",1]
2019-12-06 21:00:00.043 - info: host.ioBroker-Pi instance system.adapter.tvspielfilm.0 started with pid 3058
2019-12-06 21:00:04.073 - info: host.ioBroker-Pi instance system.adapter.dwd.0 started with pid 3232
2019-12-06 21:00:05.374 - info: tvspielfilm.0 (3058) starting. Version 1.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v10.17.0
2019-12-06 21:00:05.476 - info: tvspielfilm.0 (3058) objects written
2019-12-06 21:00:07.921 - info: dwd.0 (3232) starting. Version 2.4.3 in /opt/iobroker/node_modules/iobroker.dwd, node: v10.17.0
2019-12-06 21:00:08.099 - info: host.ioBroker-Pi instance system.adapter.ical.0 started with pid 3272
2019-12-06 21:00:09.905 - info: dwd.0 (3232) Terminated (NO_ERROR): Without reason
2019-12-06 21:00:11.025 - info: host.ioBroker-Pi instance system.adapter.dwd.0 terminated with code 0 (NO_ERROR)
2019-12-06 21:00:12.132 - info: host.ioBroker-Pi instance system.adapter.ical.1 started with pid 3425
2019-12-06 21:00:16.196 - info: host.ioBroker-Pi instance system.adapter.ical.2 started with pid 3454
2019-12-06 21:00:16.844 - info: ical.0 (3272) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v10.17.0
2019-12-06 21:00:19.352 - info: ical.0 (3272) processing URL: Müll http://p53-calendars.icloud.com/published/2/MTMwMzU2NjAzMjEzMDM1NsQPnx_uY-DyNZuxhN1hFZeNuZo9gzcxSK4D1Z83yvGL1shuxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx7UEHtc
2019-12-06 21:00:35.146 - info: tankerkoenig.0 (906) Reading data from tankerkoenig ...
2019-12-06 21:00:50.053 - warn: host.ioBroker-Pi instance system.adapter.javascript.0 terminated due to SIGKILL
2019-12-06 21:00:50.054 - info: host.ioBroker-Pi instance system.adapter.javascript.0 terminated with code NaN ()
2019-12-06 21:00:50.056 - info: host.ioBroker-Pi Restart adapter system.adapter.javascript.0 because enabled
2019-12-06 21:00:54.087 - info: ical.1 (3425) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v10.17.0
2019-12-06 21:00:56.119 - info: ical.1 (3425) processing URL: Müll http://p53-calendars.icloud.com/published/2/MTMwMzU2NjAzMjEzMDM1NsQPnx_uY-DyNZuxhN1hFZeNuZo9gzcxSK4D1Z83yvGL1shxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAtn7UEHtc
2019-12-06 21:01:00.343 - info: ical.2 (3454) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.ical, node: v10.17.0
2019-12-06 21:01:01.089 - info: ical.2 (3454) processing URL: Müll http://p53-calendars.icloud.com/published/2/MTMwMzU2NjAzMjEzMDM1NsQPnx_uY-DyNZuxhN1hFZeNuZo9gzcxSK4D1Z83yvGL1shu--xxxxxxxxxxxxxxxxxxxxxxxtAtn7UEHtc
2019-12-06 21:01:03.772 - info: ical.1 (3425) Terminated (NO_ERROR): Without reason
2019-12-06 21:01:05.363 - info: host.ioBroker-Pi instance system.adapter.ical.1 terminated with code 0 (NO_ERROR)
2019-12-06 21:01:05.479 - info: tvspielfilm.0 (3058) force terminating adapter after 1 minute
2019-12-06 21:01:05.990 - info: tvspielfilm.0 (3058) Terminated (NO_ERROR): Without reason
2019-12-06 21:01:06.514 - info: host.ioBroker-Pi instance system.adapter.tvspielfilm.0 terminated with code 0 (NO_ERROR)
2019-12-06 21:01:06.709 - info: ical.2 (3454) Terminated (NO_ERROR): Without reason
Jemand eine Idee, was das sein kann? Was mir noch auffällt, dass die Zeiten immer zu hh:01 oder hh:31 kommen, also im weitesten Sinne regelmäßig. Aber mal 6x/ täglich, mal 20/ täglich.
Ich habe jetzt die cron-jobs anders geplant (ich habe mehrere Kalender etc., welche regelmäßig abgefragt werden), so dass nun nicht mehr alle Timer "zusammenfallen".
