hi i’m completely new to the forums and have no real idea of how any of this works. i hope im in the right place. title says it all. i launch plex media server and it insta crashes.
Server Version#:issue occurs on PlexMediaServer-1.40.3.8555-fef15d30c-x86_64 as well as on PlexMediaServer-1.32.7.7621-871adbd44-x86_64 when i tried installing an older version. i have tried uninstalling and reinstalling.
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled> i can provide these two most recent log files that were generated but i have no idea what verbose logging is and since i cant launch the server idk how to disable it if its on anyways, ive never has anything like this happen before. any help is greatly appreciated. thank you.
Plex Crash Uploader.log (716 Bytes)
Plex Media Server.log (8.7 KB)
There are problems with the database. It is unclear if they can be fixed.
Is this a new installation or are you trying to update an existing server?
If a new installation, with no need to save libraries, play history, etc., then perform a complete uninstall of Plex Media Server. See Plex Documentation → Uninstall Plex Media Server. You will have to delete registry keys and a folder in %LOCALAPPDATA%.
Next, go to your list of Authorized Devices and, if listed, remove the server.
Then reboot the PC and install 1.40.3.8555.
If this is an existing installation you wish to update, then try the following:
-
Uninstall PMS 1.32.7. Perform a standard uninstall - no Revo/CCleaner/etc. type uninstallers.
-
Reboot the PC.
-
Install 1.40.3.8555.
-
If you see a “503 maintenance” message that is Plex updating the database schema. Do not interrupt the process. Check back every 10 minutes or so and refresh the web page. It does not auto-update.
-
If PMS immediately crashes, then navigate to the Plex Data Folder, zip the Logs directory and upload it to the thread. Drag the zip file into the message window & wait for it to upload. It will insert at the cursor location. FYI, the log files of interest are
Plex Media Server.logand the rollovers,.1.logto .5.log. You can upload just those files instead of the zip file. -
If PMS runs, wait about 5 minutes, see if you can access server settings. If so, go to Settings → Troubleshooting and download the server log files. Attach the zip file to the thread. Even if PMS runs, there may be some issues that need to be addressed.
hmm interesting. ok so it was an existing installation. orginally i had updated to newest server version a day or two ago and was working fine last night then got on today to find it infinite crashing. at which point i tried restarting my pc then reinstalled version 1.4 then downgraded versions to 1.32 since it was still crashing and i figured myabe an update did something. at which point it did some database update stuff. then went back to crashing. but i did what you said just now. uninstalled 1.32 rebooted install 1.40 and waiting for it to do its thing. and it seems to be functional now. heres the log files from the torubleshooting settings section you mentioned. (i think)
Plex Media Server.log (659.1 KB)
Plex Media Server.1.log (8.0 KB)
Plex Media Server.log (8.7 KB)
Plex Media Server.3.log (8.4 KB)
Plex Media Server.4.log (150.0 KB)
part 2 of my reply with the final log file. hopefully everything is good now. but since im here anyways i figure i may as well drop those and see if you see any issue i should know about.
Plex Media Server.5.log (2.3 KB)
The log file looks good. No database errors.
Scan all the libraries to make sure PMS has picked up all the media files (just me being overly cautious).
The 1.40.0 and 1.40.2 releases introduced a lot of database changes. Do not try to fall back to a version earlier than 1.40.0.
The release notes say you can go as far back as 1.32.1. However, the error messages I noticed earlier were due to the migration process not completing correctly (when you tried to fall back to 1.32.7). Hence, the suggestion to not fall back to something earlier than 1.40.0.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
