DSM DSM 7.0.1-42218 Update 3 Plex 1.27.0.5849-7000 not runing

Hi Guys,

i updated my Synology Nas with the 7.0.1-42218 Update 3.

After the Update my Plex didint started after reboot.

In the Packe Center i startet Plex manually. It starts but shut down after 5 to 6 seconds.

I edited it an reinstalled other versions.

No chance to get my folders running.

When i start plex.tv i see the folders but they are offline.

Anybody any advice for me?

i just did the update for windows and plex is now offline too same Version 1.27.0.5849

Does anybody other have the same ussue with the 1.27.0?
Could it be possible that the version of the App is damaged?
But i tryed different und the issue came at every version.
Versions which run.

1 Like

Following, also updated to DSM 7.0.1-42218 Update 4

Not able to install Plex, repair or uninstall. Possibly a DSM integration issue or Package?

**** update. After ensuring under shared folder on DSM Control Panel; permissions\system_internal_user - Edit Plex Media Server to Custom permissions and enable take ownership.

I then accessed https://app.plex.tv/desktop/#!/ which advised of a server update, manually downloaded and installed via package centre and voila; back in business.

@kivi5770_googlemail_com @plex_joat. Hopefully this works for you guys too :slight_smile:

Hi isaacla2, that didnt work at my system. Still the same

May I ask why only DSM 7.0.1 U4 ?

Most of the Synology systems are currently using DSM 7.1

Screenshot from 2022-06-01 11-47-39

Regarding changing permissions for the PlexMediaServer shared folder –

  1. You should never need to touch it.
  2. DSM itself sets and maintains the permissions

If media files have been placed in the PlexMediaServer shared folder
which break Plex – Move the files out as they don’t belong there. ( I will help reset all the permissions back to standard )

7.0 because this is now the stable version :slight_smile:

btw I’m with DSM 7.0.1-42218 update 3 and Plex 1.27.0.5849 works like a charm.

I updatet the DSM but still dosent work. I dont want to lose all date. Can i erase everything from the OS? Can i save the settings to copy them back to the PlexMediaServer Folder? Is it psooible or do i have to setup everything new? But i should have no impact to the data itself on the Synology?


I mean this folder. That should be the seetings data?

@kivi5770_googlemail_com

  1. Please stop PMS

  2. Using FileStation, go to PlexMediaServer/AppData/Plex Media Server

  3. Right-click “Logs” → “Compress to Logs.zip”

  4. Download the “Logs.zip” file

  5. Attach it here so we can see what is happening

Logs.zip (5.9 MB)

Hi Guys, sorry i was offline for a few days.

I attached the log.

There is a new version online for the dsm. Perhaps this will fix the issue. I report.

It runs now at version DSM 7.1-42661 Update 2 but still no plex. The same issue. I attached a new log.

Logs.zip (5.9 MB)

Any respond? Or idea? Otherwise i have to install from new.

You need to tag @ChuckPa if you want him to see your reply.

Did DSM crash / get shut down HARD (by holding the power button / power failure) at some point?

Asking because this log –

May 31, 2022 17:16:25.797 [0x7faaf2accb38] DEBUG - Spawned plug-in com.plexapp.system with PID 18083
May 31, 2022 17:16:25.797 [0x7faaf2accb38] DEBUG - [com.plexapp.system] Sending command: GET /:/prefixes^M
May 31, 2022 17:16:26.372 [0x7faaf34ebb38] DEBUG - Grabber: Cleaned up 0 decrepit directories in 0.2 sec.
May 31, 2022 17:16:32.922 [0x7faaf34ebb38] DEBUG - Grabber: Plex Tuner Service not running; retrying in 10 seconds.
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

is what I usually see as the OS shuts down abruptly.

Are there any newer logs?

Also, I would very much like to see the difference between 1.26.2 (which was working) and 1.27.0 which clearly is having an issue (but looks like DSM is the issue here)

Hi, seems like the DSM dosent want to comprimize the AppData anymore. I think i have to kill the hole setup and beginn from comoletly new.