DarkKnight

For the second week in a row, the vast majority of my containers that are set to update late Sunday night using this plugin are just missing entirely on Monday morning. What steps can I take to track down why this is happening?

Can we please get some fixes to the VM GUI to support more of the various QEMU/KVM options that are available? Just moved over some VMs from ESXi, and it was a pain to get the XML straight. KVM apparently can handle VMDK's natively, but the GUI doesn't support it, so I had to find some examples online and get it sorted out. The docker GUI is really nice. The VM GUI feels like an afterthought in comparison. Would be nice if it could get the same kind of attention.

Yeah, that was it. I made some changes to my firewall, and it's pretty sensitive about port 443. Swapped to another port in ovpn conf and it worked immediately. Really impressed you spotted that with so little info. Thanks man.

Updated the container, and when I restarted it, QB isn't running any more. Can't tell from the log what's wrong. After the initial startup, this just loops endlessly every couple minutes. 2018-12-29 12:05:14,449 DEBG 'start-script' stdout output: Sat Dec 29 12:05:14 2018 [UNDEF] Inactivity timeout (--ping-restart), restarting 2018-12-29 12:05:14,450 DEBG 'start-script' stdout output: Sat Dec 29 12:05:14 2018 SIGHUP[soft,ping-restart] received, process restarting 2018-12-29 12:05:14,450 DEBG 'start-script' stdout output: Sat Dec 29 12:05:14 2018 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sat Dec 29 12:05:14 2018 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 2018-12-29 12:05:14,451 DEBG 'start-script' stdout output: Sat Dec 29 12:05:14 2018 WARNING: file 'credentials.conf' is group or others accessible Sat Dec 29 12:05:14 2018 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018 Sat Dec 29 12:05:14 2018 library versions: OpenSSL 1.1.1a 20 Nov 2018, LZO 2.10 Sat Dec 29 12:05:14 2018 Restart pause, 5 second(s) 2018-12-29 12:05:19,451 DEBG 'start-script' stdout output: Sat Dec 29 12:05:19 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2018-12-29 12:05:19,452 DEBG 'start-script' stdout output: Sat Dec 29 12:05:19 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xxx:443 Sat Dec 29 12:05:19 2018 Socket Buffers: R=[212992->212992] S=[212992->212992] Sat Dec 29 12:05:19 2018 UDP link local: (not bound) Sat Dec 29 12:05:19 2018 UDP link remote: [AF_INET]xxx.xxx.xxx.xxx:443

I have dual parity. My concern was the warning message that data corruption could get worse due to using -L in the repair. If this is not the case in this instance, than I have nothing to worry about. I'm running a non-corrective parity check. I also noticed that after 18 consecutive months of error free checks, I got 394 errors on my last monthly check. No new smart warnings, but I did have to shut unraid off a couple times in the past month while I was doing work on my servers. I suppose I could have had an unclean shutdown then. In terms of backups of *really* important data like photos, I do have those on multiple machines. I don't have an off-site backup configured for older photos, but it's on the list. B2 looking pretty cheap for that. Newer photos are covered by iCloud. I have a few TB in project files for old VHS home movies that I'd be pretty pissed to lose, but uncompressed they are like 30GB/hr and I have something like 100-200hrs of footage, though not all of it has been digitized yet. I can't imagine what my ISP would do if I tried to pass 10+TB of upload in a month over top of my already high usage to cover backing up that plus my existing irreproducible data. Would raise a red flag I don't want. Besides, I don't wan't the monthly sub. Would make more sense to me to get a 10-14TB drive, back it up locally and store that off-site. Just not in the budget. 😒

md4 & md15 both had log errors. Edit: I believe it was related to an unclean shutdown due to too short of a default timer on the disks. I set it to 7 min per the recommendation today.

I was down two disks. I did not want to take the chance of a problem occurring during rebuild that would lose all of that data. I don't have 4TB of space available outside the array for backup of the emulated contents either.

The server is at about 30/50TBs. used. There's no other backup. Unraid is capable of emulating the disks when they are missing using parity, provided enough other disks are available. If it can do that, why can't we choose to have the data corrected rather than the parity?

I turned off my unraid server via the GUI a couple times this week, and when restarting it yesterday it came back up with two unmountable disks with 'Corruption warning: Metadata has LSN (1:83814) ahead of current LSN (1:80338).' I restarted the array in maintenance mode and ran xfs_repair -v for both devices which indicated -L was needed. I reran it with -L and the output looked good: Phase 1 - find and verify superblock... - block cache size set to 2292464 entries Phase 2 - using internal log - zero log... zero_log: head block 451270 tail block 451266 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:452526) is ahead of log (1:2). Format log to cycle 4. XFS_REPAIR Summary Sat Dec 8 08:49:37 2018 Phase Start End Duration Phase 1: 12/08 08:44:23 12/08 08:44:23 Phase 2: 12/08 08:44:23 12/08 08:45:44 1 minute, 21 seconds Phase 3: 12/08 08:45:44 12/08 08:45:45 1 second Phase 4: 12/08 08:45:45 12/08 08:45:45 Phase 5: 12/08 08:45:45 12/08 08:45:45 Phase 6: 12/08 08:45:45 12/08 08:45:45 Phase 7: 12/08 08:45:45 12/08 08:45:45 Total run time: 1 minute, 22 seconds done xfs_repair -v -L /dev/md15 Phase 1 - find and verify superblock... - block cache size set to 2292464 entries Phase 2 - using internal log - zero log... zero_log: head block 80338 tail block 80334 ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:83814) is ahead of log (1:2). Format log to cycle 4. XFS_REPAIR Summary Sat Dec 8 08:50:28 2018 Phase Start End Duration Phase 1: 12/08 08:45:19 12/08 08:45:19 Phase 2: 12/08 08:45:19 12/08 08:47:15 1 minute, 56 seconds Phase 3: 12/08 08:47:15 12/08 08:47:15 Phase 4: 12/08 08:47:15 12/08 08:47:15 Phase 5: 12/08 08:47:15 12/08 08:47:15 Phase 6: 12/08 08:47:15 12/08 08:47:15 Phase 7: 12/08 08:47:15 12/08 08:47:15 Total run time: 1 minute, 56 seconds done I restarted the array and it detected the disks normally and everything 'looks' okay. Now I need to run a consistency check, but I'd like the check to consider the parity authoritative rather than the data disks in case there are differences. How can I do this? diagnostics-20181208-0926.zip

NP. I can appreciate that. Thanks for doing the tedious work.

I was checking the config files in the appdata directory. Privoxy's config file is like 2000 lines. I honestly had no idea where the setting you were referencing was. I don't work with this stuff every day.

You can find the qBitorrent.conf file with the user/pass in appdata/binhex-qbittorrentvpn/qBittorrent/config Solved the issue. Must have missed the LAN_Network setting in the docker template. I didn't realize that is where that setting was. In your Q3 question/answer, you should use 'Docker Template' so it's painfully obvious where the setting is.

I don't think I'm experiencing these issues; /data was definitely populated on my install. VPN connects fine, and Privoxy starts, but having issues connecting to it. Are you sure you have the right docker?

Thanks for developing this container. I'm trying to use Privoxy, but constantly getting "Proxy is not responding" messages when testing it with Chrome. Log Below: Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2018-11-13 21:48:00.699660 [info] System information Linux 27cb18cb1c3d 4.18.17-unRAID #1 SMP Sun Nov 4 08:16:44 PST 2018 x86_64 GNU/Linux 2018-11-13 21:48:00.749849 [info] PUID defined as '99' 2018-11-13 21:48:00.929923 [info] PGID defined as '100' 2018-11-13 21:48:01.172380 [info] UMASK defined as '000' 2018-11-13 21:48:01.218015 [info] Permissions already set for volume mappings 2018-11-13 21:48:01.268454 [info] VPN_ENABLED defined as 'yes' 2018-11-13 21:48:01.326128 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/XXXXX-XXXXXXXXXXXXX.ovpn dos2unix: converting file /config/openvpn/XXXXX-XXXXXXXXXXXXX.ovpn to Unix format... 2018-11-13 21:48:01.400947 [info] VPN remote line defined as 'remote xxxxxxxxxxx.com 443' 2018-11-13 21:48:01.444842 [info] VPN_REMOTE defined as 'xxxxxxxxxxx.com' 2018-11-13 21:48:01.489940 [info] VPN_PORT defined as '443' 2018-11-13 21:48:01.545786 [info] VPN_PROTOCOL defined as 'udp' 2018-11-13 21:48:01.592086 [info] VPN_DEVICE_TYPE defined as 'tun0' 2018-11-13 21:48:01.640001 [info] VPN_PROV defined as 'custom' 2018-11-13 21:48:01.687777 [info] LAN_NETWORK defined as '192.168.1.0/24' 2018-11-13 21:48:01.734800 [info] NAME_SERVERS defined as '8.8.4.4' 2018-11-13 21:48:01.782309 [info] VPN_USER defined as 'XXXXXXXXXXX' 2018-11-13 21:48:01.828605 [info] VPN_PASS defined as 'XXXXXXXXXXX' 2018-11-13 21:48:01.876373 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2018-11-13 21:48:01.924109 [info] ENABLE_PRIVOXY defined as 'yes' 2018-11-13 21:48:01.972317 [info] WEBUI_PORT defined as '8089' 2018-11-13 21:48:02.024303 [info] Starting Supervisor... 2018-11-13 21:48:02,574 INFO Included extra file "/etc/supervisor/conf.d/qbittorrent.conf" during parsing 2018-11-13 21:48:02,574 INFO Set uid to user 0 succeeded 2018-11-13 21:48:02,579 INFO supervisord started with pid 8 2018-11-13 21:48:03,582 INFO spawned: 'start-script' with pid 143 2018-11-13 21:48:03,585 INFO spawned: 'watchdog-script' with pid 144 2018-11-13 21:48:03,587 INFO spawned: 'privoxy-script' with pid 145 2018-11-13 21:48:03,587 INFO reaped unknown pid 9 2018-11-13 21:48:03,596 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2018-11-13 21:48:03,597 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-11-13 21:48:03,597 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-11-13 21:48:03,597 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2018-11-13 21:48:03,598 DEBG 'watchdog-script' stdout output: [info] qBittorrent config file already exists, skipping copy [info] Removing session lock file (if it exists)... 2018-11-13 21:48:03,602 DEBG 'watchdog-script' stderr output: dos2unix: 2018-11-13 21:48:03,603 DEBG 'watchdog-script' stderr output: converting file /config/qBittorrent/config/qBittorrent.conf to Unix format... 2018-11-13 21:48:03,613 DEBG 'start-script' stdout output: [warn] Password contains characters which could cause authentication issues, please consider changing this if possible 2018-11-13 21:48:03,713 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2018-11-13 21:48:03,720 DEBG 'start-script' stdout output: [info] Adding XXXXXXXXXX to /etc/resolv.conf 2018-11-13 21:48:03,725 DEBG 'start-script' stdout output: [info] Adding XXXXXXXXXXXXX to /etc/resolv.conf 2018-11-13 21:48:03,730 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2018-11-13 21:48:03,735 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2018-11-13 21:48:03,740 DEBG 'start-script' stdout output: [info] Adding XXXXXXXXXXXXX to /etc/resolv.conf 2018-11-13 21:48:03,745 DEBG 'start-script' stdout output: [info] Adding XXXXXXXXXXXX to /etc/resolv.conf 2018-11-13 21:48:03,750 DEBG 'start-script' stdout output: [info] Adding 1.0.0.1 to /etc/resolv.conf 2018-11-13 21:48:03,756 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2018-11-13 21:48:04,067 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2018-11-13 21:48:04,068 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2018-11-13 21:48:04,070 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.9 192.168.1.0/24 via 172.17.0.1 dev eth0 2018-11-13 21:48:04,070 DEBG 'start-script' stdout output: -------------------- 2018-11-13 21:48:04,076 DEBG 'start-script' stdout output: iptable_mangle 16384 1 ip_tables 24576 3 iptable_filter,iptable_nat,iptable_mangle 2018-11-13 21:48:04,077 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2018-11-13 21:48:04,108 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2018-11-13 21:48:04,215 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2018-11-13 21:48:04,219 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 443 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8089 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8089 -j ACCEPT -A INPUT -s 192.168.1.0/24 -i eth0 -p tcp -m tcp --dport 8089 -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 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 443 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8089 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8089 -j ACCEPT -A OUTPUT -d 192.168.1.0/24 -o eth0 -p tcp -m tcp --sport 8089 -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 2018-11-13 21:48:04,219 DEBG 'start-script' stdout output: -------------------- 2018-11-13 21:48:04,220 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2018-11-13 21:48:04,253 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 Tue Nov 13 21:48:04 2018 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6 2018-11-13 21:48:04,254 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 WARNING: file 'credentials.conf' is group or others accessible Tue Nov 13 21:48:04 2018 OpenVPN 2.4.6 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Apr 24 2018 Tue Nov 13 21:48:04 2018 library versions: OpenSSL 1.1.1 11 Sep 2018, LZO 2.10 2018-11-13 21:48:04,255 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts [info] OpenVPN started 2018-11-13 21:48:04,256 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]xx.xx.xx.50:443 Tue Nov 13 21:48:04 2018 Socket Buffers: R=[212992->212992] S=[212992->212992] Tue Nov 13 21:48:04 2018 UDP link local: (not bound) Tue Nov 13 21:48:04 2018 UDP link remote: [AF_INET]xx.xx.xx.50:443 2018-11-13 21:48:04,263 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 TLS: Initial packet from [AF_INET]xx.xx.xx.50:443, sid=a6d0612f f3f8f70c 2018-11-13 21:48:04,282 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 VERIFY OK: depth=1, C=US, ST=FL, L=Location, O=XXXXX, OU=XXXXX VPN, CN=XXXXX CA, [email protected] 2018-11-13 21:48:04,283 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 VERIFY X509NAME OK: C=US, ST=FL, L=Location, O=XXXXX, OU=XXXXX VPN, CN=xxxxxxxxxxx.com, [email protected] Tue Nov 13 21:48:04 2018 VERIFY OK: depth=0, C=US, ST=FL, L=Location, O=XXXXX, OU=XXXXX VPN, CN=xxxxxxxxxxx.com, [email protected] 2018-11-13 21:48:04,335 DEBG 'start-script' stdout output: Tue Nov 13 21:48:04 2018 Control Channel: TLSv1.2, cipher SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Tue Nov 13 21:48:04 2018 [xxxxxxxxxxx.com] Peer Connection Initiated with [AF_INET]xx.xx.xx.50:443 2018-11-13 21:48:05,360 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 SENT CONTROL [xxxxxxxxxxx.com]: 'PUSH_REQUEST' (status=1) 2018-11-13 21:48:05,368 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS XXXXXXX,dhcp-option DNS XXXXXXXXXXX,rcvbuf 493216,sndbuf 493216,explicit-exit-notify 5,comp-lzo no,route-gateway xx.xx.xx.1,topology subnet,ping 20,ping-restart 40,ifconfig xx.xx.xx.55 255.255.254.0,peer-id 9,cipher AES-256-GCM' 2018-11-13 21:48:05,369 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: timers and/or timeouts modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: explicit notify parm(s) modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: compression parms modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: --sndbuf/--rcvbuf options modified Tue Nov 13 21:48:05 2018 Socket Buffers: R=[212992->986432] S=[212992->986432] Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: --ifconfig/up options modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: route options modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: route-related options modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: peer-id set Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: adjusting link_mtu to 1625 Tue Nov 13 21:48:05 2018 OPTIONS IMPORT: data channel crypto options modified Tue Nov 13 21:48:05 2018 Data Channel: using negotiated cipher 'AES-256-GCM' Tue Nov 13 21:48:05 2018 NCP: overriding user-set keysize with default Tue Nov 13 21:48:05 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Tue Nov 13 21:48:05 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Tue Nov 13 21:48:05 2018 ROUTE_GATEWAY 172.17.0.1/255.255.0.0 IFACE=eth0 HWADDR=XXXXXXXXXXXXXXX Tue Nov 13 21:48:05 2018 TUN/TAP device tun0 opened Tue Nov 13 21:48:05 2018 TUN/TAP TX queue length set to 100 Tue Nov 13 21:48:05 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 2018-11-13 21:48:05,370 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /usr/bin/ip link set dev tun0 up mtu 1500 2018-11-13 21:48:05,371 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /usr/bin/ip addr add dev tun0 xx.xx.xx.55/23 broadcast XXXXXXXXXX 2018-11-13 21:48:05,373 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /root/openvpnup.sh tun0 1500 1553 xx.xx.xx.55 255.255.254.0 init 2018-11-13 21:48:05,377 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /usr/bin/ip route add xx.xx.xx.50/32 via 172.17.0.1 2018-11-13 21:48:05,379 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /usr/bin/ip route add 0.0.0.0/1 via xx.xx.xx.1 2018-11-13 21:48:05,381 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 /usr/bin/ip route add 128.0.0.0/1 via xx.xx.xx.1 2018-11-13 21:48:05,382 DEBG 'start-script' stdout output: Tue Nov 13 21:48:05 2018 Initialization Sequence Completed 2018-11-13 21:48:05,471 DEBG 'privoxy-script' stdout output: [info] Configuring Privoxy... 2018-11-13 21:48:05,475 DEBG 'watchdog-script' stdout output: [info] qBittorrent listening interface IP 0.0.0.0 and VPN provider IP xx.xx.xx.55 different, marking for reconfigure 2018-11-13 21:48:05,481 DEBG 'watchdog-script' stdout output: [info] qBittorrent not running 2018-11-13 21:48:05,548 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address xx.xx.xx.50 2018-11-13 21:48:05,584 DEBG 'watchdog-script' stdout output: [info] Removing session lock file (if it exists)... 2018-11-13 21:48:05,586 DEBG 'watchdog-script' stdout output: [info] Attempting to start qBittorrent... 2018-11-13 21:48:05,655 DEBG 'watchdog-script' stdout output: [info] qBittorrent process started [info] Waiting for qBittorrent process to start listening on port 8089... 2018-11-13 21:48:07,183 DEBG 'privoxy-script' stdout output: [info] All checks complete, starting Privoxy... 2018-11-13 21:48:07,185 DEBG 'privoxy-script' stderr output: 2018-11-13 21:48:07.185 152fa106b100 Info: Privoxy version 3.0.26 2018-11-13 21:48:07.185 152fa106b100 Info: Program name: /usr/bin/privoxy 2018-11-13 21:48:35,938 DEBG 'watchdog-script' stdout output: [info] qBittorrent running

I have this in my syslog as well, and I do not have this plugin.

Yeah, after 4 more months of headaches I had enough with CP acting up. I installed radarr last night and am in the process of setting it up. Wonder what happened with ruddburger that after so many years CP is getting abandoned. Looks like he just shifted his time into a different project: https://github.com/ReactTraining/react-router Lots of updates to that over the past few months with relatively nothing into CP. I'd venture a guess that CP is just done at this point.

I think you are going about this the wrong way. All your movies should be in the same folder with the same download handling and you use filters in your media player to display only the kids movies. I'm not sure what you use, but Plex has tagging, multiple user support, and parental controls making it even easier to limit what's available. For me I just set a filter for animation in PHT and that's enough to make it easy to find only the content I'm looking for with kids. That said, there's nothing stopping you from running another docker of radarr. You'll need to use a separate port, download category, and you should use separate working folders for download handling. Just seems cumbersome for what you are trying to do.

The template for radarr is missing a path option for "drone factory" folder. I don't help adding it, just mentioning it was missing.

Can't log anything on their github. Issues have been closed/unavailable for a while. My CP docker has been growing more unstable for a while. Lots of little bugs keep popping up.

Sample userscript: #!/bin/bash echo "Fix /tmp permissions" mkdir -p /tmp/logs/cp mkdir -p /tmp/logs/hp mkdir -p /tmp/logs/plex chown -R 99:100 /tmp/logs/cp chown -R 99:100 /tmp/logs/hp chown -R 99:100 /tmp/logs/plex chmod -R 777 /tmp/logs echo "All Done" This works for me, transcoding and all. You can use a subdirectory /tmp/transcode if you like and chown that if you have problems.

Oh cool. I'm transcoding to RAM already, how are you writing Plex logs to RAM? Use the docker page and map the container log path to a host path within /tmp (e.g. /tmp/logs/plex/) You'll need a userscript to create and chown the log directory within the tmp path so plex can write to it.

Yes. Use the docker page and create a linked path between /tmp (Host) & /transcode (Container). I don't do plex transcodes or log files in any place but RAM. Has worked fine for a long time.

Any of the methods will do the job just fine. If compatibility with other tools is required then MD5 is the safest choice. A simple way to test is to copy a file to your /tmp folder so it stays in RAM memory and do time md5sum /tmp/testfile time b2sum /tmp/testfile time sha256sum /tmp/testfile Thanks. Seems Blake2 is not the fastest method, but I have used it for my entire array. MD5 is about 2x as fast, and SHA256 is about 2x as long. Seems like I should have used MD5. Recommendations?

I've read through a lot of pages at the beginning and end of this thread, and I can't find an relevant answer to my questions. 1) Is there any reason to use one hashing method over another? e.g. Blake2 vs MD5? 2) How can I benchmark my system with the different available methods to determine which is fastest?

I have some SAS drives attached to my array. They are connected through the same SAS controller that my SATA drives are connected to. The SAS drives, while showing up fine, and looking as if everything is okay do not display the drive temps on the dashboard. There is a wealth of SMART data available on these drives, much more so than regular SATA drives. Why isn't something as basic as the Temp showing up?