lionelhutz

I'm going to provide more of an overview then a step by step guide. At this time, I'm not going to get into exact step by step detail to the level it take to get someone with no prior knowledge about any of this running. I'm assuming anyone reading this is using Community Applications, can install Dockers and plugins, has some basic command line knowledge, can use the right text editors to edit Linux script and config files and (most obviously) knows enough or can read enough about newznab to set it up and configure it. 1. Install the following - Nerd Tools plugin. - Linuxserver.io Apache Docker. - Any MariaDb or MySQL Docker or Plugin. The database Docker or plugin version really doesn't matter since you can connect Newznab to any of them. At this time i am using Needo's MariaDB docker because it was the first database docker published and I've been doing this since dockers were first around. I've never changed it because it still works. But, the Linuxserver.io docker would be one of the more obvious choices here. 2. In the Nerd Tools configuration install the following packages. - apr - apr-utils - neon - serf - subversion These are needed to run subversion to download Newznab. I have the Perl package installed but I don't believe it is required for subversion. If the subversion command line doesn't work then install it too. 3. Download Newznab Log-onto the unRAID server and go to the Apache Docker installation location - the directory where you pointed /config to in the Apache docker setup. Then, further go into the www directory that is there. Now, use Subversion to download Newznab. The command line should be, - svn checkout svn://svn.newznab.com/nn/branches/nnplus If this works how I remember, you should have the newznab install directly in this www directory so you have 5 directories and 6 files in the directory. If it dumped everything into yet another subdirectory them move everything from that directory to the www directory and delete that subdirectory. You should have paid for Newznab by now and received a username and password to use for this. 4. Setup the Apache docker. By default Apache is looking for the website in the www directory where you just installed Newznab but Newznab creates another www directory inside the Docker www directory. So, you have to setup Apache so it looks for it in the www/www directory. Go to the same Apache docker "/config" directory as in step 3 then go into the apache\site-confs subdirectory and edit the default.conf file. Change the top part to look like this. <VirtualHost *:80> DocumentRoot /config/www/www <Directory "/config/www/www"> Options Indexes FollowSymLinks MultiViews AllowOverride all Order allow,deny Allow from all </Directory> </VirtualHost> Basically, just change /www to be /www/www Now setup the Apache docker to use the advance script so you can install perl and unrar (optionally for use in Newznab for deeper password checking). In the Apache docker setup set the "ADVANCED_SCRIPT" variable to true. In the Apache install directory (where you pointed /config) put a file called "userscript.sh" containing the following. apt-get install php-pear apt-get install unrar-free Now, restart the Apache docker and go to it's WebUI and you should get the Newnab setup page. It'll take a bit the first time because the docker has to install those packages first before being run. Go through the setup pages and point it to your usenet server and the MariaDB or mySQL database and it should come up ready to use. As a minimum, you need to go into the site setup and put in your Newznab ID and you should also activate a single group for testing to ensure it's working. Since I installed unrar I put "/usr/bin/unrar" into the path to unrar box in the Newznab site setup. Then, I could use deep password checking. 5. The last part is to setup the indexing script. Yet again starting at the same Apache "/config" directory in step 3, go to this directory. - \www\misc\update_scripts\nix_scripts. Edit the newznab_screen.sh file and edit the top part to look something like this. #!/bin/sh # call this script from within screen to get binaries, processes releases and # every half day get tv/theatre info and optimise the database set -e export NEWZNAB_PATH="/config/www/misc/update_scripts" export NEWZNAB_SLEEP_TIME="300" # in seconds LASTOPTIMIZE=`date +%s` while : do CURRTIME=`date +%s` cd ${NEWZNAB_PATH} #/usr/bin/php5 ${NEWZNAB_PATH}/update_binaries.php /usr/bin/php5 ${NEWZNAB_PATH}/update_binaries_threaded.php /usr/bin/php5 ${NEWZNAB_PATH}/update_releases.php The import line is the NEWZNAB_PATH because and to take the # off the start of the update script lines for the ones you want to use. I use the threaded update binaries script but you could use the other script too. I use 300 seconds or 5 minutes as the update interval but you can change this to whatever time interval you want. 6. Now, test it to make sure it will index. Log-in to the Apache docker by using this line at the unRAID command prompt. - docker exec -t -i Apache /bin/bash Then run this. - sh /config/www/misc/update_scripts/nix_scripts/newznab_screen.sh And the update scripts should start to run. 6. To automate the updating when the Apache docker runs add this line to the Apache userscript.sh file and re-start the apache docker. sh /config/www/misc/update_scripts/nix_scripts/newznab_screen.sh &>/dev/null & I would recommend you "Browse Groups" to check they are being updated at least once a day. If they quit being updated then just re-start the Apache docker. As you can see, this isn't simple. The last time I actually did this was at least a year ago so I might have missed something. So, let me know if you get so far and I missed something obvious so it doesn't work for you.

No, it's not been discussed lately. There never seemed to be much interest in running newznab here. Basically I use, Linuxserver.io Apache docker to run the web interface. This docker has everything needed to make it easy to get running. A MariaDB docker for the back-end database, any MariaDB or MySQL database docker would work. NerdTools to install the packages needed to run subversion so I can download newznab from the unRAID command line. I've been running newznab since before Dockers existed then with Dockers before anyone had an "unRAID Apache" docker. So, I've gone through multiple ways to do it. Running it bare metal actually was fairly easy to do but during one of the unRAID releases there was no support for another web server so I switched to dockers. The Linuxserver.io Apache docker was the first I found to be easily customized so it would just work. I could start a thread with an overview of what to do to get it running if people are actually interested. The problem is without me actually going through the setup again I would probably miss a step or two. For example, I can't see the newznab initial setup pages unless I started over with it.

Is it allowed to discuss running your own indexer by using a couple of dockers and the nerd tools plugin?

Mover doesn't work like that. (And if it did, it would be rather pointless) It physically moves the file. If anything its actually far more inefficient since hardlink support came into effect with 6.2 I wasn't clear enough ... my statement was about how the file is moved/renamed between SAB and Sickbeard, not how mover copies the file from the cache disk to the data disk. Actually doesn't even matter there either. Because /mnt/user/TV Shows and /mnt/user/Downloads are different mount points, the system will always do a copy / delete. No linking involved. But, that might be the key here. Vast majority of users add multiple paths to a docker app instead of just passing in /mnt/user So now you've got a single mount point passed through to a docker app that ultimately contains multiple mount points. I would surmise that the docker system is puking at that and just doing the rename instead of actually following the rules for following mounts. Solution is to pass separate mounts to all the docker apps involved of /downloads and /tv and make all the internal references point to them and ditch the mapping of /mnt or /mnt/user If this works, then its probably also @Nick5429's issue as he also is apparently passing through /mnt/user and then its an actual issue with docker, not unRaid per se. I have tried it with my TV_Shows share set to use cache and not use it and it works correctly both ways for me. I only pass through the lower level directory to my dockers. No /mnt or /mnt/user gets passed through. For example Sickbeard uses, /downloads -> /mnt/cache/appdata/Downloads/ /tv -> /mnt/user/TV_Shows/ /config -> /mnt/cache/appdata/Sickbeard/

I have turned the use cache setting on and off on my TV share and files are not written to the cache with it turned off. You have a setup problem. What downloader and how is is the post-processing being done?

"Root Directories" like you are describing isn't a SickBeard setting so it must be something to do with the plugin settings??? What does Sickbeard show here? Go to a show that is on the cache disk and see what is under the location here? This is a Docker so /tv is mapped to the user share by the Docker settings.

Did you stop the array and re-start it in normal mode?

You have Sickbeard pointed to /mount/cache/TV Series. Either in the Docker config or in the Sickbeard config. You need to change it to /mnt/user/TV Series.

Yes, rebuilding the docker would require making the link again. Probably the easiest way is to use the user script option and make a script that creates the link. That way, you don't have to go into the container and it will get created.

The server ran 24/7 from the end of September until Friday and then it locked-up again. I reset it and it did it again on Saturday. So, it appeared to be good but isn't and I still don't know why. There was a BIOS update for the motherboard so maybe it'll help.

If you want to explain your directory structure for each of those shares and how you'd like them stored then we can suggest initial share settings. I recommend this before you go off and end up with something you decide you want to fix later. Personally, I would not use the default settings to initially fill a new server.

It appears to be old server hardware so it might run at 200W even with the disks spun down. Picking the right newer hardware can run 50W with the disks spun down. Take wattage times hours per year and divide by 1000 to convert to kWh. Then, multiply by your local kWh billing rate to calculate the electricity cost. Hint - the final multiplier is 8.76 to calculate yearly kWh from wattage for always on usage. Here, it could mean the difference between about $75/year and $300/year or about $6 a month vs $24 a month.

Those controllers weren't supported probably a year or so ago. I'm not sure if they ever got included into newer versions or not. Maybe post specifically asking if that card works here or in the general support area for a quicker answer. The rest would likely work but would probably be power hungry. If the Areca card does work then it and the case plus some other small parts you could re-use are likely worth the $100.

The VM image only uses the size required. I have some VM's all sized at 40gig and they are reported as 40gig but the size on disk are 27gig, 17gig or 33gig.

Nice mess. The gouge looks deep enough it would soon cause the center to break out of the patter. You should let it go and see if it'll explode... I had a drive years ago fail where one where the one side of the platter was fairly evenly ground down so there was no shine left on it. There was a lot of dust in it. It happened in < 10 hours while I was at work. The drive was continually seeking and then parking the bad head across the platter when I came home. You know the very audible seek and park sounds old drives would make.

FYI, if you copy the UUID code from the XML and use that code to create a new VM then when you install W10 it will activate itself once it goes online. Each VM needs a unique UUID so you have to copy the UUID and delete the old VM before editing the XML of the new VM to change it's UID.

You're asking about moving the Dockers from an old unRAID server to a new one, right? Just wanting to make sure you don't have the Dockers running one some other OS. To move to a new unRAID server, I'd think all you have to do is copy the app data to the new server into the same location and copy the xml files from the flash\config\plugins\dockerMan\templates-user directory to the new USB drive. Then, turn-on docker and when you click the Add Docker button under the templates there should be my-xxx templates for every docker you had installed. Select each one and click the Create button and the Docker should get installed just like it was on the old server. Of course, if you move the flash drive and hard drives to the new server then the Dockers will just keep working like before. It's stupid easy to upgrade hardware.

You can't pass through a whole USB controller? That's the easy solution to hot-plugging USB devices.

Yes, no issues since disabling the C states. I'm not sure why because I never spent any more time trying to find out, but in my case it was definitely a C-state issue.

I disabled the C-states in the bios and my server has run without locking up for 9 days so far. Previous best was about 3-4 days before I would find it locked up. I'm not sure what impact this has on energy use but I expect little for me since I have some dockers that are always working. I'm going to try and get the power meter on it soon to see if it does make a difference.

You can't pass the integrated video/audio to a VM.

Just saw this and can only respond quickly. I've had the same problem without running any VM's so the VM isn't the issue. Is your system Skylake based?

W10 uses an online activation that ties to the hardware. The W10 update activation doesn't give the user a new key so it's activation is tied to the motherboard (along with the rest of the hardware combination) of the machine that the W10 update was performed on. Since the update doesn't give a license key, you can't transfer the licensed W10 install to another machine. Even when just making enough changes to the hardware you'll need to buy W10.

A little hint. docker exec -t -i 37fcc75e886d /bin/bash You can just put the docker name where "37fcc75e886d" is.

Wasn't even aware of it....installing it now. One question about it, and a big reason I don't want to completely wipe my docker.img file - does it retain the data within the dockers? I've got a bunch of stuff / config within my mariadb, and the thought of recreating it isn't overly appealing. No, all the config stuff is stored in the appdata directory unless you manually edited the docker after installing it.