Trouble installing frigate on casaos

ifishtoo · June 25, 2024, 2:04am

I Click install and it gets to 75% and stops. Eventually the error says “Installing error info” “container frigate is unhealthy”. If I click the 3 dots and settings there is no icon for terminal and logs. I am not familiar with casaos or docker yet so I do not yet have the skills to troubleshoot this without help. I am using debian 11 bullseye with casaos 0.4.9 . This is a fresh install. I have made very few changes. Setup blueman. disabled ufw. I have tried repeatedly and looked for discrepancies in my config.yaml and docker compose.

I watched the video several times. I have tried to install frigate several times.

debian 11 bullseye
Casaos 0.4.9

I copy and paste the docker file.
I delete the /dev/bus line since I have no coral tpu

I modified the config.yaml as follows in this latest attempt.

mqtt:
enabled: false
cameras:
path: rtsp://admin:********@10.0..:8554/live/video_audio/profile0
roles:
- detect
detect:
width: 3840
height: 2160

I have verified the path provides a video/audio feed with vlc.
I can access casaos from a local browser and also from another system on the same lan subnet. I can access the terminal from casaos home page and ssh works fine too but only with the casaos user. the terminal does not work with casaosuser. That user only works in the homepage login.
I modifed the volumes as instructed in the video with /DATA/AppData/frigate and verified they exist in the proper locations.

I monitored <journalctl -f> during the install and several lines emerged shortly after install failed.

*********************************************************8
Jun 24 18:51:13 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37\x2dinit-merged.mount: Succeeded.
Jun 24 18:51:16 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:17 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.G8DS8t.mount: Succeeded.
Jun 24 18:51:21 casaos-optiplex9020m sudo[729528]: casaos : TTY=pts/2 ; PWD=/home/casaos ; USER=root ; COMMAND=/usr/bin/dmesg
Jun 24 18:51:21 casaos-optiplex9020m sudo[729528]: pam_unix(sudo:session): session opened for user root(uid=0) by casaos(uid=1000)
Jun 24 18:51:21 casaos-optiplex9020m sudo[729528]: pam_unix(sudo:session): session closed for user root
Jun 24 18:51:21 casaos-optiplex9020m systemd[1001]: run-docker-netns-04df7edc2bd4.mount: Succeeded.
Jun 24 18:51:21 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:26 casaos-optiplex9020m systemd[1001]: run-docker-netns-190083ab8828.mount: Succeeded.
Jun 24 18:51:26 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:27 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.IMT5v6.mount: Succeeded.
Jun 24 18:51:32 casaos-optiplex9020m systemd[1001]: run-docker-netns-9a0114636cdc.mount: Succeeded.
Jun 24 18:51:32 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:32 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.AAGZfA.mount: Succeeded.
Jun 24 18:51:37 casaos-optiplex9020m systemd[1001]: run-docker-netns-977e156de446.mount: Succeeded.
Jun 24 18:51:37 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:37 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.KiMJjC.mount: Succeeded.
Jun 24 18:51:42 casaos-optiplex9020m systemd[1001]: run-docker-netns-db449e485665.mount: Succeeded.
Jun 24 18:51:42 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:43 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.x4nFuV.mount: Succeeded.
Jun 24 18:51:48 casaos-optiplex9020m systemd[1001]: run-docker-netns-f2ee6c91c837.mount: Succeeded.
Jun 24 18:51:48 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:51:51 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.4Elg7Q.mount: Succeeded.
Jun 24 18:51:56 casaos-optiplex9020m systemd[1001]: run-docker-netns-adbfdd39e4fc.mount: Succeeded.
Jun 24 18:51:56 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:52:02 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.HpNEAw.mount: Succeeded.
Jun 24 18:52:07 casaos-optiplex9020m systemd[1001]: run-docker-netns-1bdbce15d0cd.mount: Succeeded.
Jun 24 18:52:07 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:52:24 casaos-optiplex9020m systemd[1001]: run-docker-netns-a44d74733a93.mount: Succeeded.
Jun 24 18:52:24 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.
Jun 24 18:52:50 casaos-optiplex9020m systemd[1001]: run-docker-runtime\x2drunc-moby-ce9a944f7383b527efb1af473c395d5703a244abe57c66a2ca0e5875ae732648-runc.xVpKA8.mount: Succeeded.
Jun 24 18:52:54 casaos-optiplex9020m systemd[1001]: run-docker-netns-b7566ccb317d.mount: Succeeded.
Jun 24 18:52:54 casaos-optiplex9020m systemd[1001]: var-lib-docker-overlay2-5bfbc8ad18c4a560a636ed41effe139562847be1bff9a514c73fa00f63824b37-merged.mount: Succeeded.

I clicked on settings but the terminal and log icon is missing.

I clicked on launch and open and watched journalctl again. Error: app may not be available.

If you all have some recommendations that will move this project forward I am all ears. In the mean time I will start reading to see if I can find something that will provide me with troubleshooting tools I am so used to having at my fingertips. Running into dead ends like this is why I switched to Linux 40 years ago.

ifishtoo · June 26, 2024, 6:19pm

The wiki says use debian 11 but github says debian 12. I switched to Ubuntu server 22.04 and got better results. Still not full success but the log is generated properly and I have enough info to continue trouble shooting my setup. I would call this particular issue solved.

btw: the config.yml does not work. He did not mention it in the video but the syntax of this file needs to be correct. see Frigate Configuration | Frigate and Frigate Configuration | Frigate

snip from my log

frigate  | 2024-06-26 18:05:35.383475320  *************************************************************
frigate  | 2024-06-26 18:05:35.383478492  *************************************************************
frigate  | 2024-06-26 18:05:35.383482339  ***    Your config file is not valid!                     ***
frigate  | 2024-06-26 18:05:35.383484880  ***    Please check the docs at                           ***
frigate  | 2024-06-26 18:05:35.383486474  ***    https://docs.frigate.video/configuration/index     ***
frigate  | 2024-06-26 18:05:35.383500695  *************************************************************
frigate  | 2024-06-26 18:05:35.383502179  *************************************************************
frigate  | 2024-06-26 18:05:35.383525143  ***    Config Validation Errors                           ***
frigate  | 2024-06-26 18:05:35.383526643  *************************************************************
frigate  | 2024-06-26 18:05:35.383630407  3 validation errors for FrigateConfig
frigate  | 20*24-06-26 18:05:35.383644671  mqtt -> back*
*frigate  | 2024-06-26 18:05:35.383646422    extra fields not permitted (type=value_error.extra)*
*frigate  | 2024-06-26 18:05:35.383647679  mqtt -> cameras*
*frigate  | 2024-06-26 18:05:35.383649105    extra fields not permitted (type=value_error.extra)*
*frigate  | 2024-06-26 18:05:35.383650278  cameras*
*frigate  | 2024-06-26 18:05:35.383651685    field required (type=value_error.missing)*
*frigate  | 2024-06-26 18:05:35.384276458  Traceback (most recent call last):*
*frigate  | 2024-06-26 18:05:35.384278519    File "/opt/frigate/frigate/app.py", line 645, in start*
*frigate  | 2024-06-26 18:05:35.384279777      self.init_config()*
*frigate  | 2024-06-26 18:05:35.384281104    File "/opt/frigate/frigate/app.py", line 112, in init_config*
*frigate  | 2024-06-26 18:05:35.384282400      user_config = FrigateConfig.parse_file(config_file)*
*frigate  | 2024-06-26 18:05:35.384283756    File "/opt/frigate/frigate/config.py", line 1346, in parse_file*
*frigate  | 2024-06-26 18:05:35.384284963      return cls.parse_obj(config)*
*frigate  | 2024-06-26 18:05:35.384286328    File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj*
*frigate  | 2024-06-26 18:05:35.384287719    File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__*
*frigate  | 2024-06-26 18:05:35.384289746  pydantic.error_wrappers.ValidationError: 3 validation errors for FrigateConfig*
*frigate  | 2024-06-26 18:05:35.384291507  mqtt -> back*
*frigate  | 2024-06-26 18:05:35.384292825    extra fields not permitted (type=value_error.extra)*
*frigate  | 2024-06-26 18:05:35.384320899  mqtt -> cameras*
*frigate  | 2024-06-26 18:05:35.384322382    extra fields not permitted (type=value_error.extra)*
*frigate  | 2024-06-26 18:05:35.384323503  cameras*
*frigate  | 2024-06-26 18:05:35.384325407    field required (type=value_error.missing)*
*frigate  | 2024-06-26 18:05:35.384326531  *
*frigate  | 2024-06-26 18:05:35.384327933  **************************************************************
*frigate  | 2024-06-26 18:05:35.384355984  ***    End Config Validation Errors                       ****
*frigate  | 2024-06-26 18:05:35.384357713  **************************************************************

dragonfire1119 · June 26, 2024, 6:42pm

Glad this is solved. When I made the video that was the correct way to format the config.yml it may have changed though. I think I was using Ubuntu Jammy when I made the video.

If you want you can create a pull request for the script that makes the config.yml. It would help others:

github.com

bigbeartechworld/big-bear-scripts/blob/fd09bc224eb676bdd1fb1fde07b59be387c71d44/frigate-casaos/create_config.sh#L9


      
          #!/bin/bash
          
          CONFIG_PATH="/DATA/AppData/frigate/config/config.yml"
          
          # Ensure the directory exists
          mkdir -p $(dirname $CONFIG_PATH)
          
          # Write the content to config.yml
          cat > $CONFIG_PATH <<EOL
          mqtt:
            host: mqtt.server.com
          cameras:
            back:
              ffmpeg:
                inputs:
                  - path: rtsp://viewer:[email protected]:554/cam/realmonitor?channel=1&subtype=2
                    roles:
                      - detect
              detect:

ifishtoo · June 26, 2024, 7:02pm

You have provided a valuable resource by making the video. I added the comments there as well. Updating instructions as we go is just part of the process. “It takes a village to maintain a set of instructions.”

dragonfire1119 · June 28, 2024, 4:39am

Thank you, glad to hear! 100% agree, and that’s why I want people to discuss on the forum because it keeps a dialogue about solutions and what needs to be changed. Also helps people from the search engines: