Gee it might be good to not throw away the old guide data till the new guide is 100% downloaded/verified

That way things like a flakey setup as is happening right now, doesn’t nuke everything. This is kinda sad state of affairs to toss away the whole guide each time - I guess it doesn’t do incremental updates, 100% each time and throws away your data first.

1 Like

Time for someone to write an XML/Json merge - what ever format your new data comes down in, merge it with the existing data - then insert/replace things. That way if the merge fails - you still have your old data.

I remember doing stuff like this way way back building my own guide data for a custom code I had written before I found Tivo - we have been Tivo users for many years and the thing they did well was reliability. Hoping Plex can get to that level and I won’t have to resort to reviving my old software.

The regular incremental update guide should only result in a portion of the guide disappearing in event of failure. If the issue remains over a long period eg one or two weeks then the guide data will eventually all disappear.

Do you have evidence of fully populated guide being emptied after a failure ? Would need logs and ideally copy of the epg database before and after - the database files are within Plug-in Support\Databases within the Plex Media Server data area and have names starting with tv.plex

For info

There was an issue giving rise to JSON Parse Error where the response for the guide refresh contained error 403 Forbidden. This should be fixed now.
Plex Media Server beta 1.14.0.5465 has retries for failed requests to fetch the guide - so that in itself would have helped whilst the issue was there
Please do manual update to the guide and once that completes ok, then incremental updates would ensure the guide remains up to date

If problems persist, please provide fresh logs from the server with debug logging enabled beforehand and also a zip of the Diagnostics directory which is within the Plex Media Server data area
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/

Well all I can say is once I saw you were having epg problems, my guide was empty – totally – I’ll see if I have enough logs – I upped it to 500 files (got lots of space) but I on’tt hink it goes back ‘2’ weeks which is what we would need.

Some sort of alarm/warning etc is needed then to wake people up to the situation/problem.

If you had that JSON Parse Error there would be files within the Diagnostics directory and you can check date and times

Verified files in that directory from the 7th to 14th

All with { “message”: “Request forbidden by administrative rules”, “__Type”: “CloudSearchException” }

Any typos are mine – having to transcribe from other machine, not easily accessible from this one.

But even then – it should have had ‘7’ days of epg – right? It does 2 weeks usually?

I will discuss with the development team

Yes it is 14 days. But the incremental periodic updates that are done every 4 hours would only address the next 12 hours and also extend the data at the end to reach Today + 14 days.

If there has been an outage or issues with data then after the issue gets resolved, it is necessary to do a manual full refresh - as was advised by me in the forum threads that reported the JSON Parse Errors

The problem is now fixed - see my latest post here Epg guide not loading any listings. also plex now giving me for hd homerun tuner a wan address instead of my local 192. address - #13 by sa2000

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