HA just hanging at random after upgrade to 0.65

Anyone finding HA quite unstable since on 0.65? Since upgrading my instance just hangs randomly. It’s done it twice over the last couple of days while I was running it in a virtual env, and today I moved to running it from docker and it’s done it again.

Nothing of much use in the logs. One minute it’s running, and then it just stops logging anything except that pychromecast warning.

home-assistant   | 2018-03-13 22:41:29 INFO (SyncWorker_7) [homeassistant.components.device_tracker.nmap_tracker] nmap scan successful
home-assistant   | 2018-03-13 22:41:30 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sun.sun, old_state=<state sun.sun=below_horizon; next_dawn=2018-03-14T05:47:03+00:00, next_dusk=2018-03-14T18:37:39+00:00, next_midnight=2018-03-14T00:12:13+00:00, next_noon=2018-03-14T12:12:21+00:00, next_rising=2018-03-14T06:20:17+00:00, next_setting=2018-03-14T18:04:26+00:00, elevation=-37.15, azimuth=330.79, friendly_name=Sun @ 2018-03-13T19:58:42.013659+00:00>, new_state=<state sun.sun=below_horizon; next_dawn=2018-03-14T05:47:03+00:00, next_dusk=2018-03-14T18:37:39+00:00, next_midnight=2018-03-14T00:12:13+00:00, next_noon=2018-03-14T12:12:21+00:00, next_rising=2018-03-14T06:20:17+00:00, next_setting=2018-03-14T18:04:26+00:00, elevation=-37.23, azimuth=331.09, friendly_name=Sun @ 2018-03-13T19:58:42.013659+00:00>>
home-assistant   | 2018-03-13 22:41:31 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.songpal
home-assistant   | 2018-03-13 22:41:47 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 22:46:52 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 22:51:58 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 22:57:04 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:02:09 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:04:21 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:14:39 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:19:45 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:24:50 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:29:56 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:30:19 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:35:24 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:42:17 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:47:23 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:52:29 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
home-assistant   | 2018-03-13 23:57:34 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection

I’m wondering if I could create a script to determine if HA is not responding, and restart the docker container.

I tried wget on the local IP/Port and it didn’t return anything. I could only get a response via my external URL. Is that because I’ve got my base url set to the external url in my config?

And it’s died again, randomly

dTS=2018-03-16 11:38:34:574 , lastRequestRTT=24, averageRequestRTT=24, lastResponseRTT=36, averageResponseRTT=35, battery_level=0, wake_up_interval=7200, friendly_name=Fibaro Hallway Motion Sensor @ 2018-03-16T01:41:07.325612+00:00>>
2018-03-16 11:38:35 INFO (SyncWorker_4) [homeassistant.components.device_tracker.nmap_tracker] No MAC address found for 192.168.0.26
2018-03-16 11:38:35 INFO (SyncWorker_4) [homeassistant.components.device_tracker.nmap_tracker] nmap scan successful
2018-03-16 11:38:37 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.songpal
2018-03-16 11:38:53 WARNING (Thread-11) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-03-16 11:43:59 WARNING (Thread-11) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-03-16 11:49:04 WARNING (Thread-11) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-03-16 11:54:09 WARNING (Thread-11) [pychromecast.socket_client] Heartbeat timeout, resetting connection

Have set this up in a cron so at least it gets restarted when it hangs:

jhayes@server:~/docker$ cat check_homeassistant 
#!/bin/bash
timeout 10s curl http://192.168.0.26:8123 -s -f -o /dev/null || echo "Home Assistant down" | docker restart home-assistant