Frigate NVR will not start after even if its fresh installed

Apps and Virtualization
, ,
1

Hi.

Try to install Frigate NVR from the app section.
Filled in the necessary, in the dashboard its stuck at “deployment”
In the logs its say that the config is wrong, but this is fresh install. Also tried to use config from another frigate running on truenas scale without any problems. But still the same problem. Any Idea how to resolve this?

2024-11-10 18:50:03.701524+00:00s6-rc: info: service s6rc-fdholder: starting
2024-11-10 18:50:03.701694+00:00s6-rc: info: service s6rc-oneshot-runner: starting
2024-11-10 18:50:03.705106+00:00s6-rc: info: service s6rc-oneshot-runner successfully started
2024-11-10 18:50:03.705416+00:00s6-rc: info: service fix-attrs: starting
2024-11-10 18:50:03.706536+00:00s6-rc: info: service s6rc-fdholder successfully started
2024-11-10 18:50:03.712149+00:00s6-rc: info: service fix-attrs successfully started
2024-11-10 18:50:03.712442+00:00s6-rc: info: service legacy-cont-init: starting
2024-11-10 18:50:03.720888+00:00s6-rc: info: service legacy-cont-init successfully started
2024-11-10 18:50:03.721164+00:00s6-rc: info: service log-prepare: starting
2024-11-10 18:50:03.734189+00:00s6-rc: info: service log-prepare successfully started
2024-11-10 18:50:03.734480+00:00s6-rc: info: service nginx-log: starting
2024-11-10 18:50:03.734958+00:00s6-rc: info: service go2rtc-log: starting
2024-11-10 18:50:03.735391+00:00s6-rc: info: service frigate-log: starting
2024-11-10 18:50:03.735704+00:00s6-rc: info: service certsync-log: starting
2024-11-10 18:50:03.737797+00:00s6-rc: info: service nginx-log successfully started
2024-11-10 18:50:03.737986+00:00s6-rc: info: service go2rtc-log successfully started
2024-11-10 18:50:03.738163+00:00s6-rc: info: service go2rtc: starting
2024-11-10 18:50:03.738397+00:00s6-rc: info: service frigate-log successfully started
2024-11-10 18:50:03.738656+00:00s6-rc: info: service certsync-log successfully started
2024-11-10 18:50:03.740811+00:00s6-rc: info: service go2rtc successfully started
2024-11-10 18:50:03.740956+00:00s6-rc: info: service go2rtc-healthcheck: starting
2024-11-10 18:50:03.741247+00:00s6-rc: info: service frigate: starting
2024-11-10 18:50:03.743604+00:00s6-rc: info: service go2rtc-healthcheck successfully started
2024-11-10 18:50:03.743791+00:00s6-rc: info: service frigate successfully started
2024-11-10 18:50:03.744063+00:00s6-rc: info: service nginx: starting
2024-11-10 18:50:03.748509+00:002024-11-10 18:50:03.748273151  [INFO] Preparing Frigate...
2024-11-10 18:50:03.749597+00:002024-11-10 18:50:03.749447766  [INFO] Starting NGINX...
2024-11-10 18:50:03.751327+00:002024-11-10 18:50:03.751173051  [INFO] Preparing new go2rtc config...
2024-11-10 18:50:03.754508+00:002024-11-10 18:50:03.754427913  [INFO] Starting Frigate...
2024-11-10 18:50:03.763846+00:002024-11-10 18:50:03.763784069  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-11-10 18:50:04.397665+00:002024-11-10 18:50:04.397500026  [INFO] Starting go2rtc...
2024-11-10 18:50:04.686464+00:002024-11-10 18:50:04.686291836  19:50:04.686 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-11-10 18:50:04.686521+00:002024-11-10 18:50:04.686298507  19:50:04.686 INF config path=/dev/shm/go2rtc.yaml
2024-11-10 18:50:04.686874+00:002024-11-10 18:50:04.686764133  19:50:04.686 INF [api] listen addr=:1984
2024-11-10 18:50:04.687038+00:002024-11-10 18:50:04.686995437  19:50:04.686 INF [rtsp] listen addr=:8554
2024-11-10 18:50:04.687167+00:002024-11-10 18:50:04.687129365  19:50:04.687 INF [webrtc] listen addr=:8555/tcp
2024-11-10 18:50:06.097420+00:00s6-rc: info: service nginx successfully started
2024-11-10 18:50:06.097742+00:00s6-rc: info: service certsync: starting
2024-11-10 18:50:06.100461+00:00s6-rc: info: service certsync successfully started
2024-11-10 18:50:06.100640+00:00s6-rc: info: service legacy-services: starting
2024-11-10 18:50:06.104340+00:002024-11-10 18:50:06.104124440  [INFO] Starting certsync...
2024-11-10 18:50:06.107992+00:00s6-rc: info: service legacy-services successfully started
2024-11-10 18:50:06.176642+00:002024-11-10 18:50:06.176497051  127.0.0.1 - - [10/Nov/2024:19:50:06 +0100] "" 400 0 "-" "-" "-"
2024-11-10 18:50:06.749116+00:002024-11-10 18:50:06.748964985  No config file found, saving default config
2024-11-10 18:50:06.749266+00:002024-11-10 18:50:06.749185741  [2024-11-10 19:50:06] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-11-10 18:50:06.749310+00:002024-11-10 18:50:06.749269653  [2024-11-10 19:50:06] frigate.app                    INFO    : Creating directory: /media/frigate/recordings
2024-11-10 18:50:06.749382+00:002024-11-10 18:50:06.749355677  [2024-11-10 19:50:06] frigate.app                    INFO    : Creating directory: /media/frigate/clips/cache
2024-11-10 18:50:06.749466+00:002024-11-10 18:50:06.749439356  [2024-11-10 19:50:06] frigate.app                    INFO    : Creating directory: /config/model_cache
2024-11-10 18:50:06.749546+00:002024-11-10 18:50:06.749519686  [2024-11-10 19:50:06] frigate.app                    INFO    : Creating directory: /media/frigate/exports
2024-11-10 18:50:06.749665+00:002024-11-10 18:50:06.749622642  [2024-11-10 19:50:06] frigate.util.builtin           INFO    : Created default config file, see the getting started docs for configuration https://docs.frigate.video/guides/getting_started
2024-11-10 18:50:06.750028+00:002024-11-10 18:50:06.749932481  [2024-11-10 19:50:06] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-11-10 18:50:06.759746+00:002024-11-10 18:50:06.759692338  [2024-11-10 19:50:06] frigate.util.config            INFO    : copying config as backup...
2024-11-10 18:50:06.760051+00:002024-11-10 18:50:06.759949644  *************************************************************
2024-11-10 18:50:06.760076+00:002024-11-10 18:50:06.759952220  *************************************************************
2024-11-10 18:50:06.760087+00:002024-11-10 18:50:06.759963801  ***    Your config file is not valid!                     ***
2024-11-10 18:50:06.760106+00:002024-11-10 18:50:06.759965442  ***    Please check the docs at                           ***
2024-11-10 18:50:06.760116+00:002024-11-10 18:50:06.759966814  ***    https://docs.frigate.video/configuration/index     ***
2024-11-10 18:50:06.760125+00:002024-11-10 18:50:06.759970990  *************************************************************
2024-11-10 18:50:06.760139+00:002024-11-10 18:50:06.759972598  *************************************************************
2024-11-10 18:50:06.760149+00:002024-11-10 18:50:06.759995054  ***    Config Validation Errors                           ***
2024-11-10 18:50:06.760157+00:002024-11-10 18:50:06.760005947  *************************************************************
2024-11-10 18:50:06.760171+00:002024-11-10 18:50:06.760007515  [Errno 1] Operation not permitted: '/config/backup_config.yaml'
2024-11-10 18:50:06.762223+00:002024-11-10 18:50:06.762069589  Traceback (most recent call last):
2024-11-10 18:50:06.762247+00:002024-11-10 18:50:06.762072631    File "/opt/frigate/frigate/app.py", line 645, in start
2024-11-10 18:50:06.762268+00:002024-11-10 18:50:06.762074086      self.init_config()
2024-11-10 18:50:06.762278+00:002024-11-10 18:50:06.762075585    File "/opt/frigate/frigate/app.py", line 137, in init_config
2024-11-10 18:50:06.762287+00:002024-11-10 18:50:06.762076925      migrate_frigate_config(config_file)
2024-11-10 18:50:06.762296+00:002024-11-10 18:50:06.762078454    File "/opt/frigate/frigate/util/config.py", line 39, in migrate_frigate_config
2024-11-10 18:50:06.762310+00:002024-11-10 18:50:06.762079959      shutil.copy(config_file, os.path.join(CONFIG_DIR, "backup_config.yaml"))
2024-11-10 18:50:06.762320+00:002024-11-10 18:50:06.762081310    File "/usr/lib/python3.9/shutil.py", line 419, in copy
2024-11-10 18:50:06.762328+00:002024-11-10 18:50:06.762084270      copymode(src, dst, follow_symlinks=follow_symlinks)
2024-11-10 18:50:06.762342+00:002024-11-10 18:50:06.762085726    File "/usr/lib/python3.9/shutil.py", line 308, in copymode
2024-11-10 18:50:06.762352+00:002024-11-10 18:50:06.762087428      chmod_func(dst, stat.S_IMODE(st.st_mode))
2024-11-10 18:50:06.762360+00:002024-11-10 18:50:06.762088957  PermissionError: [Errno 1] Operation not permitted: '/config/backup_config.yaml'
2024-11-10 18:50:06.762373+00:002024-11-10 18:50:06.762120588  
2024-11-10 18:50:06.762382+00:002024-11-10 18:50:06.762122427  *************************************************************
2024-11-10 18:50:06.762391+00:002024-11-10 18:50:06.762123788  ***    End Config Validation Errors                       ***
2024-11-10 18:50:06.762404+00:002024-11-10 18:50:06.762141657  *************************************************************
2024-11-10 18:50:08.045238+00:002024-11-10 18:50:08.044955416  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-11-10 18:50:08.050615+00:00s6-rc: info: service legacy-services: stopping
2024-11-10 18:50:08.054710+00:00s6-rc: info: service legacy-services successfully stopped
2024-11-10 18:50:08.054945+00:00s6-rc: info: service go2rtc-healthcheck: stopping
2024-11-10 18:50:08.055134+00:00s6-rc: info: service certsync: stopping
2024-11-10 18:50:08.062966+00:002024-11-10 18:50:08.062819650  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-11-10 18:50:08.063849+00:00s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-11-10 18:50:08.067108+00:002024-11-10 18:50:08.066928632  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-11-10 18:50:08.068575+00:00s6-rc: info: service certsync successfully stopped
2024-11-10 18:50:08.068851+00:00s6-rc: info: service nginx: stopping
2024-11-10 18:50:08.068965+00:00s6-rc: info: service certsync-log: stopping
2024-11-10 18:50:08.177101+00:002024-11-10 18:50:08.177001702  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-11-10 18:50:08.178608+00:00s6-rc: info: service nginx successfully stopped
2024-11-10 18:50:08.178989+00:00s6-rc: info: service nginx-log: stopping
2024-11-10 18:50:08.179382+00:00s6-rc: info: service frigate: stopping
2024-11-10 18:50:08.181310+00:00s6-rc: info: service frigate successfully stopped
2024-11-10 18:50:08.181516+00:00s6-rc: info: service go2rtc: stopping
2024-11-10 18:50:08.181736+00:00s6-rc: info: service frigate-log: stopping
2024-11-10 18:50:08.182995+00:002024-11-10 18:50:08.182950711  exit with signal: terminated
2024-11-10 18:50:08.188158+00:002024-11-10 18:50:08.188036176  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-11-10 18:50:08.189036+00:00s6-rc: info: service go2rtc successfully stopped
2024-11-10 18:50:08.189470+00:00s6-rc: info: service go2rtc-log: stopping
2

Did you ever resolve this problem? I have found a few posts on other forums with the same problem but none of them have provided a solution.

Thanks

3

It’s best if you post the details of your system, os version, etc. The version of Frigate would help too. Try to provide as much info as you can.

4

ElectricEel-24.10.1

Installed Frigate from the apps folder and got it working. It worked for several months. Recently I updated from V 0.13 to V0.14 and got errors shown in the log (shown below). Restoring back to 0.13 would make it work again.

Here is the log:
2025-02-27 01:11:31.930116+00:00s6-rc: info: service s6rc-fdholder: starting
2025-02-27 01:11:31.930195+00:00s6-rc: info: service s6rc-oneshot-runner: starting
2025-02-27 01:11:31.932437+00:00s6-rc: info: service s6rc-oneshot-runner successfully started
2025-02-27 01:11:31.932522+00:00s6-rc: info: service fix-attrs: starting
2025-02-27 01:11:31.933238+00:00s6-rc: info: service s6rc-fdholder successfully started
2025-02-27 01:11:31.935597+00:00s6-rc: info: service fix-attrs successfully started
2025-02-27 01:11:31.935688+00:00s6-rc: info: service legacy-cont-init: starting
2025-02-27 01:11:31.938558+00:00s6-rc: info: service legacy-cont-init successfully started
2025-02-27 01:11:31.938649+00:00s6-rc: info: service log-prepare: starting
2025-02-27 01:11:31.944244+00:00s6-rc: info: service log-prepare successfully started
2025-02-27 01:11:31.944366+00:00s6-rc: info: service nginx-log: starting
2025-02-27 01:11:31.944452+00:00s6-rc: info: service go2rtc-log: starting
2025-02-27 01:11:31.944571+00:00s6-rc: info: service frigate-log: starting
2025-02-27 01:11:31.944671+00:00s6-rc: info: service certsync-log: starting
2025-02-27 01:11:31.945806+00:00s6-rc: info: service go2rtc-log successfully started
2025-02-27 01:11:31.945875+00:00s6-rc: info: service go2rtc: starting
2025-02-27 01:11:31.946162+00:00s6-rc: info: service nginx-log successfully started
2025-02-27 01:11:31.946404+00:00s6-rc: info: service frigate-log successfully started
2025-02-27 01:11:31.946618+00:00s6-rc: info: service certsync-log successfully started
2025-02-27 01:11:31.947135+00:00s6-rc: info: service go2rtc successfully started
2025-02-27 01:11:31.947205+00:00s6-rc: info: service go2rtc-healthcheck: starting
2025-02-27 01:11:31.947295+00:00s6-rc: info: service frigate: starting
2025-02-27 01:11:31.948531+00:00s6-rc: info: service go2rtc-healthcheck successfully started
2025-02-27 01:11:31.948708+00:00s6-rc: info: service frigate successfully started
2025-02-27 01:11:31.948788+00:00s6-rc: info: service nginx: starting
2025-02-27 01:11:31.950552+00:002025-02-27 01:11:31.950426976 [INFO] Preparing new go2rtc config…
2025-02-27 01:11:31.951022+00:002025-02-27 01:11:31.950973373 [INFO] Preparing Frigate…
2025-02-27 01:11:31.952031+00:002025-02-27 01:11:31.951991316 [INFO] Starting NGINX…
2025-02-27 01:11:31.956697+00:002025-02-27 01:11:31.956661376 [INFO] No TLS certificate found. Generating a self signed certificate…
2025-02-27 01:11:32.007113+00:002025-02-27 01:11:32.007013986 [INFO] Starting Frigate…
2025-02-27 01:11:32.226790+00:00s6-rc: info: service nginx successfully started
2025-02-27 01:11:32.226920+00:00s6-rc: info: service certsync: starting
2025-02-27 01:11:32.228538+00:00s6-rc: info: service certsync successfully started
2025-02-27 01:11:32.228678+00:00s6-rc: info: service legacy-services: starting
2025-02-27 01:11:32.230669+00:002025-02-27 01:11:32.230543550 [INFO] Starting certsync…
2025-02-27 01:11:32.232958+00:00s6-rc: info: service legacy-services successfully started
2025-02-27 01:11:32.409267+00:002025-02-27 01:11:32.409119026 127.0.0.1 - - [26/Feb/2025:20:11:32 -0500] “” 400 0 “-” “-” “-”
2025-02-27 01:11:32.503810+00:002025-02-27 01:11:32.503641140 [INFO] Starting go2rtc…
2025-02-27 01:11:32.564748+00:002025-02-27 01:11:32.564637912 20:11:32.564 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-02-27 01:11:32.564794+00:002025-02-27 01:11:32.564642060 20:11:32.564 INF config path=/dev/shm/go2rtc.yaml
2025-02-27 01:11:32.565097+00:002025-02-27 01:11:32.565017476 20:11:32.564 INF [rtsp] listen addr=:8554
2025-02-27 01:11:32.565129+00:002025-02-27 01:11:32.565019189 20:11:32.564 INF [api] listen addr=:1984
2025-02-27 01:11:32.565177+00:002025-02-27 01:11:32.565135528 20:11:32.565 INF [webrtc] listen addr=:8555/tcp
2025-02-27 01:11:33.662898+00:002025-02-27 01:11:33.662733939 2025/02/26 20:11:33 [error] 171#171: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.13, server: , request: “GET /api/stats HTTP/1.1”, subrequest: “/auth”, upstream: “http://127.0.0.1:5001/auth”, host: “192.168.2.10:30059”
2025-02-27 01:11:33.662961+00:002025-02-27 01:11:33.662738146 2025/02/26 20:11:33 [error] 171#171: *2 auth request unexpected status: 502 while sending to client, client: 192.168.2.13, server: , request: “GET /api/stats HTTP/1.1”, host: “192.168.2.10:30059”
2025-02-27 01:11:34.164301+00:002025-02-27 01:11:34.164176777 [2025-02-26 20:11:34] frigate.util.config INFO : Checking if frigate config needs migration…
2025-02-27 01:11:34.167527+00:002025-02-27 01:11:34.167440984 [2025-02-26 20:11:34] frigate.util.config INFO : copying config as backup…
2025-02-27 01:11:34.168430+00:002025-02-27 01:11:34.168276225 Traceback (most recent call last):
2025-02-27 01:11:34.168456+00:002025-02-27 01:11:34.168278008 File “/usr/lib/python3.9/runpy.py”, line 197, in _run_module_as_main
2025-02-27 01:11:34.168472+00:002025-02-27 01:11:34.168279481 return _run_code(code, main_globals, None,
2025-02-27 01:11:34.168482+00:002025-02-27 01:11:34.168281394 File “/usr/lib/python3.9/runpy.py”, line 87, in _run_code
2025-02-27 01:11:34.168491+00:002025-02-27 01:11:34.168282577 exec(code, run_globals)
2025-02-27 01:11:34.168507+00:002025-02-27 01:11:34.168283178 File “/opt/frigate/frigate/main.py”, line 64, in
2025-02-27 01:11:34.168516+00:002025-02-27 01:11:34.168297144 main()
2025-02-27 01:11:34.168525+00:002025-02-27 01:11:34.168297845 File “/opt/frigate/frigate/main.py”, line 35, in main
2025-02-27 01:11:34.168539+00:002025-02-27 01:11:34.168298837 config = FrigateConfig.load(install=True)
2025-02-27 01:11:34.168548+00:002025-02-27 01:11:34.168299438 File “/opt/frigate/frigate/config/config.py”, line 643, in load
2025-02-27 01:11:34.168557+00:002025-02-27 01:11:34.168299979 migrate_frigate_config(config_path)
2025-02-27 01:11:34.168566+00:002025-02-27 01:11:34.168300601 File “/opt/frigate/frigate/util/config.py”, line 53, in migrate_frigate_config
2025-02-27 01:11:34.168580+00:002025-02-27 01:11:34.168318144 shutil.copy(config_file, os.path.join(CONFIG_DIR, “backup_config.yaml”))
2025-02-27 01:11:34.168588+00:002025-02-27 01:11:34.168318775 File “/usr/lib/python3.9/shutil.py”, line 419, in copy
2025-02-27 01:11:34.168602+00:002025-02-27 01:11:34.168319737 copymode(src, dst, follow_symlinks=follow_symlinks)
2025-02-27 01:11:34.168611+00:002025-02-27 01:11:34.168320288 File “/usr/lib/python3.9/shutil.py”, line 308, in copymode
2025-02-27 01:11:34.168620+00:002025-02-27 01:11:34.168332090 chmod_func(dst, stat.S_IMODE(st.st_mode))
2025-02-27 01:11:34.168629+00:002025-02-27 01:11:34.168332791 PermissionError: [Errno 1] Operation not permitted: ‘/config/backup_config.yaml’
2025-02-27 01:11:34.484771+00:002025-02-27 01:11:34.484317213 [INFO] Service Frigate exited with code 1 (by signal 0)
2025-02-27 01:11:34.486749+00:00s6-rc: info: service legacy-services: stopping
2025-02-27 01:11:34.488640+00:00s6-rc: info: service legacy-services successfully stopped
2025-02-27 01:11:34.488775+00:00s6-rc: info: service go2rtc-healthcheck: stopping
2025-02-27 01:11:34.488936+00:00s6-rc: info: service certsync: stopping
2025-02-27 01:11:34.493256+00:002025-02-27 01:11:34.493195346 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2025-02-27 01:11:34.493964+00:00s6-rc: info: service go2rtc-healthcheck successfully stopped
2025-02-27 01:11:34.494079+00:002025-02-27 01:11:34.494055663 [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2025-02-27 01:11:34.495057+00:00s6-rc: info: service certsync successfully stopped
2025-02-27 01:11:34.495129+00:00s6-rc: info: service nginx: stopping
2025-02-27 01:11:34.495227+00:00s6-rc: info: service certsync-log: stopping
2025-02-27 01:11:34.613929+00:002025-02-27 01:11:34.613736249 [INFO] Service NGINX exited with code 0 (by signal 0)
2025-02-27 01:11:34.614600+00:00s6-rc: info: service nginx successfully stopped
2025-02-27 01:11:34.614757+00:00s6-rc: info: service nginx-log: stopping
2025-02-27 01:11:34.614938+00:00s6-rc: info: service frigate: stopping
2025-02-27 01:11:34.616093+00:00s6-rc: info: service frigate successfully stopped
2025-02-27 01:11:34.616176+00:00s6-rc: info: service go2rtc: stopping
2025-02-27 01:11:34.616256+00:00s6-rc: info: service frigate-log: stopping
2025-02-27 01:11:34.617044+00:002025-02-27 01:11:34.617004244 exit with signal: terminated
2025-02-27 01:11:34.620464+00:002025-02-27 01:11:34.620421809 [INFO] The go2rtc service exited with code 0 (by signal 0)
2025-02-27 01:11:34.621096+00:00s6-rc: info: service go2rtc successfully stopped
2025-02-27 01:11:34.621202+00:00s6-rc: info: service go2rtc-log: stopping

The error sequence starts at “2025-02-27 01:11:34.167527+00:002025-02-27 01:11:34.167440984 [2025-02-26 20:11:34] frigate.util.config INFO : copying config as backup…”

image
image769×426 15.9 KB

As you can see from the attached image, the permissions on backup_config.yaml seem correct.

I tried to uninstalled Frigate and reinstall it in a new directory (frigatenew). It starts the first time it runs but throws the error at any subsequent attempt to start the program.

Current attempts were on

App Version: 0.15.0
Version: 1.1.17

I had the same problem with 0.14.0 but it worked OK with 0.13.0. I was able to rollback to 0.13.0 until I deleted the app tov try a fresh install.

Please let me know if other info would be helpul.

Ricke

5

I wonder if you should try to report it as a bug in the app. There should be a link when you bring up the Frigate app on the right side that leads to github.

When you post logs, etc in the future, please use Preformatted Text (</>) or Ctrl+e. It makes for easier reading.

6

Two problems which I have encountered, which look like this:
1- the config version is not correct for the app version
2-the paths for the new app version overlap with the paths for a previous app version and hence some config elements are presented to the new app version which are incompatible.

The solution for me has been to obliterate all references to previous configs (find them/delete them or make sure that you create new host paths which are unique, along the lines of " /mnt/tank/frigate_new " or something, and hence cannot contain leftovers from previous attempts) and/or get the bare config from the frigate documentation and start from scratch and make certain that the result is entirely compatible with the version of frigate you are trying to use. At the moment, that is v0.15 for the official app.

Good luck - let us know what you find

1 Like
7

@SmallBarky

Sorry for the formatting.

I took your advice and opened an issue on the truenas/apps github.

Ricke

1 Like
8

@E_B

I have already tried uninstalling Frigate, creating new directories, and reinstalling in new directories but the same problem occurs.

Thanks for the suggestion.

Ricke

9

purely guesses, to try to think of something new for you to try:

you could install with explicit host paths for everything

image
image296×966 19 KB

and if that doesn’t work you could try it with ixVolume instead:
image

10

Problem solved although root cause is unknown.

Earlier, in an attempt to solve this problem, I deleted and recreated directories using rmdir and mkdir. That did not help.

This time I created a new Dataset for the config files (still nested same as not working Dataset) from Truenas Datasets GUI. I then copied the files from the old dataset to the new one and changed the pointers in the app configuration screen. All works fine with the new Dataset.

I am not able to determine why the old Dataset has the problem. It’s ACL and the resulting file permissions look the same with both datasets.

Thanks for the suggestions. BTW, I also reported this on the Github issue I opened so hopefully others who have this problem will see the solution/workaround here or there.

Ricke

11

Update: I think there may be an easier solution. Just delete the file named “\backup_config.yaml” and restart the app. I tried this with the dataset that was not working and it solved the problem in that Dataset too.

1 Like
12

That’s a good piece of detective work - interesting. What’s your theory?

I wonder if (somehow) the default config is being corrupted or not generated when the new Frigate is installed, and that causes the backup to be read but the backup, being from an older Frigate, is not compatible.

In the case of mkdir and rmdir not working, my presumption is that ZFS+TrueNAS is very integrated with databases and hence instructions like zfs pool destroy or create must be needed to ensure a database is correctly synchronised/adjusted (made up terms because I don’t know anything about this).

13

I tried this, but it didn’t work for me when trying to upgrade from 0.14.1_1.1.15 to 0.15.0_1.1.17. Any other ideas?

14

It’s not a solution, but I do notice that if you delete the config file and its backup, Frigate v0.15.0_1.1.17 will deploy, but only once. On subsequent deploys, it throws the same error.

If anyone can get it to deploy reliably, note that there is a breaking change in the record feature: “events” no longer exists. I discovered this after I deleted my config file, deployed the app, pasted the old config contents into the default one that Frigate creates, and noticed it highlighted “events” as an error.

15

To start, the problem is a permissions issue on the file backup_config.yaml. WIth a new install of Frigate (or it seem with an upgrade) the error doesn’t occur on the initial program start after installing Frigate. It occurs on the second and subsequent attempt to start the program. The permissions on that file look OK using LS.

On the issue I opened on Github, the respondent theorized it had something to do with the latest Frigate code having a problem with ACL’s and recommended
using Linux permissions instead. Following hid theory I first tried using the “Strip ACL” function in the dataset tab on the existing dataset. That did not help. I then created two new datasets, one with the Linux permissions root:root and another with an ACL appropriate for my AD situation. The ACL did include a root:root entry though. I installed a fresh Frigate install in both worked so I am not so sure it is ACL’s. I also noted installing a fresh instance and using ixVolume for the Config directory worked

I then went back to the original dataset, linked it in a new install of Frigate, and verified it still had the problem. I then deleted the file backup_config.yaml and restarted Frigate and it all worked.

I do not know what is happening that causes the problem but it seems linked to the permission on the original back_config.yaml file.

Ricke

16

What exactly did you try? Did you create a totally new dataset and try installing into it? If you did try a new dataset, what permissions did you use?

17

If the upgrade had worked properly, those “event” entries would have been converted to “alerts” and “detections” in your yaml. I ran into the same issue.

18

So far, I’ve tried:

  1. Deleting back_config.yaml: Same error
  2. Deleting back_config.yaml and config.yml (it appears this is now config.yaml in v0.15.0_1.1.17): Allows it to deploy, but only once.
  3. Manually creating the back_config.yaml file, hoping it would skip this step: Same error
  4. Manually editing config.yaml to replace events with alerts and detections: Same error

I’m hesitant to make changes to my datasets or create new ones because:

  1. Time constraints - datasets affect my backup systems
  2. Risk of compounding issues
  3. Hope that someone finds and fixes a bug in the code. This all works fine for me in v0.14.1_1.1.15 and I haven’t changed anything with the datasets, so this seems like a bug to me. Otherwise, if it’s a permanent, breaking change, it would be nice for the devs to confirm this and disclose what exactly to do to remdedy the issue.
19

Interesting that deleting back_config.yaml did not work. I stumbled across that after I had already created a new dataset and new instance of Frigate. Since I did not delete the old dataset or instance of Frigate I was able to test it.

If you create a new Dataset, copy the files from the existing dataset into the new Dataset, create a second instance of Frigate in apps (use different name) and then get it working (which I think it will), you can then delete the old dataset and instance of Frigate. You will yhrn be backing up the same amount of data as before so time and space would not be impacted.

Creating a new dataset and creating a new instance of Frigate (You can have multiple with different names) does not touch your existing instance so there is no risk of “compounding issues”.

I agree this problem is being caused by a bug, but I see no evidence anyone is working on it. I fear we will need to go through the same exercise at the next upgrade. I am actually surprised not more people are having this problem. It makes me wonder what is unique about those of us who are having the problem

20

From what I can gather, this issue is at least as old as v0.14.1_1.1.15, which is the version that’s working for me. The issue arises when Frigate thinks there’s something wrong with the config and triggers a backup of the config. I discovered this when I made an error in my config in v0.14.1_1.1.15 - it failed to deploy and reported the same error. I hadn’t noticed this before because I haven’t made a config error in a long time.

The reason why I (and probably others) are just now seeing this error when trying to upgrade to v0.15.0+ is because this forces a config backup, presumably due to breaking changes between v0.14.0 and v0.15.0, which triggers this error.

I tried working around this by manually fixing the “events” issue and changing the version at the bottom of the config from v0.14 to v0.15, then upgrading Frigate, but it runs the config backup even if it doesn’t need to, which triggers this error.