I’ve used home assistant for about 6 months, but moved to hassio somewhat recently (inside a pi4). I just updated to 103, but my instance is no longer accessible. I stopped all of my addon containers, thinking something in there was causing a problem.
I can ssh to my pi without a problem. I restarted the hassio container, but I still can’t access the web interface. What can I do to troubleshoot this?
Look at the error information in the logs.
My syslog of the pi? Not much in there related to HA that seems to show an error…
Dec 12 02:12:39 rpi04 hassio-supervisor[15548]: #033[32m19-12-12 02:12:39 INFO (MainThread) [hassio.host.services] Update service information#033[0m
Dec 12 02:12:39 rpi04 hassio-supervisor[15548]: #033[32m19-12-12 02:12:39 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1#033[0m
Dec 12 02:15:15 rpi04 systemd[14233]: run-docker-runtime\x2drunc-moby-9e6304fa3b68295181ed57e50e9ded7312f914a9fff7740b0f84d1f6e1af0dc7-runc.oTpfpk.mount: Succeeded.
Dec 12 02:15:15 rpi04 systemd[1]: run-docker-runtime\x2drunc-moby-9e6304fa3b68295181ed57e50e9ded7312f914a9fff7740b0f84d1f6e1af0dc7-runc.oTpfpk.mount: Succeeded.
home-assistant.log
The homeassistant container is up, and I can access it:
root@rpi04:/home/pi# docker exec -it homeassistant /bin/bash
bash-5.0# top
Mem: 1603736K used, 382288K free, 81308K shrd, 151516K buff, 939336K cached
CPU: 0% usr 0% sys 0% nic 99% idle 0% io 0% irq 0% sirq
Load average: 1.22 2.65 6.02 4/381 155
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
6 1 root S 163m 8% 2 1% /usr/local/bin/python3 -m homeassistant --config /config
8 1 root S 2256 0% 1 0% udevd --daemon
150 0 root S 1820 0% 3 0% /bin/bash
155 150 root R 1272 0% 3 0% top
1 0 root S 716 0% 1 0% /sbin/docker-init -- /bin/entry.sh python3 -m homeassistant --config /config
I have some errors in that log file (mostly related to addons I stopped). I’ll start those up and take a new look.
One of my errors was about wake_on_lan. A change I saw in the 103 change log, but then forgot to update in my configuration.yaml. I made that change (mac_address to mac) and restarted the homeassistant docker.
I’m still not getting the front end up, but the log files seem to just have errors saying that something can’t communicate with homeassistant. I’m confused by the vesync error (because I commented those lines out of my config file to take that out of account:
2019-12-11 18:29:44 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for vesync which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-12-11 18:29:48 ERROR (MainThread) [homeassistant.setup] Error during setup of component vesync
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 176, in _async_setup_component
component.setup, hass, processed_config # type: ignore
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/vesync/__init__.py", line 26, in setup
conf = config[DOMAIN]
KeyError: 'vesync'
2019-12-11 18:30:15 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 84, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 74, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 387, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.7/http/client.py", line 1252, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1298, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1247, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1026, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 184, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 169, in _new_conn
self, "Failed to establish a new connection: %s" % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0xabc45d10>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.2.14', port=8060): Max retries exceeded with url: /query/device-info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xabc45d10>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/roku/__init__.py", line 52, in roku_discovered
_setup_roku(hass, config, {CONF_HOST: info["host"]})
File "/usr/src/homeassistant/homeassistant/components/roku/__init__.py", line 104, in _setup_roku
r_info = roku.device_info
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 258, in device_info
resp = self._get('/query/device-info')
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 207, in _get
return self._call('GET', path, *args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 224, in _call
resp = func(url, timeout=self.timeout, *args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 546, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.2.14', port=8060): Max retries exceeded with url: /query/device-info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xabc45d10>: Failed to establish a new connection: [Errno 111] Connection refused'))
2019-12-11 18:30:15 ERROR (MainThread) [homeassistant.core] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 84, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 74, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen
chunked=chunked,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 387, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.7/http/client.py", line 1252, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1298, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1247, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1026, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 184, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 169, in _new_conn
self, "Failed to establish a new connection: %s" % e
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0xabc45f30>: Failed to establish a new connection: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
timeout=timeout
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.2.14', port=8060): Max retries exceeded with url: /query/device-info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xabc45f30>: Failed to establish a new connection: [Errno 111] Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/roku/__init__.py", line 52, in roku_discovered
_setup_roku(hass, config, {CONF_HOST: info["host"]})
File "/usr/src/homeassistant/homeassistant/components/roku/__init__.py", line 104, in _setup_roku
r_info = roku.device_info
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 258, in device_info
resp = self._get('/query/device-info')
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 207, in _get
return self._call('GET', path, *args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/roku/core.py", line 224, in _call
resp = func(url, timeout=self.timeout, *args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 546, in get
return self.request('GET', url, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='192.168.2.14', port=8060): Max retries exceeded with url: /query/device-info (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0xabc45f30>: Failed to establish a new connection: [Errno 111] Connection refused'))
Well what the… I opened it in a new private tab in Safari and it worked, so I restarted Safari and now I can reach the lovelace frontend. I guess it was a cache issue within the browser.
Not a cache issue for me. Didn’t load on any of my devices and it reverted to.102.3
If you can connect to hassio via SSH, try to run
hassio homeassistant info
and
hassio homeassistant logs
What do you see there?
See nothing in the logs. After an long time it reboots to .102.3.
Same issue here. Lovelace is unnaccessible after updating to 0.103
What do your logs say??
Nothing obvious in log. What should I look for?
Before upgrade I completeley reinstalled hassio (in order to fix audio issue), then full restored my latest backup abd then deleted homeassistand db file (there were sensors errors after restore)
And after that i’ve upgraded to 103…
I don’t know, maybe you can try removing db file first, and if it won’t help just reinstall hassio
The only thing I’ve lost is my historical data. All customizations and configurations are in place
Errors?
You’re looking at the log file? There should be errors if the GUI is inaccessible, otherwise have you verified it’s not just a cache issue on your browser?
Tried it on 4 devices and cleared cache on all. Only saw some components taking too long to load errors. I see this from time to time. I just ran the check configuration integration and it di not like wemo. I have removed it as it has never worked correctly for me. I’ll try again. How is the GUI (Lovelace) addressed in the log?
I renamed db and it rebuilt file, but did not load Lovelace.
Ok I have tried to remove every integration sending error messages but I still get a stuck Homeassistant and an unresponsive lovelace page.
Here are some information.
-I am runnning a docker based installation. It has been running perfectly and upgrading on every new versions perfectly fine for a full year now. It is the first time I have an issue after an upgrade.
-Confirmed that reverting to 102.3 restores the service immediately
-Looking at the homeassistant.log file I see that it stops updating after a few seconds after starting the container
-I have removed every integration that would log an error such as camera, custom_updater, custom components.
-I have renamed my event db which get recreated fine
-I have no logs whatsoever of what could cause the container to hang the way it does.
Do you have api_password: set anywhere?