Closed Plawasan closed 8 months ago
looks like your docker compose is not using the tmpfs that is recommended in the docs for /tmp/cache, I would recommend using that https://deploy-preview-6262--frigate-docs.netlify.app/frigate/installation#common-docker-compose-storage-configurations
updated however the errors are still coming:
volumes:
- /etc/localtime:/etc/localtime
- /home/frigate/config.yml:/config/config.yml
- /mnt/cctv:/media/frigate
- /mnt/frigate-db:/media/frigate-db
- type: tmpfs
target: /tmp/cache
tmpfs:
size: 1000000000
2023-12-01 20:34:17.104199104 [h264 @ 0x7fdce41ce1c0] SEI type 5 size 1296 truncated at 976
2023-12-01 20:34:17.104415780 [h264 @ 0x7fdce41ce1c0] SEI type 5 size 1296 truncated at 968
2023-12-01 20:34:27.003615059 [h264 @ 0x7fdce41baf00] SEI type 5 size 1296 truncated at 976
2023-12-01 20:34:27.003715688 [h264 @ 0x7fdce41baf00] SEI type 5 size 1296 truncated at 968
2023-12-01 20:34:27.025381634 [h264 @ 0x7fdce41baf00] SEI type 5 size 1296 truncated at 976
2023-12-01 20:34:27.025513296 [h264 @ 0x7fdce41baf00] SEI type 5 size 1296 truncated at 968
2023-12-01 20:34:37.012429343 [h264 @ 0x7fdce411d580] SEI type 5 size 1296 truncated at 976
2023-12-01 20:34:37.012600602 [h264 @ 0x7fdce411d580] SEI type 5 size 1296 truncated at 968
2023-12-01 20:34:37.032819475 [h264 @ 0x7fdce411d580] SEI type 5 size 1296 truncated at 976
2023-12-01 20:34:37.032919171 [h264 @ 0x7fdce411d580] SEI type 5 size 1296 truncated at 968
2023-12-01 20:34:37.100765264 [h264 @ 0x7fdce411d580] SEI type 5 size 1296 truncated at 976
Let me try and reduce my config to a single camera to see if anything changes.
I would get a shell in the container and see what the contents of /tmp/cache are
root@86ce54720b58:/opt/frigate# cd /tmp/cache/
root@86ce54720b58:/tmp/cache# ls -l
total 30864
prwxr-xr-x 1 root root 0 Dec 1 20:42 birdseye
-rw-r--r-- 1 root root 7210053 Dec 1 20:55 entry_camera@20231201205508+0100.mp4
-rw-r--r-- 1 root root 1835056 Dec 1 20:55 entry_camera@20231201205518+0100.mp4
-rw-r--r-- 1 root root 7235063 Dec 1 20:55 garage_camera@20231201205507+0100.mp4
-rw-r--r-- 1 root root 2097200 Dec 1 20:55 garage_camera@20231201205518+0100.mp4
-rw-r--r-- 1 root root 1835056 Dec 1 20:55 garden_camera@20231201205518+0100.mp4
-rw-r--r-- 1 root root 1835056 Dec 1 20:55 sidefront_camera@20231201205517+0100.mp4
-rw-r--r-- 1 root root 5722672 Dec 1 20:55 siderear_camera@20231201205508+0100.mp4
-rw-r--r-- 1 root root 3407920 Dec 1 20:55 siderear_camera@20231201205516+0100.mp4
-rw-r--r-- 1 root root 392926 Dec 1 20:55 tapo@20231201205506+0100.mp4
-rw-r--r-- 1 root root 48 Dec 1 20:55 tapo@20231201205516+0100.mp4
root@86ce54720b58:/tmp/cache#
Ah I think I see, you have not set the detect width and height, this is recommended even in 0.13
If only that was pinned on top of the list of issues :) ... I even read that, I was just relying on the fact that my cameras natively produce a 1280x720 subfeed that I'm using for detection and the only one that doesn't has detect turned off..
anyway, added the following to my config:
detect:
annotation_offset: -1400
width: 1280
height: 720
and then specifically under the the camera that doesn't have a subfeed (tapo):
detect:
width: 2304
height: 1296
still getting the same errors though :/
interesting, I have no idea what would be producing these logs in that case then
To me it looks like a ffmpeg bug/issue, when I googled this (i really did!) the closest I got was this - https://stackoverflow.com/questions/22823599/ffmpeg-decode-video-h264-with-warning-sei-type-truncated-error-concealment ..
it's not that simple though, frigate captures all ffmpeg logs and only prints them when needed (and includes info like the log level and timestamp). Something is logging to the frigate pipe without frigate knowing about it
I've removed all but one camera from my config and the errors are gone (for the last 10 mins at least), I will try to isolate the cause tomorrow when I have the time..
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
For the record - I've tried every single setting I could think of in the video config of my cameras, I've been able to narrow the issue down to only one type of camera (of which I have 4...) but I have not been able to either eliminate it or reduce it. It doesn't seem to be causing any issues other than flooding logs so I guess I'll learn to live with it.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
Since upgrading to 0.13-beta5 (and now on beta6) my logs are filled with the following error messages:
I'm running 5 Uniview cameras and 1 Tapo (C210) however I cannot easily tell from the log if these errors are specific to a camera.
Version
0.13.0-614A36A
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Proxmox
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Uniview/TapoC210
Any other information that may be helpful
Docker compose:
Camera setup (can't really tell which camera is causing it though)