Awoke to a sea of red :: Supportability

[gniknalu]

I've let the dev docker container run since starting it yesterday morning. When I awoke this morning, there was a sea of red ERRORS in the log. Here is a snipit:

[2021-06-12 02:01:16] [ERROR   ] [viseron.camera.stream.backeast] - rtsp://*****:*****@xxx.xxx.xxx.xxx:554/*******************: No route to host
[2021-06-12 02:01:16] [ERROR   ] [viseron.camera.backeast ] - FFmpeg process has exited
[2021-06-12 02:01:17] [ERROR   ] [viseron.camera.frontwest] - Restarting frame pipe
[2021-06-12 02:01:18] [ERROR   ] [viseron.camera.stream.fronteast] - [tcp @ 0x55c026e04f80] Connection to tcp://xxx.xxx.xxx.xxx:554?timeout=5000000 failed: No route to host
[2021-06-12 02:01:18] [ERROR   ] [viseron.camera.stream.fronteast] - rtsp://*****:*****@xxx.xxx.xxx.xxx:554*********: No route to host
[2021-06-12 02:01:18] [ERROR   ] [viseron.camera.fronteast] - FFmpeg process has exited
[2021-06-12 02:01:21] [ERROR   ] [viseron.camera.backeast ] - Restarting frame pipe

Find it odd that all the camera's say "No route to host" as the cameras were reachable. But I couldn't scroll up to the actual cause.

Suggestion: Is there a way to send an alert on fatal errors like this via MQTT so you can generate a notification in Home Assistant?

[roflcoopter]

Never seen this before, but it seems like a networking error rather than something caused by Viseron or FFmpeg.

There is a status sensor already in Home Assistant that shows scanning_for_objects, recording etc. It is on my to do list to add an availability status aswell

[gniknalu]

Never seen this before, but it seems like a networking error rather than something caused by Viseron or FFmpeg.

There are other apps that run on the same box and they were running fine. I think something related to the container ran into issues. When you looked at the videos in Home Assistant, they still showed detection but the log showed something different.

Thank you for any supportability updates that you make!