Plex media Server manually stopped in Synology NAS

Plex Media Server NAS & Devices
31

@asangaxp

Thank you. That’s the output I was hoping for.

What is CodecPack?

Are you using VideoStation as well concurrently with PMS ?

The log shows PMS running for 2 minutes.
This is more than enough time for your PMS logs to be written to.
If there are no logs then we know the problem.

2022/10/11 16:40:39 start PlexMediaServer 1.29.1.6276-7000 Begin start-stop-status start
2022/10/11 16:41:01 start PlexMediaServer 1.29.1.6276-7000 End start-stop-status start ret=[0]
2022/10/11 16:41:02 start PlexMediaServer: start version 1.29.1.6276-7000 successfully, result 0
2022/10/11 16:43:17 start PlexMediaServer: begin to stop due to abnormal status
2022/10/11 16:43:17 start PlexMediaServer: begin to stop version 1.29.1.6276-7000
2022/10/11 16:43:17 start PlexMediaServer 1.29.1.6276-7000 Begin start-stop-status stop
2022/10/11 16:43:17 start PlexMediaServer 1.29.1.6276-7000 End start-stop-status stop ret=[0]
32

Hi @ChuckPa . I am unsure what CodecPack and I cannot see wither this or VideoStation in my list of applicaions

Screenshot 1
Screenshot 1911×549 62.1 KB

As for PMS Logs, I cannot see this appearing in my Plex Web App

Screenshot 2
Screenshot 21026×487 31.2 KB

33

As far as logs go, scroll up to post 2 and 3.
Maybe Advanced Media Extensions wraps in Codec Pack according to

34

Hi @nibbles and @ChuckPa
Ok I got it thanks, I have re-attached the PMS logs as per the earlier posts
Logs (1).zip (7.6 MB)

1 Like
35

Hi, was this problem resolved? this is the last post I can see and I have the same issue.

36

Yes it is fixed now thanks to @ChuckPa it was a bug in the software if I am not mistaken

37

I am having the EXACT same issue right now and am feeling very frustrated. I’ve read through this whole post and am not understanding how it was resolved?

38

Manually stopped is a major error.

Make a ZIP file of the Logs folder under “Plex Media Server”

attach it here please

39

Logs.zip (1.2 MB)
Here you go! I’m hoping this has everything you need.

40

The one I attached above was from the most recent uninstall/reinstall, where I tried the “claim lost token” route. I do have a copy of the logs from before that uninstall—attaching that one here.
Logs2.zip (5.4 MB)

41

This log… NOT GOOD.

We need to do some fixing, Lucy!

Jan 14, 2023 09:19:37.287 [0x7f9bb9e880d0] INFO - SQLITE3:0x80000001, 283, recovered 239 frames from WAL file /var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - SQLITE3:0x80000001, 11, statement aborts at 10: [] database disk image is malformed
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - SQLITE3:0x80000001, 11, database disk image is malformed in "PRAGMA cache_size=2048"
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - SQLITE3:0x80000001, 11, database corruption at line 61875 of [1b256d97b5]
Jan 14, 2023 09:19:37.289 [0x7f9bb9e880d0] ERROR - Database corruption: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2048

Changing cache size isn’t always the answer.
If the DB is fragmented, it can easily be fixed and you can go back to the default which does work the best.

42

Dang! Not sure how everything got so messed up. How do I easily fix the fragmented DB? Right now all drives are reading healthy. Should I scrub all the data?

43

This is something you had set.

PMS default is 40.
I have a tool which will both reorg & repack the db. As a consequence, that size will be reset to default.

what would you like to do?

44

Assuming that is a paid service? Is there a way to direct message you? I’m happy to pay to have this fixed by someone who knows what they’re doing and clearly you do.

PMS default is 40 on cache size? So when I increased the cache size it screwed it all up? I don’t fully understand still. Just willing to do what it takes to recover my server.

45

No, not a paid service.

I wrote a tool, with instructions, and placed it on Github.

Click ‘Releases’, download the ZIP file or tar.gz (your preference), put it on the Syno, extract and run (as ‘root’ user - not an administrative user)

The README.md is full of examples and info.

For you, I recommend the sequence 1, 4, and 3 then exit.
( will make sense when you see the tool )

46

Ok sounds good. I’ll give it a go! Might take me a minute to figure it all out and will come back with questions as needed. Thanks, Chuck!

47

Actually - quick clarification. Does it matter if I change the PMS location after the fix? I want the server hosted on a storage pool with 4 drives to ensure longevity. The logs I sent through above have it hosted on a single drive not apart of the larger storage pool. I’m going to move the file location to Volume 2 and then do this fix? So long as that won’t majorly mess with the way your tool works…

48

longevity meaning, if a drive fails I won’t have to lose my server due to a degraded storage pool. Which has happened to me twice. If it’s on the larger storage pool with 4 drives if one corrupts I won’t have to move my server.

49

What do you mean? Move the shared folder using Control Panel - Shared Folder method?

50

correct