Sometimes pi unresponsive, tuner locked, still recording?

[TheRealRoland]

It has happened perhaps only three times in the last 6 or so months. This is the behavior.

- can't connect to the UI via port 8866
- am able to remote login to the pi
- the homerunhd tuner shows that there's a channel lock on the channel that it should be recording

So, rebooting the pi.

Then ofcourse it all works again, however:
- the recording (and previous recordings, probably right after 'the event') show as failed in the UI. so no file was created
- any new recordings will start, and they record correctly (the lock has been released / renewed?)

I've attached the log files, it all happened on (US Central time) Monday 30th of May; during the day (let's say until about 5 pm when i think i reset the pi). if i remember correctly, 4 recordings were scheduled during that day, but all failed.

The logs were pulled about right after i restarted the pi / nextpvr.

Would you be able to take a look and see what could have caused this weird state nextpvr was in?

[mvallevand]

Can you get the logs from your HDHR and zip them up?

Martin

[TheRealRoland]

Can you get the logs from your HDHR and zip them up?

Martin

Attached.

Doesn't show a whole lot. But, timestamps should be in the same timezone as the info coming out of the logs of nextpvr; only weird thing that i see is at midnight on 5/29 into 5/30

20220529-14:01:59 Tuner: tuner1 http stream ended (remote closed)
20220529-18:44:00 Tuner: tuner1 tuning 51.15 TCM (qam256:507MHz-15)
20220529-18:44:00 Tuner: tuner1 streaming http to 192.168.0.119:35456
20220529-23:59:00 Tuner: tuner0 tuning 51.15 TCM (qam256:507MHz-15)
20220529-23:59:00 Tuner: tuner0 streaming http to 192.168.0.119:35458
20220530-00:00:00 Tuner: tuner1 http stream ended (remote closed)
20220530-00:00:00 Tuner: tuner1 tuning 5055 Unknown (qam256:609MHz-3)
20220530-00:00:00 Tuner: tuner1 streaming http to 192.168.0.119:35460
20220530-21:18:35 Tuner: tuner0 http stream ended (remote closed)
20220530-21:18:35 Tuner: tuner1 http stream ended (remote closed)

21:18 must have been when i rebooted the pi4, and so the hdhr got released?

After that everything works as normal again.

Also - channel 5055 is an HD channel, for which the tv provider doesn't pass on a channel name (like it does on the 51.15 channel, "TCM") -- 5055 is WTTW-Prime, 88.3 in my channel lineup.

[mvallevand]

It looks like you need to do a clear QAM recscan whatever you have listed for 609MHz-1 and 609MHz-3 aren't valid channels. Could one of those be WTTW-Prime

Martin

[TheRealRoland]

It looks like you need to do a clear QAM recscan  whatever you have listed for 609MHz-1 and 609MHz-3 aren't valid channels.  Could one of those be WTTW-Prime

Martin

Apologies for the late reply. I think i observed that at times the channel gets encrypted by the provider (dunno why, but they keep on tinkering with adding / removing channels from lineups), thus the HDHomerun has no valid signal at all to record, and then NextPVR goes perhaps unresponsive, especially during recording.

This happens very rarely, hasn't happened at all since my last posting.

I'm considering this thread closed.