DrSpaldo Posted October 31, 2023 Author Share Posted October 31, 2023 1 hour ago, bucketphobia said: Hey @DrSpaldo, I was having a very similar issue, but slightly different - the cause of mine was a dockerd log process. The solution to mine was to ensure that "Permit exclusive shares" is on, and that "Exclusive Access" is indeed active on my cache pool. Hope this helps. Thanks @bucketphobia, I will also turn that on. Fortunately mine has died down heaps since I made the above other changes, but who knows what the actual root cause is. Seems to be so many people in similar (but not exactly) the same situation Quote Link to comment
DrSpaldo Posted October 31, 2023 Author Share Posted October 31, 2023 @bucketphobiaI've turned on the permit exclusing shares, however, I don't see how to turn on the exclusive access part anywhere. Although, I do remember that I did change the default for my dockers to point directly to the drive and not use fuse... /mnt/cachetwo/appdata/opera rather than /mnt/user/appdata/opera Quote Link to comment
itimpi Posted October 31, 2023 Share Posted October 31, 2023 1 hour ago, DrSpaldo said: @bucketphobiaI've turned on the permit exclusing shares, however, I don't see how to turn on the exclusive access part anywhere. Although, I do remember that I did change the default for my dockers to point directly to the drive and not use fuse... /mnt/cachetwo/appdata/opera rather than /mnt/user/appdata/opera Once you have enabled the global option it should be automatic if a share is set up to have all its files to be on a single pool/drive and that is how they are actually currently placed If it is not enabling then you have probably not met that criteria. Quote Link to comment
bucketphobia Posted November 1, 2023 Share Posted November 1, 2023 10 hours ago, DrSpaldo said: @bucketphobiaI've turned on the permit exclusing shares, however, I don't see how to turn on the exclusive access part anywhere. Although, I do remember that I did change the default for my dockers to point directly to the drive and not use fuse... /mnt/cachetwo/appdata/opera rather than /mnt/user/appdata/opera If it says no - you likely need to (1): disable secondary storage; (2): make sure that nothing on the share is on other drives Quote Link to comment
DrSpaldo Posted November 1, 2023 Author Share Posted November 1, 2023 No worries, thanks @bucketphobia@itimpi Quote Link to comment
MrK Posted November 5, 2023 Share Posted November 5, 2023 Do you think the issues have gone after removing frigate from the server? When playing about with frigate (2 cams go2rtc streams and HW encoding enabled intel with coral). Only seems to happen when I am messing about with settings trying to get go2rtc in to home assistant etc. Nov 5 13:00:58 Tower kernel: ffmpeg invoked oom-killer: gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), order=0, oom_score_adj=0 Nov 5 13:00:58 Tower kernel: CPU: 3 PID: 7505 Comm: ffmpeg Tainted: P O 6.1.49-Unraid #1 It says invoking oom-killer but I guess it doesn't work? It makes the server unreachable. I have to power cycle it. I have added the "--memory=3G" line to the frigate docker and installed the swap file plugin. Quote Link to comment
DrSpaldo Posted November 6, 2023 Author Share Posted November 6, 2023 (edited) 4 hours ago, MrK said: Do you think the issues have gone after removing frigate from the server? When playing about with frigate (2 cams go2rtc streams and HW encoding enabled intel with coral). Only seems to happen when I am messing about with settings trying to get go2rtc in to home assistant etc. Nov 5 13:00:58 Tower kernel: ffmpeg invoked oom-killer: gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), order=0, oom_score_adj=0 Nov 5 13:00:58 Tower kernel: CPU: 3 PID: 7505 Comm: ffmpeg Tainted: P O 6.1.49-Unraid #1 It says invoking oom-killer but I guess it doesn't work? It makes the server unreachable. I have to power cycle it. I have added the "--memory=3G" line to the frigate docker and installed the swap file plugin. Hi @MrK, yes, I do think that was either the primary cause or a big part of it. Although I have no concrete proof. I know originally when I was deep into the issue, I found out that the --memory line doesn't always work with Unraid. I did a quick search earlier and didn't find the exact post where I remember seeing it though... Here are a few to look through that may help - Unraid OOM Issues · blakeblackshear/frigate Edit: check this post to see if you are using the fuse file system for your Unraid Frigate container - FUSE post - Frigate Github Edited November 6, 2023 by DrSpaldo 1 Quote Link to comment
DrSpaldo Posted June 15 Author Share Posted June 15 For those that also may come and find this thread. I have just upgraded a friends server from 6.9.2 to 6.12.10 and now having crashing issues. It is lasting max of 1 day then the server goes totally unresponsive, even on SSH. It does ping back though. At this stage, I am trying all the suggestions above, however, I cannot take Frigate off this server. So it will be interesting to find out if there is a way to keep Unraid running with Frigate as well. I try to keep updating this thread with the outcome/progress Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.