Device doesn't always start

[simonhenry700]

I have NextPVR installed on a Raspberry Pi5, with the latest OS (Trixie) and a Hauppauge dual tuner USB stick.

While NextPVR works most of the time, occasionally when trying to watch a programme remotely via the web interface, it fails with the message "Streaming Failed (transcoder exited)" after about 15 seconds of "Starting Device. Please Wait...". Also, sometimes a scheduled recording will fail, presumably for the same reason.

Re-booting the Raspberry PI always results in normal service being resumed. The Raspberry Pi is not being used for any other purpose.

I've attached log files from the most recent failure; any insight you can provide would be most appreciated .

Simon

[mvallevand]

From the logs it looks like the tuner simply failed to lock a signal but we can't tell if that is because of the signal or perhaps the tuner h/w or USB failed after the lengthy (5+ hours) that the tuners were open. If you do put your RPi to sleep that could cause a problem. You might need to review the dmesg and journalctl logs to check for info.

Marin

[simonhenry700]

Thanks for the response Marin.

The Pi is never intentionally put into sleep. I'm not aware that's even a 'thing' with the Pi. Unless there's a default behaviour that I'm unaware of?

I've had a look at dmesg but don't know what I'm looking for. None of the entries are timestamped. I've done a file search for journlctl* and all of the returned files don't look like logs - they look like configuration files. I'm still stumped.

Simon

[mvallevand]

Timestamping is 0 is boot time. journalctl is a program so

sudo journalctl | less

There are many power manage sleep modes for USB and devices that you might need to research if you don't think it is a signal or interference issue.

Martin

[simonhenry700]

Thanks Martin. Last night a recording started but failed to complete. I've attached the log for journalctl at the point where it failed. Also spotted something strange (to me) in dmsg (the Pi was rebooted about 14 hours before).

Simon

[simonhenry700]

Although the recording failed, I was able to stream a programme 4 hours after it failed without needing to reboot. And I now realise that the dvb-demod firmware is downloaded each time I start a stream so dmesg seems OK.

Simon

[mvallevand]

It is normal for the timing and thumbnail extraction to log stream errors to the system log but perhaps sub can look at this since that might not be necessary any longer.

If the tuner works after a failure it indicates the problem is a signal lock issue. That also could have been loading the second tuner though if for example that was live tv.

Martin

[simonhenry700]

Thanks for the suggestions. The second tuner was not in use, and will rarely be, so I'll try disabling it.

Simon

[simonhenry700]

I effectively disabled the second tuner by deleting all of its channels, and so far the device has never failed to start. Admittedly, I've only tried a few times so I'll wait and see what the long-term effect is. But it would be strange if I'm the only person experiencing this.

Simon

[simonhenry700]

Failed to start device again. Unplugging the tuner for 10 seconds doesn't bring it back. Only a reboot brings it back.

Very frustrating. I'd really like to get this working, so I'd appreciate any suggestions.

Simon