Excellent News that you narrowed the problem to a single album.
Your google drive link gives me an error. Could you provide me the album files as you have them in the library - you can share link by private message and i do want to see the logs with debug logging enabled after one of these crashes
Thanks
Thank you very much. It is a similar crash but in your case I do not believe we were doing video preview thumbnailing at the time - but other media analysis
The problem we have is that we are not getting any dumps created for these xc0000409 Stack overrrun crashes
@bb1200x believes it is certain media files give rise to the crashes - so that would be a good way to get us repro the failure
Lets see if the next overnight crash is processing the same item
We can work out what the item that was being refreshed by making a request in the browser to the server - but you will need to find the server token string - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
The requests for the last few items being refreshed before crashing would be
http://127.0.0.1:32400/library/metadata/383533?X-Plex-Token=xxxxxxxxxx
http://127.0.0.1:32400/library/metadata/403482?X-Plex-Token=xxxxxxxxxx
http://127.0.0.1:32400/library/metadata/431687?X-Plex-Token=xxxxxxxxxx
http://127.0.0.1:32400/library/metadata/403360?X-Plex-Token=xxxxxxxxxx
Replace the xxxxxxx with the server token
And for each copy the response to a text file and save each
Please let me have the responses and then we can see if the crash is replicated by processing these items in scheduled tasks
Also any more logs for crashes
1.15.0.659 = scan = crash, glad iām not the only one.
Joining in the Misery
1.15.0.659 on Windows 7 here. Iād attach server logs, but at this point Iām three seconds from erasing PMS altogether and demanding my annual sub refunded.
My issue i laid out elsewhere, but summarized ā Iām trying to make changes to my library setup due to an AWOL drive and changed folder positions (Iām moving everything from that drive to newer drives) and Plex is crashing with grand repeatability and not saving the changes. Itās also crashed on cleaning bundles, emptying trash, and library scans.
Iām thinking I need to roll back a few versions to one that actually works.
Optimization seems to be running okay. Next crash, thoughā¦
Oh, so I first have to uninstall and start from scratch? I canāt just roll back to an earlier version?
lets hope 1.15.1.686(or later) is released soon, this multi-times a day crashing is a headache and a first for Plex Server(for me) in 5years~ of using it
That was a very specific fix to a specific situation that arose because of the number of scheduled recordings.
If you have crashes / issues, point me to where you posted debug server logs and i will have a look
cool, where would i post? thanks!
if it is crashing and windows 10 then here - otherwise new topic and link to it from here
got it will do; running latest on server2012, so i guess a new thread and iāll put the link here; Iāve enabled debug, it last crashed overnight nite, is start some scanning and and post after the next crash/ is there anything i would need to remove from the log before posting? (any key that would relate to my account/etc)
thanks you!
server just crashed; downloaded logs to zip file; reviewing the data within; not something iād like posted to a public forum; is there another way to provide the zip file for your review?
Iāll have to start a new topic and throw logs in there, as Iām in Win7. Not for a day, thoughā¦too much crap to handle at home right now.
It is all windows - keep it here. I will edit the title
another crash; is there a way to pass you the log without posting in public?
No idea if any of these are useful, and the zip file itself seems awfully small.
Plex LOGS 02-16-2019.zip (2.1 MB)
Iāll upload a link for the database files shortly. They might be in some way instructive, I do not know. Iām probably not bothering to repair them as Iām doing the rollback.
Database :
Edited by sa2000 - link removed. database link saved
Yes both useful - the logs and db
The logs show two issues
One is the crashes and that is being investigated by the development team,
You had 9 crashes in 3 day period
The other issue appears to be to do with time to process requests and access the sqlite3 database. Requests and actions are taking far too long to process and leading to timeouts and client app failures
Having seen the database i can understand why - it is a 3Gb database with a million items. Is this on SSD Drive? If not, you should consider it
and also run a database optimize -see library actions
https://support.plex.tv/articles/200392106-library-actions/
Itās more like 70 crashes in four days. The 659 version is terribly hinky. The database issue is weirdā¦itās optimized regularly because of the size of it; it shouldnāt be a million items, even where two different libraries point to the same folders. There is currently the issue of not being ble to deleted the pointers for moved libraries, though.
Iāve rolled back to the last non-Plex Pass version - 1.14.1.5488 ā and itās staying upright thus far, although itās still reluctant to remove those old pointers. As it stands, the next library scan is going to be hellacious.
Iām going to crunch on through, however, and then set up a new box to act as a server and port everything over (as per the FAQ) in the next bit of time. The SSD suggestion is excellent, and Iāll see about getting an SSD into the new box. Had I my druthers, Iād have the libraries on SSDs, but thatāll have to wait until capacity goes up and price comes way down.
Considering I have a Mac Mini here thatās doing mostly nothing, I might even just set up Plex there. Makes it a little more of a PITA to get media from the new directory on Brain to the Mac, though.
