Transcoding-Temp Growing alrge enough to kill server (Ran out of disk space...). How to clean?

[douglasg14b 0]

The jist is that my docker host died because it ran out of disk space, upon analysis it turns out that Emby's `transcoding-temp` directory is at 18GB, which ate the remaining space on the server up (Of which I only have 30GB allocated).

 

Is there a way to limit the size of this directory? Why is it not being cleaned? Can I manually clear it out??

 

It's extremely problematic if Emby can, on a whim, kill off all my docker containers because there is no control over a wildly growing temp-file directory :/

 

Edit:

 

From reading other threads, this appears to be related to someone exiting out of an app that's playing a video without stopping it. Which is fairly normal user behavior that is not likely to ever change. For instance, I have family members that watch from a Roku, they just turn it off when done with a video and it's in the credits, which is an entirely anticipated action...

 

Edit2: Just deleted all temp files, can start it now. Running Emby v4.0.2.0

Edited July 20, 2019 by douglasg14b

[Luke 37065]

 

 

Why is it not being cleaned? Can I manually clear it out??

 

Hi there @@douglasg14b, transcoding temp files are cleaned after you stop playing. I would suggest updating to the latest version of Emby Server, which is currently 4.1.1.

 

Please let us know if this helps. Thanks !

[GregMo 21]

Ummm, I'm seeing this problem on the latest version.

Also, I see in Dashboard where it lists this path but where does one go to change the path to a different location?

[UCM_1 10]

I can confirm that this still happens occasionally.  I believe I posted about it some time ago as well.

My solution was just to put Emby on a larger drive -- My system is on a virtual machine, and was originally given just 40GB.  Now it has 135GB.  That appeard to solve my problem for months, but recently it did just ran out of space again.

In watching space usage on the drive, it stays low most of the time.  7GB used (total -- includes operating system and server files) on the drive just after a restart, and typically bounces around in the lower teens after the server is up and running for awhile.  But then, out of the blue, a day will come along and the entire drive gets wiped out until a system reset.

As a previous comment in this thread states, previous posts seem to blame the problem on someone exiting an app while live TV (or similar) is still playing....  But that doesn't appear to always be the case -- and that's a lot of transcoding needed to fill up 120GB of space.  Seems unlikely to be caused by someone leaving the "TV on" while not there, especially with "Are you still watching" prompts that theoretically should shut it down in such a case.

But even if that is the case....  Maybe set some limit to how large the files can be in the temp file folder and automatically clean/trim them if they get to large?

[UCM_1 10]

8 hours ago, GregMo said:

Ummm, I'm seeing this problem on the latest version.

Also, I see in Dashboard where it lists this path but where does one go to change the path to a different location?

Under "Transcoding" there is an option to set the transcoding temporary path.

[GregMo 21]

1 hour ago, UCM_1 said:

But even if that is the case....  Maybe set some limit to how large the files can be in the temp file folder and automatically clean/trim them if they get to large?

 

Agreed. In addition, when the log files roll at midnight it would be nice if clean up of the temp files were done.  Could delete anything over 'x' hours old.

 

For the devs that might be looking into this, I can tell you I don't watch live TV so I know the issue isn't tied to that.