Wob76

Thanks for the reply CHBMB, I was only slightly hopeful, since it was working on rc3 it seems only a minor upgrade broke it . I will have a look when I get home, but it was working in the current slot on RC3. I think it is just going to be a waiting game till a fix is applied to the kernel. Just thought I would update if anything else is having issues with this driver. Thanks for all you help.

Hi, I have this docker working, but a couple of questions. I am only getting 1/2 listeners working, when I highlight it I see that the error is "x509: failed to load system roots and no roots provided". A google tells me this error in a docker container can be related to missing ca-certificates (http://blog.cloud66.com/x509-error-when-using-https-inside-a-docker-container/) and chance of a fix for this? Also how often does this docker get an update? or is it possible to in a update to the app in the docker, it is currently 14.3 but my other syncthing is up to 14.6. Thanks, Wob

Updated to RC5 last night, unfortunately my tuner still doesn't work

Thanks, I thought that would be the case, but thought best to check

Out of interest, does one need to update to say RC4 via the normal method before using the plugin, or can you go straight from a DVB RC4 ot DVB RC5 without causing any issues? Thanks, Wob

No joy with CrazyCat TBS.. Aug 30 10:18:44 TheBox kernel: dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware Aug 30 10:18:44 TheBox kernel: usb 4-1: Direct firmware load for dvb-usb-af9015.fw failed with error -2 Aug 30 10:18:44 TheBox kernel: dvb-usb: did not find the firmware file. (dvb-usb-af9015.fw) Please see linux/Documentation/dvb/ for more details on firmware-problems. (-2) Aug 30 10:18:44 TheBox kernel: dvb_usb_af9015: probe of 4-1:1.0 failed with error -2 Aug 30 10:18:44 TheBox kernel: usbcore: registered new interface driver dvb_usb_af9015 Thanks anyway, I'll just wait and see if a kernal patch fixes the issue, I don't use the tuner much, so not a huge issue.

Hey CHBMB, Gave it a try, but I still get the same result, Thanks for all your efforts. Wob

I just did it now to be sure, but still the same errors. I had rebooted, and removed\reinstalled the USB Tuner previously. I guess I will just have to wait and hope they fix the kernel. Thanks again, Wob

Thanks for all your help, I did some googling and found some older references to a similar issue, and it did seem to be Kernel related.

Still no luck, here are some snippits from my syslog. Can I run any commands to help diagnose the problem? Aug 24 09:23:41 TheBox kernel: usb 4-1: new high-speed USB device number 2 using xhci_hcd Aug 24 09:23:41 TheBox kernel: Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7 Aug 24 09:23:41 TheBox kernel: input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1c.6/0000:04:00.0/usb4/4-1/4-1:1.1/0003:15A4:9016.0001/input/input5 Aug 24 09:23:41 TheBox kernel: hid-generic 0003:15A4:9016.0001: input,hidraw0: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:04:00.0-1/input1 Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in cold state Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: downloading firmware from file 'dvb-usb-af9015.fw' Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 0x00000b, prod_id: 0x2000, dev_id: 0x13) Aug 24 09:23:41 TheBox kernel: ipmi_si IPI0001:00: IPMI kcs interface initialized Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer Aug 24 09:23:41 TheBox kernel: DVB: registering new adapter (Afatech AF9015 reference design) Aug 24 09:23:41 TheBox kernel: i2c i2c-0: af9013: firmware version 5.24.0.0 Aug 24 09:23:41 TheBox kernel: usb 4-1: DVB: registering adapter 0 frontend 0 (Afatech AF9013)... Aug 24 09:23:41 TheBox kernel: mxl5007t 0-00c0: creating new instance Aug 24 09:23:41 TheBox kernel: usb 4-1: dvb_usb_af9015: command failed=2 Aug 24 09:23:41 TheBox kernel: mxl5007t_read_reg: 505: failed! Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: error -121 on line 818 Aug 24 09:23:41 TheBox kernel: mxl5007t_get_chip_id: unable to identify device @ 0-00c0 Aug 24 09:23:41 TheBox kernel: mxl5007t_attach: error -121 on line 891 Aug 24 09:23:41 TheBox kernel: usbcore: registered new interface driver dvb_usb_af9015 Aug 24 09:24:02 TheBox root: plugin: installing: /boot/config/plugins/UnraidDVB.plg Aug 24 09:24:02 TheBox root: plugin: running: anonymous Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: plugin: running: anonymous Aug 24 09:24:02 TheBox root: plugin: skipping: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz already exists Aug 24 09:24:02 TheBox root: plugin: running: /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: +============================================================================== Aug 24 09:24:02 TheBox root: | Installing new package /boot/config/plugins/UnraidDVB/UnraidDVB-2016.08.18.txz Aug 24 09:24:02 TheBox root: +============================================================================== Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: Verifying package UnraidDVB-2016.08.18.txz. Aug 24 09:24:02 TheBox root: Installing package UnraidDVB-2016.08.18.txz: Aug 24 09:24:02 TheBox root: PACKAGE DESCRIPTION: Aug 24 09:24:02 TheBox root: Package UnraidDVB-2016.08.18.txz installed. Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: plugin: running: anonymous Aug 24 09:24:02 TheBox root: V6.2 compatible Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: ---------------------------------------------------- Aug 24 09:24:02 TheBox root: UnraidDVB has been installed. Aug 24 09:24:02 TheBox root: CHBMB/Squid Aug 24 09:24:02 TheBox root: Version: 2016.08.18 Aug 24 09:24:02 TheBox root: ---------------------------------------------------- Aug 24 09:24:02 TheBox root: Aug 24 09:24:02 TheBox root: plugin: installed Aug 24 09:24:55 TheBox root: tvheadend: Error response from daemon: error gathering device information while adding custom device "/dev/dvb": lstat /dev/dvb: no such file or directory Error: failed to start containers: tvheadend Edit: Also just noting I can see the firmware file located /lib/firmware/dvb-usb-af9015.fw And I have the following related files. /sys/bus/usb/drivers/dvb_usb_af9015 /sys/module/rc_core/holders/dvb_usb_af9015 /sys/module/dvb_usb_v2/holders/dvb_usb_af9015 /sys/module/dvb_usb_af9015 /sys/module/dvb_usb_af9015/drivers/usb:dvb_usb_af9015 /lib/modules/4.4.18-unRAID/kernel/drivers/media/usb/dvb-usb-v2/dvb-usb-af9015.ko.gz

Just repull the LibreELEC build from within the plugin. I did a repull and reboot but same result. Any other ideas? Can I post any logs to help? Sent from my SM-G900I using Tapatalk

No hassle at all, I appreciate all your hard work. Happy to test, will I see an updated DVB Plugin or do I just repull the LibreELEC build inside the plugin? Thanks, Wob

No Joy with remove\reinstall of usb device. Let me know if I can supply anything else. This is what I am seeing in the dvb plug in. unRAID Version: 6.2.0-rc4 DVB Version: LibreELEC Driver Version: 1.0.0 DVB Kernel: Detected DVB Adapter Drivers: Not Detected DVB Adapter 0: Afatech AF9013

When I can get near the box, I did the update remotely, I'll pull the usb tuner out and put it back in. i have rebooted a couple of times, but this could still help. Thanks, Wob

Hi, My update to rc4 hasn't worked, using LibreELEC with a USB dual tuner that uses the "Afatech AF9013" driver. It was working fine with rc3. This is what I am seeing in the logs; Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_v2: found a 'Afatech AF9015 reference design' in warm state Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer Aug 22 10:30:13 kernel: DVB: registering new adapter (Afatech AF9015 reference design) Aug 22 10:30:13 kernel: i2c i2c-0: af9013: firmware version 5.24.0.0 Aug 22 10:30:13 kernel: usb 4-1: DVB: registering adapter 0 frontend 0 (Afatech AF9013)... Aug 22 10:30:13 kernel: mxl5007t 0-00c0: creating new instance Aug 22 10:30:13 kernel: usb 4-1: dvb_usb_af9015: command failed=2 Aug 22 10:30:13 kernel: mxl5007t_read_reg: 505: failed! Aug 22 10:30:13 kernel: mxl5007t_get_chip_id: error -121 on line 818 Aug 22 10:30:13 kernel: mxl5007t_get_chip_id: unable to identify device @ 0-00c0 Aug 22 10:30:13 kernel: mxl5007t_attach: error -121 on line 891 Aug 22 10:30:13 kernel: usbcore: registered new interface driver dvb_usb_af9015 Any ideas? Thanks, Wob

OK, not sure what was going on. I pulled down a fresh version, with all the defaults to test. Worked fine. Reloaded with my existing configs, set a password, and it is working again. It may have been something to do with the URL I was entering. I am using a base path override (although since I am not actually reverse proxying jackett I could turn that off) If I go to http://server:9117/ it redirects to http://server:9117/jackett/Admin/Dashboard and is working fine. if I go to http://server:9117/jackett/ then I get the interface but with the error, so I am guessing you need to go to the base path and let the redirect kick in. So note, don't add base path unless you are going to specify the full path. Thanks, Wob

I had to remap docker.sock to get this to work. I am using 1.1.3 and it was looking for /var/tun/docker.sock inside the container, not /docker.sock as it was mapped in the template. I added a second Volume Mapping and it is all working. I haven't had any issues requiring any container restarting.

OK, there seems to be a problem with the Admin Password. I did a fresh install, first thing I did was set a Admin Password, then when I log back in it gives me the above mentioned errors. Remove the password from ServerConfig.json and it works again. Different password didn't make any difference. I restored my old config, removed the password and it all works. I don't expose my Jackett externally so I am just leaving it without a password set. Wob.

Tried clearing your browser cache? Hi CHBMB, Yep, I also tried an alternative browser without any luck. I might just delete the container and config, then set up again. Thanks, Wob

Looking at my logs since my last post and it appears that jacket is still working from a search point of view, I am still seeing logs for results found. But I can't access the admin dashboard.

I updated my container yesterday, everything was running fine, but now when I log into it I get an error "Error loading Jackett settings, request to Jackett server failed" and all my config is gone, if I click on anything I just get errors ending in request to jack failed. Docker log shows it boots up fine, I did restart to see if that would help but no luck. No further errors are show. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-update: executing... [cont-init.d] 20-update: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 08-10 17:15:10 Info Starting Jackett 0.7.303.0 08-10 17:15:10 Info Using HTTP Client: UnixLibCurlWebClient 08-10 17:15:10 Info LibCurl init Ok 08-10 17:15:10 Info LibCurl version libcurl/7.50.1 OpenSSL/1.0.2h zlib/1.2.8 libssh2/1.7.0 08-10 17:15:10 Info Starting web server at http://*:9117/ 08-10 17:15:45 Info redirecting to /jackett/Admin/Dashboard

Is this still the best way to get a container on the local LAN if using 6.2 (hand hence docker 1.10) https://hub.docker.com/r/dreamcat4/pipework/ now recommends alternatives for L2 bridging if using Docker 1.10 They link to this page (http://stackoverflow.com/questions/35742807/docker-1-10-containers-ip-in-lan) I tried following those steps but get stuck when attempting to bridge the bridge, I am using a bond and the tells me the interface is already bridge and can't be linked. I am trying to move my plex docker onto a different IP so I can monitor its bandwidth usage.

Thanks for the reply, I'll have a tinker and see how I go.

Hi dmacias, Just wondering, would it be a hard task to port you plugin to a self contained docker? or other freestanding install, on say a Raspberry Pi? I want to have something that I can make a little more portable, and I haven't been able to find anything that looks as nice as your output (graph, etc) Thanks, Wob

Super quick response. Thanks for looking into it.