Iām having the same issue.
HassOS v. 3.11
Has anyone found a solution?
_ml
March 10, 2020, 1:42pm
23
Potentially the cause of thisā¦ I rebooted my hassio VM last night, and docker couldnāt start the supervisor afterward. Eventually found this:
opened 03:39PM - 03 Mar 20 UTC
closed 05:48PM - 03 Mar 20 UTC
**Operating environment (HassOS/Generic):**
<!--
Please provide details about ā¦ your environment.
-->
Ubuntu 18.04 Supervisor 207
**Supervisor logs:**
<!--
- Frontend -> Hass.io -> System
- Or use this command: hassio su logs
-->
Mar 03 15:30:58 hassio hassio-supervisor[7786]: raise EnvironmentError('Could not create udev monitor')
Mar 03 15:30:58 hassio hassio-supervisor[7786]: OSError: Could not create udev monitor
Mar 03 15:30:58 hassio hassio-supervisor[7786]: 20-03-03 15:30:58 ERROR (MainThread) [asyncio] Unclosed client session
Mar 03 15:30:58 hassio hassio-supervisor[7786]: client_session: <aiohttp.client.ClientSession object at 0x7f3e87052bd0>
Mar 03 15:30:58 hassio hassio-supervisor[7786]: 20-03-03 15:30:58 ERROR (MainThread) [asyncio] Unclosed client session
Mar 03 15:30:58 hassio hassio-supervisor[7786]: client_session: <aiohttp.client.ClientSession object at 0x7f3e86e16150>
Mar 03 15:30:58 hassio hassio-supervisor[7786]: [cont-finish.d] executing container finish scripts...
Mar 03 15:30:58 hassio hassio-supervisor[7786]: [cont-finish.d] done.
Mar 03 15:30:58 hassio hassio-supervisor[7786]: [s6-finish] waiting for services.
Mar 03 15:30:58 hassio hassio-supervisor[7786]: [s6-finish] sending all processes the TERM signal.
**Description of problem:**
Supervisor doesn't start, see log above.
Just updated the supervisor to 207 via frontend, now it logs the `Could not create udev monitor` error
The bit from @frenck : āyour instance would have thrown warnings for that same time as wellā made me think of the āSupervisor does not run in Privileged modeā warnings that I couldnāt find an answer for and so ignored (
Running the install instructions from our website again will fix this issue.
Installation - Home Assistant
Running the installer again, preserves data.
), but the resolution to that will probably resolve this issue too: