收起左侧

J4125飞牛最新版安装frigate报错

1
回复
46
查看
[ 复制链接 ]

1

主题

0

回帖

0

牛值

江湖小虾

悬赏1飞牛币未解决

如题,

1.N100主机直接安装商店里的frigate没问题。

2.J4125安装就报错,报错信息如下

s6-rc: info: service s6rc-fdholder: startings6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-oneshot-runner successfully starteds6-rc: info: service fix-attrs: startings6-rc: info: service s6rc-fdholder successfully starteds6-rc: info: service fix-attrs successfully starteds6-rc: info: service legacy-cont-init: startings6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service prepare: startings6-rc: info: service log-prepare: startings6-rc: info: service log-prepare successfully starteds6-rc: info: service nginx-log: startings6-rc: info: service go2rtc-log: startings6-rc: info: service frigate-log: startings6-rc: info: service certsync-log: startings6-rc: info: service frigate-log successfully starteds6-rc: info: service go2rtc-log successfully starteds6-rc: info: service nginx-log successfully starteds6-rc: info: service certsync-log successfully starteds6-rc: info: service prepare successfully starteds6-rc: info: service go2rtc: startings6-rc: info: service go2rtc successfully starteds6-rc: info: service go2rtc-healthcheck: startings6-rc: info: service frigate: startings6-rc: info: service go2rtc-healthcheck successfully starteds6-rc: info: service frigate successfully starteds6-rc: info: service nginx: starting2025-12-24 13:54:26.153345825  [INFO] Starting NGINX...2025-12-24 13:54:26.193063431  [INFO] No TLS certificate found. Generating a self signed certificate...2025-12-24 13:54:26.658328492  [INFO] Preparing Frigate...2025-12-24 13:54:26.812881000  [INFO] Preparing new go2rtc config...2025-12-24 13:54:27.333792414  [INFO] Starting Frigate...2025-12-24 13:54:27.474725481  [INFO] Starting go2rtc...2025-12-24 13:54:27.610218153  13:54:27.610 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.92025-12-24 13:54:27.610231209  13:54:27.610 INF config path=/dev/shm/go2rtc.yaml2025-12-24 13:54:27.611385658  13:54:27.611 INF [api] listen addr=:19842025-12-24 13:54:27.611735314  13:54:27.611 INF [rtsp] listen addr=:85542025-12-24 13:54:27.612269968  13:54:27.612 INF [webrtc] listen addr=:8555s6-rc: info: service nginx successfully starteds6-rc: info: service certsync: startings6-rc: info: service certsync successfully starteds6-rc: info: service legacy-services: starting2025-12-24 13:54:29.804197105  [INFO] Starting certsync...s6-rc: info: service legacy-services successfully started2025-12-24 13:54:30.539179887  127.0.0.1 - - [24/Dec/2025:13:54:30 +0800] "" 400 0 "-" "-" "-"2025-12-24 13:54:30.999069805  2025/12/24 13:54:30 [error] 204#204: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"2025-12-24 13:54:30.999104867  2025/12/24 13:54:30 [error] 204#204: *2 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"2025-12-24 13:54:31.988177620  [2025-12-24 13:54:31] frigate.util.config            INFO    : Checking if frigate config needs migration...2025-12-24 13:54:32.012430533  [2025-12-24 13:54:32] frigate.util.config            INFO    : frigate config does not need migration...2025-12-24 13:54:32.050618767  [2025-12-24 13:54:32] frigate.app                    INFO    : Starting Frigate (0.16.3-9034454)2025-12-24 13:54:32.068462717  [2025-12-24 13:54:32] peewee_migrate.logs            INFO    : Starting migrations2025-12-24 13:54:32.068983579  [2025-12-24 13:54:32] peewee_migrate.logs            INFO    : There is nothing to migrate2025-12-24 13:54:32.091747133  [2025-12-24 13:54:32] frigate.app                    INFO    : Recording process started: 3892025-12-24 13:54:32.093140289  [2025-12-24 13:54:32] frigate.app                    INFO    : Review process started: 3962025-12-24 13:54:32.101449348  [2025-12-24 13:54:32] frigate.app                    INFO    : go2rtc process pid: 1282025-12-24 13:54:32.123781367  [2025-12-24 13:54:32] detector.ov                    INFO    : Starting detection process: 4142025-12-24 13:54:32.139437223  [2025-12-24 13:54:32] frigate.app                    INFO    : Output process started: 4302025-12-24 13:54:32.172406802  [2025-12-24 13:54:32] frigate.app                    INFO    : Camera processor started for back: 4602025-12-24 13:54:32.186924612  [2025-12-24 13:54:32] frigate.app                    INFO    : Capture process started for back: 4672025-12-24 13:54:32.874566137  [2025-12-24 13:54:32] frigate.api.fastapi_app        INFO    : Starting FastAPI app2025-12-24 13:54:33.270349105  [2025-12-24 13:54:33] frigate.api.fastapi_app        INFO    : FastAPI started2025-12-24 13:54:36.148805489  [INFO] Starting go2rtc healthcheck service...2025-12-24 13:54:42.235603060  [2025-12-24 13:54:42] frigate.video                  ERROR   : back: Unable to read frames from ffmpeg process.2025-12-24 13:54:42.236164242  [2025-12-24 13:54:42] frigate.video                  ERROR   : back: ffmpeg process is not running. exiting capture thread...2025-12-24 13:54:43.015596494  Process detector:ov:2025-12-24 13:54:43.015601810  Traceback (most recent call last):2025-12-24 13:54:43.015604422    File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap2025-12-24 13:54:43.015609873      self.run()2025-12-24 13:54:43.015613085    File "/opt/frigate/frigate/util/process.py", line 41, in run_wrapper

3.百度了下说是要强制驱动i965。

/vol1/@appcenter/frigate/docker/docker-compose.yaml改了并保存

version: "3.8"

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    stop_grace_period: 30s
    image: docker.cnb.cool/frigate-cn/frigate:${wizard_version}
    shm_size: ${wizard_shm_size}
    devices:
      - /dev/dri/:/dev/dri/${wizard_coral}
      - /dev/dri/renderD128:/dev/dri/renderD128  #核显映射
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${TRIM_PKGETC}:/config
      - ${TRIM_PKGHOME}/video:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "${TRIM_SERVICE_PORT}:8971"
      - "8554:8554"
      - "8555:8555/tcp"
      - "8555:8555/udp"
    environment:
      FRIGATE_RTSP_PASSWORD: "password"
      TZ: "Asia/Shanghai"
      HF_ENDPOINT: $wizard_endpoint
      GITHUB_ENDPOINT: $wizard_github_endpoint
      - LIBVA_DRIVER_NAME=i965 #强制i965驱动

重新构建(本地镜像没删,还是商店里下载的那个)构建失败

在compose里粘贴docker-compose.yml,显示构建失败

time="2025-12-25T13:21:21+08:00" level=warning msg="The \"TRIM_SERVICE_PORT\" variable is not set. Defaulting to a blank string."
time="2025-12-25T13:21:21+08:00" level=warning msg="/vol1/1000/Docker/Frigate/docker-compose.yml: the attribute ​version​ is obsolete, it will be ignored, please remove it to avoid potential confusion"
Image blakeblackshear/frigate:stable Pulling
Image blakeblackshear/frigate:stable Error unknown: failed to resolve reference "docker.io/blakeblackshear/frigate:stable": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://docker.fnnas.com/service/token?scope=repository%3Ablakeblackshear%2Ffrigate%3Apull&scope=repository%3Afnnas%2Fblakeblackshear%2Ffrigate%3Apull&service=harbor-registry: 401 Unauthorized
Error response from daemon: unknown: failed to resolve reference "docker.io/blakeblackshear/frigate:stable": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://docker.fnnas.com/service/token?scope=repository%3Ablakeblackshear%2Ffrigate%3Apull&scope=repository%3Afnnas%2Fblakeblackshear%2Ffrigate%3Apull&service=harbor-registry: 401 Unauthorized
Exited:0

求助各位大佬,如何解决。

收藏
送赞
分享

2

主题

1982

回帖

350

牛值

共建版主

fnOS1.0上线纪念勋章社区共建团荣誉勋章

换个镜像源docker.fnnas.com好像有问题
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则