dsmitty166 Posted September 23, 2014 Share Posted September 23, 2014 Hello, Just wondering if anyone else has faced this issue. It really only happens with large Movies, 1080, DTS, but Plex Docker seems to load really slow. Also, I cannot resume some of these movies where I left off. I also cannot forward ahead. It just sits there and spins and then eventually says there was a problem playing this movie. However, if I just choose to start the movie from the beginning, it takes about 5 seconds and starts playing normally. Anyway to grab a log or figure out what's going on? Or is this a known issue? Never had this type of issue running a Xen VM before. Just wondering if docker can't handle the load? Is there a way to check my CPU load in unRAID while this is going on? I'm on the latest Plex Docker, beta 10a, and Docker is on my SSD Cache Drive. It also doesn't make a difference playing on my chromecast, phone, or computer. All results are the same. Thanks Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 What did you enter as your :config directory when setting up Plex dpcker? Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 What did you enter as your :config directory when setting up Plex dpcker? Hope this helps Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 I would think you :/config directory is on your array and not on your cache. I have used mnt/user/cache/appdata and set to cache only in the shares. Yours is /mnt/cache/appdata I initially did the same and plex performance was sluggish plus stop start. I presume it's slow due to having to spin up disks and perhaps limited space for transcoding directory Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 So should I just change it to /mnt/cache/config ? Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 Check your array disks first and see if the appdata folder is on one of your array disks and also check the share setting on the appdata folder before you do anything to confirm that is the case Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 Check your array disks first and see if the appdata folder is on one of your array disks and also check the share setting on the appdata folder before you do anything to confirm that is the case OK, I found appdata folder on disk1 and disk5. The share setting is also not set to use the cache disk. If I change it to only cache, will it fix itself? Thanks Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 I don't think it will move the files for you. Setting to cache only will just stop it from being moved from the cache to the array. I would manually move the files to mnt/user/cache/appdata, correct the docker setting and set that share to cache only. Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 My docker setting is already: /mnt/user/appdata is there something else that you're referring to? Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 Missing the cache Mnt/user/cache/appdata/plexmediaserver Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 Missing the cache Mnt/user/cache/appdata/plexmediaserver Ok I changed to that, and it broke it. Won't load the Plex page with those settings. Anyways, while I was at it, I created a new directory. /mnt/user/cache/appdata/plexmediaserver2 Readded some of my libraries, but still the same result. Cannot resume larger movies, and I cannot seek forward in the film either. Just times out. Again, in the smaller movie files, there's no issue, I can skip forward as much as I'd like EDIT: Upon further review, it's not necessarily the size of the file. I just skipped ahead in some larger files, but there are still a few that I cannot. Any thoughts? Could it be an encoding issue? Quote Link to comment
Ashe Posted September 23, 2014 Share Posted September 23, 2014 Did you copy your appdata files from the array to the cache? And set the share to cache only? Shouldn't be an encoding issue, plex will only choke if there is not enough space for the temporary transcoding of files. Is there enough free space on your ssd? Have you specified the temporary transcoding location within plex settings? Quote Link to comment
dsmitty166 Posted September 23, 2014 Author Share Posted September 23, 2014 Did you copy your appdata files from the array to the cache? And set the share to cache only? Shouldn't be an encoding issue, plex will only choke if there is not enough space for the temporary transcoding of files. Is there enough free space on your ssd? Have you specified the temporary transcoding location within plex settings? I did copy them. I have 232GB free on my SSD But I also created a new folder on a new library. Same thing. I've set the share to cache only. Can I just set the temp folder to /mnt/user/cache/appdata Like I said, only a few 14gb + files do this. But not all. I have everything set to direct play Quote Link to comment
dsmitty166 Posted September 24, 2014 Author Share Posted September 24, 2014 OK update: I installed plex as a plugin, and I have the same issue, cannot advance forward or resume some movies. Anyone else experience this at all?? Quote Link to comment
dsmitty166 Posted November 1, 2014 Author Share Posted November 1, 2014 Bump... I still have this issue. Can't believe I'm the only one. My config must not be correct. Is anyone able to help me with this? EDIT: Just found this in the logs Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Attempting to create directory '/mnt/user/cache/appdata' for transcoder temporary files. Nov 01, 2014 10:48:02 [0x2ae105234700] ERROR - Wasn't able to create directory for transcoder temporary files. Can anyone help me solve this? Is it permissions? Nov 01, 2014 10:48:02 [0x2ae10663e700] DEBUG - It took 0.000011 sec to serialize a list with 0 elements. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Shutting down idle session 7j5uzamcwi5dn29 (idle time is 180 seconds) Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Killing job. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Signalling job ID 13430 with 9 Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Job was already killed, not killing again. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Stopping transcode session 7j5uzamcwi5dn29 Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Cleaning directory for session 7j5uzamcwi5dn29 (/tmp/plex-transcode-7j5uzamcwi5dn29-87137f6f-c764-4587-82f3-09efd1b69cc7) Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Cleaning old transcode directories. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Attempting to create directory '/mnt/user/cache/appdata' for transcoder temporary files. Nov 01, 2014 10:48:02 [0x2ae105234700] ERROR - Wasn't able to create directory for transcoder temporary files. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Whacked session, 0 remaining. Nov 01, 2014 10:48:02 [0x2ae105234700] DEBUG - Killed 1 idle sessions, and 0 remain. Next I removed the hardcoded transcoder directory from plex settings. Here's the log, I started the movie from the beginning, and then randomly selected a spot further ahead in the film. It then timed out trying to load. Any help please?? http://pastebin.com/jMs0RVuV Quote Link to comment
dsmitty166 Posted November 2, 2014 Author Share Posted November 2, 2014 Just an update after more troubleshooting and configuring, I still haven't solved this, but I installed PMS on my windows computer, and the same issue still persists. So I know it's not the docker container. Does anyone know how to analyze .mkv's to see what the differences are? Quote Link to comment
brettm357 Posted November 3, 2014 Share Posted November 3, 2014 Try http://mediaarea.net/en/MediaInfo Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.