Hung client - how to detect

[snagglewest]

So I have several Raspberry Pi2 as kodi clients for live TV throughout the house. They have worked well for over a year now except today... From what I can figure last night around 11ish one got hung streaming a tv channel. Since the TV was set to sleep (and me too) it was never discovered until about 4 this afternoon when I noticed the Patriots game didn't get extended by NextEnd. A bit of checking showed a extra tuner in use which got tracked back to the Pi.

I have a script for updateEPG which checks to see if a tuner is in use to delay the update until all tuners are free. Long story short, with the tuner in use updateEPG never fired which also launches NextEnd so it didn't fire either and I lost the last of the Patriots game.

Not a huge deal, but it got me to thinking... is there some way with a setting or via script to see if a client has been streaming for xx number of hours and kill the connection?


On another note, I'm seeing a lot of these errors (NPVR.log.2). Is this anything to be conserned about?

Code:

2016-10-30 16:32:36.139    [DEBUG][13]    Scanning DRI devices
2016-10-30 16:32:36.140    [DEBUG][13]    Device: HDHomeRun DRI Tuner 13217F3A   *
2016-10-30 16:32:36.140    [DEBUG][13]    Adding DRI interface: urn:microsoft-com:serviceId:OCTAMessage (urn:schemas-microsoft-com:service:OCTAMessage:1)
2016-10-30 16:32:36.140    [DEBUG][13]    Failed to find capture source (HDHomeRun DRI Tuner 13217F3A) in the 7 items

I'm not sure the logs are going to be much help as I've done a good bit of mucking around in the last bit to try and figure out what was up but here they are.

[ATTACH=CONFIG]43169[/ATTACH]

[mvallevand]

I have a script for updateEPG which checks to see if a tuner is in use to delay the update until all tuners are free. Long story short, with the tuner in use updateEPG never fired which also launches NextEnd so it didn't fire either and I lost the last of the Patriots game.

For extending NextEnd should not have been impacted. Do you still have the football recording? If so what does

NextEnd --oid 48687

give you?

Martin

[snagglewest]

No, I deleted it. However, I just noticed my ParallelProcessing didn't have start /b "" "%PROGRAMFILES%\NPVR\NextEnd.exe" --oid %3 so that was probably the problem with the game. I guess the client getting hung and holding the tuner in use was a sorta a good thing, at least I figured out I had problem with my NextEnd setup.

On the error in the NPVR.log

Code:

016-10-30 16:32:36.139 [DEBUG][13] Scanning DRI devices
2016-10-30 16:32:36.140 [DEBUG][13] Device: HDHomeRun DRI Tuner 13217F3A *
2016-10-30 16:32:36.140 [DEBUG][13] Adding DRI interface: urn:microsoft-com:serviceId:OCTAMessage (urn:schemas-microsoft-com:service:OCTAMessage:1)
2016-10-30 16:32:36.140 [DEBUG][13] Failed to find capture source (HDHomeRun DRI Tuner 13217F3A) in the 7 items

Is this something to be worried about? The only tuners I have are 2 HDHR Primes (6 tuners) and everything seems to be working ok with the recordings and live TV. But then again "Failed to find capture source" is a bit disconcerting.

[sub]

On the error in the NPVR.log

Code:

016-10-30 16:32:36.139 [DEBUG][13] Scanning DRI devices
2016-10-30 16:32:36.140 [DEBUG][13] Device: HDHomeRun DRI Tuner 13217F3A *
2016-10-30 16:32:36.140 [DEBUG][13] Adding DRI interface: urn:microsoft-com:serviceId:OCTAMessage (urn:schemas-microsoft-com:service:OCTAMessage:1)
2016-10-30 16:32:36.140 [DEBUG][13] Failed to find capture source (HDHomeRun DRI Tuner 13217F3A) in the 7 items

Is this something to be worried about?

This isn't a problem, and can be safely ignored.