[Support] Linuxserver.io - Plex Media Server


5051 posts in this topic Last Reply

Recommended Posts

  • Replies 5.1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Go to the appdata share and look in Plex\Library\Application Support\Plex Media Server\Crash Reports You will find folders for your previous versions named as the release version.

Yep, seems like the problem.   Not to be outdone... google.  And what do I find.... Hoopster's post from over a year ago. I see your post here regarding the iGPU not being enabled corr

Application Name: Plex Media Server Application Site: https://plex.tv/ Docker Hub: https://hub.docker.com/r/linuxserver/plex/ Github: https://github.com/linuxserver/docker-plex  

Posted Images

3 hours ago, randomusername said:

I just updated to the latest version of this container and more than half of my 'on deck' shows are not showing on deck. On top of this, one series had a first episode of a new season come out today and Plex didn't put it on the deck.

 

I have tried changing the number of weeks on deck shows - my standard is 999, but I tried 0,1,52,99999. Even at 99999 it doesn't show all of them.

 

Does anyone have any ideas? On deck is great for not missing shows.

I would suggest posting this on the Plex forum. Really looks like a problem with the app.

Link to post

Hey all, I've been running this docker pretty well for awhile. Recently, I've run into a couple issues and I thought I'd reach out for some direction.

 

1) Some time ago (maybe 6 months?), I simply was unable to update my plex docker. I'd attempt the upgrade and it would stall at removing or stopping the container and when I "Xed" out of the upgrade popup, it would simply remove the container. After the first time heart attack, I figured out how easy it was to reinstall previous docker images so I would simply just do that and eventually I became ok with just not upgrading. However, now that I am here, I'd like to resolve so I can keep using the latest and greatest.

 

2) Recently, as in a few days ago, I began losing mounted drives containing media I was streaming in Plex. At first, I lost the most recent drive I had mounted (A single drive in a caddy plugged into a machine on my network), but now I appear to have lost my main drive (Drobo 5N) which took everything down. The weird thing is from the "Main" tab in the docker UI, the shares both exists, report as mounted, and when I click the hyperlink for the mount, I browse to them and into directories and even pull up files. Nothing has really changed in any configs, so I am at a loss.

 

Any help for either issue would be appreciated. I'm also willing to provide more info such as logs, etc. if needed.

Link to post
49 minutes ago, davcollins said:

Hey all, I've been running this docker pretty well for awhile. Recently, I've run into a couple issues and I thought I'd reach out for some direction.

 

1) Some time ago (maybe 6 months?), I simply was unable to update my plex docker. I'd attempt the upgrade and it would stall at removing or stopping the container and when I "Xed" out of the upgrade popup, it would simply remove the container. After the first time heart attack, I figured out how easy it was to reinstall previous docker images so I would simply just do that and eventually I became ok with just not upgrading. However, now that I am here, I'd like to resolve so I can keep using the latest and greatest.

 

2) Recently, as in a few days ago, I began losing mounted drives containing media I was streaming in Plex. At first, I lost the most recent drive I had mounted (A single drive in a caddy plugged into a machine on my network), but now I appear to have lost my main drive (Drobo 5N) which took everything down. The weird thing is from the "Main" tab in the docker UI, the shares both exists, report as mounted, and when I click the hyperlink for the mount, I browse to them and into directories and even pull up files. Nothing has really changed in any configs, so I am at a loss.

 

Any help for either issue would be appreciated. I'm also willing to provide more info such as logs, etc. if needed.

That is an issue with unraid and not Plex, so better to open a new thread in the general support subforum.

Link to post

last weekend i found out that maybe the problem was the DVR, so i remove this from my main server and created an second server for this, but my problem still exist:

Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.21.4.4079-1b7748a7b/PLEX MEDIA SERVER/6507dcb9-aeb8-178e-763c213c-306a3ee2.dmp
Starting Plex Media Server.
Critical: libusb_init failed
Mar 1 14:25:39 LMFSv3 kernel: Plex Media Serv[121438]: segfault at b8 ip 0000000000b456af sp 0000148a6a86e920 error 4 in Plex Media Server[a0c000+f23000]
Mar 1 14:25:39 LMFSv3 kernel: Code: 46 04 00 48 8d 05 51 ee de 00 49 89 46 08 89 6c 24 08 eb 0d 89 6c 24 08 83 fd ff 0f 84 54 02 00 00 4c 89 64 24 60 4d 8b 67 08 <41> 80 bc 24 b8 00 00 00 00 74 15 49 8d bc 24 90 00 00 00 e8 89 4d
Mar 1 14:26:19 LMFSv3 kernel: Plex Media Serv[122854]: segfault at 30 ip 0000000000bbaf9f sp 000014e9e8ffa980 error 4 in Plex Media Server[a0c000+f23000]
Mar 1 14:26:19 LMFSv3 kernel: Code: cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 50 49 89 d5 49 89 f6 8b 36 83 fe ff 0f 84 5b 01 00 00 49 89 fc <48> 8b 7f 08 4d 8d 7e 08 31 c9 41 f6 46 04 40 0f 94 c1 4c 89 fa e8
Mar 1 14:27:00 LMFSv3 kernel: Plex Media Serv[124369]: segfault at b8 ip 0000000000b456af sp 000014840a892920 error 4 in Plex Media Server[a0c000+f23000]
Mar 1 14:27:00 LMFSv3 kernel: Code: 46 04 00 48 8d 05 51 ee de 00 49 89 46 08 89 6c 24 08 eb 0d 89 6c 24 08 83 fd ff 0f 84 54 02 00 00 4c 89 64 24 60 4d 8b 67 08 <41> 80 bc 24 b8 00 00 00 00 74 15 49 8d bc 24 90 00 00 00 e8 89 4d

 

the second server is stable, no crash at all. does this mean my main server is corrupted????

WHAT CAN I DO WITHOUT RECREATING MY LIBRARY?

its pretty big and recreate this means hours of work and probably some temp ip bans from the metadata sites...

 

i tried this already on the plex forum, the suggested to downgrade to unraid 6.8.3. with is NOT possible for me, i lose HW transcode and the Multi cache pool (where all my VM are running on...)

Link to post
22 minutes ago, John_M said:

 

What is using a USB connection?

 

my VM and unRAID itself use a mouse/keyboard of the unRAID GUI.

but i search on the Plex forum on that error message and its from the Plex tuner services, i don't use DVR on this server anymore? why is this still trowing errors and instability??

i found this topic where they kill the plex tuner service, i just tried this out and will monitor the logs for any other errors/instability...

 

edit:

server still crashing, but now i got this message:

Jobs: Exec of /usr/lib/plexmediaserver/Plex Tuner Service failed. (13)

 

no more "Critical: libusb_init failed".

but still an unstable server :(

 

Edited by sjaak
Link to post
51 minutes ago, Endda said:

all good to update to stable unraid 6.9.0 with this docker?

Yes. Why wouldn't it?

Edited by saarg
Link to post

I have a peculiar problem with plex:

I added a new library entry and mapped it to a cached share (via /mnt/user/*). Scan works, playback works, all is perfect ... until my array drives are spun down. When I try to play a video, I get the following error:
image.png.28d327a47dc58e8d86c50cdfdb91d965.png
When I spin up the drive containing the video manually playback works as expected. So plex isn't accessing the file in a way that makes unraid spin up the drive. Any idea why that may be? I tried the search but most hits are regarding plex spinning up their drives, that's not really my issue.

 

Initially I assumed it might be related to me using the Dynamix Cache Directories plugin, but the problem persists when I disable it. Besides I had the relevant folders excluded within the plugin settings. I'll take the question to the plugin thread if noone has an idea here, but I thought I'd start with plex since the problem doesn't appear if I start the video file manually on my pc.

Link to post

Hello All,

I'm moving from binHex's Plex to Linuxserver.io so I can take advantage of my nvidia card.  I do have it working but not without some annoying behavior that I'm sure is my fault somehow so I thought I would ask.

 

4 or 5 times now I have entered something wrong in the Docker Configuration page...  I see the error when saving and then the docker is not visible in my 'Dockers page' anymore.  I have to re-add it from the APPS.  When I re-add it, none of the Ports, Variables, etc... are shown in the UI anymore.   However, if I 're-add from the APPS and just start it, it will run like those items are still there.   Is it possible to overcome this and have it show my configuration without having to re-enter it?    Thanks

 

Link to post
4 hours ago, cerickso88@gmail.com said:

I have to re-add it from the APPS.  When I re-add it, none of the Ports, Variables, etc... are shown in the UI anymore.

Not clear what the difference is between what you said you did above, and what you said you did in the sentence which follows it below

4 hours ago, cerickso88@gmail.com said:

However, if I 're-add from the APPS

 

Perhaps you could clarify?

Link to post

Not sure it's been addressed  here (I'm not reading 194 pages.. lol) but I updated Unraid to 6.9.0 this morning. Everything went well until Plex tried to autostart, kept getting bad parameter. Checked log noticed Critical: libusb_init failed. Searched internet and everything was pointing to a database corruption issue.

 

Just so happened to look at my dashboard and noticed GPU Statistics was missing (it's done this before) so on a hunch I checked for new nVidia driver app. Once installed, I had to disable docker and then re-enable and Plex was up and running again. Also downloaded the new GPU Statistics App. 

 

Just thought I'd post in case anyone else runs into this issue.

 

 

Link to post

Ran into an issue today after a slew of other issues that a lot of googling and other troubleshooting has not solved. My Plex container is up and running but is unreachable (all on the same network via LAN).

 

My server went thru a long move, restarted fine, but after a few weeks a drive randomly disabled and yesterday I had to remove it from the array, add it back and rebuild from parity. I had updated to 6.9 a day or two before the drive issue. I also had a weird issue where my docker image got full, but ended up clearing itself out after the rebuild.

 

Now I'm running into the above issue trying to reach my server from any of my usual devices (Roku, web app / webGUI). Nothing seems to get to it even if I am logged in directly to the IP:port combo.

 

I've run through all of the Plex official troubleshooting, deleted my docker image and rebuilt it via saved container templates but no luck. Unfortunately its been quite some time since I've had hands on the server due to the move, and I'm a bit out of my depth at this point in troubleshooting. I tried to pull the container logs but they just listed a few startup items with no errors (log attached.)  I don't seem to have access to the actual Plex logs, assuming this is because I cannot actually get to my server.

 

 

plexlog.txt

Link to post
On 1/7/2021 at 12:47 PM, CJston15 said:

I have been running Plex in docker for quite a while now and never had issues until last night. Starting last evening none of my media with EAC3 audio will play in Plex now (Roku, Shield, or Web). I have tried changing the transcode folder location, deleting my codecs, turning off automatic library scanning, verifying that my Unraid servers inotify value isn't too low (it's over 500K, tried increasing to 1mill no change and changed back to default value), restored docker container from backup, completely blew it up and did fresh install of Plex. Nothing has resolved this issue in the last 18 hours. Only thing that happened was that my power went out yesterday afternoon for a couple hours and my Unraid server shut down (gracefully, it's connected to APC UPS and it sent the shutdown command at 20%).

 

Anyone have any other ideas? Been using Plex for like 10 years now, and on Unraid for the last 2-3 without any issues. I have about 1500 movies, 200 TV shows (15K episodes), 2k Music, and another 200 misc documentaries/specials. Nothing crazy compared to what I've seen others host.

Did you figure this out?

I'm roughly in the same situation as you. I cannot seem to transcode EAC3 anymore. Videos just buffer indefinitely.

Link to post
10 minutes ago, gustomucho said:

I'm roughly in the same situation as you. I cannot seem to transcode EAC3 anymore. Videos just buffer indefinitely.

Delete the codecs folder in [path to your Plex appdata folder]/Library/Application Support/Plex Media Server

 

This will force Plex to again download codecs as needed.  It is likely some corrupt codes are causing EAC3 audio issue.

Edited by Hoopster
Link to post
28 minutes ago, Hoopster said:

Delete the codecs folder in [path to your Plex appdata folder]/Library/Application Support/Plex Media Server

 

This will force Plex to again download codecs as needed.  It is likely some corrupt codes are causing EAC3 audio issue.

Thanks for the tip Hoopster. I tried deleting said folder and it did not change anything.

I still kept getting the error "EAE timeout! EAE not running, or wrong folder?" in the Plex console.

Which made me wonder. I followed @mgutt suggestion, specifically the part to enable direct disk access for Plex config (changing the config mapping to /mnt/cache/appdata/Plex-Media-Server instead of /mnt/user/appdata/Plex-Media-Server).

 

After changing it back to the default /mnt/user/appdata/Plex-Media-Server, Plex is now able to transcode EAC3 without any problems. I'm not exactly sure what the problem is, but it seems that using the cache option doesn't give Plex access to codecs folder for some reason?

Link to post
5 minutes ago, gustomucho said:

After changing it back to the default /mnt/user/appdata/Plex-Media-Server, Plex is now able to transcode EAC3 without any problems.

Yeah, not sure why that would make a difference but the important thing is that it is working.

 

The solution I suggested is one that is mentioned in the Plex forums for those with EAC3 audio issues.  Your problem obviously had a different solution but at least there is a solution.

Link to post
5 hours ago, gustomucho said:

I'm not exactly sure what the problem is, but it seems that using the cache option doesn't give Plex access to codecs folder for some reason?

Can't be possible as both paths return the same files.

 

Are you sure that your appdata is located only on the cache? Check the appdata location as mentioned in the manual!

Link to post
1 hour ago, mgutt said:

Can't be possible as both paths return the same files.

 

Are you sure that your appdata is located only on the cache? Check the appdata location as mentioned in the manual!

I had read your instructions carefully and followed everything to the letter (I re-read everything again just now to be extra-certain!).

My appdata folder was indeed only on my SSD cache drive. No appdata files were on any of the array drives.

I have no idea what went wrong, but after being out of ideas and only trying 1 possible solution at a time, reverting back to /mnt/user/ instead of /mnt/cache/ did give Plex access to the codecs folder for transcoding.

I don't know if there could be a permission's problem with my docker config, but I did not change anything else from the defaults (other than mapping the media folders and adding the 2 following extra parameters in the docker) :

--device=/dev/dri --mount type=tmpfs,destination=/tmp,tmpfs-size=4000000000

Everything works great now so I will leave it at that. Transcoding to RAM still works well with your instructions.

Edited by gustomucho
Link to post
4 hours ago, gustomucho said:

I don't know if there could be a permission's

Can't be, because a container has no clue what happens outside of it and /mnt/user/appdata targets the exact same files with the same permissions as /mnt/cache/appdata (as long there are no files left on the array). I would say the reason of the fix is the recreation of the container (which happens everytime you change container settings). So /mnt/cache/appdata should work.

 

 

Link to post
5 hours ago, mgutt said:

(as long there are no files left on the array)

 

Or in another pool (in the case of Unraid 6.9). If there are appdata files that are neither in the "cache" pool, nor on the array, but are present in some other pool, then they would be seen via the /mnt/user path but not via the /mnt/cache path.

Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.