On 12/28/2025 at 5:48 AM, Naticus said:

This is probably because your buffer directory has millions of files in it. I have so many right now that it won't even list the files so I'm purging the directory beyond 14 days of modified time and then will restart the container. Obviously double-check this and fix the path before just blindly running. There were issues reported on the git repo back in October that have since been closed out and Josh5 has added a buffer retention setting. From what others had said, unmanic was maybe making files every few seconds for months.

find /mnt/user/appdata/unmanic/.unmanic/logs/buffer -type f -mtime +14 -exec rm {} \;

Edit: lol so I'm waiting for this to complete the removal and I realized I had done an ls -l in the logs directory before I started. I have 170 MILLION hardlinks on the buffer directory. Yeah, this would explain why it took like 45 min to start unmanic and have a working webui.

So you are suggesting to copy/paste that above command into the terminal of UnRaid or, the terminal of the container?

I've manually opened the .unamanic/logs/buffer directory and I have files in there from 2025.....

So I went and copy/paste your above command into a terminal window in UnRaid and hit enter. It's been about 30 minutes now. I can no longer access any of my UnRaid shares over the network, it just "times out". I still have access to the UnRaid webgui though. So perhaps it's due to this command running causing it to time out over the network. However, this is making me very nervous LOL

I've gone from waiting for 10-15 minutes for this container to start up to, now, hours of waiting for the container /WebGUI to start.

Edited January 30Jan 30 by CoZ

So I let that command / open terminal window sit there for 2 hours or so. Nothing happened at all. All those log files are still in that directory.

I had a few movies transcode to H265. I noticed that when the transcoding runs, the CPU cores are maxed out but nothing is happening on the GPU side (even though I can see unmanic loaded into the GPU).

I did set the --runtime=nvidia and the correct UUID. In the plugin for transcoding, it does see the GPU. But it doesn't seem to use the GPU.
How can I fix this?
Also I noticed the transcoded quality isn't great.

GPU is a GTX1080 8GB

Under global plugin settings:

Standard config mode
max input stream buffer 2040
video codec - HEVC/H265
force transcoding checked
NVENC-hevc_nvenc
The nvidia device selected
HW decoding - NVDEC/CUDA - use GPU hardware
Quality - P5
Tune - HQ
Profile - Auto
Encoder ratecontrol - Auto
keep same container checked

9 hours ago, plunderisley said:

I had a few movies transcode to H265. I noticed that when the transcoding runs, the CPU cores are maxed out but nothing is happening on the GPU side (even though I can see unmanic loaded into the GPU).

I did set the --runtime=nvidia and the correct UUID. In the plugin for transcoding, it does see the GPU. But it doesn't seem to use the GPU.
How can I fix this?
Also I noticed the transcoded quality isn't great.

GPU is a GTX1080 8GB

Under global plugin settings:

Standard config mode
max input stream buffer 2040
video codec - HEVC/H265
force transcoding checked
NVENC-hevc_nvenc
The nvidia device selected
HW decoding - NVDEC/CUDA - use GPU hardware
Quality - P5
Tune - HQ
Profile - Auto
Encoder ratecontrol - Auto
keep same container checked

Audio? I’ve had transcoding audio max out my threadripper cores.

Are you sure the video portion isn’t being skipped because of other reasons and it’s only doing audio? (Ex. File is already 265, etc.)

4 minutes ago, Conson Droppa said:

Audio? I’ve had transcoding audio max out my threadripper cores.

Are you sure the video portion isn’t being skipped because of other reasons and it’s only doing audio? (Ex. File is already 265, etc.)

hmm not sure. How can I check if its the audio?

It shouldnt be skipped as I marked it to transcode even if same format.

1 minute ago, plunderisley said:

hmm not sure. How can I check if its the audio?

It shouldnt be skipped as I marked it to transcode even if same format.

I’m in between a user and a power user and I say this to not be funny.

I open Dozzle and watch the live log of unManic. I squint and read what’s happening. (I suck at reading logs). I google some things that don’t make since or are not verbatim English. Usually gives me a direction to go in.

Hopefully someone who is better at this can chime in. Maybe post your log to your last or next comment and I’m sure someone can offer more.

On 2/2/2026 at 3:08 PM, CoZ said:

So I let that command / open terminal window sit there for 2 hours or so. Nothing happened at all. All those log files are still in that directory.

You should try going to the "Help & Suport" page from the main Unmanic container page. Once there look for "Logs" and click the "Log Buffer Retention" dropdown. Choose a short interval and make sure that "Enable Debugging" is turned off.

Restart the container - this will take a LONG time as the ungodly number of files are being deleted. Once the container has restarted you should be back to a much more resonable "restart" time. On my server the container GUI now starts up in a few seconds.

Hope this helps. . .

On 2/4/2026 at 3:54 PM, Gandalf1369 said:

You should try going to the "Help & Suport" page from the main Unmanic container page. Once there look for "Logs" and click the "Log Buffer Retention" dropdown. Choose a short interval and make sure that "Enable Debugging" is turned off.

Restart the container - this will take a LONG time as the ungodly number of files are being deleted. Once the container has restarted you should be back to a much more resonable "restart" time. On my server the container GUI now starts up in a few seconds.

Hope this helps. . .

Thank you friend. I've done what you've suggested. It seems to have improved the start-up time after an update, etc and the /logs directory now contains only a few instead of hundreds of thousands of entries

Has anyone else's umask setting stopped working. i have umask set to 000 and have tried others but no matter what all output files are set to read only except for nobody user.