Interesting thing that happens upon restart of the virtual machine si:
..@server:~$ sudo systemctl status checkmk-telegram-plus-nadzor
● checkmk-telegram-plus-nadzor.service - CheckMK Telegram Plus Service
Loaded: loaded (/etc/systemd/system/checkmk-telegram-plus-nadzor.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2023-06-05 10:10:53 CEST; 37min ago
Process: 2194 ExecStart=/usr/sbin/runuser -l nadzor -c cd /omd/sites/nadzor/local/share/checkmk-telegram-plus && /omd/sites/nadzor/bin/python3 /omd/sites>
Main PID: 2194 (code=exited, status=1/FAILURE)
Jun 05 10:10:53 server systemd[1]: checkmk-telegram-plus-nadzor.service: Main process exited, code=exited, status=1/FAILURE
Jun 05 10:10:53 server systemd[1]: checkmk-telegram-plus-nadzor.service: Failed with result 'exit-code'.
Jun 05 10:10:53 server systemd[1]: checkmk-telegram-plus-nadzor.service: Scheduled restart job, restart counter is at 5.
Jun 05 10:10:53 server systemd[1]: Stopped CheckMK Telegram Plus Service.
Jun 05 10:10:53 server systemd[1]: checkmk-telegram-plus-nadzor.service: Start request repeated too quickly.
Jun 05 10:10:53 server systemd[1]: checkmk-telegram-plus-nadzor.service: Failed with result 'exit-code'.
Jun 05 10:10:53 server systemd[1]: Failed to start CheckMK Telegram Plus Service.
Any idea as how to avoid it?