PlexMediaServer-1.18.1.1973-0f4abfbcc-x86_64 crashed my Synology Nas

Plex Media Server NAS & Devices
1

I updated to latest version of PMS, and lost contact to server completely. Reset wifi/router.unplugged all devices, tried webapp - no dice.

Tried claimit. Can’t connect. Looks like latest update crashed on my DS218+. When I return to DSM after claimit, it’s always stopped already.

Really awesome this happened hours before Game 7 of WS. Really awesome.

Server Version#:1.18.1.1973 (uldated today)
Player Version#:
DSM # DSM 6.2.2-24922 Update 3
DS218+

2

It didn’t crash but I noticed that it’s running my Synology CPU at like 99%… so I have to ‘stop’ the service, let everything calm down, and then run it again.

3

Hi, for me it’s something similar, no crash but pms use 40-50% cpu and 4.57g of ram.
It’s seems very high ,no ?

EDIT: after a nas reboot everything back to normal. I don’t understand what happened ?

4

I rebooted it just now, and it still crashes after about a minute of run time.

So frustrating. Was working well before.

Please assist me with a fix, Plex Support!

5

File Station - Plex share

Drill down until you see the Logs directory.

Right click it, -> Compress to Logs.zip

Attach the ZIP please

6

I can’t find anything in my plex library.

DSM1
DSM1942×531 22.2 KB

7

Not the Plex directory under there please.

  1. Control Panel - Shared Folders - EDIT the Plex share
  2. Permissions tab
  3. Give your Username permission to R/W the Plex share
  4. Return to FileStation.
  5. The Plex share will be listed in the left Pane.
8

Logs.zip (1.2 MB)

9

Exactly same situation here, only on DS412+, running same version of DSM and Server Version as Mbrett.

Stopping/restarting the Plex package or rebooting the NAS has only temporary effect. Within minutes I’m back to the same situation: server unreachable and but extremely high usage of RAM

10

@mbrett

Thanks, I found it.

Oct 31, 2019 12:40:18.262 [0x7f87125e5740] ERROR - SQLITE3:(nil), 11, database corruption at line 68035 of [bf8c1b2b7a]

In the Databases directory (Plex Media Server/Plug-in Support/Databases), you should find a backup of your database (assuming scheduled tasks ran normally).

Using that file and this procedure will get you running again.

11

I did find a backup, I believe. Although I don’t know exactly what file I’m looking for in the Databases folder.

How do I fix this from within the DS218.+? The directions are for Windows/Mac/Linux. OSs. My server is on the DS218+… I imagine it is running a Linux derivative, but I’m not sure which.

12

Synology uses Linux.

In the Databases directory, you’ll find something like this:

# ls -la
total 604M
drwxr-xr-x 2 admin administrators 4.0K 2019-10-30 03:20 ./
drwxr-xr-x 7 admin administrators 4.0K 2019-09-18 19:18 ../
-rw-r--r-- 1 admin administrators  68K 2019-10-18 19:50 com.plexapp.dlna.db
-rw-r--r-- 1 admin administrators  32K 2019-10-18 19:50 com.plexapp.dlna.db-shm
-rw-r--r-- 1 admin administrators 286K 2019-10-18 19:50 com.plexapp.dlna.db-wal
-rw-r--r-- 1 admin administrators 327K 2019-10-24 17:26 com.plexapp.plugins.library.blobs.db
-rw-r--r-- 1 admin administrators 327K 2019-10-20 02:00 com.plexapp.plugins.library.blobs.db-2019-10-20
-rw-r--r-- 1 admin administrators 327K 2019-10-23 02:00 com.plexapp.plugins.library.blobs.db-2019-10-23
-rw-r--r-- 1 admin administrators 327K 2019-10-26 02:02 com.plexapp.plugins.library.blobs.db-2019-10-26
-rw-r--r-- 1 admin administrators 327K 2019-10-29 02:04 com.plexapp.plugins.library.blobs.db-2019-10-29
-rw-r--r-- 1 admin administrators 111M 2019-10-30 03:20 com.plexapp.plugins.library.db
-rw-r--r-- 1 admin administrators 135M 2019-10-20 02:00 com.plexapp.plugins.library.db-2019-10-20
-rw-r--r-- 1 admin administrators 135M 2019-10-23 02:00 com.plexapp.plugins.library.db-2019-10-23
-rw-r--r-- 1 admin administrators 111M 2019-10-26 02:02 com.plexapp.plugins.library.db-2019-10-26
-rw-r--r-- 1 admin administrators 111M 2019-10-29 02:04 com.plexapp.plugins.library.db-2019-10-29
#

On Synology:

  1. Sign in
  2. Elevate to root privilege wtih: sudo -su root
  3. Now go to the directory

cd "/volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases"

  1. ls -la (this gives you a directory listing so you can see what you’re working with)

  2. mv com.plexapp.plugins.library.db com.plexapp.plugins.library.db-corrupt

  3. cp com.plexapp.plugins.library.db-(use most recent date) com.plexapp.plugins.library.db

  4. chown plex:users com.plexapp.plugins.library.db

This does the following:

  1. moves the corrupt one (which you can delete later) out of the way
  2. Copyies the last known good to be the default name.
  3. Makes certain user plex has permission to read/write it (linux permissions will make it owned by the admin without this command)

At this point, leaving the ssh session open, You can start plex and see where you stand.

Alternatively,

You can do this with FileStation if you Prefer.
The choice is yours. The GUI might be a lot easier.

  • Just remember to give your username R/W permission
  • Remember to right-click and go to Properties to give user Plex ownership of the new database file. Linux is very strict on these things.
13

OK. I’m a bit over my head here. I’m not unfamiliar with command line in Windows or Linux, but this seems super complicated. I don’t even know how to open terminal in DM.

Is there a way to do a complete fresh install? Further, is it better to have Plex server on PC (where I’ve never had any problems), and just point to media files on NAS?

14

OK, did it through File Station. Appears to have worked. Plex is running.

16

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