Homeserver Forum

I have odd issue with one of my client computers. I finally got around to debugging this issue by systematically disabling services and start-up apps.

When Lights-out client UI is running on this computer it will not enter sleep whenever sleep time is set greater than approximately 5 minutes.
The problem seems to correlate to the lights-out UI tray app:
If the lights-out UI tray app is running the machine will not sleep with sleep time > 5 minutes.
If I exit the tray app the machine WILL sleep.

For this one computer, I can reproduce this behavior consistently.

Is there anything in client UI code that you can think of that may account for this behavior? Some timer around that 5 minute mark?

Windows Server 1016 Essential
Lights-out 3.5 (just upgraded)

I had same issue occurred with previous Lights-out 3.0 version

It is very odd. I have the other client machines that sleep as expected


Thanks

Hi whoareyou,

I'm not aware of such an issue and have never seen that myself.
The UI has a timer which checks for user activity every 15 seconds.

The client service has a timer which reports the client state every 5 minutes to the server.

You can check for a standby block with this command on the command line:

powercfg -requests

This will report all processes which block standby.

Regards
Martin

P.S. Moved to English forums

Hi Martin,

Thanks for the powercfg suggestion. Already have tried that and everything else I could think of.
Results of the powercfg query have never helped to resolve this issue.
Occasionally powercfg will detail an audio stream which was blocking - and easily explained by some running application.

So, you don't think the client service's 5 minute timer could somehow be related?
I realize that powercfg is not identifying any blocking app, but that 5 minutes mark seems to be the same time interval at which my sleep issue manifests itself.


Thanks again

You said it would work if you stopped the UI. But the five-minute timer is not in the UI, it's on service.
So I doubt it's the cause of the problem.

You can take a look at the log files at c:\Program Data\LightsOut3Client\Logs. Maybe this will help.

Yes, unless my testing got out of whack, it was not the service.

Ok. I'll take a look at the logs. Anything in particular you can suggest to look for in logs?

On the 15 second UI user activity check I assume that is keyboard or mouse activity?

I'll also take another look at my testing procedure

Sorry for all the questions ....
I really don't want to take too much of your time on this issue as it's not critical.

Thanks

Yes, user activity is mouse and/or keyboard.
What you can try also: Stop the Lights-Out client service and check if it still blocks standby. Then close the UI and check again.

I tested as follows:
Service and Ui Running
Stop service
Computer will not sleep
Close Tray app
Computer will sleep

I also tried following:
Disable service
Restart machine
Tray app running
Machine sleeps as expected

So I have two different results depending on if service running when machine boots

I just thought of one more test I can run. I will set service to delayed start

If I start service with the delayed start, machine sleeps as expected with sleep configuration at > 5 minutes.
I'll leave this configuration for a while and see if this result is consistent.
If sleep continues to function correctly, I'll switch back to the original startup configuration and see if original issue returns.

For now, my machine sleep is function as expected

That's strange.
Does this machine run with a SSD or a HD?

Boot is NVME. It has one large hard drive for data.

In case you're wondering it's a Dell 8930. Core i7-8700 with 32GB memory

I really don't get what's going on. I have 3 other machines with lights-out client installed and none of them ever had this issue.
Two machines are much older, but one is a newer core i5 also with NVME boot.

Of course, 8930 has a much different set of software/drivers installed than other machines.

As time allows I'll do some more testing.
For now, please don't devote too much time to this. If you happen to be in code, I'd appreciate if you keep my situation in mind, and if you see something that could account for this....

Thanks