Not using Schedules Dirct, Don't Have Key - So what

[BobPhoenix]

Working fine for me. Saturday I just setup my new server and had no problems with the SageTV EPG.

[weeber]

I'm having problems too. I'm trying to setup a new SageTV server today and when I try to setup the EPG, Sage keeps saying that there was an error connecting to the SageTV server.

I have no other connectivity issues, and I tried turning off the firewall.

I'm still using the same key in my old computer until I get this new server up and running. It can still download EPG data OK. Makes me thing that I need to deactivate my old license first. Does the Sage sever do a hardware check vour each license? Is there anyway to transition my key to the new server so it's seamless?

[tmiranda]

It looks to me like it is intermittently up and down. Very frustrating.

Some time ago Narflex said it is the same EPG service that Google Fiber uses. I wonder if that has changed?

If it doesn't get more reliable I will pony up the $$ and go to Schedules Direct.

[ASegredo]

Originally Posted by rkulagow

[I'm the Schedules Direct "server end" guy]

When the application logs into the JSON service, it gets a token. It uses that token when accessing the service. If another application is running on your system at the same time requests a token, the old token is invalidated.

If running SageTV9 on two machines, how can we ensure that they are not updating at the same time? I'm a long time SD XML user. I use a linux cron job to download the xml file weekly and then serve it locally to the other linux machines. I want to be a good user and not hammer their server.

How can I avoid this problem with the JSON server? IOW how can I control when sageTV checks for an update?

[rkulagow]

Don't worry about hammering the servers. They're always hammered anyways. The only thing that you must do is to make sure that they're not updating at the same time; each client gets a token, which is good for 24 hours, unless a new token is requested. In a worst case scenario, each server is going to ping-pong, invalidating each other's tokens. Just have one server finish, and then have the other one start.

[EnterNoEscape]

Originally Posted by ASegredo

If running SageTV9 on two machines, how can we ensure that they are not updating at the same time? I'm a long time SD XML user. I use a linux cron job to download the xml file weekly and then serve it locally to the other linux machines. I want to be a good user and not hammer their server.

How can I avoid this problem with the JSON server? IOW how can I control when sageTV checks for an update?

The SageTV code accounts for that possible situation and it does attempt to get "off sync" with the other servers using the same account if it is suspected that this is happening. I wouldn't be too worried about working this out yourself. I never even think about it when I'm doing testing because the code handles the situation so well.

[ASegredo]

Thanks!