Plex is filling my docker.img

Server Version#: version-1.30.0.6486
Player Version#: Version 4.97.3
Using linuxserver container

Hi there,

So I’m just going to lay it out there since it’s doing my head in and I’ve been on unraid discord support linuxserver support already and now I’m here.

The plex container size yesterday was only 300ish mb and now this morning woke up to my docker.img full at 100% capacity and when I went looking plex had gone up to 50 GB in container size. since then I have found that the /tmp is where the music analyse input is and it seems from what everyone is saying that’s what makes all these big files. The pictures below have my plex unraid configurations and mappings and show that the container is now 50 GB and now I can’t basically do anything on my docker because of plex.

is there a way for it to not use the docker.img and use something else or limit the amount it’s doing since it literally jumped more then 5x its size?

If any other information you need please let me know I would like this to be resolved asap.

Thanks


looks like a lot of other people are having my issue also with the sonic music analyser using a lot of dramatic storage space on the /tmp/.

as seen in this photo here its just continuing lines of this music analysis input.

so since then plex has basically my server ■■■■ itself and i have turned off the sonic analyser since that seems to be the stupid reason for all of this now how in the hell do i remove all those tmp file its created so i can free up my docker.img and then after all this is done please someone explain to me why tf you have sonic analysing making so many go dam files in the docker.img container folder and how can i run sonic analyser without it filling up the docker can i mount it somewhere else?

Ok, so i figure out you can just change the transcoding mount since I’ve figured out also that’s what it’s doing with the audio with the sonic analyzer. and because the files are stupidly big i either have to mount it outside of docker into the ram or mount into a drive somewhere and let it roll up the gbs. Now i wanna know is this safe to put on ram if i was to run sonic analyser with ram? i know you can transcoding normally with ram would it be safe with sonic analyser?

This issue is still on going after moving my transcoding to ram properly since before my configuration was slightly off creating a temp folder within the docker.img which now has been fixed. This Stupid sonic analyser is still to this day creating massive size in the docker.img after just turning it back on yesterday and every mount point possible is directed outside of the docker.img. Can someone explain to me how to remount the sonic analyser or why plex puts it like this?


currently now have a full docker.img and i will be waiting for someone to help me because ive had enough of this crap.

PMS version please (or first 3 lines of your Plex Media Server.log)

Just saw this thread and am writing it up now.

Also please show me where Sonic Analysis is not cleaning up after itself ?
(A directory listing would be ideal)

Jan 18, 2023 12:20:40.585 [0x14e4e6ffcb38] INFO - Plex Media Server v1.30.1.6562-915986d62 - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT 11:00
Jan 18, 2023 12:20:40.585 [0x14e4e6ffcb38] INFO - Linux version: 5.19.17-Unraid, language: en-US
Jan 18, 2023 12:20:40.585 [0x14e4e6ffcb38] INFO - Processor: 16-core Intel(R) Core™ i7-10700 CPU @ 2.90GHz
Jan 18, 2023 12:20:40.585 [0x14e4e6ffcb38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Jan 18, 2023 12:20:40.585 [0x14e4e6ffcb38] INFO - /usr/lib/plexmediaserver/Plex Media Server

i dont know what you mean by directory. the only plex configuration i have for directory is in the above photo from unraid and its all directed outside of the docker.img. Which is why im unsure why the sonic analyser is still using the docker.img files for its process unraid has still telling me its at 93% like before in the above shot showing my docker capacity and showing plex at 50gb which its normally at like 2 to 3 gb before activating sonic analyser. I simply dont get it why its actions are taking place within there? and its seems to not be cleaning its self either because it hasnt moved since this morning.

@nath2125 chuck is looking for a screenshot of the sonic files that are not being deleted.

i dont even know where to start about where they would be stored? All the plex files are ment to be stored in the app data but thats off the docker.img and this wouldnt be an issue?

This is a container, right?

Get on a command line and exec into the docker shell.

From there, getting a directory listing is trivial.

You don’t care where the container is stored. The docker exec command launches you into it

[chuck@lizum ~.2002]$ sudo bash
root@lizum:/home/chuck# docker container list
CONTAINER ID   IMAGE                         COMMAND   CREATED          STATUS                    PORTS     NAMES
dbe7e1f9eb23   plexinc/pms-docker:plexpass   "/init"   23 seconds ago   Up 22 seconds (healthy)             plex
root@lizum:/home/chuck# docker exec -it plex bash
root@dockerplex:/# df
Filesystem                          1K-blocks        Used   Available Use% Mounted on
overlay                             127866880    24947724   102919156  20% /
tmpfs                                   65536           0       65536   0% /dev
tmpfs                                32886268           0    32886268   0% /sys/fs/cgroup
shm                                     65536           4       65532   1% /dev/shm
/dev/sda1                           976283900   391176944   585106956  41% /tmp
/dev/nvme0n1p2                      127866880    24947724   102919156  20% /data
tmpfs                                32886268           0    32886268   0% /proc/asound
tmpfs                                32886268           0    32886268   0% /proc/acpi
tmpfs                                32886268           0    32886268   0% /proc/scsi
tmpfs                                32886268           0    32886268   0% /sys/firmware
root@dockerplex:/# cd /config
root@dockerplex:~# ls
DBRepair.sh  Library  plexmediaserver_1.29.2.6273-2b1f0cbcd_amd64.deb  tmp  transcode
root@dockerplex:~# cd /config/Library/Application\ Support/Plex\ Media\ Server/
root@dockerplex:~/Library/Application Support/Plex Media Server# 

EDIT: You want a listing of the /tmp/music-analysis-input* … whatever’s there.

Reference this screenshot

ive got the main appdata for plex going here /mnt/plexcache/appdata/plex/ from what i see on unraid itself .

i also ran docker exec -it plex /bin/bash in console and its pulled up that directory. and went to the tmp folder and has


i can also bring up that reference photo too but ofc a recent version also if you want.

goes for quite a while. Its a lot of jpg files and .wave

while in those directories… Find out how much space is being used and get a file count.

I need definitive numbers. Sizes and counts.

For the added bonus: How many music tracks does PMS have indexed :slight_smile:

I got this

root@MediaServer:/tmp# du
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to WAV (to 2ch or less)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to WAV (to 8ch or less)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to Dolby Digital (Low Quality - 384 kbps)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to Dolby Digital (High Quality - 640 kbps)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to Dolby Digital Plus (High Quality - 384 kbps)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder/Convert to Dolby Digital Plus (Max Quality - 1024 kbps)
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0/EasyAudioEncoder
0 ./pms-2ffd4de5-4fe9-4ad2-9ef5-d62a69afa7b0
49012432 ./music-analysis-input-59ed3d71-4f81-49f8-a183-54d310b94a6e
49045120 .
root@MediaServer:/tmp# ls

from before when in the tmp directory.

Not sure if this tells you what you need to know. Il try and find exact numbers for each in a second

getting close.

cd /tmp/music-analysis-input-59ed3d71-4f81-49f8-a183-54d310b94a6e
du -ms .
find . -print | wc -l

Separate thought. Cleanup of the container will be fun… not.

I have a decent amount of songs is there a way to find out which ones have been actually indexed or do u mean in reference to how many i have content wise?