betaman

I have some interest if I can ever get this docker to start! Seriously though, I'd like it and in particular with deluge. Thanks.

yep thats normal, the existing layers are from the base image which is common to all my docker images, as well as the openvpn image, which again is common to all the vpn dockers, the 13MB your seeing is the actual size of the difference, the unique layers. the docker will attempt to start even with badly configured vpn info, yes, but it wont get too far as it will attempt to create the tunnel and fail, at that point its game over and you will never get passed that point until the issue is resolved (by design). but for some reason your having issues much earlier on, just cant work out what it is. can you double check you def do not have anything else running on port 8080 or 8090 (not running unmenu are you?) one last question, and im hoping this isnt the issue, what version of unraid are you running?. Ok, I started troubleshooting using your basic template. On first install, docker won't run. If I uncheck Privileged then it runs. If I add my /config and /data folders (with Privileged unchecked) it again won't run. All other variables are left as-is with your default template. I deleted my /config directory and the docker appears to recreate it without issue (although it's empty). My /data directory is used by several other dockers so I can't see it being an issue but I could be wrong. I'm using UnRAID 6.1.9. I did have linuxserver.io's SABnzbd docker running on those ports but I've since deleted that docker and rebooted the server prior to posting my issue today. No unmenu running. ok im stumped for now, i will have to rack my brain for any ideas, just to double check i did a clean install here and it started with no issues Thanks for checking the clean install. Are you running 6.1.9 or the 6.2 RC? The only other thing I've been playing with is the ADVANCED_DISABLEUPDATES ENV variable. I couldn't get the linuxserver.io docker to load and in that support thread I read about something being broken. Once I added this variable, the docker would load fine. I tried the same with your docker but no dice. im running 6.1.9, the ADVANCED_DISABLEUPDATES env var is specific to linuxserver.io docker images, as they auto update on restart, mine dont. FWIW, I was able to configure your regular SABnzbd docker and get it to start. Something with the VPN version isn't allowing me to configure it correctly.

yep thats normal, the existing layers are from the base image which is common to all my docker images, as well as the openvpn image, which again is common to all the vpn dockers, the 13MB your seeing is the actual size of the difference, the unique layers. the docker will attempt to start even with badly configured vpn info, yes, but it wont get too far as it will attempt to create the tunnel and fail, at that point its game over and you will never get passed that point until the issue is resolved (by design). but for some reason your having issues much earlier on, just cant work out what it is. can you double check you def do not have anything else running on port 8080 or 8090 (not running unmenu are you?) one last question, and im hoping this isnt the issue, what version of unraid are you running?. Ok, I started troubleshooting using your basic template. On first install, docker won't run. If I uncheck Privileged then it runs. If I add my /config and /data folders (with Privileged unchecked) it again won't run. All other variables are left as-is with your default template. I deleted my /config directory and the docker appears to recreate it without issue (although it's empty). My /data directory is used by several other dockers so I can't see it being an issue but I could be wrong. I'm using UnRAID 6.1.9. I did have linuxserver.io's SABnzbd docker running on those ports but I've since deleted that docker and rebooted the server prior to posting my issue today. No unmenu running. ok im stumped for now, i will have to rack my brain for any ideas, just to double check i did a clean install here and it started with no issues Thanks for checking the clean install. Are you running 6.1.9 or the 6.2 RC? The only other thing I've been playing with is the ADVANCED_DISABLEUPDATES ENV variable. I couldn't get the linuxserver.io docker to load and in that support thread I read about something being broken. Once I added this variable, the docker would load fine. I tried the same with your docker but no dice.

yep thats normal, the existing layers are from the base image which is common to all my docker images, as well as the openvpn image, which again is common to all the vpn dockers, the 13MB your seeing is the actual size of the difference, the unique layers. the docker will attempt to start even with badly configured vpn info, yes, but it wont get too far as it will attempt to create the tunnel and fail, at that point its game over and you will never get passed that point until the issue is resolved (by design). but for some reason your having issues much earlier on, just cant work out what it is. can you double check you def do not have anything else running on port 8080 or 8090 (not running unmenu are you?) one last question, and im hoping this isnt the issue, what version of unraid are you running?. Ok, I started troubleshooting using your basic template. On first install, docker won't run. If I uncheck Privileged then it runs. If I add my /config and /data folders (with Privileged unchecked) it again won't run. All other variables are left as-is with your default template. I deleted my /config directory and the docker appears to recreate it without issue (although it's empty). My /data directory is used by several other dockers so I can't see it being an issue but I could be wrong. I'm using UnRAID 6.1.9. I did have linuxserver.io's SABnzbd docker running on those ports but I've since deleted that docker and rebooted the server prior to posting my issue today. No unmenu running.

I changed the name of the docker to SABnzbdVPN and when I type "docker logs SABnzbdVPN" it just brings back the prompt. Just to confirm the command was working, I tried delugeVPN and got a response. hmm ok screenshots is all we have then, can you please left click the icon, select edit and then toggle the advanced view option on then take a screenshot (you might want to temporarily remove username and password from the vpn section). Ok, before I do that, I noticed a configuration difference between your SABnzbd docker and linuxserver.io's. The Privileged checkbox in the advanced view was ticked with the default settings. If I uncheck this box then the docker starts. I need to configure all of my variables to see if the gui will start but is this an issue if it solves my problem? you will need to have the privileged checkbox ticked for this docker to run, it creates a vpn tunnel adapter which wont happen unless you have that checked, there are a LOT of differences between this one and the linux io one, as this includes a vpn which needs to be configured (see advanced settings). Ok, the only way I could get the docker to start was to load your default and uncheck Privileged. Once I updated directories, and ENV variable information, the docker would no longer start with the attached settings. ok two things, firstly are you sure the defined LAN_NETWORK is correct?, as in is your lan network 192.168.1.x ?, secondly check the permissions on the unraid side for /config and /data, your using user nobody group users (99 and 100), which is the standard permissions for unraid, if you have it set to something else then you will need to change the PUID and PGID values. oh and lastly, make sure you have ALL sabnzbd docker containers stopped, otherwise you will get a port clash I just went through all of this setting up PIA with your delugeVPN docker and it's working fine with the same settings. I figured this would be a breeze to setup having gone through a couple issues there (mostly related to updating the dynamix webgui). Anyway, permissions on both directories is the default (plus I re-ran the permissions tool on my cache drive just to be sure). One other thing I noticed is that even when I delete the docker plus container iso, when I reinstall, it just pulls 13MB as it thinks the image already exists?! Finally, just to be clear, I thought the docker would start successfully even if the VPN info wasn't correct and only the webgui would be affected?

I changed the name of the docker to SABnzbdVPN and when I type "docker logs SABnzbdVPN" it just brings back the prompt. Just to confirm the command was working, I tried delugeVPN and got a response. hmm ok screenshots is all we have then, can you please left click the icon, select edit and then toggle the advanced view option on then take a screenshot (you might want to temporarily remove username and password from the vpn section). Ok, before I do that, I noticed a configuration difference between your SABnzbd docker and linuxserver.io's. The Privileged checkbox in the advanced view was ticked with the default settings. If I uncheck this box then the docker starts. I need to configure all of my variables to see if the gui will start but is this an issue if it solves my problem? you will need to have the privileged checkbox ticked for this docker to run, it creates a vpn tunnel adapter which wont happen unless you have that checked, there are a LOT of differences between this one and the linux io one, as this includes a vpn which needs to be configured (see advanced settings). Ok, the only way I could get the docker to start was to load your default and uncheck Privileged. Once I updated directories, and ENV variable information, the docker would no longer start with the attached settings.

I changed the name of the docker to SABnzbdVPN and when I type "docker logs SABnzbdVPN" it just brings back the prompt. Just to confirm the command was working, I tried delugeVPN and got a response. hmm ok screenshots is all we have then, can you please left click the icon, select edit and then toggle the advanced view option on then take a screenshot (you might want to temporarily remove username and password from the vpn section). Ok, before I do that, I noticed a configuration difference between your SABnzbd docker and linuxserver.io's. The Privileged checkbox in the advanced view was ticked with the default settings. If I uncheck this box then the docker starts. I need to configure all of my variables to see if the gui will start but is this an issue if it solves my problem?

I changed the name of the docker to SABnzbdVPN and when I type "docker logs SABnzbdVPN" it just brings back the prompt. Just to confirm the command was working, I tried delugeVPN and got a response.

Yeah, that's just it. My /config directory (/mnt/cache/appdata/SABnzbVPN/) is empty but it shows the docker installed on my docker page?!

I'm still not seeing an update available... how did you update? Sent from my HTC6535LVW using Tapatalk I didn't actually "update". I'm coming over from linuxserver.io's docker because I wanted the VPN. I noticed the update issue with my current version so I added the ENV variable ADVANCED_DISABLEUPDATES and it loaded. When I installed this docker, I tried with and without this variable but still couldn't get it to load. This is an unraid bug, left click icon in unraid webui, select edit, change nothing and click save to pull the latest down Sent from my SM-G900F using Tapatalk I still can't get the docker to start. Here's my UnRAID log from when I initiate the "start" of the docker: Jul 11 09:22:43 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'SABnzbdVPN' Jul 11 09:22:43 Tower kernel: device veth44766e5 entered promiscuous mode Jul 11 09:22:43 Tower kernel: docker0: port 3(veth44766e5) entered forwarding state Jul 11 09:22:43 Tower kernel: docker0: port 3(veth44766e5) entered forwarding state Jul 11 09:22:43 Tower kernel: docker0: port 3(veth44766e5) entered disabled state Jul 11 09:22:43 Tower avahi-daemon[13940]: Withdrawing workstation service for vethd8970f6. Jul 11 09:22:43 Tower avahi-daemon[13940]: Withdrawing workstation service for veth44766e5. Jul 11 09:22:43 Tower kernel: device veth44766e5 left promiscuous mode Jul 11 09:22:43 Tower kernel: docker0: port 3(veth44766e5) entered disabled state

I'm still not seeing an update available... how did you update? Sent from my HTC6535LVW using Tapatalk I didn't actually "update". I'm coming over from linuxserver.io's docker because I wanted the VPN. I noticed the update issue with my current version so I added the ENV variable ADVANCED_DISABLEUPDATES and it loaded. When I installed this docker, I tried with and without this variable but still couldn't get it to load.

I can't seem to get this version to run. Docker installs but won't start. I know there's an issue with the PPA and the auto update but does this affect a first time install? Does this image need to be rolled back to the previous SABnzbd version? SabnzbdVPN log is blank and UnRAID log doesn't show any errors.

Thanks! Once I updated the webui plugin it installed correctly. Pretty sure those missing ENV's were my issue since I came from the non-VPN version of Deluge my existing template didn't have those defined and I just added the ones I read about in the thread. Just checked my torrent IP and I'm all set!

So I thought the above was my issue but I still can't seem to get PIA to connect to DelugeVPN. I've set all the ENV variables and still my supervisord.log just looks like this: 2016-07-07 17:05:05,337 CRIT Set uid to user 0 2016-07-07 17:05:05,337 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing 2016-07-07 17:05:05,340 INFO supervisord started with pid 12 2016-07-07 17:05:06,342 INFO spawned: 'deluged' with pid 15 2016-07-07 17:05:06,343 INFO spawned: 'deluge-web' with pid 16 2016-07-07 17:05:07,344 INFO success: deluged entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-07-07 17:05:07,344 INFO success: deluge-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) When I use checkmytorrentip it just returns the IP provided by my ISP?! I have the following ENV variables defined: LAN_NETWORK 192.168.1.0/24 (Server ip is 192.168.1.71, using DHCP Reservation and 255.255.255.0) VPN_PROV pia VPN_USER "PIA Username" VPN_PASS "PIA Password" VPN_ENABLED yes Same volume & port mappings as others have posted. I tried deleting my docker image as well as my config directory to reinstall the delugevpn docker. I noticed the default template has more ENV variables defined so I'm guessing this might be my issue (e.g. VPN_REMOTE, VPN_PORT, VPN_PROTOCOL); however, I can't seem to get the docker installed correctly now?! root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="binhex-delugevpn" --net="bridge" --privileged="true" -e VPN_ENABLED="yes" -e VPN_USER="********" -e VPN_PASS="**********" -e VPN_REMOTE="nl.privateinternetaccess.com" -e VPN_PORT="1194" -e VPN_PROTOCOL="udp" -e VPN_PROV="pia" -e ENABLE_PRIVOXY="no" -e LAN_NETWORK="192.168.1.0/24" -e DEBUG="false" -e PUID="99" -e PGID="100" -e TZ="America/New_York" -p 8112:8112/tcp -p 58846:58846/tcp -p 8118:8118/tcp -v "/mnt/cache/appdata/DelugeVPN/":"/config":rw -v "/mnt/cache/appdata/downloads/incomplete/":"/data":rw binhex/arch-delugevpn sh: airvpn: command not found sh: custom: command not found docker: "run" requires a minimum of 1 argument. See '/usr/bin/docker run --help'. Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...] Run a command in a new container The command finished successfully! When I check my docker page, the delugeVPN doesn't show up in basic view. When I switch views, it shows an orphaned docker. I tried deleting and reinstalling but no luck.

So I thought the above was my issue but I still can't seem to get PIA to connect to DelugeVPN. I've set all the ENV variables and still my supervisord.log just looks like this: 2016-07-07 17:05:05,337 CRIT Set uid to user 0 2016-07-07 17:05:05,337 INFO Included extra file "/etc/supervisor/conf.d/deluge.conf" during parsing 2016-07-07 17:05:05,340 INFO supervisord started with pid 12 2016-07-07 17:05:06,342 INFO spawned: 'deluged' with pid 15 2016-07-07 17:05:06,343 INFO spawned: 'deluge-web' with pid 16 2016-07-07 17:05:07,344 INFO success: deluged entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-07-07 17:05:07,344 INFO success: deluge-web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) When I use checkmytorrentip it just returns the IP provided by my ISP?! I have the following ENV variables defined: LAN_NETWORK 192.168.1.0/24 (Server ip is 192.168.1.71, using DHCP Reservation and 255.255.255.0) VPN_PROV pia VPN_USER "PIA Username" VPN_PASS "PIA Password" VPN_ENABLED yes Same volume & port mappings as others have posted.

Just reporting back that the U9's fit perfectly (fans centered) and my cpu temps went from 68/74C to 39/41C (cpu1/cpu2). Couldn't be more pleased with the ease of installation and results.

Well, I installed Perl and ran sensors-detect. This is the output: # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200) # System: Rackable Systems Inc. CYPRESS11 [..................] # Board: Intel Corporation S2600CP This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... Success! (driver `coretemp') Intel AMB FB-DIMM thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Found `IPMI BMC KCS' at 0xca2... Success! (confidence 8, driver `to-be-written') Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (YES/no): YES Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): no Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `to-be-written': * ISA bus, address 0xca2 Chip `IPMI BMC KCS' (confidence: Driver `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Note: there is no driver for IPMI BMC KCS yet. Check http://www.lm-sensors.org/wiki/Devices for updates. I still can't get the Dynamix GUI to auto detect coretemp so I can load it. I noticed in the terminal output the following when I hit the detect button: grep: /etc/sensors.d/sensors.conf: No such file or directory yes: standard output: Broken pipe yes: write error grep: /etc/sensors.d/sensors.conf: No such file or directory Did you use the Dynamix plugin to load coretemp? EDIT: After a few minutes I tried the Detect button again and now I have the following options:

Ok, I think it finally get it. I installed the Dynamix System Temp plugin but not Perl. I didn't realize the "detect" on the plugin required Perl as I thought it was only required for sensors-detect. Thanks!

I'm still struggling with getting temps setup on my Intel S2600CP board. I can't download the latest version of sensors-detect because lm-sensors.org is down. Any other suggestions?

So when I run the sensors cmd, all I get is this: Tower login: root Linux 4.1.18-unRAID. root@Tower:~# sensors i350bb-pci-0700 Adapter: PCI adapter loc1: +55.0°C (high = +120.0°C, crit = +110.0°C) root@Tower:~#

Yeah, I'm working on getting the CPU temps setup. Very pleased with the Natex combo. I still have a lot to figure out. My transfer speeds are still capping around 40-50 MB/sec (previously 30-35). Not sure what else I need to tweak though?!

Thanks bobkart and Drider for the info. I finally got my new server up and running so I'll be checking the temps to decide if I need active cooling.

Haha, yeah 128GB. Thanks for the info. I'm really hoping there might be an easier solution but I'll keep this in the back pocket.

So I've been asking a lot of questions lately in the Good Deals section and thought it might be better to start a new build thread since I know others are in a similar situation. With my upgrade to UnRAID v6, I realized my current server is underpowered for my current (and future) needs. I'm currently using Sonarr, SabNZBd, Emby Media Server and Deluge for dockers. I quickly discovered that 2GB of RAM is barely enough to run all the dockers at the same time and forget about transcoding any of my content to other devices. I also want to create a Win10 VM and eliminate my desktop PC. Anyway, I jumped on the recent E5-2670 bandwagon and purchased a motherboard/cpu/ram combo from Natex. Here's my equipment list thus far: Case: Lian Li PC-P80 (confirmed SSI-EEB MB fits my removable MB mounting plate with some small tweaks), 3 140mm intake fans and 2 exhaust (1 rear and 1 top) Drive Cages: 4x 3in4 Lian LI EX-H34 PSU: EVGA 850W Supernova P2 Platinum MB/CPU/RAM: Intel S2600CP LGA 1100 with dual Xeon E5-2670's and 128GB RAM Controllers: Dual Intel RS2WC080 flashed to IT Drives: 14 total now, 2TB-4TB combination of Seagate, Toshiba and HGST The motherboard combo from Natex comes with two passive copper heatsinks. Given the relatively low investment for the MB/CPU/RAM, I thought it might be prudent to upgrade these to active cooling. I am considering 2x Noctua NH U9DX I4 CPU Heatsink and Cooling Fans. Being new to IPMI, I think I'll be able to monitor temps actively with my new configuration to see if additional CPU cooling is necessary (guessing it will be but thought as long as I don't get too hot it would be worth checking before I invest in the Noctua's). I'm also wondering about the orientation of the CPU fans (i.e. intake from bottom and exhaust upwards or intake from front of case and exhaust to rear)? The latter scenario has me wondering if I'll just be pulling hot air from CPU1 into CPU2 given their close proximity? Here's a layout of my case configuration: http://www.lian-li.com/en/dt_portfolio/armorsuit-pc-p80/ Any other suggestions on plugins/dockers that might help me monitor the status of the server would be appreciated. Currently, I haven't found a way to get CPU temp info on my Asus P5Q Premium board so I'm hoping this will be resolved with the new board/bios/IPMI configuration?

So I'm having an issue trying to flash my RS2WC080 to IT FW. I thought I saw an error after executing the 3.bat command but not positive. Anyway, when I tried to execute 5IT.bat, I got an error saying chip was in reset state mode (is this from 3.bat?). Not sure how to proceed? Should I try to execute 3.bat again? C:\LSIMEGA\SAS2FLSH.EXE -l Flashlog.txt -o -f 2118it.bin -b mptsas2.rom Advanced Mode Set Adapter Selected is a LSI SAS: SAS2008(B2) Executing Operation: Flash Firmware Image Firmware Image has a Valid Checksum. Firmware Image compatible with Controller. Valid NVDATA Image found. NVDATA Device ID and Chip Revision match verified. Valid Initialization Image verified. Valid BootLoader Image verified. Chip is in RESET state. Attempting Host Boot... ERROR: Firmware Host Boot Failed ! Due to error remaining commands will not be executed. Unable to Process Commands. Exiting SAS2Flash. Edit: Ok, so for some reason I needed to reboot between steps 2 and 3 as well as 3 and 5. Both cards flashed without any further issues. Thanks for the step by step guide!