LumberJackGeek

dataserver2-diagnostics-20200107-0338.zip I left for a few hours to get dinner and drinks, and now it's moved, it's at 67.1% now, I'll keep an eye on it. Logs are attached, maybe it was just a fluke. And yes I was refreshing the the web page when I was doing my checks

Ok so I am in the middle of swapping out my cache drive, and I started doing it as if it was a drive in my array before I realized it didn't work the same and I found this article: https://wiki.unraid.net/index.php/Replace_A_Cache_Drive So here is what I did: Shutdown the unRAID server, installed new SSD, left old one in there still connected. Booted up, stopped the array, unassigned the old cache drive, and assigned the new one, started the array back up (including dockers and VMs). At this point I tried clicking the button to invoke the mover and nothing really happened and that's when I realized I was doing something wrong. Found the above article, stopped the array again, set all my shares to Cache: Yes that were using the Cached drive and started the array and invoked the mover and it started moving stuff, however... I was keeping track of how this was progressing so I could get a rate of how quickly stuff was moved off the cache drive, and it stopped moving at 88.7%, should I be concerned? 88.7% - 6:26 PM 88.7% - 6:15 PM 88.8% - 5:12 PM 89.8% - 4:51 PM 90.4% - 4:41 PM 90.8% - 4:31 PM

Never mind, I accidentally turned off the "External Access" instead of the Enhanced logging *face palm*

So I am troubleshooting an issue with a specific tracker, so I enabled the "Enhanced" logging via the WebUI, zipped the files, turned the logging off and restarted the docker, and now I can't navigate to the docker via the web. Now when I check the logs, it says this: Now listening on: http://127.0.0.1:9117 However, prior to enabled/disabling the "Enhanced" logging it used to say this: Now listening on: http://[::]:9117 When i try navigating to the IP address every other docker is running on, I get this: Hmmm… can't reach this page 192.168.86.143 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED Hey did you fix your IPTorrents issue? It recently stopped working for me as well. I think it's the site's DDoS protection...

That fixed it, thanks!

Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2019-10-25 17:13:00.590669 [info] System information Linux bfa57bcbfb29 4.19.56-Unraid #1 SMP Thu Jun 27 13:13:13 BST 2019 x86_64 GNU/Linux 2019-10-25 17:13:00.890171 [info] PUID defined as '99' 2019-10-25 17:13:01.153779 [info] PGID defined as '100' 2019-10-25 17:13:02.653070 [info] UMASK defined as '000' 2019-10-25 17:13:02.704820 [info] Permissions already set for volume mappings 2019-10-25 17:13:02.814684 [info] DELUGE_DAEMON_LOG_LEVEL defined as 'info' 2019-10-25 17:13:02.849781 [info] DELUGE_WEB_LOG_LEVEL defined as 'info' 2019-10-25 17:13:02.886115 [info] VPN_ENABLED defined as 'yes' 2019-10-25 17:13:03.258954 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us4027.nordvpn.com.tcp443.ovpn 2019-10-25 17:13:03.258954 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/us4027.nordvpn.com.tcp443.ovpn 2019-10-25 17:13:03.374224 [info] VPN remote line defined as 'remote 207.189.2.238 443' 2019-10-25 17:13:03.409641 [info] VPN_REMOTE defined as '207.189.2.238' 2019-10-25 17:13:03.445171 [info] VPN_PORT defined as '443' 2019-10-25 17:13:03.483212 [info] VPN_PROTOCOL defined as 'tcp-client' 2019-10-25 17:13:03.517472 [info] VPN_DEVICE_TYPE defined as 'tun0' 2019-10-25 17:13:03.551377 [info] VPN_PROV defined as 'custom' 2019-10-25 17:13:03.585993 [info] LAN_NETWORK defined as '192.168.86.0/24' 2019-10-25 17:13:03.620365 [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' 2019-10-25 17:13:03.656347 [info] VPN_USER defined as 'redacted' 2019-10-25 17:13:03.690964 [info] VPN_PASS defined as 'redacted' 2019-10-25 17:13:03.726825 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2019-10-25 17:13:03.763026 [info] ENABLE_PRIVOXY defined as 'yes' 2019-10-25 17:13:03.798628 [info] Starting Supervisor... 2019-10-25 17:13:05,380 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2019-10-25 17:13:05,380 INFO Set uid to user 0 succeeded 2019-10-25 17:13:05,383 INFO supervisord started with pid 6 2019-10-25 17:13:05,380 INFO Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2019-10-25 17:13:05,380 INFO Set uid to user 0 succeeded 2019-10-25 17:13:05,383 INFO supervisord started with pid 6 2019-10-25 17:13:06,386 INFO spawned: 'start-script' with pid 151 2019-10-25 17:13:06,387 INFO spawned: 'watchdog-script' with pid 152 2019-10-25 17:13:06,388 INFO reaped unknown pid 7 2019-10-25 17:13:06,423 DEBG 'watchdog-script' stdout output: [info] Deluge config file doesn't exist, copying default... 2019-10-25 17:13:06,423 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-10-25 17:13:06,423 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2019-10-25 17:13:06,424 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2019-10-25 17:13:06,431 DEBG 'start-script' stdout output: [warn] Username contains characters which could cause authentication issues, please consider changing this if possible 2019-10-25 17:13:06,434 DEBG 'start-script' stdout output: [warn] Password contains characters which could cause authentication issues, please consider changing this if possible 2019-10-25 17:13:06,576 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2019-10-25 17:13:06,580 DEBG 'start-script' stdout output: [info] Adding 209.222.18.222 to /etc/resolv.conf 2019-10-25 17:13:06,583 DEBG 'start-script' stdout output: [info] Adding 84.200.69.80 to /etc/resolv.conf 2019-10-25 17:13:06,586 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2019-10-25 17:13:06,589 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2019-10-25 17:13:06,593 DEBG 'start-script' stdout output: [info] Adding 209.222.18.218 to /etc/resolv.conf 2019-10-25 17:13:06,596 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2019-10-25 17:13:06,599 DEBG 'start-script' stdout output: [info] Adding 84.200.70.40 to /etc/resolv.conf 2019-10-25 17:13:06,602 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2019-10-25 17:13:06,604 DEBG 'start-script' stdout output: 207.189.2.238 2019-10-25 17:13:06,661 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2019-10-25 17:13:06,664 DEBG 'start-script' stdout output: [info] Adding 192.168.86.0/24 as route via docker eth0 2019-10-25 17:13:06,665 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2019-10-25 17:13:06,666 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.2 192.168.86.0/24 via 172.17.0.1 dev eth0 2019-10-25 17:13:06,667 DEBG 'start-script' stdout output: -------------------- 2019-10-25 17:13:06,670 DEBG 'start-script' stdout output: iptable_mangle 16384 4 ip_tables 24576 9 iptable_filter,iptable_nat,iptable_mangle 2019-10-25 17:13:06,670 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2019-10-25 17:13:06,828 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2019-10-25 17:13:06,830 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 443 -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.86.0/24 -i eth0 -p tcp -m tcp --dport 58846 -j ACCEPT -A INPUT -s 192.168.86.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 443 -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.86.0/24 -o eth0 -p tcp -m tcp --sport 58846 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 192.168.86.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 2019-10-25 17:13:06,830 DEBG 'start-script' stdout output: -------------------- 2019-10-25 17:13:06,846 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2019-10-25 17:13:07,134 DEBG 'start-script' stdout output: Fri Oct 25 17:13:07 2019 WARNING: file 'credentials.conf' is group or others accessible Fri Oct 25 17:13:07 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Fri Oct 25 17:13:07 2019 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10 2019-10-25 17:13:07,134 DEBG 'start-script' stdout output: [info] OpenVPN started 2019-10-25 17:13:07,135 DEBG 'start-script' stdout output: Fri Oct 25 17:13:07 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit Fri Oct 25 17:13:07 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Fri Oct 25 17:13:07 2019 NOTE: --fast-io is disabled since we are not using UDP 2019-10-25 17:13:07,135 DEBG 'start-script' stdout output: Fri Oct 25 17:13:07 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Fri Oct 25 17:13:07 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2019-10-25 17:13:07,135 DEBG 'start-script' stdout output: Fri Oct 25 17:13:07 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.238:443 Fri Oct 25 17:13:07 2019 Socket Buffers: R=[87380->87380] S=[65536->65536] Fri Oct 25 17:13:07 2019 Attempting to establish TCP connection with [AF_INET]207.189.2.238:443 [nonblock] 2019-10-25 17:15:07,146 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 TCP: connect to [AF_INET]207.189.2.238:443 failed: Connection timed out Fri Oct 25 17:15:07 2019 SIGHUP[connection failed(soft),init_instance] received, process restarting 2019-10-25 17:15:07,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 WARNING: file 'credentials.conf' is group or others accessible Fri Oct 25 17:15:07 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Fri Oct 25 17:15:07 2019 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10 2019-10-25 17:15:07,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 Restart pause, 5 second(s) 2019-10-25 17:15:07,146 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 TCP: connect to [AF_INET]207.189.2.238:443 failed: Connection timed out Fri Oct 25 17:15:07 2019 SIGHUP[connection failed(soft),init_instance] received, process restarting 2019-10-25 17:15:07,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 WARNING: file 'credentials.conf' is group or others accessible Fri Oct 25 17:15:07 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Fri Oct 25 17:15:07 2019 library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.10 2019-10-25 17:15:07,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:07 2019 Restart pause, 5 second(s) 2019-10-25 17:15:12,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit Fri Oct 25 17:15:12 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Fri Oct 25 17:15:12 2019 NOTE: --fast-io is disabled since we are not using UDP 2019-10-25 17:15:12,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Fri Oct 25 17:15:12 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2019-10-25 17:15:12,148 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.238:443 Fri Oct 25 17:15:12 2019 Socket Buffers: R=[87380->87380] S=[65536->65536] Fri Oct 25 17:15:12 2019 Attempting to establish TCP connection with [AF_INET]207.189.2.238:443 [nonblock] 2019-10-25 17:15:12,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 WARNING: --ping should normally be used with --ping-restart or --ping-exit Fri Oct 25 17:15:12 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Fri Oct 25 17:15:12 2019 NOTE: --fast-io is disabled since we are not using UDP 2019-10-25 17:15:12,147 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication Fri Oct 25 17:15:12 2019 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication 2019-10-25 17:15:12,148 DEBG 'start-script' stdout output: Fri Oct 25 17:15:12 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]207.189.2.238:443 Fri Oct 25 17:15:12 2019 Socket Buffers: R=[87380->87380] S=[65536->65536] Fri Oct 25 17:15:12 2019 Attempting to establish TCP connection with [AF_INET]207.189.2.238:443 [nonblock] Hey all of a sudden my client keeps getting stuck at "Attempting to establish TCP connection" after updating to the latest bits. Ideas?

Well here's the problem, this has only happened once so I don't have a repro of this issue. If I update now and it never happens again, I have no idea if the update fixed it, or if it was something else that was just once in a million to repro. It'd be nice if more folks could look over these logs that have more familiarity with unRAIDs code and give input. But thank you for your help thus far! I really do appreciate it, John.

Someone trying to log in from externally shouldn't stop the system from being shutdown. This is clearly a bug.

I've already had to pull the plug to get this to restart, but does no one have any idea what caused this?

I am using NordVPN. The majority of my torrents show up, but a handful are not showing up in their tracker. I am not using port forwarding since NordVPN doesn't work with it.

Binhex you rock This docker works much better than it did on Windows performance wise. I am developing an issue where some of my torrents are not showing up as being seeded by my private tracker and they are pointing to my client as being the issue since no one else is hitting this. I was planning on asking for help on the Deluge forums, but wanted to know if I need to do anything special to obtain logs with it being a docker and such? Thanks in advance!

dataserver2-diagnostics-20191007-1820.zip Logs attached

So I clicked on "Update All" under my dockers, and it hung trying to shutdown one of them, Netdata. So I tried opening a new webUI window and could no longer see any of my dockers. All of them are not responding. I tried using the WebUI to restart, didn't work. As in the machine won't reboot. I get a 504 error after some time. Tried restarting from the commandline, and it just hangs here and doesn't actually restart: root@Dataserver2:~# /sbin/reboot Broadcast message from root@Dataserver2 (pts/1) (Mon Oct 7 13:19:45 2019): The system is going down for reboot NOW! Are the machines finally taking over?

That worked, thank you! Not sure where that old value came from...

Hi everyone, Thanks for the work on this! However I realized I am currently stuck on a very old build, what do I need to do to update? Version 3.0.0.348 Mono Version 5.18.0.240

Hey every one, I get this every time I try converting DVD files: Failed to execute external program 'ccextractor' from location 'usr/bin/mmccextr' Ideas?

@binhex, thanks for all your help on everything! Is it possible to get the extractor add-in for this?

@jonp when users are posting log after log, and no one is replying with any actual update, not even "We still don't see the problems in these logs...", it gets a little frustrating. This is a product that folks here paid for, and blaming people's hardware/setup with 0 evidence is a little hard to swallow when rolling back a build fixes it. Adding a cache drive also fixes it. Do you all still need more logs or not?

Hey is it possible to get the Extractor add-in working for this? if so, how?

Just used a Windows VM with Powershell to do what I needed

I was able to remedy this by using a cache drive, try it out and see if it works for you! Mine was also corrupting before I could get a daily backup.

What approach would you recommend?

I was just trying to do it on the OS itself. Is that wrong?

I am trying to rename files using "rename", but I guess I want the "perl version" of rename that does regex. To do this, I was trying to use cpan to install it, however cpan throws a YAML error, and so based on what I was reading I will need to install "make" which I am told I need to install "build-essential". This is what's supposed to work for Ubunutu, but it's probably different for unRAID: sudo apt-get install build-essential Ideas?

@limetech any news on this?