[Config Support]: Frigate exited with code 256 (by signal 4)

[Robert0309]

Describe the problem you are having

sorry if this is a duplicate but I coughed not find a discussion on this.
I am new to Frigate and plan on migrating from motioneye.
I can't figure out why it stops and what "by signal 4" is.
any help would be greatly be appreciated.

Version

0.13.2

Frigate config file

go2rtc:
  streams:
    back:
      # - rtsp:https://user:[email protected]:554/cam/realmonitor?channel=1&subtype=2
      - rtsp:https://ha:[email protected]:554/

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 fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service s6rc-fdholder successfully started
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 go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service nginx-log successfully started
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
2024-04-23 11:16:28.154817292  [INFO] Preparing Frigate...
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2024-04-23 11:16:28.168322225  [INFO] Preparing new go2rtc config...
2024-04-23 11:16:28.169361833  [INFO] Starting NGINX...
2024-04-23 11:16:28.192199819  [INFO] Starting Frigate...
s6-rc: info: service legacy-services successfully started
2024-04-23 11:16:28.332485164  [INFO] Got IP address from supervisor: 192.168.0.132
2024-04-23 11:16:28.506455793  [INFO] Got WebRTC port from supervisor: 8555
2024-04-23 11:16:29.384555504  [INFO] Starting go2rtc...
2024-04-23 11:16:29.503325487  13:16:29.501 INF go2rtc version 1.8.4 linux/amd64
2024-04-23 11:16:29.503977255  13:16:29.503 INF [rtsp] listen addr=:8554
2024-04-23 11:16:29.504417825  13:16:29.504 INF [webrtc] listen addr=:8555
2024-04-23 11:16:29.515607587  13:16:29.514 INF [api] listen addr=:1984
2024-04-23 11:16:31.331087137  [INFO] Service Frigate exited with code 256 (by signal 4)
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
2024-04-23 11:16:31.365324815  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-04-23 11:16:31.394448923  [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 go2rtc-healthcheck successfully stopped
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2024-04-23 11:16:31.500013105  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
2024-04-23 11:16:31.690815603  [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 frigate-log successfully stopped
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

Frigate stats

No response

Operating system

HassOS

Install method

HassOS Addon

Coral version

CPU (no coral)

Any other information that may be helpful

No response

[NickM-27]

Your config file is not valid

[Robert0309]

I have tried it with:

mqtt:
  enabled: False

cameras:
  dummy_camera: # <--- this will be changed to your actual camera later
    enabled: False
    ffmpeg:
      inputs:
        - path: rtsp:https://127.0.0.1:554/rtsp
          roles:
            - detect

and the same thing with my mqtt enabled but it still ends with: Service Frigate exited with code 256 (by signal 4)

[Robert0309]

Never mind I shoed have been using Frigate (For old x86_64 CPU without AVX)