wrckid

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by wrckid

  1. Hi guys, I upgraded my old server to a new more powerful system. I can launch the GUI no problem and I can see the torrents going in, however I do not show anything for the downstream at all so in other words they are not downloaded, they just remain at 0% complete. I basically copied the same configuration from my old server to this new one, and configured the app in the same manner, I am pretty sure I am missing something and this is driving me nuts. Thank you for your assistance. Below is a copy of my supervisord.log file. 2021-02-11 13:07:58,669 WARN received SIGTERM indicating exit request 2021-02-11 13:07:58,670 DEBG killing watchdog-script (pid 173) with signal SIGTERM 2021-02-11 13:07:58,670 INFO waiting for start-script, watchdog-script to die 2021-02-11 13:07:59,672 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22516988188368 for <Subprocess at 22516988680560 with name watchdog-script in state STOPPING> (stdout)> 2021-02-11 13:07:59,673 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22516988421072 for <Subprocess at 22516988680560 with name watchdog-script in state STOPPING> (stderr)> 2021-02-11 13:07:59,673 INFO stopped: watchdog-script (terminated by SIGTERM) 2021-02-11 13:07:59,674 DEBG received SIGCHLD indicating a child quit 2021-02-11 13:07:59,674 DEBG killing start-script (pid 172) with signal SIGTERM 2021-02-11 13:08:00,677 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22516992268800 for <Subprocess at 22516992270048 with name start-script in state STOPPING> (stdout)> 2021-02-11 13:08:00,677 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22516988680320 for <Subprocess at 22516992270048 with name start-script in state STOPPING> (stderr)> 2021-02-11 13:08:00,678 INFO stopped: start-script (terminated by SIGTERM) 2021-02-11 13:08:00,678 DEBG received SIGCHLD indicating a child quit Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2021-02-11 13:08:05.930701 [info] System information Linux baa72b9179f1 4.19.107-Unraid #1 SMP Thu Mar 5 13:55:57 PST 2020 x86_64 GNU/Linux 2021-02-11 13:08:06.029220 [info] OS_ARCH defined as 'x86-64' 2021-02-11 13:08:06.124638 [info] PUID defined as '99' 2021-02-11 13:08:06.227618 [info] PGID defined as '100' 2021-02-11 13:08:06.553188 [info] UMASK defined as '000' 2021-02-11 13:08:06.646008 [info] Permissions already set for volume mappings 2021-02-11 13:08:06.741813 [info] Deleting files in /tmp (non recursive)... 2021-02-11 13:08:06.850162 [info] VPN_ENABLED defined as 'yes' 2021-02-11 13:08:06.946528 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn' 2021-02-11 13:08:07.040324 [info] VPN_PROV defined as 'pia' 2021-02-11 13:08:07.347029 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us_silicon_valley.ovpn 2021-02-11 13:08:07.540677 [info] VPN remote server(s) defined as 'us-siliconvalley.privacy.network,' 2021-02-11 13:08:07.634127 [info] VPN remote port(s) defined as '1198,' 2021-02-11 13:08:07.674777 [info] VPN remote protcol(s) defined as 'udp,' 2021-02-11 13:08:07.700048 [info] VPN_DEVICE_TYPE defined as 'tun0' 2021-02-11 13:08:07.723696 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2021-02-11 13:08:07.744882 [info] LAN_NETWORK defined as '192.168.1.0/24' 2021-02-11 13:08:07.766216 [info] NAME_SERVERS defined as '209.222.18.222,84.200.69.80,37.235.1.174,1.1.1.1,209.222.18.218,37.235.1.177,84.200.70.40,1.0.0.1' 2021-02-11 13:08:07.788342 [info] VPN_USER defined as 'XXXXXXXXX' 2021-02-11 13:08:07.810862 [info] VPN_PASS defined as 'XXXXXXXXX' 2021-02-11 13:08:07.832124 [info] STRICT_PORT_FORWARD defined as 'no' 2021-02-11 13:08:07.853123 [info] ENABLE_PRIVOXY defined as 'yes' 2021-02-11 13:08:07.874059 [info] ADDITIONAL_PORTS not defined (via -e ADDITIONAL_PORTS), skipping allow for custom incoming ports 2021-02-11 13:08:07.895478 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2021-02-11 13:08:07.917093 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2021-02-11 13:08:07.937554 [info] Starting Supervisor... 2021-02-11 13:08:08,066 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2021-02-11 13:08:08,067 INFO Set uid to user 0 succeeded 2021-02-11 13:08:08,068 INFO supervisord started with pid 6 2021-02-11 13:08:09,072 INFO spawned: 'start-script' with pid 172 2021-02-11 13:08:09,076 INFO spawned: 'watchdog-script' with pid 173 2021-02-11 13:08:09,077 INFO reaped unknown pid 7 (exit status 0) 2021-02-11 13:08:09,094 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2021-02-11 13:08:09,095 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-02-11 13:08:09,096 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2021-02-11 13:08:09,308 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2021-02-11 13:08:09,318 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2021-02-11 13:08:09,329 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2021-02-11 13:08:09,339 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2021-02-11 13:08:09,350 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2021-02-11 13:08:09,360 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2021-02-11 13:08:09,371 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2021-02-11 13:08:09,381 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2021-02-11 13:08:09,482 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2021-02-11 13:08:09,525 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2021-02-11 13:08:09,537 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2021-02-11 13:08:09,541 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2021-02-11 13:08:09,544 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.5 192.168.1.0/24 via 172.17.0.1 dev eth0 2021-02-11 13:08:09,544 DEBG 'start-script' stdout output: -------------------- 2021-02-11 13:08:09,553 DEBG 'start-script' stdout output: iptable_mangle 16384 2 ip_tables 24576 5 iptable_filter,iptable_nat,iptable_mangle 2021-02-11 13:08:09,554 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2021-02-11 13:08:09,725 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2021-02-11 13:08:09,729 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -s 192.168.1.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8112 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8112 -j ACCEPT -A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.1.0/24 -o eth0 -p tcp -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT 2021-02-11 13:08:09,732 DEBG 'start-script' stdout output: -------------------- 2021-02-11 13:08:09,735 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2021-02-11 13:08:09,755 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. 2021-02-11 13:08:09,756 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 WARNING: file 'credentials.conf' is group or others accessible 2021-02-11 13:08:09,757 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 OpenVPN 2.5.0 [git:makepkg/a73072d8f780e888+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Nov 6 2020 2021-02-11 13:08:09 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10 2021-02-11 13:08:09,757 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2021-02-11 13:08:09,759 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL----- ****REMOVED ON PURPOSE**** -----END X509 CRL----- 2021-02-11 13:08:09,760 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 TCP/UDP: Preserving recently used remote address: [AF_INET]154.21.212.61:1198 2021-02-11 13:08:09 UDP link local: (not bound) 2021-02-11 13:08:09 UDP link remote: [AF_INET]154.21.212.61:1198 2021-02-11 13:08:09,869 DEBG 'start-script' stdout output: 2021-02-11 13:08:09 [siliconvalley402] Peer Connection Initiated with [AF_INET]154.21.212.61:1198 2021-02-11 13:08:10,920 DEBG 'start-script' stdout output: 2021-02-11 13:08:10 TUN/TAP device tun0 opened 2021-02-11 13:08:10 net_iface_mtu_set: mtu 1500 for tun0 2021-02-11 13:08:10 net_iface_up: set tun0 up 2021-02-11 13:08:10,920 DEBG 'start-script' stdout output: 2021-02-11 13:08:10 net_addr_v4_add: 10.10.112.101/24 dev tun0 2021-02-11 13:08:10 /root/openvpnup.sh tun0 1500 1553 10.10.112.101 255.255.255.0 init 2021-02-11 13:08:10,926 DEBG 'start-script' stdout output: 2021-02-11 13:08:10 Initialization Sequence Completed 2021-02-11 13:08:13,061 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2021-02-11 13:08:13,415 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 154.21.212.61 2021-02-11 13:08:13,419 DEBG 'start-script' stdout output: [info] Port forwarding is not enabled 2021-02-11 13:08:14,246 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.10.112.101 different, marking for reconfigure 2021-02-11 13:08:14,258 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2021-02-11 13:08:14,270 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2021-02-11 13:08:14,281 DEBG 'watchdog-script' stdout output: [info] Privoxy not running 2021-02-11 13:08:14,282 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2021-02-11 13:08:14,682 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.9.112.67' [info] Deluge key 'listen_interface' will have a new value '10.10.112.101' [info] Writing changes to Deluge config file '/config/core.conf'... 2021-02-11 13:08:14,943 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'tun0' [info] Deluge key 'outgoing_interface' will have a new value 'tun0' [info] Writing changes to Deluge config file '/config/core.conf'... 2021-02-11 13:08:15,074 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of '10b19b4b5cab422684e9256359d90e57' [info] Deluge key 'default_daemon' will have a new value '10b19b4b5cab422684e9256359d90e57' [info] Writing changes to Deluge config file '/config/web.conf'... 2021-02-11 13:08:15,309 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2021-02-11 13:08:15,521 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2021-02-11 13:08:17,233 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2021-02-11 13:08:19,340 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (6890, 6890) Configuration value successfully updated. 2021-02-11 13:08:21,610 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2021-02-11 13:08:21,611 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2021-02-11 13:08:21,611 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2021-02-11 13:08:21,615 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-02-11 13:08:22,631 DEBG 'watchdog-script' stdout output: [info] Privoxy process started [info] Waiting for Privoxy process to start listening on port 8118... 2021-02-11 13:08:22,646 DEBG 'watchdog-script' stdout output: [info] Privoxy process listening on port 8118
  2. I recently upgraded my server to newer hardware and I am going through the rebuild process, I re-installed my Docker Apps and when I attempt to start the DelugeVPN app, the container fails to start, and just remains as "stopped" Digging deeper I see this on the log file... 2019-12-15 13:54:34.057325 [info] System information Linux 131ebefdafcc 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux 2019-12-15 13:54:34.152775 [info] PUID defined as '99' 2019-12-15 13:54:34.256328 [info] PGID defined as '100' 2019-12-15 13:54:34.588442 [info] UMASK defined as '000' 2019-12-15 13:54:34.689946 [info] Permissions already set for volume mappings 2019-12-15 13:54:34.798754 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2019-12-15 13:54:34.893517 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2019-12-15 13:54:34.986419 [info] VPN_ENABLED defined as 'yes' 2019-12-15 13:54:35.104633 [crit] No OpenVPN config file located in /config/openvpn/ (ovpn extension), please download from your VPN provider and then restart this container, exiting... Not sure, if this is my issue or part of the issue but I also don't see why I need to add an OpenVPN config file, if I am using PIA. Anyone else have this problem?
  3. Thank you! My Parity drive is 1TB, I was intending on converting the Parity to a 2TB drive and using the 1TB and add it as an additional member of the array.
  4. Excellent! Thank you that helps out a lot, also one more question. If I add more drives other drives (of different sizes) would UNRAID throw a fit? I purchased a license 3 years ago to do just this, I just never done it since I had no room to expand. Again, thank you for answering my question.
  5. Hello, Let's start this with the standard, I am a bit of a novice when it comes to UNRAID so by no means am I an expert. I have been an UNRAID user since 2011 and have been running it on an HP NL36 Micro server, this little guy has been running like a trooper and without any major issues, in January I replaced a faulty PSU and this system has since been running flawlessly. About 5 months ago I purchased a Proliant ML10 server with a Xeon e3 1241 processor, to use as my ESXi Host for my home lab. Needless to say I have had lots of issues with my ESX host and had to rebuild it a few times, I have finally come to the realization that perhaps it is time to upgrade my NL36 server to the Proliant box. So here are my questions, - I am going to do the upgrade, my real concern is my data from the Micro server to the new server. If I physically take the drives out from one server to another, does the new hardware recognize the drives and data? It can't be that simple can it? - Since I have not had the horsepower to run VM's on my micro server I am not familiar how the VM environment of the OS would be. I am sure several people here are running this setup, would you mind briefly answering, whether it runs great or there is some work to get it to run. - My setup would mainly be used to run media applications, such as Plex, Airsonic, DelugeVPN, as well as HomeAssistant (So far this is what I run in my server) - For those of you who have done this in the past what was your solution from transferring your data to your new hardware or drives? With the new system, I purchased additional storage to run near-line in my ESX host I intend to run those drives but as I mentioned before if it's as easy as moving drives from one server to another then I might not do that simply because I do not want to loose all of my data. Thank you for you looking and thank you for your assistance! Cheers!
  6. Hi, I am running the same server and have been since 2012. Earlier this year, my PSU died as well and ended up replacing it with a refurbished one. It's been running great ever since, but the AMD Athlon II is not up to snuff for running VM's and now I am torn about replacing this little bogger that's been running strong for a long time. Are you by chance still running your Micro server? And how does it perform with running VM's on it.