NEWS
Proxmox LXC mit Frigate
-
@wal Hallo Walter,
vielen Dank für deine Mühen. Auch mit der minimalen config ändert sich bei mir nichts. Ich setze das Ganze nochmals neu auf. Wenn es bei allen anderen geht, muss ich ja irgendwo einen Fehler gemacht haben.
Ich wünsche Dir ein angenehmes Wochenende.
Ralf -
@radi ,
in der frigate config vom container wird das Laufwerk auf /media/frigate gemappt, falls es das Verzeichnis im LXC nicht nicht gibt .... -
Heute habe ich auf den Kernel 5.15.107-1-pve geupdatet und was soll ich sagen, die Coral Edge TPU funktioniert nicht mehr in einem Unprivilegierten Container.
Die Backups funktionieren auch nicht mehr. Ich installiere jetzt schon 5 Stunden am Proxmox und bin jetzt bei einem Privilegierten LXC gelandet.Edit: Ich habe die Rechte der Coral TPU von 660 auf 755 erhöht und da ging es dann.
-
@wal hallo welche lxc hast du genommen bei mir gibt es fehler mit pfad findet config nicht frigate geht in bootschleife .
habe ubuntu 22.1detectors: ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 9, column 2: cameras: ^ 2023-05-07 12:39:35.229716379 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-05-07 12:39:36.234223582 [INFO] Preparing go2rtc config... Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 36, in get_single_node document = self.compose_document() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 55, in compose_document node = self.compose_node(None, None) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node while not self.check_event(MappingEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 438, in parse_block_mapping_key raise ParserError("while parsing a block mapping", self.marks[-1], yaml.parser.ParserError: while parsing a block mapping in "<unicode string>", line 1, column 1: detectors: ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 9, column 2: cameras: ^ 2023-05-07 12:39:36.459721903 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-05-07 12:39:37.463508621 [INFO] Preparing go2rtc config... Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 36, in get_single_node document = self.compose_document() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 55, in compose_document node = self.compose_node(None, None) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node while not self.check_event(MappingEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 438, in parse_block_mapping_key raise ParserError("while parsing a block mapping", self.marks[-1], yaml.parser.ParserError: while parsing a block mapping in "<unicode string>", line 1, column 1: detectors: ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 9, column 2: cameras: ^ 2023-05-07 12:39:37.661047849 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-05-07 12:39:38.665754030 [INFO] Preparing go2rtc config... Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 36, in get_single_node document = self.compose_document() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 55, in compose_document node = self.compose_node(None, None) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node while not self.check_event(MappingEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 438, in parse_block_mapping_key raise ParserError("while parsing a block mapping", self.marks[-1], yaml.parser.ParserError: while parsing a block mapping in "<unicode string>", line 1, column 1: detectors: ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 9, column 2: cameras: ^ 2023-05-07 12:39:38.884406556 [INFO] The go2rtc service exited with code 1 (by signal 0)
version: "3.9" services: frigate: container_name: frigate privileged: true # this may not be necessary for all setups restart: unless-stopped image: ghcr.io/blakeblackshear/frigate:stable shm_size: "64mb" # update for your cameras based on calculation above devices: - /dev/bus/usb:/dev/bus/usb # passes the USB Coral, needs to be modified for other versions - /dev/apex_0:/dev/apex_0 # passes a PCIe Coral, follow driver instructions here https://cora> - /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware volumes: - /etc/localtime:/etc/localtime:ro - /frigate/config.yml:/config/config.yml:ro - /frigate:/media/frigate - type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear target: /tmp/cache tmpfs: size: 1000000000 ports: - "5000:5000" - "1935:1935" # RTMP feeds
volumes: - /etc/localtime:/etc/localtime:ro - /root/config/config.yml:/config/config.yml:ro - /root/frigate:/media/frigate
das klappte auch nicht
-
@exitus,
ich nutze das docker script von TTeck .
Konnte da man Ubuntu auswählen ?
Ich nutze Debian./frigate/config.yml
das kann nur funktionieren wenn im Ordner /frigate eine config.yml liegt.
Mittlerweile habe ich einen User frigate erstellt und im Userordner einen Ordner frigate, dort liegt meine config.yml.
- /home/frigate/frigate/config.yml:/config/config.yml
-
@wal Ja, man kann da, zumindest bei mir, aus drei verschiedenen Versionen Ubuntu oder eben Debian auswählen.
@exitus Wo findet man das Logfile. Ich komme nur über Portainer an ein nicht sonderlich aussagekräftiges Logfile, dass mir alle paar Sekunden ein "Container frigate exited with status code 1" ausspuckt.Manchmal ist es wie verhext. Ich suche ja schon eine ganze Weile, warum das bei mir nicht funktioniert.
Jetzt habe ich im Portainer auch das Logfile für den Container Frigate gefunden. Da steht: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-07 13:43:21.141928870 [INFO] Preparing go2rtc config... s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting 2023-05-07 13:43:21.143878913 [INFO] Starting NGINX... s6-rc: info: service legacy-services successfully started 2023-05-07 13:43:21.151714209 [INFO] Starting Frigate... Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 23, in <module> with open(config_file) as f: IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 13:43:21.323364168 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-05-07 13:43:21.841745413 ************************************************************* 2023-05-07 13:43:21.841749020 ************************************************************* 2023-05-07 13:43:21.841750573 *** Your config file is not valid! *** 2023-05-07 13:43:21.841752110 *** Please check the docs at *** 2023-05-07 13:43:21.841753273 *** https://docs.frigate.video/configuration/index *** 2023-05-07 13:43:21.841754729 ************************************************************* 2023-05-07 13:43:21.841755781 ************************************************************* 2023-05-07 13:43:21.841763459 *** Config Validation Errors *** 2023-05-07 13:43:21.841764598 ************************************************************* 2023-05-07 13:43:21.841765506 [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 13:43:21.842565222 Traceback (most recent call last): 2023-05-07 13:43:21.842567276 File "/opt/frigate/frigate/app.py", line 351, in start 2023-05-07 13:43:21.842568370 self.init_config() 2023-05-07 13:43:21.842569532 File "/opt/frigate/frigate/app.py", line 80, in init_config 2023-05-07 13:43:21.842570616 user_config = FrigateConfig.parse_file(config_file) 2023-05-07 13:43:21.842571677 File "/opt/frigate/frigate/config.py", line 1064, in parse_file 2023-05-07 13:43:21.842572588 with open(config_file) as f: 2023-05-07 13:43:21.842573621 IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 13:43:21.842574440 2023-05-07 13:43:21.842575493 ************************************************************* 2023-05-07 13:43:21.842576482 *** End Config Validation Errors *** 2023-05-07 13:43:21.842577477 ************************************************************* 2023-05-07 13:43:21.842645337 [2023-05-07 13:43:21] frigate.app INFO : Starting Frigate (0.12.0-da3e197) 2023-05-07 13:43:22.326572470 [INFO] Preparing go2rtc config... Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 23, in <module> with open(config_file) as f: IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 13:43:22.445020382 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-05-07 13:43:22.932425363 [INFO] Service Frigate exited with code 1 (by signal 0) 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-07 13:43:22.937461001 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) s6-rc: info: service go2rtc-healthcheck successfully stopped 2023-05-07 13:43:23.051822574 [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 s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service frigate-log successfully stopped 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
Das deutet meiner Meinung nach darauf hin, das er das config.File nicht findet.
Da muss ich nochmal Hausaufgaben machen, wieso das so ist. -
@radi sagte in Proxmox LXC mit Frigate:
Ja, man kann da, zumindest bei mir, aus drei verschiedenen Versionen Ubuntu oder eben Debian auswählen.
Ok, ist ja auch schon 4 Wochen her.
Logfiles sind was für Memmen.@exitus ,
der erste Teil der FileUrl ist der Pfad der config.yml im LXC und der zweite im Docker Container der immer gleich bleibt.
Und nutze erst die minimal Config, ich habe Tage für die endgültige config.yml gebraucht. -
-
@exitus Wie ich oben ergänzt habe, habe ich das gerade gefunden. Ich habe es inzwischen mit allen Ubuntu-Versionen wie auch mit Debian über das TTeck Script probiert und war nicht in der Lage eine lauffähige Installation hinzubekommen.
Ich bin mir sicher, ich mache da etwas Grundsätzliches, das für Containernutzer selbstverständlich ist, falsch. Leider bin ich noch nicht dahinter gekommen, was das ist.Die Odnerstruktur ist allerdings so, wie ich das erwarten würde:
[Link Text]( Link Adresse)
-
@radi ,
eben getestet.docker logs -f frigate
auf dem LXC oder normalen Installation zeigt den log an
-
@wal Dankeschön, ich schau mal, ob noch etwas mehr drin steht.
-
@Wal Da steht letztenendes dasselbe wie im Portainerlogfile drin. Ursächlich scheint wohl dies zu sein:
2023-05-07 14:44:51.033075103 ************************************************************* 2023-05-07 14:44:51.033078419 ************************************************************* 2023-05-07 14:44:51.033079955 *** Your config file is not valid! *** 2023-05-07 14:44:51.033081414 *** Please check the docs at *** 2023-05-07 14:44:51.033082613 *** https://docs.frigate.video/configuration/index *** 2023-05-07 14:44:51.033083997 ************************************************************* 2023-05-07 14:44:51.033085013 ************************************************************* 2023-05-07 14:44:51.033092726 *** Config Validation Errors *** 2023-05-07 14:44:51.033093828 ************************************************************* 2023-05-07 14:44:51.033094705 [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 14:44:51.033656750 Traceback (most recent call last): 2023-05-07 14:44:51.033658821 File "/opt/frigate/frigate/app.py", line 351, in start 2023-05-07 14:44:51.033659876 self.init_config() 2023-05-07 14:44:51.033660984 File "/opt/frigate/frigate/app.py", line 80, in init_config 2023-05-07 14:44:51.033661995 user_config = FrigateConfig.parse_file(config_file) 2023-05-07 14:44:51.033662995 File "/opt/frigate/frigate/config.py", line 1064, in parse_file 2023-05-07 14:44:51.033663850 with open(config_file) as f: 2023-05-07 14:44:51.033664794 IsADirectoryError: [Errno 21] Is a directory: '/config/config.yml' 2023-05-07 14:44:51.033665538 2023-05-07 14:44:51.033666509 ************************************************************* 2023-05-07 14:44:51.033667457 *** End Config Validation Errors *** 2023-05-07 14:44:51.033668354 **********************************************************
Nur weiß ich nicht, wie man diesen "IsADirectoryError" korrigiert. Findet Frigate in dem angegebenen Pfad nichts? Oder hat dies eine andere Ursache? Den Screenshot aus dem Filezilla habe ich ja schon weiter oben gepostet. Mit meinem bescheidenen oder nicht vorhandenen Wissen würde ich annehmen, dass der Pfad zur config.yaml so passt.
-
@radi ,
wie erstellst du die config.yml ? mit nano ? -
@radi ,
mach mal im Container diesen Befehl:cat /config/config.yml
-
@wal sagte in Proxmox LXC mit Frigate:
cat /config/config.yml
Hallo Walter,
das ganze verwirrt mich jetzt etwas. Die Ausgabe ist:
cat: /config/config.yml: No such file or directory
will ich das Verzeichnis erzeugen, kommt das:
mkdir config mkdir: cannot create directory 'config': File exists
Will ich mit nano eine neue config erzeugen kommt:
GNU nano 6.4 /config/config.yml [ Directory '/config' does not exist ] ^G Help ^O Write Out ^W Where Is ^K Cut ^T Execute ^C Location ^X Exit ^R Read File ^\ Replace ^U Paste ^J Justify ^/ Go To Line
Wechsel ich dann zu Fuß in das Verzeichnis config und gebe dann deinen cat-Befehl angepasst ein kommt das:
~/config# cat config.yml detectors: cpu1: type: cpu mqtt: host: 192.168.69.159 user: user password: xxx cameras: back: ffmpeg: hwaccel_args: preset-vaapi inputs: - path: rtsp:/XXX:xxx@192.168.69.162:554/h264Preview_01_sub roles: - detect - path: rtsp://XXX.xxx@192.168.69.162:554/h264Preview_01_main roles: - record detect: width: 640 height: 360 mqtt: enabled: False objects: track: - person - car - truck - bicycle - motorcycle - dog - cat snapshots: enabled: True timestamp: False bounding_box: False crop: False height: 175 required_zones: [] retain: default: 10 objects: person: 15 record: enabled: True retain: days: 7 mode: motion events: retain: default: 14 mode: active_objects objects: person: 14 dog: 2 car: 7
-
@radi ,
du musst da aufpassen.
Im Docker-Container muss man diese Datei nicht erzeugen, die zeigt nur auf die Datei im LXC.- /home/frigate/frigate/config.yml:/config/config.yml
also die Datei im LXC "/home/frigate/frigate/config.yml" wird im Docker auf "/config/config.yml" gemappt.
das geht automatisch. Du musst nur die Datei wie hier im LXC "/home/frigate/frigate/config.yml" oder wie in deiner Docker-Config angegeben erzeugen.edit: oder mappst du die Datei in der Docker-Config gar nicht auf "/config/config.yml"
editedit: der Docker Container ist fertig eingerichtet, da muss nichts verändert werden. -
danke euch allen
mit viel grübeln habe ich frigate am laufen aber nur minimal.
habe ein camera eingebunden mit minimal config rest mache ich weiter wenn mein tpu da ist. -
ich habe kamera eingebunden habe aber ein greenscreen nur
woran kann es liegen???
erledigt -
Hallo was ist an diesem config falsch
detectors: cpu1: type: cpu database: path: /db/frigate.db mqtt: host: 172.16.0.10 port: 1689 user: admin password: passwort cameras: Parkplatz: ffmpeg: output_args: record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -st> rtmp: -c:v copy -c:a aac -f flv inputs: - path: rtsp://admin:passwort@172.16.0.147:554/Streaming/Channels/102/?trans> roles: - detect - path: rtsp://admin:passwort1@172.16.0.147:554/Streaming/Channels/101?tr> roles: - record rtmp: enabled: False detect: width: 640 height: 480 objects: track: - person - car - dog snapshots: enabled: true timestamp: true bounding_box: true retain: default: 2 record: enabled: true retain: days: 10
was sind das für errors
[2023-05-10 06:39:21] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:39:21] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:39:24] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:39:24] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:39:31] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:39:31] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:39:31] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x5613b818fec0] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:39:31] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:39:31] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:39:31] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:39:35] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:39:35] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:39:41] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:39:41] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:39:41] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x565490d5b080] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:39:41] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:39:41] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:39:41] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:39:45] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:39:45] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:39:46] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:51710] [2023-05-10 06:39:51] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:39:51] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:39:51] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x55d19e0b4f40] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:39:51] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:39:51] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:39:51] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:39:55] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:39:55] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:40:01] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:40:01] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:40:01] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x55c154580500] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:40:01] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:40:01] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:40:01] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:40:04] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:40:04] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:40:11] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:40:11] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:40:11] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x561611bada80] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:40:11] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:40:11] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:40:11] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:40:14] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:40:14] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:40:21] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:40:21] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:40:21] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x55cdb7c11380] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:40:21] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:40:21] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:40:21] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:40:25] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:40:25] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:40:31] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:40:31] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:40:31] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x555cad1cc4c0] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:40:31] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:40:31] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:40:31] ffmpeg.Parkplatz.detect ERROR : [2023-05-10 06:40:35] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:40:35] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:40:41] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:40:41] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:40:41] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x55c7da0535c0] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:40:41] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:40:41] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:40:41] ffmpeg.Parkplatz.detect ERROR : [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] done. [services.d] starting services [services.d] done. [2023-05-10 06:40:49] frigate.app INFO : Starting Frigate (0.11.1-2eada21) Starting migrations [2023-05-10 06:40:49] peewee_migrate INFO : Starting migrations There is nothing to migrate [2023-05-10 06:40:49] peewee_migrate INFO : There is nothing to migrate [2023-05-10 06:40:49] detector.cpu1 INFO : Starting detection process: 216 [2023-05-10 06:40:49] frigate.app INFO : Output process started: 218 [2023-05-10 06:40:49] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2023-05-10 06:40:49] ws4py INFO : Using epoll [2023-05-10 06:40:49] frigate.app INFO : Camera processor started for Parkplatz: 222 [2023-05-10 06:40:49] frigate.app INFO : Capture process started for Parkplatz: 224 [2023-05-10 06:40:49] ws4py INFO : Using epoll [2023-05-10 06:40:53] frigate.video ERROR : Parkplatz: Unable to read frames from ffmpeg process. [2023-05-10 06:40:53] frigate.video ERROR : Parkplatz: ffmpeg process is not running. exiting capture thread... [2023-05-10 06:41:09] watchdog.Parkplatz ERROR : Ffmpeg process crashed unexpectedly for Parkplatz. [2023-05-10 06:41:09] watchdog.Parkplatz ERROR : The following ffmpeg logs include the last 100 lines prior to exit. [2023-05-10 06:41:09] ffmpeg.Parkplatz.detect ERROR : [hevc_mp4toannexb @ 0x5621d50b8800] Codec 'h264' (27) is not supported by the bitstream filter 'hevc_mp4toannexb'. Supported codecs are: hevc (173) [2023-05-10 06:41:09] ffmpeg.Parkplatz.detect ERROR : Error initializing bitstream filter: hevc_mp4toannexb [2023-05-10 06:41:09] ffmpeg.Parkplatz.detect ERROR : Error initializing output stream 0:0 -- [2023-05-10 06:41:09] ffmpeg.Parkplatz.detect ERROR :
snapshot bewegung wird erkannt aber ich habe keine aufnahmen oder clips
-
@exitus sagte in Proxmox LXC mit Frigate:
output_args:
record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -st>
rtmp: -c:v copy -c:a aac -f flvWas möchtest du damit erreichen ?
Wenn du was transcodieren möchtest nimmt man in frigate 0.12.0 go2rtc das ist mit dabei.