[2.2.1][LINUX] hlsjs-lite:Network error

"transcoding-temp.stf saturates /tmp/serviio"
Hello,

I'm using Serviio 2.2.1 on Debian 11.
When I launch a video with a web browser, ffmpeg saturates /tmp/serviio/transcoding-temp-xxxxxxx.stf very fast with segment00xxx.ts file.
When /tmp volume is full i obtain the error message : hlsjs-lite:Network error

Could you please give me a solution? A tricks or parameter to reduce the saturation to a max level ?

Thank you for your help

Virtua

[atc98092]

It sounds like your /tmp location isn't large enough to store the files while transcoding is performed. You can change the location that Serviio uses to store transcoded files on the Serviio console on the Delivery/Transcoding tab. Create a folder somewhere you have sufficient disc space, and then point Serviio to that location.

Transcoding creates a large number of files, which are purged after the video has been watched. But they can take a significant amount of space.

Hi atc98092,
Thank you for your respond.
you are explaining to me that I have to dedicate a volume 100 or 1000 times bigger than a film itself when there is no such problem with Windows ?
Are you sure there is no other possibility than to dedicate a huge disk space ?
I will explore how many space is necessary

Virtua

Hi,
OK I understand, almost the same space as the size of the movie playing is necessary.
It's OK for me.
Thank you so much for your help.
I changed & choose a space on a remote disk in /mnt/
Virtua

[atc98092]

Yep, you just need a large enough space for the transcoded files. I don't think the space necessary has to be much larger than the original file before transcoding, but don't forget that if Serviio is transcoding two movies at the same time (two different people are watching something on different TVs) you need space for both of them.

Since Linux by default makes a /tmp partition on the hard drive separate from the OS partition, it's absolutely possible that partition isn't large enough for transcoding. Under Windows for example, the entire C: drive partition is used for the OS, personal files, and the temp location. So it's something that isn't likely to happen with Windows. Not a good or bad thing for either OS, just the way they work.