Plex Media Server 1.6.1 horribly broken on Synology

Just my $0.02 that PMS 1.6.1 is horribly broken on Synology. I upgraded from 1.5.5, and the only thing the app does is complain it can’t find the 1.5.5 plug-ins folder in resources without anything else showing up in the log files or on plex web. Symbolic linking this folder does make the log entries go away but doesn’t budge the app into starting. This goes for both the x86 and X64 versions. Did the devs even bother to test this?

Since you can’t even downgrade anymore these days and this effectively broke my whole setup I guess I’ll have to sit down and twiddle my thumbs until this gets fixed.

1.6.1 won’t find 1.5.5 plug-ins. It will be looking for the 1.6.1 plug-ins distributed with it.

Would you be kind enough to post your log files? I’ll figure out what is going on.

Also, what Synology model are you running on and are you using 32 or 64 bit?

it does complain that it can’t find the 1.5.5 plugins :

Apr 29, 2017 01:46:37.927 [0xef511b40] WARN - Warning: ex: boost::filesystem::last_write_time: No such file or directory: "/volume1/@appstore/Plex Media Server/Resources/Plug-ins-995f1dead", couldn't check file: /volume1/@appstore/Plex Media Server/Resources/Plug-ins-995f1dead

Thats all there is in the log files.

I’ve tried both the x86 and X64 versions on DSM 6.1-cedarview

Go to the Plex share in File Station. Navigate down until you see Logs. Right click on Logs and Compress to Logs.zip.

Attach that file with your next post please. What you’ve presented here is insufficient for me to diagnose.

I’m sorry I’m not going to publish my complete logs to a publically available forum.

Then PM me the log files and provide the link to this thread.

In your PM, kinly detail the Synology model and other running applications. There are apps which, when incorrectly configured, will drive pms ‘crazy’.

FYI the issue was fixed after installing a later version.

This problem has re-appeared in version 1.8.0/1.8.1. I’d like to know where this path is linked from so I can fix this issue myself. Thanks.

Since your Library and the application are separate, have you done a complete uninstall-reinstall of PMS itself with a reboot in between?