Plex Media Server Crashing Refreshing Guide Data

For the past two weeks, my Plex Media Server on WIndows 7 is crashing after 5-10 minutes after starting. The last entry in the server log is consistent across all crashes and seems to be related to the Live TV guide (I’ve removed the Live TV/DVR hooked to my HDHomeRun and the server stays alive). The JSON parse error shows up many times in the file, but the crashed server log always ends with these lines:

Aug 26, 2018 19:27:46.648 [10200] DEBUG - Beginning read from two-way stream.
Aug 26, 2018 19:27:46.835 [9568] DEBUG - EPG: Found a dupe show ‘New Larry King Update: Is Your Credit In Crisis’ with a different GUID.
Aug 26, 2018 19:27:54.118 [10376] DEBUG - EPG[onconnect]: Purging 0 airings which completed in the past.
Aug 26, 2018 19:27:54.226 [9568] DEBUG - JSON parse error: Invalid value. (0)
Aug 26, 2018 19:27:54.233 [9568] DEBUG - JSON parse error: Invalid value. (0)
Aug 26, 2018 19:27:54.568 [9568] DEBUG - JSON parse error: Invalid value. (0)
Aug 26, 2018 19:27:54.575 [9568] DEBUG - JSON parse error: Invalid value. (0)
Aug 26, 2018 19:28:04.961 [11224] DEBUG - Job running: J:\Program Files (x86)\Plex\Plex Media Server\CrashUploader.exe “–directory=J:\Users\Todd\AppData\Local\Plex Media Server\Crash Reports\1.13.5.5332-21ab172de” --version=1.13.5.5332-21ab172de “–platform=windows-i386 (6.1 (Build 7601))” --serverUuid=3bab5e6212e4be29f4dd0ded6f63861137ff9250 --userId=marvin826@comcast.net --url=https://crashreport.plexapp.com
Aug 26, 2018 19:28:04.972 [11224] DEBUG - Jobs: Starting child process with pid 6004

Anyone else see this or have any suggestions? I did cut down the number of channels to those I care about (maybe 100?) and I did delete my epg database, but no luck.

Any suggestions would be great!

I have 3 HDHomeRun receivers, and have only added one to my current Plex Server. Plex Logs state errors for the HDHomeRun Devieces that are not connected to the Internet and have never been added to the system. I was playing with the idea of adding HDHomeRun to a separate unrouted VLAN with Direct Connection to Plex. HDHomeRun freaks out will never allow any non-internet connected HDHomeRun work; so it has to have a constant connection to the Internet and to http://my.hdhomerun.com/ Make sure this URL shows no errors and the Receiver is listed. Even if you add a Receiver in Plex, if it is not on this page, Plex ignores its existence.

Also, check DLNA Logs. I noticed my DLNA log started a cascading failure across the Plex process. I have disabled DLNA since HDHomeRun could be causing issues with this protocol.

Could you please attach full logs zip file so the relevant dump can be found

I will. I’ll have to run it again as I uninstalled and cleaned out everything per recommendations of some other Plex users. Having reinstalled, the server has stayed up for 2 days now, but I’ve not added Live TV/DVR. I’ll do that and see what happens.

Well, my uninstall wiped out my logs (should have grabbed them first). I have slowly added libraries and then added the Live TV and DVR. I did trim down the number of channels (total available is over 500, I trimmed down to 112) and this has kept the server very stable. Very disappointing in the respect that I don’t have access to all channels, but positive in the aspect that its easier to tune to a channel on devices that don’t have a guide (like my Roku). I guess I could try to add channels and see what number (or channel) crashes it again.

An uninstall of Plex Media Server on windows does not touch the local app data area. I presume you deleted the folders yourself

That would help us find the bug

Please make sure you run with debug logging enabled in server settings

and when the crash occurs, restart and capture the logs zip and attach here
Please also check the Diagnostics folder for any content - it is a folder within the Plex Media Server local app data and is alongside the Logs folder. If there are files in the folder, please zip and include in your attachments

Thank you

You are correct - I was a bit flippant in my response. When I uninstalled, I also cleaned out all directories to ensure a clean install on the next go. I’ll add some channels in little by little and see if it crashes again.

Plex Media Server Logs_2018-10-29_11-14-49.zip (1.7 MB)
I’ m having the same issue. PMS crashes within minutes of starting unless i stop the guide refresh. then it stays up until it kicks off the guide refresh again! please help!

I need to know the setup options selected and will see if we can reproduce this. Some invalid data being received

language / zip code / country / guide option chosen /
you can send the info by private message

you could try to delete the dvr and recreate it to see if it makes a difference

Is this still happening ? Thanks for letting me have the zip code and country

I am still waiting for you to tell which guide option you selected for the source during setup. See my reply to your private messaege

I selected the following guide:

DVR—Comcast Suburbs Denver N&S - Digital

I don’t know if this is still happening. I was testing out on Windows 7 to see if Plex worked to replace Windows Media Player for my house. It did and I love it! I’ve moved to a Synology NAS as Plex is AWESOME! Have not had any guide issues there, but I’ve also reduced the guide down to just the HD channels, so the list is shorter than I was using on Windows 7, so…

Thanks for the feedback. There may have been some invalid data in the guide for some channels. I have not been able to reproduce

not sure if i is specific channels. I keep running it, and it can go from die immediately, to going past 15% (18209 airing), but then dies.

@jcbplex- Likely not the same issue the guide update failing as it isn’t crashing the whole app for us. Just failing to update the guide. This is happening to a lot (if not most) of us.

sorry if I wasn’t clear. My problem is that the EPG will not update, and it has been empty for at least a week. It is getting a JSON error, then stops EPG processing.
Nov 09, 2018 07:33:57.714 [30196] ERROR - EPG: JSON parse error. Data from request is {
“message”: “Request forbidden by administrative rules”,
“__type”: “CloudSearchException”
}

We did have a couple of users with crashes before when EPG data was updating. The crashes went away. Probably some bad unexpected data

But … the current issue that has been affecting many users is the
ERROR - EPG: JSON parse error. Wrote JSON data to xxxxxxxxx

This is currently with our metadata provider for the Guide. I do not have any updates from them yet.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.