Quote:
Originally Posted by emveepee
I know in addition to the artwork changes we tested with NextPVR SD introduced blocking for multiple uses of user credentials. So you have various SD clients, if the token isn't re-authenticated on failure things won't work.
Previous behaviour was all tokens were valid for 24 hours, and I'm not sure how SageTV deals with this. If you have multiple servers calling SD definitely don't run EPG updates at the same time.
Martin
|
'blocking for multiple uses of user credentials' might have caused my issue. Thanks for the clue! I only have one instance of SageTV and it is the only thing that grabs guide data from Schedules Direct. However, I now have three Internet connections in a load-balance and failover configuration. Connections from my SageTV server could randomly appear to be coming from three different IP addresses.
Regardless of the error I was seeing in the SageTV log, my guide data was still filling out and updating. The OTA broadcast channels that got shuffled around over the weekend are now mostly fixed. I think there is now just one channel with the wrong guide data and a couple of channels that still have the wrong channel logo.
I have reconfigured my router to route all traffic from my SageTV server through only one of the load-balance Internet connections and the failover Internet connection. After doing that and restarting SageTV, I haven't seen any EPG errors.
__________________
--Jason
Server Hardware: GIGABYTE GA-EP45-UD3R, Intel Q9550 CPU 2.83GHz, 11GB RAM, 1xHDHR, 1xHVR1600, 1xHVR2250
29TB Server Storage: 1TB SSD (OS), 1TB (data), 2x6TB+2x10TB (22TB FlexRaid storage pool), 2x2TB (recordings), 1x750GB (VMs).
Server Software: Win10 Pro x64 OS, SageTV 64bit v9.2.0.441, Java 1.8 u241, PlayOn, Comskip (Donator) v0.82.003, WampServer v2.5.
Clients: 3xHD300s, 2xHD100, 2xPlaceshifters
|