@sa2000 I’m having the same issue. Server log attached. Any help would be appreciated!
I use multiple clients so not sure which client logs would be useful?
Same issue here… Any help would be appreciated!
@jpirotte said:
@sa2000 I’m having the same issue. Server log attached. Any help would be appreciated!I use multiple clients so not sure which client logs would be useful?
You are getting the JSON Parsing Error when processing EPG data for the 576 channels that you have
This is the issue I already mentioned as being seen on systems with circa 600 channels. It is a Gracenote problem that has been referred to Gracenote but at the same time the Plex Devs are looking into ways to get round the problem
Feb 21, 2018 09:35:32.157 [0x7ffa8cb35700] ERROR - EPG: JSON parse error. Data from request
@rdmckinnon said:
Same issue here… Any help would be appreciated!
Same issue
Feb 21, 2018 12:56:56.652 [0x7f228a447700] ERROR - EPG: JSON parse error. Data from request is
What is different in your case is that you appear to get the issue with only 317 channels and not at the 600 level
Could you use curl to get me the JSON lineup of the channels and send me the zip code / country / territory / Provider by Private Message
To get the JSON, use curl command
curl http://192.168.7.223:80/lineup.json > tuner-linup.json
and zip the tuner-lineup.json and attach
Thanks
@sa2000 said:
@rdmckinnon said:
Same issue here… Any help would be appreciated!Same issue
Feb 21, 2018 12:56:56.652 [0x7f228a447700] ERROR - EPG: JSON parse error. Data from request isWhat is different in your case is that you appear to get the issue with only 317 channels and not at the 600 level
Could you use curl to get me the JSON lineup of the channels and send me the zip code / country / territory / Provider by Private Message
To get the JSON, use curl command
curl http://192.168.7.223:80/lineup.json > tuner-linup.jsonand zip the
tuner-lineup.jsonand attachThanks
I now have confirmation that this issue has been seen to arise with just 307 channels - so no need for the info
@sa2000 Do you think there’s any chance of a quick fix for this, or a workaround that we can perform on our own? Sounds like quite a few of us have guides that already expired or expiring at any moment.
@jpirotte said:
@sa2000 Do you think there’s any chance of a quick fix for this, or a workaround that we can perform on our own? Sounds like quite a few of us have guides that already expired or expiring at any moment.
The quick fix for me each time my recording schedule runs out is just to remove the dvr (homerun prime), restart the PC, then re-add the dvr on start up. Not the fastest thing but it seems to work most times. I’ve basically given up on channel selection at this point however from having to remove and add so often. I too only have ~300 channels.
It is unfortunate that whilst we have this Gracenote issue with updates, one needs to look at options like this.
@jpirotte said:
@sa2000 Do you think there’s any chance of a quick fix for this, or a workaround that we can perform on our own? Sounds like quite a few of us have guides that already expired or expiring at any moment.
Other option is to reduce the number of channels until there is a fix
Thanks! I ended up seeing Kiepert’s post earlier in the chain, and figured I’d give it a shot before removing the DVR, and it worked! I was assuming that since the issue was described as being on the Gracenote’s side that the json would be bad regardless of whether it was for an existing or new DVR in plex.
It really would be good for users to be notified when a guide can’t be updated and is about to expire though, thankfully for me I noticed it just in time but I’m sure that’s not always the case.
@jpirotte said:
Thanks! I ended up seeing Kiepert’s post earlier in the chain, and figured I’d give it a shot before removing the DVR, and it worked! I was assuming that since the issue was described as being on the Gracenote’s side that the json would be bad regardless of whether it was for an existing or new DVR in plex.
The bug is in how Gracenote updates/adds to the info as opposed to create it
Thanks! Hopefully they get it resolved
@vinceanido said:
@Kiepert said:
Found a work around from a Facebook group
This solved the issue for me. Thanks!
@Kiepert said:
Found a work around from a Facebook group
This work around solve the issue for me. Thanks!!!
I tried the other work around of going tthough all the channels and deleting/removing the channels causing the issue. It initially worked but within a day or two it stopped refeshing again and different channels were causing the issue. Going though 500+ channels, trying to figure out which channel is causing the issue every couple of days is too time consuming.
@shon said:
@vinceanido said:
@Kiepert said:
Found a work around from a Facebook group
This solved the issue for me. Thanks!
@Kiepert said:
Found a work around from a Facebook group
This work around solve the issue for me. Thanks!!!
I tried the other work around of going tthough all the channels and deleting/removing the channels causing the issue. It initially worked but within a day or two it stopped refeshing again and different channels were causing the issue. Going though 500+ channels, trying to figure out which channel is causing the issue every couple of days is too time consuming.
I don’t think it is channel specific - it is probably to do with the number of channels and the amount of data in the updates. It has been seen to arise with number of channels being 307 or higher
@sa2000 said:
@shon said:
@vinceanido said:
@Kiepert said:
Found a work around from a Facebook group
This solved the issue for me. Thanks!
@Kiepert said:
Found a work around from a Facebook group
This work around solve the issue for me. Thanks!!!
I tried the other work around of going tthough all the channels and deleting/removing the channels causing the issue. It initially worked but within a day or two it stopped refeshing again and different channels were causing the issue. Going though 500+ channels, trying to figure out which channel is causing the issue every couple of days is too time consuming.
I don’t think it is channel specific - it is probably to do with the number of channels and the amount of data in the updates. It has been seen to arise with number of channels being 307 or higher
I was having the issue with only 241-260 channels selected. When I went through the process of selecting and removing channels only certain channels stopped the refesh.
@shon said:
@sa2000 said:
@shon said:
@vinceanido said:
@Kiepert said:
Found a work around from a Facebook group
This solved the issue for me. Thanks!
@Kiepert said:
Found a work around from a Facebook group
This work around solve the issue for me. Thanks!!!
I tried the other work around of going tthough all the channels and deleting/removing the channels causing the issue. It initially worked but within a day or two it stopped refeshing again and different channels were causing the issue. Going though 500+ channels, trying to figure out which channel is causing the issue every couple of days is too time consuming.
I don’t think it is channel specific - it is probably to do with the number of channels and the amount of data in the updates. It has been seen to arise with number of channels being 307 or higher
I was having the issue with only 241-260 channels selected. When I went through the process of selecting and removing channels only certain channels stopped the refesh.
Do you have any logs ? Just want to see if there is a JSON Parsing Error and If it is using onConnect
I have the same json parse error as the others. It seems to indicate a specific channel - if I disable that channel will it work temporarily?
Feb 21, 2018 13:00:13.458 [9456] ERROR - EPG: JSON parse error. Data from request is [{“stationId”:“11331”,“callSign”:“WCBS”,“affiliateCallSign”:“CBS”,“affiliateId”:“10098”,“channel”:“002”,“preferredImage”:
Also I can send my logs as well if that is helpful.
@dansarrosick said:
I have the same json parse error as the others. It seems to indicate a specific channel - if I disable that channel will it work temporarily?Feb 21, 2018 13:00:13.458 [9456] ERROR - EPG: JSON parse error. Data from request is [{“stationId”:“11331”,“callSign”:“WCBS”,“affiliateCallSign”:“CBS”,“affiliateId”:“10098”,“channel”:“002”,“preferredImage”:
From my experience and others posting the same error I would say no, disabling channel 2 won’t help. The error info in the log is misleading in that it’s not channel 2, it’s something else. My error (and all others I’ve seen posted) show the lowest# channel you have enabled in the log data, probably because there’s too much data to show in the log entry. I had the error and when I removed some channels I’ll never watch it went away and hasn’t returned. I could probably add them back one at a time to see which one triggers the error, but I’m not going to spend days doing that as each EPG refresh is taking 80-90 minuted to complete.
Yep - same behavior here.
@dansarrosick said:
I have the same json parse error as the others. It seems to indicate a specific channel - if I disable that channel will it work temporarily?Feb 21, 2018 13:00:13.458 [9456] ERROR - EPG: JSON parse error. Data from request is [{“stationId”:“11331”,“callSign”:“WCBS”,“affiliateCallSign”:“CBS”,“affiliateId”:“10098”,“channel”:“002”,“preferredImage”:
How many channels do you have?
Channel 002 is just the first data in the JSON response - what you pasted is just the first line of a long response that gets truncated at 4000 characters for the log
I have no evidence of the issue arising with less than 300 channels - so if you have less than 300 please provide logs covering the time of the error and ensure you had debug logging enabled beforehand
See
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
