Frigate on Docker, in Windows Subsystem for Linux (WSL) #4375

MinimumDowntime · 2022-11-11T18:26:41Z

MinimumDowntime
Nov 11, 2022

I wanted to write something up to share with the HA community as it's mentioned only briefly in the Installation of Frigate. Specifically:

Windows is not officially supported, but some users have had success getting it to run under WSL or Virtualbox. Getting the GPU and/or Coral devices properly passed to Frigate may be difficult or impossible. Search previous discussions or issues for help.

I couldn't find much in the way of this, but I'll openly admit I could have just been searching in the wrong places. In any case, if you're like me with a computer running Windows, you may think to yourself "I can run Docker on Windows. Docker can interface with WSL. I should be able to pull off running Frigate." and I'm here to tell you that yes you can, and it's easier than you might think.

I've also been able to get Frigate running with Nvidia GPU Tensor, as well as the Google Coral USB. Granted, the Coral as of this current edit produces some errors in Frigate logs. It never the less works!

Anyway, let's get Frigate running in Windows.

Deploy and Configure WSL

There are two ways to get WSL going in Windows. If you want the fast path to WSL, open up Windows PowerShell (not x86, not ISE, just regular old blue icon Windows PowerShell) as an Admin and execute

wsl --install -d Ubuntu

This command will make WSL available and deploy Ubuntu. Want to see more about this approach? Check out the Microsoft Docs article on it. Want to go the slightly longer way? Read steps 1-3 to get started with WSL.

Windows Subsystem for Linux must be enabled in Windows. Just open the Start menu and type "Turn Windows Features on or off". As you type, it will probably come up without you having to finish. Open it up, scroll down, and make sure the two following items are checked:
- Windows Subsystem for Linux
- Virtual Machine Platform

This might requite a reboot once installed. I forget.

Open up the Microsoft Store. You can do this by going to start and typing "store". Then, search for a Linux distro. You can use Ubuntu, OpenSuse, Kali, and Debian. In my environment, I am using and have only tested it with Ubuntu.

Setup WSL by going to start, type 'wsl' and you should see 'run command' with the tux/penguin icon. Click to open it up and then set a username/password and perform any other initial config as necessary.

At this point, WSL/Linux are running on Windows. Neat! Onto Docker.

Deploy and Configure Docker on Windows (updated 2.21.25 for v4.38.0)

Install Docker Desktop from here. Once Docker is running, open it up and click the small Gear icon in the top right by the sign in button. This will take you to Docker Settings. In the General tab (where you'll land by default) you should have "Use the WSL 2 based engine" already checked off. If not, make sure its enabled.

Next, head into Resources above the General tab. Then select "WSL Integration". Make sure that "enable integration with my default WSL distro' is checked and that the distro you installed from above is listed, and enabled.

At this point, we have WSL running and we have Docker integrated with it. Finally, it's time to pull down Frigate and configure it.

Deploy and Configure Frigate

Per Frigate installation on Docker, Compose is the preferred installation method. The good news is that the initial compose as laid out can be used with very slight tweaks. Specifically:
- you might not have devices you are passing into the container. In which case, this section can be removed/commented out entirely.
- we need to alter the Volumes section. Given the first three lines, we'll need to alter to allow the Frigate Docker Container, access to your Windows host/WSL instance.

BEFORE

/etc/localtime:/etc/localtime:ro
/path/to/your/config:/config
/path/to/your/storage:/media/frigate

AFTER

\\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
./config:/config
./media:/media/frigate

Everything to the left of the ":" is a path to somewhere on your Windows host/WSL instance. Everything to the right of ":" is the path Frigate knows. Its Docker that is handling the abstraction and mapping of these paths into the container. Which is to say, this is telling the Frigate container in Docker, how to access resources that exist on your Windows host and WSL instance. This means if you want to place your Config directory and Media directory in different locations on your Windows host (for example, you might place media on a large disk) you could alter that path. For example:

\\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
./config:/config
T:\frigatemedia:/media/frigate

Again, note that everything to the left ":" is what is changing in these examples

In fact, you might recognize part of the above as a UNC Network Path because it is! Curious? Open up File Explorer in Windows, and type in "\\wsl$". Doing so allows you to navigate into the WSL distro. just use "\\wsl$" with a single $ instead of $$ as listed above in the docker compose. As far as the rest of the Compose is concerned, configure everything else such as the password, ports, etc. as you see fit.

We need to now define a Frigate configuration file (config.yml). Let's head into the path as defined above by opening Windows File Explorer and navigating into the folder you chose for the Config directory. Create a new file called config.yml. Within it, you should define your MQTT server, cameras, etc. and everything that you see in the setup instructions, YouTube videos, and elsewhere.
Now let's spin up the container using our Docker Compose file. Open up a PowerShell window (connected to your Windows host, not your WSL instance) if you don't already have one open (see the paragraph above step 1 on choosing the "right" PowerShell to open if you have question). Navigate to the directory where you docker compose file is located. If you don't have a Compose file yet, the above link to "compose is the preferred installation method" should be followed. There, copy the contents laid out and save it to a file called "docker-compose.yaml". Wherever you place this file, that is where you'll need to cd/navigate into from the terminal. You can do this by typing "cd c:\folder\path" where c:\folder\path is the directory the file is stored. Now type/paste in "docker-compose up -d". The very first time you do this, Docker will download the Frigate image to your Windows host. Once downloaded, it will then spinup an instance (container) of Frigate. If in the future you run "docker-compose up -d" as long as the image remains on disk, you'll near instantly spinup a replacement of the container. Which you'll end up doing when it comes to updating Frigate to newer versions. Eventually, you should see a result returned such as "Running". Interested in what this command and other relevant Docker arguments mean? Check out https://docs.docker.com/engine/reference/commandline/compose_up/
Head back into Docker within Windows, and go to Containers. You should see the name of your folder the Docker Compose was located in and a sub item of "frigate" now running. At this point, Frigate is now running in Docker and all troubleshooting/subsequent configuration should follow any other threads you find online.

Hardware Acceleration

The other thing that might cross your mind with a Windows computer is taking advantage of a dedicated GPU to use within WSL. Fortunately, there are only a couple things that are required

Your WSL instance must be V2, you can check this at a command prompt in Windows by typing and executing:

wsl -l -v

and verifying you see "2" next to the distro you configured above.

You must be running at least Windows 21H2
- This version of Windows was released on 10/4/2021 so chances are if you've updated since then you're probably okay. But if you want to double check, open the start menu, type "winver" and open up to see which version you have.
- If you want to read more about Windows update release history, check out the Microsoft doc here
- You have the latest drivers for your GPU installed. In my case, I'm using a Nvidia GTX1080

Once you've met these requirements, open up your WSL command prompt by going to Start, typing "WSL" and opening up the command prompt. There, type "nvidia-smi". You should return a result that looks something like this:

In the above screenshot, I've highlighted and circled the ID for the GPU in the event you have multiple GPUs and want to pick and choose what gets passed into WSL.

Then in your Docker Compose file, you'll want to add the following section. You'll notice I commented out #device_ids, and instead opted for count: all. Count takes either an integer or the string of "all".

    deploy:    # <------------- Add this section
      resources:
        reservations:
          devices:
            - driver: nvidia
              #device_ids: ['0'] # this is only needed when using multiple GPUs
              count: all # number of GPUs
              capabilities: [gpu]

As an example, here's the Docker Compose file with that section added.

Finally, in your config.yml we'll need to add arguments for hardware acceleration. Per Frigate Documentation on Nvidia GPUs I'm just going to use h264. To see a list of supported codecs, in Docker, navigate into the Terminal for the Frigate container. Then use

ffmpeg -decoders | grep cuvid

to see a list of supported codecs. In my case, I have an Nvidia GPU so per documentation I can simply use "preset-nvidia-h264"

Again, we'll use "docker-compose up -d" at the Windows PowerShell command line in the directory the compose file is located to rebuild the container using the new compose that makes use of the GPU. Then in WSL, we'll type "nvidia-smi" once again, only this time we should see the ffmpeg process attached for each camera we have HW Accel arguments defined in our config.yml.

Limiting WSL Host Resources

If you've done the above, something you may notice after a couple days of use is that your Windows host, has near maxed out it's memory usage! This is because WSL will continue to consume resources as it needs them. So you will more than likely want to set a ceiling on what WSL is capable of consuming. Solving this is incredibly simple.

Navigate to C:\Users\YOURUSERNAMEHERE
Create a file called ".wslconfig"
Modify/Paste the following based on your respective requirements

[wsl2]
memory=16GB #WSL only consume up to 16gb of memory
processors=4 #WSL will only make use of 4 processors

In the above config, only the CPU/Memory for WSL is capped and everything after the # is a note per line. Want to know what else you can configure? Check out the following Microsoft Doc on Advanced Settings Configuration in WSL

At this point, either restart your Windows host or just restart WSL with PowerShell (as an Admin) for changes to take effect:

Restart-Service LxssManager

Using a Google Coral USB Detector

It should be noted, while the following works, I am as of this writing currently producing sporadic errors in Frigate that result in either the detection service restarting or the container restarting. However these events seemingly have not adversely affected recording, performance, or anything that jeopardizes Frigate's ability to function. From what I've seen, no more than 5 seconds of downtime occurs as a result of this. Secondly, it appears the Coral will not auto-attach as described in Step 7 below. After a reboot of the Windows host the command must be executed to re-establish connectivity. I suspect this can be automated and am working on doing so. I'll update this section if I can get that working.

With WSL2, it's possible to attach USB devices to your Windows host and pass them through to the WSL instance using the open source project known as usbipd-win that Microsoft is advertising as the recommended path forward. With a single USB Coral, my inferencing times average about 15-17ms vs. the 75-80ms I had with two CPUs.

But when it comes to setting this up. Things seem to be ever so slightly different based on whether you are running Windows 10 vs. Windows 11 per the Microsoft documentation.

Windows 10: Seems like it requires some setup
Windows 11: Seems like it just works out of the box

The good news is that the Windows 10 setup is in fact pretty minimal

Intall the usbipd-win msi to your Windows host (v3.2.0 at the time of this writing)
Once installed, open a terminal on Windows. Issue the following command which should return any attached USB devices on your Windows host:

usbipd wsl list

At this point, the Windows side of things are done. Now we need to configure WSL instance so it can receive/listen to when we mount the USB Coral. But it's worth calling out some conflicting documentation here and which one to choose.

The Microsoft documentation listed above in the Install the USBIP tools and hardware database in Linux tells you to issue:

sudo apt install linux-tools-generic hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip /usr/lib/linux-tools/*-generic/usbip 20

The usbipd-win WSL Support documentation tells you to issue:

sudo apt install linux-tools-virtual hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip `ls /usr/lib/linux-tools/*/usbip | tail -n1` 20

Specifically, the very first line in those respective commands is the only problem I ran into. Note the very small difference of "generic" vs. "virtual" in those commands. When I followed the Microsoft documentation, the command starts returning output before eventually throwing an error that the listed dependencies/packages can't be found. But following the usbipd-win WSL Support documentation, everything works as expected. So I'm going to advise that you use the usbipd-win documentation's respective commands. To do that:

Open a terminal to your WSL instance. Verify the kernel version returned is 5.10.60.1 or greater:

uname -a

In the same terminal connected to your WSL instance, install USB/IP client tools

sudo apt install linux-tools-virtual hwdata
sudo update-alternatives --install /usr/local/bin/usbip usbip `ls /usr/lib/linux-tools/*/usbip | tail -n1` 20

Back in your Windows terminal (step 2, above) find the Bus ID of the attached Coral device. If you aren't sure which is the Coral device. Unplug it, run the command, plug the Coral in, run it again and spot the difference.
(OPTIONAL) If you received a warning somewhere along the way in a Windows terminal about needing to use bind and force commands. Make sure you run those first and no less from an administrative terminal in Windows. Run the following where IDENTIFIERHERE is the Bus ID of the Coral. For example, usbipd wsl attach --busid 4-3

usbipd wsl bind --force --busid IDENTIFIERHERE

From an administrative terminal in Windows, run ONE of the two following commands. For example, usbipd wsl attach --busid 4-3 --auto-attach.

usbipd wsl attach --busid IDENTIFIERHERE --auto-attach
usbipd wsl attach --hardware-id VID:PID --auto-attach

Verify the Coral USB is mounted with the following commands in Windows and WSL. You should see a device that cites the Google Coral USB Accelerator in the name/description of the result. If you don't see this, unattach the device, and reattach. It's crucial this device shows correctly mounted, otherwise docker will never serve it correctly to the Frigate container.

From Windows

usbipd wsl list

From WSL

lsusb

At this point, modify your Frigate configuration to use the Google Coral detector(s) per Frigate documentation of Edge-TPU Detector. Restart Frigate with the new config, head over to Logs/System to verify Frigate has picked up your Coral and you're done!

Using Nvidia GPUs and TensorRT Detectors

With the advent of Frigate 0.12, not only can you use your Nvidia GPU for Hardware Acceleration as outlined above. But also as your detectors. When I began using Frigate, I allocated two CPUs to it. They each averaged about 75-80ms inferencing time. With an Nvidia GTX1080, inferencing time now averages 5-7ms. Before we get started, if Frigate is currently running in Docker/WSL you'll want to stop the container before starting model training, much less building the needed TensorRT specific container for Frigate. Secondly, if this is your only GPU and you enjoy gaming. You might experience decreased frame rates and less than optimal gaming performance while the Frigate container is utilizing GPU inferencing.

Open up a shell to your WSL instance. I personally use Windows Terminal to make bouncing between my Windows host and Ubuntu/WSL instance easier to keep track of. Then follow the documentation for generating models by running the following commands at the WSL command line.

mkdir trt-models
wget https://github.com/blakeblackshear/frigate/raw/master/docker/tensorrt_models.sh
chmod +x tensorrt_models.sh

At this point, if you use File Explorer you can go into WSL and verify the folder was created and tensorrt_models.sh are both in your \\wsl$\Ubuntu\home\YOURUSERNAMEHERE directory.

Let's head back to your WSL command line. Then we'll run the final command to begin training

docker run --gpus=all --rm -it -v `pwd`/trt-models:/tensorrt_models -v `pwd`/tensorrt_models.sh:/tensorrt_models.sh nvcr.io/nvidia/tensorrt:22.07-py3 /tensorrt_models.sh

If your card doesn't support FP16 operations you might see some warnings get generated from running the above. In which case, you can just delete the files and start over. You can do that with:

sudo rm -rf trt-models/

Let's try it one more time, with a single additional argument per the documentation of "-e USE_FP16=False"

docker run --gpus=all --rm -it -v `pwd`/trt-models:/tensorrt_models -v `pwd`/tensorrt_models.sh:/tensorrt_models.sh nvcr.io/nvidia/tensorrt:22.07-py3 /tensorrt_models.sh -e USE_FP16=False

Once you return to a blinking command line, your models are trained and your GPU is ready to go. We just need to do some slight alteration of the Docker Compose from above.

First, we need to use a Tensor RT specific instance of Frigate
BEFORE

image: ghcr.io/blakeblackshear/frigate:stable

AFTER

image: ghcr.io/blakeblackshear/frigate:stable-tensorrt

Second, we need to introduce a new line item to our Volumes section:
BEFORE

- \\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- ./config:/config
- ./media:/media/frigate

AFTER

- \\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- ./config:/config
- ./media:/media/frigate
- \\wsl$$\Ubuntu\home\USERNAME\trt-models:/trt-models:ro

Once again, please note that the config and media paths above will work. But you may have alternative paths/choose to set them elsewhere such as the following:

\\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
./config:/config
T:\frigatemedia:/media/frigate
\wsl$$\Ubuntu\home\USERNAME\trt-models:/trt-models:ro

Then we'll use "docker-compose up -d" at the Windows PowerShell command line in the directory the compose file is located to rebuild the container using the new compose that makes use of the GPU and TensorRT instance of Frigate. Once Frigate starts, you'll want to update your config.yml/detectors section per the documentation. Once you've done this, save your config, and then restart Frigate to finalize your flip towards TensorRT based inferencing.

You can verify things are running smoothly by heading into Logs and ensuring you don't see errors. Finally, check out System to see

Just wanted to throw this out there and hope someone finds it helpful.

NickM-27 · 2022-11-11T18:29:51Z

NickM-27
Nov 11, 2022
Collaborator Sponsor

Thanks for the post! Have you been able to get your GPU passed in for hardware acceleration? That's another important part 👍

10 replies

MinimumDowntime Dec 21, 2022
Author

Updated to include how to create a WSL Config file to cap resources for the WSL instance.

MinimumDowntime Jul 18, 2023
Author

Updated to reflect Frigate 0.12 and alternative ways of passing the DEPLOY section for Nvidia GPUs

MinimumDowntime Jul 18, 2023
Author

Updated to include Nvidia TensorRT inferencing within WSL

MinimumDowntime Sep 1, 2023
Author

~~Updated to include using USB Coral Accelerator within WSL~~

Unfortunately, it looks like despite this initially running successfully. Errors are thrown in Frigate that line up with the random disconnects that happens between Windows and WSL as cited in Frigate/USBIP communities.

MinimumDowntime Nov 22, 2023
Author

Been running with a USB Coral the last several days with only the occasional container crash/restart. It looks as though nine days after I updated my previous comment directly above, I completely missed that usbipd-win released 3.2.0 which seems to have got the Google Coral USB looks to be fairly stable within WSL. The following both happen sporadically in Frigate:

Occasionally Frigate restarts the detection service. Total downtime is about 4-5 seconds. Apart from a smooth startup and finding the TPU, logs go as follows:
- HandleQueuedBulkIn transfer in failed. Invalid argument: USB transfer error 4 [LibUsbDataInCallback]
- Fatal Python error: Aborted
- Two Thread errors (paraphrasing this)
- Detection appears to be stuck. Restarting detection process...
The container crashed once or twice, and self-restarts

So again, this seems to be functional and Frigate seems to be running with ...uhh. I can't believe this fits... minimum downtime.

It's worth calling out that this experience is SLIGHTLY different than the original scenario wherein the [LibUsbDataInCallback] occurred, and then Windows would detach the Coral USB from WSL. Now at least Windows keeps the Coral mounted throughout both of the above bullet points within Frigate. Documentation above has been updated to reflect all of this.

WhiteNoseThunderPants · 2022-12-21T16:10:06Z

WhiteNoseThunderPants
Dec 21, 2022

This is awesome, has anyone done this with an intel gpu and a google coral yet?

7 replies

enzo2 Dec 21, 2022

What would be the equivalent command like nvidia-smi for integrated Intel GPUs, and for AMD/Radeon? (I have both)

NickM-27 Dec 21, 2022
Collaborator Sponsor

intel_gpu_top and radeontop

Aryankids Feb 17, 2023

I am running WSL2 for a couple of years for my Home Assistant. As we all know Frigate integrates very well with HA. But all my attempts to pass through a USB from the host (windows) failed.
You might like to know, I could manage to make a USB available to WSL2 using USBIP_WSL but when I tried to use Coral on top of it that miserably fails. I raised a couple of bugs on both sides i.e. Google Coral and USBIP but it seems there is no intention for any of these teams to get the issue sorted. HTH.

MinimumDowntime Sep 1, 2023
Author

~~Just wanted to provide an update to this thread that I have a Google Coral USB Accelerator successfully working in WSL and being utilized by Frigate.~~

Correction. After a few hours it looks like I'm in the same camp with everyone else. Errors thrown now line up with comments experienced in the Frigate and USBIP GitHub communities

MinimumDowntime Nov 22, 2023
Author

Wanted to update this thread that since usbipd-win 3.2.0 was released, passing a USB Coral into WSL is more stable. Frigate has some sporadic issues, but it is functional. Documentation has been updated above to reflect this.

Mehrez13 · 2023-05-07T21:00:11Z

Mehrez13
May 7, 2023

hello, I have some issue in my docker-compose file but can find where is the probleme. Can you help me?

version: "3.9"
services:
frigate:
container_name: frigate
#privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "64mb" # update for your cameras based on calculation above
volumes:
- \wsl$$\Ubuntu-18.04\etc\localtime:/etc/localtime:ro
- \wsl$$\Ubuntu-18.04\home\hicham\frigate\config.yml:/config/config.yml:ro
- \wsl$$\Ubuntu-18.04\home\hicham\frigate:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "PASSWORD"

1 reply

NickM-27 May 8, 2023
Collaborator Sponsor

You need to provide logs or something otherwise there's no way to help

backcountrymountains · 2023-08-05T15:05:16Z

backcountrymountains
Aug 5, 2023

There is also the possibility of creating a Hyper-V Debian VM and using DDA to pass through an entire PCIe coral device. I don't think the VM is using /dev/dri/card0 (the virtual graphics interface provided by Hyper-V) for decode but my hypervisor CPU usage is 2% at idle. My inference time is ~7ms. I'm only running one stream at 2304x1296. It's a Lenovo desktop with an i7-12700 and 64 GB ram.

Result of DDA survey (powershell survey-dda.ps1):

Coral PCIe Accelerator
Express Endpoint -- more secure.
    And its interrupts are message-based, assignment can work.
PCIROOT(0)#PCI(1C04)#PCI(0000)

My devices in docker compose:

devices:
      - /dev/apex_0:/dev/apex_0 
      - /dev/dri/card0

This is the table in the frigate/system tab:

Process	P-ID	FPS	CPU %	Memory %
ffmpeg	11423	5.2	18.9%	1.3%
Capture	529	5.2	2.0%	0.7%
Detect	514	0 (0 skipped)	0.3%	0.9%

The VM is set up to use 10 processors. The CPU of ffmpeg here results in only 2% CPU usage on the Hypervisor.

VAINFO in the frigate/system tab returns:

error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/hyperv_drm_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

1 reply

MinimumDowntime Aug 7, 2023
Author

Well that's awesome to see someone has made progress on the DDA (Discrete Device Assignment) front 😄

backcountrymountains · 2023-08-07T22:58:20Z

backcountrymountains
Aug 7, 2023

What's unfortunate is that GPU-PV doesn't play nice with DDA in Hyper-V VMs (ffmpeg -hwaccel cuda segfaults) so I can't get hardware encode/decode unless I DDA a discrete video device. WSL works amazingly well with GPU-PV (jellyfin!) but has no DDA functionality to pass through a Coral. I can get the tensorrt detection working in WSL but it makes my GPU work a bit more than I'd like and I'm trying to do other stuff with it (Baldur's Gate 3!).

I'm hoping that WSL getting VAAPI might allow me to use the Intel iGPU in a Hyper-V VM so I can use hardware acceleration encode/decode.

I just want one computer that can do all of the things! Someday.

1 reply

MinimumDowntime Aug 9, 2023
Author

Baldur's Gate 3!

hah. I don't play, but I absolutely get the reference/hardware requirements point you're making. Also, good idea. I've updated the TensorRT section above to highlight you might experience some gaming performance woes whilst utilizing GPU inferencing.

I'm hoping that WSL getting VAAPI might allow me to use the Intel iGPU in a Hyper-V VM so I can use hardware acceleration encode/decode.

Oh! Now THAT is a great idea! Glad to see someone else out there playing in this very specific Windows oriented space. If you make any progress it sounds deserving of its own Show n Tell thread 😃

justinhsa · 2023-10-04T04:11:52Z

justinhsa
Oct 4, 2023

Hello, when running "docker-compose up -d" in WSL Ubuntu, I got the following:

[+] Building 0.0s (0/0) docker:default [+] Running 0/0 ⠋ Container frigate Creating 0.0s Error response from daemon: create \\wsl$\Ubuntu\etc\localtime: "\\\\wsl$\\Ubuntu\\etc\\localtime" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path

How do I modify the volume paths in my docker-compose.yml to avoid this error? Any help would be appreciated. Host OS is Win11 22H2, and the Docker Desktop version is v4.24.0. My docker-compose.yml:

version: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:0.13.0-beta2
shm_size: "64mb" # update for your cameras based on calculation above
devices:
volumes:
- \\wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- \\wsl$$\Ubuntu\home\justinhsa\frigate\config.yml:/config/config.yml
- \\wsl$$\Ubuntu\home\justinhsa\frigate\clips:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 1000000000
ports:
- "5000:5000"
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "abcdefgh"

2 replies

justinhsa Oct 4, 2023

Never mind. Figured out I have to run "docker-compose up -d" in Windows Powershell, not in Ubuntu shell.

MinimumDowntime Oct 4, 2023
Author

Glad to hear you got this sorted. I've gone ahead and updated the post above to call this out for others who may venture down this path. Thanks for your help!

smith3d · 2023-11-07T15:54:49Z

smith3d
Nov 7, 2023

Hi there,

I'm getting error not a valid Windows Path

PS D:\docker\frigate> docker-compose up -d
[+] Building 0.0s (0/0) docker:default
[+] Running 0/0

Container frigate-devcontainer Creating 0.0s
Error response from daemon: \wsl$\Ubuntu\home\USERNAME\frigate\config.yml%!(EXTRA string=is not a valid Windows path)
PS D:\docker\frigate>

seems like i can't use

volumes:
  - \\wsl$$\Ubuntu\home\USERNAME\frigate\config.yml:/config/config.yml
  - \\wsl$$\Ubuntu\home\USERNAME\frigate\clips:/media/frigat
  
 I have been using Frigate on my Windows 11, somehow since the last update, it break the docker.

2 replies

rodrigoratan Nov 10, 2023

I use relative paths:

volumes:
- /etc/localtime:/etc/localtime:ro
- ../frigate_config:/config:rw
- ../frigate_data/media:/media/frigate:rw
- ../frigate_data/db:/db:rw

frigate_config and frigate_data should be placed in the same parent folder where frigate with docker composer is.

MinimumDowntime Nov 10, 2023
Author

I use relative paths:

Huh. How about that. I was so focused trying to make this work initially, I never thought to try this. Excellent work @rodrigoratan 👍

kshweikeh · 2023-11-16T06:25:29Z

kshweikeh
Nov 16, 2023

I have a problem that the UI keeps loading on port 5000
and here is the log :

2023-11-16 09:20:33 Traceback (most recent call last):
2023-11-16 09:20:33 File "/usr/local/go2rtc/create_config.py", line 23, in
2023-11-16 09:20:33 with open(config_file) as f:
2023-11-16 09:20:33 FileNotFoundError: [Errno 2] No such file or directory: '/config/config.yml'
2023-11-16 09:20:32 2023-11-16 06:20:32.948214443 [INFO] Preparing go2rtc config...
2023-11-16 09:20:32 2023-11-16 06:20:32.948833456 [INFO] Starting Frigate...
2023-11-16 09:20:32 2023-11-16 06:20:32.949619722 [INFO] Starting NGINX...
2023-11-16 09:20:33 2023-11-16 06:20:33.183227691 [INFO] The go2rtc service exited with code 1 (by signal 0)
2023-11-16 09:20:33 2023-11-16 06:20:33.955265296 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.955269064 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.955270526 *** Your config file is not valid! ***
2023-11-16 09:20:33 2023-11-16 06:20:33.955271855 *** Please check the docs at ***
2023-11-16 09:20:33 2023-11-16 06:20:33.955272812 *** https://docs.frigate.video/configuration/index ***
2023-11-16 09:20:33 2023-11-16 06:20:33.955273986 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.955274801 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.955300059 *** Config Validation Errors ***
2023-11-16 09:20:33 2023-11-16 06:20:33.955300966 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.955301660 [Errno 2] No such file or directory: '/config/config.yml'
2023-11-16 09:20:33 2023-11-16 06:20:33.956736719 [2023-11-16 06:20:33] frigate.app INFO : Starting Frigate (0.12.1-367d724)
2023-11-16 09:20:33 2023-11-16 06:20:33.956934921 Traceback (most recent call last):
2023-11-16 09:20:33 2023-11-16 06:20:33.956937018 File "/opt/frigate/frigate/app.py", line 351, in start
2023-11-16 09:20:33 2023-11-16 06:20:33.956937918 self.init_config()
2023-11-16 09:20:33 2023-11-16 06:20:33.956938780 File "/opt/frigate/frigate/app.py", line 80, in init_config
2023-11-16 09:20:33 2023-11-16 06:20:33.956939495 user_config = FrigateConfig.parse_file(config_file)
2023-11-16 09:20:33 2023-11-16 06:20:33.956940305 File "/opt/frigate/frigate/config.py", line 1070, in parse_file
2023-11-16 09:20:33 2023-11-16 06:20:33.956940968 with open(config_file) as f:
2023-11-16 09:20:33 2023-11-16 06:20:33.956941733 FileNotFoundError: [Errno 2] No such file or directory: '/config/config.yml'
2023-11-16 09:20:33 2023-11-16 06:20:33.956942317
2023-11-16 09:20:33 2023-11-16 06:20:33.956943086 *************************************************************
2023-11-16 09:20:33 2023-11-16 06:20:33.956943913 *** End Config Validation Errors ***
2023-11-16 09:20:33 2023-11-16 06:20:33.956944688 *************************************************************
2023-11-16 09:20:34 2023-11-16 06:20:34.198030496 [INFO] Preparing go2rtc config...
2023-11-16 09:20:34 Traceback (most recent call last):
2023-11-16 09:20:34 File "/usr/local/go2rtc/create_config.py", line 23, in
2023-11-16 09:20:34 with open(config_file) as f:
2023-11-16 09:20:34 FileNotFoundError: [Errno 2] No such file or directory: '/config/config.yml'
2023-11-16 09:20:34 2023-11-16 06:20:34.394672251 [INFO] The go2rtc service exited with code 1 (by signal 0)
2023-11-16 09:20:35 2023-11-16 06:20:35.046751189 172.17.0.1 - - [16/Nov/2023:06:20:35 +0000] "GET / HTTP/1.1" 200 6641 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.0.0" "-"
2023-11-16 09:20:35 2023-11-16 06:20:35.087189189 2023/11/16 06:20:35 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: , request: "GET /api/config HTTP/1.1", upstream: "http://127.0.0.1:5001/config", host: "localhost:5000", referrer: "http://localhost:5000/"
2023-11-16 09:20:35 2023-11-16 06:20:35.087194205 172.17.0.1 - - [16/Nov/2023:06:20:35 +0000] "GET /api/config HTTP/1.1" 502 559 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.0.0" "-"
2023-11-16 09:20:35 2023-11-16 06:20:35.129823269 [INFO] Service Frigate exited with code 1 (by signal 0)
2023-11-16 09:20:35 s6-rc: info: service legacy-services: stopping
2023-11-16 09:20:35 s6-rc: info: service legacy-services successfully stopped
2023-11-16 09:20:35 s6-rc: info: service nginx: stopping
2023-11-16 09:20:35 s6-rc: info: service go2rtc-healthcheck: stopping
2023-11-16 09:20:35 2023-11-16 06:20:35.141917306 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2023-11-16 09:20:35 s6-rc: info: service go2rtc-healthcheck successfully stopped
2023-11-16 09:20:35 2023-11-16 06:20:35.342473179 [INFO] Service NGINX exited with code 0 (by signal 0)
2023-11-16 09:20:35 s6-rc: info: service nginx successfully stopped
2023-11-16 09:20:35 s6-rc: info: service nginx-log: stopping
2023-11-16 09:20:35 s6-rc: info: service frigate: stopping
2023-11-16 09:20:35 s6-rc: info: service frigate successfully stopped
2023-11-16 09:20:35 s6-rc: info: service go2rtc: stopping
2023-11-16 09:20:35 s6-rc: info: service frigate-log: stopping
2023-11-16 09:20:35 s6-rc: info: service nginx-log successfully stopped
2023-11-16 09:20:35 s6-rc: info: service go2rtc successfully stopped
2023-11-16 09:20:35 s6-rc: info: service go2rtc-log: stopping
2023-11-16 09:20:35 s6-rc: info: service frigate-log successfully stopped
2023-11-16 09:20:35 s6-rc: info: service go2rtc-log successfully stopped
2023-11-16 09:20:35 s6-rc: info: service log-prepare: stopping
2023-11-16 09:20:35 s6-rc: info: service s6rc-fdholder: stopping
2023-11-16 09:20:35 s6-rc: info: service log-prepare successfully stopped
2023-11-16 09:20:35 s6-rc: info: service legacy-cont-init: stopping
2023-11-16 09:20:35 s6-rc: info: service s6rc-fdholder successfully stopped
2023-11-16 09:20:35 s6-rc: info: service legacy-cont-init successfully stopped
2023-11-16 09:20:35 s6-rc: info: service fix-attrs: stopping
2023-11-16 09:20:35 s6-rc: info: service fix-attrs successfully stopped
2023-11-16 09:20:35 s6-rc: info: service s6rc-oneshot-runner: stopping
2023-11-16 09:20:35 s6-rc: info: service s6rc-oneshot-runner successfully stopped

And I am pretty sure about the path of my config file
How can I fix this problem

1 reply

MinimumDowntime Nov 18, 2023
Author

I cannot stress enough how much I'm not trying to insult your intelligence when I ask "Are you sure about the location of the config file?" I would double check this by navigating to the UNC path.

I ask because the log very much suggests that is the issue. But having made several mistakes when I was originally trying to get this going/simultaneously draft this thread. I thought it might be worth sharing some of my own initial troubleshooting and observations before I even started this thread. Here are some of my initial 🤦‍♂️

I accidentally created a folder called "config.yml"
The above also led to getting some of the folder structure wrong between tries of getting it initially running
Once I had the config path set, the errors I started receiving were more along the lines of required configuration in the file that were missing

But even if port 5000 is ever so briefly hosting Frigate, the good news is that it sounds like you're close.

m-laj · 2024-01-25T05:03:07Z

m-laj
Jan 25, 2024

Thank you for these comprehensive instructions. Saved me many hours!

I am running Windows 11 / WSL2 and have had success passing the Coral USB to WSL2 using the command:

usbipd attach --busid IDENTIFIERHERE --auto-attach --wsl

The problem I'm running into is that this command needs to be given every time the machine starts up or the USB device is not passed through to WSL (and so far I've failed to get this to work as a Task Scheduler task).

Is this to be expected? Any ideas on how to handle this?

3 replies

MinimumDowntime Feb 2, 2024
Author

My apologies on the delay in response. Always great to hear when your work has helped someone else 😄

I too recently ran into this (3 days ago!) and haven't spent a great deal of time troubleshooting other than the pseduo-code that feels like:

On startup (or on login, whichever is cleaner)
Start a PowerShell script
That PowerShell script should be a loop that checks for the availability of WSL as WSL is not immediately available
Once WSL is available, mount the Coral

I'll try to see if I can get this going this weekend or sooner. In meantime, I'll update the discussion above. Thanks again for your kind words and help 👍

MinimumDowntime Feb 3, 2024
Author

Alright, spent the last few hours on this and figured I'd update this thread with my experience so far.

When I originally got this working, it was done with usbipd v3.2. As of usbipd v4+, "sharing a device is persistent; it survives reboots.". This obviously gave me some hope as I was looking at it, so I went ahead with upgrading. But rebooting my Windows host results in a technicality:

The device remains shared after a reboot
The device does not attach after a reboot

But upon a complete reading of usbipd's readme, it does qualify that:

Attaching devices to a client is non-persistent. You will have to re-attach after a reboot, or when the device resets or is physically unplugged/replugged.

All of that said, here's where I'm at with things:

I will update the discussion above with new installation steps once I've had this running successfully for a couple days with usbipd 4.1
- A few steps above need to be updated to reflect changes in usbipd v4.1 (for example, client side tooling is no longer required. Which means no conflicting documentation to deal with and thus, no modifications to WSL required to get this going. All resulting in making things for people getting started with this.)
- The syntax of the commands has changed
I will resume auto-attach testing once I complete the previous step

MinimumDowntime Feb 26, 2024
Author

Just reporting back in. Thus far, I haven't been able to reliably do this post reboot. For the sake of thinking aloud, it feels like there are a few possible hooks we'd care about in this process.

A script that loops for 5 or so minutes after user logon
- this is just playing the odds
A script that looks for WSL availability
- this seems like the most fitting thing, but I'm having trouble reliably parsing output/errors in powershell
A script that looks for Docker container status
- this seems too late, the container is always going to try to start/be starting. So this becomes, if it's in a status of start/starting then we are assuming WSL is available and it's failing to find the missing TPU

From my limited understanding of Docker, if there was a script associated with the compose/container it would execute in the context of the container/WSL and not the physical Windows host

Open to suggestions/discussion.

j2eubank · 2024-02-15T19:23:54Z

j2eubank
Feb 15, 2024

have followed directions for coral tpu and can see the device in both windows and wsl (the vid is correct, comes as global unichip corp in wsl) but upon container start frigate is telling me it can't find the tpu.

Any ideas for troubleshooting?

2024-02-15 13:16:53.175712047 [2024-02-15 13:16:49] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb
frigate | 2024-02-15 13:16:53.175985145 [2024-02-15 13:16:53] frigate.detectors.plugins.edgetpu_tfl ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
frigate | 2024-02-15 13:16:53.175987745 Process detector:coral:
frigate | 2024-02-15 13:16:53.176866438 Traceback (most recent call last):
frigate | 2024-02-15 13:16:53.176868838 File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate
frigate | 2024-02-15 13:16:53.176892638 delegate = Delegate(library, options)
frigate | 2024-02-15 13:16:53.176894438 File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in init
frigate | 2024-02-15 13:16:53.176897338 raise ValueError(capture.message)
frigate | 2024-02-15 13:16:53.176909738 ValueError
frigate | 2024-02-15 13:16:53.176938138
frigate | 2024-02-15 13:16:53.176939838 During handling of the above exception, another exception occurred:
frigate | 2024-02-15 13:16:53.176940738
frigate | 2024-02-15 13:16:53.176941838 Traceback (most recent call last):
frigate | 2024-02-15 13:16:53.176942938 File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
frigate | 2024-02-15 13:16:53.176943838 self.run()
frigate | 2024-02-15 13:16:53.176945038 File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run
frigate | 2024-02-15 13:16:53.176946038 self._target(*self._args, **self._kwargs)
frigate | 2024-02-15 13:16:53.176947838 File "/opt/frigate/frigate/object_detection.py", line 102, in run_detector
frigate | 2024-02-15 13:16:53.176949438 object_detector = LocalObjectDetector(detector_config=detector_config)
frigate | 2024-02-15 13:16:53.176950638 File "/opt/frigate/frigate/object_detection.py", line 53, in init
frigate | 2024-02-15 13:16:53.176951738 self.detect_api = create_detector(detector_config)
frigate | 2024-02-15 13:16:53.176964238 File "/opt/frigate/frigate/detectors/init.py", line 18, in create_detector
frigate | 2024-02-15 13:16:53.176965238 return api(detector_config)
frigate | 2024-02-15 13:16:53.176966738 File "/opt/frigate/frigate/detectors/plugins/edgetpu_tfl.py", line 41, in init
frigate | 2024-02-15 13:16:53.176967938 edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
frigate | 2024-02-15 13:16:53.176975637 File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate
frigate | 2024-02-15 13:16:53.176976937 raise ValueError('Failed to load delegate from {}\n{}'.format(
frigate | 2024-02-15 13:16:53.176978337 ValueError: Failed to load delegate from libedgetpu.so.1.0

9 replies

MinimumDowntime Feb 15, 2024
Author

You're welcome 😄

MinimumDowntime Apr 5, 2024
Author

I forgot to follow up on this! In my casual searching, I came across the following thread:

google-coral/edgetpu#536

I haven't tried the suggested workarounds yet, but this sounds A LOT LIKE what we've both experienced.

j2eubank Apr 6, 2024

Yeah, this sounds the same. It's very odd behavior, I've only had it happen twice and a detach resolves
I'm going to give this a try though.

jimmyhhnguyen Apr 18, 2024

I've tried detaching and attaching a dozen times, and the company name never changes to Google. Is there another workaround for this?

j2eubank Apr 18, 2024

Attach and be sure to run lsusb in wsl to ensure you see it (even though named incorrectly). Start frigate and you should see it likely fail to start in the logs (no edge tpu found). Stop frigate, detach and attach it again.

qubanga · 2024-03-19T10:40:34Z

qubanga
Mar 19, 2024

Thanks a lot for this guide. I have followed it to get Nvidia hwaccell for decode/encode which works like a charm.

However I struggle to get the detect hw support working with tensorrt.

nvidia-smi in WSL outputs:

Which seem to indicate that the GPU is available in WSL.

The frigate log have no errors an talks about GPU:
2024-03-19 11:21:09.803064075 [INFO] Preparing Frigate...
2024-03-19 11:21:09.812231375 [INFO] Starting Frigate...
2024-03-19 11:21:11.053611729 [2024-03-19 11:21:11] frigate.app INFO : Starting Frigate (0.13.2-6476f8a)
2024-03-19 11:21:11.330288519 [2024-03-19 11:21:11] peewee_migrate.logs INFO : Starting migrations
2024-03-19 11:21:11.334376718 [2024-03-19 11:21:11] peewee_migrate.logs INFO : There is nothing to migrate
2024-03-19 11:21:11.338941318 [2024-03-19 11:21:11] frigate.app INFO : Recording process started: 309
2024-03-19 11:21:11.341232118 [2024-03-19 11:21:11] frigate.app INFO : go2rtc process pid: 98
2024-03-19 11:21:11.360333817 [2024-03-19 11:21:11] frigate.app INFO : Output process started: 320
2024-03-19 11:21:11.370507217 [2024-03-19 11:21:11] frigate.app INFO : Camera processor started for 932L_uthus: 325
2024-03-19 11:21:11.375717417 [2024-03-19 11:21:11] frigate.app INFO : Capture process started for 932L_uthus: 326
2024-03-19 11:21:11.497801612 [2024-03-19 11:21:11] detector.tensorrt INFO : Starting detection process: 318
2024-03-19 11:21:11.739667803 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : Loaded engine size: 146 MiB
2024-03-19 11:21:11.895866998 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +6, GPU +8, now: CPU 272, GPU 1132 (MiB)
2024-03-19 11:21:11.903295097 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuDNN: CPU +1, GPU +8, now: CPU 273, GPU 1140 (MiB)
2024-03-19 11:21:11.912355797 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] TensorRT-managed allocation in engine deserialization: CPU +0, GPU +145, now: CPU 0, GPU 145 (MiB)
2024-03-19 11:21:11.925092297 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +8, now: CPU 127, GPU 1132 (MiB)
2024-03-19 11:21:11.925202097 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuDNN: CPU +1, GPU +8, now: CPU 128, GPU 1140 (MiB)
2024-03-19 11:21:11.926734897 [2024-03-19 11:21:11] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] TensorRT-managed allocation in IExecutionContext creation: CPU +0, GPU +30, now: CPU 0, GPU 175 (MiB)

However the system tab in frigate says no GPU detected but says tensorrt is used and the interference speed is better than with default CPU but not on pair with a 1070 GPU.

Does anyone have any pointers to what is going on? Any more logs I can look at?

2 replies

MinimumDowntime Apr 5, 2024
Author

This is unfortunately uncharted and unknown territory for me. I'm not sure I even understand how I could go about attempting to reproduce this.

callithrixx Sep 4, 2024

I had the exact same issue, but after doing a clean install of the latest nVidia Studio drivers it worked flawlessly, cpu usage has gone down exponentially and my gpu now shows up. Maybe it's a driver conflict that causes it.

bobloadmire · 2024-04-25T23:45:56Z

bobloadmire
Apr 25, 2024

trying to set this u on intel system, but unfortunately wsl intel_gpu_top returns "not found"

2 replies

j2eubank Apr 25, 2024

Did you run "wsl --install"

bobloadmire Apr 26, 2024

yes

itispip · 2024-05-31T12:34:29Z

itispip
May 31, 2024

Intel iGPU won't work; Even latest verison WSL2 host already supported iGPU VAAPI, but frigate docker under WSL2 still not.

0 replies

clintyip · 2024-06-11T12:12:01Z

clintyip
Jun 11, 2024

Tried the steps and it's working great - haven't yet tried the GPU passthrough to use for hw acceleration yet.

I have a current Frigate instance that's in an LXC container which seems to use significantly less CPU usage when using that to decode. I'm able to assign 3 cores to the LXC container and barely have it hit 50% usage

Whereas I have 4 cores assigned to the Windows VM and it's capping 99% usage with the exact same settings.

Is there something I'm doing differently?

0 replies

irharrier2 · 2024-06-12T18:29:52Z

irharrier2
Jun 12, 2024

For anyone who might have issue with hardware acceleration. I was getting ffmpeg errors the whole day. Turns out here is problem with Nvidia driver version 555, which prevents GPU acceleration to work with Docker Desktop below 4.31.
So either ensure you have the latest version of Docker Desktop or install a lower version of Nvidia driver.

1 reply

MinimumDowntime Aug 8, 2024
Author

Appreciate the insight!

TSTNVR · 2024-07-19T10:40:19Z

TSTNVR
Jul 19, 2024

I am able to connect to the web UI for a few seconds, then the container stops. Any help is greatly appreciated.

2024-07-19 15:22:12 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:12 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:12 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:12 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:12 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:12 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:12 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:12 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:12 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:12 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:12 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:12 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:12 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:12 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:12 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:12 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:12 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:12 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:12 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:12 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:12 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:12 s6-rc: info: service frigate: starting
2024-07-19 15:22:12 s6-rc: info: service frigate successfully started
2024-07-19 15:22:12 s6-rc: info: service nginx: starting
2024-07-19 15:22:12 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:13 s6-rc: info: service nginx successfully started
2024-07-19 15:22:13 s6-rc: info: service certsync: starting
2024-07-19 15:22:13 s6-rc: info: service certsync successfully started
2024-07-19 15:22:13 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:13 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:12 2024-07-19 15:22:12.056513358  [INFO] Preparing Frigate...
2024-07-19 15:22:12 2024-07-19 15:22:12.056534098  [ERROR] Frigate config file not found
2024-07-19 15:22:12 2024-07-19 15:22:12.057478355  [INFO] Starting NGINX...
2024-07-19 15:22:12 2024-07-19 15:22:12.060447555  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:12 2024-07-19 15:22:12.073084697  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-07-19 15:22:12 2024-07-19 15:22:12.112311000  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:12 2024-07-19 15:22:12.916586494  [INFO] Starting go2rtc...
2024-07-19 15:22:13 2024-07-19 15:22:13.083787467  15:22:13.083 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:22:13 2024-07-19 15:22:13.083833430  15:22:13.083 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:22:13 2024-07-19 15:22:13.084803872  15:22:13.084 INF [rtsp] listen addr=:8554
2024-07-19 15:22:13 2024-07-19 15:22:13.084807892  15:22:13.084 INF [api] listen addr=:1984
2024-07-19 15:22:13 2024-07-19 15:22:13.084813737  15:22:13.084 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:22:13 2024-07-19 15:22:13.702322639  [INFO] Starting certsync...
2024-07-19 15:22:13 2024-07-19 15:22:13.727435488  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:13 2024-07-19 15:22:13.730487579  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:13 2024-07-19 15:22:13.927166726  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:13 2024-07-19 15:22:13.932337117  exit with signal: terminated
2024-07-19 15:22:13 2024-07-19 15:22:13.936359027  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:22:13 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:13 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:13 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:13 s6-rc: info: service certsync: stopping
2024-07-19 15:22:13 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:13 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:13 s6-rc: info: service nginx: stopping
2024-07-19 15:22:13 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:13 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:13 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:13 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:13 s6-rc: info: service frigate: stopping
2024-07-19 15:22:13 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:13 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:13 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:13 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:13 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:13 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:13 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:13 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:13 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:13 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:13 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:13 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:13 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:13 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:13 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:13 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:13 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:13 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:18 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:18 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:18 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:18 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:18 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:18 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:18 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:18 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:18 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:18 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:18 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:18 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:18 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:18 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:18 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:18 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:18 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:18 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:18 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:18 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:18 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:18 s6-rc: info: service frigate: starting
2024-07-19 15:22:18 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:18 s6-rc: info: service frigate successfully started
2024-07-19 15:22:18 s6-rc: info: service nginx: starting
2024-07-19 15:22:20 s6-rc: info: service nginx successfully started
2024-07-19 15:22:20 s6-rc: info: service certsync: starting
2024-07-19 15:22:20 s6-rc: info: service certsync successfully started
2024-07-19 15:22:20 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:20 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:20 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:20 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:20 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:20 s6-rc: info: service certsync: stopping
2024-07-19 15:22:18 2024-07-19 15:22:18.923472909  [INFO] Preparing Frigate...
2024-07-19 15:22:18 2024-07-19 15:22:18.923598738  [ERROR] Frigate config file not found
2024-07-19 15:22:18 2024-07-19 15:22:18.927740603  [INFO] Starting NGINX...
2024-07-19 15:22:18 2024-07-19 15:22:18.928344578  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:18 2024-07-19 15:22:18.931350930  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:19 2024-07-19 15:22:19.327041403  [INFO] Starting go2rtc...
2024-07-19 15:22:19 2024-07-19 15:22:19.539533128  15:22:19.539 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:22:19 2024-07-19 15:22:19.539539281  15:22:19.539 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:22:19 2024-07-19 15:22:19.541627412  15:22:19.541 INF [rtsp] listen addr=:8554
2024-07-19 15:22:19 2024-07-19 15:22:19.541772923  15:22:19.541 INF [api] listen addr=:1984
2024-07-19 15:22:19 2024-07-19 15:22:19.542305099  15:22:19.541 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:22:20 2024-07-19 15:22:20.004766347  [INFO] Starting certsync...
2024-07-19 15:22:20 2024-07-19 15:22:20.037536302  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:20 2024-07-19 15:22:20.038116310  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:20 2024-07-19 15:22:20.197747938  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:20 2024-07-19 15:22:20.203811916  exit with signal: terminated
2024-07-19 15:22:20 2024-07-19 15:22:20.208616819  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:22:25 2024-07-19 15:22:25.274457347  [INFO] Preparing Frigate...
2024-07-19 15:22:25 2024-07-19 15:22:25.274525822  [ERROR] Frigate config file not found
2024-07-19 15:22:25 2024-07-19 15:22:25.274589765  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:25 2024-07-19 15:22:25.278797130  [INFO] Starting NGINX...
2024-07-19 15:22:25 2024-07-19 15:22:25.281115867  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:25 2024-07-19 15:22:25.389423865  [INFO] Starting certsync...
2024-07-19 15:22:25 2024-07-19 15:22:25.403506969  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:25 2024-07-19 15:22:25.405067115  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:25 2024-07-19 15:22:25.566762947  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:25 2024-07-19 15:22:25.574892986  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:22:20 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:20 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:20 s6-rc: info: service nginx: stopping
2024-07-19 15:22:20 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:20 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:20 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:20 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:20 s6-rc: info: service frigate: stopping
2024-07-19 15:22:20 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:20 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:20 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:20 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:20 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:20 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:20 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:20 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:20 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:20 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:20 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:20 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:20 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:20 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:20 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:20 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:20 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:20 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:25 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:25 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:25 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:25 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:25 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:25 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:25 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:25 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:25 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:25 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:25 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:25 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:25 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:25 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:25 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:25 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:25 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:25 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:25 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:25 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:25 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:25 s6-rc: info: service frigate: starting
2024-07-19 15:22:25 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:25 s6-rc: info: service frigate successfully started
2024-07-19 15:22:25 s6-rc: info: service nginx: starting
2024-07-19 15:22:25 s6-rc: info: service nginx successfully started
2024-07-19 15:22:25 s6-rc: info: service certsync: starting
2024-07-19 15:22:25 s6-rc: info: service certsync successfully started
2024-07-19 15:22:25 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:25 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:25 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:25 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:25 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:25 s6-rc: info: service certsync: stopping
2024-07-19 15:22:25 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:25 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:25 s6-rc: info: service nginx: stopping
2024-07-19 15:22:25 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:25 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:25 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:25 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:25 s6-rc: info: service frigate: stopping
2024-07-19 15:22:25 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:25 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:25 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:25 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:25 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:25 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:25 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:25 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:25 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:25 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:25 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:25 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:25 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:25 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:25 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:25 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:25 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:25 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:30 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:30 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:30 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:30 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:30 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:30 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:30 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:30 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:30 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:30 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:30 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:30 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:30 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:30 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:30 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:30 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:30 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:30 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:30 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:30 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:30 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:30 s6-rc: info: service frigate: starting
2024-07-19 15:22:30 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:30 s6-rc: info: service frigate successfully started
2024-07-19 15:22:30 s6-rc: info: service nginx: starting
2024-07-19 15:22:31 s6-rc: info: service nginx successfully started
2024-07-19 15:22:31 s6-rc: info: service certsync: starting
2024-07-19 15:22:31 s6-rc: info: service certsync successfully started
2024-07-19 15:22:31 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:31 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:31 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:31 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:31 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:31 s6-rc: info: service certsync: stopping
2024-07-19 15:22:31 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:31 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:31 s6-rc: info: service nginx: stopping
2024-07-19 15:22:31 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:31 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:31 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:31 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:31 s6-rc: info: service frigate: stopping
2024-07-19 15:22:31 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:31 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:31 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:31 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:31 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:31 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:31 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:31 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:31 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:31 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:31 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:31 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:31 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:31 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:31 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:30 2024-07-19 15:22:30.643976185  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:30 2024-07-19 15:22:30.645559370  [INFO] Starting NGINX...
2024-07-19 15:22:30 2024-07-19 15:22:30.647081738  [INFO] Preparing Frigate...
2024-07-19 15:22:30 2024-07-19 15:22:30.647254259  [ERROR] Frigate config file not found
2024-07-19 15:22:30 2024-07-19 15:22:30.652136644  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:31 2024-07-19 15:22:31.105323804  [INFO] Starting go2rtc...
2024-07-19 15:22:31 2024-07-19 15:22:31.336816929  15:22:31.336 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:22:31 2024-07-19 15:22:31.336822886  15:22:31.336 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:22:31 2024-07-19 15:22:31.337304403  15:22:31.337 INF [api] listen addr=:1984
2024-07-19 15:22:31 2024-07-19 15:22:31.338079633  15:22:31.337 INF [rtsp] listen addr=:8554
2024-07-19 15:22:31 2024-07-19 15:22:31.338498510  15:22:31.338 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:22:31 2024-07-19 15:22:31.730854313  [INFO] Starting certsync...
2024-07-19 15:22:31 2024-07-19 15:22:31.744653892  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:31 2024-07-19 15:22:31.746134650  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:31 2024-07-19 15:22:31.937384619  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:31 2024-07-19 15:22:31.943338502  exit with signal: terminated
2024-07-19 15:22:31 2024-07-19 15:22:31.947345749  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:22:37 2024-07-19 15:22:37.366578616  [INFO] Preparing Frigate...
2024-07-19 15:22:37 2024-07-19 15:22:37.366663213  [ERROR] Frigate config file not found
2024-07-19 15:22:37 2024-07-19 15:22:37.370088469  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:37 2024-07-19 15:22:37.372407676  [INFO] Starting NGINX...
2024-07-19 15:22:37 2024-07-19 15:22:37.377002786  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:37 2024-07-19 15:22:37.473932671  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET / HTTP/1.1" 200 2652 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.613325203  2024/07/19 15:22:37 [error] 159#159: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.613333417  2024/07/19 15:22:37 [error] 159#159: *1 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.613379515  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/config HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.613718672  2024/07/19 15:22:37 [error] 160#160: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.613722892  2024/07/19 15:22:37 [error] 160#160: *2 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.613854771  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/profile HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.621536919  2024/07/19 15:22:37 [error] 161#161: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.621596531  2024/07/19 15:22:37 [error] 161#161: *5 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.629916458  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET / HTTP/1.1" 200 2652 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.630039510  2024/07/19 15:22:37 [error] 159#159: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.630055452  2024/07/19 15:22:37 [error] 159#159: *8 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.630169775  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.646606502  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /fonts/Inter-Regular.woff2 HTTP/1.1" 200 108488 "http://localhost:5000/assets/index-qcILJ-ZU.css" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.728749275  2024/07/19 15:22:37 [error] 162#162: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.728757732  2024/07/19 15:22:37 [error] 162#162: *7 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.728762195  2024/07/19 15:22:37 [error] 159#159: *10 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.728860407  2024/07/19 15:22:37 [error] 159#159: *10 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.728864707  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/config HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.728868922  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/profile HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.746544275  2024/07/19 15:22:37 [error] 159#159: *13 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.746554212  2024/07/19 15:22:37 [error] 159#159: *13 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.746607785  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.746976282  2024/07/19 15:22:37 [error] 160#160: *15 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.746984966  2024/07/19 15:22:37 [error] 160#160: *15 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.810167650  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET / HTTP/1.1" 200 2652 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.810208055  2024/07/19 15:22:37 [error] 160#160: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.810215354  2024/07/19 15:22:37 [error] 160#160: *18 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.810331346  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/review?limit=10&severity=alert HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.814186618  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /images/android-chrome-192x192.png HTTP/1.1" 200 9201 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.853853780  2024/07/19 15:22:37 [error] 159#159: *20 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.853877044  2024/07/19 15:22:37 [error] 159#159: *20 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.853925789  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/config HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.854269349  2024/07/19 15:22:37 [error] 159#159: *17 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.854305572  2024/07/19 15:22:37 [error] 159#159: *17 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.854413992  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/profile HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.859491497  2024/07/19 15:22:37 [error] 159#159: *23 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.859549385  2024/07/19 15:22:37 [error] 159#159: *23 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.863224359  2024/07/19 15:22:37 [error] 159#159: *25 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.863261529  2024/07/19 15:22:37 [error] 159#159: *25 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.863314476  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.890519542  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /images/android-chrome-192x192.png HTTP/1.1" 200 9201 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.893576972  2024/07/19 15:22:37 [error] 159#159: *27 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.893623233  2024/07/19 15:22:37 [error] 159#159: *27 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.893681235  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/review?limit=10&severity=alert HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.911458253  [INFO] Starting go2rtc...
2024-07-19 15:22:37 2024-07-19 15:22:37.921099653  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET / HTTP/1.1" 200 2652 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.971410704  2024/07/19 15:22:37 [error] 159#159: *29 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.971416658  2024/07/19 15:22:37 [error] 159#159: *29 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/config HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.971525157  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/config HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.972932881  2024/07/19 15:22:37 [error] 159#159: *30 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.972970335  2024/07/19 15:22:37 [error] 159#159: *30 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.973033195  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /api/profile HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:37 2024-07-19 15:22:37.975096258  2024/07/19 15:22:37 [error] 159#159: *33 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.975160818  2024/07/19 15:22:37 [error] 159#159: *33 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/stats HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:37 2024-07-19 15:22:37.980476461  2024/07/19 15:22:37 [error] 159#159: *35 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.980482487  2024/07/19 15:22:37 [error] 159#159: *35 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", host: "localhost:5000"
2024-07-19 15:22:37 2024-07-19 15:22:37.980557440  172.18.0.1 - - [19/Jul/2024:15:22:37 +0500] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:38 2024-07-19 15:22:38.065216745  2024/07/19 15:22:38 [error] 159#159: *37 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:38 2024-07-19 15:22:38.065257404  2024/07/19 15:22:38 [error] 159#159: *37 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/review?limit=10&severity=alert HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:38 2024-07-19 15:22:38.065366029  172.18.0.1 - - [19/Jul/2024:15:22:38 +0500] "GET /api/review?limit=10&severity=alert HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:38 2024-07-19 15:22:38.066323318  172.18.0.1 - - [19/Jul/2024:15:22:38 +0500] "GET /images/android-chrome-192x192.png HTTP/1.1" 200 9201 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:38 2024-07-19 15:22:38.090271235  15:22:38.090 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:22:38 2024-07-19 15:22:38.090276202  15:22:38.090 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:22:38 2024-07-19 15:22:38.091397178  15:22:38.091 INF [rtsp] listen addr=:8554
2024-07-19 15:22:38 2024-07-19 15:22:38.091437526  15:22:38.091 INF [api] listen addr=:1984
2024-07-19 15:22:38 2024-07-19 15:22:38.091638821  15:22:38.091 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:22:38 2024-07-19 15:22:38.457020163  [INFO] Starting certsync...
2024-07-19 15:22:38 2024-07-19 15:22:38.472107381  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:38 2024-07-19 15:22:38.474276053  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:38 2024-07-19 15:22:38.628171981  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:38 2024-07-19 15:22:38.633902111  exit with signal: terminated
2024-07-19 15:22:38 2024-07-19 15:22:38.638119222  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:22:44 2024-07-19 15:22:44.840578447  [INFO] Preparing Frigate...
2024-07-19 15:22:44 2024-07-19 15:22:44.840653039  [ERROR] Frigate config file not found
2024-07-19 15:22:44 2024-07-19 15:22:44.842431609  [INFO] Starting NGINX...
2024-07-19 15:22:44 2024-07-19 15:22:44.843466950  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:44 2024-07-19 15:22:44.849611557  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:44 2024-07-19 15:22:44.935414947  [INFO] Starting certsync...
2024-07-19 15:22:44 2024-07-19 15:22:44.950573289  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:44 2024-07-19 15:22:44.951876005  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:45 2024-07-19 15:22:45.123760820  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:45 2024-07-19 15:22:45.131133505  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:22:52 2024-07-19 15:22:52.933693498  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:52 2024-07-19 15:22:52.935239042  [INFO] Preparing Frigate...
2024-07-19 15:22:52 2024-07-19 15:22:52.935361438  [ERROR] Frigate config file not found
2024-07-19 15:22:52 2024-07-19 15:22:52.938029530  [INFO] Starting NGINX...
2024-07-19 15:22:52 2024-07-19 15:22:52.940835535  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:22:53 2024-07-19 15:22:53.016402333  [INFO] Starting certsync...
2024-07-19 15:22:53 2024-07-19 15:22:53.029637897  2024/07/19 15:22:53 [error] 158#158: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:53 2024-07-19 15:22:53.029643535  2024/07/19 15:22:53 [error] 158#158: *1 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /api/profile HTTP/1.1", host: "localhost:5000", referrer: "http://localhost:5000/"
2024-07-19 15:22:53 2024-07-19 15:22:53.029930629  172.18.0.1 - - [19/Jul/2024:15:22:53 +0500] "GET /api/profile HTTP/1.1" 500 579 "http://localhost:5000/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:22:53 2024-07-19 15:22:53.052213703  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:22:53 2024-07-19 15:22:53.053079589  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:22:53 2024-07-19 15:22:53.280187370  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:22:53 2024-07-19 15:22:53.287402103  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:23:04 2024-07-19 15:23:04.289883615  [INFO] Preparing Frigate...
2024-07-19 15:23:04 2024-07-19 15:23:04.290008374  [ERROR] Frigate config file not found
2024-07-19 15:23:04 2024-07-19 15:23:04.293355086  [INFO] Starting NGINX...
2024-07-19 15:23:04 2024-07-19 15:23:04.294535586  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:23:04 2024-07-19 15:23:04.298212203  [INFO] Preparing new go2rtc config...
2024-07-19 15:23:04 2024-07-19 15:23:04.722616663  [INFO] Starting go2rtc...
2024-07-19 15:23:04 2024-07-19 15:23:04.874599982  15:23:04.874 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:23:04 2024-07-19 15:23:04.874606251  15:23:04.874 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:23:04 2024-07-19 15:23:04.875423450  15:23:04.874 INF [rtsp] listen addr=:8554
2024-07-19 15:23:04 2024-07-19 15:23:04.875426795  15:23:04.875 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:23:04 2024-07-19 15:23:04.875428534  15:23:04.875 INF [api] listen addr=:1984
2024-07-19 15:23:05 2024-07-19 15:23:05.369125030  [INFO] Starting certsync...
2024-07-19 15:23:05 2024-07-19 15:23:05.381435326  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:23:05 2024-07-19 15:23:05.382690802  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:23:05 2024-07-19 15:23:05.539812112  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:23:05 2024-07-19 15:23:05.546532080  exit with signal: terminated
2024-07-19 15:23:05 2024-07-19 15:23:05.550829151  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:23:22 2024-07-19 15:23:22.914155038  [INFO] Preparing Frigate...
2024-07-19 15:23:22 2024-07-19 15:23:22.914234950  [ERROR] Frigate config file not found
2024-07-19 15:23:22 2024-07-19 15:23:22.915342640  [INFO] Starting NGINX...
2024-07-19 15:23:22 2024-07-19 15:23:22.918640028  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:23:22 2024-07-19 15:23:22.920533057  [INFO] Preparing new go2rtc config...
2024-07-19 15:23:23 2024-07-19 15:23:23.330523876  [INFO] Starting go2rtc...
2024-07-19 15:23:23 2024-07-19 15:23:23.495194406  15:23:23.495 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:23:23 2024-07-19 15:23:23.495233602  15:23:23.495 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:23:23 2024-07-19 15:23:23.496443023  15:23:23.496 INF [rtsp] listen addr=:8554
2024-07-19 15:23:23 2024-07-19 15:23:23.496447166  15:23:23.496 INF [api] listen addr=:1984
2024-07-19 15:23:23 2024-07-19 15:23:23.496625453  15:23:23.496 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:23:23 2024-07-19 15:23:23.991618936  [INFO] Starting certsync...
2024-07-19 15:23:24 2024-07-19 15:23:24.005641435  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:23:24 2024-07-19 15:23:24.007051162  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:23:24 2024-07-19 15:23:24.170964830  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:23:24 2024-07-19 15:23:24.176128569  exit with signal: terminated
2024-07-19 15:23:24 2024-07-19 15:23:24.180080197  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:23:54 2024-07-19 15:23:54.558448716  [INFO] Preparing Frigate...
2024-07-19 15:23:54 2024-07-19 15:23:54.559219160  [ERROR] Frigate config file not found
2024-07-19 15:23:54 2024-07-19 15:23:54.559477377  [INFO] Starting NGINX...
2024-07-19 15:23:54 2024-07-19 15:23:54.561218396  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:23:54 2024-07-19 15:23:54.604675619  [INFO] Preparing new go2rtc config...
2024-07-19 15:23:55 2024-07-19 15:23:55.454903470  [INFO] Starting go2rtc...
2024-07-19 15:23:55 2024-07-19 15:23:55.619778276  15:23:55.619 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:23:55 2024-07-19 15:23:55.619783902  15:23:55.619 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:23:55 2024-07-19 15:23:55.620697285  15:23:55.620 INF [rtsp] listen addr=:8554
2024-07-19 15:23:55 2024-07-19 15:23:55.620856522  15:23:55.620 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:23:55 2024-07-19 15:23:55.621134832  15:23:55.620 INF [api] listen addr=:1984
2024-07-19 15:23:55 2024-07-19 15:23:55.723053693  [INFO] Starting certsync...
2024-07-19 15:23:55 2024-07-19 15:23:55.741229496  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:23:55 2024-07-19 15:23:55.742525390  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:23:55 2024-07-19 15:23:55.897837582  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:23:55 2024-07-19 15:23:55.902785490  exit with signal: terminated
2024-07-19 15:23:55 2024-07-19 15:23:55.907004226  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:24:51 2024-07-19 15:24:51.740097354  [INFO] Preparing Frigate...
2024-07-19 15:24:51 2024-07-19 15:24:51.740232458  [ERROR] Frigate config file not found
2024-07-19 15:24:51 2024-07-19 15:24:51.741486655  [INFO] Starting NGINX...
2024-07-19 15:24:51 2024-07-19 15:24:51.748980269  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:24:51 2024-07-19 15:24:51.755925911  [INFO] Preparing new go2rtc config...
2024-07-19 15:22:31 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:31 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:31 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:37 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:37 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:37 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:37 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:37 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:37 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:37 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:37 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:37 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:37 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:37 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:37 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:37 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:37 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:37 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:37 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:37 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:37 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:37 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:37 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:37 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:37 s6-rc: info: service frigate: starting
2024-07-19 15:22:37 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:37 s6-rc: info: service frigate successfully started
2024-07-19 15:22:37 s6-rc: info: service nginx: starting
2024-07-19 15:22:38 s6-rc: info: service nginx successfully started
2024-07-19 15:22:38 s6-rc: info: service certsync: starting
2024-07-19 15:22:38 s6-rc: info: service certsync successfully started
2024-07-19 15:22:38 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:38 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:38 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:38 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:38 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:38 s6-rc: info: service certsync: stopping
2024-07-19 15:22:38 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:38 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:38 s6-rc: info: service nginx: stopping
2024-07-19 15:22:38 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:38 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:38 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:38 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:38 s6-rc: info: service frigate: stopping
2024-07-19 15:22:38 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:38 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:38 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:38 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:38 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:38 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:38 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:38 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:38 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:38 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:38 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:38 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:38 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:38 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:38 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:38 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:38 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:38 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:44 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:44 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:44 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:44 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:44 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:44 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:44 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:44 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:44 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:44 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:44 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:44 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:44 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:44 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:44 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:44 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:44 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:44 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:44 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:44 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:44 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:44 s6-rc: info: service frigate: starting
2024-07-19 15:22:44 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:44 s6-rc: info: service frigate successfully started
2024-07-19 15:22:44 s6-rc: info: service nginx: starting
2024-07-19 15:22:44 s6-rc: info: service nginx successfully started
2024-07-19 15:22:44 s6-rc: info: service certsync: starting
2024-07-19 15:22:44 s6-rc: info: service certsync successfully started
2024-07-19 15:22:44 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:44 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:44 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:44 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:44 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:44 s6-rc: info: service certsync: stopping
2024-07-19 15:22:44 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:44 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:44 s6-rc: info: service nginx: stopping
2024-07-19 15:22:44 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:44 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:45 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:45 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:45 s6-rc: info: service frigate: stopping
2024-07-19 15:22:45 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:45 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:45 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:45 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:45 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:45 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:45 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:45 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:45 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:45 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:45 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:45 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:45 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:45 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:45 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:45 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:45 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:45 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:22:52 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:22:52 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:22:52 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:22:52 s6-rc: info: service fix-attrs: starting
2024-07-19 15:22:52 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:22:52 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:22:52 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:22:52 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:22:52 s6-rc: info: service log-prepare: starting
2024-07-19 15:22:52 s6-rc: info: service log-prepare successfully started
2024-07-19 15:22:52 s6-rc: info: service nginx-log: starting
2024-07-19 15:22:52 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:22:52 s6-rc: info: service frigate-log: starting
2024-07-19 15:22:52 s6-rc: info: service certsync-log: starting
2024-07-19 15:22:52 s6-rc: info: service nginx-log successfully started
2024-07-19 15:22:52 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:22:52 s6-rc: info: service go2rtc: starting
2024-07-19 15:22:52 s6-rc: info: service frigate-log successfully started
2024-07-19 15:22:52 s6-rc: info: service certsync-log successfully started
2024-07-19 15:22:52 s6-rc: info: service go2rtc successfully started
2024-07-19 15:22:52 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:22:52 s6-rc: info: service frigate: starting
2024-07-19 15:22:52 s6-rc: info: service frigate successfully started
2024-07-19 15:22:52 s6-rc: info: service nginx: starting
2024-07-19 15:22:52 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:22:53 s6-rc: info: service nginx successfully started
2024-07-19 15:22:53 s6-rc: info: service certsync: starting
2024-07-19 15:22:53 s6-rc: info: service certsync successfully started
2024-07-19 15:22:53 s6-rc: info: service legacy-services: starting
2024-07-19 15:22:53 s6-rc: info: service legacy-services successfully started
2024-07-19 15:22:53 s6-rc: info: service legacy-services: stopping
2024-07-19 15:22:53 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:22:53 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:22:53 s6-rc: info: service certsync: stopping
2024-07-19 15:22:53 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:22:53 s6-rc: info: service certsync successfully stopped
2024-07-19 15:22:53 s6-rc: info: service nginx: stopping
2024-07-19 15:22:53 s6-rc: info: service certsync-log: stopping
2024-07-19 15:22:53 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:22:53 s6-rc: info: service nginx successfully stopped
2024-07-19 15:22:53 s6-rc: info: service nginx-log: stopping
2024-07-19 15:22:53 s6-rc: info: service frigate: stopping
2024-07-19 15:22:53 s6-rc: info: service frigate successfully stopped
2024-07-19 15:22:53 s6-rc: info: service go2rtc: stopping
2024-07-19 15:22:53 s6-rc: info: service frigate-log: stopping
2024-07-19 15:22:53 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:22:53 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:22:53 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:22:53 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:22:53 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:22:53 s6-rc: info: service log-prepare: stopping
2024-07-19 15:22:53 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:22:53 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:22:53 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:22:53 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:22:53 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:22:53 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:22:53 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:22:53 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:22:53 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:23:04 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:23:04 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:23:04 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:23:04 s6-rc: info: service fix-attrs: starting
2024-07-19 15:23:04 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:23:04 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:23:04 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:23:04 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:23:04 s6-rc: info: service log-prepare: starting
2024-07-19 15:23:04 s6-rc: info: service log-prepare successfully started
2024-07-19 15:23:04 s6-rc: info: service nginx-log: starting
2024-07-19 15:23:04 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:23:04 s6-rc: info: service frigate-log: starting
2024-07-19 15:23:04 s6-rc: info: service certsync-log: starting
2024-07-19 15:23:04 s6-rc: info: service nginx-log successfully started
2024-07-19 15:23:04 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:23:04 s6-rc: info: service go2rtc: starting
2024-07-19 15:23:04 s6-rc: info: service frigate-log successfully started
2024-07-19 15:23:04 s6-rc: info: service certsync-log successfully started
2024-07-19 15:23:04 s6-rc: info: service go2rtc successfully started
2024-07-19 15:23:04 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:23:04 s6-rc: info: service frigate: starting
2024-07-19 15:23:04 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:23:04 s6-rc: info: service frigate successfully started
2024-07-19 15:23:04 s6-rc: info: service nginx: starting
2024-07-19 15:23:05 s6-rc: info: service nginx successfully started
2024-07-19 15:23:05 s6-rc: info: service certsync: starting
2024-07-19 15:23:05 s6-rc: info: service certsync successfully started
2024-07-19 15:23:05 s6-rc: info: service legacy-services: starting
2024-07-19 15:23:05 s6-rc: info: service legacy-services successfully started
2024-07-19 15:23:05 s6-rc: info: service legacy-services: stopping
2024-07-19 15:23:05 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:23:05 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:23:05 s6-rc: info: service certsync: stopping
2024-07-19 15:23:05 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:23:05 s6-rc: info: service certsync successfully stopped
2024-07-19 15:23:05 s6-rc: info: service nginx: stopping
2024-07-19 15:23:05 s6-rc: info: service certsync-log: stopping
2024-07-19 15:23:05 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:23:05 s6-rc: info: service nginx successfully stopped
2024-07-19 15:23:05 s6-rc: info: service nginx-log: stopping
2024-07-19 15:23:05 s6-rc: info: service frigate: stopping
2024-07-19 15:23:05 s6-rc: info: service frigate successfully stopped
2024-07-19 15:23:05 s6-rc: info: service go2rtc: stopping
2024-07-19 15:23:05 s6-rc: info: service frigate-log: stopping
2024-07-19 15:23:05 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:23:05 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:23:05 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:23:05 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:23:05 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:23:05 s6-rc: info: service log-prepare: stopping
2024-07-19 15:23:05 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:23:05 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:23:05 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:23:05 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:23:05 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:23:05 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:23:05 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:23:05 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:23:05 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:23:22 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:23:22 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:23:22 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:23:22 s6-rc: info: service fix-attrs: starting
2024-07-19 15:23:22 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:23:22 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:23:22 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:23:22 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:23:22 s6-rc: info: service log-prepare: starting
2024-07-19 15:23:22 s6-rc: info: service log-prepare successfully started
2024-07-19 15:23:22 s6-rc: info: service nginx-log: starting
2024-07-19 15:23:22 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:23:22 s6-rc: info: service frigate-log: starting
2024-07-19 15:23:22 s6-rc: info: service certsync-log: starting
2024-07-19 15:23:22 s6-rc: info: service nginx-log successfully started
2024-07-19 15:23:22 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:23:22 s6-rc: info: service go2rtc: starting
2024-07-19 15:23:22 s6-rc: info: service frigate-log successfully started
2024-07-19 15:23:22 s6-rc: info: service certsync-log successfully started
2024-07-19 15:23:22 s6-rc: info: service go2rtc successfully started
2024-07-19 15:23:22 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:23:22 s6-rc: info: service frigate: starting
2024-07-19 15:23:22 s6-rc: info: service frigate successfully started
2024-07-19 15:23:22 s6-rc: info: service nginx: starting
2024-07-19 15:23:22 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:23:23 s6-rc: info: service nginx successfully started
2024-07-19 15:23:23 s6-rc: info: service certsync: starting
2024-07-19 15:23:23 s6-rc: info: service certsync successfully started
2024-07-19 15:23:23 s6-rc: info: service legacy-services: starting
2024-07-19 15:23:23 s6-rc: info: service legacy-services successfully started
2024-07-19 15:23:23 s6-rc: info: service legacy-services: stopping
2024-07-19 15:23:24 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:23:24 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:23:24 s6-rc: info: service certsync: stopping
2024-07-19 15:23:24 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:23:24 s6-rc: info: service certsync successfully stopped
2024-07-19 15:23:24 s6-rc: info: service nginx: stopping
2024-07-19 15:23:24 s6-rc: info: service certsync-log: stopping
2024-07-19 15:23:24 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:23:24 s6-rc: info: service nginx successfully stopped
2024-07-19 15:23:24 s6-rc: info: service nginx-log: stopping
2024-07-19 15:23:24 s6-rc: info: service frigate: stopping
2024-07-19 15:23:24 s6-rc: info: service frigate successfully stopped
2024-07-19 15:23:24 s6-rc: info: service go2rtc: stopping
2024-07-19 15:23:24 s6-rc: info: service frigate-log: stopping
2024-07-19 15:23:24 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:23:24 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:23:24 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:23:24 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:23:24 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:23:24 s6-rc: info: service log-prepare: stopping
2024-07-19 15:23:24 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:23:24 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:23:24 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:23:24 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:23:24 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:23:24 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:23:24 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:23:24 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:23:24 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:23:54 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:23:54 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:23:54 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:23:54 s6-rc: info: service fix-attrs: starting
2024-07-19 15:23:54 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:23:54 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:23:54 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:23:54 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:23:54 s6-rc: info: service log-prepare: starting
2024-07-19 15:23:54 s6-rc: info: service log-prepare successfully started
2024-07-19 15:23:54 s6-rc: info: service nginx-log: starting
2024-07-19 15:23:54 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:23:54 s6-rc: info: service frigate-log: starting
2024-07-19 15:23:54 s6-rc: info: service certsync-log: starting
2024-07-19 15:23:54 s6-rc: info: service nginx-log successfully started
2024-07-19 15:23:54 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:23:54 s6-rc: info: service go2rtc: starting
2024-07-19 15:23:54 s6-rc: info: service frigate-log successfully started
2024-07-19 15:23:54 s6-rc: info: service certsync-log successfully started
2024-07-19 15:23:54 s6-rc: info: service go2rtc successfully started
2024-07-19 15:23:54 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:23:54 s6-rc: info: service frigate: starting
2024-07-19 15:23:54 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:23:54 s6-rc: info: service frigate successfully started
2024-07-19 15:23:54 s6-rc: info: service nginx: starting
2024-07-19 15:23:55 s6-rc: info: service nginx successfully started
2024-07-19 15:23:55 s6-rc: info: service certsync: starting
2024-07-19 15:23:55 s6-rc: info: service certsync successfully started
2024-07-19 15:23:55 s6-rc: info: service legacy-services: starting
2024-07-19 15:23:55 s6-rc: info: service legacy-services successfully started
2024-07-19 15:23:55 s6-rc: info: service legacy-services: stopping
2024-07-19 15:23:55 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:23:55 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:23:55 s6-rc: info: service certsync: stopping
2024-07-19 15:23:55 s6-rc: info: service certsync successfully stopped
2024-07-19 15:23:55 s6-rc: info: service nginx: stopping
2024-07-19 15:23:55 s6-rc: info: service certsync-log: stopping
2024-07-19 15:23:55 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:23:55 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:23:55 s6-rc: info: service nginx successfully stopped
2024-07-19 15:23:55 s6-rc: info: service nginx-log: stopping
2024-07-19 15:23:55 s6-rc: info: service frigate: stopping
2024-07-19 15:23:55 s6-rc: info: service frigate successfully stopped
2024-07-19 15:23:55 s6-rc: info: service go2rtc: stopping
2024-07-19 15:23:55 s6-rc: info: service frigate-log: stopping
2024-07-19 15:23:55 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:23:55 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:23:55 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:23:55 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:23:55 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:23:55 s6-rc: info: service log-prepare: stopping
2024-07-19 15:23:55 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:23:55 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:23:55 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:23:55 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:23:55 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:23:55 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:23:55 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:23:55 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:23:55 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:24:51 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:24:51 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:24:51 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:24:51 s6-rc: info: service fix-attrs: starting
2024-07-19 15:24:51 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:24:51 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:24:51 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:24:51 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:24:51 s6-rc: info: service log-prepare: starting
2024-07-19 15:24:51 s6-rc: info: service log-prepare successfully started
2024-07-19 15:24:51 s6-rc: info: service nginx-log: starting
2024-07-19 15:24:51 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:24:51 s6-rc: info: service frigate-log: starting
2024-07-19 15:24:51 s6-rc: info: service certsync-log: starting
2024-07-19 15:24:51 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:24:51 s6-rc: info: service go2rtc: starting
2024-07-19 15:24:51 s6-rc: info: service nginx-log successfully started
2024-07-19 15:24:51 s6-rc: info: service frigate-log successfully started
2024-07-19 15:24:51 s6-rc: info: service certsync-log successfully started
2024-07-19 15:24:51 s6-rc: info: service go2rtc successfully started
2024-07-19 15:24:51 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:24:51 s6-rc: info: service frigate: starting
2024-07-19 15:24:51 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:24:51 s6-rc: info: service frigate successfully started
2024-07-19 15:24:51 s6-rc: info: service nginx: starting
2024-07-19 15:24:52 s6-rc: info: service nginx successfully started
2024-07-19 15:24:52 s6-rc: info: service certsync: starting
2024-07-19 15:24:52 s6-rc: info: service certsync successfully started
2024-07-19 15:24:52 s6-rc: info: service legacy-services: starting
2024-07-19 15:24:52 s6-rc: info: service legacy-services successfully started
2024-07-19 15:24:52 s6-rc: info: service legacy-services: stopping
2024-07-19 15:24:52 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:24:52 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:24:52 s6-rc: info: service certsync: stopping
2024-07-19 15:24:52 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:24:52 s6-rc: info: service certsync successfully stopped
2024-07-19 15:24:52 s6-rc: info: service nginx: stopping
2024-07-19 15:24:52 s6-rc: info: service certsync-log: stopping
2024-07-19 15:24:52 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:24:53 s6-rc: info: service nginx successfully stopped
2024-07-19 15:24:53 s6-rc: info: service nginx-log: stopping
2024-07-19 15:24:53 s6-rc: info: service frigate: stopping
2024-07-19 15:24:53 s6-rc: info: service frigate successfully stopped
2024-07-19 15:24:53 s6-rc: info: service go2rtc: stopping
2024-07-19 15:24:53 s6-rc: info: service frigate-log: stopping
2024-07-19 15:24:53 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:24:53 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:24:53 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:24:53 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:24:53 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:24:53 s6-rc: info: service log-prepare: stopping
2024-07-19 15:24:53 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:24:53 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:24:53 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:24:53 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:24:53 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:24:53 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:24:53 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:24:53 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:24:53 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:25:57 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:25:57 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:25:57 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:25:57 s6-rc: info: service fix-attrs: starting
2024-07-19 15:25:57 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:25:57 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:25:57 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:25:57 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:25:57 s6-rc: info: service log-prepare: starting
2024-07-19 15:25:57 s6-rc: info: service log-prepare successfully started
2024-07-19 15:25:57 s6-rc: info: service nginx-log: starting
2024-07-19 15:25:57 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:25:57 s6-rc: info: service frigate-log: starting
2024-07-19 15:25:57 s6-rc: info: service certsync-log: starting
2024-07-19 15:25:57 s6-rc: info: service nginx-log successfully started
2024-07-19 15:25:57 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:25:57 s6-rc: info: service go2rtc: starting
2024-07-19 15:25:57 s6-rc: info: service frigate-log successfully started
2024-07-19 15:25:57 s6-rc: info: service certsync-log successfully started
2024-07-19 15:25:57 s6-rc: info: service go2rtc successfully started
2024-07-19 15:25:57 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:25:57 s6-rc: info: service frigate: starting
2024-07-19 15:25:57 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:25:57 s6-rc: info: service frigate successfully started
2024-07-19 15:25:57 s6-rc: info: service nginx: starting
2024-07-19 15:25:57 s6-rc: info: service nginx successfully started
2024-07-19 15:25:57 s6-rc: info: service certsync: starting
2024-07-19 15:25:57 s6-rc: info: service certsync successfully started
2024-07-19 15:25:57 s6-rc: info: service legacy-services: starting
2024-07-19 15:25:57 s6-rc: info: service legacy-services successfully started
2024-07-19 15:25:57 s6-rc: info: service legacy-services: stopping
2024-07-19 15:25:57 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:25:57 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:25:57 s6-rc: info: service certsync: stopping
2024-07-19 15:25:57 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:25:57 s6-rc: info: service certsync successfully stopped
2024-07-19 15:25:57 s6-rc: info: service nginx: stopping
2024-07-19 15:25:57 s6-rc: info: service certsync-log: stopping
2024-07-19 15:25:57 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:25:58 s6-rc: info: service nginx successfully stopped
2024-07-19 15:25:58 s6-rc: info: service nginx-log: stopping
2024-07-19 15:25:58 s6-rc: info: service frigate: stopping
2024-07-19 15:25:58 s6-rc: info: service frigate successfully stopped
2024-07-19 15:25:58 s6-rc: info: service go2rtc: stopping
2024-07-19 15:25:58 s6-rc: info: service frigate-log: stopping
2024-07-19 15:25:58 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:25:58 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:25:58 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:25:58 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:25:58 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:25:58 s6-rc: info: service log-prepare: stopping
2024-07-19 15:25:58 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:25:58 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:25:58 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:25:58 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:25:58 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:25:58 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:25:58 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:25:58 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:25:58 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:27:02 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:27:02 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:27:02 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:27:02 s6-rc: info: service fix-attrs: starting
2024-07-19 15:27:02 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:27:02 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:27:02 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:27:02 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:27:02 s6-rc: info: service log-prepare: starting
2024-07-19 15:27:02 s6-rc: info: service log-prepare successfully started
2024-07-19 15:27:02 s6-rc: info: service nginx-log: starting
2024-07-19 15:27:02 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:27:02 s6-rc: info: service frigate-log: starting
2024-07-19 15:27:02 s6-rc: info: service certsync-log: starting
2024-07-19 15:27:02 s6-rc: info: service frigate-log successfully started
2024-07-19 15:27:02 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:27:02 s6-rc: info: service go2rtc: starting
2024-07-19 15:27:02 s6-rc: info: service nginx-log successfully started
2024-07-19 15:27:02 s6-rc: info: service certsync-log successfully started
2024-07-19 15:27:02 s6-rc: info: service go2rtc successfully started
2024-07-19 15:27:02 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:27:02 s6-rc: info: service frigate: starting
2024-07-19 15:27:02 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:27:02 s6-rc: info: service frigate successfully started
2024-07-19 15:27:02 s6-rc: info: service nginx: starting
2024-07-19 15:27:02 s6-rc: info: service nginx successfully started
2024-07-19 15:27:02 s6-rc: info: service certsync: starting
2024-07-19 15:27:02 s6-rc: info: service certsync successfully started
2024-07-19 15:27:02 s6-rc: info: service legacy-services: starting
2024-07-19 15:27:02 s6-rc: info: service legacy-services successfully started
2024-07-19 15:27:02 s6-rc: info: service legacy-services: stopping
2024-07-19 15:27:02 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:27:02 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:27:02 s6-rc: info: service certsync: stopping
2024-07-19 15:27:02 s6-rc: info: service certsync successfully stopped
2024-07-19 15:27:02 s6-rc: info: service nginx: stopping
2024-07-19 15:27:02 s6-rc: info: service certsync-log: stopping
2024-07-19 15:27:02 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:27:02 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:27:02 s6-rc: info: service nginx successfully stopped
2024-07-19 15:27:02 s6-rc: info: service nginx-log: stopping
2024-07-19 15:27:02 s6-rc: info: service frigate: stopping
2024-07-19 15:27:02 s6-rc: info: service frigate successfully stopped
2024-07-19 15:27:02 s6-rc: info: service go2rtc: stopping
2024-07-19 15:27:02 s6-rc: info: service frigate-log: stopping
2024-07-19 15:27:02 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:27:02 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:27:02 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:27:02 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:27:02 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:27:02 s6-rc: info: service log-prepare: stopping
2024-07-19 15:27:02 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:27:02 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:27:02 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:27:02 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:27:02 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:27:02 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:27:02 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:27:02 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:27:02 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:28:07 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:28:07 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:28:07 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:28:07 s6-rc: info: service fix-attrs: starting
2024-07-19 15:28:07 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:28:07 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:28:07 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:28:07 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:28:07 s6-rc: info: service log-prepare: starting
2024-07-19 15:28:07 s6-rc: info: service log-prepare successfully started
2024-07-19 15:28:07 s6-rc: info: service nginx-log: starting
2024-07-19 15:28:07 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:28:07 s6-rc: info: service frigate-log: starting
2024-07-19 15:28:07 s6-rc: info: service certsync-log: starting
2024-07-19 15:28:07 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:28:07 s6-rc: info: service go2rtc: starting
2024-07-19 15:28:07 s6-rc: info: service nginx-log successfully started
2024-07-19 15:28:07 s6-rc: info: service frigate-log successfully started
2024-07-19 15:28:07 s6-rc: info: service certsync-log successfully started
2024-07-19 15:28:07 s6-rc: info: service go2rtc successfully started
2024-07-19 15:28:07 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:28:07 s6-rc: info: service frigate: starting
2024-07-19 15:28:07 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:28:07 s6-rc: info: service frigate successfully started
2024-07-19 15:28:07 s6-rc: info: service nginx: starting
2024-07-19 15:28:07 s6-rc: info: service nginx successfully started
2024-07-19 15:28:07 s6-rc: info: service certsync: starting
2024-07-19 15:28:07 s6-rc: info: service certsync successfully started
2024-07-19 15:28:07 s6-rc: info: service legacy-services: starting
2024-07-19 15:28:07 s6-rc: info: service legacy-services successfully started
2024-07-19 15:28:07 s6-rc: info: service legacy-services: stopping
2024-07-19 15:28:07 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:28:07 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:28:07 s6-rc: info: service certsync: stopping
2024-07-19 15:28:07 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:28:07 s6-rc: info: service certsync successfully stopped
2024-07-19 15:28:07 s6-rc: info: service nginx: stopping
2024-07-19 15:28:07 s6-rc: info: service certsync-log: stopping
2024-07-19 15:28:07 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:28:07 s6-rc: info: service nginx successfully stopped
2024-07-19 15:28:07 s6-rc: info: service nginx-log: stopping
2024-07-19 15:28:07 s6-rc: info: service frigate: stopping
2024-07-19 15:28:07 s6-rc: info: service frigate successfully stopped
2024-07-19 15:28:07 s6-rc: info: service go2rtc: stopping
2024-07-19 15:28:07 s6-rc: info: service frigate-log: stopping
2024-07-19 15:28:07 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:28:07 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:28:07 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:28:07 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:28:07 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:28:07 s6-rc: info: service log-prepare: stopping
2024-07-19 15:28:07 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:28:07 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:28:07 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:28:07 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:28:07 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:28:07 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:28:07 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:28:07 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:28:07 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:29:12 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:29:12 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:29:12 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:29:12 s6-rc: info: service fix-attrs: starting
2024-07-19 15:29:12 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:29:12 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:29:12 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:29:12 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:29:12 s6-rc: info: service log-prepare: starting
2024-07-19 15:29:12 s6-rc: info: service log-prepare successfully started
2024-07-19 15:29:12 s6-rc: info: service nginx-log: starting
2024-07-19 15:29:12 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:29:12 s6-rc: info: service frigate-log: starting
2024-07-19 15:29:12 s6-rc: info: service certsync-log: starting
2024-07-19 15:29:12 s6-rc: info: service nginx-log successfully started
2024-07-19 15:29:12 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:29:12 s6-rc: info: service go2rtc: starting
2024-07-19 15:29:12 s6-rc: info: service frigate-log successfully started
2024-07-19 15:29:12 s6-rc: info: service certsync-log successfully started
2024-07-19 15:29:12 s6-rc: info: service go2rtc successfully started
2024-07-19 15:29:12 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:29:12 s6-rc: info: service frigate: starting
2024-07-19 15:29:12 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:29:12 s6-rc: info: service frigate successfully started
2024-07-19 15:29:12 s6-rc: info: service nginx: starting
2024-07-19 15:29:13 s6-rc: info: service nginx successfully started
2024-07-19 15:29:13 s6-rc: info: service certsync: starting
2024-07-19 15:29:13 s6-rc: info: service certsync successfully started
2024-07-19 15:29:13 s6-rc: info: service legacy-services: starting
2024-07-19 15:29:13 s6-rc: info: service legacy-services successfully started
2024-07-19 15:29:13 s6-rc: info: service legacy-services: stopping
2024-07-19 15:29:13 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:29:13 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:29:13 s6-rc: info: service certsync: stopping
2024-07-19 15:29:13 s6-rc: info: service certsync successfully stopped
2024-07-19 15:29:13 s6-rc: info: service nginx: stopping
2024-07-19 15:29:13 s6-rc: info: service certsync-log: stopping
2024-07-19 15:29:13 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:29:13 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:29:13 s6-rc: info: service nginx successfully stopped
2024-07-19 15:29:13 s6-rc: info: service nginx-log: stopping
2024-07-19 15:29:13 s6-rc: info: service frigate: stopping
2024-07-19 15:29:13 s6-rc: info: service frigate successfully stopped
2024-07-19 15:29:13 s6-rc: info: service go2rtc: stopping
2024-07-19 15:29:13 s6-rc: info: service frigate-log: stopping
2024-07-19 15:29:13 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:29:13 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:29:13 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:29:13 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:29:13 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:29:13 s6-rc: info: service log-prepare: stopping
2024-07-19 15:29:13 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:29:13 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:29:13 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:29:13 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:29:13 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:29:13 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:29:13 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:29:13 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:29:13 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:30:18 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:30:18 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:30:18 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:30:18 s6-rc: info: service fix-attrs: starting
2024-07-19 15:30:18 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:30:18 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:30:18 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:30:18 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:30:18 s6-rc: info: service log-prepare: starting
2024-07-19 15:30:18 s6-rc: info: service log-prepare successfully started
2024-07-19 15:30:18 s6-rc: info: service nginx-log: starting
2024-07-19 15:30:18 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:30:18 s6-rc: info: service frigate-log: starting
2024-07-19 15:30:18 s6-rc: info: service certsync-log: starting
2024-07-19 15:30:18 s6-rc: info: service certsync-log successfully started
2024-07-19 15:30:18 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:30:18 s6-rc: info: service go2rtc: starting
2024-07-19 15:30:18 s6-rc: info: service nginx-log successfully started
2024-07-19 15:30:18 s6-rc: info: service frigate-log successfully started
2024-07-19 15:30:18 s6-rc: info: service go2rtc successfully started
2024-07-19 15:30:18 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:30:18 s6-rc: info: service frigate: starting
2024-07-19 15:30:18 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:30:18 s6-rc: info: service frigate successfully started
2024-07-19 15:30:18 s6-rc: info: service nginx: starting
2024-07-19 15:30:18 s6-rc: info: service nginx successfully started
2024-07-19 15:30:18 s6-rc: info: service certsync: starting
2024-07-19 15:30:18 s6-rc: info: service certsync successfully started
2024-07-19 15:30:18 s6-rc: info: service legacy-services: starting
2024-07-19 15:30:18 s6-rc: info: service legacy-services successfully started
2024-07-19 15:30:18 s6-rc: info: service legacy-services: stopping
2024-07-19 15:30:18 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:30:18 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:30:18 s6-rc: info: service certsync: stopping
2024-07-19 15:30:18 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:30:18 s6-rc: info: service certsync successfully stopped
2024-07-19 15:30:18 s6-rc: info: service nginx: stopping
2024-07-19 15:30:18 s6-rc: info: service certsync-log: stopping
2024-07-19 15:30:18 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:30:18 s6-rc: info: service nginx successfully stopped
2024-07-19 15:30:18 s6-rc: info: service nginx-log: stopping
2024-07-19 15:30:18 s6-rc: info: service frigate: stopping
2024-07-19 15:30:18 s6-rc: info: service frigate successfully stopped
2024-07-19 15:30:18 s6-rc: info: service go2rtc: stopping
2024-07-19 15:30:18 s6-rc: info: service frigate-log: stopping
2024-07-19 15:30:18 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:30:18 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:30:18 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:30:18 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:30:18 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:30:18 s6-rc: info: service log-prepare: stopping
2024-07-19 15:30:18 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:30:18 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:30:18 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:30:18 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:30:18 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:30:18 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:30:18 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:30:18 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:30:18 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:31:23 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:31:23 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:31:23 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:31:23 s6-rc: info: service fix-attrs: starting
2024-07-19 15:31:23 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:31:23 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:31:23 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:31:23 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:31:23 s6-rc: info: service log-prepare: starting
2024-07-19 15:31:23 s6-rc: info: service log-prepare successfully started
2024-07-19 15:31:23 s6-rc: info: service nginx-log: starting
2024-07-19 15:31:23 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:31:23 s6-rc: info: service frigate-log: starting
2024-07-19 15:31:23 s6-rc: info: service certsync-log: starting
2024-07-19 15:31:23 s6-rc: info: service nginx-log successfully started
2024-07-19 15:31:23 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:31:23 s6-rc: info: service go2rtc: starting
2024-07-19 15:31:23 s6-rc: info: service frigate-log successfully started
2024-07-19 15:31:23 s6-rc: info: service certsync-log successfully started
2024-07-19 15:31:23 s6-rc: info: service go2rtc successfully started
2024-07-19 15:31:23 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:31:23 s6-rc: info: service frigate: starting
2024-07-19 15:31:23 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:31:23 s6-rc: info: service frigate successfully started
2024-07-19 15:31:23 s6-rc: info: service nginx: starting
2024-07-19 15:31:23 s6-rc: info: service nginx successfully started
2024-07-19 15:31:23 s6-rc: info: service certsync: starting
2024-07-19 15:31:23 s6-rc: info: service certsync successfully started
2024-07-19 15:31:23 s6-rc: info: service legacy-services: starting
2024-07-19 15:31:23 s6-rc: info: service legacy-services successfully started
2024-07-19 15:31:23 s6-rc: info: service legacy-services: stopping
2024-07-19 15:31:23 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:31:23 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:31:23 s6-rc: info: service certsync: stopping
2024-07-19 15:31:23 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:31:23 s6-rc: info: service certsync successfully stopped
2024-07-19 15:31:23 s6-rc: info: service nginx: stopping
2024-07-19 15:31:23 s6-rc: info: service certsync-log: stopping
2024-07-19 15:31:23 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:31:23 s6-rc: info: service nginx successfully stopped
2024-07-19 15:31:23 s6-rc: info: service nginx-log: stopping
2024-07-19 15:31:23 s6-rc: info: service frigate: stopping
2024-07-19 15:31:23 s6-rc: info: service frigate successfully stopped
2024-07-19 15:31:23 s6-rc: info: service go2rtc: stopping
2024-07-19 15:31:23 s6-rc: info: service frigate-log: stopping
2024-07-19 15:31:23 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:31:23 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:31:23 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:31:23 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:31:23 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:31:23 s6-rc: info: service log-prepare: stopping
2024-07-19 15:31:23 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:31:23 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:31:23 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:31:23 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:31:23 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:31:23 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:31:23 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:31:23 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:31:23 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:32:28 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:32:28 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:32:28 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:32:28 s6-rc: info: service fix-attrs: starting
2024-07-19 15:32:28 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:32:28 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:32:28 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:32:28 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:32:28 s6-rc: info: service log-prepare: starting
2024-07-19 15:32:28 s6-rc: info: service log-prepare successfully started
2024-07-19 15:32:28 s6-rc: info: service nginx-log: starting
2024-07-19 15:32:28 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:32:28 s6-rc: info: service frigate-log: starting
2024-07-19 15:32:28 s6-rc: info: service certsync-log: starting
2024-07-19 15:32:28 s6-rc: info: service nginx-log successfully started
2024-07-19 15:32:28 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:32:28 s6-rc: info: service go2rtc: starting
2024-07-19 15:32:28 s6-rc: info: service frigate-log successfully started
2024-07-19 15:32:28 s6-rc: info: service certsync-log successfully started
2024-07-19 15:32:28 s6-rc: info: service go2rtc successfully started
2024-07-19 15:32:28 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:32:28 s6-rc: info: service frigate: starting
2024-07-19 15:32:28 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:32:28 s6-rc: info: service frigate successfully started
2024-07-19 15:32:28 s6-rc: info: service nginx: starting
2024-07-19 15:32:29 s6-rc: info: service nginx successfully started
2024-07-19 15:32:29 s6-rc: info: service certsync: starting
2024-07-19 15:32:29 s6-rc: info: service certsync successfully started
2024-07-19 15:32:29 s6-rc: info: service legacy-services: starting
2024-07-19 15:32:29 s6-rc: info: service legacy-services successfully started
2024-07-19 15:32:29 s6-rc: info: service legacy-services: stopping
2024-07-19 15:32:29 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:32:29 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:32:29 s6-rc: info: service certsync: stopping
2024-07-19 15:32:29 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:32:29 s6-rc: info: service certsync successfully stopped
2024-07-19 15:32:29 s6-rc: info: service nginx: stopping
2024-07-19 15:32:29 s6-rc: info: service certsync-log: stopping
2024-07-19 15:32:29 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:32:29 s6-rc: info: service nginx successfully stopped
2024-07-19 15:32:29 s6-rc: info: service nginx-log: stopping
2024-07-19 15:32:29 s6-rc: info: service frigate: stopping
2024-07-19 15:32:29 s6-rc: info: service frigate successfully stopped
2024-07-19 15:32:29 s6-rc: info: service go2rtc: stopping
2024-07-19 15:32:29 s6-rc: info: service frigate-log: stopping
2024-07-19 15:32:29 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:32:29 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:32:29 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:32:29 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:32:29 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:32:29 s6-rc: info: service log-prepare: stopping
2024-07-19 15:32:29 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:32:29 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:32:29 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:32:29 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:32:29 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:32:29 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:32:29 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:32:29 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:32:29 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:33:33 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:33:33 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:33:33 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:33:33 s6-rc: info: service fix-attrs: starting
2024-07-19 15:33:33 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:33:33 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:33:33 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:33:33 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:33:33 s6-rc: info: service log-prepare: starting
2024-07-19 15:33:33 s6-rc: info: service log-prepare successfully started
2024-07-19 15:33:33 s6-rc: info: service nginx-log: starting
2024-07-19 15:33:33 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:33:33 s6-rc: info: service frigate-log: starting
2024-07-19 15:33:33 s6-rc: info: service certsync-log: starting
2024-07-19 15:33:33 s6-rc: info: service nginx-log successfully started
2024-07-19 15:33:33 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:33:33 s6-rc: info: service go2rtc: starting
2024-07-19 15:33:33 s6-rc: info: service frigate-log successfully started
2024-07-19 15:33:33 s6-rc: info: service certsync-log successfully started
2024-07-19 15:33:33 s6-rc: info: service go2rtc successfully started
2024-07-19 15:33:33 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:33:33 s6-rc: info: service frigate: starting
2024-07-19 15:33:33 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:33:33 s6-rc: info: service frigate successfully started
2024-07-19 15:33:33 s6-rc: info: service nginx: starting
2024-07-19 15:33:35 s6-rc: info: service nginx successfully started
2024-07-19 15:33:35 s6-rc: info: service certsync: starting
2024-07-19 15:33:35 s6-rc: info: service certsync successfully started
2024-07-19 15:33:35 s6-rc: info: service legacy-services: starting
2024-07-19 15:33:35 s6-rc: info: service legacy-services successfully started
2024-07-19 15:33:35 s6-rc: info: service legacy-services: stopping
2024-07-19 15:33:35 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:33:35 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:33:35 s6-rc: info: service certsync: stopping
2024-07-19 15:33:35 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:33:35 s6-rc: info: service certsync successfully stopped
2024-07-19 15:33:35 s6-rc: info: service nginx: stopping
2024-07-19 15:33:35 s6-rc: info: service certsync-log: stopping
2024-07-19 15:33:35 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:33:35 s6-rc: info: service nginx successfully stopped
2024-07-19 15:33:35 s6-rc: info: service nginx-log: stopping
2024-07-19 15:33:35 s6-rc: info: service frigate: stopping
2024-07-19 15:33:35 s6-rc: info: service frigate successfully stopped
2024-07-19 15:33:35 s6-rc: info: service go2rtc: stopping
2024-07-19 15:33:35 s6-rc: info: service frigate-log: stopping
2024-07-19 15:33:35 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:33:35 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:33:35 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:33:35 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:33:35 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:33:35 s6-rc: info: service log-prepare: stopping
2024-07-19 15:33:35 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:33:35 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:33:35 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:33:35 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:33:35 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:33:35 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:33:35 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:33:35 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:33:35 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:34:39 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:34:39 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:34:39 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:34:39 s6-rc: info: service fix-attrs: starting
2024-07-19 15:34:39 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:34:39 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:34:39 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:34:39 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:34:39 s6-rc: info: service log-prepare: starting
2024-07-19 15:34:39 s6-rc: info: service log-prepare successfully started
2024-07-19 15:34:39 s6-rc: info: service nginx-log: starting
2024-07-19 15:34:39 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:34:39 s6-rc: info: service frigate-log: starting
2024-07-19 15:34:39 s6-rc: info: service certsync-log: starting
2024-07-19 15:34:39 s6-rc: info: service nginx-log successfully started
2024-07-19 15:34:39 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:34:39 s6-rc: info: service go2rtc: starting
2024-07-19 15:34:39 s6-rc: info: service frigate-log successfully started
2024-07-19 15:34:39 s6-rc: info: service certsync-log successfully started
2024-07-19 15:34:39 s6-rc: info: service go2rtc successfully started
2024-07-19 15:34:39 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:34:39 s6-rc: info: service frigate: starting
2024-07-19 15:34:39 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:34:39 s6-rc: info: service frigate successfully started
2024-07-19 15:34:39 s6-rc: info: service nginx: starting
2024-07-19 15:34:41 s6-rc: info: service nginx successfully started
2024-07-19 15:34:41 s6-rc: info: service certsync: starting
2024-07-19 15:34:41 s6-rc: info: service certsync successfully started
2024-07-19 15:34:41 s6-rc: info: service legacy-services: starting
2024-07-19 15:34:41 s6-rc: info: service legacy-services successfully started
2024-07-19 15:34:41 s6-rc: info: service legacy-services: stopping
2024-07-19 15:34:41 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:34:41 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:34:41 s6-rc: info: service certsync: stopping
2024-07-19 15:34:41 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:34:41 s6-rc: info: service certsync successfully stopped
2024-07-19 15:34:41 s6-rc: info: service nginx: stopping
2024-07-19 15:34:41 s6-rc: info: service certsync-log: stopping
2024-07-19 15:34:41 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:34:41 s6-rc: info: service nginx successfully stopped
2024-07-19 15:34:41 s6-rc: info: service nginx-log: stopping
2024-07-19 15:34:41 s6-rc: info: service frigate: stopping
2024-07-19 15:34:41 s6-rc: info: service frigate successfully stopped
2024-07-19 15:34:41 s6-rc: info: service go2rtc: stopping
2024-07-19 15:34:41 s6-rc: info: service frigate-log: stopping
2024-07-19 15:34:41 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:34:41 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:34:41 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:34:41 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:34:41 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:34:41 s6-rc: info: service log-prepare: stopping
2024-07-19 15:34:41 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:34:41 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:34:41 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:34:41 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:34:41 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:34:41 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:34:41 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:34:41 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:34:41 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:35:45 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:35:45 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:35:45 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:35:45 s6-rc: info: service fix-attrs: starting
2024-07-19 15:35:45 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:35:45 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:35:45 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:35:45 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:35:45 s6-rc: info: service log-prepare: starting
2024-07-19 15:35:45 s6-rc: info: service log-prepare successfully started
2024-07-19 15:35:45 s6-rc: info: service nginx-log: starting
2024-07-19 15:35:45 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:35:45 s6-rc: info: service frigate-log: starting
2024-07-19 15:35:45 s6-rc: info: service certsync-log: starting
2024-07-19 15:35:45 s6-rc: info: service nginx-log successfully started
2024-07-19 15:35:45 s6-rc: info: service frigate-log successfully started
2024-07-19 15:35:45 s6-rc: info: service certsync-log successfully started
2024-07-19 15:35:45 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:35:45 s6-rc: info: service go2rtc: starting
2024-07-19 15:35:45 s6-rc: info: service go2rtc successfully started
2024-07-19 15:35:45 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:35:45 s6-rc: info: service frigate: starting
2024-07-19 15:35:45 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:35:45 s6-rc: info: service frigate successfully started
2024-07-19 15:35:45 s6-rc: info: service nginx: starting
2024-07-19 15:35:47 s6-rc: info: service nginx successfully started
2024-07-19 15:35:47 s6-rc: info: service certsync: starting
2024-07-19 15:35:47 s6-rc: info: service certsync successfully started
2024-07-19 15:35:47 s6-rc: info: service legacy-services: starting
2024-07-19 15:35:47 s6-rc: info: service legacy-services successfully started
2024-07-19 15:35:47 s6-rc: info: service legacy-services: stopping
2024-07-19 15:35:47 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:35:47 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:35:47 s6-rc: info: service certsync: stopping
2024-07-19 15:35:47 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:35:47 s6-rc: info: service certsync successfully stopped
2024-07-19 15:35:47 s6-rc: info: service nginx: stopping
2024-07-19 15:35:47 s6-rc: info: service certsync-log: stopping
2024-07-19 15:35:47 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:35:47 s6-rc: info: service nginx successfully stopped
2024-07-19 15:35:47 s6-rc: info: service nginx-log: stopping
2024-07-19 15:35:47 s6-rc: info: service frigate: stopping
2024-07-19 15:35:47 s6-rc: info: service frigate successfully stopped
2024-07-19 15:35:47 s6-rc: info: service go2rtc: stopping
2024-07-19 15:35:47 s6-rc: info: service frigate-log: stopping
2024-07-19 15:35:47 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:35:47 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:35:47 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:35:47 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:35:47 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:35:47 s6-rc: info: service log-prepare: stopping
2024-07-19 15:35:47 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:35:47 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:35:47 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:35:47 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:35:47 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:35:47 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:35:47 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:35:47 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:35:47 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:36:52 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:36:52 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:36:52 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:36:52 s6-rc: info: service fix-attrs: starting
2024-07-19 15:36:52 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:36:52 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:36:52 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:36:52 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:36:52 s6-rc: info: service log-prepare: starting
2024-07-19 15:36:52 s6-rc: info: service log-prepare successfully started
2024-07-19 15:36:52 s6-rc: info: service nginx-log: starting
2024-07-19 15:36:52 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:36:52 s6-rc: info: service frigate-log: starting
2024-07-19 15:36:52 s6-rc: info: service certsync-log: starting
2024-07-19 15:36:52 s6-rc: info: service nginx-log successfully started
2024-07-19 15:36:52 s6-rc: info: service frigate-log successfully started
2024-07-19 15:36:52 s6-rc: info: service certsync-log successfully started
2024-07-19 15:36:52 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:36:52 s6-rc: info: service go2rtc: starting
2024-07-19 15:36:52 s6-rc: info: service go2rtc successfully started
2024-07-19 15:36:52 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:36:52 s6-rc: info: service frigate: starting
2024-07-19 15:36:52 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:36:52 s6-rc: info: service frigate successfully started
2024-07-19 15:36:52 s6-rc: info: service nginx: starting
2024-07-19 15:36:53 s6-rc: info: service nginx successfully started
2024-07-19 15:36:53 s6-rc: info: service certsync: starting
2024-07-19 15:36:53 s6-rc: info: service certsync successfully started
2024-07-19 15:36:53 s6-rc: info: service legacy-services: starting
2024-07-19 15:36:53 s6-rc: info: service legacy-services successfully started
2024-07-19 15:36:53 s6-rc: info: service legacy-services: stopping
2024-07-19 15:36:53 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:36:53 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:36:53 s6-rc: info: service certsync: stopping
2024-07-19 15:36:53 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:36:53 s6-rc: info: service certsync successfully stopped
2024-07-19 15:36:53 s6-rc: info: service nginx: stopping
2024-07-19 15:36:53 s6-rc: info: service certsync-log: stopping
2024-07-19 15:36:53 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:36:53 s6-rc: info: service nginx successfully stopped
2024-07-19 15:36:53 s6-rc: info: service nginx-log: stopping
2024-07-19 15:36:53 s6-rc: info: service frigate: stopping
2024-07-19 15:36:53 s6-rc: info: service frigate successfully stopped
2024-07-19 15:36:53 s6-rc: info: service go2rtc: stopping
2024-07-19 15:36:53 s6-rc: info: service frigate-log: stopping
2024-07-19 15:36:53 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:36:53 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:36:53 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:36:53 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:36:53 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:36:53 s6-rc: info: service log-prepare: stopping
2024-07-19 15:36:53 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:36:53 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:36:53 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:36:53 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:36:53 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:36:53 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:36:53 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:36:53 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:36:53 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:37:58 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:37:58 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:37:58 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:37:58 s6-rc: info: service fix-attrs: starting
2024-07-19 15:37:58 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:37:58 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:37:58 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:37:58 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:37:58 s6-rc: info: service log-prepare: starting
2024-07-19 15:37:58 s6-rc: info: service log-prepare successfully started
2024-07-19 15:37:58 s6-rc: info: service nginx-log: starting
2024-07-19 15:37:58 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:37:58 s6-rc: info: service frigate-log: starting
2024-07-19 15:37:58 s6-rc: info: service certsync-log: starting
2024-07-19 15:37:58 s6-rc: info: service nginx-log successfully started
2024-07-19 15:37:58 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:37:58 s6-rc: info: service go2rtc: starting
2024-07-19 15:37:58 s6-rc: info: service frigate-log successfully started
2024-07-19 15:37:58 s6-rc: info: service certsync-log successfully started
2024-07-19 15:37:58 s6-rc: info: service go2rtc successfully started
2024-07-19 15:37:58 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:37:58 s6-rc: info: service frigate: starting
2024-07-19 15:37:58 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:37:58 s6-rc: info: service frigate successfully started
2024-07-19 15:37:58 s6-rc: info: service nginx: starting
2024-07-19 15:37:59 s6-rc: info: service nginx successfully started
2024-07-19 15:37:59 s6-rc: info: service certsync: starting
2024-07-19 15:37:59 s6-rc: info: service certsync successfully started
2024-07-19 15:37:59 s6-rc: info: service legacy-services: starting
2024-07-19 15:37:59 s6-rc: info: service legacy-services successfully started
2024-07-19 15:37:59 s6-rc: info: service legacy-services: stopping
2024-07-19 15:37:59 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:37:59 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:37:59 s6-rc: info: service certsync: stopping
2024-07-19 15:37:59 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:37:59 s6-rc: info: service certsync successfully stopped
2024-07-19 15:37:59 s6-rc: info: service nginx: stopping
2024-07-19 15:37:59 s6-rc: info: service certsync-log: stopping
2024-07-19 15:37:59 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:37:59 s6-rc: info: service nginx successfully stopped
2024-07-19 15:37:59 s6-rc: info: service nginx-log: stopping
2024-07-19 15:37:59 s6-rc: info: service frigate: stopping
2024-07-19 15:37:59 s6-rc: info: service frigate successfully stopped
2024-07-19 15:37:59 s6-rc: info: service go2rtc: stopping
2024-07-19 15:37:59 s6-rc: info: service frigate-log: stopping
2024-07-19 15:37:59 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:37:59 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:37:59 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:37:59 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:37:59 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:37:59 s6-rc: info: service log-prepare: stopping
2024-07-19 15:37:59 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:37:59 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:37:59 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:37:59 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:37:59 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:37:59 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:37:59 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:37:59 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:37:59 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:39:03 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:39:03 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:39:03 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:39:03 s6-rc: info: service fix-attrs: starting
2024-07-19 15:39:03 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:39:03 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:39:03 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:39:03 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:39:03 s6-rc: info: service log-prepare: starting
2024-07-19 15:39:03 s6-rc: info: service log-prepare successfully started
2024-07-19 15:39:03 s6-rc: info: service nginx-log: starting
2024-07-19 15:39:03 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:39:03 s6-rc: info: service frigate-log: starting
2024-07-19 15:39:03 s6-rc: info: service certsync-log: starting
2024-07-19 15:39:03 s6-rc: info: service nginx-log successfully started
2024-07-19 15:39:03 s6-rc: info: service frigate-log successfully started
2024-07-19 15:39:03 s6-rc: info: service certsync-log successfully started
2024-07-19 15:39:03 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:39:03 s6-rc: info: service go2rtc: starting
2024-07-19 15:39:03 s6-rc: info: service go2rtc successfully started
2024-07-19 15:39:03 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:39:03 s6-rc: info: service frigate: starting
2024-07-19 15:39:03 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:39:03 s6-rc: info: service frigate successfully started
2024-07-19 15:39:03 s6-rc: info: service nginx: starting
2024-07-19 15:39:03 s6-rc: info: service nginx successfully started
2024-07-19 15:39:03 s6-rc: info: service certsync: starting
2024-07-19 15:39:03 s6-rc: info: service certsync successfully started
2024-07-19 15:39:03 s6-rc: info: service legacy-services: starting
2024-07-19 15:39:03 s6-rc: info: service legacy-services successfully started
2024-07-19 15:39:03 s6-rc: info: service legacy-services: stopping
2024-07-19 15:39:03 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:39:03 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:39:03 s6-rc: info: service certsync: stopping
2024-07-19 15:39:04 s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-07-19 15:39:04 s6-rc: info: service certsync successfully stopped
2024-07-19 15:39:04 s6-rc: info: service nginx: stopping
2024-07-19 15:39:04 s6-rc: info: service certsync-log: stopping
2024-07-19 15:39:04 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:39:04 s6-rc: info: service nginx successfully stopped
2024-07-19 15:39:04 s6-rc: info: service nginx-log: stopping
2024-07-19 15:39:04 s6-rc: info: service frigate: stopping
2024-07-19 15:39:04 s6-rc: info: service frigate successfully stopped
2024-07-19 15:39:04 s6-rc: info: service go2rtc: stopping
2024-07-19 15:39:04 s6-rc: info: service frigate-log: stopping
2024-07-19 15:39:04 s6-rc: info: service nginx-log successfully stopped
2024-07-19 15:39:04 s6-rc: info: service frigate-log successfully stopped
2024-07-19 15:39:04 s6-rc: info: service go2rtc successfully stopped
2024-07-19 15:39:04 s6-rc: info: service go2rtc-log: stopping
2024-07-19 15:39:04 s6-rc: info: service go2rtc-log successfully stopped
2024-07-19 15:39:04 s6-rc: info: service log-prepare: stopping
2024-07-19 15:39:04 s6-rc: info: service s6rc-fdholder: stopping
2024-07-19 15:39:04 s6-rc: info: service log-prepare successfully stopped
2024-07-19 15:39:04 s6-rc: info: service legacy-cont-init: stopping
2024-07-19 15:39:04 s6-rc: info: service s6rc-fdholder successfully stopped
2024-07-19 15:39:04 s6-rc: info: service legacy-cont-init successfully stopped
2024-07-19 15:39:04 s6-rc: info: service fix-attrs: stopping
2024-07-19 15:39:04 s6-rc: info: service fix-attrs successfully stopped
2024-07-19 15:39:04 s6-rc: info: service s6rc-oneshot-runner: stopping
2024-07-19 15:39:04 s6-rc: info: service s6rc-oneshot-runner successfully stopped
2024-07-19 15:40:08 s6-rc: info: service s6rc-fdholder: starting
2024-07-19 15:40:08 s6-rc: info: service s6rc-oneshot-runner: starting
2024-07-19 15:40:08 s6-rc: info: service s6rc-oneshot-runner successfully started
2024-07-19 15:40:08 s6-rc: info: service fix-attrs: starting
2024-07-19 15:40:08 s6-rc: info: service s6rc-fdholder successfully started
2024-07-19 15:40:08 s6-rc: info: service fix-attrs successfully started
2024-07-19 15:40:08 s6-rc: info: service legacy-cont-init: starting
2024-07-19 15:24:51 2024-07-19 15:24:51.979834235  2024/07/19 15:24:51 [error] 160#160: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "localhost:5000"
2024-07-19 15:24:51 2024-07-19 15:24:51.979841403  2024/07/19 15:24:51 [error] 160#160: *1 auth request unexpected status: 502 while sending to client, client: 172.18.0.1, server: , request: "GET /ws HTTP/1.1", host: "localhost:5000"
2024-07-19 15:24:51 2024-07-19 15:24:51.979852632  172.18.0.1 - - [19/Jul/2024:15:24:51 +0500] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0" "-"
2024-07-19 15:24:52 2024-07-19 15:24:52.190574608  [INFO] Starting go2rtc...
2024-07-19 15:24:52 2024-07-19 15:24:52.338479824  15:24:52.338 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:24:52 2024-07-19 15:24:52.338485873  15:24:52.338 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:24:52 2024-07-19 15:24:52.339851524  15:24:52.339 INF [api] listen addr=:1984
2024-07-19 15:24:52 2024-07-19 15:24:52.341553195  15:24:52.341 INF [rtsp] listen addr=:8554
2024-07-19 15:24:52 2024-07-19 15:24:52.341829194  15:24:52.341 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:24:52 2024-07-19 15:24:52.852401503  [INFO] Starting certsync...
2024-07-19 15:24:52 2024-07-19 15:24:52.874825132  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:24:52 2024-07-19 15:24:52.875148994  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:24:53 2024-07-19 15:24:53.023686675  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:24:53 2024-07-19 15:24:53.028119007  exit with signal: terminated
2024-07-19 15:24:53 2024-07-19 15:24:53.032114789  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:25:57 2024-07-19 15:25:57.606069666  [INFO] Preparing Frigate...
2024-07-19 15:25:57 2024-07-19 15:25:57.606243923  [ERROR] Frigate config file not found
2024-07-19 15:25:57 2024-07-19 15:25:57.609439048  [INFO] Starting NGINX...
2024-07-19 15:25:57 2024-07-19 15:25:57.613707766  [INFO] Preparing new go2rtc config...
2024-07-19 15:25:57 2024-07-19 15:25:57.614019215  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:25:57 2024-07-19 15:25:57.692729259  [INFO] Starting certsync...
2024-07-19 15:25:57 2024-07-19 15:25:57.732380290  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:25:57 2024-07-19 15:25:57.744770800  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:25:58 2024-07-19 15:25:58.004862276  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:25:58 2024-07-19 15:25:58.012946548  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:27:02 2024-07-19 15:27:02.656670643  [INFO] Preparing Frigate...
2024-07-19 15:27:02 2024-07-19 15:27:02.656732288  [ERROR] Frigate config file not found
2024-07-19 15:27:02 2024-07-19 15:27:02.658548202  [INFO] Preparing new go2rtc config...
2024-07-19 15:27:02 2024-07-19 15:27:02.659430650  [INFO] Starting NGINX...
2024-07-19 15:27:02 2024-07-19 15:27:02.661431031  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:27:02 2024-07-19 15:27:02.737097195  [INFO] Starting certsync...
2024-07-19 15:27:02 2024-07-19 15:27:02.754968120  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:27:02 2024-07-19 15:27:02.755909738  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:27:02 2024-07-19 15:27:02.927032695  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:27:02 2024-07-19 15:27:02.934875001  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:28:07 2024-07-19 15:28:07.479332080  [INFO] Preparing Frigate...
2024-07-19 15:28:07 2024-07-19 15:28:07.479432619  [ERROR] Frigate config file not found
2024-07-19 15:28:07 2024-07-19 15:28:07.481625296  [INFO] Starting NGINX...
2024-07-19 15:28:07 2024-07-19 15:28:07.486948028  [INFO] Preparing new go2rtc config...
2024-07-19 15:28:07 2024-07-19 15:28:07.487488179  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:28:07 2024-07-19 15:28:07.566987100  [INFO] Starting certsync...
2024-07-19 15:28:07 2024-07-19 15:28:07.599802896  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:28:07 2024-07-19 15:28:07.604491388  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:28:07 2024-07-19 15:28:07.860101570  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:28:07 2024-07-19 15:28:07.867813359  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:29:12 2024-07-19 15:29:12.404462811  [INFO] Preparing new go2rtc config...
2024-07-19 15:29:12 2024-07-19 15:29:12.406618413  [INFO] Starting NGINX...
2024-07-19 15:29:12 2024-07-19 15:29:12.407341797  [INFO] Preparing Frigate...
2024-07-19 15:29:12 2024-07-19 15:29:12.407424848  [ERROR] Frigate config file not found
2024-07-19 15:29:12 2024-07-19 15:29:12.412749696  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:29:12 2024-07-19 15:29:12.810790879  [INFO] Starting go2rtc...
2024-07-19 15:29:12 2024-07-19 15:29:12.961056579  15:29:12.960 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:29:12 2024-07-19 15:29:12.961097056  15:29:12.961 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:29:12 2024-07-19 15:29:12.962390176  15:29:12.962 INF [api] listen addr=:1984
2024-07-19 15:29:12 2024-07-19 15:29:12.962480098  15:29:12.962 INF [rtsp] listen addr=:8554
2024-07-19 15:29:12 2024-07-19 15:29:12.962849032  15:29:12.962 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:29:13 2024-07-19 15:29:13.489643769  [INFO] Starting certsync...
2024-07-19 15:29:13 2024-07-19 15:29:13.526070662  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:29:13 2024-07-19 15:29:13.527444910  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:29:13 2024-07-19 15:29:13.742552663  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:29:13 2024-07-19 15:29:13.747751187  exit with signal: terminated
2024-07-19 15:29:13 2024-07-19 15:29:13.751830964  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:30:18 2024-07-19 15:30:18.309709024  [INFO] Preparing Frigate...
2024-07-19 15:30:18 2024-07-19 15:30:18.309767749  [ERROR] Frigate config file not found
2024-07-19 15:30:18 2024-07-19 15:30:18.311867354  [INFO] Starting NGINX...
2024-07-19 15:30:18 2024-07-19 15:30:18.313874283  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:30:18 2024-07-19 15:30:18.347817083  [INFO] Preparing new go2rtc config...
2024-07-19 15:30:18 2024-07-19 15:30:18.414115738  [INFO] Starting certsync...
2024-07-19 15:30:18 2024-07-19 15:30:18.428994581  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:30:18 2024-07-19 15:30:18.431712112  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:30:18 2024-07-19 15:30:18.583828592  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:30:18 2024-07-19 15:30:18.590648757  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:31:23 2024-07-19 15:31:23.200696195  [INFO] Preparing Frigate...
2024-07-19 15:31:23 2024-07-19 15:31:23.200754617  [ERROR] Frigate config file not found
2024-07-19 15:31:23 2024-07-19 15:31:23.201920870  [INFO] Preparing new go2rtc config...
2024-07-19 15:31:23 2024-07-19 15:31:23.203010814  [INFO] Starting NGINX...
2024-07-19 15:31:23 2024-07-19 15:31:23.205301699  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:31:23 2024-07-19 15:31:23.283246916  [INFO] Starting certsync...
2024-07-19 15:31:23 2024-07-19 15:31:23.299424936  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:31:23 2024-07-19 15:31:23.300109042  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:31:23 2024-07-19 15:31:23.450422667  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:31:23 2024-07-19 15:31:23.457585544  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:32:28 2024-07-19 15:32:28.046984559  [INFO] Preparing new go2rtc config...
2024-07-19 15:32:28 2024-07-19 15:32:28.047403136  [INFO] Starting NGINX...
2024-07-19 15:32:28 2024-07-19 15:32:28.048330366  [INFO] Preparing Frigate...
2024-07-19 15:32:28 2024-07-19 15:32:28.048405825  [ERROR] Frigate config file not found
2024-07-19 15:32:28 2024-07-19 15:32:28.053363756  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:32:28 2024-07-19 15:32:28.478152388  [INFO] Starting go2rtc...
2024-07-19 15:32:28 2024-07-19 15:32:28.628661699  15:32:28.628 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:32:28 2024-07-19 15:32:28.628667991  15:32:28.628 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:32:28 2024-07-19 15:32:28.629653332  15:32:28.629 INF [rtsp] listen addr=:8554
2024-07-19 15:32:28 2024-07-19 15:32:28.629657073  15:32:28.629 INF [api] listen addr=:1984
2024-07-19 15:32:28 2024-07-19 15:32:28.629658776  15:32:28.629 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:32:29 2024-07-19 15:32:29.132231669  [INFO] Starting certsync...
2024-07-19 15:32:29 2024-07-19 15:32:29.167093080  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:32:29 2024-07-19 15:32:29.168509624  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:32:29 2024-07-19 15:32:29.327551033  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:32:29 2024-07-19 15:32:29.335689337  exit with signal: terminated
2024-07-19 15:32:29 2024-07-19 15:32:29.339944906  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:33:33 2024-07-19 15:33:33.912376285  [INFO] Preparing Frigate...
2024-07-19 15:33:33 2024-07-19 15:33:33.912466730  [ERROR] Frigate config file not found
2024-07-19 15:33:33 2024-07-19 15:33:33.917996302  [INFO] Preparing new go2rtc config...
2024-07-19 15:33:33 2024-07-19 15:33:33.920347472  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:33:33 2024-07-19 15:33:33.927803818  [INFO] Starting NGINX...
2024-07-19 15:33:34 2024-07-19 15:33:34.452600280  [INFO] Starting go2rtc...
2024-07-19 15:33:34 2024-07-19 15:33:34.597546610  15:33:34.597 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:33:34 2024-07-19 15:33:34.597553199  15:33:34.597 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:33:34 2024-07-19 15:33:34.598103165  15:33:34.598 INF [api] listen addr=:1984
2024-07-19 15:33:34 2024-07-19 15:33:34.598970778  15:33:34.598 INF [rtsp] listen addr=:8554
2024-07-19 15:33:34 2024-07-19 15:33:34.599423895  15:33:34.599 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:33:35 2024-07-19 15:33:35.067497366  [INFO] Starting certsync...
2024-07-19 15:33:35 2024-07-19 15:33:35.080867339  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:33:35 2024-07-19 15:33:35.081991409  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:33:35 2024-07-19 15:33:35.231954769  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:33:35 2024-07-19 15:33:35.241252691  exit with signal: terminated
2024-07-19 15:33:35 2024-07-19 15:33:35.246038596  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:34:39 2024-07-19 15:34:39.913613027  [INFO] Preparing Frigate...
2024-07-19 15:34:39 2024-07-19 15:34:39.913784059  [ERROR] Frigate config file not found
2024-07-19 15:34:39 2024-07-19 15:34:39.920609111  [INFO] Starting NGINX...
2024-07-19 15:34:39 2024-07-19 15:34:39.921171904  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:34:39 2024-07-19 15:34:39.921233882  [INFO] Preparing new go2rtc config...
2024-07-19 15:34:40 2024-07-19 15:34:40.404800210  [INFO] Starting go2rtc...
2024-07-19 15:34:40 2024-07-19 15:34:40.574877764  15:34:40.574 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:34:40 2024-07-19 15:34:40.574882159  15:34:40.574 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:34:40 2024-07-19 15:34:40.575641143  15:34:40.575 INF [api] listen addr=:1984
2024-07-19 15:34:40 2024-07-19 15:34:40.577431066  15:34:40.577 INF [rtsp] listen addr=:8554
2024-07-19 15:34:40 2024-07-19 15:34:40.577763390  15:34:40.577 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:34:41 2024-07-19 15:34:41.011962313  [INFO] Starting certsync...
2024-07-19 15:34:41 2024-07-19 15:34:41.026614191  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:34:41 2024-07-19 15:34:41.028037900  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:34:41 2024-07-19 15:34:41.204725948  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:34:41 2024-07-19 15:34:41.211202323  exit with signal: terminated
2024-07-19 15:34:41 2024-07-19 15:34:41.217959397  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:35:45 2024-07-19 15:35:45.879269160  [INFO] Preparing Frigate...
2024-07-19 15:35:45 2024-07-19 15:35:45.879337776  [ERROR] Frigate config file not found
2024-07-19 15:35:45 2024-07-19 15:35:45.879514016  [INFO] Preparing new go2rtc config...
2024-07-19 15:35:45 2024-07-19 15:35:45.891361746  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:35:45 2024-07-19 15:35:45.892377661  [INFO] Starting NGINX...
2024-07-19 15:35:46 2024-07-19 15:35:46.401101035  [INFO] Starting go2rtc...
2024-07-19 15:35:46 2024-07-19 15:35:46.605555073  15:35:46.605 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:35:46 2024-07-19 15:35:46.605569119  15:35:46.605 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:35:46 2024-07-19 15:35:46.606714535  15:35:46.606 INF [api] listen addr=:1984
2024-07-19 15:35:46 2024-07-19 15:35:46.606900258  15:35:46.606 INF [rtsp] listen addr=:8554
2024-07-19 15:35:46 2024-07-19 15:35:46.610173089  15:35:46.608 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:35:47 2024-07-19 15:35:47.013606371  [INFO] Starting certsync...
2024-07-19 15:35:47 2024-07-19 15:35:47.034939513  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:35:47 2024-07-19 15:35:47.037370157  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:35:47 2024-07-19 15:35:47.217423356  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:35:47 2024-07-19 15:35:47.224677493  exit with signal: terminated
2024-07-19 15:35:47 2024-07-19 15:35:47.231267331  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:36:52 2024-07-19 15:36:52.125008922  [INFO] Starting NGINX...
2024-07-19 15:36:52 2024-07-19 15:36:52.124985666  [INFO] Preparing Frigate...
2024-07-19 15:36:52 2024-07-19 15:36:52.125440372  [ERROR] Frigate config file not found
2024-07-19 15:36:52 2024-07-19 15:36:52.127936043  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:36:52 2024-07-19 15:36:52.171179284  [INFO] Preparing new go2rtc config...
2024-07-19 15:36:53 2024-07-19 15:36:53.131163875  [INFO] Starting go2rtc...
2024-07-19 15:36:53 2024-07-19 15:36:53.261604054  [INFO] Starting certsync...
2024-07-19 15:36:53 2024-07-19 15:36:53.278882448  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:36:53 2024-07-19 15:36:53.280279856  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:36:53 2024-07-19 15:36:53.332511978  15:36:53.332 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:36:53 2024-07-19 15:36:53.332582522  15:36:53.332 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:36:53 2024-07-19 15:36:53.334955990  15:36:53.334 INF [api] listen addr=:1984
2024-07-19 15:36:53 2024-07-19 15:36:53.335594013  15:36:53.335 INF [rtsp] listen addr=:8554
2024-07-19 15:36:53 2024-07-19 15:36:53.336017743  15:36:53.335 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:36:53 2024-07-19 15:36:53.441139121  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:36:53 2024-07-19 15:36:53.445135392  exit with signal: terminated
2024-07-19 15:36:53 2024-07-19 15:36:53.451330424  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:37:58 2024-07-19 15:37:58.036886698  [INFO] Preparing Frigate...
2024-07-19 15:37:58 2024-07-19 15:37:58.036975821  [ERROR] Frigate config file not found
2024-07-19 15:37:58 2024-07-19 15:37:58.039896655  [INFO] Preparing new go2rtc config...
2024-07-19 15:37:58 2024-07-19 15:37:58.044101624  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:37:58 2024-07-19 15:37:58.044319451  [INFO] Starting NGINX...
2024-07-19 15:37:58 2024-07-19 15:37:58.467413908  [INFO] Starting go2rtc...
2024-07-19 15:37:58 2024-07-19 15:37:58.630727183  15:37:58.630 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-07-19 15:37:58 2024-07-19 15:37:58.630733014  15:37:58.630 INF config path=/dev/shm/go2rtc.yaml
2024-07-19 15:37:58 2024-07-19 15:37:58.631868840  15:37:58.631 INF [rtsp] listen addr=:8554
2024-07-19 15:37:58 2024-07-19 15:37:58.631873278  15:37:58.631 INF [webrtc] listen addr=:8555/tcp
2024-07-19 15:37:58 2024-07-19 15:37:58.631875248  15:37:58.631 INF [api] listen addr=:1984
2024-07-19 15:37:59 2024-07-19 15:37:59.127612884  [INFO] Starting certsync...
2024-07-19 15:37:59 2024-07-19 15:37:59.142481404  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:37:59 2024-07-19 15:37:59.143697520  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:37:59 2024-07-19 15:37:59.296543860  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:37:59 2024-07-19 15:37:59.301556449  exit with signal: terminated
2024-07-19 15:37:59 2024-07-19 15:37:59.306087130  [INFO] The go2rtc service exited with code 0 (by signal 0)
2024-07-19 15:39:03 2024-07-19 15:39:03.898278578  [INFO] Preparing Frigate...
2024-07-19 15:39:03 2024-07-19 15:39:03.898358781  [ERROR] Frigate config file not found
2024-07-19 15:39:03 2024-07-19 15:39:03.901347766  [INFO] Starting NGINX...
2024-07-19 15:39:03 2024-07-19 15:39:03.901473522  [INFO] Preparing new go2rtc config...
2024-07-19 15:39:03 2024-07-19 15:39:03.903144053  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:39:03 2024-07-19 15:39:03.991636650  [INFO] Starting certsync...
2024-07-19 15:39:04 2024-07-19 15:39:04.003972966  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:39:04 2024-07-19 15:39:04.005057168  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:39:04 2024-07-19 15:39:04.178050719  [INFO] Service NGINX exited with code 0 (by signal 0)
2024-07-19 15:39:04 2024-07-19 15:39:04.184818801  [INFO] The go2rtc service exited with code 256 (by signal 15)
2024-07-19 15:40:08 2024-07-19 15:40:08.792490148  [INFO] Preparing Frigate...
2024-07-19 15:40:08 2024-07-19 15:40:08.792602091  [ERROR] Frigate config file not found
2024-07-19 15:40:08 2024-07-19 15:40:08.794199262  [INFO] Starting NGINX...
2024-07-19 15:40:08 2024-07-19 15:40:08.799168758  [INFO] Preparing new go2rtc config...
2024-07-19 15:40:08 2024-07-19 15:40:08.802580457  [INFO] Service Frigate exited with code 1 (by signal 0)
2024-07-19 15:40:08 s6-rc: info: service legacy-cont-init successfully started
2024-07-19 15:40:08 s6-rc: info: service log-prepare: starting
2024-07-19 15:40:08 s6-rc: info: service log-prepare successfully started
2024-07-19 15:40:08 s6-rc: info: service nginx-log: starting
2024-07-19 15:40:08 s6-rc: info: service go2rtc-log: starting
2024-07-19 15:40:08 s6-rc: info: service frigate-log: starting
2024-07-19 15:40:08 s6-rc: info: service certsync-log: starting
2024-07-19 15:40:08 s6-rc: info: service nginx-log successfully started
2024-07-19 15:40:08 s6-rc: info: service certsync-log successfully started
2024-07-19 15:40:08 s6-rc: info: service go2rtc-log successfully started
2024-07-19 15:40:08 s6-rc: info: service go2rtc: starting
2024-07-19 15:40:08 s6-rc: info: service frigate-log successfully started
2024-07-19 15:40:08 s6-rc: info: service go2rtc successfully started
2024-07-19 15:40:08 s6-rc: info: service go2rtc-healthcheck: starting
2024-07-19 15:40:08 s6-rc: info: service frigate: starting
2024-07-19 15:40:08 s6-rc: info: service frigate successfully started
2024-07-19 15:40:08 s6-rc: info: service nginx: starting
2024-07-19 15:40:08 s6-rc: info: service go2rtc-healthcheck successfully started
2024-07-19 15:40:08 s6-rc: info: service nginx successfully started
2024-07-19 15:40:08 s6-rc: info: service certsync: starting
2024-07-19 15:40:08 s6-rc: info: service certsync successfully started
2024-07-19 15:40:08 s6-rc: info: service legacy-services: starting
2024-07-19 15:40:08 2024-07-19 15:40:08.890107911  [INFO] Starting certsync...
2024-07-19 15:40:08 s6-rc: info: service legacy-services successfully started
2024-07-19 15:40:08 s6-rc: info: service legacy-services: stopping
2024-07-19 15:40:08 s6-rc: info: service legacy-services successfully stopped
2024-07-19 15:40:08 s6-rc: info: service go2rtc-healthcheck: stopping
2024-07-19 15:40:08 s6-rc: info: service certsync: stopping
2024-07-19 15:40:08 2024-07-19 15:40:08.908225455  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
2024-07-19 15:40:08 2024-07-19 15:40:08.908588279  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-07-19 15:40:08 s6-rc: info: service certsync successfully stopped
2024-07-19 15:40:08 s6-rc: info: service nginx: stopping
2024-07-19 15:40:08 s6-rc: info: service certsync-log: stopping
2024-07-19 15:40:08 s6-rc: info: service certsync-log successfully stopped
2024-07-19 15:40:08 s6-rc: info: service go2rtc-healthcheck successfully stopped

3 replies

NickM-27 Jul 19, 2024
Collaborator Sponsor

2024-07-19 15:22:37 2024-07-19 15:22:37.366663213 [ERROR] Frigate config file not found

is the issue

NickM-27 Jul 22, 2024
Collaborator Sponsor

let's see the logs

NickM-27 Jul 22, 2024
Collaborator Sponsor

[tcp @ 0x55f38de70540] Connection to tcp://[192.168.1.10:554?timeout=5000000](http://192.168.1.10:554/?timeout=5000000) failed: Connection timed out the camera connection is timing out

wookie666 · 2024-09-22T07:15:09Z

wookie666
Sep 22, 2024

Dude, i just wanted to say thank you.
ive been running on docker for windows for a little bit now with constant issues. Just runniing wsl and ubuntu, and changing storage and config locations and everything is so much smoother now.
Thanks again

0 replies

Andries1234 · 2024-10-17T13:30:05Z

Andries1234
Oct 17, 2024

Hi Man,

Thanks for this. I am just strugling with getting the Nvidia GPU to work as detector in WSL2 and docker desktop.

this command shows error 404 and I also can not go to the Website.

wget https://github.com/blakeblackshear/frigate/raw/master/docker/tensorrt_models.sh

I do not see this file tensorrt_models.sh

6 replies

Andries1234 Oct 17, 2024

Hi Thanks for quick response I will have a look at that.

Andries1234 Oct 17, 2024

Hi I have followed this. but I am getting these errors
2024-10-17 19:19:52 /usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py:149: DeprecationWarning: Use network created with NetworkDefinitionCreationFlag::EXPLICIT_BATCH flag instead.
2024-10-17 19:19:52 builder.max_batch_size = MAX_BATCH_SIZE
2024-10-17 19:19:52 /usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py:151: DeprecationWarning: Use set_memory_pool_limit instead.
2024-10-17 19:19:52 config.max_workspace_size = 1 << 30
2024-10-17 19:19:52 /usr/local/src/tensorrt_demos/yolo/onnx_to_tensorrt.py:174: DeprecationWarning: Use build_serialized_network instead.
2024-10-17 19:19:52 engine = builder.build_engine(network, config)
2024-10-17 19:19:54 2024-10-17 19:19:54.509307594

NickM-27 Oct 17, 2024
Collaborator Sponsor

those are all warnings, there is no indication of an error

Andries1234 Oct 17, 2024

Hi yeah I see now, sorry for that.

My problem is that the docker container does start but not work. It just stays with that warnings.

I will check again from scratch to see what I missed.

NickM-27 Oct 17, 2024
Collaborator Sponsor

are you sure it is not just building the model?

Andries1234 · 2024-10-17T18:12:40Z

Andries1234
Oct 17, 2024

No it gets stuck and CPU usage went through the roof I manage to fix it not quite sure what I did.

…

On Thu, 17 Oct 2024, 19:56 Nicolas Mowen, ***@***.***> wrote: are you sure it is not just building the model? — Reply to this email directly, view it on GitHub <#4375 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVL5HRFONRIPSSHFGOWYD7TZ3724FAVCNFSM6AAAAAAR52USTSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJXGQ4DANI> . You are receiving this because you commented.Message ID: ***@***.*** com>

0 replies

khalidaboelmagd · 2024-12-03T07:59:58Z

khalidaboelmagd
Dec 3, 2024

Hi ,
I've installed frigate beta 0.15 on docker with wsl2 and passed coral usb using usbipd ,
but yet cannot pass GPU ,
in the new beta i noticed that large indexing using GPU and during the index my GPU utilization is very high ,
and I think it is using openvino is there any way to build ffmpeg that will use openvino for decoding videos ?
if possible then frigate on wsl2 will be fully function with GPU ..
note: I tried to use vaapi , it works for a bit but suddenly my camera 1 ffmpeg crash due to drm permission denied
I've other reolink doorbell and ffmpeg is working without any issues

any ideas ?

0 replies

geckyo · 2025-02-17T04:01:25Z

geckyo
Feb 17, 2025

Forgive me I am a total noob when it comes to this stuff.
When I get to section 9

Now let's spin up the container using our Docker Compose file. Open up a PowerShell window (connected to your Windows host, not your WSL instance) if you don't already have one open (see the paragraph above step 1 on choosing the "right" PowerShell to open if you have question). Navigate to the directory where you compose file is located. You can do this by typing "cd c:\folder\path" where c:\folder\path is the directory the file is stored. Now type/paste in "docker-compose up -d". You should see a result returned such as "Running". Interested in what this command and other relevant Docker arguments mean? Check out https://docs.docker.com/engine/reference/commandline/compose_up/

I am running the regular power shell. I copied the config.yml into a folder c:\frigate_docker\config.yml

PS C:\frigate_docker> docker-compose up -d
no configuration file provided: not found

I don't understand where the hang up is. Also the new docker for desktop install I have has no option for the following ""'use docker compose v2' is checked off. ""

13 replies

soonerfan237 Mar 2, 2025

@MinimumDowntime

At least I'm pretty sure you could 😄

I'll update it above, but since you've prompted this. Here's how you could use Windows paths (instead of WSL paths). In the volume section, use this:
- ./config:/config
-  T:\frigatemedia:/media/frigate
If you update your compose file with the above, and run it. Docker will re-create the container (as you've already downloaded the image). You'll see that the "Config" directory gets created alongside your compose file location and the media location (in this case the T: drive) would have a "frigatemedia" folder created. That said, you should be able to point those anywhere else you'd like. Of course, you can also call them anything you'd like as well.

I've got most of my setup working, except I have just hit a brick wall with using any drive other than C:\ for my media recordings.

This works:
volumes:
- ./config:/config
- \wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
-./storage:/media/frigate

This also works, specifying another folder in the C:\ drive:
volumes:
- ./config:/config
- \wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- C:\Users\username\Documents\docker_test:/media/frigate

But this does NOT work. The docker container runs, but no recordings show up on the D:\ drive folder docker_test:
volumes:
- ./config:/config
- \wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- D:\docker_test:/media/frigate

I also tried using the /mnt/d/ syntax based on some stuff I'd read, but also no luck:
volumes:
- ./config:/config
- \wsl$$\Ubuntu\etc\localtime:/etc/localtime:ro
- /mnt/d/docker_test:/media/frigate

For more context, I've tried this on a couple different external drives. First was a NAS folder that I mapped to a drive on Windows. I also tried plugging in a little external USB hard drive stick that I plugged into the front of my computer, which showed up as the D:\ drive.

Any suggestions to help trouble shoot?

MinimumDowntime Mar 21, 2025
Author

@wookie666 - how recent was this observation/configuration of yours? I ask because part of re-writing these steps above to be able to use different drives for recordings should remove that problem. In which case, the WSL instance should stay vanilla and not consume its own disk space.

MinimumDowntime Mar 21, 2025
Author

@soonerfan237 for the sake of argument, i re-read my own instructions and attempted to repro. Container spun up, established config directory and media directories as described above.

./config:/config

T:\frigatemedia:/media/frigate

After a couple of seconds, video appeared, and I coincidentally had a detection/recording occur. Media directory had a few *.mp4's in it and all played. For the sake of argument, I moved the compose file to a different directory, and changed my media path. Container rebuilds, new paths were established, video feed starts, etc.

Unfortunately I'm not sure what your issue could be.

soonerfan237 Mar 21, 2025

@MinimumDowntime thank you for following up. But I did eventually get it working a couple days after I made that last comment. I don’t know what fixed it. But I switched to a new SSD connected directly to my motherboard, instead of a network share or usb drive. It still wasn’t working initially and I was throwing stuff against the wall with random commands. The last thing I remember trying before I saw it start working was I logged into WSL as admin and used a touch command to create a new file in the directory I was trying to store recordings. After that I saw the recording files start to flow in. No idea if that specifically fixed it, but it did eventually start working.

wookie666 Apr 6, 2025

@wookie666 - how recent was this observation/configuration of yours? I ask because part of re-writing these steps above to be able to use different drives for recordings should remove that problem. In which case, the WSL instance should stay vanilla and not consume its own disk space.

Hey mate.
I've since mapped to my E:/ drive instead of inside the Ubuntu folder structure. I haven't tested the function which deletes recordings when space runs low yet because my E drive is an external portable 2tb SSD and my recording structure doesn't fill it before it deletes recordings longer than my retain time.

keyboarderror · 2025-03-07T20:24:19Z

keyboarderror
Mar 7, 2025

Just a note this guide is a bit dated at this point, for example the Nvidia GPUs and TensorRT Detectors section seems obsolete I only had to define YOLO_MODELS in the environment section of docker-compose to get it to download and generate the detectors the first time. A lots of cross reading of documentation. But I currently have a fully functional Windows WSL2 Frigate installation with GPU accelerated FFMPEG and tensor detection talking to my Home Assistant installation. Thanks!

2 replies

MinimumDowntime Mar 21, 2025
Author

Thanks for pointing this out. Would you mind sharing in detail what you've done? I'll gladly update the above.

keyboarderror Apr 6, 2025

I'd post the config.yml code but it refuses to format correctly.

keyboarderror · 2025-04-06T19:22:56Z

keyboarderror
Apr 6, 2025

In docker-compose.yaml I only had to set the enviroment

environment:      
  YOLO_MODELS: yolov7-320,yolov7x-640model:

For it to download and compile the models. Then choose a model in config.yml like normal.

My problem after testing it a few weeks is the recording review function doesn't really work. It may work briefly after starting up where it will play back after a long delay but after a while even that doesn't work any more. It just times out with the spinning circle. It does it in any browser or app, with any camera. I'm using an SSD formatted and mounted in Windows but I'm not sure about I/O throughput from WSL. Something's not right.

4 replies

MinimumDowntime Apr 7, 2025
Author

On one hand - thanks for clearing this up, on another...huh. I'm not sure how to troubleshoot that. F12/Dev Tools in a browser perhaps and see if anything noteworthy is happening in the network or console tab?

wookie666 Apr 7, 2025

In docker-compose.yaml I only had to set the enviroment
environment:      
  YOLO_MODELS: yolov7-320,yolov7x-640model:
For it to download and compile the models. Then choose a model in config.yml like normal.

My problem after testing it a few weeks is the recording review function doesn't really work. It may work briefly after starting up where it will play back after a long delay but after a while even that doesn't work any more. It just times out with the spinning circle. It does it in any browser or app, with any camera. I'm using an SSD formatted and mounted in Windows but I'm not sure about I/O throughput from WSL. Something's not right.

I have the same issue. Seems Internittent

My Vmemm keeps climbing. I started to limit that and thought that was the cause but I guess not. I would love to find out more information to make it more stable.

I initially thought it was a h265 issue with some video feeds in browsers like Firefox but it does it randomly.

Chrome dev tools just says 404 error

soonerfan237 Apr 8, 2025

I'm also experiencing this same issue.

If I navigate to my recorded .mp4 files they all play just fine in VLC. It's just that some of the segments just refuse to play in the Frigate UI. I've tried via multiple browsers (Chrome, Firefox, Safari, iOS Home Assistant app). And tried accessing Frigate via multiple methods: going to Frigate IP directly, Frigate Proxy in Home Assistant. But none of those seem to make a difference.

I'm seeing errors like this in developer tools in my browsers:
ERR_CONTENT_LENGTH_MISMATCH
NS_ERROR_NET_PARTIAL_TRANSFER

soonerfan237 Apr 8, 2025

I did a deeper dive into what could be causing those partial transfer errors. Here's some additional info I'm seeing.

Here's the http request info. The header says the file size will be ~21.2MB. But the actual size transferred shows 5.9MB. So it seems something is going wrong there.

Request URL:
http://xxx.xxx.xx.xxx:5000/vod/garage_camera/start/1744077600/end/1744081200/seg-6-v1-a1.ts
Request Method:
GET
Status Code:
200 OK
Remote Address:
xxx.xxx.xx.xxx:5000
Referrer Policy:
strict-origin-when-cross-origin
accept-ranges:
bytes
cache-control:
no-store
connection:
keep-alive
content-length:
21215800
content-type:
video/MP2T
date:
Tue, 08 Apr 2025 04:05:56 GMT
etag:
"-1-143ba38"
last-modified:
Sun, 19 Nov 2000 08:52:00 GMT
server:
nginx/1.25.3
accept:
*/*
accept-encoding:
gzip, deflate
accept-language:
en-US,en;q=0.9
connection:
keep-alive
host:
xxx.xxx.xx.xxx:5000
referer:
http://xxx.xxx.xx.xxx:5000/review
user-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.36

I also tried manually using ffmpeg command to convert my mp4 file to ts file and I'm also getting around 21.2MB. So it seems the file size advertised in the request header is correct.

So seems to be a problem in the streaming of the .ts file? Something is getting cut off or timing out?

keyboarderror · 2025-04-07T04:08:09Z

keyboarderror
Apr 7, 2025

Checking review in dev console under chrome in console all resources fail like:

BirdseyeLivePlayer-Dqa9iVX4.js:9 WebSocket connection to 'wss://192.168.1.24:8971/live/jsmpeg/family_room_ptz' failed: Received a broken close frame containing a reserved status code.

And under network there's an error:

master.m3u8 status: cancled

I see the same kinds of websocket errors in live view but nothing obviously wrong under network. It seems to work ok.

0 replies

keyboarderror · 2025-04-07T04:10:06Z

keyboarderror
Apr 7, 2025

Also I see motion and playback in the thumbnails it's only when I click on a video to fully review that it fails.

0 replies

keyboarderror · 2025-04-15T08:29:56Z

keyboarderror
Apr 15, 2025

Initial results after updating to v0.15.1 are very promising. Thank you. Review playback is now consistently working with some buffer delay. That could be my hardware.

0 replies

keyboarderror · 2025-04-16T00:02:31Z

keyboarderror
Apr 16, 2025

Well, after running for a day I'm back to failures like

`

BirdseyeLivePlayer-Dqa9iVX4.js:9 WebSocket connection to 'wss://192.168.4.24:8971/live/jsmpeg/shop_ptz' failed: WebSocket is closed before the connection is established.
BirdseyeLivePlayer-Dqa9iVX4.js:12 WebSocket connection to 'wss://192.168.4.24:8971/live/mse/api/ws?src=front_porch' failed: WebSocket is closed before the connection is established.

BirdseyeLivePlayer-Dqa9iVX4.js:9 WebSocket connection to 'wss://192.168.4.24:8971/live/jsmpeg/driveway1' failed: WebSocket is closed before the connection is established.
BirdseyeLivePlayer-Dqa9iVX4.js:9 WebSocket connection to 'wss://192.168.4.24:8971/live/jsmpeg/back_yard' failed: Received a broken close frame containing a reserved status code.`

And nothing works again. Restarting doesn't seem to help.

0 replies

Hackshaq · 2025-09-09T14:18:13Z

Hackshaq
Sep 9, 2025

I seem to be one of the one's who are not able to figure out how to set up the config file mapping. I have tried a bunch of different ways, all of which give a "No such file or directory: '/config/config.yaml'" error when trying to start the container. My config.yaml is here E:/Frigate/config/config.yaml. The docker-compose.yaml is in E:/Frigate, along with another copy of the config. The ways I have tried the mapping are:

- \wsl$$\Ubuntu-24.04\home\madhatter\frigate\config\config.yaml:/config/config.yaml
- E:/Frigate/config/config.yaml:/config/config.yaml
- E:/Frigate/config/:/config/
- ../config:/config:rw
- ./config:/config

This is my config.yaml: https://pastebin.com/GeKZKpdh
This is the docker-compose.yaml: https://pastebin.com/CgCm17qF
The full log for the container: https://pastebin.com/EZ4gEYCS

Story of my life. Works fine for everyone else. I follow directions and I spend hours debugging.
What am I doing wrong with this setup?

5 replies

NickM-27 Sep 9, 2025
Collaborator Sponsor

The logs don't contain any errors or anything past Frigate beginning to start

Hackshaq Sep 9, 2025

Hey Nick. Thanks for pointing that out. I have updated the paste for the logs.

Hackshaq Sep 9, 2025

The corrected log file is pasted here: https://pastebin.com/EZ4gEYCS

NickM-27 Sep 9, 2025
Collaborator Sponsor

You'll need to figure out where you are running docker compose from, at that point the path to the config folder should be relative to that location (of the docker-compose.yaml) and map to /config. So for example if you run pwd and you get docker-compose.yaml config then it would be ./config:/config

Hackshaq Sep 11, 2025

Cool thanks

keenlearner-404 · 2025-10-14T01:52:59Z

keenlearner-404
Oct 14, 2025

Thanks for the instructions.

When I run this command:

docker-compose up -d

I got an error:

 => ERROR [nginx 1/1] RUN --mount=type=bind,source=docker/main/build_nginx.sh,target=/deps/build_nginx.sh     /de  1.1s
 => [ov-converter 1/3] COPY docker/main/requirements-ov.txt /requirements-ov.txt                                   0.6s
 => CANCELED [ov-converter 2/3] RUN apt-get -qq update     && apt-get -qq install -y wget python3 python3-dev pyt  0.8s
------
 > [nginx 1/1] RUN --mount=type=bind,source=docker/main/build_nginx.sh,target=/deps/build_nginx.sh     /deps/build_nginx.sh:
0.932 /bin/sh: 1: /deps/build_nginx.sh: not found
------
failed to solve: process "/bin/sh -c /deps/build_nginx.sh" did not complete successfully: exit code: 127

It's true I don't have /deps/build_nginx.sh. Is it a specific issue in wsl only? How should I change this line to make it point to the correct location?

Edit:
I have fixed the issue.

change
before

RUN --mount=type=bind,source=docker/main/build_nginx.sh,target=/deps/build_nginx.sh    \
 /deps/build_nginx.sh

after

RUN --mount=type=bind,source=docker/main/build_nginx.sh,target=/deps/build_nginx.sh    \
bash /deps/build_nginx.sh

change all CR/LF to LF.

0 replies

Uh oh!

Frigate on Docker, in Windows Subsystem for Linux (WSL) #4375

Uh oh!

Uh oh!

Deploy and Configure WSL

Deploy and Configure Docker on Windows (updated 2.21.25 for v4.38.0)

Deploy and Configure Frigate

Hardware Acceleration

Limiting WSL Host Resources

Using a Google Coral USB Detector

Using Nvidia GPUs and TensorRT Detectors

Replies: 29 comments · 75 replies

Uh oh!

NickM-27 Nov 11, 2022 Collaborator Sponsor

Uh oh!

MinimumDowntime Dec 21, 2022 Author

Uh oh!

MinimumDowntime Jul 18, 2023 Author

Uh oh!

MinimumDowntime Jul 18, 2023 Author

Uh oh!

Uh oh!

MinimumDowntime Sep 1, 2023 Author

Uh oh!

Uh oh!

MinimumDowntime Nov 22, 2023 Author

Uh oh!

Uh oh!

Uh oh!

NickM-27 Dec 21, 2022 Collaborator Sponsor

Uh oh!

Uh oh!

Uh oh!

MinimumDowntime Sep 1, 2023 Author

Uh oh!

MinimumDowntime Nov 22, 2023 Author

Uh oh!

Uh oh!

NickM-27 May 8, 2023 Collaborator Sponsor

Uh oh!

Uh oh!

MinimumDowntime Aug 7, 2023 Author

Uh oh!

Uh oh!

Uh oh!

MinimumDowntime Aug 9, 2023 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

MinimumDowntime Oct 4, 2023 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

MinimumDowntime Nov 10, 2023 Author

Uh oh!

Uh oh!

Replies: 29 comments 75 replies

NickM-27
Nov 11, 2022
Collaborator Sponsor

MinimumDowntime Dec 21, 2022
Author

MinimumDowntime Jul 18, 2023
Author

MinimumDowntime Jul 18, 2023
Author

MinimumDowntime Sep 1, 2023
Author

MinimumDowntime Nov 22, 2023
Author

NickM-27 Dec 21, 2022
Collaborator Sponsor

MinimumDowntime Sep 1, 2023
Author

MinimumDowntime Nov 22, 2023
Author

NickM-27 May 8, 2023
Collaborator Sponsor

MinimumDowntime Aug 7, 2023
Author

MinimumDowntime Aug 9, 2023
Author

MinimumDowntime Oct 4, 2023
Author

MinimumDowntime Nov 10, 2023
Author