Server Version#: 1.28.2.6106
Player Version#: 4.87.2
Since yesterday, Plex Media Server has been crashing every few minutes. I have tried rolling back to a previous version, uninstalling and reinstalling the latest version, and rebooting the computer. The only change in the system since yesterday was when I reset my password and reclaimed my server.
-Deleted logs to get ones with debug on-
Two items:
Logging Level
Debug level logging is turned off, which limits visibility to what is happening on the server.
If the server will stay up long enough, please reenable debug logging.
Settings → Server_Name → General + Show Advanced
See Advanced, Hidden Server Settings for details on using regedit. You want to set logDebug = 1.
After changing the debug level, upload a new set of log files that captures the system crashing.
Sync Lists
There are twelve old sync lists trying to sync media files that no longer exist.
Example from Plex Media Server.log:
Aug 25, 2022 10:19:16.512 [2120] ERROR - LPE: unknown item 1799647.
Aug 25, 2022 10:19:16.512 [2120] ERROR - Sync: failed to generate query for path library://26ecaa7f-3be1-42af-9cd8-7464ccc1e925/item/%2Flibrary%2Fmetadata%2F1799647 in sync item 38303283
Aug 25, 2022 10:19:16.512 [2120] ERROR - Sync: empty sync set, unable to update status for sync list 22137608, sync item 38303283
I do not know if this is causing the crashes, but it cannot be helping things.
If possible, remove these sync jobs from the server.
Hey FordGuy,
Thank you for your fast response! I’ve turned on debug logging, just waiting for another crash so I can pull the logs then. I don’t have any pending sync jobs, and I’m not sure how to clear the sync lists?
EDIT: Ok, it crashed, here are the new logs!
Plex Media Server Logs_2022-08-25_11-38-17.zip (583.2 KB)
Thanks for the log files.
The crash is visible at the end of Plex Media Server.1.log, but I cannot tell why the crash occurred.
The server was transcoding an episode of 3rd Rock and it just quit (E14 - This Little Dick Went to Market). See log entries below.
I hate to ask, but could you wait for the next crash and upload another set of log files. This was the first crash captured with debug level logs. Maybe the next will show some similarities.
The last of the errors about stale sync jobs was several minutes before the crash. I’ll keep researching that as well.
Thanks.
Here’s the last few lines of Plex Media Server.1.log. It is transcoding the episode, then something goes wrong and the crash reporter runs.
Aug 25, 2022 11:37:04.873 [9544] DEBUG - [Req#29ae/Transcode/i2oa3qjubneykoyl4ex7z9h9] Asked for segment 299 from session.
Aug 25, 2022 11:37:04.873 [9544] DEBUG - [Req#29ae/Transcode/i2oa3qjubneykoyl4ex7z9h9] Returning segment 299 from session
Aug 25, 2022 11:37:04.873 [4108] DEBUG - [Req#29fa/Transcode/i2oa3qjubneykoyl4ex7z9h9/5d0353e0-49fe-44d4-8064-a56fb3cdf09d] Session i2oa3qjubneykoyl4ex7z9h9 (4) is unthrottling
Aug 25, 2022 11:37:04.873 [9728] DEBUG - Content-Length of C:\Users\nickw\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-i2oa3qjubneykoyl4ex7z9h9-5d0353e0-49fe-44d4-8064-a56fb3cdf09d\init-stream1.m4s,C:\Users\nickw\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-i2oa3qjubneykoyl4ex7z9h9-5d0353e0-49fe-44d4-8064-a56fb3cdf09d\chunk-stream1-00300.m4s is 25394 (of total: 25394).
Aug 25, 2022 11:37:04.873 [9544] DEBUG - Content-Length of C:\Users\nickw\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-i2oa3qjubneykoyl4ex7z9h9-5d0353e0-49fe-44d4-8064-a56fb3cdf09d\init-stream0.m4s,C:\Users\nickw\AppData\Local\Plex Media Server\Cache\Transcode\Sessions\plex-transcode-i2oa3qjubneykoyl4ex7z9h9-5d0353e0-49fe-44d4-8064-a56fb3cdf09d\chunk-stream0-00300.m4s is 2738715 (of total: 2738715).
Aug 25, 2022 11:37:05.135 [17300] DEBUG - [JobRunner] Job running: "C:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe" "--directory=C:\Users\nickw\AppData\Local\Plex Media Server\Crash Reports\1.28.2.6106-44a5bbd28" --version=1.28.2.6106-44a5bbd28 --platform=Windows "--platformVersion=10.0 (Build 19044)" --serverUuid=027e977e7083dfbbfc59c4111581955cc203df43 --userId=nick.wolf@gmail.com --sentryUrl=https://sentry.io/api/1233455/minidump --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Microsoft --model=x64 --device=PC --allowRetries=0
Aug 25, 2022 11:37:05.143 [17300] DEBUG - [JobRunner] Jobs: Starting child process with pid 6368
Sure! I’ll run it now. I’ll play the same episode to see if it triggers it.
A quick update.
Good News: The sync messages are not the problem.
Bad news: Not sure what caused the server to crash.
A Request:
Send Crash Reports to Plex and Save Changes.If/when the server crashes, upload both the server logs and the crash report.
%LOCALAPPDATA%\Plex Media Server\Crash Reports.Write back if you’ve any questions about this.
Thanks.
Thanks Ford, I’ll do that now. Sorry for the delay, it hasn’t crashed yet ( 
) and it looks like my wife has covid, so I might have to work on this a little later. I appreciate your help here.
I’m pretty sure family health takes priority…
No crashes are a good thing and whenever you get to it is fine.
Stay well & hope your wife is better soon.
Still enjoying covid, but we had a crash last night, and the drugs are working enough for me to pull some logs! Fun fact, the oldest folder in my Crash Report folder is from 2015.
1.28.2.6106-44a5bbd28.zip (113.8 KB)
Plex Media Server Logs_2022-08-29_12-54-02.zip (643.3 KB)
Thanks for the files.
Looking at the log files, it looks like there is a Nvidia card used for transcoding.
If so, what model?
Also, if it is a consumer card (GTX, etc), any chance you are using the modified drivers to get past the three transcode limit?
There are some CUDA out of memory errors in the log files. Wondering what might be causing them.
Still investigating. Just something I noticed in the log files.
Hey Ford,
It’s a GTX 970, but I’m not using modified drivers, I didn’t even realize that was possible. If that’s not the cause of the crash, I may look into those later, it would be nice to squeeze out some more transcodes…
Had a bunch of weird behavior last night and today, where I was getting “Successful database backup messages” every 20 minutes. I’ve attached logs in case they help determine the issue. Nothing in the crash logs folder.
Plex Media Server Logs_2022-09-01_09-44-43.zip (525.1 KB)
I’m having the same issue with the latest update as this thread. I’ve since rolled back to PlexMediaServer-1.27.2.5929-a806c5905-x86.
New crash log from today
376edaec-de57-4fb9-a84c-550aff21edf3.zip (46.6 KB)
Just want to flag that my Plex server is still crashing frequently. I went ahead and updated to 1.29, and it crashed clearing bundles.
**Edit: Yup, if I go to troubleshooting > Clean Bundles, I get a hard crash. Crash report folder is empty.
“Clean Bundles” crashes my server every time I click it too
This is the final line in my logs after a crash:
Sep 15, 2022 15:04:32.286 [13144] DEBUG - Activity: updated activity 1028087c-0788-47dd-a3fb-55faf9ee360f - completed 0.0% - Cleaning bundles
I have a problem with Plex crashing shortly after I start to clean bundles. Using 64-bit Windows server and the recent version 1.29.0.6244 had no impact on the problem. Have repaired the DB with the included plex sql tool and also tried a rebuild.
Will not being able to clean bundles eventually become a problem? I do have some movement in and out of the library and Plex keeps a bunch of files for each media file iirc.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
