Synology - Issue Migrating Plex to another Storage Pool

It’s strange that you say the server is running cause it definitely had crashed and stopped itself. Interesting about the network config too, that’s definitely not new but nevertheless I bonded the 2 adapters by following the instructions, rebooted the NAS to be sure it stuck, then started up Plex. Plex started then immediately crashed.
Looking at the logs plex definitely sees the network change but still crashes

Here are the new logs

You are definitely generating crash reports.

NOT cool.

Jun 09, 2022 19:45:58.638 [0x7fd2b7735700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jun 09, 2022 19:45:59.083 [0x7fd2b7735700] DEBUG - HTTP 200 response from GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jun 09, 2022 19:45:59.382 [0x7fd2b7735700] DEBUG - Job running: '/volume2/@appstore/Plex Media Server/CrashUploader' '--directory=/volume2/Plex/Library/Application Support/Plex Media Server/Crash Reports/1.18.5.2309-f5213a238' '--version=1.18.5.2309-f5213a238' '--platform=Linux' '--platformVersion=DSM 6.2.4.25556-3' '--serverUuid=272aa85f2fbbd92acb08d4f435085f56d85d41ba' '--userId=EMAIL_OMITTED' '--sentryUrl=https://sentry.io/api/1233455/minidump' '--sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' '--vendor=Synology' '--model=x86_64' '--device=DS416play'
Jun 09, 2022 19:45:59.394 [0x7fd2b7735700] DEBUG - Jobs: Starting child process with pid 11879
Jun 09, 2022 19:45:59.440 [0x7fd2bfa30700] DEBUG - Jobs: '/volume2/@appstore/Plex Media Server/CrashUploader' exit code for process 11879 is 0 (success)
Jun 09, 2022 19:46:07.707 [0x7fd2b62b3700] DEBUG - DVR:Device: Discovering and refreshing all devices

Now to figure out why.

So I had a hunch after reading the logs. I had previously been using several plugins with plex (webtoold, trakt, export tools, audiobook metadata support, youtube agent). Even though plugin support had officially been discontinued I hadn’t seen any adverse effects but maybe it was having some effect now.
To test this I removed the plugin .bundle files from the Plug-ins folder (all but Services.bundle which I believe is official?) and tried to start plex again.

It starts and stays running!
However the metadata is still not loading up and the server is ‘unreachable’
image

here are the logs
Plex Media Server.log (51.4 KB)

Oh I also made sure the permissions were correct again by following your directions from before

Let’s try it this way.

  1. Stop it
  2. Rename AppData to AppData.hold
  3. Create folder AppData
  4. Set the permissions (owner) to PlexMediaServer:PlexMediaServer in FileStation
  5. Let it start a new TEST server
  6. Open an incognito browser window
  7. open the Syno by http://Syno.Lan.IP.addr:32400/web
  8. Confirm it starts to setup a new server

Where is the AppData folder? Also PlexMediaServer is not a valid user or group, does that need to be created? (Previous owner as set by Plex is plex:users)

I’m sorry.

I was thinking DSM 7

On DSM 6.

  1. Rename “Library” to “Library.keep”
  2. Now start Plex
  3. It will create the new “Test” server

Continue with the incognito as above.
Remember to give this a TEST name so as to not conflict with your existing production server

Ah yea that makes sense. OK, followed the above directions and created a test server while in incognito. The server seems to be created just fine and is able to create new libraries.
image

here are the logs created from that test server
Plex Media Server.log (1.6 MB)

WOW…

Did you look at it?

It’s flip-flopping the network like crazy

Not really sure what to look for in the logs to be honest. I see a fair few network service errors even though the Test Server seemed be be operating as expected and could play media files just fine

That’s what I’m referring to. It’s telling us the network is flipflopping the connection.

Have you rebooted the syno since creating the bond adapter ?

Yes, I rebooted right after creating the bond connection. Rebooted again just now to test then ran through starting and opening up plex in incognito mode same as before. A reboot seems to have done some good, no more network errors. Here are the logs

That’s much better.

I am looking at your logs.

You have certificate issues.

Jun 09, 2022 22:13:13.573 [0x7fec8af34700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
Jun 09, 2022 22:13:13.573 [0x7fec8af34700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
Jun 09, 2022 22:13:19.602 [0x7fec8af34700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
Jun 09, 2022 22:13:19.602 [0x7fec8ac46700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown

In your setting , did you have “Secure Connections” set to REQUIRED ?

No I have Secure Connections set to PREFERRED

image

Where did that cert error come from? 192.168.1.205 seems indicated

Jun 09, 2022 22:13:23.871 [0x7fec8ac46700] DEBUG - Completed: [192.168.1.205:64956] 200 GET /myplex/account (22 live) TLS GZIP 1ms 3201 bytes (pipelined: 6)
Jun 09, 2022 22:13:26.916 [0x7fec8ac46700] DEBUG - Completed: [192.168.1.205:64930] 200 GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (19 live) TLS GZIP 20001ms 5 bytes (pipelined: 3)
Jun 09, 2022 22:13:27.598 [0x7fec8ac46700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
Jun 09, 2022 22:13:27.598 [0x7fec8ac46700] DEBUG - CERT: incomplete TLS handshake: sslv3 alert certificate unknown
Jun 09, 2022 22:13:28.216 [0x7fec8af34700] DEBUG - Completed: [192.168.1.205:64923] 200 GET /player/proxy/poll?deviceClass=pc&protocolVersion=3&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1 (17 live) TLS GZIP 20001ms 5 bytes (pipelined: 7)
Jun 09, 2022 22:13:28.231 [0x7fec8ac46700] DEBUG - Auth: authenticated user 1 as treasureChest

Do you have something playing media?

192.168.1.205 is the laptop that I opened plex on in the incognito browser. I played a media file to test and see if it worked

I do not understand where the certificate error is coming from unless you have a certificate (self signed) on your NAS ??

as yes I do have a self-signed cert. I set up a small website hosted from my NAS last year. I’ve run plex throughout that whole time with no problems though. Why would that become a problem now?

That shouldn’t be a problem.

I did just have an idea.

Open FileStation
Navigate Plex/Library.keep/Application Support/Plex Media Server (your main that we saved)

Right-click “Preferences.xml” → Open with Text Editor.

Look carefully at the Name="Value" pairs (preferences) in there.
Of interest are:

– PlexOnlineUsername
– PlexOnlineToken
– PlexOnlineEmail
– PlexOnlineHome (which is optional)

All of them should have a value in the parenthesis

Looks like PlexOnlineEmail doesn’t exist in the prefs though I do have PlexOnlineMail. Other than that they all exist and are filled out