[Support]: Frigate Docker Container Exits suddenly on Clean Install #13865
Replies: 1 comment 14 replies
-
|
we need to see the frigate volumes, most likely something is wrong there. |
Beta Was this translation helpful? Give feedback.
-
Is it possible it is failing because it can not communicate between the s6 services somehow? How does it do it, localhost/127.0.0.1:port? Could IPv6 be the problem maybe? |
Beta Was this translation helpful? Give feedback.
-
|
If I had to guess it's because you have no config file so the go2rtc startup script is failing because it can't parse a config. I've not seen this type of issue in a long time S6 does not communicate it's just a runner which naturally knows when its child processes stop |
Beta Was this translation helpful? Give feedback.
-
I creates the config (and all the rest of the files/folders) on first run, as can be seen from the logs. On second run I can see it has the config there (part of second run log below). The thing is that I am running this on Triton datacenter, which is actually running docker containers in their own zones, each is self contained and has its own network,storage etc... It should not matter, but frigate might need something specific which is not there. All the other containers run normally (passbolt, zulip, haproxy, even immich). |
Beta Was this translation helpful? Give feedback.
-
|
right, on the first run the config file doesn't exist yet so go2rtc can't parse from it. it appears this is the first sign of something stopping, seems somewhere it must be getting a signal to stop, but doesn't make sense from where |
Beta Was this translation helpful? Give feedback.
-
|
How can this be found? Any suggestions? Its interesting that it does not say in the logs anything from where this signal to stop comes. Everything in frigate runs as root, right? |
Beta Was this translation helpful? Give feedback.
-
Checklist
Describe the problem you are having
I performed a clean installation of Frigate (version 0.14.1) using Docker. Shortly after starting, the Frigate container exits unexpectedly with a list index out of range error. This happens even with a minimal configuration.
Environment:
Frigate Version: 0.14.1
Installation Type: Docker
OS: Triton SDC Cloud (Docker environment similar to standard Docker)
Hardware: Cloud-based infrastructure
Steps to reproduce
...
Version
0.14.1
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Other Linux
Install method
Docker Compose
Network connection
Wired
Camera make and model
not used
Screenshots of the Frigate UI's System metrics pages
Does not even start, so no screenshost possible.
Any other information that may be helpful
Are there any additional debugging steps I can take to pinpoint the cause of this error?
This issue occurs on a clean installation with no previous data or configurations present.
Increased the logging level to debug to capture more detailed logs, but logs are always the same.
Beta Was this translation helpful? Give feedback.
All reactions