Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Config Support]: Installed in Docker Container in Proxmox LXC but no frames are being received #9019

Closed
tomhusband opened this issue Dec 19, 2023 · 9 comments

Comments

@tomhusband
Copy link

Describe the problem you are having

Frigate loads but I can't get a picture. Previously I had Frigate as an add-on in Home Assistant in a Proxmox VM. Now on a new NUC I have HA in a VM and Frigate in Docker in a Proxmox LXC. I plan on linking the two at a later date. When I go to the Frigate IP address everything loads but no camera. I used this tutorial as a guide. I used the config file from my old installation as the camera didn't change (maybe that's where I went wrong).

The logs seem very brief. I have a USB Coral Accelerator and when I restarted the initial log had a lot more information but disappeared.

Version

I don't see the version in Debug but it should the latest

Frigate config file

mqtt:
  enabled: false
ffmpeg:
  hwaccel_args: preset-vaapi
detectors:
  coral:
    type: edgetpu
    device: usb
#Global Object Settings
objects:
  track:
    - person
  filters:
    person:
      min_area: 5000
      max_area: 100000
cameras:
  driveway_cam:
    ffmpeg:
      inputs:
        - path: rtsp://admin:username@192.168.1.15:554/cam/realmonitor?channel=1&subtype=0&authbasic=64
          roles:
            - detect
            - record
            - rtmp
    detect:
      width: 1280
      height: 720
      fps: 10
      
    objects:
      track:
        - car
            mask
              - 1164,611,610,720,493,211,838,71
        - person
        - dog
        - cat
        - bicycle
      filters:
        person:
          min_score: 0.6
          threshold: 0.7
        dog:
          min_score: 0.6
          threshold: 0.75
    record:
      enabled: True
      retain:
        days: 0
        mode: active_objects
      events:
        retain:
          default: 3
          mode: active_objects
      
    motion:
      improve_contrast: True

Relevant log output

2023-12-19 15:19:42.588698274  [INFO] Starting Frigate...
2023-12-19 15:19:43.121530468  [2023-12-19 15:19:43] frigate.app                    INFO    : Starting Frigate (0.12.1-367d724)
2023-12-19 15:19:43.130164166  [2023-12-19 15:19:43] peewee_migrate                 INFO    : Starting migrations
2023-12-19 15:19:43.132207181  [2023-12-19 15:19:43] peewee_migrate                 INFO    : There is nothing to migrate
2023-12-19 15:19:43.138841189  [2023-12-19 15:19:43] detector.coral                 INFO    : Starting detection process: 553

Frigate stats

No response

Operating system

Proxmox

Install method

Docker Compose

Coral version

USB

Any other information that may be helpful

No response

@NickM-27
Copy link
Collaborator

yeah, we're going to need more logs to know what is going wrong. Should be able to get logs from docker if they are not in the UI

@tomhusband
Copy link
Author

OK, how about this?
_frigate_logs.txt

Thanks again.

@NickM-27
Copy link
Collaborator

okay, we can see that the coral is not detected, which would be a proxmox configuration issue or potentially a power issue from the USB ports on the new device (though this is relatively unlikely)

@tomhusband
Copy link
Author

tomhusband commented Dec 19, 2023

Hmmm, Part of the setup tutorial was to add the following two lines to /etc/pve/lxc at the bottom:

`lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file 0, 0

lxc.mount.entry: /dev/bus/usb/002/ dev/bus/usb/002/ none bind,optional,create=dir 0,0`

The Coral is plugged into the USB 3.0 port. Are those lines incorrect possibly?

@NickM-27
Copy link
Collaborator

It's possible it's a different bus than 002

@tomhusband
Copy link
Author

tomhusband commented Dec 19, 2023

Right, Here's lsusb but I can't make out the Coral.

root@pve:~# lsusb
Bus 004 Device 002: ID 1a6e:089a Global Unichip Corp. 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@pve:~# 

@NickM-27
Copy link
Collaborator

Bus 004 Device 002: ID 1a6e:089a Global Unichip Corp. is the coral so you'd likely want to update the mount above to 004 instead of 002

@tomhusband
Copy link
Author

Hey, now we're getting somewhere. I have video! Now I guess i need to give it a little time and see if I get some events.

Thanks a lot for the help!

Copy link

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.

@github-actions github-actions bot added the stale label Jan 19, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants