Wartung am 15.11. – Forum ab 22:00 Uhr nicht erreichbar

[exitus]

@wal habe es geschafft jetz anderes problem habe 2 cameras beide machen screenshots dedection klappt bei einen habe ich clips bei den anderen nur bilder ohne clips wo kein clips sind ist die kamera mit der bezeichnung back
ier mein config

database: 
  path: /media/frigate/db/frigate.db
detectors:
  cpu1:
    type: cpu
ui:
  use_experimental: false
  live_mode: mse
mqtt:
  host: 172.16.0.10
  port: 12345
  user: xxxxxxx
  password: exxxxx

cameras:
  back1:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxxxx@172.16.0.177:554/channel=2
          roles:
            - detect
            - rtmp
        - path: rtsp://admin:xxxxxxx@172.16.0.177:554/channel=1
          roles:
            - record
  back:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxxxxxxx@172.16.0.147:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2
          roles:
            - detect
            - rtmp
        - path: rtsp://admin:xxxxxxxx@172.16.0.147:554
          roles:
            - record

detect:
      width: 640
      height: 480
      fps: 5
objects:
      track:
        - person
        - dog
        - bicycle
        - cat
      filters:
        person:
          min_score: 0.7
          threshold: 0.5
          min_area: 700
snapshots:
      enabled: true
      timestamp: true
      bounding_box: true
      crop: True
      height: 500
      retain:
        default: 1

record:
  enabled: True
  events:
    retain:
      default: 10

birdseye:
  enabled: True
  mode: continuous

[Wal]

@exitus ,
schau mal im Adapter ob das dort eingeschaltet ist.

[exitus]

@wal bei mir steht OFF wo kann man es den einschalten im config ist ja true,
warum ist der eine on und der andere off

[Wal]

@exitus ,
state ist nur der Status und mit Set kann man an und ausschalten.

[exitus]

mein coral cpu ist das was habe ich gemacht habe unter proxmox wie auf der seite von coral installiert
ausgabe lsusb

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1a6e:089a Global Unichip Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 002: ID 0451:16c8 Texas Instruments, Inc. CC2538 USB CDC
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ls -l /dev/bus/usb/002/002
crw-rw-r-- 1 root plugdev 189, 129 May 24 16:13 /dev/bus/usb/002/002

lxc 117.conf

arch: amd64
cores: 6
hostname: frigate
memory: 8096
net0: name=eth0,bridge=vmbr0,firewall=1,gw=172.16.0.1,hwaddr=22:88:33:2D:28:77,ip=172.1>
ostype: debian
rootfs: local-lvm:vm-117-disk-1,size=30G
swap: 512
lxc.cgroup.devices.allow: c 226:0 rwm
lxc.cgroup.devices.allow: c 226:128 rwm
lxc.cgroup.devices.allow: c 29:0 rwm
lxc.cgroup.devices.allow: c 189:* rwm
lxc.apparmor.profile: unconfined
lxc.cgroup.devices.allow: a
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file >
lxc.mount.entry: /dev/bus/usb/002/ dev/bus/usb/002/ none bind,optional,create=dir 0, 0
lxc.cap.drop:
lxc.mount.auto: cgroup:rw

frigate conf

database: 
  path: /media/frigate/db/frigate.db
detectors:
  coral:
    type: edgetpu
    device: usb
ui:
  use_experimental: false
  live_mode: mse
mqtt:
  host: 172.16.0.10
  port: 1689
  user: so
  password: xxxxx
record:
  enabled: True
  retain:
    days: 7
    mode: all
  events:
    retain:
      default: 30
snapshots:
  enabled: True
  timestamp: False
  bounding_box: true
  retain:
    default: 90

detect:
  stationary:
    max_frames:
      objects:
        person: 1200
cameras:
  back1:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxxxxx@172.16.0.177:554/channel=2
          roles:
            - detect
            - rtmp
        - path: rtsp://admin:xxxxx@172.16.0.177:554/channel=1
          roles:
            - record
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -c:a aac
    
    detect:
      width: 1280
      height: 720
    objects:
      track:
        - person
        - car
    record:
      events:
        required_zones:
          - street
          - all
    zones:
      street:
        coordinates: 352,544,416,519,476,513,502,334,472,199,391,107,325,127,261,136,62,162,45,347,59,430,207,535
        objects:
          - car
      all:
        coordinates: 352,544,416,519,476,513,502,334,472,199,391,107,325,127,261,136,62,162,45,347,59,430,207,535
        objects:
          - person
    motion:
      mask:
        - 254,79,503,44,848,24,1113,43,1111,0,439,0,291,0,226,0,0,0,0,159        
          
  back:
    ffmpeg:
      inputs:
        - path: rtsp://admin:xxxxxx@172.16.0.147:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2
          roles:
            - detect
            - rtmp
        - path: rtsp://admin:xxxxxx@172.16.0.147:554
          roles:
            - record
    detect:
      width: 1280
      height: 720
    objects:
      track:
        - person
        - car
    record:
      events:
        required_zones:
          - street
          - all
    zones:
      street:
        coordinates: 470,676,592,583,1051,569,1257,341,1147,254,1063,247,779,299,536,378,476,471,389,399,332,473,241,427,293,647
        objects:
          - person
      #all:
        #coordinates: 472,57,526,64,1031,129,1060,95,941,30,504,26,376,0,175,0,0,0,33,169,191,143,360,110
        #objects:
         # - person

ohne edge tpu ging es , habe detector auf edgetpu geänder seit dem habe ich kein bild kommt so für 1 sekunde und wider alles schwarz wie auf dem bild

mein log vom docker

2023-05-24 16:34:48.086320180  
2023-05-24 16:34:53.211082426  [2023-05-24 16:34:53] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service go2rtc-healthcheck: stopping
2023-05-24 16:34:53.227039323  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2023-05-24 16:34:53.305962172  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
2023-05-24 16:34:53.309352767  [2023-05-24 16:34:53] frigate.app                    INFO    : Stopping...
s6-rc: info: service nginx-log successfully stopped
2023-05-24 16:34:53.311354844  [2023-05-24 16:34:53] frigate.watchdog               INFO    : Exiting watchdog...
2023-05-24 16:34:53.312088389  [2023-05-24 16:34:53] frigate.storage                INFO    : Exiting storage maintainer...
2023-05-24 16:34:53.312100611  [2023-05-24 16:34:53] frigate.stats                  INFO    : Exiting stats emitter...
2023-05-24 16:34:53.312107805  [2023-05-24 16:34:53] frigate.record                 INFO    : Exiting recording maintenance...
2023-05-24 16:34:53.320612754  [2023-05-24 16:34:53] frigate.record                 INFO    : Exiting recording cleanup...
2023-05-24 16:34:53.321374794  [2023-05-24 16:34:53] frigate.events                 INFO    : Exiting event cleanup...
2023-05-24 16:34:53.321393162  [2023-05-24 16:34:53] frigate.object_processing      INFO    : Exiting object processor...
2023-05-24 16:34:53.571418465  [2023-05-24 16:34:53] frigate.comms.ws               INFO    : Exiting websocket client...
2023-05-24 16:34:54.249977376  [2023-05-24 16:34:54] frigate.events                 INFO    : Exiting event processor...
2023-05-24 16:34:54.250550076  [2023-05-24 16:34:54] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
2023-05-24 16:34:54.259106288  [2023-05-24 16:34:54] watchdog.back                  INFO    : Terminating the existing ffmpeg process...
2023-05-24 16:34:54.259777814  [2023-05-24 16:34:54] watchdog.back                  INFO    : Waiting for ffmpeg to exit gracefully...
2023-05-24 16:34:54.266624376  [2023-05-24 16:34:54] watchdog.back1                 INFO    : Terminating the existing ffmpeg process...
2023-05-24 16:34:54.266775374  [2023-05-24 16:34:54] watchdog.back1                 INFO    : Waiting for ffmpeg to exit gracefully...
2023-05-24 16:34:54.383145698  [2023-05-24 16:34:54] watchdog.back1                 INFO    : Terminating the existing ffmpeg process...
2023-05-24 16:34:54.383311572  [2023-05-24 16:34:54] watchdog.back1                 INFO    : Waiting for ffmpeg to exit gracefully...
2023-05-24 16:34:54.415749456  [2023-05-24 16:34:54] watchdog.back                  INFO    : Terminating the existing ffmpeg process...
2023-05-24 16:34:54.415853799  [2023-05-24 16:34:54] watchdog.back                  INFO    : Waiting for ffmpeg to exit gracefully...
2023-05-24 16:34:54.637141769  [2023-05-24 16:34:54] frigate.output                 INFO    : exiting output process...
2023-05-24 16:34:58.559268884  /usr/lib/python3.9/multiprocessing/resource_tracker.py:216: UserWarning: resource_tracker: There appear to be 13 leaked shared_memory objects to clean up at shutdown
2023-05-24 16:34:58.559280338    warnings.warn('resource_tracker: There appear to be %d '
2023-05-24 16:34:58.560386418  [INFO] Service Frigate exited with code 0 (by signal 0)
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2023-05-24 16:34:58.563280091  exit OK
s6-rc: info: service frigate-log successfully stopped
2023-05-24 16:34:58.570563372  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2023-05-24 16:35:03.269511637  [INFO] Preparing go2rtc config...
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
2023-05-24 16:35:03.274350536  [INFO] Starting Frigate...
2023-05-24 16:35:03.274655883  [INFO] Starting NGINX...
s6-rc: info: service legacy-services successfully started
2023-05-24 16:35:03.544117376  [INFO] Starting go2rtc...
2023-05-24 16:35:03.635953359  16:35:03.635 INF go2rtc version 1.2.0 linux/amd64
2023-05-24 16:35:03.636486320  16:35:03.636 INF [api] listen addr=:1984
2023-05-24 16:35:03.636814435  16:35:03.636 INF [rtsp] listen addr=:8554
2023-05-24 16:35:03.637127674  16:35:03.637 INF [srtp] listen addr=:8443
2023-05-24 16:35:03.637534711  16:35:03.637 INF [webrtc] listen addr=:8555
2023-05-24 16:35:04.485742533  [2023-05-24 16:35:04] frigate.app                    INFO    : Starting Frigate (0.12.0-da3e197)
2023-05-24 16:35:04.527219793  [2023-05-24 16:35:04] peewee_migrate                 INFO    : Starting migrations
2023-05-24 16:35:04.531970132  [2023-05-24 16:35:04] peewee_migrate                 INFO    : There is nothing to migrate
2023-05-24 16:35:04.549606158  [2023-05-24 16:35:04] detector.coral                 INFO    : Starting detection process: 429
2023-05-24 16:35:04.554122319  [2023-05-24 16:35:04] frigate.app                    INFO    : Output process started: 431
2023-05-24 16:35:04.561305867  [2023-05-24 16:35:04] frigate.app                    INFO    : Camera processor started for back1: 437
2023-05-24 16:35:04.570196340  [2023-05-24 16:35:04] frigate.app                    INFO    : Camera processor started for back: 439
2023-05-24 16:35:04.576351891  [2023-05-24 16:35:04] frigate.app                    INFO    : Capture process started for back1: 440
2023-05-24 16:35:04.582484533  [2023-05-24 16:35:04] frigate.app                    INFO    : Capture process started for back: 444
2023-05-24 16:35:13.274499111  [INFO] Starting go2rtc healthcheck service...

[Wal]

@exitus ,
in der docker.yml hast du die coral usb auch durchgereicht ?
Die Treiber im Proxmox-Host sind auch installiert ?

[exitus]

@wal proxmox host sind die treiber installiert die ausgabe von lsusb ist vom host
mit der rechte meinst du doch
/dev/bus/usb:/dev/bus/usb
habe frigate so getstartet

docker run --name frigate --privileged --shm-size=1g --mount type=tmpfs,target=/tmp/cache,tmpfs-size=2000000000 -v /shared/frigate/config:/config:rw -v /dev/bus/usb:/dev/bus/usb -v /etc/localtime:/etc/localtime:ro -v /shared/frigate:/media/frigate/clips:rw -v /shared/frigate/recordings:/media/frigate/recordings:rw -v /home/frigate:/media/frigate/db:rw --device-cgroup-rule="c 189:* rmw" --device=/dev/dri/renderD128 -d -p 5000:5000 -e FRIGATE_RTSP_PASSWORD='elajelaj-61' ghcr.io/blakeblackshear/frigate:stable

[Wal]

@exitus sagte in Proxmox LXC mit Frigate:

proxmox host sind die treiber installiert die ausgabe von lsusb ist vom host

das ist mir schon klar, heisst aber nicht das du das gemacht hast:

echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

sudo apt-get update

sudo apt-get install libedgetpu1-std gasket-dkms

und der aktuelle pve-kernel-header muss vorher auch installiert sein, wobei der gasket-dkms evtl. auch nur für die PCI Version installiert werden muss, weiß ich aber nicht da ich keine USB-Verdion habe.

[exitus]

@wal

echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list

curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

sudo apt-get update
Install the Edge TPU runtime:

sudo apt-get install libedgetpu1-std

das habe ich gemacht unter proxmox host und im container

[Wal]

@exitus ,
ok da würde ich mal auf github beim frigate Projekt nachfragen, da man aus dem Log nicht viel herausziehen kann.

[holzapfelauge]

@radi Hast du das ganze zum laufen bekommen? ich hab das selbe Problem wie du. Hab den Ladebildschirm und sonst tut sich nix.

[Hansi1234]

@holzapfelauge
@Radi

Habt ihr zu eurem Endlosloop schon eine Lösung gefunden? Habe es vorhin für Testzwecke auch installiert und stehe nun vor dem gleichen Problem.

@Wal kannst du hier vielleicht helfen?

[Wal]

@hansi1234 ,
wenn du möchtest können wir die Installation heute Abend Schritt für Schritt gemeinsam durchführen.

[Hansi1234]

@wal gerne. Hast du die Installation zufällig in letzter Zeit auch versucht?
Könnte es bei mir am nicht aktuellen proxmox Host liegen?

[Wal]

@hansi1234 sagte in Proxmox LXC mit Frigate:

Könnte es bei mir am nicht aktuellen proxmox Host liegen?

Denke ich nicht.
Wäre so um 19Uhr bereit.

[Hansi1234]

@wal super, ich schreibe dich dann im Chat an

[Wal]

@hansi1234 ,
wir könnten es auch hier machen, da hätten die anderen auch was davon.
Wenn du unter Windows auf Proxmox zugreifst, installier bitte den Bitvise SSH-Client.
Da geht Copy-Paste hervorragend, nehm ich lieber als Putty und die Proxmox-Konsole geht gar nicht.

[Hansi1234]

@wal alles klar. Bis später

[Wal]

@hansi1234 ,
habe ich eben getestet, mit der alten Anleitung geht es nicht
Neue Anleitung auf Seite 1 !!!

[Hansi1234]

@wal said in Proxmox LXC mit Frigate:

exit

Funktioniert, danke dir