Server Version#: PlexMediaServer-1.40.0.7998 and previous version
Plex stopped working suddenly 1 day ago, was on 1.29.2.6364. Every time I try to run it on my NAS it stops and says “Manually Stopped”
Tried uninstalling, restarting NAS, and installing 1.40.0.7998, same thing happens.
The first thing someone is going to request is your log files. You can attach them here to your post in the forum. Here’s how to get them, manually.
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Good Luck
Chris
Thank you. I’ve been running Plex on NAS for a while but have not had to do much troubleshooting so I’m new to this.
Logs.zip (393.9 KB)
From Plex Media Server.log:
Feb 16, 2024 10:33:56.798 [140079610399376] ERROR - SQLITE3:0x80000001, 11, database corruption at line 70168 of [a29f994989]
Feb 16, 2024 10:33:56.798 [140079610399376] ERROR - SQLITE3:0x80000001, 11, database disk image is malformed in "PRAGMA cache_size=2048"
You’ve database corruption. It is bad enough that Plex Media Server refuses to run.
Option: Plex DBRepair Utility
If you are familiar with the Linux CLI, use the Plex DBRepair Utility [Download].
Run it as root. Use the AUTOMATIC option. If it runs into problems importing the database, try the IGNORE option.
If the repair fails, try the REPLACE option, to restore a backup copy of the database.
Option: Restore from backup with FileStation.
If you are not comfortable with the Linux CLI, you can try to restore from a backup using Synology File Station.
Note that this procedure does not check for database corruption, so it is possible that the backup may also be corrupt.
See FAQ 30 - DSM 7 - Database Repair using a Backup copy.
Option: Delete and start over
If the database cannot be repaired and no viable backup exists, then you can delete the database.
You will have to re-create all libraries and reshare them with any friends/family.
To delete the databases:
So far so good, I did the Restore from backup with FileStation, and Plex is now running. When I click on Open I get:
Not authorized
You do not have access to this server.
You may be able to claim it by choosing “Open Plex…” from the Plex menu in the macOS menu bar or Windows system tray. For more troubleshooting tips, see our support article.
I looked at the support article referenced but there is no entry for NAS, I looked at the Preferences.xml described in the Linux section but I don’t see those entries.
Your upgrade jumped too many versions. You will need to bump up slowly. Revert back to your previous one and work up slowly.
No. It is not possible to revert to 1.29.2 from 1.40. Too many database changes.
See release notes: Plex Media Server - #612 by drzoidberg33
Point a private/incognito browser at the IP address of the NAS.
For example, if the IP address is 10.1.2.3, use http://10.1.2.3:32400/web.
Use http, not https.
Don’t forget the /web part.
Incognito is to bypass any browser plug-ins that may get in the way.
Nevermind! I got it. I followed the FAQ 31: Reset / Reclaim PMS on DSM 7 (Not Authorized - Locked Out) article and got it reinstalled with the Token.
I’m back in - THANK YOU SO MUCH FOR YOUR HELP
Glad it is working.
You should still pull the server log files and check for database corruption.
Look in Plex Media Server.log for the same type of entries in my first reply. You can search for corruption or malformed.
There are levels of corruption.
PMS may still run with a slightly corrupt db. However, you may see problems trying to add media to the server, create/delete libraries, etc.
The corruption will not fix itself and will only get worse over time. If bad enough, then PMS will not run (as you experienced).
Not trying to be a harbinger of doom. Just better safe than sorry. 
A search for those two words is not coming up with anything.
If it does continue what does that mean? Disks are bad? My media has been corrupted? or the Plex DB needs to be wiped out and rebuilt?
Then you’re good to go. No need to worry that the current db is corrupt.
Database corruption does not mean your media, drives, etc. have problems.
Database corruption usually occurs when Plex Media Server quits abnormally while reading/writing to the db.
An easy example is a power failure which crashes the NAS. The database files would not be closed correctly and the structure of the information is damaged.
There can be other causes as well.
Corruption can usually be fixed using the methods mentioned above.
It is something of which to be aware, but do not worry about it. It is a good idea to check the log files before performing a major PMS update. For example, the 1.40 release notes specifically mention database changes.
Plex Media Server can notify you, via a Plex mobile app, when it detects corruption.
In Settings → General, enable Push Notifications.
In the Plex mobile app, Settings → Notifications → Database Corruption Detected.
Same problem . here’s the crash log
Feb 27, 2024 10:49:52.574 [0x7f221fe72808] ERROR - Too many crashdumps detected / retries disallowed!
Latest DSM and Plex reinstalled today . Before setting permissions in Control Panel, I would RUN the Plex app , and after about 10 seconds it would shut down. After setting permissions, it takes a bit longer but still shuts down “Manually”
Just found this as part of a log;
Feb 27, 2024 10:49:32.904 [0x7f397c66fb38] DEBUG - [JobRunner] Job running: /volume1/@appstore/PlexMediaServer/CrashUploader “–directory=/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Crash Reports/1.29.2.6364-6d72b0cf6” --version=1.29.2.6364-6d72b0cf6 --platform=Linux “–platformVersion=DSM 7.2.1.69057-4” --serverUuid=6be6324ef4284debbb3721cbc37ef08ed1d91fad --userId=NOUSERID --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/minidump/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Synology --model=x86_64 --device=DS920+ --allowRetries=0
Feb 27, 2024 10:49:32.905 [0x7f397c66fb38] DEBUG - [JobRunner] Jobs: Starting child process with pid 4323
I’m concerned about the second to last line “allow Retries=0” Could that cause the Manual Shut Downs?
Using FileStation,
Navigate to PlexMediaServer shared folder and drill down until you see the “Logs” folder.
Right-click → Compress to Logs.zip
Download that zip and attach here
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
