Kodi addon keeps freezing, on playback then dumping back in the recordings list

[sitush]

I stopped and restarted the recording service at 6:03 per your suggestion in another thread here. The Event Viewer confirms that.

I think I am getting lost in your terminology yet again. You asked above "I did notice that the web server reset earlier while streaming a recording did you restart it manually or reboot the server?" and I said that I had rebooted the server since at least yesterday. If recording service = web server then, yes, I did a manual stop/start at 6:03 ... but I'm pretty sure there was no recording being played or in a paused state at that time. I always ensure Kodi is out of action when doing stuff on the NPVR backend, and that was the last thing I did on the backend today other than package the two NPVR logs posted above.

[mvallevand]

Ok, semantics for sure. When I speak of server I generally mean the recording service and not the PC. I also asked for you to restart both the server and Kodi to have a clean started, but you didn't restart Kodi so I was confused. You were deleting files in Kodi 2 seconds after the server was back up without a new login.

Also you don't do the EPG update overnight my point is really about do the clean restart after the EPG update .

Martin

[sitush]

OK, sorry. It has just crashed again - Kodi and NPVR logs at https://drive.google.com/drive/u/0/folde...jlBxuecOvF - but I'm now going to go the whole hog by doing a manual EPG update with the client PC turned off, then reboot the backend PC, reboot the client PC and clear the Kodi EPG so that it reloads. Hope this is what you want.

Can you confirm that I am now using the advancedsettings.xml, please?

[mvallevand]

Can you make that a public link?

Martin

[sitush]

Is https://drive.google.com/open?id=1sysnhW...jlBxuecOvF any better?

[mvallevand]

Yes it is better, I probably need to do a deeper check tomorrow but I do see you had a recording paused for many hours which is probably not a great idea.

2019-04-05 20:34:49.975 T:784 DEBUG: CAnnouncementManager - Announcement: OnPause from xbmc
...
2019-04-06 03:19:30.743 T:4272 DEBUG: CAESinkDirectSound::CheckPlayStatus: Resuming Playback
...
2019-04-06 03:21:12.018 T:4376 DEBUG: AddOnLog: NextPVR PVR Client: DoRequest return /service?method=recording.watched.set&recording_id=11625&position=1423 200 66 1

After that because of the delay there is a major update to get all the guide info etc and you probably shouldn't have started to play the video so soon after that. Then I see you try and upload the logs but the log was too big.

What I don't see is a crash.


Martin

[sitush]

Yes, that long pause was my mistake and I will try not to repeat it - I got distracted when I paused.

And it is semantics again, I'm afraid: on this occasion, I definitely should not have said "crashed". It did the freezing thing and then dropped out of playback to the recordings listing. There was no buffering circle but there was a pause of anything up to maybe 10 seconds before it flipped from the non-moving playback to the listing.

Yes, the log was too big for paste.kodi.tv, hence uploading it with the NPVR logs to GDrive.

Thanks for your perseverance with this.

[sitush]

It has just done the same thing again, despite all of the restarting, updating EPG etc. Kodi log at https://paste.kodi.tv/axuperoyoh and the NPVR log is that timed at 0521 at https://drive.google.com/open?id=1sysnhW...jlBxuecOvF

I can see a lot of timer updates around 0519 but if I am reading the log correctly, those are after it is dropped from playback into the recordings list.

[mvallevand]

Those are more like your original freeze issue where the server did not respond to either the playback or watch.set command.

To answer your other question no that advancedsettings.xml is not working perhaps use the setting I suggested with the ip and not "PVR"

Martin

[sitush]

Happened again at about 2030 7 April - logs at https://drive.google.com/open?id=1sysnhW...jlBxuecOvF

I adjusted the advancedsettings.xml to use the backend IP address but would still be grateful for confirmation that it is working. The Windows share is definitely accessible from other PCs on the network, both Windows and Ubuntu.