core: Extremely slow to restart by clicking Restart in the interface

The problem

Now when I select Restart under config the server goes offline and never comes back … when I restart the container it all works without issue… There are no errors in the log as such … I have placed the docker console output in the Traceback

Environment

Home Assistant release with the issue: 0.105.2 (I skipped the previous 105 versions … but I am guessing it started with the safe mode)
Last working Home Assistant release (if known): 0.104.3
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Integration causing this issue: Core?
Link to integration documentation on our website: N/A

Problem-relevant `configuration.yaml`

N/A

Traceback/Error logs

Docker console output is below after the restart button is clicked:

2020-02-07 18:58:57 WARNING (MainThread) [homeassistant.components.device_tracker] The 'hide_if_away' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-02-07 18:58:57 WARNING (MainThread) [homeassistant.components.device_tracker] The 'hide_if_away' option (with value 'False') is deprecated, please remove it from your configuration. This option will become invalid in version 0.107.0
2020-02-07 18:58:57 INFO (SyncWorker_24) [homeassistant.loader] Loaded homekit from homeassistant.components.homekit
2020-02-07 18:58:57 INFO (MainThread) [homeassistant.components.stream] Stopped stream workers.
2020-02-07 18:58:57 INFO (SyncWorker_13) [homeassistant.components.xiaomi_aqara] Shutting down Xiaomi Hub
2020-02-07 18:58:57 INFO (SyncWorker_13) [xiaomi_gateway] Closing multisocket
2020-02-07 18:58:57 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.140011379229200] Connection closed by client
2020-02-07 18:58:57 INFO (MainThread) [homeassistant.components.websocket_api.http.connection.140011379567120] Connection closed by client
2020-02-07 18:58:57 INFO (Thread-7) [pychromecast.socket_client] [Kitchen display:8009] Stopped while reading message, disconnecting.

Additional information

Config validates … and like I said, if I reboot the docker container all works well again.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 1
Comments: 18 (9 by maintainers)

Most upvoted comments

Running RPI 3 Model B+ with Home Assistant (formerly Hass.IO). Have had very stable Home Assistant experiences up to 0.104.3

When upgrading to 0.105.x I started getting roll-backs, with the upgrade failing to upgrade from 0.104.3 to 0.105.x At first I thought it may had to do with my config, so I removed the netatmo integration from the config file because others were reporting success with that. No luck. Then I decided to start a fresh installation with a new SD card and clean hassos 3.10 install. Added only the deconz add-on and restored from backup, then did a reboot to get all the lights from DeConz into Home Assistant. This took much longer than I was used with prior to 0.105.x. The logs reported about 940 seconds of boot time for HA Core.

When doing the HA (Hass.IO) upgrade from 0.104.3 to 0.105.x I noticed that the logs were indicating a timeout and that it did not want to wait longer and was therefor falling back to the 0.104.3 install. Other in the forum were reporting the same thing, these are logs I just copied from the forum: 20-02-06 14:11:25 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation in progress 20-02-06 14:14:35 INFO (MainThread) [hassio.homeassistant] Home Assistant pip installation done 20-02-06 14:24:39 WARNING (MainThread) [hassio.homeassistant] Don’t wait anymore of Home Assistant startup! 20-02-06 14:24:39 CRITICAL (MainThread) [hassio.homeassistant] HomeAssistant update fails -> rollback!

Notice that the timeout occurs after about 10 minutes.

Then look at the logs from my reboot of the clean 0.105.4 installation with only DeConz, SSH and Configuratorenator running:

[…] 2020-02-18 20:09:02 INFO (MainThread) [homeassistant.setup] Setup of domain default_config took 0.6 seconds. 2020-02-18 20:09:02 INFO (MainThread) [homeassistant.setup] Setup of domain hassio took 2.1 seconds. 2020-02-18 20:09:02 INFO (SyncWorker_15) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate 2020-02-18 20:09:03 INFO (MainThread) [homeassistant.setup] Setting up tts 2020-02-18 20:09:03 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.1 seconds. 2020-02-18 20:24:26 INFO (MainThread) [homeassistant.components.cloud.account_link] Timeout fetching tokens for flow a8097fb3fb2647a19456b570d8258b31 2020-02-18 20:24:26 INFO (MainThread) [homeassistant.components.cloud.account_link] Timeout fetching tokens for flow 2ebd84ef805841b48e848907ba8f2c97 2020-02-18 20:24:26 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 945.19s 2020-02-18 20:24:26 INFO (MainThread) [homeassistant.core] Starting Home Assistant 2020-02-18 20:24:26 INFO (SyncWorker_17) [homeassistant.components.zeroconf] Starting Zeroconf broadcast 2020-02-18 20:24:26 INFO (MainThread) [homeassistant.core] Timer:starting 2020-02-18 20:24:26 INFO (SyncWorker_3) [homeassistant.loader] Loaded deconz from homeassistant.components.deconz 2020-02-18 20:24:29 INFO (SyncWorker_0) [homeassistant.loader] Loaded plaato from homeassistant.components.plaato 2020-02-18 20:24:29 INFO (SyncWorker_14) [homeassistant.loader] Loaded mqtt from homeassistant.components.mqtt

I am suspecting that there is a 15 minute timeout occuring against the cloud component (which hasn’t been configured yet in my near clean installation) while the HA upgrade stops after 10 minutes.

Is there a possibility that these are interconnected and the one issue is causing the next? Should I wait for a resolution of this slow restart or start from a clean install?

Looking forward to your thoughts. Kind regards, Mats

mvoort1337 on Feb 18, 2020

I have noticed my instance takes way longer to test config and restart. I can click restart and want the the pop-up of it being offline till over a minute after on 104. It was instantaneous.

jes1417 on Feb 7, 2020

updating to supervisor 200 made it behave again on this side

Mariusthvdb on Feb 13, 2020

Might be that it is the config check which is taking extremely long.

When clicking that in the Ha interface it never seems to finish.

Hence causing restart to take forever, since that first does a config check

When using ssh Hassio Ha check it is as swift as before. Never sure if it is as safe but it works at least

Mariusthvdb on Feb 11, 2020

Same here. Before, the check config took 5-8 minutes as where to before it was done within 1 minute. And also when rebooting. The device only reboots after a few minutes of waiting. The actual boot time is equal between 0.104x and 0.105.x

This happened after installing 105.x. Running 0.105.2 atm.

How can i measure what it causing this delay? As there’s no error… but for some reason needs so much more time to proces certain stuff. I went back to 104.x just to test and it was fast again. Upon upgrading again, same slow experience as before

Tosko4 on Feb 9, 2020