Close X-NEWA (webclient) when server goes to sleep

[Sheik Yerbouti]

Great Add-On, Martin! How do I close X-NEWA when my server has gone to sleep, so I can start it up again and wake my server?

Chris

[mvallevand]

Hi Chris, thanks,

X-NEWA issues a WOL the next time you ask for something if the server goes to sleep, so I assume you meant in web client, (oops I didn't notice you wrote it in the subject). I hadn't actually tested it after putting my PC to sleep I forget that people like to just let NextPVR run and I don't trap the timeout error on sends to the server in web client. I've fixed that for the next build. Right now I just have it exit to XBMC, but I might send a prompt to send the WOL or just do the auto WOL that X-NEWA does.

Martin

[Sheik Yerbouti]

That great, Martin, thanks. I'm doing several testing at the moment, before I'll start using it "live". There is one more issue. Sometimes the web client gives me a very low screen resolution, but it's set at a high resolution in the config. I think it only happens when I reconnect after closing the web client. The first logon is always fine. I've attached an example. You can probably imagine this image looks very bad on a full screen HD TV.

Chris

[dgeezer]

I used to have the same thing happen with the low resolution. Martin told me how to fix it but I can't remember what I did and can't find the thread here by searching....

I believe that it has to do with how you exit. I would try adding back the exit button in Npvr and using that to close x-newa.

[nitram]

I get this problem with the X-NEWA res switching to lowres quite often as well. Sometimes it recovers back to hires if you restart XBMC, otherwise I stop XBMC, restart NPVR and then start XBMC again.

NPVR 3.2.9
X_NEWA 2.4.3
NEWA - last thing I downloaded was NEWA.v2.10_20131230-1.zip, not sure how you tell which version you have

[mvallevand]

The server default to low res so what you are likely seeing here are server crashes that web client doesn't know about and x-newa and it NextPVR is silently reestablishing a connection with another server instance. I could always sent the command to show high res but my preference is for users to send in logs so sub can get to the bottom of the crash. Besides I figure I'd still get posts that x-newa is slow and taking them to the main menu.

The Exit from the main menu is how to fix this and it will start a new session that x-newa knows about but you must modify config.xml by adding or change this in the General section

<FakeExit>false</FakeExit>

I still think that sub has the default wrong on this one. http://forums.nextpvr.com/showthread.php...post474932

Martin

[jcjefferies]

I have not had the Lo Res screen for quite a few weeks although I it happened much more regularly at one time. Thinking back it may have been after X-NEWA locked up so the power button was the only way out. The lockups happened while doing fast remote control key presses probably to get to near the end of the Ready Recordings list.

[Sheik Yerbouti]

I did a quick test with the <FakeExit>false</FakeExit> but that didn't help. But here are some logs.

Chris

[mvallevand]

The broken pipe messages are the problem on the server that sub needs to look at resolve this

Code:

4-10-05 21:10:31.783    [DEBUG][4]    Unexpected client control error: System.Runtime.Remoting.RemotingException: Kan niet lezen van een IPC-poort: De pipe is beëindigd.


Server stack trace:
   bij System.Runtime.Remoting.Channels.Ipc.IpcPort.Read(Byte[] data, Int32 offset, Int32 length)
   bij System.Runtime.Remoting.Channels.Ipc.PipeStream.Read(Byte[] buffer, Int32 offset, Int32 size)
   bij System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
   bij System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
   bij System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
   bij System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
   bij System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
   bij System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.ReadHeaders()
   bij System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   bij System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   bij System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   bij System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bij NUtility.IClientControl.ClientGetScreenImage()

The fake exit just allows you to reset the server session. In this case you did and then the server crashed again

Code:

014-10-05 21:10:43.031    [DEBUG][4]    Unexpected client control error: System.Runtime.Remoting.RemotingException: Kan niet lezen van een IPC-poort: De pipe is beëindigd.

Martin

[stustunz]

The server default to low res so what you are likely seeing here are server crashes that web client doesn't know about and x-newa and it NextPVR is silently reestablishing a connection with another server instance. I could always sent the command to show high res but my preference is for users to send in logs so sub can get to the bottom of the crash. Besides I figure I'd still get posts that x-newa is slow and taking them to the main menu.

The Exit from the main menu is how to fix this and it will start a new session that x-newa knows about but you must modify config.xml by adding or change this in the General section

<FakeExit>false</FakeExit>

I still think that sub has the default wrong on this one. http://forums.nextpvr.com/showthread.php...post474932

Martin

I add this to the server config.xml ?

I am getting this if i leave raspberry pi on overnight and since the server restarts at 5:00am everynight the resolution is low when I turn tv back on next day