NextPVR Forums - Socket exception on upgrade to 3.2.9

Pages: 1 2 3 4 5

Getting exception after upgrade to 3.2.9. I've rebooted the machine and still have a problem. Is 8968 a new port? I have not touched the FW in months. I do however have HDHomeRun, not sure if that is a factor.

LOG:

Code:
2014-03-29 10:54:46.770 [DEBUG][4] OnStart()

2014-03-29 10:54:46.786 [INFO][4] Using local in-process recording service

2014-03-29 10:54:46.786 [DEBUG][6] Starting MVP server 1

2014-03-29 10:55:01.427 [DEBUG][4] RecordingServiceProxy@exit

2014-03-29 10:55:01.833 [INFO][4] RecordingService.Startup()

2014-03-29 10:55:01.833 [INFO][4] Starting remoting service (on port 8968)

....

2014-03-29 10:55:51.134 [DEBUG][16] checking: HDHomeRun Device 1318E35A

2014-03-29 10:55:51.134 [DEBUG][16] enabled and present

2014-03-29 10:55:51.134 [DEBUG][16] has channel

2014-03-29 10:55:51.134 [DEBUG][16] live tv is possible

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@1]HDHomeRunRecorder@1[/email]

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@2.0]HDHomeRunRecorder@2.0[/email]

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@2.1]HDHomeRunRecorder@2.1[/email]

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@2.2]HDHomeRunRecorder@2.2[/email] nextPort=36312

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@2.2.0]HDHomeRunRecorder@2.2.0[/email]

2014-03-29 10:55:51.138 [DEBUG][16] HDHomeRunRecorder@2.2.0@allocated

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@2.3]HDHomeRunRecorder@2.3[/email]

2014-03-29 10:55:51.138 [DEBUG][16] Allocated port: 36312

2014-03-29 10:55:51.138 [DEBUG][16] [email=HDHomeRunRecorder@3]HDHomeRunRecorder@3[/email]

2014-03-29 10:55:51.138 [DEBUG][16] About to start HDHR device. Checking status for information sake... (could tell if it's already in use elsewhere)

2014-03-29 10:55:51.138 [DEBUG][16] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 1318E35A get /tuner0/status

2014-03-29 10:55:51.211 [DEBUG][16] Status: ch=none lock=none ss=0 snq=0 seq=0 bps=0 pps=0

2014-03-29 10:55:52.311 [DEBUG][16] [email=SetTarget@2]SetTarget@2[/email]

2014-03-29 10:55:52.311 [DEBUG][16] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 1318E35A set /tuner0/vchannel 2

2014-03-29 10:55:52.885 [DEBUG][16] ForcedIP.xml does not exists

2014-03-29 10:55:52.912 [DEBUG][16] 1318E35A can be found via adapter with ip address: 192.168.1.30

2014-03-29 10:55:52.912 [DEBUG][16] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 1318E35A set /tuner0/target rtp://192.168.1.30:36312

2014-03-29 10:55:52.913 [DEBUG][16] [email=SetTarget@2]SetTarget@2[/email]

2014-03-29 10:55:52.914 [DEBUG][16] Allocated Handle: 1

2014-03-29 10:55:52.915 [DEBUG][16] Live TV handle: 0x250001

EXCEPTION:

Code:
See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************

System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:8968

Server stack trace: 

   at System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port)

   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(AddressFamily family)

   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()

   at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()

   at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)

   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)

   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)

   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.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 NShared.IRecordingService.RenewStream(Int32 handle)

   at NextPVR.Players.LiveTvPlayer.RefeshOSD()

   at NextPVR.ControllerForm.timer1_Tick(Object sender, EventArgs e)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

....

JavaWiz Wrote:Getting exception after upgrade to 3.2.9. I've rebooted the machine and still have a problem. Is 8968 a new port? I have not touched the FW in months.

No, it's not a new port. 8968 has always been used by the frontend to talk to the recording service.

It can only really be one of two things. Either the nrecord.exe isn't running, or you have a firewall blocking communication. Maybe something about the new release caused your firewall block it?

I'm getting these errors too. I'm wondering if its because Nrecord is communicating over 127.0.0.1 instead of localhost which causes issues in widows 8 & 8.1

BrainStormer Wrote:I'm wondering if its because Nrecord is communicating over 127.0.0.1 instead of localhost

It's always used 127.0.0.1.

Quote:which causes issues in widows 8 & 8.1

I think you're referring to the sandboxing of win8 style metro/modern apps, which doesn't apply here, because NextPVR is a desktop app. For that sandboxing problem, localhost is also a problem, not just 127.0.0.1

sub Wrote:It's always used 127.0.0.1.

I think you're referring to the sandboxing of win8 style metro/modern apps, which doesn't apply here, because NextPVR is a desktop app. For that sandboxing problem, localhost is also a problem, not just 127.0.0.1

I saw ths in the PLEX forums, thought it pertained to services too.

"The 127.0.0.1 was replaced by localhost in recent update of Plex Media Server to overcome security lockdown in Windows 8.1 for 127.0.0.1"

I'm not aware of any other Windows problems with using 127.0.0.1. I'm using it here in Windows 8.1, and everyone else has been using the same with every other NextPVR release, and I don't remember any significant problems with it in the past.

So here is what I find.
When I go to Live TV I first get " An existing Connection was forcibly closed by the remote host"

Then I get " No Connection could be made because the target machine actively refused it 127.0.0.1:8968" Repeating. My Silicondust prime is stuck sending the stream to the
server and the file on the server never grows and the recording service appears stuck.
and Status is blank.

It probably is related to the Silicondust Prime.

BrainStormer Wrote:So here is what I find.
When I go to Live TV I first get " An existing Connection was forcibly closed by the remote host"

Then I get " No Connection could be made because the target machine actively refused it 127.0.0.1:8968" Repeating.

Is nrecord.exe disappearing from the task list when that happens?

It looks like it's successfully sending the request to the recording service, but maybe the recording service is dying before it can respond.

In Task Manager I have NRecord (32 Bit) under that it says NPVR Recording Service.
After the hang it still has Nrecord (32 bit) but the Recording Service drop down is no longer there.

Pages: 1 2 3 4 5