optiman

I do not have any issues with my docker and the dvr is working fine. I have updated the docker recently, and still everything is working. I'm running the latest docker. unraid 6.6.7 However, if I go to the docker and then the hdhomerun WebUI, I see a message at the top that says No DVR detected. That is just a advertisement to purchase their dvr service. I just confirmed that shows are recording to my unraid / hdhomerun docker with no issues. Let me know if there is something you want me to check, as it does seem that you are the only one reporting this missing dvr issue.

@binhex Thank you so much! I installed and tested the couchpotato script and that worked! I think we're good to go. I'm now waiting for a tv show to dl to test the sickbeard script. I'm all caught up so nothing to dl just yet. I'll confirm back once the sb script runs. Thanks again for the speedy response! Update: @binhex - I have confirmed that both sb and cp scripts are now working. 😀

@clinton.hall Ok, thank you again for your help. So I have python3 installed via nerdpack at the unraid server level. But from what you are saying, the sab docker container should also include python3 - but for some reason it is not? @binhex I have already did a Forced Update so I should have the latest version. Also keep in mind that I did a fresh install about 10 months back. How can I fix this issue and do you know why python3 isn't showing up inside the sab docker container?

@clinton.hall Here you go: root@Tower:~# docker exec -it binhex-sabnzbd bash [root@Tower /]# cd /usr/bin [root@Tower bin]# ls -al py* -rwxr-xr-x 1 root root 78 Jun 27 2018 pydoc2 lrwxrwxrwx 1 root root 18 Jan 18 15:41 python -> /usr/bin/python2.7 lrwxrwxrwx 1 root root 9 Jun 27 2018 python2 -> python2.7 -rwxr-xr-x 1 root root 5920 Jun 27 2018 python2.7 -rwxr-xr-x 1 root root 1681 Jun 27 2018 python2.7-config lrwxrwxrwx 1 root root 16 Jun 27 2018 python2-config -> python2.7-config [root@Tower bin]# which python /usr/sbin/python [root@Tower bin]#

@clinton.hall Ok, I went back into the terminal inside the sab docker and ran that command. I then sent a dl to sab, and it failed - just like it did before we changed the link to python2. Below is a test dl. The file dl's and unpacks, then runs the script, but fails when it can't find python. When I put it back to what we tested, ln -sf /usr/bin/python2.7 /usr/bin/python It works again. I can also repeat this testing by just doing a Forced Update for this docker container, which puts it back to python3. After the update, I have to go back into the terminal inside the docker and link it to python2.7 Just for the record, my unraid is most stock, very little custom stuff. I only have a few dockers and all but one are Bin-hex and again with no custom stuff. I just install and they work. I also have Nerdpack installed, but again only a few packages are installed. Both python2.7 and python3 are installed and up to date. I'm curious what we do next....

@binhex Thank you sir! Good info, but some of that is over my head. My hope is that we can find a solution that isn't a one-off or custom fix that has to be reapplied each time there is an update to either your docker or his script, not to mention an update to unraid. I have relayed the message back to Clinton, as the nzbtomedia script is his. I think given the number of people who run your sab docker and his script, it would be best for the two of you to talk directly and help find the best path forward. I've invited him to visit this thread. Many Thanks!

@binhex My unraid setup has been solid for months now and I've made no changes at all. Since 1/3/2019, I now see this error on the main sabnzbz webgui for each download, /usr/bin/env: ‘python’: No such file or directory I looked and the file downloads fine and extracts. The tv show file is in the directory, yet the script errors out with Exit 127 /usr/bin/env: ‘python’: No such file or directory I've been working with Clinton Hall to troubleshoot why the nzbtomedia script started failing and we have found that due to recent updates, we now need to link Python to Python2. To temporary fix this, I had to ssh into a terminal inside the sab docker and run this command; ln -sf /usr/bin/python2.7 /usr/bin/python While that resolved the issue and I no longer get any errors, this fix will be reverted with your next update. To test this part, I did a Forced Update for this docker and it broke the link. I once again had to ssh in and link python again. Here are the suggestions from Clinton: Have a script run at startup that will ssh into docker and then make the link with /usr/bin... or Ask binhex if this can be added into future sab dockers. Can you please add the python link in your next update to fix this? I would prefer this be fixed inside the sab docker, and I would rather avoid having to have a custom script, if possible. many thanks!

I thought there were 3 version of python, but after reading your reply I understand there are only two versions, python2 and python3. I have both installed via nerdpack. You are right, the command python is not working so I need a link. I just ran sudo find / -type f -name 'python*' -perm -a+x root@Tower:/mnt/user/Automation/Apps/binhex-sabnzbd/nzbToMedia# sudo find / -type f -name 'python*' -perm -a+x /usr/lib64/python3.6/config-3.6m-x86_64-linux-gnu/python-config.py /usr/bin/python2.7 /usr/bin/python2.7-config /usr/bin/python3.6m /usr/bin/python3.6 /usr/bin/python3.6m-config /boot/config/plugins/NerdPack/packages/6.3/python3-3.6.1a-x86_64-1.txz /boot/config/plugins/NerdPack/packages/6.5/python-2.7.14a-x86_64-1.txz /boot/config/plugins/NerdPack/packages/6.5/python3-3.6.2b-x86_64-1.txz this is only the first part, and then the screen scrolled up past where I an copy / paste here.

I have nerd pack installed and I see both python2 and python3 are available and installed. I do not see Python listed, yet I I know Python is installed. I'm surprised not to see Python in the list. Is this normal? I discovered this because I wanted to check and see if I had the latest version of Python installed.

sickrage is dead, for the most part. Upgrade to sickchill - read this thread for instructions

I have moved to SC and restored the backup from SR. Everything is there and looks good. I did a rescan for all files for all tv shows. In the log I saw this line for all of my tv shows - show Dir doesn't exist, skipping NFO generation and it then moves to the next show. I did not see these messages in the SR logs. Will this correct itself, or do I need to fix it? Thank you! Here is the actual log entree: update: I had to edit each show and re-point to the show directory. I just need to test the nzbtomedia script and should be good to go.

Many thanks clinton.hall!

For the nzbtomedia script, I have reached out to clinton-hall, who manages and updates that script. I'm hoping he can help us with the migration steps to SC.

doesn't sound like you are using the nzbtomedia script. If you are not, yes it looks very simple. I need to confirm if the cfg file needs to be edited so that the script still works correctly. Anyone out there using the script and have migrated to SC?

ok, thanks for the additional information. With that, I will migrate soon. I just want to hear from others using nzbtomedia script first to ensure that works with SC, or how to ensure it will work (migration steps).

I use nzbtomedia and it is working great with SR. It took a while for me to sort that out and I'm worried about breaking it. I'd like others running SR and the nzbtomedia script to confirm my above steps are safe steps to migrate. It sure would be nice to just keep SR up and running, as it works great and it isn't broken. I vote to keep it if we can.

Before I swtich to Sickchill, I kindly ask that you help confirm the steps to be taken. I rolled back to :v2018.10.06-1-01 a couple weeks ago, when the last update broke SR. It's been running great ever since, although it will not get any updates. I use nzbtomedia script, which is working perfectly right now. What steps are necessary to keep nzbtomedia working? In your notes, you say to perform a backup prior to 10/13, how ever that date has passed. I did a backup today, again I'm on :v2018.10.06-1-01. Please confirm is these steps are correct. 1. I have SR backup already, taken today. 2. Install Sickchill docker, using the same config settings as I used with SR (tv directory, download directory, and create a new directory on my cache drive for Sickchill. 3. Stop SR and start Sickchill. 4. Go to Sickchill webgui and restore the SR backup file. I hope this restores my account and search provider information. 5. Copy nzbtomedia folder that is currently in my SR folder To the Sickchill folder. There is no Sickchill section in autoProcessMedia.cfg, so do I need to make any changes to this config file or does it still point to SR section? Did I miss anything?

My SR install was fresh only a few months ago and it has prompted me to update several times since I've installed it. I fully deleted my dockers at that time and recreated / installed everything fresh on a new cache drive. In any case, now I know that trick so thanks again! After a new working release comes out, I'll put mine to latest.

my repository line has this: binhex/arch-sickrage Yours has the word latest and then I see you point to a specific release. I'm just curious why mine did not have the latest part at the end. My install was a fresh install of the binhex SR docker, with all defaults, and it has been working perfect until this last update blew it up. I've never had to delete an orphan from docker tab either, so I need to read a little more before doing this. Thanks! Update: ok, deleting orphan container is super easy, obvious which one to delete. Changing the repository line worked great! I'm back up and running again. Thanks you again!

I've never tried to roll back a docker before. So to confirm, I just go to the console and type binhex/arch-sickrage:v2018.10.06-1-01 And that will roll back SR? I don't need to stop any service, or restart the server, nothing else? Many thanks!

I updated today and now SR docker starts, but I cannot access the WUI, so this last update broke it.

I used the minidnla docker as well as the hdhomerun docker, and it works as expected. You still have to link the the two together to record shows.

You need to install and use binhex-minidlna. You will then see the Linux icon, select that, login, and save. Assuming you have your directory path set correctly, should work. Of course you also need to setup a share. To help you with the minidnla settings, see mine below.

@limetech I have run several tests that write to the cache pool and then the Mover transferring them to the array. I also ran a full Parity check, all good. Syslog shows no major errors and as mentioned in my last post, trim command ran successfully. However, I just noticed that my Used Space on my cache in the gui is now showing about half of what it was before. It was showing I had about 84gb in use and this is when the Mover has ran, and now it shows about 44gb. I have checked and all my files that should be on the cache drive are there. My dockers are running on the cache drive and working great. With that, it seems that the gui is just reporting the wrong information. Maybe splitting the total in use by 2 x drives ?? Again, no errors in syslog. I did a quick search and nothing came up that matched my issue. Should I be worried about this?

I installed a 2nd 1tb ssd drive and connected both the new one and the existing ssd to my mb sata ports. Enabled Trim to be scheduled and no more errors. output that is in the log: Sep 23 06:00:32 Tower root: /var/lib/docker: 34.4 GiB (36966330368 bytes) trimmed Sep 23 06:00:32 Tower root: /mnt/cache: 1.7 TiB (1853984260096 bytes) trimmed I did not bother trying to upgrade the firmware 9305. At this point, I yield and do what most others have done, and be forced to put ssd's on mb ports.