ElixirForge/frigate
1
0
Fork 0
mirror of https://github.com/alexhopeoconnor/frigate.git synced 2026-10-19 01:41:31 +10:00
Code Releases Activity

docs: move docs to docusaurus

Browse Source
This commit is contained in:
Paul Armstrong
2021-01-26 21:40:33 -06:00
committed by Blake Blackshear
parent d315dbea22
commit 6790467bbc
44 changed files with 15722 additions and 1234 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/troubleshooting.md
+21
View File
@@ -0,0 +1,21 @@
---
id: troubleshooting
title: Troubleshooting
---
## "[mov,mp4,m4a,3gp,3g2,mj2 @ 0x5639eeb6e140] moov atom not found"
These messages in the logs are expected in certain situations. Frigate checks the integrity of the video cache before assembling clips. Occasionally these cached files will be invalid and cleaned up automatically.
## "ffmpeg didnt return a frame. something is wrong"
Turn on logging for the ffmpeg process by overriding the global_args and setting the log level to `info` (the default is `fatal`). Note that all ffmpeg logs show up in the Frigate logs as `ERROR` level. This does not mean they are actually errors.
```yaml
ffmpeg:
global_args: -hide_banner -loglevel info
```
## "On connect called"
If you see repeated "On connect called" messages in your config, check for another instance of frigate. This happens when multiple frigate containers are trying to connect to mqtt with the same client_id.