NewDisplayName

Maybe all of those users have corrupt ram, which never gave any problems < 6.12 or what?

And again posted over 10 days ago, no response. Thats a stable release. They could have changed it to beta as they noticed ppl having problems months ago, but no, every day new users update and have to face this issues. I DONT GET IT.

https://www.google.com/search?q=tmpfs+2gb

Someone know if night detection is working somehow? Ive googled abit around and it just seems to be old posts...? My cam has night vision...

look for the only tmpfs command in this docker and change it accordingly

Sorry, then i didnt see it. (probbaly because you ahve to scroll, cant you add that to the "overview"?) Heres my config like i said, if i were you, couldnt you provide a "standard" config with the installer? And or post these config on your first forum thread? So people can learn from it themselfs? Installation: 1.) Choose the template with Nvidia 2.) add --runtime=nvidia to extra parameter 3.) move this config.yml to your config directory 4.) change pw user port and url to your camera 5.) run this command (inside the trt directory) in shell: If u get errors about 16 bit something then run this command instead (or just run it again, if the above fails) config.yml

Im good, thanks to your starting help i was able to figure it out, even got detection working and recording... not sure about the retention but ill see how it goes and change it like i need to. Something very important was missing tho, ive selected frigate and nvidia docker, but it was missing --runtime=nvidia, which should be set, when you selecting the docker with the nvidia. But im not sure if you can change that in the template, but atleast i would add it somewhere in help so others dont have problems with it. Later ill post my config for others to use.

thats the only thread i found about this issue. Im not running it directly on unraid, im just using containers which uses ffmpeg, but still iget those errors. Aug 13 16:10:36 Unraid-Server kernel: ffmpeg[27483]: segfault at 0 ip 000014815cbdabee sp 00007fffbb727028 error 4 in libc-2.31.so[14815ca79000+178000] Aug 13 16:10:36 Unraid-Server kernel: Code: 0f 84 fd fe ff ff e9 21 7e f3 ff 90 f3 0f 1e fa 89 f8 31 d2 c5 c5 ef ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 52 03 00 00 <c5> fe 6f 0f c5 f5 74 06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 It doesnt seem to make a big problem, but i wonder whatst he problem is?

I know! Im not talking to you, just getting it off my mind, because i cant understand such devs. It still doesnt want to startup... I dont get it. Just to be sure, my TRT folder is empty, is that normal? My file is called config.yml, is that right? -08-13 12:27:27.525611633 ************************************************************* 2023-08-13 12:27:27.525722961 *** Your config file is not valid! *** -snip- I fixed it... There were 2 empty spaces missing infront of "back". This whole configuration marathon is unbelievable (useless) complicated. Im currently tryin to get my NVIDIA in it, lets see how that goes.

I found that straight forward because you explizit wrote "REMOVE THIS IF NOT NEEDED". Was clear to me, even as non english speaker. Its directly copied from the original config, and only edited with notepad++ who ever thought that padding would be a good idea........... And still, even with your config, errors... 2023-08-10 19:45:10.035521192 1 validation error for FrigateConfig 2023-08-10 19:45:10.035523378 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.035843523 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037033664 Traceback (most recent call last): 2023-08-10 19:45:10.037036489 File "/opt/frigate/frigate/app.py", line 351, in start 2023-08-10 19:45:10.037038031 self.init_config() 2023-08-10 19:45:10.037041198 File "/opt/frigate/frigate/app.py", line 80, in init_config 2023-08-10 19:45:10.037043098 user_config = FrigateConfig.parse_file(config_file) 2023-08-10 19:45:10.037044866 File "/opt/frigate/frigate/config.py", line 1078, in parse_file 2023-08-10 19:45:10.037057005 return cls.parse_obj(config) 2023-08-10 19:45:10.037058333 File "pydantic/main.py", line 526, in pydantic.main.BaseModel.parse_obj 2023-08-10 19:45:10.037060270 File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__ 2023-08-10 19:45:10.037062454 pydantic.error_wrappers.ValidationError: 1 validation error for FrigateConfig 2023-08-10 19:45:10.037063890 cameras -> back -> ffmpeg -> roles 2023-08-10 19:45:10.037065265 extra fields not permitted (type=value_error.extra) 2023-08-10 19:45:10.037902506 2023-08-10 19:45:10.038198131 ************************************************************* 2023-08-10 19:45:10.038475954 *** End Config Validation Errors *** I have no problem googling problems and searching for myself, but oh god why he not just create a standard config, whcih you can fill via GUI... i even googled "extra fields not permitted" but no usefull results...

Hmm, im a bit lost. I saw the standard guide, but this doenst really apply to unraid?! Isnt there a guide for unraid + frigate? Do i need to install mqtt? Why isnt that included in the docker? I just want to have one camera rtsp which should only record when moving. I tried this: mqtt: enabled: false cameras: back: ffmpeg: inputs: - path: rtsp://XXX:[email protected]:1338/11/ roles: - detect detect: width: 1280 height: 720 and it keeps constant crashing 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 39, in get_single_node 2023-08-09 20:51:31.897105168 [INFO] Starting NGINX... if not self.check_event(StreamEndEvent): 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 171, in parse_document_start raise ParserError(None, None, yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>' in "<unicode string>", line 3, column 1: cameras: ^ It sounds like "cameras" is the problem, but thats literally the first example for a config file on their page...?

holy hell are you a graveyard keeper?

Hey, ive read here: https://docs.ombi.app/guides/migrating-databases/#3-create-and-prepare-tables that they now can use mysql and they say it has better performance, could the docker be updated to make use of it?

I don't even have the nerve anymore to talk about this whole ... Youre right lim answered, but literally NOTHING about my problem, we just chatted about the "why unraid has wrong ip" thing. This answer, came how many days after i posted this and direct sent it to you via feedback? As long as unraid is working as expected all is good, but if not, your on your own, even if you provide all details and do what asked. And that is a fact. If you would use as much time on threads or reviewing/answering emails you use to defend yourself (or attack me), then we wouldnt have this problem. AND STILL no one answered if this problem is now fixed or not, its like im talking to a wall. I dont understand it. Maybe you should use a ticket system or something. I see everyday the same problems with unraid since 6.12 popping up in facebook or here in the forums and it doesnt seem like you guys want to fix it (or see the problem)... and if these problems are still there, your still saying 6.12 is a major release, update. -Freezing (even with ipvlan) -"no internet" (some DNS issue)

Also ich bin echt lange bei Unraid dabei, fast 10 Jahre? man muss halt ehrlich sagen das es sehr billig ist, dafür das es bezahlt ist, dann relativiert sich das wieder. Normalerweiße funktionieren die Stable perfekt, allerdings habe ich in meiner laufbahn 2 erlebt wo es nicht so war (eine davon jetzt 6.12), selbst die betas funktionieren normalerweise wunderbar. Das gute ist halt du kannst einfach zurück wechseln...

Er kann doch nachfragen, heißt aber nicht das ich mich geirrt habe oder was durcheinander werfe. Wenn man "der pihole ist im router und verteilt die dann per dhcp an die clients" liest, dann sollte man wissen was damit gemeitn ist, da fehlt im endeffekt im router "eingetragen". Ergibt sich aber durch den rest des Satzes.

der pihole ist im router und verteilt die dann per dhcp an die clients,

Ich werf da gar nichts durcheinander. was im router eingetragen ist, wird ignoriert wenn im unraid ein anderer DNS eingetragen ist. Du brauchst auch nicht rätseln ob es im dhcp eingetragen ist, da ich genau das geschrieben habe und damit eindeutig klar war, was ich sagte.

Ja ich habe nicht nur einen thread eröffnet ich habe sogar direkt nach dem release den link zum thread und der beschreibung direkt an die devs geschickt

Ich versteh dein Problem gar nicht. Vielleicht kannst du es mal zusammenfassen, übrigens hab ich mittlerweile genug und bin zurück zu 6.11, damit gibts monaten keine Probleme mit irgendwas.

man man man man man "Dein Router sagtest du ist eine Fritzbox?" ja. "Pihole ist im Router?" Ja, ist im Router EINGETRAGEN "also in der Fritzbox?" siehe oben

Versteh nicht was du da nicht verstehst, der pihole ist im router und verteilt die dann per dhcp an die clients, unraid hat einen anderen dns server eingetragen, nutzt also diesen...

I did rollback. They label it as mayjor release, not beta, while so much is broken, cant understand. And not a single answer from dev if they work on it or not, some mods even seems to not noticing how many ppl have problems...

I can confirm it doesnt crash anymore, instead if just looses connectifity atleast partly (you always know when "Unraid-Server Unraid API Error CLOUD: Socket closed" shows up on top right) Also logs show Jul 12 19:31:32 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png Jul 12 19:31:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png Jul 12 19:33:49 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png Jul 12 19:34:05 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png Jul 12 19:35:54 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png Jul 12 19:36:10 Unraid-Server root: SabNZBd: Could not download icon https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/sabnzbd-logo.png The best thing is while it cant reach a URL IT WILL LITERALLY FREEZE unraid till it times out... network restart didnt help, i have to restart every time (sometimes once a day, sometimes it works for some days) Still not a answer from devs, sad, they could atleast tell us, they know theres somethign wrong and they work on it, i dont get it. Sometimes some dockers partly still work, like i can reach plex (via internet), but cant play anything.

its unraid bug, it looses connectifity partially or complete after a while with latest updates... Even netowkr restart /etc/rc.d/rc.inetd restart doesnt fix it, i need to restart unraid every time.