Lots of errors when streaming from TVHeadEnd server

Anon Nona · 2016-01-02T11:51:58+00:00

I'm using a Raspberry Pi B exclusively for a TVHeadEnd server, with the latest Jessie Lite distro (updated and upgraded). This is whatuname -a spits out: Lin...

mpmc

Anon Nona wrote:
> Mark Clarkstone wrote:
> > I had a similar issue with an older Pi, I increased the nice value. if that doesn't work try removing everything but the tuner.
>

> Hmm, where do I find thenice value? I have only the tuner connected to the RPi already, it's completely dedicated to the task, with Jessie Lite distro, having only the bare minimum to leave ample processing power to TVHeadEnd.

Try.

sudo renice -n -5 -p <pid of tvheadend>

See ps -ef for the pid of tvheadend.

What kernel is your other system running? Is the broken system running a newer kernel? It could be driver changes.

Anon Nona

Mark Clarkstone wrote:
> Anon Nona wrote:
> > Mark Clarkstone wrote:
> > > I had a similar issue with an older Pi, I increased the nice value. if that doesn't work try removing everything but the tuner.
> >
> > Hmm, where do I find thenice value? I have only the tuner connected to the RPi already, it's completely dedicated to the task, with Jessie Lite distro, having only the bare minimum to leave ample processing power to TVHeadEnd.
>
> Try.
>
> [...] See ps -ef for the pid of tvheadend.
>

> What kernel is your other system running? Is the broken system running a newer kernel? It could be driver changes.

I tried, got the response396 (process ID) old priority 0, new priority -5. No change in the error stream...

When using VLC I get a glitched frame and then the errorUnidentified codec, VLC could not identify the audio or video codec. Although I think the issue lies on the RPi side, not VLC.

What other system? I'm using my Mac OSX 10.11.2 to view the stream.

I've heard that newer drivers might break the system, but as I said I usedphysically the same hard- and software after I got it to work successfully on another network. Moreover I can record the stream locally, then transfer the file and watch it OK, but not live TV... maybe the network or some obscure firewall settings?

mpmc

Anon Nona wrote:
> Mark Clarkstone wrote:
> > Anon Nona wrote:
> > > Mark Clarkstone wrote:
> > > > I had a similar issue with an older Pi, I increased the nice value. if that doesn't work try removing everything but the tuner.
> > >
> > > Hmm, where do I find thenice value? I have only the tuner connected to the RPi already, it's completely dedicated to the task, with Jessie Lite distro, having only the bare minimum to leave ample processing power to TVHeadEnd.
> >
> > Try.
> >
> > [...] See ps -ef for the pid of tvheadend.
> >
> > What kernel is your other system running? Is the broken system running a newer kernel? It could be driver changes.
>
> I tried, got the response396 (process ID) old priority 0, new priority -5. No change in the error stream...
>
> When using VLC I get a glitched frame and then the errorUnidentified codec, VLC could not identify the audio or video codec. Although I think the issue lies on the RPi side, not VLC.
>

> What other system? I'm using my Mac OSX 10.11.2 to view the stream.

You said you've used the same setup in another country I assumed that is still running. :P

> I've heard that newer drivers might break the system, but as I said I usedphysically the same hard- and software after I got it to work successfully on another network. Moreover I can record the stream locally, then transfer the file and watch it OK, but not live TV... maybe the network or some obscure firewall settings?

Where are you storing the recordings? on an external hard drive? or internal SD?

Anon Nona

Mark Clarkstone wrote:
> You said you've used the same setup in another country I assumed that is still running. :P
>
> >
> > I've heard that newer drivers might break the system, but as I said I usedphysically the same hard- and software after I got it to work successfully on another network. Moreover I can record the stream locally, then transfer the file and watch it OK, but not live TV... maybe the network or some obscure firewall settings?
>

> Where are you storing the recordings? on an external hard drive? or internal SD?

It was for testing before deployment, I wanted to be sure there was no driver problems or other issues...

Currently I store on the SD card, not a very good solution I know, I might use a USB dongle later.

mpmc

Anon Nona wrote:
> Mark Clarkstone wrote:
> > You said you've used the same setup in another country I assumed that is still running. :P
> >
> > >
> > > I've heard that newer drivers might break the system, but as I said I usedphysically the same hard- and software after I got it to work successfully on another network. Moreover I can record the stream locally, then transfer the file and watch it OK, but not live TV... maybe the network or some obscure firewall settings?
> >
> > Where are you storing the recordings? on an external hard drive? or internal SD?
>
> It was for testing before deployment, I wanted to be sure there was no driver problems or other issues...
>

>Currently I store on the SD card, not a very good solution I know, I might use a USB dongle later.

I did some testing on my RPi2 a while back & found that the Pi can't stream 45mbps over the network without glitching. The input was from a Technisat Skystar DVB-S2 HD USB tuner. I highly doubt your dvb-t muxes are that size so it shouldn't have any issues receiving via usb and outputting it over Ethernet.

I do have a few spare Pis (1 & 2) I'll have to hook up one of my RTL2832's & see if I get the same errors.

mpmc

Mark Clarkstone wrote:
> Anon Nona wrote:
> > Mark Clarkstone wrote:
> > > You said you've used the same setup in another country I assumed that is still running. :P
> > >
> > > >
> > > > I've heard that newer drivers might break the system, but as I said I usedphysically the same hard- and software after I got it to work successfully on another network. Moreover I can record the stream locally, then transfer the file and watch it OK, but not live TV... maybe the network or some obscure firewall settings?
> > >
> > > Where are you storing the recordings? on an external hard drive? or internal SD?
> >
> > It was for testing before deployment, I wanted to be sure there was no driver problems or other issues...
> >
> >Currently I store on the SD card, not a very good solution I know, I might use a USB dongle later. >
> I did some testing on my RPi2 a while back & found that the Pi can't stream 45mbps over the network without glitching. The input was from a Technisat Skystar DVB-S2 HD USB tuner. I highly doubt your dvb-t muxes are that size so it shouldn't have any issues receiving via usb and outputting it over Ethernet.
>

> I do have a few spare Pis (1 & 2) I'll have to hook up one of my RTL2832's & see if I get the same errors.

Just for you I built tvheadend on an RPi1 B 512MB (Debian Jessie installed via raspbian-ua-netinst kernel: Linux rpi_peter 4.1.14+ !#828 PREEMPT Thu Dec 10 13:07:09 GMT 2015 armv6l GNU/Linux) with an el-cheapo rtl2832u
http://dvb.drag2web.com/rtl2832u-r820t/r820t.jpg
and got it to play a full mux and as you can see its running fine.

http://i.imgur.com/g0POoKD.png?1

This is all being powered by an Anker 40W 5 port usb charger.

Btw what is this Debian Jessie Lite you speak of?

Anon Nona

Thank you for taking so much time to help me :)

It's definitely not a hardware issue then, I have the same el-cheapo DVB-T dongle.

I use Raspbian Jessie Lite, which is like a stripped-down version of Raspbian Jessie, got it from here: https://www.raspberrypi.org/downloads/raspbian/

You built it? You compiled TVHeadEnd on your system?

This was my install process:

$ wget -O - http://apt.tvheadend.org/repo.gpg.key | sudo apt-key add - $ echo "deb http://apt.tvheadend.org/stable wheezy main" | sudo tee -a /etc/apt/sources.list.d/tvheadend.list $ sudo apt-get update $ sudo apt-get install tvheadend -y

I used this as reference: https://tvheadend.org/projects/tvheadend/wiki/AptRepository, then this for setup: http://www.htpcguides.com/configure-pctv-triplestick-292e-tvheadend-on-raspberry-pi/

mpmc

Anon Nona wrote:
> Thank you for taking so much time to help me :)
>
> It's definitely not a hardware issue then, I have the same el-cheapo DVB-T dongle.
>

> I use Raspbian Jessie Lite, which is like a stripped-down version of Raspbian Jessie, got it from here: https://www.raspberrypi.org/downloads/raspbian/

Ah I see, I always use "raspbian-ua-netinst" on mine.
>

> You built it? You compiled TVHeadEnd on your system?

I usually use the autobuild script & install a deb but in this case (as I was doing a test) I just git cloned the master repo, bashed in ./configure installed any missing deps & ran make, once it built ran it from the build dir. Don't do this if you want a proper install that starts on boot etc.

>
> This was my install process:

> [...]

Why are you using the Wheezy repo for Jessie?

> I used this as reference: https://tvheadend.org/projects/tvheadend/wiki/AptRepository, then this for setup: http://www.htpcguides.com/configure-pctv-triplestick-292e-tvheadend-on-raspberry-pi/

You're running 3.4 (like in those screenshots from that guide)? If so try upgrading.

You may want try raspbian-ua-netinst (which by default is barebones Debian) & see how that goes.

Anon Nona

Mark Clarkstone wrote:

> You're running 3.4 (like in those screenshots from that guide)? If so try upgrading.

Good catch. I updated TVHeadEnd to 4.0.8.

However having the latest TVHeadEnd did not solve the issue, now I have other error messages:

2016-01-03 00:19:19.613 http: 192.168.0.16: using ticket 09CC9DDEA2480A64C1E32F3F4B12767091165B8E for /stream/service/33a918d568cf875bb74cea0c522a3c43 2016-01-03 00:19:23.000 subscription: 0002: No input source available for subscription "HTTP" to service "levira/530MHz/ETV2" in mux "530MHz in levira" 2016-01-03 00:19:23.001 subscription: 0002: No input source available for subscription "HTTP" to service "levira/530MHz/ETV2" in mux "530MHz in levira" 2016-01-03 00:19:23.006 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:23.007 webui: Couldn't start streaming /stream/service/33a918d568cf875bb74cea0c522a3c43?ticket=09CC9DDEA2480A64C1E32F3F4B12767091165B8E, No free adapter 2016-01-03 00:19:23.007 subscription: 0002: "HTTP" unsubscribing, hostname="192.168.0.16", client="VLC/2.2.1 LibVLC/2.2.1" 2016-01-03 00:19:23.017 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:23.018 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:23.028 http: 192.168.0.16: using ticket 09CC9DDEA2480A64C1E32F3F4B12767091165B8E for /stream/service/33a918d568cf875bb74cea0c522a3c43 2016-01-03 00:19:24.677 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:24.683 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:24.685 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:24.704 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:24.705 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:24.712 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:26.476 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:26.477 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:27.000 subscription: 0004: No input source available for subscription "HTTP" to service "levira/530MHz/ETV2" in mux "530MHz in levira" 2016-01-03 00:19:27.000 webui: Couldn't start streaming /stream/service/33a918d568cf875bb74cea0c522a3c43?ticket=09CC9DDEA2480A64C1E32F3F4B12767091165B8E, No free adapter 2016-01-03 00:19:27.000 subscription: 0004: "HTTP" unsubscribing, hostname="192.168.0.16", client="VLC/2.2.1 LibVLC/2.2.1" 2016-01-03 00:19:27.137 http: 192.168.0.16: using ticket 09CC9DDEA2480A64C1E32F3F4B12767091165B8E for /stream/service/33a918d568cf875bb74cea0c522a3c43 2016-01-03 00:19:28.509 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:28.515 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:28.516 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:28.533 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:30.471 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:30.472 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:31.000 subscription: 0005: No input source available for subscription "HTTP" to service "levira/530MHz/ETV2" in mux "530MHz in levira" 2016-01-03 00:19:31.000 webui: Couldn't start streaming /stream/service/33a918d568cf875bb74cea0c522a3c43?ticket=09CC9DDEA2480A64C1E32F3F4B12767091165B8E, No free adapter 2016-01-03 00:19:31.000 subscription: 0005: "HTTP" unsubscribing, hostname="192.168.0.16", client="NSPlayer/7.10.0.3059" 2016-01-03 00:19:32.474 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:32.475 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1 2016-01-03 00:19:32.483 http: 84.252.64.195: HTTP/1.1 GET /subscriptions -- 1

I might just try raspbian-ua-netinst tomorrow...

mpmc

Anon Nona wrote:
> Mark Clarkstone wrote:
> > You're running 3.4 (like in those screenshots from that guide)? If so try upgrading.
>
> Good catch. I updated TVHeadEnd to 4.0.8.
>
> However having the latest TVHeadEnd did not solve the issue, now I have other error messages:
> [...]
>

> I might just try raspbian-ua-netinst tomorrow...

"No input source available for subscription" means that you don't have any adapters assigned to the network, you need to make sure your adapter has a network and the network has muxes (See Config -> DVB Input -> Muxes).

Anon Nona

I tried raspbian-ua-netinst and sure enough it works. Thank you very much, I wonder where the problem was though.

Next issues to solve are: tvheadend does not start at boot and does not allow me to login as administrator to the web-UI (using the credentials I entered during setup - triple checked). I usedtvheadend -C in the terminal to test quickly, but now my system is open to the world without a password... no good!

mpmc

Anon Nona wrote:
> I tried raspbian-ua-netinst and sure enough it works. Thank you very much, I wonder where the problem was though.
>

> Next issues to solve are: tvheadend does not start at boot and does not allow me to login as administrator to the web-UI (using the credentials I entered during setup - triple checked). I usedtvheadend -C in the terminal to test quickly, but now my system is open to the world without a password... no good!

If you've installed the deb package try:

sudo update-rc.d tvheadend defaults

and reboot to test.

Check that you have a superuser file in/home/hts/.hts/tvheadend, if not rundpkg-reconfigure tvheadend.