Closed sshaikh closed 10 months ago
What is your docker compose?
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: "150mb" # update for your cameras based on calculation above
devices:
# - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions
- /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://coral.ai/docs/m2/get-started/#2a-on-linux
#- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /home/cctv/frigate/config.yml:/config/config.yml:rw
- /home/cctv/go2rtc/go2rtc:/config/go2rtc:ro
- /cctv-storage/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
- "1935:1935" # RTMP feeds
environment:
FRIGATE_RTSP_PASSWORD: "xxx"
FRIGATE_MQTT_PASSWORD: "yyy"
it is showing signs of CPU overwork, easiest to diagnose will be if you enable debug logs for recordings
logger:
logs:
frigate.record: debug
and then paste all logs here after you see one that says something like 2023-10-07 00:06:47.994950326 [2023-10-07 00:06:47] frigate.record WARNING : Unable to keep up with recording segments in cache for doorbell. Keeping the 5 most recent segments out of 9 and discarding the rest...
I've had this for a few days now and no longer see Unable to keep up
log lines. I am still seeing Unable to create jpg because frame 1697110156.642571 is not in the cache
though.
that error has been fixed in 0.13 (currently in beta)
Ok - happy to move to beta or wait till release before revisiting this. Let me know which is more useful for the project.
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
I see the following lines in my log - they seem to have started at the same time so I am assuming they are related (see later section for log entries).
The first happens across cameras, the others I can't tell which camera they relate to.
I suspect it's a resource issue but can confirm storage is available (a stable 72% in use as retain is enabled). CPU sits at 30-40%, 5m load is 2-2.5.
I've noticed the issue since installing a reolink doorbell camera which had gaps in recording until I reduced its framerate/bitrate and seems to be working fine now. There are no errors in Go2rtc.
Version
0.12.0-da3e197
Frigate config file
Relevant log output
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
Reolink Doorbell
Any other information that may be helpful
No response