Synology DSM7 Plex "manually stopped" after a few seconds

Plex Media Server NAS & Devices
1

Server Version#: DSM 7

I had a power outage a few days ago, and now I can’t access my server. I am running DSM 7 on Synology 1815+. I was dealing directly with synology, and we setup port forwarding and did a bunch of other trouble shooting, but no fix. I should preface what that I am not super technologically savvy, so you’ll have to speak slow and use small words for me - not even sure if I’m adding the debug log correctly. Not that this makes any difference, but I use a mac to access it - no pc.

Please help!
Logs (3).zip (3.6 MB)

2

your logs show, while running, a normal server.

This tells me either:

  1. The package software got damaged
  2. The permissions in the PlexMediaServer got damaged

Let’s do both

  1. Uninstall the pagkage, use the “KEEP” (uninstall only) option
  2. Now run this procedure (Scheduled Task) which will make certain everything inside the PlexMediaServer shared folder is accessible again.
  1. When you get the mail the task is complete and successful,
  2. Install the same SPK file / version again and let it start up NORMAL install.
    5 That should be it.

If it’s running but not accessible,

  1. Uninstall KEEP
  2. Reinstall again but use the “New or Lost” (Plex Claim Token) method.
  3. That process will reclaim the server for you.
3

I created the scheduled task, and it ran and here’s what the email says.

Task: Fix PlexMediaServer owner
Start time: Sun, 30 Apr 2023 00:00:01 GMT
Stop time: Sun, 30 Apr 2023 00:00:01 GMT
Current status: 0 (Normal)
Standard output/error:
/bin/bash: line 1: cd: /var/packages/PlexMediaServer/shares/PlexMediaServer: No such file or directory
chown: cannot access ‘AppData’: No such file or directory
find: `AppData’: No such file or directory

I installed using the keep and normal method, and I couldn’t find the server, and plex would show “manually stopped”. I then tried the reinstall method, after uninstalling, and used the new or lost (claim) method. I clicked the link that take you to plex.tv/claim, copied and pasted that into the installation claim screen. This gave me the same results. Any other suggestions?

4

@AlexBegue

You stated you’re using DSM 7.

When the package is installed,
/var/packages/PlexMediaServer/shares/PlexMediaServer always takes you to it. (That’s how DSM 7 works)

There is always a directory at the top named AppData.
(That’s how I wrote it :slight_smile: )

Are you, by chance, running Plex 1.21.0.3744 ?

5

I installed 1.32.0.6973-7000

6

You, as the administrative group user, should be able to open FileStation and see “PlexMediaServer” in the left column.

Do you?

7

Yep, I see it there.

8

Here’s how it works:

  1. When you install any -7000 package, it creates /PlexMediaServer/AppData
  2. It’s owned by the service PlexMediaServer
  3. While the package is installed. DSM 7 maintains the linkage from
    /volume1/PlexMediaServer (or wherever it is)
    -to-
    /var/packages/PlexMediaServer/shares/PlexMediaServer

chuck@ds418:~$ cd /var/packages/PlexMediaServer/shares/PlexMediaServer
chuck@ds418:/var/packages/PlexMediaServer/shares/PlexMediaServer$ pwd
/var/packages/PlexMediaServer/shares/PlexMediaServer
chuck@ds418:/var/packages/PlexMediaServer/shares/PlexMediaServer$

I don’t understand why the User-Script failed unless you Uninstalled the paclage before running the script ??

9

I tried lots of things prior to posting on the forum. I have uninstalled it and reinstalled it multiple times before running the script. I tried multiple versions of Plex, older version, hoping that it would fix the issue.

10

Alex,
Just to see what happens.

  1. Uninstall the package (KEEP – first radio button)
  2. Open FileStation
  3. Go to PlexMediaServer
  4. Rename ‘AppData’ to ‘AppData-Alex’ (This is all your server data)
  5. Now install the SPK (either from package center or the downloads page - only those two )

Let me know if it starts up and wants to create a new server.
If it does, go ahead and give it a goofy Friendly Name and only 1 small media section.

(We’re testing to see what’s happening)

When were done, we’ll put it all back thte way it belongs.

11

It looks like we’re making progress! After I renamed it to AppData-Alex, and reinstalled it, plex will now stay open in the package center, and doesn’t say “manually stopped”. I went into plex, and it didn’t have any of my media, so I added a small library.

12

COOL.

Open FileStation
Go into PlexMediaServer/AppData-Alex/Plex Media Server

Look at the file size of ‘Preferences.xml’ .
Is it zero length?

Is there a Preferences.xml.tmp ?

14

I deleted the post for privacy

The problem with your preference file is that it shows as unclaimed. (No username or token). That’s easily resolved once permissions are ok.

all this confirms you have a permissions problem in there somewhere (happens with these events)

I want to revisit this:

Task: Fix PlexMediaServer owner
Start time: Sun, 30 Apr 2023 00:00:01 GMT
Stop time: Sun, 30 Apr 2023 00:00:01 GMT
Current status: 0 (Normal)
Standard output/error:
/bin/bash: line 1: cd: /var/packages/PlexMediaServer/shares/PlexMediaServer: No such file or directory
chown: cannot access ‘AppData’: No such file or directory
find: `AppData’: No such file or directory

Did you set the task to run as user ‘root’ ?

DO NOT run it now … I’m just asking.

15

If I did, then it was not intentional.

16

Check the setting in the Task Scheduler.

On the settings tab, it will show which user it runs as. It should show as ‘root’.

17

The task we made, “Fix PlexMediaSever owner”, the user that is selected is root

18

the reason I am concerned is because , right now,

/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/

does exist.

As long as the package is installed, it will exist.

(That’s how I wrote it)

19

Do you want me to change it to something else?

20

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.