Normal
Re: PowerScheduler++ Version 1.2.0.10 (RC1)Hi there,I have an interesting issue/problem (aren't they all).I am running 1.2.0A (custom SVN with Sky EPG functionality), on a single seat setup - Windows 7 x64.I have PS++ RC1 installed, and it seems to work ok, except for sometimes when I press the power button, and it goes into away mode.Auto poweroff (standby) after x minutes of idle works fine.I have it configured such that RC1 manages the power options (and not the OS). It is configured with the following:Only allow shutdown on home screenDo not shutdown Network Activity is > 2KDo not shut down if the following processes are running: Configuration, TVSetup, Comskip, BackupManagerThe options on the PS++ client plugin are greyed - which means it knows its single seat (managed by the TVServer plugin)Last night, it had recorded a program and comskip was running. I simply pressed the power button (I think Live TV was on the screen), I believe it entered away mode (didn't shutdown). I came down this morning expecting to find the HTPC powered off (standby), but it was still on.The MePo client error log was full of:2011-01-24 03:11:36.064282 [ERROR][PSClientPlugin Timer(410)]: PSClientPlugin: Cannot register client's PowerScheduler: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:31457 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace ---Server stack trace: at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream) at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream) at System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage msg)Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at TvEngine.PowerScheduler.Interfaces.IPowerController.RegisterRemote(String standbyHandlerURI, String wakeupHandlerURI) at MediaPortal.Plugins.Process.PowerScheduler.RegisterToRemotePowerScheduler()The HTPC is using a static IP, with the firewall turned off for the local/private network.The TV Server log shows nothing (unfortunately I no longer have the log) I will watch for this happening again and capture the actual logs.Thanks,J.
Re: PowerScheduler++ Version 1.2.0.10 (RC1)
Hi there,
I have an interesting issue/problem (aren't they all).
I am running 1.2.0A (custom SVN with Sky EPG functionality), on a single seat setup - Windows 7 x64.
I have PS++ RC1 installed, and it seems to work ok, except for sometimes when I press the power button, and it goes into away mode.
Auto poweroff (standby) after x minutes of idle works fine.
I have it configured such that RC1 manages the power options (and not the OS). It is configured with the following:
Only allow shutdown on home screen
Do not shutdown Network Activity is > 2K
Do not shut down if the following processes are running: Configuration, TVSetup, Comskip, BackupManager
The options on the PS++ client plugin are greyed - which means it knows its single seat (managed by the TVServer plugin)
Last night, it had recorded a program and comskip was running. I simply pressed the power button (I think Live TV was on the screen), I believe it entered away mode (didn't shutdown). I came down this morning expecting to find the HTPC powered off (standby), but it was still on.
The MePo client error log was full of:
2011-01-24 03:11:36.064282 [ERROR][PSClientPlugin Timer(410)]: PSClientPlugin: Cannot register client's PowerScheduler: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:31457
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
Server stack trace:
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessAndSend(IMessage msg, ITransportHeaders headers, Stream inputStream)
at System.Runtime.Remoting.Channels.Http.HttpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
at System.Runtime.Remoting.Channels.SoapClientFormatterSink.SyncProcessMessage(IMessage msg)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at TvEngine.PowerScheduler.Interfaces.IPowerController.RegisterRemote(String standbyHandlerURI, String wakeupHandlerURI)
at MediaPortal.Plugins.Process.PowerScheduler.RegisterToRemotePowerScheduler()
The HTPC is using a static IP, with the firewall turned off for the local/private network.
The TV Server log shows nothing (unfortunately I no longer have the log)
I will watch for this happening again and capture the actual logs.
Thanks,
J.