TVheadend plugin for unRaid 6


Recommended Posts

it seems to take an age when stopping or starting the plugin, is this normal?

 

with those settings the it seems to hang when starting with this line at the bottom

 

Starting Tvheadend: sudo -u nobody tvheadend -c /usr/local/tvheadend/.htsconfig -u nobody -g users -f >/dev/null 2>&1

 

before i reinstalled i had it set to mnt/cache/appdata/tvheadend is that an ok path?

 

if you don't use the plugin what do you use a docker?

 

Link to comment

it seems to take an age when stopping or starting the plugin, is this normal?

 

with those settings the it seems to hang when starting with this line at the bottom

 

Starting Tvheadend: sudo -u nobody tvheadend -c /usr/local/tvheadend/.htsconfig -u nobody -g users -f >/dev/null 2>&1

 

before i reinstalled i had it set to mnt/cache/appdata/tvheadend is that an ok path?

 

if you don't use the plugin what do you use a docker?

 

/mnt/cache/appdata/tvheadend is good.

 

Yeah I use a docker container, but I don't think it really matters it's purely personal preference and there are some advantages to using a plugin, like when I stop the docker service to backup my configs, I lose my PVR, you don't with a plugin. 

Link to comment

Do you think it would it be worth giving the docker a go? Or worth upgrading to the 6.2 beta (which I've been wanting to do)?

 

The Web gui isn't accessible this morning,  think I'm going to have to reboot via console.

 

It is still serving files though,  the kids are watching a film on an rpi2 with libreelec.

 

I take it not a lot of people go down the dvb-s route then? Could be worth cutting my losses and returning the card to amazon,  then making do with the wetek for a while longer.

 

My hope was to have everything running on the server with 3 rpi2 as clients.

 

Thanks again for your time:)

Link to comment

saarg uses DVB-S, no harm in giving the docket a go, I'd recommend switching to the unstable branch.  It's pretty stable.  I wouldn't give up on DVB-S that easily.  No reason why you can't achieve what you want.  Pretty much identical to my setup. 

Link to comment

saarg uses DVB-S, no harm in giving the docket a go, I'd recommend switching to the unstable branch.  It's pretty stable.  I wouldn't give up on DVB-S that easily.  No reason why you can't achieve what you want.  Pretty much identical to my setup.

I did use it, but now I have fiber and use IPTV  ;)

Link to comment

When I stop this plugin from the webinterface, it spams a constant stream of "y y y y y y y y y y y y y y y y y....." which continues until I close the tab and re-open it, at which point tvheadend has stopped.

 

The same thing happens when I stop the array and I have to SSH in and "killall yes" then wait a few mins for it to recover.

 

Really annoying!

Link to comment

Hey everyone! Please empty the "Script to call on shutdown" field in the configuration page. There is an error in the plugin where it gets set to yes. I'll try to resolve that in a future version

 

Hi

 

That field won't empty for me.

 

I stop the plug in, remove the 'yes' from the script filed and hit apply. As soon as I do, the 'yes' reappears.

 

I simply cannot get rid of it!!

 

Thanks

 

 

Link to comment

Sorry for that  :(

You have to find the configuration file and change a line in it like I described here: https://lime-technology.com/forum/index.php?topic=40704.msg475315#msg475315

I believe you'll only have to do that once. The file is located in your storage directory.

 

Thanks. Will do that over the weekend. Another step towards a super smooth unRAID.

 

Sorry now, this didn't work....

 

My data directory is set to /mnt/cache/tvheadend/.htsconfig in the settings UI

 

I SSH'd in there and nano'd the config file.

 

I added this to the bottom, following the format of the existing entries...

 

"script": ""

 

I disabled TVHeadEnd in the settings UI and removed YES from the script field. However, on hitting 'Apply', it popped right back in.

 

Is there another step to force the plugin to read the updated config? Is this even the correct config file? (the entry format is different to that which you outline).

 

Help appreciated.

 

 

 

 

Link to comment
  • 3 weeks later...

Hey!

 

Sorry for the late reply, I had some troubles reproducing the bug since I am not at home currently  ???

 

As a workaround for everyone who is not using the wakeup script: Please fill the text field with the following: /dev/null

Please update the plugin to the recent version.

 

 

and it will finally work again. Sorry for any inconvenience.

Link to comment

Hey!

 

Sorry for the late reply, I had some troubles reproducing the bug since I am not at home currently  ???

 

As a workaround for everyone who is not using the wakeup script: Please fill the text field with the following:

/dev/null

 

and it will finally work again. Sorry for any inconvenience.

 

Thanks!  Fixed it.

Link to comment
  • 3 weeks later...

What is everyone doing in order to get EPG data?  I know there was a Zap2xml plugin a while back, but has since been blacklisted due to a dispute of copyrights....or whatever they were arguing about.  Is there another solution or does anyone have a step by step guide on how to get it working?  Thanks!!

Link to comment

What is everyone doing in order to get EPG data?  I know there was a Zap2xml plugin a while back, but has since been blacklisted due to a dispute of copyrights....or whatever they were arguing about.  Is there another solution or does anyone have a step by step guide on how to get it working?  Thanks!!

 

You could use the Webgrab++ container if your source of EPG data works with it.

I use XMLTV that comes with the tvheadend container. But you also have to check if your source is available.

Link to comment
  • 1 month later...

I have an issue with tvheadend randomly stopping.  Here is what seems to be the relevant log entry:

 

Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31524 (tvheadend) score 776 or sacrifice child
Sep 15 04:32:49 TOWER kernel: Killed process 31524 (tvheadend) total-vm:14558828kB, anon-rss:13054820kB, file-rss:5664kB
Sep 15 04:32:49 TOWER kernel: mc invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0
Sep 15 04:32:49 TOWER kernel: mc cpuset=/ mems_allowed=0
Sep 15 04:32:49 TOWER kernel: CPU: 5 PID: 6006 Comm: mc Tainted: P        W  O    4.1.15-unRAID #1
Sep 15 04:32:49 TOWER kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B75M-ITX, BIOS P1.90 07/17/2013
Sep 15 04:32:49 TOWER kernel: 0000000000000000 ffff880110bb79e8 ffffffff815f8950 0000000000007c48
Sep 15 04:32:49 TOWER kernel: ffff8803d9508000 ffff880110bb7a98 ffffffff815f4ecc ffff880110bb7a48
Sep 15 04:32:49 TOWER kernel: ffffffff810f6ce9 ffff880014007000 01ff880110bb7a08 ffff880110bb7a48
Sep 15 04:32:49 TOWER kernel: Call Trace:
Sep 15 04:32:49 TOWER kernel: [<ffffffff815f8950>] dump_stack+0x4c/0x6e
Sep 15 04:32:49 TOWER kernel: [<ffffffff815f4ecc>] dump_header+0x7a/0x20b
Sep 15 04:32:49 TOWER kernel: [<ffffffff810f6ce9>] ? mem_cgroup_iter+0x2fd/0x3fb
Sep 15 04:32:49 TOWER kernel: [<ffffffff810fac63>] ? vmpressure+0x1c/0x6f
Sep 15 04:32:49 TOWER kernel: [<ffffffff81355273>] ? ___ratelimit+0xcf/0xe0
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3c52>] oom_kill_process+0xb7/0x37b
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3957>] ? oom_badness+0xb6/0x100
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b43a7>] __out_of_memory+0x441/0x463
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b4508>] out_of_memory+0x4f/0x66
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b850c>] __alloc_pages_nodemask+0x722/0x7b6
Sep 15 04:32:49 TOWER kernel: [<ffffffff810e4a14>] alloc_pages_current+0xb4/0xd5
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b1a5e>] __page_cache_alloc+0x88/0x95
Sep 15 04:32:49 TOWER kernel: [<ffffffff810b25d5>] generic_file_read_iter+0x32e/0x551
Sep 15 04:32:49 TOWER kernel: [<ffffffff810fd847>] __vfs_read+0x89/0xad
Sep 15 04:32:49 TOWER kernel: [<ffffffff810fdd33>] vfs_read+0x84/0x11d
Sep 15 04:32:49 TOWER kernel: [<ffffffff810fe543>] SyS_read+0x42/0x86
Sep 15 04:32:49 TOWER kernel: [<ffffffff815fe06e>] system_call_fastpath+0x12/0x71
Sep 15 04:32:49 TOWER kernel: Mem-Info:
Sep 15 04:32:49 TOWER kernel: active_anon:3730744 inactive_anon:108262 isolated_anon:0
Sep 15 04:32:49 TOWER kernel: active_file:9983 inactive_file:10619 isolated_file:290
Sep 15 04:32:49 TOWER kernel: unevictable:0 dirty:4528 writeback:831 unstable:0
Sep 15 04:32:49 TOWER kernel: slab_reclaimable:96842 slab_unreclaimable:29449
Sep 15 04:32:49 TOWER kernel: mapped:26683 shmem:205360 pagetables:12848 bounce:0
Sep 15 04:32:49 TOWER kernel: free:20239 free_pcp:0 free_cma:0
Sep 15 04:32:49 TOWER kernel: Node 0 DMA free:15104kB min:12kB low:12kB high:16kB active_anon:64kB inactive_anon:176kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15360kB mlocked:0kB dirty:0kB writeback:0kB mapped:64kB shmem:240kB slab_reclaimable:16kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 3423 15939 15939
Sep 15 04:32:49 TOWER kernel: Node 0 DMA32 free:53496kB min:3444kB low:4304kB high:5164kB active_anon:3051428kB inactive_anon:102404kB active_file:10344kB inactive_file:11520kB unevictable:0kB isolated(anon):0kB isolated(file):200kB present:3581300kB managed:3506316kB mlocked:0kB dirty:5788kB writeback:680kB mapped:22072kB shmem:182956kB slab_reclaimable:175688kB slab_unreclaimable:28640kB kernel_stack:4208kB pagetables:11936kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:144228 all_unreclaimable? yes
Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 12516 12516
Sep 15 04:32:49 TOWER kernel: Node 0 Normal free:12356kB min:12600kB low:15748kB high:18900kB active_anon:11871484kB inactive_anon:330468kB active_file:29696kB inactive_file:30816kB unevictable:0kB isolated(anon):0kB isolated(file):832kB present:13080576kB managed:12816552kB mlocked:0kB dirty:12324kB writeback:2644kB mapped:84596kB shmem:638244kB slab_reclaimable:211664kB slab_unreclaimable:89156kB kernel_stack:8048kB pagetables:39456kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:433692 all_unreclaimable? yes
Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 0 0
Sep 15 04:32:49 TOWER kernel: Node 0 DMA: 0*4kB 0*8kB 2*16kB (EM) 1*32kB (E) 1*64kB (E) 1*128kB (E) 2*256kB (EM) 2*512kB (EM) 3*1024kB (UEM) 3*2048kB (UEM) 1*4096kB (R) = 15104kB
Sep 15 04:32:49 TOWER kernel: Node 0 DMA32: 2868*4kB (UER) 3174*8kB (UEMR) 1000*16kB (UEMR) 5*32kB (R) 2*64kB (R) 3*128kB (R) 1*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 53792kB
Sep 15 04:32:49 TOWER kernel: Node 0 Normal: 2815*4kB (UEM) 58*8kB (EM) 32*16kB (R) 8*32kB (R) 2*64kB (R) 3*128kB (R) 2*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 13516kB
Sep 15 04:32:49 TOWER kernel: 226405 total pagecache pages
Sep 15 04:32:49 TOWER kernel: 0 pages in swap cache
Sep 15 04:32:49 TOWER kernel: Swap cache stats: add 0, delete 0, find 0/0
Sep 15 04:32:49 TOWER kernel: Free swap  = 0kB
Sep 15 04:32:49 TOWER kernel: Total swap = 0kB
Sep 15 04:32:49 TOWER kernel: 4169465 pages RAM
Sep 15 04:32:49 TOWER kernel: 0 pages HighMem/MovableOnly
Sep 15 04:32:49 TOWER kernel: 84908 pages reserved
Sep 15 04:32:49 TOWER kernel: [ pid ]   uid  tgid total_vm      rss nr_ptes nr_pmds swapents oom_score_adj name
Sep 15 04:32:49 TOWER kernel: [ 1045]     0  1045     5395      598      15       3        0         -1000 udevd
Sep 15 04:32:49 TOWER kernel: [ 1299]     0  1299    58398      850      25       3        0             0 rsyslogd
Sep 15 04:32:49 TOWER kernel: [ 1572]     0  1572     1671      452       8       3        0             0 dhcpcd
Sep 15 04:32:49 TOWER kernel: [ 1582]     1  1582     1714      369       9       3        0             0 rpc.portmap
Sep 15 04:32:49 TOWER kernel: [ 1586]    32  1586     3209      448      11       3        0             0 rpc.statd
Sep 15 04:32:49 TOWER kernel: [ 1596]     0  1596     1615      435       8       3        0             0 inetd
<snip>
Sep 15 04:32:49 TOWER kernel: [31386]     0 31386    11038      165      25       4        0             0 ssh
Sep 15 04:32:49 TOWER kernel: [31395]     0 31395    11038      166      25       3        0             0 ssh
Sep 15 04:32:49 TOWER kernel: [32019]   999 32019   243894    25320     123       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [ 3295]   999  3295   297309    20457     123       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [ 3410]   999  3410   242943    20734     117       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [ 4908]   999  4908   261243    19817     117       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [32178]   999 32178   397437    18226     126       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [32181]   999 32181   315003    16144     115       4        0             0 Plex Script Hos
Sep 15 04:32:49 TOWER kernel: [ 8082]     0  8082     1091      189       7       3        0             0 sleep
Sep 15 04:32:49 TOWER kernel: [ 8129]     0  8129     2159      216       9       3        0             0 timeout
Sep 15 04:32:49 TOWER kernel: [ 8130]     0  8130     2974      260      10       3        0             0 find
Sep 15 04:32:49 TOWER kernel: [ 8149]     0  8149     1091      158       7       3        0             0 sleep
Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31526 (linuxdvb_fronte) score 776 or sacrifice child
Sep 15 04:32:49 TOWER kernel: Killed process 31572 (mpegts_input_th) total-vm:14558828kB, anon-rss:13055084kB, file-rss:6388kB

 

There is 16gb RAM in the server so with no VMs running so I wouldn't have expected to be out of memory...

Link to comment

Sounds like a memleak in tvheadend. Sorry, but unRaid isn't exactly the right platform to debug applications :P

I will refresh this addon soon and upgrade to the 4,2 branch which has a ton of improvements, maybe your problems are gone then. In the meantime try different settings, I remember I had crashes when using different container formats for recordings in the past.

Link to comment
  • 1 month later...
On 28.10.2016 at 3:12 AM, gundamguy said:

Stumbled across this... because I have an HDHomerun now... is this no longer supported or getting updates?

 

Hey there! 4.0.9 is still the most recent stable version of tvheadend... I just recently moved back home so I have my server in operation again. I will most probably look into updating to 4.2 in the next days. :)

Edited by Mettbrot
Link to comment

Stumbled across this... because I have an HDHomerun now... is this no longer supported or getting updates?

 

Hey! 4.0.9 is still the most recent stable version of tvheadend... I just recently moved back home so I have my server in operation again. I will most probably look into updating to 4.2 in the next days. :)

 

I apologize, I didn't realize that 4.2 was not the most recent stable, tricked by their website. X_X

Link to comment

I got this installed up and running tonight using my HDhomerun. It found my channels and figured out the muxes and all that, but I didn't get the EPG figured out.

 

Also I wasn't sure how to change the recording directory, which I want to be a cache enabled share. I turned it off since I wasn't 100% up and running, (but very close.)

 

Where do I change the record directory, and is there a good guide to figuring out the EPG with a HDHomerun (with OTA antenna)?

Link to comment

I just pushed an update. Since it will probably take forever till 4.1 will be released I just decided to upgrade to the latest and greatest since there are a lot of fixes in there and other cool stuff! It works great for me so far... let me know what you think.

PLEASE MAKE SURE TO BACK UP YOUR USER DATABASE

 

Be aware that there is a settings View Level now in the top right corner. Set it to Expert to see all settings.

have fun :)

Link to comment
  • 2 months later...

I did another update with tvheadend_4.1-2409 and a more intuitive way to wakeup for recordings. (No more workarounds) You may have to disable/enable the plugin to change the setting to yes (if you want the wakeup - its pretty neat :) )

 

The server will wake up 5 minutes before the recording. Make sure you don't record to the cache disk if you dont want the server to shut down in the middle of the recording. Once the recording is done, the disk will eventually spin down and the sleep plugin will power down the server. Works like a charm for me!

 

Let me know what you think.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.