m1ll3rt1m3

Absolutely loving these containers! I used to host mc servers on pufferpanel but this is so much better and easier. Not sure if you take requests but would love to see a container for FTB One.

Here are the logs from today. I have made several attempts since this morning so this should be everything involved. [Fri Dec 25 07:06:33.256182 2015] [mpm_prefork:notice] [pid 73] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.16. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 07:26:44.829615 2015] [:notice] [pid 9624] FastCGI: process manager initialized (pid 9624) [Fri Dec 25 07:26:44.854913 2015] [mpm_prefork:notice] [pid 9623] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 07:26:44.855302 2015] [core:notice] [pid 9623] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 07:30:18.056901 2015] [mpm_prefork:notice] [pid 9623] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.17. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 07:30:28.297599 2015] [:notice] [pid 77] FastCGI: process manager initialized (pid 77) [Fri Dec 25 07:30:28.325521 2015] [mpm_prefork:notice] [pid 72] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 07:30:28.325742 2015] [core:notice] [pid 72] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 08:02:46.877503 2015] [mpm_prefork:notice] [pid 72] AH00169: caught SIGTERM, shutting down [Fri Dec 25 08:02:47.906380 2015] [:notice] [pid 182] FastCGI: process manager initialized (pid 182) [Fri Dec 25 08:02:47.977489 2015] [mpm_prefork:notice] [pid 179] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 08:02:47.977710 2015] [core:notice] [pid 179] AH00094: Command line: '/usr/sbin/apache2' [Fri Dec 25 08:02:48.669340 2015] [mpm_prefork:notice] [pid 179] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.17. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 08:02:49.727242 2015] [:notice] [pid 223] FastCGI: process manager initialized (pid 223) [Fri Dec 25 08:02:49.765997 2015] [mpm_prefork:notice] [pid 222] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 08:02:49.766239 2015] [core:notice] [pid 222] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 08:11:51.715671 2015] [mpm_prefork:notice] [pid 222] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.18. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 08:48:48.901231 2015] [:notice] [pid 6631] FastCGI: process manager initialized (pid 6631) [Fri Dec 25 08:48:48.930577 2015] [mpm_prefork:notice] [pid 6630] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 08:48:48.930967 2015] [core:notice] [pid 6630] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 08:48:59.583948 2015] [mpm_prefork:notice] [pid 6630] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.19. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 08:49:09.746374 2015] [:notice] [pid 77] FastCGI: process manager initialized (pid 77) [Fri Dec 25 08:49:09.776339 2015] [mpm_prefork:notice] [pid 72] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 08:49:09.776626 2015] [core:notice] [pid 72] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 10:24:46.768869 2015] [mpm_prefork:notice] [pid 72] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.20. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 10:35:49.053935 2015] [:notice] [pid 77] FastCGI: process manager initialized (pid 77) [Fri Dec 25 10:35:49.080646 2015] [mpm_prefork:notice] [pid 72] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 10:35:49.080894 2015] [core:notice] [pid 72] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND' [Fri Dec 25 12:45:05.535052 2015] [mpm_prefork:notice] [pid 72] AH00169: caught SIGTERM, shutting down AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.22. Set the 'ServerName' directive globally to suppress this message [Fri Dec 25 13:20:10.562323 2015] [:notice] [pid 75] FastCGI: process manager initialized (pid 75) [Fri Dec 25 13:20:10.618927 2015] [mpm_prefork:notice] [pid 71] AH00163: Apache/2.4.7 (Ubuntu) mod_fastcgi/mod_fastcgi-SNAP-0910052141 PHP/5.5.9-1ubuntu4.14 OpenSSL/1.0.1f configured -- resuming normal operations [Fri Dec 25 13:20:10.619205 2015] [core:notice] [pid 71] AH00094: Command line: '/usr/sbin/apache2 -D FOREGROUND'

Possibly, but the cache drive hasn't been used in awhile. So ignored most notifications about it. Had no idea the cache drive would bring down everything else with it.

So I am trying to put pretty much everything through this proxy, and for the most part it's working. The problem comes into play when I try to proxy plex with it's own subdomain. A friend of mine is using apache with a very similar config. <VirtualHost *:80> ServerName example.com ServerAlias www.example.com DocumentRoot /config/www <Directory /config/www/> AllowOverride All </Directory> Redirect permanent / https://example.com/ </VirtualHost> exit <VirtualHost *:443> ServerName example.com ServerAlias www.example.com ServerAdmin webmaster@localhost DocumentRoot /config/www <Directory /config/www/> AllowOverride All </Directory> SSLCertificateFile /config/keys/root/ssl.crt SSLCertificateKeyFile /config/keys/root/decrypted.cert.key SSLCertificateChainFile /config/keys/root/sub.class1.server.ca.pem SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH SSLProtocol All -SSLv2 -SSLv3 SSLHonorCipherOrder On SSLSessionTickets Off Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload" Header always set X-Frame-Options DENY Header always set X-Content-Type-Options nosniff SSLCompression off SSLUseStapling on SSLEngine on SSLProxyEngine On RewriteEngine On ProxyPreserveHost On <Location /couchpotato> ProxyPass http://192.168.0.245:5050/couchpotato ProxyPassReverse http://192.168.0.245:5050/couchpotato </Location> <Location /sonarr> ProxyPass http://192.168.0.245:8989/sonarr ProxyPassReverse http://192.168.0.245:8989/sonarr </Location> <Location /nzbget> ProxyPass http://192.168.0.245:6789/nzbget ProxyPassReverse http://192.168.0.245:6789/nzbget </Location> <Location /headphones> ProxyPass http://192.168.0.245:8181/headphones ProxyPassReverse http://192.168.0.245:8181/headphones </Location> <Location /plexpy> ProxyPass http://192.168.0.245:8180/plexpy ProxyPassReverse http://192.168.0.245:8180/plexpy </Location> <Location /requests> ProxyPass http://192.168.0.245:3000/requests ProxyPassReverse http://192.168.0.245:3000/requests </Location> <Location /deluge/> RequestHeader append X-Deluge-Base "/deluge" ProxyPass http://192.168.0.245:8112/ ProxyPassReverse http://192.168.0.245:8112/ </Location> <Location /guacamole/> Order allow,deny Allow from all ProxyPass http://192.168.0.245:9050/guacamole/ flushpackets=on ProxyPassReverse http://192.168.0.245:9050/guacamole/ </Location> </VirtualHost> <VirtualHost *:443> ServerName plex.example.com ServerAlias example.com ServerAdmin webmaster@localhost DocumentRoot /config/www <Directory /config/www/> AllowOverride All </Directory> SSLCertificateFile /config/keys/plex/plex.ssl.crt SSLCertificateKeyFile /config/keys/plex/decyrpted.plex.ssl.key SSLCertificateChainFile /config/keys/plex/root.crt SSLCipherSuite EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH SSLProtocol All -SSLv2 -SSLv3 SSLHonorCipherOrder On SSLSessionTickets Off Header always set Strict-Transport-Security "max-age=63072000; includeSubdomains; preload" Header always set X-Frame-Options DENY Header always set X-Content-Type-Options nosniff SSLCompression off SSLUseStapling on SSLEngine on SSLProxyEngine On RewriteEngine On ProxyPreserveHost On <Location /> AuthType Basic AuthName "Restricted area" AuthUserFile /config/www/.htpasswd Require valid-user </Location> <Proxy *> Order deny,allow Allow from all </Proxy> ProxyRequests Off ProxyPass / http://192.168.0.245:32400/ ProxyPassReverse / http://192.168.0.245:32400/ RewriteEngine on RewriteCond %{REQUEST_URI} !^/web RewriteCond %{HTTP:X-Plex-Device} ^$ RewriteRule ^/$ /web/$1 [R,L] </VirtualHost> If I remove the plex.example.com virtual host it works fine. As soon as it gets added apache fails across the board.

Thanks, that worked perfectly. I feel like an idiot for overlooking it but thanks again.

So just pull the stop the array and pull the cache drive?

Here it is. mediasvr-diagnostics-20151224-1928.zip

So I made a bonehead move the other day and accidentally pulled the wrong cord while removing a faulty power cable, and unplugged my server. When it came back online all my shares were missing from the GUI, and not able to be accessed through the network. My docker containers, however, are still working as though the shares are present. A "ls -l" of /mnt/user returns "Stale NFS file handle" I have spent the last few days searching through the forums for any kind information, I have cleanly rebooted the system several times and let it complete 2 separate parity checks. Any thoughts on how I could recover my shares to fully operational would be appreciated.

Anyone have any thoughts on this? Disregard folks. I pulled the trigger and got a year with PIA, notified my tracker admins, and setup Sonarr. Once I figure out what is keeping CouchPotato from seeing deluge I will be 100%.

Anyone have any thoughts on this?

I understand that "du" results are lengthy, but couldn't one just pipe them to a text file in a mounted share " du > /mnt/user/SHARE/du_results.txt"?

Someone correct me if I am wrong since I am pretty new with linux and virtualization, but is isn't /dev/loop0 show the utilization of the OS storage. In this docker. Could this be showing that the allocated space for docker or at least this specific container is full? cd /var/lib/docker du should show you the files utilizing the space in loop0

So I have a vps server overseas running OpenVPN for me on the cheap. I would like to get delugevpn setup to connect to it. I have added the .ovpn file to /config/openvpn/ and my settings are: VPN_Enabled = "yes" VPN_USER = "vpn username" VPN_PASS = "vpn password" VPN_REMOTE = "" VPN_PORT = "1194" VPN_PROV = "custom" ENABLE_PROXY = "no" LAN_RANGE = "192.168.0.1-192.168.0.254" . When I check the logs I see: 2015-08-03 20:19:32,574 CRIT Set uid to user 0 2015-08-03 20:19:32,630 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2015-08-03 20:19:32,801 INFO supervisord started with pid 1 2015-08-03 20:19:33,803 INFO spawned: 'deluge' with pid 8 2015-08-03 20:19:33,805 INFO spawned: 'setip' with pid 9 2015-08-03 20:19:33,807 INFO spawned: 'start' with pid 10 2015-08-03 20:19:33,809 INFO spawned: 'webui' with pid 11 2015-08-03 20:19:33,815 INFO spawned: 'privoxy' with pid 14 2015-08-03 20:19:33,816 INFO spawned: 'setport' with pid 15 2015-08-03 20:19:33,817 DEBG 'deluge' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2015-08-03 20:19:33,817 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-03 20:19:33,817 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-03 20:19:33,818 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-03 20:19:33,818 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-03 20:19:33,822 DEBG 'start' stdout output: [info] VPN is enabled, beginning configuration of OpenVPN 2015-08-03 20:19:33,825 DEBG 'privoxy' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2015-08-03 20:19:34,344 DEBG 'start' stdout output: [info] VPN provider defined as custom 2015-08-03 20:19:35,179 DEBG 'start' stdout output: [info] ip routing table 2015-08-03 20:19:35,179 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-08-03 20:19:35,179 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-08-03 20:19:35,180 DEBG 'start' stdout output: default via 172.17.42.1 dev eth0 2015-08-03 20:19:35,180 DEBG 'start' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.11 -------------------- 2015-08-03 20:19:36,157 DEBG 'start' stdout output: [info] iptables 2015-08-03 20:19:36,159 DEBG 'start' 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 -m iprange --src-range 192.168.0.1-192.168.0.254 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 1194 -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 -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 -m iprange --dst-range 192.168.0.1-192.168.0.254 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 1194 -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 -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 2015-08-03 20:19:36,159 DEBG 'start' stdout output: -------------------- [info] nameservers 2015-08-03 20:19:36,161 DEBG 'start' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2015-08-03 20:19:36,161 DEBG 'start' stdout output: -------------------- [info] Starting OpenVPN... 2015-08-03 20:19:36,896 DEBG 'start' stdout output: Options error: --keepalive conflicts with --ping, --ping-exit, or --ping-restart. If you use --keepalive, you don't need any of the other --ping directives. 2015-08-03 20:19:36,896 DEBG 'start' stdout output: Use --help for more information. 2015-08-03 20:19:36,898 DEBG fd 15 closed, stopped monitoring (stdout)> 2015-08-03 20:19:36,898 DEBG fd 19 closed, stopped monitoring (stderr)> 2015-08-03 20:19:36,898 INFO exited: start (exit status 1; not expected) 2015-08-03 20:19:36,898 DEBG received SIGCLD indicating a child quit If I change VPN_ENABLED to "no" I can access the WebUI and everything seems all happy fun time, but when I try to actually secure myself just a wee bit, everything goes to shit for me. Any thoughts? Does the "custom" option not really do what I think it does? Am I skipping over something so completely obvious that I deserve bad things to happen to m nether regions? All help will be appreciated.