2020-04-07, 11:05 AM
My system consists of v4 running on W10 in the loft with 4 PCH clients and this has been rock solid for years. Now it's failing and I'm stumped but it must have been something I did so here is what has happened over the last 24 hours, most of which will be irrelevant but someone might just notice something...
Some of you may have seen my other thread about setting up a projector and needing an extra client where I managed to get a 5th PCH working, just about. Well I decided that it would be nice to add a PC to the projection setup and I had my old NPVR server gathering dust so I fired it up (it had already had NPVR software removed), installed an HDMI card, went through all the W10 updates and got it working to the projector. It has a blu-ray/HD-DVD drive so I could then watch old DVDs. All good.
I then thought 'why don't I install NPVR in client mode', so I downloaded the latest version (also running on main PVR server) and installed it. I ran NPVR, went into settings and ticked 'client mode'. Of course it asked for the server name and share so I went back to the main server to share the c:\users\public\npvr folder. Windows said this folder 'could not be shared'(?) so after some trials I ended up sharing c:\users. I completed the client mode setup and it worked perfectly, played recordings etc. I did have a problem with HD recordings stuttering so I went into settings (on this new client) and changed the Video Renderer from EVR to VMR9 (clutching at straws) but it had no effect so I decided it's most likely a network issue as this new client goes through a couple of routers/hubs. I wasn't worried as I can sort that another time. We streamed a couple of things from the Internet that evening but did not watch NPVR at all.
Now, cut to this morning and I woke up and powered up my bedroom PCH to watch the news and see if Boris was hanging on. When I selected Play on the recording it went to a black screen and then after about 4 seconds started to play fine and then about 4 seconds later it stopped and went back to the menu. Strange, I thought, so I selected another recording which did the same thing. Checked more recordings that I knew were OK and the same thing happened. So I rebooted the server and the PCH and tried again. Same thing. I tried a second PCH, same. So I went to the server and tried to play the news there and it worked perfectly. I ran WinMerge on the latest config.xml and one from my last update in December and the only difference, aside from version numbers/dates, was a new section MVP-LOCAL so I removed this and tried again, still no joy. Checked the drives weren't full, all OK. I should mention also that the new client PC was switched off last night and has not been on since. I've also rebooted the networking.
So, in summary I think I have somehow broken something in the web/mvp/PCH area (unless it's a windows update? But looks like only definition updates yesterday) but I really didn't change anything. Can anyone (Martin!) spot anything or have any ideas? I have attached a clean set of logs which do show a couple of streaming errors:
Unexpected error streaming file: System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at Cassini.Connection.WriteBody(Byte[] data, Int32 offset, Int32 length)
at Cassini.Request.StreamFile(Dictionary`2 parameters)
and
Unexpected error streaming file: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Net.UnsafeNclNativeMethods.OSSOCK.send(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at Cassini.Connection.WriteBody(Byte[] data, Int32 offset, Int32 length)
at Cassini.Request.StreamFile(Dictionary`2 parameters)
but they mean nothing to me. Are they the issue? What do they point to?
Sorry for the lengthy post but I'm stumped so not sure what, if anything, is relevant and too much info is better than not enough...
Logs.zip (Size: 9.29 KB / Downloads: 3)
Some of you may have seen my other thread about setting up a projector and needing an extra client where I managed to get a 5th PCH working, just about. Well I decided that it would be nice to add a PC to the projection setup and I had my old NPVR server gathering dust so I fired it up (it had already had NPVR software removed), installed an HDMI card, went through all the W10 updates and got it working to the projector. It has a blu-ray/HD-DVD drive so I could then watch old DVDs. All good.
I then thought 'why don't I install NPVR in client mode', so I downloaded the latest version (also running on main PVR server) and installed it. I ran NPVR, went into settings and ticked 'client mode'. Of course it asked for the server name and share so I went back to the main server to share the c:\users\public\npvr folder. Windows said this folder 'could not be shared'(?) so after some trials I ended up sharing c:\users. I completed the client mode setup and it worked perfectly, played recordings etc. I did have a problem with HD recordings stuttering so I went into settings (on this new client) and changed the Video Renderer from EVR to VMR9 (clutching at straws) but it had no effect so I decided it's most likely a network issue as this new client goes through a couple of routers/hubs. I wasn't worried as I can sort that another time. We streamed a couple of things from the Internet that evening but did not watch NPVR at all.
Now, cut to this morning and I woke up and powered up my bedroom PCH to watch the news and see if Boris was hanging on. When I selected Play on the recording it went to a black screen and then after about 4 seconds started to play fine and then about 4 seconds later it stopped and went back to the menu. Strange, I thought, so I selected another recording which did the same thing. Checked more recordings that I knew were OK and the same thing happened. So I rebooted the server and the PCH and tried again. Same thing. I tried a second PCH, same. So I went to the server and tried to play the news there and it worked perfectly. I ran WinMerge on the latest config.xml and one from my last update in December and the only difference, aside from version numbers/dates, was a new section MVP-LOCAL so I removed this and tried again, still no joy. Checked the drives weren't full, all OK. I should mention also that the new client PC was switched off last night and has not been on since. I've also rebooted the networking.
So, in summary I think I have somehow broken something in the web/mvp/PCH area (unless it's a windows update? But looks like only definition updates yesterday) but I really didn't change anything. Can anyone (Martin!) spot anything or have any ideas? I have attached a clean set of logs which do show a couple of streaming errors:
Unexpected error streaming file: System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at Cassini.Connection.WriteBody(Byte[] data, Int32 offset, Int32 length)
at Cassini.Request.StreamFile(Dictionary`2 parameters)
and
Unexpected error streaming file: System.Threading.ThreadAbortException: Thread was being aborted.
at System.Net.UnsafeNclNativeMethods.OSSOCK.send(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at Cassini.Connection.WriteBody(Byte[] data, Int32 offset, Int32 length)
at Cassini.Request.StreamFile(Dictionary`2 parameters)
but they mean nothing to me. Are they the issue? What do they point to?
Sorry for the lengthy post but I'm stumped so not sure what, if anything, is relevant and too much info is better than not enough...
Logs.zip (Size: 9.29 KB / Downloads: 3)
Dual Pentium 1.8GHz, 4GB, 5TB, Colossus, NOVA-T, NOVA-HD-S2, W10, Latest NPVR 4, 3 PCH A100, 2 PCH A110