Docker Crashing

Installation
1

I am running home-assistant in an unraid docker. Last couple of days I come home to find none of my automations have triggered for lighting. I in turn find that the docker isn’t running. The last line of the docker log says:

Assertion failed: loop->watchers[w->fd] == w (src/unix/core.c: uv__io_stop: 932)

Attached are the home-assistant.log and docker log. If anyone could help I would greatly appreciate it. The big change 2 days ago was adding camera streams.

home-assistant.log: https://pastebin.com/embed_js/fLrh0fVV
docker log: https://pastebin.com/embed_js/d6zb27SP

Thanks,

J

2

You have some errors in your lovelace. yaml. It’s in you HA log. Fix that first.
then it looks like you have an issue with your unifi integration. Try dissabling it and see if you get HA running.

3

Took care of the duplicate lovelace syntax errors and disabled the custom component. As I suspected neither of those were the culprit. Still getting an assertion failed

Assertion failed: loop->watchers[w->fd] == w (src/unix/core.c: uv__io_stop: 932)

I also have a bunch of ISY warnings that I never had:

2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: MBRKPL, type: 1.66.68.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: HBRMotionSensor.Motion, type: 16.22.70.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: LRKPL, type: 1.66.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FrontDoorSensorState, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FrontDoorSensorLowBat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FrontDoorSensorHeartbeat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: GIRLSBRKPL, type: 1.66.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FoyerDoorSensorState, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FoyerDoorSensorLowBat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: FoyerDoorSensorHeartbeat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: PatioDoorSensorState, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: PatioDoorSensorLowBat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: PatioDoorSensorHeartbeat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: WalkOutDoorSensorState, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: WalkOutDoorSensorLowBat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: WalkOutDoorSensorHeartBeat, type: 16.17.69.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: BasementFloorDrain-Dry, type: 16.8.68.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: BasementFloorDrain-Wet, type: 16.8.68.0
2019-12-03 18:40:56 WARNING (SyncWorker_33) [homeassistant.components.isy994] Unsupported node: BasementFloorDrain-Heartbeat, type: 16.8.68.0

The other change that I mad was put camera feeds from 3 outdoor cameras running live. Would this cause any issues that could lead to this assertion error?

4

This has been raised before but closed Random Docker Container Restarts. · Issue #20829 · home-assistant/core · GitHub

5

I can just about confirm that it was the camera feeds that I added. They are ffmpeg/onvif feeds. I disabled them and their corresponding lovelace page and I have had a crash yet.

6

After 5 days of having the onvif cams taken out of my config, I haven’t experienced a single crash. Now to figure out why the cameras kill me.

7

I’m having the same issue, but i don’t see removing the cameras as a solution personally.

8

Sorry to hear you are having the same issues. In my case it was, it was the single biggest addition that I had made. I haven’t had any issues with docker to date except for this camera integration.