supervisor: connection refused to hassio

any idea why there is no access to the service from the hassio-CLI?

hassio > ha info
The HTTP request failed with the error: Get http://hassio/homeassistant/info: dial tcp 192.168.1.226:80: getsockopt: connection refused

hassio > ne info
The HTTP request failed with the error: Get http://hassio/network/info: dial tcp 192.168.1.226:80: getsockopt: connection refused

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 2
Comments: 59 (9 by maintainers)

Most upvoted comments

I’m encountering this same issue. I’m unable to ssh into my Raspberry Pi at all, I had to plug it into a monitor and keyboard and access the console directly. Which reminds me, for anyone else that comes along, and is frustrated by the console spam do the following:

Enter root as the login
Press enter a second time to skip the empty password.
login to get access to a shell prompt.
dmesg -n 1 will stop the spam.
exit will put you back into the hassio login.

When I do journalctl -fu hassos-supervisor I get output very similar to @Megachip, but the version is 165 and not 155. That is, hassos-supervisor.service is constantly existing with status=1/FAILURE and restarting.

My /mnt/data/hassos.json is identical to the one posted by @dzerovibe.

All the hassos/hassio commands in the console (like supervisor logs fail with Get http://hassio/supervisor/logs: dial tcp 192.168.1.34:80: connect: connection refused.

date returns the correct date and time.

I’m able to ping IP addresses and domain names, so I’ve got DNS and wireless connectivity.

At this point I have no idea what else to do other than pop in a new microSD card and start over. Open to suggestions!

greygore on Jun 9, 2019

@Fusseldieb I have wrong time on freshly flashed hassio , cca Jan 28 2018 16:00 and there are errors - due to certificate validity - journalctl -fu hassos-supervisor = ... certificate has expired or is not yet valid ... Fails install landingpage, retry after 60sec … . Command date -s "2018-11-18 18:38" solved my problem.

Cooper-Dale on Nov 18, 2018

Forgot to say I’ve been running fine for months and it just stopped working for no discernible reason.

greygore on Jun 9, 2019

😦 i’m not considering move to OpenHAB but …

You’ll probably have other problems with it, I guess. No project is perfect.

I think we should fix this together and stay strong 😃

Fusseldieb on Nov 7, 2019

Same Problem with 0.88.1 docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument")

19-05-13 22:04:49 INFO (MainThread) [__main__] Initialize Hass.io setup
19-05-13 22:04:49 INFO (MainThread) [__main__] Setup HassIO
19-05-13 22:04:49 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to Supervisor homeassistant/armhf-hassio-supervisor with version 155
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 261, in _raise_for_status
    response.raise_for_status()
  File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.39/images/sha256:79ca1e9052ff88c77aed2945128f620e5b436211108cc635b5119b9baf5eb6db/json

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.7/site-packages/hassio/__main__.py", line 45, in <module>
    loop.run_until_complete(coresys.core.setup())
  File "uvloop/loop.pyx", line 1451, in uvloop.loop.Loop.run_until_complete
  File "/usr/local/lib/python3.7/site-packages/hassio/core.py", line 30, in setup
    await self.sys_supervisor.load()
  File "/usr/local/lib/python3.7/site-packages/hassio/supervisor.py", line 42, in load
    await self.instance.cleanup()
  File "/usr/local/lib/python3.7/site-packages/hassio/utils/__init__.py", line 27, in wrap_api
    return await method(api, *args, **kwargs)
  File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.7/site-packages/hassio/docker/interface.py", line 315, in _cleanup
    for image in self.sys_docker.images.list(name=self.image):
  File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 359, in list
    return [self.get(r["Id"]) for r in resp]
  File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 359, in <listcomp>
    return [self.get(r["Id"]) for r in resp]
  File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 316, in get
    return self.prepare_model(self.client.api.inspect_image(name))
  File "/usr/local/lib/python3.7/site-packages/docker/utils/decorators.py", line 19, in wrapped
    return f(self, resource_id, *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/docker/api/image.py", line 245, in inspect_image
    self._get(self._url("/images/{0}/json", image)), True
  File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 267, in _result
    self._raise_for_status(response)
  File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 263, in _raise_for_status
    raise create_api_error_from_http_exception(e)
  File "/usr/local/lib/python3.7/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
    raise cls(e, response=response, explanation=explanation)
docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /mnt/data/docker/overlay2/l: invalid argument")
19-05-13 22:04:50 ERROR (MainThread) [asyncio] Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x752e0df0>
19-05-13 22:04:50 ERROR (MainThread) [asyncio] Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x752e0fd0>

Megachip on May 13, 2019

@loopforever Log in as root (#) and type in “date”. Do you get todays date?

Fusseldieb on Oct 24, 2018

@Fusseldieb I have wrong time on freshly flashed hassio , cca Jan 28 2018 16:00 and there are errors - due to certificate validity - journalctl -fu hassos-supervisor = ... certificate has expired or is not yet valid ... Fails install landingpage, retry after 60sec … . Command date -s "2018-11-18 18:38" solved my problem.

THANK YOU!!! exactly that happened. after setting right time it starts ))))

Partizan7676 on Oct 24, 2019

Hey,

I stuck the sd card in my windows system and whent trough the files and found my samba login and logs. So booted back up and after 10+ reboots i came in with Samba. Fixed my config.yaml and now kicking! Just configured my second Floor with floorplan. Thanks for your help, you are one of the people communities like this need.

Dareno1995 on Mar 19, 2019

There is a fault in my config.yaml file but in hassio-cli i cant use VI or Nano i guess?

In the cli it should work.

If it doesn’t, try to log into the host system using the command login and then when it prompts you username and password, type in root and root. It should then log you in.

When you’re logged in, (I think) because you’re in the host system (and not in the frontend container where your config folders are), you won’t be able to see your files in /config/, but in any other folder. Each container has it’s own folder structure, independent from the others. Try searching for it. I’m not sure if you can search in this minimal linux disto, but try typing find * | grep configuration.yaml in the main folder (/).

Basically in this way (pseudolog, I’m not in front of a RPi nor Linux right now):

hassio-cli> login
username: root
password: root (while typing it won't appear, that's by design, just type it in and press Enter)

#
# cd /
# find * | grep configuration.yaml

/some/folder/configuration.yaml

#
# cd /some/folder/
# vi configuration.yaml

< vi will open >

Fusseldieb on Mar 19, 2019

Can’t get back in over: SSH, Network hassio or frontend after a power outage. Really disappointing when half your house is running Home assistant. HELP!

I’ve identified myself here. Also using Hassio on the entire home and bad things would happen if it stops out of a sudden (Water tanks would not fill anymore, switches would not synchronize anymore, etc). Since I have no problem right now, I’ll try to help you.

So, to your problem… Try to hook a HDMI monitor to your Raspberry Pi and then restart it (In this order!). You should see linux starting up. If you don’t, your SD card is probably corrupted or fried - always make backups via the Web Interface or manually! If you didn’t make a backup, try hooking the card up to a linux computer (or starting a Linux Live USB stick). If it still doesn’t recognize it there, you’re probably out of luck and you’ll need to begin from scratch! Always backup! Two SD cards of mine failed, and once I lost everything! It lasted 6 months. Don’t be the next to suffer. If it still works somehow, immediately save your configs, as it could be the first signs of corruption (if you did nothing wrong with your configs)! With Win32DiskImager you can do a exact backup of your card - byte per byte.

If it boots up, hook up a USB keyboard and then in the console check for every log you can. There should be an error somewhere. Try hassio ha logs, hassio su logs, etc.

Once you’ve found the error, you can try to edit files and things directly from your RPi with the “vi” editor (Look on Google on how to use it, it’s quite unique to use). Change folders with cd - Basic Linux commands. Or you can edit them on your computer. You should use linux for this. If you use windows, try booting a live linux from a USB stick, for that download something like Ubuntu and put it on a USB drive. Google for tutorials. Don’t want to Google? Sigh Okay, here!

Quick crash course on how to use “vi”:

Type “vi [filename]” to start it and open the document
Press <kbd>i</kbd> on your keyboard to enter the Edit/Insert mode
Navigate with your keyboards arrows
Exit edit mode pressing <kbd>ESC</kbd>
Once pressed <kbd>ESC</kbd>, you basically switched to command mode, where you can type in :wq which means write and quit. The command inserted should appear on the bottom left of the screen.
:q means only quit. If you have unsaved changes, you must do :q!. The exclamation is to force something.

Note: Sometimes while editing with “vi” directly on the RPi and having your Ethernet cable plugged in, Hassio will spit out logs in the console which overwrites the vi window and your text becomes quite messy. Don’t panic - it won’t mess up your document, just continue writing as if nothing happened and ignore the mess, or :wq (write & quit) and enter vi again,

Note: Some televisors turn the screen off when the screen is mostly black (which vi is) - cough LG cough . If this happens, open your TV’s menu and let it sit there and it won’t turn off.

All these notes were once sleepless nights. Sharing my experience and tips here…

Sorry for my bad english and I hope I helped something.

Fusseldieb on Mar 18, 2019

@loopforever Hmmm, strange.

Look at running docker container and see what each “status”/log reports.

Some container probably has some error in it and you can see it going through each and look for errors.

Google may help you with the commands to view containers and stuff.

Any help just let me know.

EDIT: Look for the supervisor container first. On mine the error was there (Certificate error downloading stuff due to wrong date - but that’s not your case).

Fusseldieb on Oct 29, 2018

Looks as if the supervisor is running based upon output of journalctl -fu hassos-supervisor but keeps restarting

Sep 10 15:57:15 hassio systemd[1]: hassos-supervisor.service: Service hold-off time over, scheduling restart.
Sep 10 15:57:15 hassio systemd[1]: hassos-supervisor.service: Scheduled restart job, restart counter is at 3.
Sep 10 15:57:15 hassio systemd[1]: Stopped HassOS supervisor.
Sep 10 15:57:15 hassio systemd[1]: Starting HassOS supervisor...
Sep 10 15:57:16 hassio docker[1843]: hassos_supervisor
Sep 10 15:57:16 hassio systemd[1]: Started HassOS supervisor.
Sep 10 15:57:25 hassio hassos-supervisor[1852]: 18-09-10 15:57:25 INFO (MainThread) [__main__] Initialize Hassio setup
Sep 10 15:57:25 hassio hassos-supervisor[1852]: 18-09-10 15:57:25 INFO (MainThread) [__main__] Setup HassIO
Sep 10 15:57:25 hassio hassos-supervisor[1852]: 18-09-10 15:57:25 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to supervisor homeassistant/armhf-hassio-supervisor with version 127
Sep 10 15:57:26 hassio hassos-supervisor[1852]: Traceback (most recent call last):
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 229, in _raise_for_status
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     response.raise_for_status()
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 939, in raise_for_status
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     raise HTTPError(http_error_msg, response=self)
Sep 10 15:57:26 hassio hassos-supervisor[1852]: requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.37/images/sha256:18262da2ab37b7d01b37d2c9a180dadbd9ecbbabc08ac567754efb8bb19e04b7/json
Sep 10 15:57:26 hassio hassos-supervisor[1852]: During handling of the above exception, another exception occurred:
Sep 10 15:57:26 hassio hassos-supervisor[1852]: Traceback (most recent call last):
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     "__main__", mod_spec)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     exec(code, run_globals)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/__main__.py", line 40, in <module>
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     loop.run_until_complete(coresys.core.setup())
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "uvloop/loop.pyx", line 1448, in uvloop.loop.Loop.run_until_complete
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/core.py", line 26, in setup
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     await self.sys_supervisor.load()
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/supervisor.py", line 29, in load
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     await self.instance.cleanup()
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/utils/__init__.py", line 25, in wrap_api
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     return await method(api, *args, **kwargs)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     result = self.fn(*self.args, **self.kwargs)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/docker/interface.py", line 283, in _cleanup
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     for image in self.sys_docker.images.list(name=self.image):
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 338, in list
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     return [self.get(r["Id"]) for r in resp]
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 338, in <listcomp>
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     return [self.get(r["Id"]) for r in resp]
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 295, in get
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     return self.prepare_model(self.client.api.inspect_image(name))
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/utils/decorators.py", line 19, in wrapped
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     return f(self, resource_id, *args, **kwargs)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/image.py", line 245, in inspect_image
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     self._get(self._url("/images/{0}/json", image)), True
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 235, in _result
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     self._raise_for_status(response)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 231, in _raise_for_status
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     raise create_api_error_from_http_exception(e)
Sep 10 15:57:26 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
Sep 10 15:57:26 hassio hassos-supervisor[1852]:     raise cls(e, response=response, explanation=explanation)
Sep 10 15:57:26 hassio hassos-supervisor[1852]: docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /var/lib/docker/overlay2/l: invalid argument")
Sep 10 15:57:26 hassio hassos-supervisor[1852]: 18-09-10 15:57:26 ERROR (MainThread) [asyncio] Unclosed client session
Sep 10 15:57:26 hassio hassos-supervisor[1852]: client_session: <aiohttp.client.ClientSession object at 0x754a25f0>
Sep 10 15:57:26 hassio hassos-supervisor[1852]: 18-09-10 15:57:26 ERROR (MainThread) [asyncio] Unclosed client session
Sep 10 15:57:26 hassio hassos-supervisor[1852]: client_session: <aiohttp.client.ClientSession object at 0x754a2470>
Sep 10 15:57:28 hassio hassos-supervisor[1852]: hassos_supervisor
Sep 10 15:57:37 hassio hassos-supervisor[1852]: 18-09-10 15:57:37 INFO (MainThread) [__main__] Initialize Hassio setup
Sep 10 15:57:37 hassio hassos-supervisor[1852]: 18-09-10 15:57:37 INFO (MainThread) [__main__] Setup HassIO
Sep 10 15:57:37 hassio hassos-supervisor[1852]: 18-09-10 15:57:37 INFO (SyncWorker_0) [hassio.docker.supervisor] Attach to supervisor homeassistant/armhf-hassio-supervisor with version 127
Sep 10 15:57:38 hassio hassos-supervisor[1852]: Traceback (most recent call last):
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 229, in _raise_for_status
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     response.raise_for_status()
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/requests/models.py", line 939, in raise_for_status
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     raise HTTPError(http_error_msg, response=self)
Sep 10 15:57:38 hassio hassos-supervisor[1852]: requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.37/images/sha256:18262da2ab37b7d01b37d2c9a180dadbd9ecbbabc08ac567754efb8bb19e04b7/json
Sep 10 15:57:38 hassio hassos-supervisor[1852]: During handling of the above exception, another exception occurred:
Sep 10 15:57:38 hassio hassos-supervisor[1852]: Traceback (most recent call last):
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/runpy.py", line 193, in _run_module_as_main
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     "__main__", mod_spec)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/runpy.py", line 85, in _run_code
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     exec(code, run_globals)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/__main__.py", line 40, in <module>
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     loop.run_until_complete(coresys.core.setup())
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "uvloop/loop.pyx", line 1448, in uvloop.loop.Loop.run_until_complete
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/core.py", line 26, in setup
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     await self.sys_supervisor.load()
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/supervisor.py", line 29, in load
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     await self.instance.cleanup()
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/utils/__init__.py", line 25, in wrap_api
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     return await method(api, *args, **kwargs)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     result = self.fn(*self.args, **self.kwargs)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/hassio/docker/interface.py", line 283, in _cleanup
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     for image in self.sys_docker.images.list(name=self.image):
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 338, in list
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     return [self.get(r["Id"]) for r in resp]
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 338, in <listcomp>
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     return [self.get(r["Id"]) for r in resp]
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/models/images.py", line 295, in get
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     return self.prepare_model(self.client.api.inspect_image(name))
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/utils/decorators.py", line 19, in wrapped
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     return f(self, resource_id, *args, **kwargs)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/image.py", line 245, in inspect_image
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     self._get(self._url("/images/{0}/json", image)), True
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 235, in _result
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     self._raise_for_status(response)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/api/client.py", line 231, in _raise_for_status
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     raise create_api_error_from_http_exception(e)
Sep 10 15:57:38 hassio hassos-supervisor[1852]:   File "/usr/local/lib/python3.7/site-packages/docker/errors.py", line 31, in create_api_error_from_http_exception
Sep 10 15:57:38 hassio hassos-supervisor[1852]:     raise cls(e, response=response, explanation=explanation)
Sep 10 15:57:38 hassio hassos-supervisor[1852]: docker.errors.APIError: 500 Server Error: Internal Server Error ("readlink /var/lib/docker/overlay2/l: invalid argument")
Sep 10 15:57:39 hassio hassos-supervisor[1852]: 18-09-10 15:57:39 ERROR (MainThread) [asyncio] Unclosed client session
Sep 10 15:57:39 hassio hassos-supervisor[1852]: client_session: <aiohttp.client.ClientSession object at 0x753439b0>
Sep 10 15:57:39 hassio hassos-supervisor[1852]: 18-09-10 15:57:39 ERROR (MainThread) [asyncio] Unclosed client session
Sep 10 15:57:39 hassio hassos-supervisor[1852]: client_session: <aiohttp.client.ClientSession object at 0x75343ad0>
Sep 10 15:57:40 hassio systemd[1]: hassos-supervisor.service: Main process exited, code=exited, status=1/FAILURE

jameswagoner on Sep 10, 2018

journalctl -fu hassos-supervisor

Look like the supervisor is not running. Try to run it manual with: systemctl start hassos-supervisor

pvizeli on Sep 10, 2018

confirm issue. try 32 and 64 bit for Raspberry Pi 3 - several times re-flash/reinstall. each try - connection refuse. first time try to wait more than 4 hours - result same.

Partizan7676 on Aug 30, 2018