-
Posts
15 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Krypto5
-
-
Do you know how to fix this error searx.botdetection.config where it says that the /etc/searxng/limiter.toml configuration file is missing?
2024-05-03 14:37:45,073 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x14750248a718 pid: 549 (default app)
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x14750248a718 pid: 569 (default app)
2024-05-03 14:37:45,073 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x14750248a718 pid: 521 (default app)
2024-05-03 14:37:45,075 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x14750248a718 pid: 514 (default app)
2024-05-03 14:37:45,075 WARNING:searx.botdetection.config: missing config file: /etc/searxng/limiter.toml
WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x14750248a718 pid: 515 (default app)
[uWSGI] getting INI configuration from /etc/searxng/uwsgi.ini -
W
12 hours ago, JorgeB said:Syslog starts over after every boot, also it usually won't have anything logged for that kind of issue anyway, just see if the server runs stable now.
with me has been the same problem , it has been more than 1 week that the server crashes every 2 or 3 days of use, and sometimes it still occurs that the dockers stop alone, right now it occurred that the dockers are all showing that they were active , but in fact they were all stopped, I tried to restart the dockers manually and presents error message:
Execution Error:
Error Code 403
In the error log here appeared this:
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS error (device loop2): block=21414051840 write time tree block corruption detected
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction)
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS info (device loop2: state E): forced readonly
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction.
Mar 19 17:38:11 ROGERSERVER kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1992: errno=-5 IO failure
Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 3(vethed82632) entered disabled state
Mar 19 17:40:30 ROGERSERVER kernel: docker0: port 8(veth41669a3) entered disabled state
Mar 19 17:40:30 ROGERSERVER kernel: vethb24fb11: renamed from eth0
Mar 19 17:40:30 ROGERSERVER kernel: veth12a7133: renamed from eth0
From what I saw other people here in the forum with the same problem , referring to the CACHE this damaged, a friend of mine who also uses unraid had exactly the same problem, and he had to delete all content from the cache, format and recreate to solve the problem. -
Here I used this command:
chmod +x /usr/local/bin/cpsumon/cpsumoncli
He proceeded to read the information again. When I reset the computer right after updating to version 6.12 the card came without any source information, when executing the command in Terminal everything worked again.
I use the Corsair AX1500i font.
Thank you for your great work GIGANODE. -
2 hours ago, SohailS said:
Thanks for the info yes I have the HikVision I was wondering what is this for?
output_args:
record: preset-record-generic-audio-aac
I now have it working with ffmpeg encoding my stream to aac
As far as I know, this code tells Frigate to record the audio from the cameras in AAC format when the camera doesn't display that audio natively, in my case if I leave the COPY option which is to get the original audio from the camera simply recording no sound, so I have to use -
aac so that it converts to that format and saves to the .mp4 file, this is what I understood, I could be wrong. -
12 hours ago, SohailS said:
I am trying to get audio working in the latest release. my camera does not support AAC which is the best option to choose?
Your camera is probably the same as mine: Hikvision, I don't know why Hikvision has difficulty enabling the audio of the cameras during recordings or streams, here I constantly end up having problems with crashes, stuttering or simply the audio is disabled for use.
What I did to work around the situation was to try to add a few lines in the code for the restream of each camera, the most incredible thing is that I have more than 4 Hikvision camera models in my house and each one I have to use a different configuration so that the Frigate understand and enable the audio, however it turns out that sometimes it works only for recording but it doesn't work live, sometimes the reverse also happens.
It's very complicated to be able to adjust the audio of the Hikvision cameras on the Frigate, it's even a question that I was thinking of posting here to see if more people have the same problem and how they solved it, it's probably some FFMPEG command that has to be included to improve compatibility or simply the syntax of the code that should have some more correct order to improve compatibility because I've already done several tests with audio trying to convert to AAC or just using COPY in some options and it works.
An example I use here:streams:
porteiro:
- rtsp://user:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
porteiro_sub:
- rtsp://user:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2
porteiro:
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/porteiro?video=copy&audio=copy
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://127.0.0.1:8554/porteiro_sub
input_args: preset-rtsp-restream
roles:
- detect
output_args:
record: preset-record-generic-audio-aac
-
I would like to ask for some help, I would greatly appreciate it if you can shed some light on how to solve the problem, I am trying to implement the use of go2rtc in my new version of FRIGATE 0.12.0-DA3E197
PROBLEM: When I entered the information that I didn't have in the old versions to use GO2RTC, the camera image no longer appears in the FRIGATE UI and instead of the image it shows this message:
No frames have been received, check error logs
In the error log, it accuses the information in the attached photo: Connection refused
Below is my config.yml , in this config I am trying to enable only 1 camera, because when I tried with all of them there was a greater chance of giving a problem, syntax, any other error, so I tried with some cameras and finally I am trying only with one to find the problem.
All Cameras are Hikvision and to avoid any chance of being the video protocol I chose the camera: PORTEIRO which only uses h.264 in both streams, the other cameras have h.265 for recording and h.264 for detection.
-
Ah ok thank you, wow what a shame they keep the hours incorrect, I believe it is not something so complex to correct.
Thanks.28 minutes ago, Tarcisio said:Read my post. In short, it can't be changed. It's gonna be like that from now on.
-
On 4/19/2023 at 3:14 PM, Tarcisio said:
Did anybody find a solution for that?
I am having the same problem as you, at this moment it is 12:20h and the folders that are being generated contain the time of: 15:20h, in short the folders are being generated with an advance of 3 Hours and my UTC is -3:00 São Paulo Brazil , how did you fix this ,
changed in which part of the system or UNRAID to perform the correction of the time the folders are created, thanks in advance for the help. -
18 minutes ago, gareth_iowc said:
Thanks that worked
I would like to review short videos clips of the events and have added
clips:
enabled: true
retain:
defualt: 15but frigate wont start with that added
mqtt: host: 10.10.50.8 cameras: back: ffmpeg: inputs: - path: rtsp://user:[email protected]:554/Streaming/Channels/101 roles: - detect - rtmp - clips objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person - car - cat - dog - bird snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: true # Optional: print a timestamp on the snapshots (default: shown below) timestamp: False # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: False # Optional: crop the snapshot (default: shown below) crop: False # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 10 # Optional: Per object retention days objects: person: 15 clips: enabled: true retain: defualt: 15 # Optional: Detectors configuration. Defaults to a single CPU detector detectors: # Required: name of the detector coral: # Required: type of the detector # Valid values are 'edgetpu' (requires device property below) and 'cpu'. type: edgetpu # Optional: device name as defined here: https://coral.ai/docs/edgetpu/multiple-edgetpu/#using-the-tensorflow-lite-python-api device: usbCLIPS no longer exist, they were removed from the code in the most current versions, now the clips are already integrated into RECORD
See how I currently use RECORD so that it leaves the event recordings (CLIPS in the past) for certain days that I choose.
The solution is to remove all that part of the CLIPS code
Example:
record:
enabled: True
retain:
days: 5
mode: all
events:
retain:
default: 5
mode: motion-
2
-
-
On 3/12/2022 at 11:58 AM, elbro_dark said:
hi,
i think i´m to dumb to add this to my homeassistant.... could someone help me ?
i added this to my configuration.yamlsensor: - platform: rest name: Corsair PSU json_attributes: - temp1 - temp2 - fan_rpm - capacity - 12v_watts - 5v_watts - 3v_watts - watts - load - uptime - poweredon resource: "http://192.168.178.123/plugins/corsairpsu/status.php" username: !secret unraid_login password: !secret unraid_password authentication: basic value_template: "{{ value_json.product }}" headers: User-Agent: Home Assistant Content-Type: application/json - platform: template sensors: psu_temp1: friendly_name: "Temperature 1" value_template: '{{ states.sensor.corsair_psu.attributes["temp1"] }}' psu_temp2: friendly_name: "Temperature 2" value_template: '{{ states.sensor.corsair_psu.attributes["temp2"] }}' psu_fan_rpm: friendly_name: "Fan Speed" value_template: '{{ states.sensor.corsair_psu.attributes["fan_rpm"] }}' psu_capactiy: friendly_name: "Capacity" value_template: '{{ states.sensor.corsair_psu.attributes["capacity"] }}' psu_12v_watts: friendly_name: "12v Watts" value_template: '{{ states.sensor.corsair_psu.attributes["12v_watts"] }}' psu_5v_watts: friendly_name: "5v Watts" value_template: '{{ states.sensor.corsair_psu.attributes["5v_watts"] }}' psu_3v_watts: friendly_name: "3v Watts" value_template: '{{ states.sensor.corsair_psu.attributes["3v_watts"] }}' psu_watts: friendly_name: "Current Load" value_template: '{{ states.sensor.corsair_psu.attributes["watts"] }}' psu_load: friendly_name: "Current Load Percentage" value_template: '{{ states.sensor.corsair_psu.attributes["load"] }}' psu_uptime: friendly_name: "Uptime" value_template: '{{ states.sensor.corsair_psu.attributes["uptime"] }}' psu_poweredon: friendly_name: "Total Power On Hours" value_template: '{{ states.sensor.corsair_psu.attributes["poweredon"] }}'This errors appears in homeassistant:
Template variable error: 'value_json' is undefined when rendering '{{ value_json.product }}'Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute '3v_watts' when rendering '{{ states.sensor.corsair_psu.attributes["3v_watts"] }}' Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'watts' when rendering '{{ states.sensor.corsair_psu.attributes["watts"] }}' Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'load' when rendering '{{ states.sensor.corsair_psu.attributes["load"] }}' Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'uptime' when rendering '{{ states.sensor.corsair_psu.attributes["uptime"] }}' Template variable warning: 'homeassistant.util.read_only_dict.ReadOnlyDict object' has no attribute 'poweredon' when rendering '{{ states.sensor.corsair_psu.attributes["poweredon"] }}'Do i need to add there something extra?
Did you manage to add this app to Home Assistant, if so, could you please explain how you did it? I'm new to home assistant and I have an AX1500i that already works correctly in UNRAID, but I wanted to create a CARD in my Home assistant with this information, thank you.
-
6 hours ago, yayitazale said:
I don't see anything wrong. Can you try to use the coral in another computer with one of the example projects https://coral.ai/examples/
We found some corals are factory defective.
Thank you immensely for your attempt to help, I managed to make the G. CORAL USB work on my server using the UNRAID system, what I did to correct it was to change information within the config.yml file that is located in the frigate/config folder.
Basically the G. Coral USB is not identified as long as FRIGATE does not present ZERO ERRORS when the service is started, while the service cannot start google coral continues to appear as unidentified, as long as there is no longer any error in the configuration of the file config.yml the pendrive will be detected and will even change the HARDWARE ID of the pendrive without the need to make any changes to the system, the frigate itself will identify the PEN DRIVE google CORAL with the ID 18d1:9302,
I saw several reports of people who were having problems with FRIGATE seeing only the HARDWARE ID as: 1a6e:089a Global Unichip Corp, this actually happens, but it only happens if the command lines in CONFIG.YML still have errors.At least that was my experience with the UNRAID system using the frigate via DOCKER, I don't know if this is replicated for other systems, but here, as soon as the configuration of the config.yml file was completely correct and I restarted the MQTT and FRIGATE service and both were in GREEN status constantly the google flash drive was detected correctly and started to work automatically changing to the ID and recognition form of the GOOGLE CORAL USB flash drive.
The correct thing is to analyze all the lines of the FRIGATE LOG and excluding the lines that are showing errors to minimize as much as possible the amount of configurations necessary to load the frigate and start the system. One detail I noticed is that FRIGATE via DOCKER on UNRAID SERVER requires much less configuration in the config.yml because they are already available in DOCKER's EDIT via UNRAID, not being necessary to be declared and configured again in config.yml, below I will list how my CONFIG.YML is currently and now everything works perfectly loading GOOGLE CORAL and identifying all objects perfectly.
The biggest problem I faced was to get the FRIGATE service on UNRAID (via DOCKER) to start, it started quickly, turning green in the status, after a few seconds the service was automatically turned off, because there were coding errors in its config.yml file,
another detail that I realized that I needed to EDIT the FRIGATE Docker in UNRAID and change its connection type from Bridge to HOST , this way also made it easier for the system to stay online permanently.
I'm going to change only the passwords and login part by putting generic values, only in the password I don't know if this is really necessary or mandatory but I followed a pattern that I saw in a documentation where it describes that the password must start with the syntax: FRIGATE_********* (**** enter your password here).
I configured the MQTT service password by creating and editing the passwords.txt file inside the MQTT folder and put
typeyourusernamehere:FRIGATE_yourpasswordhere , then save the file as passwords.txt and put on directory /MQTT the password will work from this moment on. Then use this same username and password in the config.yml filemqtt:
host: 192.168.0.50
user: insert your username here
password: FRIGATE_mypasswordhere
stats_interval: 5cameras:
doorcam: #camera name
ffmpeg:
inputs:
- path: rtsp://admin:[email protected]:554/Streaming/Channels/101/
snapshots:
enabled: true
bounding_box: true
retain:
default: 1
objects:
track:
- person
- bird
- cat
- dog
- motorcycle
- bicycle
- car
zones:
zone_0:
coordinates: 1280,720,1280,280,0,281,0,720,289,720detectors:
coral:
type: edgetpu
device: usb
Once again, thank you very much for your help, I just have one question left: the organization of the code in relation to the syntax structure must be all organized according to the text above or the config.yml can be edited without spaces and tabs? Is it necessary for each command line to have the exact position to start the text? Thanks and hugs, your software is amazing. -
14 hours ago, yayitazale said:
Can you attach the configuration of the container?
Thank you very much in advance for your help and attention, the prints are below, if that is not what you want, please let me know where I am looking for the information you need, very grateful!
-
I am not able to make the FRIGATE detect my GOOGLE CORAL USB, for all the attempts I made it always appears written: No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
What I noticed in some forums was the detail referring to the HARDWARE ID of the pendrive is different from what FRIGATE looks for when it tries to locate a GOOGLE CORAL USB, the ID that is searched for would be the number: 18d1:9302 , since what is detected in my PC (I use UNRAID SERVER system) is the number : 1a6e:089a Global Unichip Corp.
How can I make FRIGATE be able to locate the GOOGLE CORAL USB flash drive plugged into the machine?
VersionCurrent version: 3.1
Frigate config file
mqtt:
host: 192.168.0.213
port: 1883
topic_prefix: frigate
client_id: frigate
user: roger561
password: roger561
stats_interval: 60
detectors:
coral:
type: edgetpu
device: usb
database:
path: /media/frigate/frigate.db
cameras:
back:
ffmpeg:
inputs:
- path: rtsp://admin:[email protected]:554/Streaming/Channels/102/
roles:
- detect
[SUPPORT] blakeblackshear - Frigate
in Docker Containers
Posted · Edited by Krypto5
change
I'm having a daily problem with my frigate where it starts to have problems with generally two cameras (RUA ESQUERDA and POSTE), both cameras have FFMPEG errors I believe, it must be something in the configuration that I don't know how to do correctly. RUA ESUQUERDA is a Hikvision 4k camera model DS-2CD2387G2-LU and POSTE is a Sony 5MP PTZ camera.
Could anyone give me a hint as to why every day when I look at the logs and config I have these errors? The Frigate even restarts itself to correct errors. I would greatly appreciate it if anyone could give me some suggestions to correct this problem that affects my recordings every day.
LOG:
2024-05-27 21:34:18.688780742 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.detect ERROR : [rtsp @ 0x560f8d6d1e40] method DESCRIBE failed: 404 Not Found 2024-05-27 21:34:18.688787678 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.detect ERROR : rtsp://127.0.0.1:8554/rua_esquerda_sub: Server returned 404 Not Found 2024-05-27 21:34:18.697986332 [2024-05-27 21:34:18] ffmpeg.rua_esquerda.record ERROR : rtsp://127.0.0.1:8554/rua_esquerda?video&audio#?video=copy&audio=copy: Invalid data found when processing input 2024-05-27 21:34:18.697999926 [2024-05-27 21:34:18] watchdog.rua_esquerda INFO : Terminating the existing ffmpeg process... 2024-05-27 21:34:18.698012297 [2024-05-27 21:34:18] watchdog.rua_esquerda INFO : Waiting for ffmpeg to exit gracefully... 2024-05-27 21:34:20.315024489 21:34:20.314 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda 2024-05-27 21:34:21.790244449 21:34:21.790 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda_sub 2024-05-27 21:34:21.791386603 [2024-05-27 21:34:21] frigate.video ERROR : rua_esquerda: Unable to read frames from ffmpeg process. 2024-05-27 21:34:21.791412414 [2024-05-27 21:34:21] frigate.video ERROR : rua_esquerda: ffmpeg process is not running. exiting capture thread... 2024-05-27 21:34:25.426033835 21:34:25.425 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:28.705357314 [2024-05-27 21:34:28] watchdog.rua_esquerda ERROR : Ffmpeg process crashed unexpectedly for rua_esquerda. 2024-05-27 21:34:28.705455689 [2024-05-27 21:34:28] watchdog.rua_esquerda ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-05-27 21:34:28.705458298 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.detect ERROR : [rtsp @ 0x563d10856e40] method DESCRIBE failed: 404 Not Found 2024-05-27 21:34:28.705459532 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.detect ERROR : rtsp://127.0.0.1:8554/rua_esquerda_sub: Server returned 404 Not Found 2024-05-27 21:34:28.714526347 [2024-05-27 21:34:28] ffmpeg.rua_esquerda.record ERROR : rtsp://127.0.0.1:8554/rua_esquerda?video&audio#?video=copy&audio=copy: Invalid data found when processing input 2024-05-27 21:34:28.714559048 [2024-05-27 21:34:28] watchdog.rua_esquerda INFO : Terminating the existing ffmpeg process... 2024-05-27 21:34:28.714580085 [2024-05-27 21:34:28] watchdog.rua_esquerda INFO : Waiting for ffmpeg to exit gracefully... 2024-05-27 21:34:30.535760855 21:34:30.535 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:40.887557403 21:34:40.887 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1, dial tcp 192.168.0.26:554: connect: no route to host" stream=rua_esquerda 2024-05-27 21:34:40.887585019 21:34:40.887 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:55526: write: broken pipe" 2024-05-27 21:34:45.997629452 21:34:45.997 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:51.106756813 21:34:51.106 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:34:59.291877286 21:34:59.291 WRN [streams] json locked 2024-05-27 21:35:01.326830025 21:35:01.326 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:06.436519295 21:35:06.436 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: i/o timeout, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:06.436542498 21:35:06.436 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:56054: write: broken pipe" 2024-05-27 21:35:11.547261036 21:35:11.547 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:21.766576106 21:35:21.766 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: no route to host, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:26.876060191 21:35:26.875 WRN [rtsp] error="streams: dial tcp 192.168.0.26:554: connect: connection refused, exec: exit status 1" stream=rua_esquerda 2024-05-27 21:35:26.876092691 21:35:26.876 WRN github.com/AlexxIT/go2rtc/internal/rtsp/rtsp.go:225 > error="write tcp 127.0.0.1:8554->127.0.0.1:39170: write: broken pipe" 2024-05-28 05:11:23.852439638 [2024-05-28 05:11:23] frigate.record.maintainer WARNING : Discarding a corrupt recording segment: /tmp/cache/[email protected] 2024-05-28 05:11:29.207705993 [2024-05-28 05:11:29] watchdog.poste INFO : poste exceeded fps limit. Exiting ffmpeg... 2024-05-28 05:11:29.207798735 [2024-05-28 05:11:29] watchdog.poste INFO : Waiting for ffmpeg to exit gracefully... 2024-05-28 05:12:00.000561366 05:11:59.991 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error=EOF url=ffmpeg:rtsp://admin:[email protected]:554/1/h264major#video=copy 2024-05-28 05:12:00.463240751 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466337848 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466560764 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466563639 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466564850 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466565866 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466566922 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466567954 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466569045 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466570070 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466658345 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466659555 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466662726 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466663813 [2024-05-28 05:12:00] frigate.video ERROR : poste: Unable to read frames from ffmpeg process. 2024-05-28 05:12:00.466664850 [2024-05-28 05:12:00] frigate.video ERROR : poste: ffmpeg process is not running. exiting capture thread... 2024-05-28 05:12:09.667740257 [2024-05-28 05:12:09] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 05:12:10.466555950 [2024-05-28 05:12:10] watchdog.poste ERROR : Ffmpeg process crashed unexpectedly for poste. 2024-05-28 05:12:10.466707241 [2024-05-28 05:12:10] watchdog.poste ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2024-05-28 05:12:10.466709198 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 100 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:10.466710244 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 1000 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:10.466718538 [2024-05-28 05:12:10] ffmpeg.poste.detect ERROR : [out_0_0 @ 0x563d23336a00] 10000 buffers queued in out_0_0, something may be wrong. 2024-05-28 05:12:14.667533615 [2024-05-28 05:12:14] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 05:12:19.668149232 [2024-05-28 05:12:19] frigate.record.maintainer WARNING : Unable to keep up with recording segments in cache for poste. Keeping the 6 most recent segments out of 7 and discarding the rest... 2024-05-28 06:13:10.561090443 [2024-05-28 06:13:10] watchdog.poste ERROR : No new recording segments were created for poste in the last 120s. restarting the ffmpeg record process...CONFIG:
mqtt: host: 192.168.0.50 port: 1883 user: admin password: admin detectors: coral: type: edgetpu device: usb birdseye: enabled: false ffmpeg: hwaccel_args: preset-vaapi go2rtc: streams: #------------------ porteiro: - ffmpeg:rtsp://admin:[email protected]:554/h264/ch01/main/av_stream - "ffmpeg:porteiro#audio=opus" #------------------ poste: - "ffmpeg:rtsp://admin:[email protected]:554/1/h264major#video=copy" poste_sub: - rtsp://admin:[email protected]:554/1/h264minor #------------------ rua_esquerda: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:rua_esquerda#audio=opus" rua_esquerda_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ telhado: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:telhado#audio=opus" telhado_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ quintal: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 quintal_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ corredor: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:corredor#audio=opus" corredor_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ quintal_atras: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 quintal_atras_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ fundos: - rtsp://admin:[email protected]:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1 - "ffmpeg:fundos#audio=opus" fundos_sub: - rtsp://admin:[email protected]:554/Streaming/Channels/102?transportmode=unicast&profile=Profile_2 #------------------ webrtc: candidates: - 192.168.0.50:8555 - stun:8555 ports: - 8555:8555/tcp # WebRTC over tcp - 8555:8555/udp # WebRTC over udp - 5000:5000 - 1935:1935 - 8554:8554 cameras: #-------------------------------------------------------------------------------------POSTE poste: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/poste input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/poste_sub input_args: preset-rtsp-restream roles: - detect onvif: host: 192.168.0.20 port: 8999 user: admin password: password detect: width: 720 height: 576 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - car - person filters: car: mask: - 720,0,0,0,0,119,331,116,366,202,720,389 person: mask: - 0,114,0,0,720,0,720,167,422,104,358,195,335,118 zones: calçada_poste: coordinates: 0,576,720,576,720,156,412,97,354,198,338,115,0,120 motion: mask: - 0,114,330,116,359,198,410,103,720,172,720,0,0,0 ui: order: 1 #-------------------------------------------------------------------------------------PORTEIRO porteiro: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/porteiro?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - detect detect: width: 1280 height: 720 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person filters: person: mask: - 1194,415,1134,409,1147,539,1188,528 - 105,501,57,498,60,442,98,442 zones: frente_porteiro: coordinates: 0,720,1280,720,1280,320,0,169 motion: mask: - 1280,381,1280,0,0,0,0,249 ui: order: 2 #-------------------------------------------------------------------------------------RUA_ESQUERDA rua_esquerda: ffmpeg: output_args: record: preset-record-generic-audio-copy inputs: - path: rtsp://127.0.0.1:8554/rua_esquerda?video&audio input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/rua_esquerda_sub input_args: preset-rtsp-restream roles: - detect detect: width: 1280 height: 720 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person - car - motorcycle - bicycle filters: car: mask: - 1280,158,1280,0,0,0,0,124,957,93,985,150 - 828,204,864,190,859,137,815,147 - 168,418,469,314,428,283,166,362 person: mask: - 1280,0,1280,157,975,147,957,0 - 658,134,666,209,627,231,616,135 zones: ruaesquerda_frente: coordinates: 1280,166,836,93,543,108,0,256,0,720,1280,720 motion: mask: - 794,95,771,193,737,198,702,89,0,245,0,0,1280,0,1280,161,936,154,937,90 ui: order: 3 #-------------------------------------------------------------------------------------TELHADO telhado: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/telhado?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/telhado_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person - car filters: car: mask: - 640,0,640,480,510,370,358,0 person: mask: - 437,401,506,441,618,223,580,131 zones: telhado_entr: coordinates: 640,480,640,126,575,0,0,0,0,480 motion: mask: - 474,0,484,24,579,23,640,121,640,0 - 528,480,640,480,640,391 ui: order: 4 #-------------------------------------------------------------------------------------QUINTAL quintal: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/quintal?video=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/quintal_sub?video=copy input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person filters: person: mask: - 640,0,640,480,640,306,227,99,150,0 zones: quintal_frente: coordinates: 0,480,0,64,217,0,245,107,640,305,640,480 saida_de_pessoas: coordinates: 0,480,640,480,640,309,473,226,0,310 motion: mask: - 640,0,151,0,245,123,640,320 ui: order: 5 #-------------------------------------------------------------------------------------CORREDOR corredor: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/corredor?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/corredor_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: corredor_lateral: coordinates: 640,221,0,0,0,480,640,480 casa_vizinho: coordinates: 640,230,640,0,118,0,69,61 ui: order: 6 #-------------------------------------------------------------------------------------QUINTAL_ATRAS quintal_atras: ffmpeg: output_args: record: preset-record-generic inputs: - path: rtsp://127.0.0.1:8554/quintal_atras?video=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/quintal_atras_sub?video=copy input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: quint_at: coordinates: 0,480,0,194,225,0,640,0,640,480 motion: mask: - 0,0,0,207,261,0 ui: order: 7 #-------------------------------------------------------------------------------------FUNDOS fundos: ffmpeg: output_args: record: preset-record-generic-audio-aac inputs: - path: rtsp://127.0.0.1:8554/fundos?video=copy&audio=copy input_args: preset-rtsp-restream roles: - record - path: rtsp://127.0.0.1:8554/fundos_sub input_args: preset-rtsp-restream roles: - detect detect: width: 640 height: 480 fps: 5 record: enabled: true retain: days: 5 mode: all events: retain: default: 5 mode: motion snapshots: enabled: true bounding_box: true crop: true height: 300 retain: default: 5 objects: track: - person zones: fundos_mato: coordinates: 640,0,0,97,0,480,640,480 motion: mask: - 640,0,640,45,117,36,0,114,0,0 - 363,279,135,412,98,252,94,62,241,0 - 401,480,640,480,640,309,534,319,474,342 ui: order: 8