Plex Media Server on WD PR4100 goes offline

Plex Media Server
1

Server Version#:1.30.1.6497
Player Version#:

Since a couple of days PMS installed on my WD PR4100 goes offline without any warning. I canot access to it anymore no matter I use a player on the phone or via browser.
It works for few hours if I reboot the WD or if from the web interface of WD I turn off and then on again the “mange plex app” toggle.

I tried to uninstall completely the server app and reinstall but without success.

Any help? Apologies if this has been discussed already but I did not find any topic.

Thanks

2

Server Version#:1.30.1.6497

Plex Support, I am having the same issue on my WD PR4100. Some assistance, please?

3

Any resolution this this?

4

Not yet. Is anyone aware of any way to open a support ticket? I don’t see any such thing.

5

Can you post your server logs? In the WD is the app running or stopped?

6

my server install is 1.30.1.6562-915986d62, I’m running on a WD Passport Pro, since the last update of the plex server all of my movies are no longer showing. All of the articles say to reconnect to the server but when I go to the settings there is no button to connect to the server.

7

OK that changes what I thought was wrong, Please see Server credential reset utility for Linux-based platforms you need to claim the server

8

I’m running a WD Passport Pro, Plex came pre installed and there is no way to get to the Linux command line nor is there an install button. This all happened when I updated my server software. Is there plans to fix the problem with a new version / update? Any ideas that don’t involve a command line? This has been going of for a few weeks now.

9

@ChuckPa Any chance you know WD?

10

I know some of WD machines. Those with OS5 installed are still accessible.
The remainder are completely “BlackBoxed” by WD.

Is that a PR4100 ? by chance? (There seems to be other reference other than the OP)

As long as it’s OS5, we’re in business. I have a couple tools (my tools) which will run on OS5 boxes.

Yes, they run at the command line but are designed for those not familiar with command line work.

11

The WD Passport Pro is not upgradeable to OS 5 and no plans for an upgrade. I’ve searched the WD support sites. This is BlackBoxed as you put it. Everything worked find up until the last server update and since then the server is no longer showing and the button in settings/general no longer shows to attach to the server. I’ve had this problem in the past but the button to reconnect to the server always showed so I could fix it. Any ideas?

12

If you have OS4 and Plex installed on the box, It’s still accessible just like OS5 is.

I’m going to try and remotely wake up the WD Passport Pro we have in the lab.
(I can get help during the day if needed but at night, it’s a trick)

OS4 and OS5 should be similar.

The biggest thing we need are the logs to figure out what happened to it.

Once we know, it’s just Linux and moving forward from there is straight forward

What bothers me is that if it’s truly ‘black boxed’… What happened to OS4 ? OS4 alllowed SSH access. OS5 allowed SSH access. Only their new OS shuts that all down on the MyCloud products.

13

My problem is with my new PR4100, running OS5. I thought it was just an “overnight” going to sleep thing, but I actually had it happen to me while I was actively watching something the other night. What do you need from me?

14

@BitPusher

Since OS5 allows command line access, I’d really like to see the PMS logs,
captured as a tar.gz file, right after it fails and you turn it OFF.

This makes certain I have everything there is to see.

You should be able to SSH into the box

cd /mnt/HD/HD*/Nas_Prog/plex_conf

There’re you should see ‘Plex Media Server’

cd   Plex\ Media\ Server

Lastly, make the tar of the logs which you’ll be able to retrieve from the Public shared folder

tar cf /mnt/HD/HD_a2/Public/PlexLogs.tar.gz ./Logs
16
17

How much music do you have ?

I ask because there has been a lot of issues with that recently (they just fixed this past week)

-AND-

The crash occurs when you’re running nightly scheduled tasks (?)

Jan 27, 2023 03:18:03.456 [0x7fb9021a1b38] ERROR - Error parsing XML: Error parsing file.
Jan 27, 2023 03:18:03.456 [0x7fb9021a1b38] ERROR - SSDP: Error parsing device schema for http://172.30.69.150:9080
Jan 27, 2023 03:18:33.455 [0x7fb9021a1b38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://172.30.69.150:9080
Jan 27, 2023 03:18:33.455 [0x7fb9021a1b38] DEBUG - [HCl#2aa1] HTTP requesting GET http://172.30.69.150:9080
Jan 27, 2023 03:18:33.460 [0x7fb904a1fb38] DEBUG - [HttpClient/HCl#2aa1] HTTP/1.1 (0.0s) 200 response from GET http://172.30.69.150:9080
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: Entity: line 1:\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: parser\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: error :\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: Start tag expected, '<' not found\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: status=ok\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - XML: ^\00
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - Error parsing content.
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - Error parsing XML: Error parsing file.
Jan 27, 2023 03:18:33.460 [0x7fb9021a1b38] ERROR - SSDP: Error parsing device schema for http://172.30.69.150:9080
Jan 27, 2023 03:18:40.558 [0x7fb8ff70fb38] ERROR - LoudnessJobManager: job unable to complete in allotted time, killing
Jan 27, 2023 03:18:40.558 [0x7fb8ff70fb38] DEBUG - Killing job.
Jan 27, 2023 03:18:40.587 [0x7fb8ff70fb38] DEBUG - Signalling job ID 30745 with 9
Jan 27, 2023 03:18:40.606 [0x7fb906b5cb38] DEBUG - Jobs: '/mnt/HD/HD_a2/Nas_Prog/plexmediaserver/binaries/Plex Media Scanner' exit code for process 30745 is -9 (signal: Killed)
Jan 27, 2023 03:18:40.606 [0x7fb8ff70fb38] ERROR - LoudnessJobManager: job for item 20525 failed (-9)
Jan 27, 2023 03:18:40.613 [0x7fb8ff70fb38] DEBUG - Activity: Ended activity 1e5266ae-d851-4ad2-9431-806f7448d98a.
Jan 27, 2023 03:18:40.614 [0x7fb8ff70fb38] DEBUG - Activity: ended sub-activity b3c335c0-2139-4dcf-9496-d721fbf81c55 parent: 8db362db-9bdf-410e-88e5-932059ea3150 overall progress: 100.0% (692/692)
Jan 27, 2023 03:18:40.615 [0x7fb8ff70fb38] DEBUG - Activity: updated activity 8db362db-9bdf-410e-88e5-932059ea3150 - completed 100.0% - Butler tasks
Jan 27, 2023 03:18:40.686 [0x7fb8ff70fb38] DEBUG - Activity: registered new sub-activity 6d3d89a9-cee1-4082-bc2e-677e35bff361 - "LoudnessAnalysis" parent: 8db362db-9bdf-410e-88e5-932059ea3150 overall progress: 99.9% (692/693)
Jan 27, 2023 03:18:40.686 [0x7fb8ff70fb38] DEBUG - Activity: updated activity 8db362db-9bdf-410e-88e5-932059ea3150 - completed 99.9% - Butler tasks
Jan 27, 2023 03:18:40.686 [0x7fb8ff70fb38] DEBUG - Butler: Scheduling loudness analysis for album 31464.
Jan 27, 2023 03:18:41.221 [0x7fb8ff70fb38] DEBUG - [JobRunner] Job running: /mnt/HD/HD_a2/Nas_Prog/plexmediaserver/binaries/CrashUploader "--directory=/mnt/HD/HD_a2/Nas_Prog/plex_conf/Plex Media Server/Crash Reports/1.30.1.6497-5fc2e0894" --version=1.30.1.6497-5fc2e0894 --platform=Linux --platformVersion=5.26.119 --serverUuid=5f1bb6a2be450fef331d0211017b067f95ebb979 --userId=steve@asiatico.net --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/minidump/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "--vendor=Western Digital" --model=x86_64 --device=MyCloudPR4100 --allowRetries=0
Jan 27, 2023 03:18:41.222 [0x7fb8ff70fb38] DEBUG - [JobRunner] Jobs: Starting child process with pid 13619
18

125+ Gb…nearly 25k individual files.

19

My situation is similar, I have 1.2 Tb of music (mainly Flac) with more than 49.000 songs.

I have temporarily solved the issue uninstalling the last plex relase and using the one that is suggested from the WD installation menu.

The current version installed is the 1.26.2.5797. This version at least for me does NOT shut down over night

20

Any new status on this issue?

21

I’m assuming an unannounced fix was part of later releases. I am currently on 1.31.1.6716 and this issue is no longer occurring.