[Support]: Frigate out of space

[gcormier]

Describe the problem you are having

Do I have something configured wrong?

s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device

Running in docker. Should frigate be logging elsewhere then shared memory?

Version

14.1

Relevant Frigate log output

s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on device

Install method

Docker Compose

docker-compose file or Docker CLI command

frigate:
    container_name: frigate
    #privileged: true  # privileged allows GPU stats to run via intel_gpu_top
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:0.14.1
    cap_add:
      - CAP_PERFMON
    shm_size: "512mb" # update for your cameras based on calculation above
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              capabilities: [gpu]
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Toronto
      - PLUS_API_KEY=exxxxxxx
      - NVIDIA_VISIBLE_DEVICES=all
      - NVIDIA_DRIVER_CAPABILITIES=compute,video,utility
    devices:
      - /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
      #- /dev/dri/card0
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /docker/frigate:/config
      - /drives/6t/frigate:/media/frigate
    ports:
      - "5000:5000"
      - "1935:1935" # RTMP feeds

Object Detector

Coral

Network connection

Wired

Camera make and model

Reolink

[hawkeye217]

No, Frigate logs to /dev/shm by default. Your shm size is configured at 512mb via your docker-compose, but you can increase this if needed.

[gcormier]

Given /dev/shm is in RAM, no matter what I set my shm size to, as soon as you need more then that, Frigate will stop responding.

Wouldn't it be better to have logs cycle often enough for this not to happen?

[NickM-27]

The logs automatically rotate when they hit 10MB on size, the log here is a red herring. The actual issue is just /dev/shm which has been fixed for the next version

[gcormier]

Thanks - this sounds more appropriate, as even 512mb for /dev/shm is very generous I believe.