[HW Accel Support]: FFMPEG crashing after working for some time #17693
Unanswered
vmattphillips
asked this question in
Hardware Acceleration Support
Replies: 3 comments 10 replies
-
new log errors when i run it again without changing anything |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
The connection to the camera is being lost.
Is this a wifi camera? |
Beta Was this translation helpful? Give feedback.
10 replies
-
|
are there downsides to forcing frigate to use UDP with the input arg preset-rtsp-udp? Otherwise this just seems like a more stable connection? |
Beta Was this translation helpful? Give feedback.
-
|
Well, you need to make sure the camera actually outputs UDP. I'm not sure if Tapo does this. I'd recommend trying go2rtc first before going down the UDP route. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'll try setup go2rtc first |
Beta Was this translation helpful? Give feedback.
-
|
This seems better as in, it still cuts out, but noticably more uptime and seems to resolve itself once connection is restored, rather than ffmpeg crashing and the camera remaining offline until I restart the container. I assume my only real fix is to find a way to run poe to the camera |
Beta Was this translation helpful? Give feedback.
-
|
Great, glad to hear it's working better with go2rtc. PoE/wired cameras will definitely be more stable in the long-term. I have several and they are rock solid. My only wifi camera (a doorbell) is the one that drops its connection a couple of times per day. |
Beta Was this translation helpful? Give feedback.
-
|
I've been getting very similar errors with my Reolink RLC520a Cams and Reolink Doorbells, though I probably have a very different setup running Frigate 0.15.1 with Go2RTC V1.9.9 in a Proxmox VE LXC Container alongside HA running in a VM on a Dell Optiplex 3070 with 2 SSDs (one for VMs/LXCs the other for Frigate NVR storage) with a PCI Coral Edge TPU. I'm planning on raising a Discussion/Issue of my own once I gather everything together, but I have a very simple suggestion to try based on my own experiences. Can I suggest you try setting the following logging in your config.yaml file, as when I do this, the errors seem to completely stop, even when running for several days. When I remove the logging the errors seem to come back. It would be interesting to see if the same happens for you. logger: EDIT: Scrub that. The errors are still occurring, even with debugging on. More investigation required I think! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I setup a Frigate docker container with 1 camera, and it was working fine for almost an entire day, and when i check it the next morning, i see the FFMPEG process crashed, I reset the container, and within an hour or so the FFMPEG has crashed again, I honestly have no idea what to do first to debug the ffmpeg issue.
Version
0.15.0-cea210d
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
unsure how exactly to do thisInstall method
Docker Compose
Object Detector
TensorRT
Network connection
Wireless
Camera make and model
Tapo C310
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions