solved: RTSP Errors on Digibit R1
Added by Johannes Bachteler over 6 years ago
Hello,
i try since two weeks to setup an server-client architecture for tv and pvr. I installed TVHeadend on a OMV-Server and use Libreelec-clients. Source for DVB-Input is an Digibit R1.
First everything worked fine, but since this evening i have RTSP-Errors: after this error the tuning for a channel fails, log says this:
2018-02-18 00:56:07.158 subscription: 004F: "192.168.178.114 [ libelle | Kodi Media Center ]" subscribing on channel "ANIXE HD", weight: 100, adapter: "SAT>IP DVB-S Tuner #1 (192.168.178.27)", network: "Astra", mux: "10773.25H", provider: "BetaDigital", service: "ANIXE HD", profile="htsp", hostname="192.168.178.114", username="libelle", client="Kodi Media Center"
2018-02-18 00:56:07.163 satip: SAT>IP DVB-S Tuner #1 (192.168.178.27) - RTSP SETUP error -5 (Eingabe-/Ausgabefehler) [6-500]
2018-02-18 00:56:09.157 subscription: 004F: service instance is bad, reason: Tuning failed
2018-02-18 00:56:11.158 subscription: 004F: No input source available for subscription "192.168.178.114 [ libelle | Kodi Media Center ]" to channel "ANIXE HD"
2018-02-18 00:56:13.158 subscription: 004F: No input source available for subscription "192.168.178.114 [ libelle | Kodi Media Center ]" to channel "ANIXE HD"
2018-02-18 00:56:15.158 subscription: 004F: No input source available for subscription "192.168.178.114 [ libelle | Kodi Media Center ]" to channel "ANIXE HD"
2018-02-18 00:56:17.158 subscription: 004F: No input source available for subscription "192.168.178.114 [ libelle | Kodi Media Center ]" to channel "ANIXE HD"
2018-02-18 00:56:19.158 subscription: 004F: No input source available for subscription "192.168.178.114 [ libelle | Kodi Media Center ]" to channel "ANIXE HD"
...
I googled, but found nothing that explains this error.
I tried also the alternative firmwar satip-axe, but there ist the problem too.
Can please somebody here help me?
Regards
Johannes
Replies (1)
RE: RTSP Errors on Digibit R1 - Added by Johannes Bachteler over 6 years ago
The solution was to remove an satip standalone receiver fron the network ;o)