-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Support]: Service Frigate exited with code 256 (by signal 9) #7474
Comments
what exactly are the contents of the config file? only a few users have seen this and it was unrelated to frigate itself https://github.com/search?q=repo%3Ablakeblackshear%2Ffrigate+%22%28by+signal+9%29%22&type=issues |
Hey @NickM-27 cheers for taking a look, the config file is in the ticket above but for ease I've copied it here
|
right, just wanted to confirm. That is not valid yaml, |
@NickM-27 it's the name of the file. As mentioned, it's a kubernetes deployment, I left the name of the file in for clarity. |
@NickM-27 We got it! Your pointers got me in the right direction - I assume from a little python googling and the other issues on here code 256 is something to do with memory limitations. The issue is with the helm chart though so ill take it back over there. |
Describe the problem you are having
Unfortunatly im struggling to even get anything to debug.
The first item that appears to be going wrong is the log item 'Service Frigate exited with code 256 (by signal 9)' for which I cant find anything to help me figure out.
Any pointers to how to debug further or a solution would be amazing.
Version
0.12.1
Frigate config file
Relevant log output
s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting 2023-08-14 15:50:24.603040432 [INFO] Starting go2rtc... s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting 2023-08-14 15:50:24.608159821 [INFO] Starting Frigate... 2023-08-14 15:50:24.610728236 [INFO] Starting NGINX... s6-rc: info: service legacy-services successfully started 2023-08-14 15:50:24.873685862 15:50:24.873 INF go2rtc version 1.2.0 linux/amd64 2023-08-14 15:50:24.874433659 15:50:24.874 INF [api] listen addr=:1984 2023-08-14 15:50:24.875108327 15:50:24.875 INF [rtsp] listen addr=:8554 2023-08-14 15:50:24.875652916 15:50:24.875 INF [srtp] listen addr=:8443 2023-08-14 15:50:24.876464665 15:50:24.876 INF [webrtc] listen addr=:8555 2023-08-14 15:50:28.021094442 [INFO] Service Frigate exited with code 256 (by signal 9) s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping 2023-08-14 15:50:28.057922106 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) s6-rc: info: service go2rtc-healthcheck successfully stopped 2023-08-14 15:50:28.174666175 [INFO] Service NGINX exited with code 0 (by signal 0) s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped 2023-08-14 15:50:28.184357729 exit OK s6-rc: info: service frigate-log successfully stopped 2023-08-14 15:50:28.196047844 [INFO] The go2rtc service exited with code 0 (by signal 0) s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped
FFprobe output from your camera
Frigate stats
N/A
Operating system
Debian
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wired
Camera make and model
Reolink Video Doorbell POE
Any other information that may be helpful
Install method is Kubernetes following the recommended chart https://github.com/blakeblackshear/blakeshome-charts
The text was updated successfully, but these errors were encountered: