SageTV v7 No Longer Sleeping

[Diego Garcia]

I recently decommissioned the domain controller for my LAN, of which my SageTV server was a member. In that earlier configuration the SageTV server would sleep when there was no activity, and wake itself up shortly before a recording had to be made. I mention this domain -> workgroup transition only because it's the most recent significant change I can recall making to the environment that the server operates in.

Now the SageTV server will not sleep. When I run powercfg -energy at a command prompt it reports that the SageTV executable has made a request that the system not be allowed to sleep. I don't know why this should be, but I suspect it's the immediate source of the problem.

In researching online I've seen solutions to the same problem adopted by others, but they involve telling Windows to ignore the "don't sleep" requests from the SageTV executable. Since we often are watching Sage-recorded in other rooms via extenders I don't want the server to decide to go to sleep in the middle of a show. That would not be wife-friendly .

Any thoughts on what I might try to diagnose or resolve this issue?

- Diego

[Diego Garcia]

I recently decommissioned the domain controller for my LAN, of which my SageTV server was a member. In that earlier configuration the SageTV server would sleep when there was no activity, and wake itself up shortly before a recording had to be made. I mention this domain -> workgroup transition only because it's the most recent significant change I can recall making to the environment that the server operates in.

Now the SageTV server will not sleep. When I run powercfg -energy at a command prompt it reports that the SageTV executable has made a request that the system not be allowed to sleep. I don't know why this should be, but I suspect it's the immediate source of the problem.

In researching online I've seen solutions to the same problem adopted by others, but they involve telling Windows to ignore the "don't sleep" requests from the SageTV executable. Since we often are watching Sage-recorded in other rooms via extenders I don't want the server to decide to go to sleep in the middle of a show. That would not be wife-friendly .

Any thoughts on what I might try to diagnose or resolve this issue?

- Diego

[KryptoNyte]

I guess the question is; what is it about your Sage Server that puts out this no-sleep message, as mine apparently doesn't do this. Is it a plugin perhaps?

Did anything about the machine change? Do you have a Ceton tuner installed in that machine by chance?

[Diego Garcia]

Originally Posted by KryptoNyte

I guess the question is; what is it about your Sage Server that puts out this no-sleep message, as mine apparently doesn't do this. Is it a plugin perhaps?

Did anything about the machine change? Do you have a Ceton tuner installed in that machine by chance?

powercfg -energy reports that the request to not sleep was made by the SageTV executable. I don't have any other information about the basis of the request.

Other than dropping the system out of the domain there have been no changes, either to the software or the hardware.

And no Ceton tuners.

[KryptoNyte]

If you're comfortable doing so, can you post that HTML (of some modified equivalent text file).

[KryptoNyte]

Also, maybe type out a list of the plugins currently in use ...

[Diego Garcia]

Here you go.

BTW, regarding the energy report: when I ran powercfg to generate this uploaded document, Sage was recording a show, which is why the SageTVService was making a "don't power down" request.

The odd thing -- and the entry that is always present, even when Sage is doing nothing -- no playback, no recording -- is the other "don't power down" request, from the SageTV app. I have no idea why that's there.

[KryptoNyte]

Diego, I had a strange issue come up today where SageTV Service was shutting itself down after about 4 minutes of uptime (after reboot)- this is a first for me. Once I get this issue resolved I'll try to get back here - in the meantime, maybe someone else will stop in and lend some suggestions ...

[timg11]

Have you changed the media import folders recently? That caused the same symptoms: see my thread: http://forums.sagetv.com/forums/showthread.php?t=58743

[Diego Garcia]

Originally Posted by timg11

Have you changed the media import folders recently? That caused the same symptoms: see my thread: http://forums.sagetv.com/forums/showthread.php?t=58743

LOL, small world! Your post was on the first things I found when I started googling the problem.

I did recently attach a USB drive, for system backups. But when Sage popped up the "what do you want to do with this drive?" dialog box I hit escape...which I presume means "don't do anything with it". I subsequently checked to see if the media import directories included anything on the USB drive. It didn't, so I don't think that's the problem. Besides, I am getting "don't power down" requests made which show under powercfg -requests.

But I appreciate you pointing me to the other thread.

[18Scoobz]

It the USB power setting not allowing it to sleep?

[Diego Garcia]

I believe I've found the culprit: the PlayOn TV server.

I finally thought of checking out the system logs, and noticed the system >>was<< going to sleep. It was just waking itself up every 10 or 15 minutes. Since I have it configured to sleep after 10 minutes of inactivity, it was up most of the time, which is why I thought it wasn't sleeping.

Turning off the PlayOn server seems to have solved the problem (24 hours and counting). You can find the events related to the PlayOn server in the Windows/application event folder. The server is named MediaMall.

Thanks for all the help and advice!

[Diego Garcia]

I believe I've found the culprit: the PlayOn TV server.

I finally thought of checking out the system logs, and noticed the system >>was<< going to sleep. It was just waking itself up every 10 or 15 minutes. Since I have it configured to sleep after 10 minutes of inactivity, it was up most of the time, which is why I thought it wasn't sleeping.

Turning off the PlayOn server seems to have solved the problem (24 hours and counting). You can find the events related to the PlayOn server in the Windows/application event folder. The server is named MediaMall.

Thanks for all the help and advice!