I've got a bit of a weird one-
I've been having issues with Zigbee2MQTT not restarting after an update. In some cases, it will restart properly, but certain devices won't rejoin the network. In order to avoid the issue, I excluded Zigbee2MQTT and related apps (Home Assistant and MQTT) from auto updates and auto backups (and they are also set not to turn off during auto backups) My situation has improved, but I still sometimes find that it has stopped unexpectedly.
For the latest crash, I realized it coincided not with the auto app update, but with the auto plugin update.
(starting at 4:15:01, there's no data)
Here's the log:
Jul 30 04:12:37 Tower CA Backup/Restore: Backup / Restore Completed
Jul 30 04:15:01 Tower Plugin Auto Update: Checking for available plugin updates
Jul 30 04:15:02 Tower kernel: docker0: port 18(vethccf4ece) entered disabled state
Jul 30 04:15:02 Tower kernel: veth24ef50b: renamed from eth0
Jul 30 04:15:02 Tower avahi-daemon[8703]: Interface vethccf4ece.IPv6 no longer relevant for mDNS.
Jul 30 04:15:02 Tower avahi-daemon[8703]: Leaving mDNS multicast group on interface vethccf4ece.IPv6 with address fe80::9c9f:54ff:fe0f:5de.
Jul 30 04:15:02 Tower kernel: docker0: port 18(vethccf4ece) entered disabled state
Jul 30 04:15:02 Tower kernel: device vethccf4ece left promiscuous mode
Jul 30 04:15:02 Tower kernel: docker0: port 18(vethccf4ece) entered disabled state
Jul 30 04:15:02 Tower avahi-daemon[8703]: Withdrawing address record for fe80::9c9f:54ff:fe0f:5de on vethccf4ece.
Jul 30 04:15:02 Tower kernel: docker0: port 18(veth7d3c02b) entered blocking state
Jul 30 04:15:02 Tower kernel: docker0: port 18(veth7d3c02b) entered disabled state
Jul 30 04:15:02 Tower kernel: device veth7d3c02b entered promiscuous mode
Jul 30 04:15:02 Tower kernel: docker0: port 18(veth7d3c02b) entered blocking state
Jul 30 04:15:02 Tower kernel: docker0: port 18(veth7d3c02b) entered forwarding state
Jul 30 04:15:02 Tower kernel: eth0: renamed from vethabbc255
Jul 30 04:15:02 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7d3c02b: link becomes ready
Jul 30 04:15:04 Tower avahi-daemon[8703]: Joining mDNS multicast group on interface veth7d3c02b.IPv6 with address fe80::583c:b9ff:fe32:c699.
Jul 30 04:15:04 Tower avahi-daemon[8703]: New relevant interface veth7d3c02b.IPv6 for mDNS.
Jul 30 04:15:04 Tower avahi-daemon[8703]: Registering new address record for fe80::583c:b9ff:fe32:c699 on veth7d3c02b.*.
Jul 30 04:15:04 Tower Plugin Auto Update: fix.common.problems.plg version 2023.07.29 does not meet age requirements to update - 1 days old
Jul 30 04:15:04 Tower Plugin Auto Update: unassigned.devices.plg version 2023.07.28 does not meet age requirements to update - 2 days old
Jul 30 04:15:04 Tower Plugin Auto Update: Checking for language updates
Jul 30 04:15:04 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished
Jul 30 04:15:09 Tower kernel: docker0: port 18(veth7d3c02b) entered disabled state
Jul 30 04:15:09 Tower kernel: vethabbc255: renamed from eth0
Jul 30 04:15:09 Tower avahi-daemon[8703]: Interface veth7d3c02b.IPv6 no longer relevant for mDNS.
Jul 30 04:15:09 Tower avahi-daemon[8703]: Leaving mDNS multicast group on interface veth7d3c02b.IPv6 with address fe80::583c:b9ff:fe32:c699.
Jul 30 04:15:09 Tower kernel: docker0: port 18(veth7d3c02b) entered disabled state
Jul 30 04:15:09 Tower kernel: device veth7d3c02b left promiscuous mode
Jul 30 04:15:09 Tower kernel: docker0: port 18(veth7d3c02b) entered disabled state
Jul 30 04:15:09 Tower avahi-daemon[8703]: Withdrawing address record for fe80::583c:b9ff:fe32:c699 on veth7d3c02b.
Jul 30 04:30:01 Tower root: Fix Common Problems Version 2023.07.16
Any idea what could cause that?