I’ve had this server setup for a while now with no issues, however it seems like since I upgraded to PMS v 1.13.3.5223 the Plex Media Server has been crashing/stopping without warning. If using Plex the current stream will stop and buffer and eventually just stop outright. If I RDP into the Windows Server using the same user, the PMS icon still shows up in the system tray, however as soon as I mouse over it, it’s gone. It also does not show up in task manager.
I am able to restart PMS and everything works fine. I’ve uploaded the logs I took earlier today after the latest crash, however to be honest I’m not sure what I’m looking for. Any guidance on what to search for would be greatly appreciated, or if someone is kind enough to take a look and point to an issue that would be amazing.
I had the same problem, but OttoKerner could help me.
Original:
OttoKerner Plex Ninja (Moderator) 6d Hast du zufällig den Standort des Plex data folder auf ein anderes Laufwerk verschoben? Und zwar direkt auf das Wurzelverzeichnis eines Laufwerksbuchstabens, ohne einen Ordner anzugeben? Wenn ja, prüfe unter Einstellungen - Server - Allgemein - ‘Zeige erweiterte Einstellungen’ ob in “Ordner, in dem lokale Anwendungsdaten gespeichert werden” nur der Buchstabe und ein Doppelpunkt eingetragen ist, oder ob danach noch ein Backslash \ folgt. Der Backslash ist derzeit erforderlich!
Das ist bereits als Bug gemeldet, sollte also in einer zukünftigen Version wieder unkritisch sein. Aber als Workaround ist der Backslash jetzt erst mal nötig.
OttoKerner Plex Ninja (Moderator) 6d Did you happen to move the location of the Plex data folder to another drive? Directly to the root directory of a drive letter without specifying a folder? If yes, check under Settings - Server - General - ‘Show advanced settings’ whether the “folder in which local application data is stored” is the “folder in which local application data is stored”. only the letter and a colon is entered, or whether a backslash \ follows. The backslash is currently required!
This is already reported as a bug, so it should be uncritical in a future version. But as a workaround, the backslash is now necessary.
To answer sa2000’s questions:
How frequent?
Previously it seemed to crash everyday, however at around the time of the post it crashed every 10 minutes or so until I fully power cycled the server.
Anything special in your environment/server?
Not that I know of. I generally have Windows Resource Monitor open so I can quickly RDP in and see CPU and Memory usage. Only other thing I had running on it was Kiwi Syslog server (Free version 9.6) that only my NAS is pointed to. Shortly after the reboot a few days ago I turned both of these off and it hasn’t crashed. However these are not new additions to the server, they’ve both been running for many months with no previous issues.
The only other issue I have, which is probably not relevant is basically everything I record using PlexDVR has a Transcoder error and either fails, or will not playback.
I have turned both Resource Monitor and Kiwi back on to see if it’ll crash again. I thought I had a second set of logs from a previous crash, but I’m currently not able to find them. If I do or if it crashes again I’ll upload them.
Also, just to cover all the bases, to answer Zerwas’ question. I have not moved Plex or anything on the server.
So far it has not crashed again with everything “normal” turned back on. Honestly I’m at a loss for what caused it, as after the first crash I power cycled the entire server “just in case” and it crashed again a day or so later.
I’ll keep an eye on it and either update this thread with new logs, or post a new one linking to this one with new logs if this one is closed.
Again it is SSL3 related - different routine from the last one but within same module
This time the crash is in do_ssl3_write
Could you check this file properties and let me know file ./ product version from the file properties screen C:\Program Files (x86)\Plex\Plex Media Server\ssleay32.dll
Also let me have a dump of the environment variables.
In a command prompt window, dump all env variables into a text file, eg set > env_vars_2018-Aug-02.txt
and send to me
Also search the C: drive for ssleay32.dll and let me know what you find and where
I am going to pass the crash details to the development team