NextPVR Forums

I am using NPVR with an HDHR3-US, and after about 25 minutes the stream freezes and says, "The tuner you were using was required for a recording. Would you like to switch to watching a recording, or exit back to the menu?" The only option it gives it to exit to the menu.

When this occurs there is no recording set, and there are 2 tuners available, while only 1 is being used.

The log for when it fails is below:

2015-05-24 19:10:47.347 [DEBUG][31] Waiting for file to grow. Segment position now 618941496, length now 618714392
2015-05-24 19:10:47.347 [DEBUG][31] FileInfo reports file length as: 618714392
2015-05-24 19:10:47.347 [DEBUG][31] DriveInfo reports available space as: 1172132171776
2015-05-24 19:10:47.598 [DEBUG][31] Not all bytes read@2
2015-05-24 19:10:47.598 [DEBUG][31] About to switch files. The current file is H:\live-WCBS-HD-5949-3.ts
2015-05-24 19:10:47.598 [DEBUG][31] Unable to find file using method(1)
2015-05-24 19:10:47.598 [DEBUG][31] Switching to file(2): H:\live-WCBS-HD-5949-3.ts
2015-05-24 19:10:47.598 [DEBUG][31] currentFiles.Count = 3
2015-05-24 19:10:47.598 [DEBUG][31] - H:\live-WCBS-HD-5949-3.ts
2015-05-24 19:10:47.598 [DEBUG][31] - H:\live-WCBS-HD-5949-2.ts
2015-05-24 19:10:47.598 [DEBUG][31] - H:\live-WCBS-HD-5949.ts
2015-05-24 19:10:47.599 [ERROR][31] Unexpected exception in ClientConnectionHandler: System.Net.Sockets.SocketException (0x80004005): An established connection was aborted by the software in your host machine
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 size, SocketFlags socketFlags)
at NShared.ClientConnectionHandler.WorkerThread()
2015-05-24 19:10:47.599 [DEBUG][31] CLOSING file (client connection gone)
2015-05-24 19:10:47.599 [DEBUG][31] RollingFile.Close()
2015-05-24 19:10:47.599 [DEBUG][31] About to delete temp file: H:\live-WCBS-HD-5949-3.ts
2015-05-24 19:10:47.599 [DEBUG][31] About to delete temp file: H:\live-WCBS-HD-5949-2.ts
2015-05-24 19:10:47.599 [DEBUG][31] About to delete temp file: H:\live-WCBS-HD-5949.ts
2015-05-24 19:10:47.603 [DEBUG][31] Cleaning up: H:\live-WCBS-HD-5949.ts
2015-05-24 19:10:47.604 [DEBUG][31] Cleaning up: H:\live-WCBS-HD-5949-3.ts
2015-05-24 19:10:47.756 [DEBUG][31] ClientConnectionHandler exiting...


Any help would be appreciated.


Update:
I tried again, but it no longer throws an error. Now it just freezes after about 25 minutes.
The log entry for when it froze is below:
2015-05-25 18:04:30.609 [DEBUG][91] Remaining bytes required=55648
2015-05-25 18:04:40.672 [DEBUG][26] Renew lease ok (0x150004)
2015-05-25 18:04:50.736 [DEBUG][26] Renew lease ok (0x150004)

This issue only occurs on the client PC's. On the server it never freezes. I disabled the firewall on the server, but it didn't help.

The logs are attached.

Looking at the client logs it looks like the client tries to renew the lease, and the server renews it, but the client never receives the renewal from the server.
In the client log NPVR.log.2 - 2015-05-25 18:04:40.664 [DEBUG][1] Client about to request renewal of handle: 150004 repeats until the program is closed.

The client logs are also attached.

When I ran the stream through X-Newa I got a different error in the log.
The logs from when it was streaming through Kodi also suggest a failure in the lease renewal.
It looks like the database ends up locked when it tries to renew the lease even though it isn't locked at other times.

Logs are attached

Because of the spam in web.log I can't diagnose the problem without kodi.log but based on what I wrote here http://forums.nextpvr.com/showthread.php...quot/page4 it's the same problem I've reported to sub before with some proof of concept code, he needs to shorten the time on the lock for the temp file when other things are going on especially from a PC client

Martin

Thank You

Attached are the NPVR and Kodi logs.

Do you know if there is anything that I can do to fix this issue?

joeyberkovitz Wrote:Thank You

Attached are the NPVR and Kodi logs.

Do you know if there is anything that I can do to fix this issue?

I suspect it fails here because it couldn't lock the database when it needed to


deadlocked against this thread



Martin

Quote:2015-05-27 18:34:31.997 [DEBUG][33] GetRecordingsList@1
2015-05-27 18:34:51.090 [DEBUG][33] GetRecordingsList@2

Strange it would have taken this long between these two messages.

Are you recording to a network drive, or is the very slow machine slow?

sub Wrote:Strange it would have taken this long between these two messages.

Are you recording to a network drive, or is the very slow machine slow?

It is recording to a WD Red on the local machine, but the machine is very quick.
It is running Windows Server 2012. Would that have any effect on it?

How many recording have you got?

It basically look liked it took 20 seconds to load your recording list. Normally this take a few milliseconds.

sub Wrote:How many recording have you got?

It basically look liked it took 20 seconds to load your recording list. Normally this take a few milliseconds.

I have 109 recordings. Is that an issue?

No, that's not very many, and shouldn't take long.

Do you always get this type of delay between the "GetRecordingsList@1" and "GetRecordingsList@2" messages in your log file?