Recording files to temp folder filling up HD

[Ex70s]

I can reproduce this behavior.... let the stream go for over 4 hours on the same channel then these files build but do not delete themselves in line.
That is when this happens to me, or if Kodi crashes(rarely happens to me) as stated above.

Only cure.... stop recording service, restart and manually remove the leftovers.

[2leftfeet]

* (The cause of this appears to be that the server is unaware that the kodi client crashes - keeping the tuner in use and causing continuous stream data to accumulate until the disk fills up or the operator manually intervenes. - there seems to be no signaling or sense on the server's part that the client is no longer functioning and to stop the stream and free the tuner)

Sub, This just happened yet again -this time during a Windows 10 update - I am having a hard time believing that your TCP logic is working in all cases. It seems to be failing quite often, at least for me.

[sub]

As soon as NextPVR gets an error reading or writing from the TCP connection, which it should get if Kodi has crashed, then it should stop and clean up.

Are you maybe using any firewall/antivirus software that could be making it look like the TCP connection is still up?

[2leftfeet]

As soon as NextPVR gets an error reading or writing from the TCP connection, which it should get if Kodi has crashed, then it should stop and clean up.

Are you maybe using any firewall/antivirus software that could be making it look like the TCP connection is still up?

All clients are configured the same w/r firewall & antivirus - I have done nothing special with these. Nextpvr adjusts the firewall according to its needs during install - that's it.
Each client uses Windows 10 Windows Defender for antivirus using recommended settings.
Believe me that this has happened 3 times in the last 2 days, although, more typically it only happens once in about 3 weeks.

Is it possible for you to add the requesting client IP in WinTray? At least that would help detect earlier.

[mvallevand]

I am sure there is a problem in time shfiting mode since I see it too when I test it. Basically the web server continues to renew the lease even when Kodi is no longer streaming the channel. I've pointed to the problem area in then logs before

2017-11-15 13:59:24.171 [DEBUG][27] Checking for close notifications for sid: default
2017-11-15 13:59:24.171 [DEBUG][27] Renewed lease. (140002)@2.

It is not clear why there is a sid called default in the table but I think it may be because the Kodi addon is not consistent sending sid= and client= variables.

Martin

[Bobins]

I've seen this too. A kodi hiccup where kodi ends up being rebooted but Nextpvr keeps the tuner locked and accumulating files. Only way to release is a recording service restart.

[2leftfeet]

I also discovered, that when this condition occurs (like just now, again), Ntray freezes (becomes non-responsive) on clients, requiring manual termination via task manager.

Anyway to fix this?

[mvallevand]

Unfortunately as I've posted so many times,without Kodi and NextPVR logs this is not going to be magically fixed.

Martin

[Bobins]

Martin,

I've looked in the logs after this happens and don't see much relevant. Part of the problem is the logs get overwritten so quickly making it difficult to capture the point the problem starts especially when you don't notice it till some time after the trigger.

It would be useful if there was a way to adjust the maximum log size before rollover or an adjustable number of log retentions. For me, I have plenty of disk space and would happily have longer retention.

Ray.

[mvallevand]

No question that the web.log spam is a nightmare for debugging but I have yet to see a debug Kodi.old.log from the session that ended likely containing a hint on why it ended.

Also a client crash would be a good indicator that you need to send the logs right away.

Martin