Expanding Transcoding-Temp Directory

[ShadowKindjal 21]

One of the issues I have been having for a while is that my transcoding-temp directory seems to grow in size all the time. Every now and then (and it seems to be happening more frequently now) I have to delete the directory and restart my server before it expands to use the entire capacity of my SSD. Today, for example, before I deleted the folder it had expanded to over 60 GB in size. I don't believe it's a permissions issue either. It seems transcoding files aren't being deleted from the emby directory for some reason. This is an ongoing issue I've had for more than a year now.

 

 

[ShadowKindjal 21]

This is a quick example about five minutes after I've restarted my server. Al of the 9ED74B ts files are from the following transcode which has already been closed for over a minute now yet they still reside in the directory. I've attached the ffmpeg for reference.

 

ffmpeg-remux-f9a7af66-e1a1-4388-bc54-2d9346a34eb6_1.txt

[rrado 0]

You seem to have the same issue as what I got ? 

https://emby.media/community/index.php?/topic/84229-transcoding-temp-full-and-does-not-empty/

 

From my side, restarting emby server did flush these transcoding files.

But that is just a work around, and it would be better if real cause of this issue could be found...

[ShadowKindjal 21]

You seem to have the same issue as what I got ? 

https://emby.media/community/index.php?/topic/84229-transcoding-temp-full-and-does-not-empty/

 

From my side, restarting emby server did flush these transcoding files.

But that is just a work around, and it would be better if real cause of this issue could be found...

 

Yea, it seems to be a similar issue. I have to constantly monitor the space available on my drive otherwise the system will hang after running out of space. Depending on how long an update may take I'm considering buying a secondary SSD just for my transcode files to reside.

[ShadowKindjal 21]

Does anyone have any information on this?

[Happy2Play 9780]

If items are not being cleaned up after a proper stop from client/app, I believe the devs will need the server log and possibly the corresponding ffmpeg log with time of playback stop.

 

Unless this is a specific OS issue, I have never seen leftover media in my Transcode-Temp folder on Windows.  But I only use web client and Roku.

[Luke 42078]

This is a quick example about five minutes after I've restarted my server. Al of the 9ED74B ts files are from the following transcode which has already been closed for over a minute now yet they still reside in the directory. I've attached the ffmpeg for reference.

 

Annotation 2020-04-07 090348.png

How did you stop playback?

[ShadowKindjal 21]

How did you stop playback?

I believe, in this case, playback was stopped by hitting the back button in the web player.

Edited April 13, 2020 by ShadowKindjal

[ShadowKindjal 21]

If items are not being cleaned up after a proper stop from client/app, I believe the devs will need the server log and possibly the corresponding ffmpeg log with time of playback stop.

 

Unless this is a specific OS issue, I have never seen leftover media in my Transcode-Temp folder on Windows.  But I only use web client and Roku.

I posted the corresponding ffmpeg log but I will grab the server for you guys as well

[Luke 42078]

Thanks !

[ShadowKindjal 21]

I unfortunately wasn't able to grab the log from that period of time but I was able to pull the log from yesterday's streams. Would this suffice or would you need me to find another corresponding ffmpeg stream that hasn't deleted files from the transcoding directory?

embyserver-63722332800.txt

[Luke 42078]

It would be ideal to have all of the following for one single example:

• server log
• ffmpeg log
• description of how playback was stopped

Thanks.

[ShadowKindjal 21]

I believe I may have figured out the issue I was having. The temporary transcoding path I had set up didn't exist so I believe the server was using the default directory to create the transcode files but attempting to delete them from the non-existent directory and correcting this setting seems to solve my issue. I tested this solution with the default directory and another valid directory but this time it deletes the transcoding files after playback stops. 

[Luke 42078]

We'll take a look at that. thanks for the feedback.