Troubleshooting assistance for ‘Channel not found’ in recent recording

[Alan]

I have a stable NextPVR setup and this weekend encountered multiple “[Failed: Channel not found. Deleted?]” errors. Config: Windows 10, NextPVR, V5, Ceton Proxy, InfiniTV 4

What is somewhat puzzling, in one instance, is that V5 was recording the prior show on that channel that errored.

I did find several [ERROR][9] writer.Close() did not complete in a timely fashion in the logs and not sure what the cause or how to address it.

[mvallevand]

That error is normal, it never completes in a timely manner. Channel not found sounds like an issue with the Ceton Proxy

Martin

[Graham]

I have a stable NextPVR setup and this weekend encountered multiple “[Failed: Channel not found. Deleted?]” errors. Config: Windows 10, NextPVR, V5, Ceton Proxy, InfiniTV 4

cetonproxydefault20210214085919.log has this but I dunno if it's relevant ...

[2021-02-11 21:55:00.244] Starting stream on tuner 0 to 192.168.200.2:63785
[2021-02-11 21:55:00.431] Setting channel on tuner 0 to 704
[2021-02-11 21:55:00.493] Getting tuner\Frequency for tuner 0
[2021-02-11 21:55:00.538] Received tuner\Frequency for tuner 0: "363000"
[2021-02-11 21:55:00.538] Getting mux\ProgramNumber for tuner 0
[2021-02-11 21:55:00.571] Received mux\ProgramNumber for tuner 0: "20"
[2021-02-11 21:55:01.055] New packet size: 3960
[2021-02-11 21:55:01.055] Getting diag\CopyProtectionStatus for tuner 0
[2021-02-11 21:55:01.070] New packet size: 7908
[2021-02-11 21:55:01.098] Received diag\CopyProtectionStatus for tuner 0: "None"
[2021-02-11 21:55:04.274] Client 0 tuner 0 video converter: [mpegts @ 095a2cc0] Stream #0: not enough frames to estimate rate; consider increasing probesize
...
[2021-02-11 21:55:04.275] Client 0 tuner 0 video converter: [mpegts @ 095a2cc0] Could not find codec parameters for stream 0 (Video: mpeg2video ([2][0][0][0] / 0x0002), none(tv)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options

[Alan]

Graham / Martin

The first 'Channel not found' happened on 2021-02-13 and then I have two on 2021-02-14.  Channel 734 on both days and 738 on the 14th. I can view both and have recorded from both in the past.  I could not find anything in either the NextPvr or Ceton Proxy logs that corresponded to the record start date / time information (2021-02-13 20:55, 2021-02-14 20:00, 2021-02-14 21:00) and did not know if the other error had caused something to crash.  As NextPVR did successfully record 2 shows after the the second failure, I am not sure where to look.

Using Graham's observation, I looked at the Ceton Proxy Log cetonproxydefault20210214202422.log and noted several similar errors on channel 734 from the prior recorded (which did complete)

[2021-02-14 18:55:08.841] Client 0 tuner 2 video converter: [mpegts @ 01c6d680] Could not find codec parameters for stream 0 (Video: h264 ([27][0][0][0] / 0x001B), none): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options

But did not find any reference to channel 738 in the Ceton Proxy Log, so it is not clear if that channel was ever requested by NextPVR, or Ceton Proxy had crashed, and while I saw references to the program (Crossword Mysteries: Terminal Descent) in NextPVR logs, I did not find any entries between 19:55 and 21:55, yet the Recent Recording screen report the failure at 20:00.  One thing I just determined was this recording would have been then 4th of 4 tuners available, and not sure if that has anything to do with the issue. I think that was the case for the last failure but it was on the same channel that was being used at the time.  And yes, NextPVR Device Setting shows 4 active tuners with the same lineup, all using Ceton Proxy.

In the first failure case from 2021-02-13, it was the only recording that day, so i am not sure if that means anything.

Any other suggestions?  I thought I might Clear the Cable Card lineup and rescan the channels in both Ceton Proxy and NextPVR, but am holding off, in case additional information is needed about the current configuration.

[mvallevand]

Sorry I don't know how Ceton Proxy works so I can't offer any further suggestions on that Most of your recurring recordings seem corrupt so it seems that it part of the problem. Not sure how they were created in the first place.

Also make sure that Ceton Proxy is always running before NextPVR starts as there is a NextPVR quirk that tuners must be available when the server starts.

Martin