starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Frigate freezes proxmox host #274

New Issue
Closed
opened 2026-02-04 17:38:36 +03:00 by OVERLORD · 10 comments
OVERLORD commented 2026-02-04 17:38:36 +03:00
Owner
Copy Link

Originally created by @raverlution on GitHub (Jan 5, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Frigate

📂 What was the exact command used to execute the script?

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/frigate.sh)"

📝 Provide a clear and concise description of the issue.

Hi
A couple a weeks ago i added the Frigate NVR with hardware transcoding on my Lenovo Tiny with a i5-14500t with Intel UHD 770.

The problem is that every 12 - 36 hours it crashes my proxmox host. If i Connect a display to the server its just a Black screen with a little blinking White curser in the top left side. It is totally unresponsive. I can´t ssh to the server.
The logs shows nothing.
I have to pull the plug and Connect again to get it up and running.

Sometimes I Can trick it to crash, when Plex transcodes and I get lots of motion in front of my camera. But not always

I have been running Plex on this server for a couple of months without any problem (also created with the community script)

Seems like Frigate somehow crashes the igpu? or that openvino crashes my proxmox host, if my "new" settings without hwaccel and only cpu detector is working?

Proxmox 8.3.2 kernel 6.8.12-5-pve also tried kernel 6.11, but then the crash is within 1 hour.

*The things i have tried:
Disable hwaccel using:
ffmpeg:
hwaccel_args: ''

But its the same, it crashes within 36 hours.

Now for a test until my coral arrives i am running with:
ffmpeg:
hwaccel_args: ''

and cpu detector (without openvino) it it has been running for 12 hours so far without issues, but will see if it lasts

I have found a similar thread here? https://github.com/blakeblackshear/frigate/issues/8470

Any ideas?

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 11

🔄 Steps to reproduce the issue.

Sometimes not always:
Plex transcoding one or more streams.
Motion in front of the camera

❌ Paste the full error output (if available).

Nothing gets written to the log

🖼️ Additional context (optional).

Aktiver mqtt server

mqtt:
host: 192.168.1.xxx
user: user
password: passwd

detectors:
ov:
type: openvino
device: CPU

model:
width: 300
height: 300
input_tensor: nhwc
input_pixel_format: bgr
path: /openvino-model/FP16/ssdlite_mobilenet_v2.xml
labelmap_path: /openvino-model/coco_91cl_bkgr.txt

ffmpeg configuration

More information about presets at https://docs.frigate.video/configuration/ffmpeg_presets

ffmpeg:
hwaccel_args: ''
input_args: preset-rtsp-restream
output_args:
record: preset-record-generic-audio-copy

Restream configuration

Uses https://github.com/AlexxIT/go2rtc (v1.9.2)

go2rtc:
streams:
Indkoersel:
- rtsp://xxx:xxx@192.168.1.xxx:554/h264Preview_01_main
Indkoersel_sub:
- rtsp://xxx:xxx@192.168.1.xxx:554/h264Preview_01_sub

------------------------Kamera 1 konfiguration STARTER her------------------------------

cameras:
Indkoersel:
ffmpeg:
inputs:
- path: rtsp://192.168.1.xxx:8554/Indkoersel
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://192.168.1.xxx:8554/Indkoersel_sub
input_args: preset-rtsp-restream
roles:
- detect
motion:
mask:
0.001,0.229,0.119,0.17,0.133,0.301,0.178,0.227,0.266,0.164,0.308,0.114,0.501,0.147,0.544,0.153,0.829,0.207,0.832,0.368,0.82,0.996,0.998,0.992,0.998,0.006,0.002,0.002
objects:
track:
- person
- car
- car
- bicycle
- motorcycle
- boat
- cat
- dog
- hat
- backpack
- umbrella
- baseball bat
mask:
0,0,1,0,1,1,0.918,1,0.846,0.223,0.34,0.148,0.267,0.111,0.223,0.133,0.231,0.273,0.143,0.321,0.124,0.171,0,0.233
zones:
Primaer:
coordinates: 0.923,0.364,0.252,0.247,0.241,0.129,0.01,0.229,0.039,0.663,0.943,0.867
filters:
person:
min_area: 2000
max_area: 100000
threshold: 0.7
inertia: 1
loitering_time: 0
review:
alerts:
required_zones: Primaer
detections:
required_zones: Primaer
detect:
enabled: true

width: 640

height: 480

  fps: 7
snapshots:
  enabled: true
  required_zones:
    - Primaer
  retain:
    default: 30

------------------------Kamera 1 konfiguration SLUTTER her------------------------------

Global Record configuration

NOTE: Can be overridden at the camera level

record:
enabled: true
retain:
days: 14
mode: motion
events:
retain:
default: 30
mode: motion

Global Review configuration

NOTE: Can be overridden at the camera level

Dette er instillinger til forsiden hvor events bliver vist foroven

review:
alerts:
labels:
- person
- car
- car
- bicycle
- motorcycle
- boat
- cat
- dog
- hat
- backpack
- umbrella
- baseball bat
required_zones:
- Primaer

Frigate version nr.

version: 0.14

Originally created by @raverlution on GitHub (Jan 5, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Frigate ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/frigate.sh)" ### 📝 Provide a clear and concise description of the issue. Hi A couple a weeks ago i added the Frigate NVR with hardware transcoding on my Lenovo Tiny with a i5-14500t with Intel UHD 770. The problem is that every 12 - 36 hours it crashes my proxmox host. If i Connect a display to the server its just a Black screen with a little blinking White curser in the top left side. It is totally unresponsive. I can´t ssh to the server. The logs shows nothing. I have to pull the plug and Connect again to get it up and running. Sometimes I Can trick it to crash, when Plex transcodes and I get lots of motion in front of my camera. But not always I have been running Plex on this server for a couple of months without any problem (also created with the community script) Seems like Frigate somehow crashes the igpu? or that openvino crashes my proxmox host, if my "new" settings without hwaccel and only cpu detector is working? Proxmox 8.3.2 kernel 6.8.12-5-pve also tried kernel 6.11, but then the crash is within 1 hour. *The things i have tried: Disable hwaccel using: ffmpeg: hwaccel_args: '' But its the same, it crashes within 36 hours. Now for a test until my coral arrives i am running with: ffmpeg: hwaccel_args: '' and cpu detector (without openvino) it it has been running for 12 hours so far without issues, but will see if it lasts I have found a similar thread here? https://github.com/blakeblackshear/frigate/issues/8470 Any ideas? ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 11 ### 🔄 Steps to reproduce the issue. Sometimes not always: Plex transcoding one or more streams. Motion in front of the camera ### ❌ Paste the full error output (if available). Nothing gets written to the log ### 🖼️ Additional context (optional). # Aktiver mqtt server mqtt: host: 192.168.1.xxx user: user password: passwd detectors: ov: type: openvino device: CPU model: width: 300 height: 300 input_tensor: nhwc input_pixel_format: bgr path: /openvino-model/FP16/ssdlite_mobilenet_v2.xml labelmap_path: /openvino-model/coco_91cl_bkgr.txt # ffmpeg configuration # More information about presets at https://docs.frigate.video/configuration/ffmpeg_presets ffmpeg: hwaccel_args: '' input_args: preset-rtsp-restream output_args: record: preset-record-generic-audio-copy # Restream configuration # Uses https://github.com/AlexxIT/go2rtc (v1.9.2) go2rtc: streams: Indkoersel: - rtsp://xxx:xxx@192.168.1.xxx:554/h264Preview_01_main Indkoersel_sub: - rtsp://xxx:xxx@192.168.1.xxx:554/h264Preview_01_sub # ------------------------Kamera 1 konfiguration STARTER her------------------------------ cameras: Indkoersel: ffmpeg: inputs: - path: rtsp://192.168.1.xxx:8554/Indkoersel input_args: preset-rtsp-restream roles: - record - path: rtsp://192.168.1.xxx:8554/Indkoersel_sub input_args: preset-rtsp-restream roles: - detect motion: mask: 0.001,0.229,0.119,0.17,0.133,0.301,0.178,0.227,0.266,0.164,0.308,0.114,0.501,0.147,0.544,0.153,0.829,0.207,0.832,0.368,0.82,0.996,0.998,0.992,0.998,0.006,0.002,0.002 objects: track: - person - car - car - bicycle - motorcycle - boat - cat - dog - hat - backpack - umbrella - baseball bat mask: 0,0,1,0,1,1,0.918,1,0.846,0.223,0.34,0.148,0.267,0.111,0.223,0.133,0.231,0.273,0.143,0.321,0.124,0.171,0,0.233 zones: Primaer: coordinates: 0.923,0.364,0.252,0.247,0.241,0.129,0.01,0.229,0.039,0.663,0.943,0.867 filters: person: min_area: 2000 max_area: 100000 threshold: 0.7 inertia: 1 loitering_time: 0 review: alerts: required_zones: Primaer detections: required_zones: Primaer detect: enabled: true # width: 640 # height: 480 fps: 7 snapshots: enabled: true required_zones: - Primaer retain: default: 30 # ------------------------Kamera 1 konfiguration SLUTTER her------------------------------ # Global Record configuration # NOTE: Can be overridden at the camera level record: enabled: true retain: days: 14 mode: motion events: retain: default: 30 mode: motion # Global Review configuration # NOTE: Can be overridden at the camera level # Dette er instillinger til forsiden hvor events bliver vist foroven review: alerts: labels: - person - car - car - bicycle - motorcycle - boat - cat - dog - hat - backpack - umbrella - baseball bat required_zones: - Primaer # Frigate version nr. version: 0.14
OVERLORD commented 2026-02-04 17:38:50 +03:00
Author
Owner
Copy Link

@cricalix commented on GitHub (Jan 5, 2025):

Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project.

@cricalix commented on GitHub (Jan 5, 2025): Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project.
OVERLORD commented 2026-02-04 17:38:57 +03:00
Author
Owner
Copy Link

@adamsewell commented on GitHub (Jan 5, 2025):

Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project.

What other tread are you referring to? I'm having a similar issue but not with Frigate and I'm trying to narrow down what's causing it.

@adamsewell commented on GitHub (Jan 5, 2025): > Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project. What other tread are you referring to? I'm having a similar issue but not with Frigate and I'm trying to narrow down what's causing it.
OVERLORD commented 2026-02-04 17:39:10 +03:00
Author
Owner
Copy Link

@raverlution commented on GitHub (Jan 5, 2025):

Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project.

Yes it is possible, but when I disable hwaccel and uses openvino with Device: CPU then it doesnt use the igpu? In intel_gpu_top there is no ffmpeg or frigate_detect.

the Strange thing is I Can have 8+ 4K hdr to 1080p transcodes in Plex and there is no problem with that?

if you Can guide me I Can try and uninstall / disable the hardware acceleration in frigate LXC and see if it fixes things?

@raverlution commented on GitHub (Jan 5, 2025): > Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project. Yes it is possible, but when I disable hwaccel and uses openvino with Device: CPU then it doesnt use the igpu? In intel_gpu_top there is no ffmpeg or frigate_detect. the Strange thing is I Can have 8+ 4K hdr to 1080p transcodes in Plex and there is no problem with that? if you Can guide me I Can try and uninstall / disable the hardware acceleration in frigate LXC and see if it fixes things?
OVERLORD commented 2026-02-04 17:39:24 +03:00
Author
Owner
Copy Link

@raverlution commented on GitHub (Jan 5, 2025):

Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project.

What other tread are you referring to? I'm having a similar issue but not with Frigate and I'm trying to narrow down what's causing it.

This one:) https://github.com/blakeblackshear/frigate/issues/8470

@raverlution commented on GitHub (Jan 5, 2025): > > Given the other thread is talking about Docker-installs etc, it's possible this is a kernel level thing with the i915 driver, and nothing specific to proxmox or the community scripts project. > > What other tread are you referring to? I'm having a similar issue but not with Frigate and I'm trying to narrow down what's causing it. This one:) https://github.com/blakeblackshear/frigate/issues/8470
OVERLORD commented 2026-02-04 17:39:35 +03:00
Author
Owner
Copy Link

@remz1337 commented on GitHub (Jan 5, 2025):

I did face something similar once and increasing the maximum memory (RAM) fixed the issue for me. Maybe you can give that a shot? Otherwise, I think we will need to followup on the Frigate repo as the issue seems to affect people also running the official Docker image

@remz1337 commented on GitHub (Jan 5, 2025): I did face something similar once and increasing the maximum memory (RAM) fixed the issue for me. Maybe you can give that a shot? Otherwise, I think we will need to followup on the Frigate repo as the issue seems to affect people also running the official Docker image
OVERLORD commented 2026-02-04 17:39:39 +03:00
Author
Owner
Copy Link

@raverlution commented on GitHub (Jan 5, 2025):

I did face something similar once and increasing the maximum memory (RAM) fixed the issue for me. Maybe you can give that a shot? Otherwise, I think we will need to followup on the Frigate repo as the issue seems to affect people also running the official Docker image

I have 32gb ddr5 in the machine and frigate LXC has 8gb avaliable right now, but only uses around 0.5gb I will try and raise it to 16gb:)

I have also read some where else, that lowering the ram speed a bit fixed the issue. So will try that also.

@raverlution commented on GitHub (Jan 5, 2025): > I did face something similar once and increasing the maximum memory (RAM) fixed the issue for me. Maybe you can give that a shot? Otherwise, I think we will need to followup on the Frigate repo as the issue seems to affect people also running the official Docker image I have 32gb ddr5 in the machine and frigate LXC has 8gb avaliable right now, but only uses around 0.5gb I will try and raise it to 16gb:) I have also read some where else, that lowering the ram speed a bit fixed the issue. So will try that also.
OVERLORD commented 2026-02-04 17:39:49 +03:00
Author
Owner
Copy Link

@jsapede commented on GitHub (Jan 6, 2025):

hwaccel are settings for hardware ffmpeg transcoding, but has nothing to do with openvino witch is specific for AI models.

Intel_gpu_top should rise render activity on détection if you correctly set openvino.

Sometimes frigate ears all the memory and starts to swap heavily blocking the host at 100% CPU. You need to increase ram and reduce pve swappiness.

Moreover, having a pass of fstrim enhances the perfs pf frigate.

@jsapede commented on GitHub (Jan 6, 2025): hwaccel are settings for hardware ffmpeg transcoding, but has nothing to do with openvino witch is specific for AI models. Intel_gpu_top should rise render activity on détection if you correctly set openvino. Sometimes frigate ears all the memory and starts to swap heavily blocking the host at 100% CPU. You need to increase ram and reduce pve swappiness. Moreover, having a pass of fstrim enhances the perfs pf frigate.
OVERLORD commented 2026-02-04 17:39:56 +03:00
Author
Owner
Copy Link

@raverlution commented on GitHub (Jan 6, 2025):

hwaccel are settings for hardware ffmpeg transcoding, but has nothing to do with openvino witch is specific for AI models.

Intel_gpu_top should rise render activity on détection if you correctly set openvino.

Sometimes frigate ears all the memory and starts to swap heavily blocking the host at 100% CPU. You need to increase ram and reduce pve swappiness.

Moreover, having a pass of fstrim enhances the perfs pf frigate.

Yeah i know.

when i am using openvino i have a frigate_detect show up in the intel-gpu-top. But proxmox host crash within 36 hours)

I have then tried to use CPU with openvino but its the same proxmox crashes within 36 hours.

Now I have removed the detectors from the configfile as a test and so far no crashes, so i wonder of it is openvino that crashes proxmox?

I have given frigate 16gb ram and disabled swap now also

@raverlution commented on GitHub (Jan 6, 2025): > hwaccel are settings for hardware ffmpeg transcoding, but has nothing to do with openvino witch is specific for AI models. > > Intel_gpu_top should rise render activity on détection if you correctly set openvino. > > Sometimes frigate ears all the memory and starts to swap heavily blocking the host at 100% CPU. You need to increase ram and reduce pve swappiness. > > Moreover, having a pass of fstrim enhances the perfs pf frigate. Yeah i know. when i am using openvino i have a frigate_detect show up in the intel-gpu-top. But proxmox host crash within 36 hours) I have then tried to use CPU with openvino but its the same proxmox crashes within 36 hours. Now I have removed the detectors from the configfile as a test and so far no crashes, so i wonder of it is openvino that crashes proxmox? I have given frigate 16gb ram and disabled swap now also
OVERLORD commented 2026-02-04 17:40:09 +03:00
Author
Owner
Copy Link

@raverlution commented on GitHub (Jan 7, 2025):

It has just crashed again. So it has nothing to do with hwaccel or openvino.

Very strange. If I dont start frigate lxc then the server runs for months

@raverlution commented on GitHub (Jan 7, 2025): It has just crashed again. So it has nothing to do with hwaccel or openvino. Very strange. If I dont start frigate lxc then the server runs for months
OVERLORD commented 2026-02-04 17:40:12 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Jan 7, 2025):

You should better ask in the Frigate repo and not here. This dose not seem to be related to the community-scripts.

@michelroegl-brunner commented on GitHub (Jan 7, 2025): You should better ask in the Frigate repo and not here. This dose not seem to be related to the community-scripts.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#274
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?