can't get rid of "No transponder available for subscription" error
Added by Stefan Mackovik almost 10 years ago
Hello!
I'm using the latest beta version of tvheadend (3.9.1879) on a respberry pi (installed on a raspmbmc) using the Sundtek MediaTV Pro III USB Stick (in DVB-C-Mode) and I keep geeting these errors:
tvheadend7889: subscription: 0001: No transponder available for subscription "192.168.1.4 [ crazybird | VLC media player ]" to channel "ORF1 HD"
It doesn't appear always but usually after some time of usage of tvheadend, which is very annoying, because it often happens when I try to record a program - next day I see in the log that the record was "missed" because of the error.
The only thing that helps getting rid of the error is a) restarting the whole PI or b) running the sundtek install script (http://www.sundtek.de/media/sundtek_netinst.sh). Restarting tvheadend does not help.
A long time ago the error only occured only once in a while, at the moment it's far more often.
I tried different workarounds like restarting tvheadend or the driver periodically but none of it does work.
For start, it would be nice to know what happens in tvheadend when this error is written to the log.
tvheadend is a cool project but it's not worth a lot for me if I can't be sure that recording works reliable.
Thank you for any information in advance,
Stefan
Replies (1)
RE: can't get rid of "No transponder available for subscription" error - Added by Mark Clarkstone almost 10 years ago
Stefan Mackovik wrote:
Hello!
I'm using the latest beta version of tvheadend (3.9.1879) on a respberry pi (installed on a raspmbmc) using the Sundtek MediaTV Pro III USB Stick (in DVB-C-Mode) and I keep geeting these errors:
tvheadend7889: subscription: 0001: No transponder available for subscription "192.168.1.4 [ crazybird | VLC media player ]" to channel "ORF1 HD"
It doesn't appear always but usually after some time of usage of tvheadend, which is very annoying, because it often happens when I try to record a program - next day I see in the log that the record was "missed" because of the error.
The only thing that helps getting rid of the error is a) restarting the whole PI or b) running the sundtek install script (http://www.sundtek.de/media/sundtek_netinst.sh). Restarting tvheadend does not help.
A long time ago the error only occured only once in a while, at the moment it's far more often.
I tried different workarounds like restarting tvheadend or the driver periodically but none of it does work.
For start, it would be nice to know what happens in tvheadend when this error is written to the log.
tvheadend is a cool project but it's not worth a lot for me if I can't be sure that recording works reliable.
Thank you for any information in advance,
Stefan
It sounds like your device is failing after a while, I had a similar issue quite a few times in the past. Reloading the modules fixed it temporarily, I soon replaced the device(s) and the problem disappeared.
When it fails have you checked for any errors in dmesg? Although sometimes that won't report anything at all (like in my case).
You could try sending a message to mrec on freenode IRC #hts, I believe he owns or works for Sundtek, no doubt he would be really interested in hearing from you. From what's been said about Sundtek they're a pretty decent bunch!
Hope this helps.