Hi guys,

 

My server just started throwing the Out of Memory error through the Fix Common Problems plugin.

 

Could somebody look at my diagnostics and suggest what might be the culprit?

 

Thanks

bigdaddy-diagnostics-20241119-1522.zip

5 hours ago, randommonth said:

Could somebody look at my diagnostics and suggest what might be the culprit?

 

Happened on the 17th and looks like it stopped your VM, may have been frigate that ran it OOM - you'll need to reboot to clear the log so FCP stops warning you. If it happens again, check the configs for your containers so they're not writing to RAM

21 hours ago, Michael_P said:

 

Happened on the 17th and looks like it stopped your VM, may have been frigate that ran it OOM - you'll need to reboot to clear the log so FCP stops warning you. If it happens again, check the configs for your containers so they're not writing to RAM

 

Thanks, I've reset the server but not sure on whether the Frigate container is writing to RAM.

 

The "Cache to RAM" setting is set to "/tmp/frigate"

 

1 hour ago, randommonth said:

The "Cache to RAM" setting is set to "/tmp/frigate"

 

If you don't have that mapped to a disk, it's writing to RAM.

On 11/20/2024 at 8:53 PM, Michael_P said:

 

If you don't have that mapped to a disk, it's writing to RAM.

Thanks - so all I have to do is just map a disk location to this setting?

 

Do I have to change any other settings within the Frigate docker, such as those described at the following thread? 

 

 

10 hours ago, randommonth said:

Thanks - so all I have to do is just map a disk location to this setting?

 

Do I have to change any other settings within the Frigate docker, such as those described at the following thread?

 

Dunno, I don't use Frigate. Worth a shot, tho - and if it doesn't work just map whatever the cache location it has in its settings to a disk.

I mapped the cache location for the Frigate docker to a location on my SSD cache (per above suggestion), but I'm still getting out of memory errors.

 

Could anyone inspect my diagnostics and gimme a hint as to what's going on?

 

Thanks

 

 

bigdaddy-diagnostics-20241213-1613.zip

5 hours ago, randommonth said:

nd gimme a hint as to what's going on?

 

Looks like this time you were converting movies, which were going to RAM during the process

Thanks for your response.

 

That's odd as I have my Unmanic cache location set to my Unraid cache SSD, not RAM.

12 hours ago, randommonth said:

Thanks for your response.

 

That's odd as I have my Unmanic cache location set to my Unraid cache SSD, not RAM.

 

Never used it so wouldn't be able to tell you how to configure it to disk, but here's where it was doing its work. It could still be frigate, but I see this in the log so it looks like the conversions were done in RAM

 

/tmp/unmanic/unmanic_file_conversion-ungnp-1733949847/Yesterday (2019) 1080p.BluRay.1400MB.DD5.1.x264-GalaxyRG-ungnp-1733949847-WORKING-3-1.mkv

/tmp/unmanic/unmanic_file_conversion-gogqt-1733949847/X-Men Apocalypse 2016 1080p BluRay x264 DTS-JYK-gogqt-1733949847-WORKING-3-1.mkv

/tmp/unmanic/unmanic_file_conversion-tflpx-1733949847/X-Men.The.Last.Stand.2006.720p.BrRip.x264.YIFY-tflpx-1733949847-WORKING-3-1.mp4

/tmp/unmanic/unmanic_file_conversion-bjlas-1733949847/X-Men (2000)-bjlas-1733949847-WORKING-3-1.mp4

 

Edited December 14, 20241 yr by Michael_P

1 minute ago, Michael_P said:

 

Never used it so wouldn't be able to tell you how to configure it to disk, but here's where it was doing its work (tmp is in RAM unless mapped)

 

/tmp/unmanic/unmanic_file_conversion-ungnp-1733949847/Yesterday (2019) 1080p.BluRay.1400MB.DD5.1.x264-GalaxyRG-ungnp-1733949847-WORKING-3-1.mkv

/tmp/unmanic/unmanic_file_conversion-gogqt-1733949847/X-Men Apocalypse 2016 1080p BluRay x264 DTS-JYK-gogqt-1733949847-WORKING-3-1.mkv

/tmp/unmanic/unmanic_file_conversion-tflpx-1733949847/X-Men.The.Last.Stand.2006.720p.BrRip.x264.YIFY-tflpx-1733949847-WORKING-3-1.mp4

/tmp/unmanic/unmanic_file_conversion-bjlas-1733949847/X-Men (2000)-bjlas-1733949847-WORKING-3-1.mp4

 

In which case that is strange as the screenshot of the docker setting show that /tmp/unmanic IS mapped to a location on the cache.

 

1 minute ago, itimpi said:

In which case that is strange as the screenshot of the docker setting show that /tmp/unmanic IS mapped to a location on the cache.

 

Could still be frigate, since its doing ffmpeg work in RAM too - but since there was only one stream going, I'd still point to the mapped location being wrong