Hassio_supervisor is crashing (or restarting?) every 5 minutes

Development
1

Is this normal? Every 5 minutes, hassio_supervisor drops, taking hassio_dns with it, and restarts (from Docker always restart).

Every ~5 minutes, I see:

20-01-02 16:03:47 INFO (MainThread) [hassio.api] Start API on 172.30.32.2
20-01-02 16:03:47 INFO (MainThread) [hassio.addons] Phase 'initialize' start 0 add-ons
20-01-02 16:03:47 INFO (MainThread) [hassio.core] Hass.io reboot detected
20-01-02 16:03:47 INFO (MainThread) [hassio.tasks] All core tasks are scheduled
20-01-02 16:03:47 INFO (MainThread) [hassio.core] Hass.io is up and running
20-01-02 16:04:35 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token
20-01-02 16:08:27 INFO (MainThread) [__main__] Stopping Hass.io
20-01-02 16:08:27 INFO (MainThread) [hassio.api] Stop API on 172.30.32.2
20-01-02 16:08:27 INFO (MainThread) [hassio.misc.forwarder] Stop DNS forwarding
20-01-02 16:08:27 INFO (MainThread) [hassio.core] Hass.io is down
20-01-02 16:08:27 INFO (MainThread) [__main__] Close Hass.io

Ending in the logs. HA isn’t crashing or stopping. It’s only hassio_supvervisor doing this.

The container is not only downed, but removed and rebuilt on startup.

It’s very consistent.

Any idea as to why?

All other HA containers are going solid:

4f097df9fec6        homeassistant/amd64-hassio-dns:1                    "coredns -conf /conf…"   About a minute ago   Up About a minute                                                    hassio_dns
a72b4455d3fe        homeassistant/amd64-hassio-supervisor               "/bin/entry.sh pytho…"   About a minute ago   Up About a minute                                                    hassio_supervisor
ee9d83c273c3        hassioaddons/node-red-amd64:5.0.7                   "/init"                  13 hours ago         Up 13 hours                                                          addon_a0d7b954_nodered
c1460fe27f0c        sabeechen/hassio-google-drive-backup-amd64:0.98.3   "python3 -m backup"      16 hours ago         Up 16 hours         0.0.0.0:1627->1627/tcp, 8099/tcp                 addon_cebe7a76_hassio_google_drive_backup
1e7fe4e5f7b2        homeassistant/amd64-addon-samba:9.0                 "/run.sh"                16 hours ago         Up 16 hours                                                          addon_core_samba
dab2cb7832b7        hassioaddons/aircast-amd64:2.2.1                    "/init"                  16 hours ago         Up 16 hours                                                          addon_a0d7b954_aircast
e1c88b2e7b5c        homeassistant/qemux86-64-homeassistant:0.103.5      "/bin/entry.sh pytho…"   2 days ago           Up 16 hours                                                          homeassistant
2

Nevermind!

Found it. It was my watchtower taking down the supervisor container every 5 minutes. For some reason, it was unable to pull down the latest image and rebuild it. I looked at it’s logs:

time="2020-01-02T16:38:41Z" level=info msg="Creating /hassio_supervisor"
Failed to send notification email:  dial tcp 172.217.212.108:25: connect: connection timed out
time="2020-01-02T16:43:21Z" level=info msg="Found new homeassistant/amd64-hassio-supervisor:latest image (sha256:032972a1a170fba081dc67f359866683e23101010f50c73bc657d72d15b20b88)"
time="2020-01-02T16:43:27Z" level=info msg="Stopping /hassio_supervisor (9310315752ceaec2ae84db7c53c77fefd7d6b361d442e887ffffad3918936cb0) with SIGTERM"
time="2020-01-02T16:43:28Z" level=info msg="Creating /hassio_supervisor"
Failed to send notification email:  dial tcp 172.217.212.108:25: connect: connection timed out
time="2020-01-02T16:48:29Z" level=info msg="Found new homeassistant/amd64-hassio-supervisor:latest image (sha256:032972a1a170fba081dc67f359866683e23101010f50c73bc657d72d15b20b88)"
time="2020-01-02T16:48:35Z" level=info msg="Stopping /hassio_supervisor (ca7ea8346e051c6b34c2e9489db2f1f88fc00559fc221a3a4e522706adff9369) with SIGTERM"
time="2020-01-02T16:48:51Z" level=info msg="Creating /hassio_supervisor"
Failed to send notification email:  dial tcp 172.217.212.109:25: connect: connection timed out
time="2020-01-02T16:53:21Z" level=info msg="Found new homeassistant/amd64-hassio-supervisor:latest image (sha256:032972a1a170fba081dc67f359866683e23101010f50c73bc657d72d15b20b88)"
time="2020-01-02T16:53:26Z" level=info msg="Stopping /hassio_supervisor (850dcd476a5bc44c285337a92dc0c7ada7180176356651361b90ff6deff522fe) with SIGTERM"
time="2020-01-02T16:53:28Z" level=info msg="Creating /hassio_supervisor"
Failed to send notification email:  dial tcp 172.217.212.108:25: connect: connection timed out
time="2020-01-02T16:58:21Z" level=info msg="Found new homeassistant/amd64-hassio-supervisor:latest image (sha256:032972a1a170fba081dc67f359866683e23101010f50c73bc657d72d15b20b88)"
time="2020-01-02T16:58:26Z" level=info msg="Stopping /hassio_supervisor (8f663e9e7abbf398b039f49e7fb211f1682944cfa38d52e7fb2ffe252de64278) with SIGTERM"

(ignore the SMTP timeouts)

Well, at least I found the root cause to my issues! Talk about a chain of events…