Server preventing standby

[kricker]

I am running 6.5.20 RC with the default STV. When Sage server is running my PC will not enter standby mode. If I shot down the server the PC enters standby mode normally. Anyone else experiencing this, or can anyone else confirm this?

[doc]

My PC goes into standby ok on this beta version.

Do you have debug logging enabled? or native logging enabled?

What about import media rescan frequency? I have mine disabled.

Do you have any other plugins installed?

[kricker]

I am just about to disable the media scanner, but it's set to 1hour and standby is currently set at 2 minutes for testing.

I also have the webserver installed, and I am about to test removing it although standby works with just SageTV running with the websever installed.

[kricker]

Appears to be the media scanner. I set it to disabled and the PC went to sleep properly.

[doc]

I remember something changing regarding the media scanner in a recent beta but I can't find the details and my memory isn't what it used to be!

[kricker]

I may do some looking around later, but for now just disabling it works for me. I don't have that many changes going on in Sage's media folders.

...as soon as I say it's fixed though, switching back to SageMC causes sleep to not work again.

[dadavo]

Has anyone found any new information? I am running SageTV 6.5.20.216 in standalone with the TV Service and have noticed that if I stop and disable the service my PC can enter standby fine even if I still have the SageTV front-end running. If I have the front-end closed and the service running my PC will not go into Standby.

[kricker]

I'm still investigating. I ran out of time today. I plan to do more testing tomorrow.

[kricker]

Tested with Sage 6.6 and still the server is preventing standby. I am going to have to try a clean install and see what is going on.

[Sagebrush]

Changes for SageTV V6.5.16 Beta 5/26/2009, Core Updates indicated:

"6. Only check the video recording directories for new/changed/removed files when we do a library import scan instead of every 5 minutes (this was keeping systems from going into standby if UNC paths were used for recording directories)"

Like others, in upgrading to 6.6.2 from an older version, I was still not able to get my server to sleep with less than the old 3 minute setting. Perhaps there's something persisting in the properties file that needs to be modified...or maybe this product change got undone since 6.5.16.

[ellweber]

This activity still remains in the Sage Server logs:

Tue 8/11 12:09:15.189 [Seeker@a82a10] Seeker waiting for 403 mins.
Tue 8/11 12:11:47.803 [Ministry@15e10ab] Ministry is waiting for 180 sec
Tue 8/11 12:14:15.200 [Seeker@a82a10] Seeker awoken

As you can see the the "Seeker" wakes up every 5 minutes like clockwork to keep the server from sleeping. I suppose it has another purpose but it sure does prevent sleeping with anything longer than a 5 minute setting.

I too was hoping the above referenced change would allow me to set the server sleep timeout to something longer than 5 minutes.

Lynn

[kricker]

I am still having issues getting my system to sleep. I wonder if me using smb paths for my recording folder (even though it is a local drive) is the issue?