[Support]: <defunct> ffmpeg processes when camera is offline #19126
Replies: 1 comment 2 replies
-
that would be a system or docker issue then, if that is the case, as Frigate would have no control over that. |
Beta Was this translation helpful? Give feedback.
-
|
Aren't ffmpeg processes spawned by frigate? My understanding of zombie process are caused by the parent (some frigate woker) not collecting child's termination. For long-duration ffmpeg tasks, the parent could use signal handling to be notified of these events. |
Beta Was this translation helpful? Give feedback.
-
|
as soon as Frigate docker container is stopped, if ffmpeg processes that belong to Frigate are still running then that is a failure on the system or docker, as it is impossible for a process that belongs to a docker container to continue to exist after the docker container itself is stopped. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
After a camera went offline, the system start having defunct ffmpeg processes. Restarting the frigate docker container doesn't clean up these zombies.
Steps to reproduce
...
Version
0.15.0-6cb5cfb
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
N/Adocker-compose file or Docker CLI command
N/ARelevant Frigate log output
Relevant go2rtc log output
Operating system
UNRAID
Install method
Docker CLI
Network connection
Wired
Camera make and model
tp-link
Screenshots of the Frigate UI's System metrics pages
N/A
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions