Nope, it's an m3u file which has a ts (MPEG TS) link. Can I enable a more verbose log with this container ?

29 minutes ago, delivereath said:

Nope, it's an m3u file which has a ts (MPEG TS) link. Can I enable a more verbose log with this container ?

 

Go to the debugging tab and add the appropriate subsystem.

Thanks for the reply but the debug tab does not show up

 

I will install tvheadend on a regular debian and check if the same happens.

12 minutes ago, delivereath said:

Thanks for the reply but the debug tab does not show up

 

I will install tvheadend on a regular debian and check if the same happens.

 

You need to enable expert view in the general tab of configuration to see that tab. 

I don't know if this is related to the 6.5 fixes you put in place, but I'm getting into situations where tvheadend is using up all my memory - I just caught it with over 20GB in use.

 

I would have posted the logs but I can't find them - where are the tvh logs?

3 hours ago, DZMM said:

I don't know if this is related to the 6.5 fixes you put in place, but I'm getting into situations where tvheadend is using up all my memory - I just caught it with over 20GB in use.

 

I would have posted the logs but I can't find them - where are the tvh logs?

 

We didn't do any fixes in tvheadend. @CHBMB only added chmod -R 777 /dev/dvb in the DVB plugin.

The logs for the tvheadend docker is in the container log. The button to the right on the docker page.

Edited March 22, 20188 yr by saarg

10 minutes ago, saarg said:

 

We didn't do any fixes in tvheadend. @CHBMB only added chmod -R 777 /dev/dvb in the DVB plugin.

The logs for the tvheadend docker is in the container log. The button to the right on the docker page.

Grr I was hoping there was something in appdata as there wasn't much in there when it crashed.

 

If it happens again I'll post something over on the tvh forum (I don't get much joy there to be honest...)

1 minute ago, DZMM said:

Grr I was hoping there was something in appdata as there wasn't much in there when it crashed.

 

If it happens again I'll post something over on the tvh forum (I don't get much joy there to be honest...)

 

You could add debug and trace to see what is going on. Enable it in the debug tab in configuration.

 

If you want to get stuff fixed in tvheadend, you add an issue on the tvhsite, not in the forum. The developer is fast to fix stuff.

7 minutes ago, saarg said:

 

You could add debug and trace to see what is going on. Enable it in the debug tab in configuration.

 

If you want to get stuff fixed in tvheadend, you add an issue on the tvhsite, not in the forum. The developer is fast to fix stuff.

Thanks - will do

Can anyone point me in the right direction in regards to passing through my GPU please? I have a GTX 1050 I'd like to use for x265 transcoding, however I don't seem to have /dev/dri when I try to add a container device.

 

What am I doing wrong?

 

Thanks

17 minutes ago, Stee said:

Can anyone point me in the right direction in regards to passing through my GPU please? I have a GTX 1050 I'd like to use for x265 transcoding, however I don't seem to have /dev/dri when I try to add a container device.

 

What am I doing wrong?

 

Thanks

 

You're not doing anything wrong. The only GPU supported on unraid is igpu in Intel processors. 

15 minutes ago, saarg said:

 

You're not doing anything wrong. The only GPU supported on unraid is igpu in Intel processors. 

 

Ah I see, so I guess my straightforward option from here on in is VM?

 

Cheers for the quick response, I thought I was going mad!!

3 hours ago, Stee said:

 

Ah I see, so I guess my straightforward option from here on in is VM?

 

Cheers for the quick response, I thought I was going mad!!

 

I don't know how good the nvenc support is in tvheadend though. Might not work so well, but check the tvheadend site.

This docker updated last night and now it seems the majority of my mapped channels don't work. I'm in the UK on Freeview HD and they were all working fine yesterday. It says it's tuned successfully under the status page but the channel just never loads. I'm using a hd homerun connect and the channels load fine using the hdhomerun app so I know it's not a signal issue etc.

 

Does anyone know where the log is located?

6 minutes ago, allanp81 said:

Does anyone know where the log is located?

Far right of the Docker tab.

This is strange:

 

2018-03-25 13:52:47.264 [ INFO] subscription: 005C: "HTTP" unsubscribing from "BBC ONE HD", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
2018-03-25 13:52:47.269 [ INFO] mpegts: 545.8MHz in UK Freeview - tuning on HDHomeRun DVB-T Tuner #1 (192.168.7.103)
2018-03-25 13:52:47.269 [ INFO] tvhdhomerun: tuning to auto:545800000
2018-03-25 13:52:47.300 [ INFO] subscription: 005E: "HTTP" subscribing on channel "BBC ONE HD", weight: 100, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "BBC ONE HD", profile="matroska", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
2018-03-25 13:52:49.543 [WARNING] TS: UK Freeview/545.833MHz/BBC ONE HD: H264 @ #6601 Continuity counter error (total 1)

2018-03-25 13:53:07.321 [WARNING] webui: Stop streaming /stream/channel/57d583f3f68058ff9b2f5629ecdd0f3e?profile=matroska, timeout waiting for packets

Was working fine yesterday.

1 minute ago, allanp81 said:

This is strange:

 

2018-03-25 13:52:47.264 [ INFO] subscription: 005C: "HTTP" unsubscribing from "BBC ONE HD", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
2018-03-25 13:52:47.269 [ INFO] mpegts: 545.8MHz in UK Freeview - tuning on HDHomeRun DVB-T Tuner #1 (192.168.7.103)
2018-03-25 13:52:47.269 [ INFO] tvhdhomerun: tuning to auto:545800000
2018-03-25 13:52:47.300 [ INFO] subscription: 005E: "HTTP" subscribing on channel "BBC ONE HD", weight: 100, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "BBC ONE HD", profile="matroska", hostname="192.168.7.158", client="Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
2018-03-25 13:52:49.543 [WARNING] TS: UK Freeview/545.833MHz/BBC ONE HD: H264 @ #6601 Continuity counter error (total 1)

2018-03-25 13:53:07.321 [WARNING] webui: Stop streaming /stream/channel/57d583f3f68058ff9b2f5629ecdd0f3e?profile=matroska, timeout waiting for packets

Was working fine yesterday.

 

Which version are you running? 

I think it was the "default" version. I can't remember and can't check what the options were again without removing the docker container and readding it. Is there another way to find out? Log shows this on launching of the docker:

 

NOTICE] START: HTS Tvheadend version 4.3-1206~g5de70b42e started, running as PID:204 UID:99 GID:100, CWD:/run/s6/services/tvheadend CNF:/config

 

I've also just noticed this:

 

2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to acquire lockkey: ERROR: resource locked by 192.168.7.11

2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to reset pfilter: 0

 

Some channels work though but most don't.

For instance:

2018-03-25 13:59:37.613 [ INFO] subscription: 0005: "192.168.7.181 [ download | Kodi Media Center ]" subscribing on channel "ITV HD", weight: 150, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "ITV HD", profile="htsp", hostname="192.168.7.181", username="download", client="Kodi Media Center"
2018-03-25 14:00:02.912 [ INFO] subscription: 0005: "192.168.7.181 [ download | Kodi Media Center ]" unsubscribing from "ITV HD", hostname="192.168.7.181", username="download", client="Kodi Media Center"
2018-03-25 14:00:02.915 [ INFO] mpegts: 545.8MHz in UK Freeview - tuning on HDHomeRun DVB-T Tuner #1 (192.168.7.103)
2018-03-25 14:00:02.915 [ INFO] tvhdhomerun: tuning to auto:545800000
2018-03-25 14:00:02.944 [ INFO] subscription: 0007: "192.168.7.181 [ download | Kodi Media Center ]" subscribing on channel "BBC ONE HD", weight: 150, adapter: "HDHomeRun DVB-T Tuner #1 (192.168.7.103)", network: "UK Freeview", mux: "545.8MHz", service: "BBC ONE HD", profile="htsp", hostname="192.168.7.181", username="download", client="Kodi Media Center"
2018-03-25 14:00:05.171 [WARNING] TS: UK Freeview/545.8MHz/BBC ONE HD: H264 @ #6601 Continuity counter error (total 1)

Status page show it tuned to BBC ONE HD and receiving data with no errors.

Just now, allanp81 said:

I think it was the "default" version. I can't remember and can't check what the options were again without removing the docker container and readding it. Is there another way to find out? Log shows this on launching of the docker:

 

NOTICE] START: HTS Tvheadend version 4.3-1206~g5de70b42e started, running as PID:204 UID:99 GID:100, CWD:/run/s6/services/tvheadend CNF:/config

 

I've also just noticed this:

 

2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to acquire lockkey: ERROR: resource locked by 192.168.7.11

2018-03-25 13:58:24.517 [ ERROR] tvhdhomerun: failed to reset pfilter: 0

 

Some channels work though but most don't.

 

You can see in the repository field which tag you are running. Linuxserver/tvheadend means lastes, which is the development branch of tvheadend. Expect things to break here. 

If there is anything else behind linuxserver/tvheadend, then you are running a stable version and the version is what it says. 

But you are running 4.3 which is development branch. 

So this is most likely a bug in TVheadend. 

You could try using the release-4.2 version. Just add it after linuxserver/tvheadend and put a : in between. Be sure to make a backup of your appdata as it might not work to downgrade. 

Hmm that's odd as I thought I'd added the stable version.

 

What's the simplest way to "downgrade"? Do I need to remove the docker container and just re-add from the apps tab in Unraid and choose the stable version?

21 minutes ago, allanp81 said:

Hmm that's odd as I thought I'd added the stable version.

 

What's the simplest way to "downgrade"? Do I need to remove the docker container and just re-add from the apps tab in Unraid and choose the stable version?

 

Did you read my post? 

Yes but at first it didn't make sense. We're not all experts

OK I'm all working again after switching to the old stable release, thanks for your help.

 

Now to work out how to reimport all of my recordings...

15 minutes ago, allanp81 said:

OK I'm all working again after switching to the old stable release, thanks for your help.

 

Now to work out how to reimport all of my recordings...

 

You used one of the stable tags? You should use release-4.2 for the latest stable. This will update the version if there is something new when we refresh our containers on Fridays.