[Config Support]: Too many unprocessed recording segments in cache

[yousaf465]

Describe the problem you are having

Too many unprocessed recording segments in cache for Main_gate. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...

Version

0.16.0-f141b58 upgrading to current while posting this

Frigate config file

mqtt:
  enabled: false

detectors:
  onnx_0:
    type: onnx



model:
  path: plus://xxxxxxxxxxxxxxxxxxxx

record:
  enabled: true
  retain:
    days: 7
    mode: motion
  alerts:
    retain:
      days: 60
  detections:
    retain:
      days: 60

snapshots:
  # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
  enabled: true
  # Optional: save a clean PNG copy of the snapshot image (default: shown below)
  clean_copy: true
  # Optional: print a timestamp on the snapshots (default: shown below)
  timestamp: false
  # Optional: draw bounding box on the snapshots (default: shown below)
  bounding_box: true
  # Optional: crop the snapshot (default: shown below)
  crop: false
  # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones)
  required_zones: []
  # Optional: Camera override for retention settings (default: global values)
  retain:
    # Required: Default retention days (default: shown below)
    default: 60
    # Optional: Per object retention days
    objects:
      person: 60
  # Optional: quality of the encoded jpeg, 0-100 (default: shown below)
  quality: 70

Relevant Frigate log output

Too many unprocessed recording segments in cache for Main_gate_D6. This likely indicates an issue with the detect stream, keeping the 6 most recent segments out of 7 and discarding the rest...

Relevant go2rtc log output

info | 2025-07-01 14:36:01 | startup | Preparing new go2rtc config...
info | 2025-07-01 14:36:02 | startup | Starting go2rtc...
info | 2025-07-01 14:36:02 | startup | go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
info | 2025-07-01 14:36:02 | startup | config path=/dev/shm/go2rtc.yaml
info | 2025-07-01 14:36:02 | api     | listen addr=:1984
info | 2025-07-01 14:36:02 | rtsp    | listen addr=:8554
info | 2025-07-01 14:36:02 | webrtc  | listen addr=:8555
info | 2025-07-01 14:36:10 | startup | Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

Debian

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate16
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    image: ghcr.io/blakeblackshear/frigate:ea576e7-tensorrt
    cap_add:
      - CAP_PERFMON
    shm_size: 4096mb
    runtime: nvidia
    devices:
      - /dev/bus/usb:/dev/bus/usb
      - /dev/dri/renderD128:/dev/dri/renderD128
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ./config:/config
      - /mnt/hdd4tb/CCTV/storage:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 40000000000000
    ports:
      - 1984:1984
      - 5005:5000
      - 8971:8971
    environment:
      PLUS_API_KEY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
networks: {}

Object Detector

TensorRT

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

No response

[NickM-27]

We will need to see a full copy of logs. Also would be good to see camera stats

[yousaf465]

How to upload and download full logs?

[hawkeye217]

How to upload and download full logs?

You can use the Download button in the Logs pane of the Frigate UI and just upload the file here.

[yousaf465]

frigate-logs(1).txt

[hawkeye217]

There are two unusual errors in your log:

2025-07-01 15:00:55.619637491  Exception in thread recording_cleanup:
2025-07-01 15:00:55.619641676  Traceback (most recent call last):
2025-07-01 15:00:55.619643739    File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
2025-07-01 15:00:55.619773955      self.run()
2025-07-01 15:00:55.619837219    File "/opt/frigate/frigate/record/cleanup.py", line 345, in run
2025-07-01 15:00:55.619986676      self.expire_recordings()
2025-07-01 15:00:55.620050796    File "/opt/frigate/frigate/record/cleanup.py", line 315, in expire_recordings
2025-07-01 15:00:55.620202039      self.expire_existing_camera_recordings(expire_date, config, reviews)
2025-07-01 15:00:55.620271195    File "/opt/frigate/frigate/record/cleanup.py", line 176, in expire_existing_camera_recordings
2025-07-01 15:00:55.620400634      Path(recording.path).unlink(missing_ok=True)
2025-07-01 15:00:55.620472153    File "/usr/lib/python3.11/pathlib.py", line 1148, in unlink
2025-07-01 15:00:55.622586659      os.unlink(self)
2025-07-01 15:00:55.622719173  IsADirectoryError: [Errno 21] Is a directory: '/media/frigate/recordings/2025-06-21/03/Roof_Top_Solar_D7/52.13.mp4'

2025-07-01 15:06:42.240244716  Exception in thread detected_frames_processor:
2025-07-01 15:06:42.240317632  Traceback (most recent call last):
2025-07-01 15:06:42.240320164    File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
2025-07-01 15:06:42.240504897      self.run()
2025-07-01 15:06:42.240552438    File "/opt/frigate/frigate/track/object_processing.py", line 723, in run
2025-07-01 15:06:42.240713036      camera_state.update(
2025-07-01 15:06:42.240739755    File "/opt/frigate/frigate/camera/state.py", line 353, in update
2025-07-01 15:06:42.240813831      c(self.name, removed_obj, frame_name)
2025-07-01 15:06:42.240852549    File "/opt/frigate/frigate/track/object_processing.py", line 134, in end
2025-07-01 15:06:42.240908245      obj.write_thumbnail_to_disk()
2025-07-01 15:06:42.240928071    File "/opt/frigate/frigate/track/tracked_object.py", line 590, in write_thumbnail_to_disk
2025-07-01 15:06:42.241051362      with open(os.path.join(directory, f"{self.obj_data['id']}.webp"), "wb") as f:
2025-07-01 15:06:42.241157663           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-07-01 15:06:42.241177553  OSError: [Errno 34] Numerical result out of range: '/media/frigate/clips/thumbs/Main_porch_D2/1751364194.603039-v6ei6z.webp'

Both of these errors indicate that there's a potential issue with the filesystem where Frigate is trying to save the files, rather than a problem with Frigate's code itself.

The most common cause is that the filesystem (e.g., /media/frigate/clips/thumbs/Main_porch_D2/) has reached a limit on the number of files it can hold in a single directory, or the total number of inodes available on the disk. Even if there's free space, you can run out of inodes.

You should check your available disk space (df -h /media/frigate) and your available inodes (df -i /media/frigate).

What kind of filesystem are you using for your Frigate media?

[yousaf465]

sda2
     ntfs         HDD 4TB
                        xxxxxxxxxxxxxxxxxxx                      983.8G    74% /mnt/hdd4tb

I have mounted a 4TB HDD for frigate data storage. while frigate itself is installed on 256G SSD.

[hawkeye217]

As the "i" icon tooltip there indicates, the usage percentage represents the total storage used by the recordings in Frigate's database. Frigate does not track storage usage for all files on your disk.

You'll want to check your available inodes and perhaps run a filesystem check to ensure there's no data corruption.

[yousaf465]

formatted it as ext4 and started frigate again. these errors seems have gone

df -i /mnt/hdd4tb
Filesystem        Inodes IUsed     IFree IUse% Mounted on
/dev/sda2      244195328  2953 244192375    1% /mnt/hdd4tb

[hawkeye217]

Great. I think ext4fs is preferable over ntfs in this case.

Will close this for now, feel free to reopen if you have the issue again.