My Plex has stopped running on my Synology NAS a couple of times in the past month. Does anyone know why?
Without seeing the log files, collected immediately after a restart, it’s impossible to know why.
Might you be able to capture them the next time?
- Settings - Server - General - Show Advanced
- Ensure “DEBUG” logging is enabled
- Ensure “VERBOSE” logging is disabled
- SAVE if you make changes
Next, after the restart,
- wait 2 minutes
- Download the logs (ZIP file)
- Attach it here for review
I’m not sure how to download the logs? I can copy and paste them, but I don’t know if that is the best option since it is so much info. Sorry for the ignorance. Thanks.
Follow the steps here Plex Media Server Logs | Plex Support to get the log files ChuckPa is asking for.
-Shark2k
Got it. Thanks.
1 Like
Plex Media Server Logs_2021-10-31_14-05-43.zip (4.9 MB)
So, if this happens again, should I download another log since this one didn’t give any info?
I suppose this doesn’t have any info to help? 
#metoo
Hello Chuck. Thanks for the offer of help. I updated my Asustor yesterday to the latest version 3.5.7.RKU2. I have a AS-304T which is getting a little old but should surely work for (mostly) music. It is so unreliable my kid refuses to use it for movies 
The Asustor server is reliable but Plex has been a POS which is very disappointing.
Plex has been very unreliable for many months (or more). Plex stopped again overnight. This is the log file zipped for me. My NMS said the Plex service stopped working at about 4:00 am (Sydney time). I manually stopped Plex and then restarted to make it work again.
PLEASE!!!
- Settings - Server - General - Show Advanced
- Turn VERBOSE logging OFF again. (It is OFF by default)
- I can’t see anything because verbose logging can only retain 2-3 minutes of elapsed time (Log file sizes are fixed).
Please keep DEBUG ON, VERBOSE OFF unless otherwise requested.
Once done, let’s see if we can capture another set?
1 Like
Thank you, onto it. Will wait for the next crash. And as luck would have it, been running perfectly all day. New agents are running. Faultless for 36 hours but it just crashed again…
removed
Bumping this one up
I saw your post last night. Still trying to figure out what’s going on.
I’m not seeing the OOM errors that others are reporting.
1 Like
Thanks. I was having a look through the logs and by now means am I an expert in reviewing those, but I did see something about Plug-in not found, shutting down plugin etc.
I don’t use any plugins either…
You’re an expert? You’re hired! 
The logs are really difficult to read a times because there’s so much multi-threaded activity being written to them.
We actually have tools for reading and analyzing them… Still makes it tough at times to figure out what’s really happening.
I would appreciate if you go to your Synology and ensure your Locale / Region information is setup. Your logs are coming through without UTF-8 encoding set but are indeed UTF-8 characters. It cause the wrong code page / character set to be displayed when first opening. I got UTF-16 for one of them (Chinese)
Your logs don’t show any OOM error I’ve been tracking.
I don’t even see what failed to generate the crash.
I’d need the DMP file (crash uploading turned off) to figure that out.
1 Like
Lmao oops!! I am by no means an expert***
I will check what you said to check in Synology and report back if I run into another crash.
This has happened to me as well. All of a sudden I would look at Plex, and none of my libraries are found and it says it can’t find the server. When I open up DSM, PMS is no longer running at all. When I click run, it turns back on, and then is immediately working fine. It’s crashed about three times today. I’m running DSM7 (updated on Saturday I believe).
No one was watching/trying to watch anything any time it happened, and the only process that was running was Sonic Analysis (it’s been doing the big one for about a month as I had 8k albums or so, down to the last 1k now) and I have it set to run it 24/7 until it finishes. Not sure if that’s the culprit, but I saw another person in the other thread say they were also running it when it crashed
Scanned the log files, and saw one WARNING (core:541) - Unable to retrieve the machine identifier or server version. in the agents.lastfm file following a local loopback call, so that might have captured something ??
And I am totally not an expert either, concrete engineer 
removed
