Reply to thread

Message

AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)

[USER=69089]joseosoria[/USER]:
What I can see from your logs is that you ran the original PowerScheduler server plugin until 02.11. 15:29. At that time you restarted your tvservice with the PowerScheduler++ plugin, which worked without problems until 16:14, when you stopped tvservice (reboot?). When tvservice was restarted at 16:15 (PowerScheduler++ server plugin running) you made a sudden suspend within less than one minute so that tvservice could not come up properly. After a while at 16:31 and 16:44 you tried to run MP client which did not work maybe due to tvservice not running properly. But since the tvservice made no more logs after 16:15 I have no idea what was going on...
As a first step to improve system reliability you should reduce the PS++ check interval from 60 seconds to 15 seconds. Then you should watch if your system is running smoothly with PowerScheduler++ client and server plugins (scheduled wakeup, suspend after idle timeout, ...). And if this is all ok, you could check suspend and wakeup scenarios with blastcfg.exe.

Michael

<blockquote data-quote="michael_t" data-source="post: 714370" data-attributes="member: 85139">AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)[USER=69089]joseosoria[/USER]:What I can see from your logs is that you ran the original PowerScheduler server plugin until 02.11. 15:29. At that time you restarted your tvservice with the PowerScheduler++ plugin, which worked without problems until 16:14, when you stopped tvservice (reboot?). When tvservice was restarted at 16:15 (PowerScheduler++ server plugin running) you made a sudden suspend within less than one minute so that tvservice could not come up properly. After a while at 16:31 and 16:44 you tried to run MP client which did not work maybe due to tvservice not running properly. But since the tvservice made no more logs after 16:15 I have no idea what was going on...As a first step to improve system reliability you should reduce the PS++ check interval from 60 seconds to 15 seconds. Then you should watch if your system is running smoothly with PowerScheduler++ client and server plugins (scheduled wakeup, suspend after idle timeout, ...). And if this is all ok, you could check suspend and wakeup scenarios with blastcfg.exe.Michael</blockquote>

[QUOTE="michael_t, post: 714370, member: 85139"] [b]AW: Re: PowerScheduler++ Version 1.2.0.10 (RC1)[/b] [USER=69089]joseosoria[/USER]: What I can see from your logs is that you ran the original PowerScheduler server plugin until 02.11. 15:29. At that time you restarted your tvservice with the PowerScheduler++ plugin, which worked without problems until 16:14, when you stopped tvservice (reboot?). When tvservice was restarted at 16:15 (PowerScheduler++ server plugin running) you made a sudden suspend within less than one minute so that tvservice could not come up properly. After a while at 16:31 and 16:44 you tried to run MP client which did not work maybe due to tvservice not running properly. But since the tvservice made no more logs after 16:15 I have no idea what was going on... As a first step to improve system reliability you should reduce the PS++ check interval from 60 seconds to 15 seconds. Then you should watch if your system is running smoothly with PowerScheduler++ client and server plugins (scheduled wakeup, suspend after idle timeout, ...). And if this is all ok, you could check suspend and wakeup scenarios with blastcfg.exe. Michael [/QUOTE]