inkubux

Hi Thanks again for your docker, I've observed a high CPU usage when using it though between 50% to 100% when downloading. When not downloading it goes back to about 4% to 8% Is anybody having this issue ? Thanks

Thanks it actually resolved my issues. I deleted the config files, and recreated the container and now it works flawlessly. It's amazing how fast it is compared to deluge on the VPN :), almost double for me. Thanks

Thanks for your great docker. I do have some issues with the webui. I'm able to see the webui but I have RCP errors, here is a screenshot I also attached a log 2017-05-14 16:17:46.590326 [info] Starting Supervisor... 2017-05-14 16:17:47,878 CRIT Set uid to user 0 2017-05-14 16:17:47,879 INFO Included extra file "/etc/supervisor/conf.d/rtorrent.conf" during parsing 2017-05-14 16:17:47,886 INFO supervisord started with pid 7 2017-05-14 16:17:48,896 INFO spawned: 'flood-script' with pid 119 2017-05-14 16:17:48,900 INFO spawned: 'start-script' with pid 120 2017-05-14 16:17:48,903 INFO spawned: 'rtorrent-script' with pid 121 2017-05-14 16:17:48,906 INFO spawned: 'rutorrent-script' with pid 122 2017-05-14 16:17:48,910 INFO spawned: 'privoxy-script' with pid 123 2017-05-14 16:17:48,922 DEBG 'flood-script' stdout output: [info] Flood not enabled, skipping starting Flood Web UI 2017-05-14 16:17:48,923 INFO success: flood-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-05-14 16:17:48,923 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-05-14 16:17:48,923 INFO success: rtorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-05-14 16:17:48,924 INFO success: rutorrent-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-05-14 16:17:48,925 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-05-14 16:17:48,926 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47988725084960 for <Subprocess at 47988723550760 with name flood-script in state RUNNING> (stderr)> 2017-05-14 16:17:48,934 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47988725087552 for <Subprocess at 47988723550760 with name flood-script in state RUNNING> (stdout)> 2017-05-14 16:17:48,935 INFO exited: flood-script (exit status 0; expected) 2017-05-14 16:17:48,935 DEBG received SIGCLD indicating a child quit 2017-05-14 16:17:48,936 DEBG 'rtorrent-script' stdout output: [info] rTorrent config file already exists, skipping copy 2017-05-14 16:17:48,938 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-05-14 16:17:48,941 DEBG 'rtorrent-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-05-14 16:17:48,945 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-05-14 16:17:48,946 DEBG fd 31 closed, stopped monitoring <POutputDispatcher at 47988725014040 for <Subprocess at 47988723551696 with name privoxy-script in state RUNNING> (stderr)> 2017-05-14 16:17:48,946 DEBG fd 27 closed, stopped monitoring <POutputDispatcher at 47988644563640 for <Subprocess at 47988723551696 with name privoxy-script in state RUNNING> (stdout)> 2017-05-14 16:17:48,946 INFO exited: privoxy-script (exit status 0; expected) 2017-05-14 16:17:48,947 DEBG received SIGCLD indicating a child quit 2017-05-14 16:17:48,983 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-05-14 16:17:49,007 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-05-14 16:17:49,021 DEBG 'start-script' stderr output: dos2unix: 2017-05-14 16:17:49,022 DEBG 'start-script' stderr output: converting file /config/openvpn/openvpn.ovpn to Unix format... 2017-05-14 16:17:49,168 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-05-14 16:17:49,179 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2017-05-14 16:17:49,187 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2017-05-14 16:17:49,196 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2017-05-14 16:17:49,205 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2017-05-14 16:17:49,225 DEBG 'start-script' stdout output: [info] Adding 192.168.2.0/24 as route via docker eth0 2017-05-14 16:17:49,227 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-05-14 16:17:49,229 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 2017-05-14 16:17:49,230 DEBG 'start-script' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7 192.168.2.0/24 via 172.17.0.1 dev eth0 2017-05-14 16:17:49,231 DEBG 'start-script' stdout output: -------------------- 2017-05-14 16:17:49,280 DEBG 'start-script' stdout output: [warn] 'iptable_mangle' kernel module not available, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN [info] unRAID users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle' [info] Ubuntu users: Please attempt to load the module by executing the following on your host:- '/sbin/modprobe iptable_mangle' 2017-05-14 16:17:49,280 DEBG 'start-script' stdout output: [info] Synology users: Please attempt to load the module by executing the following on your host:- 'insmod /lib/modules/iptable_mangle.ko' 2017-05-14 16:17:49,332 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2017-05-14 16:17:49,650 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-05-14 16:17:49,655 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A INPUT -s 192.168.2.0/24 -i eth0 -p tcp -m tcp --dport 5000 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 9443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 9443 -j ACCEPT -A OUTPUT -d 192.168.2.0/24 -o eth0 -p tcp -m tcp --sport 5000 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2017-05-14 16:17:49,657 DEBG 'start-script' stdout output: -------------------- [info] Starting OpenVPN... 2017-05-14 16:17:49,935 DEBG 'start-script' stdout output: [info] OpenVPN started 2017-05-14 16:17:51,810 DEBG 'rtorrent-script' stdout output: [info] rTorrent not running [info] rTorrent listening interface IP 0.0.0.0 and VPN provider IP 10.39.10.6 different, marking for reconfigure 2017-05-14 16:17:58,087 DEBG 'rtorrent-script' stdout output: [info] Removing any rtorrent session lock files left over from the previous run... 2017-05-14 16:17:58,091 DEBG 'rtorrent-script' stdout output: [info] Attempting to start rTorrent... 2017-05-14 16:17:58,095 DEBG 'rtorrent-script' stdout output: Script started, file is /home/nobody/typescript 2017-05-14 16:17:58,143 DEBG 'rtorrent-script' stdout output: Script done, file is /home/nobody/typescript 2017-05-14 16:17:58,292 DEBG 'rutorrent-script' stdout output: [info] rtorrent started, setting up rutorrent... [info] Setting PHP timezone to UTC... 2017-05-14 16:17:58,324 DEBG 'rutorrent-script' stdout output: [info] nginx cert files already exists, skipping copy 2017-05-14 16:17:58,327 DEBG 'rutorrent-script' stdout output: [info] nginx security file already exists, skipping copy [info] nginx config file already exists, skipping copy 2017-05-14 16:17:58,331 DEBG 'rutorrent-script' stdout output: [info] rutorrent conf folder already exists, skipping copy 2017-05-14 16:17:58,337 DEBG 'rutorrent-script' stdout output: [info] rutorrent share folder already exists, skipping copy 2017-05-14 16:17:58,343 DEBG 'rutorrent-script' stdout output: [info] copying rutorrent plugins to container... 2017-05-14 16:17:58,376 DEBG 'rutorrent-script' stdout output: [info] starting php-fpm... 2017-05-14 16:17:58,429 DEBG 'rutorrent-script' stderr output: [NOTICE] [pool www] 'user' directive is ignored when FPM is not running as root [NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root 2017-05-14 16:17:58,441 DEBG 'rutorrent-script' stdout output: [info] starting nginx... 2017-05-14 16:17:59,172 DEBG 'rtorrent-script' stdout output: [info] rTorrent started 2017-05-14 16:17:59,173 DEBG 'rtorrent-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)... 2017-05-14 16:17:59,183 DEBG 'rtorrent-script' stdout output: [info] rTorrent running [info] Initialising ruTorrent plugins (checking nginx is running)... 2017-05-14 16:17:59,194 DEBG 'rtorrent-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins... 2017-05-14 16:17:59,287 DEBG 'rtorrent-script' stdout output: [info] ruTorrent plugins initialised 2017-05-14 16:18:03,775 DEBG 'rutorrent-script' stderr output: 2017/05/14 16:18:03 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/" 2017-05-14 16:18:32,126 DEBG 'rutorrent-script' stderr output: 2017/05/14 16:18:32 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/" 2017-05-14 16:18:46,122 DEBG 'rutorrent-script' stderr output: 2017/05/14 16:18:46 [error] 919#919: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.2.32, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.2.29:9080", referrer: "http://192.168.2.29:9080/" Thanks for your help. In the meantime I will use deluge, but I fint it a bit slow.

I may sound stupid but I see no help link in your sig :(. I'm having issues with connecting to the web gui once the container is started :(.

Finally I decided to "Trust my array" Parity is rebuilding and my data seems fine.

Ok thanks I ran it on the md device in maintenance mode, but I still get the grey icon. What do you think I should do next ? Thanks a lot i'm quite lost at the moment. Because If I mount /dev/md1 I can access the data and everything, so my disk seems fine

I'm running Unraid 6 Beta15 I'm quite new to unraid and after changing case My dashboard showed me that my main data disk was invalid. I wen to the command line and ran: xfs_repair -n /dev/sda Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... [and it goes forever] I'm just wondering if this is a fixable corruption ? My parity is still valid and my apps seems to work. (I suppose this is normal) How would I proceed to fix this corruption If It's not fixable can I reformat the drive and rebuild from the parity ? And How would I do it Bare with me i'm not an unraid or an xfs expert I uploaded a screenshot of the grey Icon Thanks for your help

For me i'm on a 50/50 with the the openvpn docker I can get about 2.1 to 2.5 MB seconds (which is almost exactly half of the speed) with the proxy I max out a 6 MB. So yes there is a difference, but this udp bug keeps me for using regularly. It's probably related to deluge and not the docker image.

I have the same issue with binhex docker, no UDP with PIA proxy It does work with start and stop, but i'm afraid that this stop start is just an IP leak between the tracker and the client.

Thanks I did ran a Smart test and they are fine, but I was not aware of preclearing unfortunately now all my data is on the disk it's kind of to late to do it. I decided to swap the drive and put the "biggest" one as parity. Parity is building at the moment My next drive will be an internal one, and if it reports bigger than the other I will swap the parity with it. Thanks for your help.

I booted HDAT2 but SET_MAX was not supported for this drive. I guess I will have to transfer all my data to this drive and use the other one for the parity. And do the same If I ever buy another one. I cleared the DCO but it did not help. My best option would be to buy another drive, but I don't have the money yet to do so .

Looks like i'm out of luck, this HDAT2 is a CD which I don't have on my server. I don't have a windows machine . My main computer is an iMac i can't put the drive in it . I will try it with ultimatebootcd which includes HDAT2 and there is some linux instruction on how to put it on a usb key The error that hdparm is giving me inout/output, is it because my drive is "frozen". ?

Thanks I will try with HDAT2 CD. Does SetMax on that CD will erease my Data ?

as a side note here is the last syslog Apr 29 22:13:26 Tower emhttp: shcmd (3846): rmmod md-mod |& logger Apr 29 22:13:26 Tower kernel: md: unRAID driver removed Apr 29 22:13:26 Tower emhttp: Unregistered Apr 29 22:13:26 Tower emhttp: array slots: 24 Apr 29 22:13:26 Tower emhttp: cache slots: 1 Apr 29 22:13:26 Tower emhttp: Device inventory: Apr 29 22:13:26 Tower emhttp: shcmd (3847): udevadm settle Apr 29 22:13:26 Tower emhttp: TOSHIBA_DT01ABA300_8448RSTGS (sda) 2930266584 Apr 29 22:13:26 Tower emhttp: WDC_WD5000BPKX-75HPJT0_WD-WX71AC381691 (sdb) 488386584 Apr 29 22:13:26 Tower emhttp: WDC_WD30EZRX-00SPEB0_WD-WCC4E0512628 (sdc) 2930233816 Apr 29 22:13:26 Tower emhttp: shcmd (3848): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Apr 29 22:13:26 Tower kernel: md: unRAID driver 2.5.0 installed Apr 29 22:13:26 Tower kernel: mdcmd (1): import 0 8,32 2930233768 WDC_WD30EZRX-00SPEB0_WD-WCC4E0512628 Apr 29 22:13:26 Tower kernel: md: import disk0: [8,32] (sdc) WDC_WD30EZRX-00SPEB0_WD-WCC4E0512628 size: 2930233768 Apr 29 22:13:26 Tower kernel: md: disk0 replaced Apr 29 22:13:26 Tower kernel: mdcmd (2): import 1 8,0 2930266532 TOSHIBA_DT01ABA300_8448RSTGS Apr 29 22:13:26 Tower kernel: md: import disk1: [8,0] (sda) TOSHIBA_DT01ABA300_8448RSTGS size: 2930266532 Apr 29 22:13:26 Tower kernel: mdcmd (3): import 2 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (4): import 3 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (5): import 4 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (6): import 5 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (7): import 6 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (: import 7 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (9): import 8 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (10): import 9 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (11): import 10 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (12): import 11 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (13): import 12 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (14): import 13 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (15): import 14 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (16): import 15 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (17): import 16 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (18): import 17 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (19): import 18 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (20): import 19 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (21): import 20 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (22): import 21 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (23): import 22 0,0 Apr 29 22:13:26 Tower kernel: mdcmd (24): import 23 0,0 Apr 29 22:13:26 Tower emhttp: import 24 cache device: sdb Apr 29 22:13:26 Tower emhttp: import flash device: sdd Apr 29 22:13:29 Tower emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1 I can see from the syslog that the drives are not the same size.

I'm new to unRaid so bare with me if my questions don't make sense. I had an old system with 2 3TB usb hard drive that I removed from their case. I created an new unRaid system and, I have put one as disk1 with unRaid. Copied all the data from the other one and started the array Now I wanted to add the second one as parity but I have the error "Disk in parity slot is not biggest." They are both 3TB I've read that it could be an HPA issue but when I run the following command: hdparm -N /dev/sdc (which is the drive I want parity on) I have the following error: /dev/sdc: READ_NATIVE_MAX_ADDRESS_EXT failed: Input/output error Any help would be appreciated My mother board is : http://www.asrock.com/mb/Intel/Q1900DC-ITX/?cat=Specifications My Drive one with the data on it is: ata-TOSHIBA_DT01ABA300_8448RSTGS 3TB (Toshiba DT01ABA300) My Drive 2 the one I want to set as parity is: ata-WDC_WD30EZRX-00SPEB0_WD-WCC4E0512628 3TB (WD Green) Is there any reason why the WD would be smaller and gives error to hdparm ? Could this be because they come from usb enclosures ? Is my only chance flipping the drives so the toshiba is the bigger one for parity ? Thanks for your help p.s. sorry for my bad english.