Dead in the water post .40 update

Archive All-In-One Installer
1

Updated to .41 via Fabric, and the webserver never comes up after I restart the service (or reboot the raspberry pi). I’m installed via all-in-one on an RPi3. Has anyone else had this issue?

Digging into the logs, I’m seeing tons of components fail with a similar callstack: it can’t find the aiohttp.file_sender module.

Relevant logs below:

Mar 21 03:32:51 gandalf hass[692]: Traceback (most recent call last):
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/loader.py", line 141, in get_component
Mar 21 03:32:51 gandalf hass[692]: module = importlib.import_module(path)
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/importlib/__init__.py", line 109, in import_module
Mar 21 03:32:51 gandalf hass[692]: return _bootstrap._gcd_import(name[level:], package, level)
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 2254, in _gcd_import
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 1129, in _exec
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 1471, in exec_module
Mar 21 03:32:51 gandalf hass[692]: File "<frozen importlib._bootstrap>", line 321, in _call_with_frames_removed
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/history.py", line 20, in <module>
Mar 21 03:32:51 gandalf hass[692]: from homeassistant.components.frontend import register_built_in_panel
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/frontend/__init__.py", line 12, in <module>
Mar 21 03:32:51 gandalf hass[692]: from homeassistant.components import api, group
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/api.py", line 26, in <module>
Mar 21 03:32:51 gandalf hass[692]: from homeassistant.helpers.state import AsyncTrackStates
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/state.py", line 8, in <module>
Mar 21 03:32:51 gandalf hass[692]: from homeassistant.components.media_player import (
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/__init__.py", line 24, in <module>
Mar 21 03:32:51 gandalf hass[692]: from homeassistant.components.http import HomeAssistantView, KEY_AUTHENTICATED
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/http/__init__.py", line 34, in <module>
Mar 21 03:32:51 gandalf hass[692]: from .static import FILE_SENDER, CACHING_FILE_SENDER, staticresource_middleware
Mar 21 03:32:51 gandalf hass[692]: File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/http/static.py", line 6, in <module>
Mar 21 03:32:51 gandalf hass[692]: from aiohttp.file_sender import FileSender
Mar 21 03:32:51 gandalf hass[692]: ImportError: No module named 'aiohttp.file_sender'
2

I’d like to know what’s going on as well. Had to do a fresh install on hassbian and nothing works… everything fails… pretty much the same errors as you along with

unable to find component xxxxxxxxx
3

There’s a bug report open for the errors about aiohttp. It looks like there’s a number of people with the same problem.

4

Same here! I’m lost! Spent the last few hours trying not to have to do a fresh install. This is the second upgrade that has hosed my setup and is making me gun shy about ever attempting upgrades. first was trying to go from 37.1 to 39+, this was from 39.3 to 40.1 AIO install. same errors about unable to find components, nothing works.
In the middle of typing this I got mine up and running. I ended up running an uninstall ‘pip3 uninstall homeassistant’
and install ‘pip3 install --upgrade homeassistant’… it took a few tries (and probably did it wrong once or twice) and checking over logs etc… etc… , but I got mine back up and running. A few errors in the logs still, but got rid of the big ones that kept me from launching hass. Only took a few too many hours…

nevermind, same issue as others. issue returns after restart

5

Good to know that I’m not alone at least… Life without my home-assistant is lonely and sad. :frowning:

6

Although I have not experienced a serious meltdown yet I have taken another pi and configured it almost the same (except with the Z wave stuff for the Aeotec stick). Before I upgrade I test it on the non used system first. If it works then I apply it to the deployed Pi. And in the event of a meltdown on the working system all I need to do is add z-wave configuration to my configuration.yaml and put the stick in.

7

I think I have the same problem, unfortunately I opened another thread before reading this one :flushed:

https://community.home-assistant.io/t/various-errors-after-upgrade-from-0-39-to-0-40-1

As posted in the bug report thread doing this in virtualenv solved it also for me so far:
pip install --upgrade aiohttp==1.3.3 -t ~/.homeassistant/deps/

1 Like
8

I had the same errors after upgrade via apt-get update.
I was able to correct by performing upgrade in the virtual environment via the following steps:

$ sudo systemctl stop [email protected]
$ sudo su -s /bin/bash homeassistant
$ source /srv/homeassistant/bin/activate
$ pip3 install --upgrade homeassistant
$ exit
$ sudo systemctl start [email protected]