DSM 7.1.1 - DS920+ - Failed to Start Plex Server (yet another one of these)

Server Version#: 1.29 and 1.3
Player Version#: N/A

So, ever since I purchased the DS920+, I’ve had issues with keeping the Plex Media Server running. On my 1019+, I never had any problems. I could finally keep the server running by using an older version and starting the server via ssh (start-stop-status start).

Today, Synology told me there was an available package update for Plex. 1.29. I tried updating to it hoping that my issues with keeping it running would be resolved, but no dice. I’m posting here to see if I can get this figured out.

I’ve tried uninstalling with the “erase” option and manually deleting the system’s internal user “PlexMediaServer”. When I install the with 1.30 from Plex.tv version (I’ve tried the plex pass and non-plex-pass versions) the install says “successful”, but I have the age-old problem of it starting for a few seconds and then just stopping on its own. I’ve gone through ChuckPa’s guide, which was informative. When I try starting it vis ssh (either with or without sudo), it just says, “Starting Plex Media Server …” and nothing happens after that. The server never starts and there is no additional information that follows.

Thanks for looking!

2 posts were split to a new topic: Amazon FireTV Activation

Following…

Server logs need to be provided

In DSM 7, we can’t start PMS from the SSH because the environment isn’t setup.
Package Center sets the environment variables before turning control over to us.

This is how DSM 7 is. We have no root / administrative privileges of any kind.
PMS is forced to run as a non-privileged user in a constrained environment.

Server logs , manually collected by making a ZIP of the “Logs” directory, are needed.

1 Like

Good to know about the DS 7 privileges. Makes life hard for you guys, I’m sure…

Attaching logs.
Logs.zip (7.5 MB)

@orembiker

something got into your shared folder and totally mucked up the ownership/permissions.

Notice ‘Permission Denied’.

Nov 29, 2022 12:05:48.219 [0x7f0a901d80d0] DEBUG - Job was already killed, not killing again.
Nov 29, 2022 12:05:48.219 [0x7f0a901d80d0] DEBUG - Database: Shutting down.
Nov 29, 2022 12:05:49.513 [0x7f0a901d80d0] ERROR - SQLITE3:0x80000001, 2570, os_unix.c:40160: (13) unlink(/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal) - Permission denied
Nov 29, 2022 12:05:49.515 [0x7f0a901d80d0] DEBUG - Database: Shutting down.
Nov 29, 2022 12:05:50.644 [0x7f0a8903fb38] DEBUG - NetworkInterface: received Netlink message len=1416, type=RTM_NEWLINK, flags=0x0
Nov 29, 2022 12:05:50.644 [0x7f0a8903fb38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=5, flags=0x1002, change=0x41
Nov 29, 2022 12:05:50.644 [0x7f0a8903fb38] DEBUG - Network change.
Nov 29, 2022 12:05:50.644 [0x7f0a8903fb38] DEBUG - NetworkInterface: Notified of network changed (force=0)
Nov 29, 2022 12:05:50.645 [0x7f0a8903fb38] DEBUG - Network change notification but nothing changed.
Nov 29, 2022 12:05:50.645 [0x7f0a8903fb38] DEBUG - NetworkInterface: received Netlink message len=88, type=RTM_GETADDR, flags=0x0
Nov 29, 2022 12:05:50.645 [0x7f0a8903fb38] DEBUG - NetworkInterface: Netlink address message family=2, index=5, flags=0x80
Nov 29, 2022 12:05:50.645 [0x7f0a8903fb38] DEBUG - Network change.
Nov 29, 2022 12:05:50.645 [0x7f0a8903fb38] DEBUG - NetworkInterface: Notified of network changed (force=0)
Nov 29, 2022 12:05:50.646 [0x7f0a8903fb38] DEBUG - Network change notification but nothing changed.
Nov 29, 2022 12:05:50.646 [0x7f0a8903fb38] DEBUG - NetworkInterface: received Netlink message len=716, type=RTM_DELLINK, flags=0x0
Nov 29, 2022 12:05:50.646 [0x7f0a8903fb38] DEBUG - NetworkInterface: Netlink information message family=0, type=1, index=5, flags=0x1002, change=0xffffffff
Nov 29, 2022 12:05:50.691 [0x7f0a901d80d0] ERROR - SQLITE3:0x80000001, 2570, os_unix.c:40160: (13) unlink(/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.blobs.db-wal) - Permission denied

Must run as user ‘root’

Permissions updated (no errors sent via email), output below:

Task Scheduler has completed a scheduled task.

Task: Fix PlexMediaServer permissions
Start time: Fri, 06 Jan 2023 11:00:49 GMT
Stop time: Fri, 06 Jan 2023 11:02:21 GMT
Current status: 0 (Normal)
Standard output/error:

Tried to run PMS again, but same result. Starting… running… manually stopped. updated logs attached.
Logs (1).zip (7.5 MB)

One thing I’ve noticed is that the log data seems to be time stamped Nov 29, despite it not being that date… is this a fixed date? Or is there an issue with my logs not updating?

Your logs aren’t updating because (I don’t think) PMS is able to access them.

Based on what I did see in those November logs, something got into your PlexMediaServer shared folder and created havoc.

This is likely to require a fair amount of inventive repair. :thinking:

alternatively, if he doesn’t mind just starting with a fresh install that could be the easier route. may take less time in the end ha!

This is best fixed. I just need to think about where it could have gone wrong that isn’t obvious.

@orembiker

Please use Control Panel - Shared Folder

  1. EDIT the PlexMediaServer shared folder
  2. Permissions tab
  3. See “PlexMediaServer” listed
  4. Click “Custom” button (right column)
  5. Go into that popup
  6. Check all the boxes (Full Control)
  7. As you come out of that, watch for this:

Apply to this folder, sub folders and files.

If this doesn’t work, we’ll push your current installation aside and verify the Syno itself is working ok.

@ChuckPa and @djfriday13 . I’ve started fresh about 5x… Everytime I remove PMS, I do “erase all” option. Outside of that, is there a more “fresh” way to start? Reinstalling DSM? Hopefully not…

Hey! This fixed it!

I’m up and running now!

Edit: Going to go ahead and say “Thanks!”. I’m not sure why standard Read/Write permissions weren’t allowing full permissions, or why the script to add permissions manually didn’t do it… but adding custom permissions for everything finally worked

Edit 2: I’m looking at the permissions again after changing them and they look to have reverted back? I check every box and it previously said “Full Control” and I checked the “apply to all subfolders” option. Then saved it and started PMS again

Full Control – exists immediately after migration.
Read Write – is the minimum.

You had something get into your PlexMediaServer shared folder and muck it all up.

Did you add Plug-ins or put media in there?

Plug-ins are OK.
You know what I’ll say about putting media in there… :smiling_imp:

So, Full Control permissions are transitory and it will default to Read & Write thereafter?

I’ve never used that folder for media, but it’s possible during all the reinstalling and migrating of Synology servers that something happened - including incorrectly and temporarily assigning this folder for media purposes.

Yes, Full Control for migration, Read/Write thereafter.

DSM 7 creates the shared folder. I don’t anymore nor do I have any control of the username. It’s all manhandled by DSM 7.

DSM 7 is a whole new animal (a brand new platform to be precise).

  1. I don’t have admin/root privileges anymore at install time so I can’t fix anything that’s broken. ( I silently used to do that on DSM 5 & 6 )

  2. With the username change from “user” to “system internal user” (aka. “service” class) all the extra restrictions apply to PMS

If you want to keep the Plex share… ENJOY.

I felt that having “PlexMediaServer” for the app data and “Plex” for media was the best outcome given DSM 7 changed so many other things

The downfall, PlexMediaServer is fragile. Anything (user / user app) can break it.
There’s nothing I can do to fix it either.

1 Like

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