Hi All
I have been running PMS now for years, but for the last several months PMS run for several hours and suddenly stops , I check and see the service has stopped and needs restarting.
Also it appears the crash reports are not being sent
May 17, 2020 09:45:14.864 [0156] DEBUG - HTTP 400 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
May 17, 2020 09:45:14.864 [0156] ERROR - Failed to upload crashdump 1b0200a2-e544-4174-a5c3-de6c9cb4af20: 400
I have noticed the scanner hangs on certain folders and new content does not appear when added.
Can someone please help and check out the attached logs and give me some advise on how to resolve this issue.
Thanks in advance
Not sure if this is the need to restart, but check your system time: May 17, 2020 11:02:49.666 [5272] ERROR - Update time was too far in future. No time machines allowed.
Thanks Fordguys61
Time and date correct on my PMS not sure why this has come up , I have disabled verbose logs most probably after the log report.
Any Idea about the crash reports not being sent ?
Not sure. The task successfully ran at a later time: May 17, 2020 11:02:46.016 [9960] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe' exit code for process 8876 is 0 (success)
The real question is why is PMS stopping.
At the end of Plex Media Server.1.log, there are 985 lines with this message: May 17, 2020 09:45:09.504 [12224] ERROR - Thread: Couldn't add a new thread to the pool of size 19: boost::thread_resource_error: Resource temporarily unavailable
Plex Media Server then starts up at 11:02 (earliest entry in Plex Media Server.log).
Searching for that error message in the forum turns up many hits regarding memory allocation errors.
This is getting beyond my understanding of Plex and Windows.
Suggest the following:
Make sure your system is set for debug logs only.
After the system crashes again, pull the log files & post to the thread.
Then somebody can hopefully see what is happening to your system.
FYI, regarding verbose vs debug logs: Look at Plex Media Server.log. The file has 43871 lines, 36496 of which contain “VERBOSE” (83% of all lines). The log files have a fixed size. With verbose logs enabled, it means they will wrap very quickly (.log -> .1.log ->… .5.log --> bit bucket) and useful information may be lost.
Thanks for looking into this FG61, hopefully someone will have seen this problem before and a remedy will be available.
As I am typing the email system crashed again, attached are the logs. Plex Media Server Logs_2020-05-18_10-09-04.zip (5.1 MB)
Thanks in advance guys
I have been having similar issues as well. Enabled debug logging and disabled my auto kill/start plex exe task to see if I i can capture it in logging.
I am a little confused and or surprised that no other people have this problem, and no moderators have made comment… I guess its only the 1st week :thinking
