Results 1 to 3 of 3

Thread: X-NEWA Web Client Crashing

  1. #1
    Join Date
    Jun 2007
    Location
    St. Paul, MN, USA
    Posts
    1,340

    X-NEWA Web Client Crashing

    I've been experiencing a few cases of weird behavior with X-NEWA (running under Kodi on an RPi 3+) recently. Since Martin is working on X-NEWA a bit at the moment, I'm going to try to capture logs and post them. I did just upgrade to X-NEWA 2.5.4, but these problems were occurring with X-NEWA 2.5.3 before, so I don't believe that the change to 2.5.4 is related. I've been running the latest LibreElec betas, so I realize that might be part of the problem. Currently, I'm on LibreElec v 8.95.003.

    One of the problems that happens somewhat frequently is that X-NEWA will just crash and Kodi will go back to the main menu. This happened just now at 06:42:30. I've uploaded logs here.

    Let me know if you need anything else or want me to try anything.

  2. #2
    Join Date
    May 2006
    Location
    Canada
    Posts
    28,426
    Hi Brett I don't see the Kodi debug log in there do you have it? It looks like a server side issue though is anything in the event viewer?

    Martin

  3. #3
    Join Date
    May 2006
    Location
    Canada
    Posts
    28,426
    Edit sorry Brett I found kodi.log didn't see it on the tablet. The server dropped the connection to NextPVR on the host

    Code:
    2019-01-31 06:42:30.502	[DEBUG][22]	Unexpected client control error: System.Runtime.Remoting.RemotingException: Failed to read from an IPC Port: The pipe has been ended.
    
    
    Server stack trace: 
       at System.Runtime.Remoting.Channels.Ipc.IpcPort.Read(Byte[] data, Int32 offset, Int32 length)
       at System.Runtime.Remoting.Channels.Ipc.PipeStream.Read(Byte[] buffer, Int32 offset, Int32 size)
       at System.Runtime.Remoting.Channels.SocketHandler.ReadFromSocket(Byte[] buffer, Int32 offset, Int32 count)
       at System.Runtime.Remoting.Channels.SocketHandler.Read(Byte[] buffer, Int32 offset, Int32 count)
       at System.Runtime.Remoting.Channels.SocketHandler.ReadAndMatchFourBytes(Byte[] buffer)
       at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadAndMatchPreamble()
       at System.Runtime.Remoting.Channels.Tcp.TcpSocketHandler.ReadVersionAndOperation(UInt16& operation)
       at System.Runtime.Remoting.Channels.Ipc.IpcClientHandler.ReadHeaders()
       at System.Runtime.Remoting.Channels.Ipc.IpcClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
       at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)
    and the client simply saw it as a 404 and exited as it should

    06:42:30.237 T:1129313136 DEBUG: http://192.168.143.10:8866/control?t...694c55e64b283b
    06:42:30.474 T:1129313136 DEBUG: 404
    06:42:30.474 T:1129313136 DEBUG: HTTP Error 404: Not Found
    06:42:30.481 T:1129313136 DEBUG: {u'action': u'exit'}

    There was no crash in x-newa as it was handled gracefully however sub would need to explain why IPC dropped.

    Martin

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •