Sage wants me to quit at 10:50pm

[MacDaddy]

I've had an interesting hiccup for the last several nights. I am watching a HD200 connected to my SageTV box. At 10:50 (local watch time) for the last several nights, I've had the programin playback stop, go to a grey screen and then the HD200 power down. When I power back up, it can't find the Sage server.

When I look on the server, one interesting item is that the wiz.bak is 10:52pm and the wiz.bin, sage.properties.autobackup and sage.properties are all 10:53pm on today's date. Is there some sort of backup schedule that might force off an extender?

[Opus4]

Originally Posted by MacDaddy

Is there some sort of backup schedule that might force off an extender?

No, unless you've got something running on your system that is causing it. SageTV doesn't do that automatically.

Turn on debug logging and check the logs to see if there is info about what is happening at that time. You may need to look at the previous log too because it sort of sounds like you are using service mode & the service is getting stopped for some reason & then automatically restarting itself.

- Andy

[MacDaddy]

Thanks. You are correct - running in service mode with service recovery enabled. I have the log enabled now and will be checking for 10:50 tonight:-)

Do you (or anyone else) know if XP keeps a log of service failures/restarts?

[brewston]

I've noticed that when the HD200 loses contact with the Sage Server for whatever reason, the Hd200 appears to be 'off' - ie my screen goes blank (Don't know what the LED states are, I covered them with tape!) Unlike the client software which kindly tells you that its lost connection with the server.

[MacDaddy]

There was no failure last night (to be expected now that I have logging turned on). However, we were out at Rodeo Houston so there was no one watching at 10:50. The failure mode might require an active session, so I'll try again tonight.

[keepersg]

Originally Posted by MacDaddy

There was no failure last night (to be expected now that I have logging turned on). However, we were out at Rodeo Houston so there was no one watching at 10:50. The failure mode might require an active session, so I'll try again tonight.

I had something like this happen the other night with the same behavior from my HD200s. Turned out that the IP address of my server had changed. I'm not certain as to what happened except that we lost internet service through comcast for some period of time. My router is my DHCP server but it's continuously powered with battery backup. Hasn't happened since.

[MacDaddy]

Good point on UPS. I have my Sage server (frankentivo), unRaid server (tower) and all my network gear behind a Belkin 1500 UPS. I am suspcious that this is something related to the network.

If anyone has the time, check the following log at 3/26 15:34:13.972 and see if you can help me understand why the sage.exit was called. Please forgive the chatter about image files not being found (I've had tower offline while trying to isolate this - unfortunately screen saver setting is set to picture slide show).