mr-hexen Posted August 1, 2015 Share Posted August 1, 2015 Hopefully final question on Deluge....everything is working fine. Just one nit. I have my volume mapping as follows: data <--> /mnt/user In my Deluge UI prefs, I have the following: Download to: /data/Torrents/working NOT WORKING, putting downloading torrent in /data Move completed to: /data/Torrents/torrents WORKING FINE Copy of .torrent file to: /data/Torrents/done WORKING FINE Any ideas? I attach screenshots - Thanks! Is the working folder present? Not sure if Deluge will create it if it isn't present and remember Linux is case sensitive. Deluge will create folders that do not exist. Link to comment
TexasDave Posted August 1, 2015 Share Posted August 1, 2015 Deluge has create my torrent storage folder (torrent) and the "done" folder. No issues there... For grins, I did create a "working" folder with the correct permissions. See attached. In my previous post - you can see my deluge prefs which looks right. I am not trying to put the data directly in the /data folder. Instead, I am trying to put it into a folder called Torrents. It is not a big deal as the "done" and .torrent folders work fine. Just wondering....Thanks! Link to comment
JustinChase Posted August 1, 2015 Share Posted August 1, 2015 Starting seemingly randomly a few days ago, I can no longer get into the GUI of a docker with vpn turned on. I've verified the login/password, changed the login/password, changed the port, changed the server (using pia), and various combinations of the port/server. none let me open the docker with vpn turned on. I'd happily provide a log, but I'm not sure where to find the docker specific log, and the syslog seems to have no relevant information about this. 2015-08-01 19:09:10,219::INFO::[sABnzbd:1262] -------------------------------- 2015-08-01 19:09:10,220::INFO::[sABnzbd:1263] SABnzbd.py-0.7.x (rev=unknown) 2015-08-01 19:09:10,220::INFO::[sABnzbd:1275] Platform = posix 2015-08-01 19:09:10,220::INFO::[sABnzbd:1276] Python-version = 2.7.10 (default, May 26 2015, 04:16:29) [GCC 5.1.0] 2015-08-01 19:09:10,220::INFO::[sABnzbd:1277] Arguments = /opt/sabnzbd/SABnzbd.py --config-file /config --server 0.0.0.0:8080 --https 8090 2015-08-01 19:09:10,220::INFO::[sABnzbd:1327] Read INI file /config/sabnzbd.ini 2015-08-01 19:09:10,244::INFO::[__init__:943] Loading data for bookmarks.sab from /config/admin/bookmarks.sab 2015-08-01 19:09:10,244::INFO::[__init__:943] Loading data for rss_data.sab from /config/admin/rss_data.sab 2015-08-01 19:09:10,260::INFO::[__init__:943] Loading data for totals9.sab from /config/admin/totals9.sab 2015-08-01 19:09:10,261::INFO::[postproc:91] Loading postproc queue 2015-08-01 19:09:10,261::INFO::[__init__:943] Loading data for postproc1.sab from /config/admin/postproc1.sab 2015-08-01 19:09:10,261::INFO::[__init__:943] Loading data for queue9.sab from /config/admin/queue9.sab 2015-08-01 19:09:11,463::INFO::[__init__:943] Loading data for watched_data.sab from /config/admin/watched_data.sab 2015-08-01 19:09:11,476::INFO::[__init__:943] Loading data for Rating.sab from /config/admin/Rating.sab 2015-08-01 19:09:11,476::INFO::[__init__:946] /config/admin/Rating.sab missing, trying old cache 2015-08-01 19:09:11,476::INFO::[__init__:949] /config/cache/Rating.sab missing 2015-08-01 19:09:11,477::INFO::[scheduler:172] Setting schedule for midnight BPS reset 2015-08-01 19:09:11,477::INFO::[__init__:335] All processes started 2015-08-01 19:09:11,477::INFO::[sABnzbd:335] Web dir is /opt/sabnzbd/interfaces/Plush 2015-08-01 19:09:11,477::INFO::[sABnzbd:335] Web dir is /opt/sabnzbd/interfaces/Config 2015-08-01 19:09:11,481::INFO::[sABnzbd:464] _yenc module... found! 2015-08-01 19:09:11,481::INFO::[sABnzbd:472] par2 binary... found (/usr/sbin/par2) 2015-08-01 19:09:11,481::INFO::[sABnzbd:480] unrar binary... found (/usr/sbin/unrar) 2015-08-01 19:09:11,481::INFO::[sABnzbd:485] unzip binary... found (/usr/sbin/unzip) 2015-08-01 19:09:11,481::INFO::[sABnzbd:491] nice binary... found (/usr/sbin/nice) 2015-08-01 19:09:11,481::INFO::[sABnzbd:495] ionice binary... found (/usr/sbin/ionice) 2015-08-01 19:09:11,481::INFO::[sABnzbd:500] pyOpenSSL... found (True) 2015-08-01 19:09:11,483::INFO::[sABnzbd:1528] Starting web-interface on 0.0.0.0:8090 2015-08-01 19:09:11,484::INFO::[_cplogging:55] [01/Aug/2015:19:09:11] ENGINE Bus STARTING 2015-08-01 19:09:11,486::INFO::[_cplogging:55] [01/Aug/2015:19:09:11] ENGINE Started monitor thread '_TimeoutMonitor'. 2015-08-01 19:09:11,687::INFO::[_cplogging:55] [01/Aug/2015:19:09:11] ENGINE Serving on 0.0.0.0:8080 2015-08-01 19:09:11,788::INFO::[_cplogging:55] [01/Aug/2015:19:09:11] ENGINE Serving on 0.0.0.0:8090 2015-08-01 19:09:11,789::INFO::[_cplogging:55] [01/Aug/2015:19:09:11] ENGINE Bus STARTED 2015-08-01 19:09:11,789::INFO::[sABnzbd:1597] Starting SABnzbd.py-0.7.x 2015-08-01 19:09:11,790::INFO::[dirscanner:277] Dirscanner starting up 2015-08-01 19:09:11,791::INFO::[urlgrabber:77] URLGrabber starting up 2015-08-01 19:30:04,970::INFO::[sABnzbd:1262] -------------------------------- 2015-08-01 19:30:04,990::INFO::[sABnzbd:1263] SABnzbd.py-0.7.x (rev=unknown) 2015-08-01 19:30:04,990::INFO::[sABnzbd:1275] Platform = posix 2015-08-01 19:30:04,990::INFO::[sABnzbd:1276] Python-version = 2.7.10 (default, May 26 2015, 04:16:29) [GCC 5.1.0] 2015-08-01 19:30:04,990::INFO::[sABnzbd:1277] Arguments = /opt/sabnzbd/SABnzbd.py --config-file /config --server 0.0.0.0:8080 --https 8090 2015-08-01 19:30:04,990::INFO::[sABnzbd:1327] Read INI file /config/sabnzbd.ini 2015-08-01 19:30:04,991::INFO::[__init__:943] Loading data for bookmarks.sab from /config/admin/bookmarks.sab 2015-08-01 19:30:05,007::INFO::[__init__:943] Loading data for rss_data.sab from /config/admin/rss_data.sab 2015-08-01 19:30:05,007::INFO::[__init__:943] Loading data for totals9.sab from /config/admin/totals9.sab 2015-08-01 19:30:05,007::INFO::[postproc:91] Loading postproc queue 2015-08-01 19:30:05,007::INFO::[__init__:943] Loading data for postproc1.sab from /config/admin/postproc1.sab 2015-08-01 19:30:05,008::INFO::[__init__:943] Loading data for queue9.sab from /config/admin/queue9.sab 2015-08-01 19:30:06,254::INFO::[__init__:943] Loading data for watched_data.sab from /config/admin/watched_data.sab 2015-08-01 19:30:06,267::INFO::[__init__:943] Loading data for Rating.sab from /config/admin/Rating.sab 2015-08-01 19:30:06,268::INFO::[__init__:946] /config/admin/Rating.sab missing, trying old cache 2015-08-01 19:30:06,268::INFO::[__init__:949] /config/cache/Rating.sab missing 2015-08-01 19:30:06,268::INFO::[scheduler:172] Setting schedule for midnight BPS reset 2015-08-01 19:30:06,268::INFO::[__init__:335] All processes started 2015-08-01 19:30:06,268::INFO::[sABnzbd:335] Web dir is /opt/sabnzbd/interfaces/Plush 2015-08-01 19:30:06,269::INFO::[sABnzbd:335] Web dir is /opt/sabnzbd/interfaces/Config 2015-08-01 19:30:06,317::INFO::[sABnzbd:464] _yenc module... found! 2015-08-01 19:30:06,317::INFO::[sABnzbd:472] par2 binary... found (/usr/sbin/par2) 2015-08-01 19:30:06,317::INFO::[sABnzbd:480] unrar binary... found (/usr/sbin/unrar) 2015-08-01 19:30:06,318::INFO::[sABnzbd:485] unzip binary... found (/usr/sbin/unzip) 2015-08-01 19:30:06,318::INFO::[sABnzbd:491] nice binary... found (/usr/sbin/nice) 2015-08-01 19:30:06,318::INFO::[sABnzbd:495] ionice binary... found (/usr/sbin/ionice) 2015-08-01 19:30:06,318::INFO::[sABnzbd:500] pyOpenSSL... found (True) 2015-08-01 19:30:06,319::INFO::[sABnzbd:1528] Starting web-interface on 0.0.0.0:8090 2015-08-01 19:30:06,321::INFO::[_cplogging:55] [01/Aug/2015:19:30:06] ENGINE Bus STARTING 2015-08-01 19:30:06,323::INFO::[_cplogging:55] [01/Aug/2015:19:30:06] ENGINE Started monitor thread '_TimeoutMonitor'. 2015-08-01 19:30:06,424::INFO::[_cplogging:55] [01/Aug/2015:19:30:06] ENGINE Serving on 0.0.0.0:8080 2015-08-01 19:30:06,525::INFO::[_cplogging:55] [01/Aug/2015:19:30:06] ENGINE Serving on 0.0.0.0:8090 2015-08-01 19:30:06,525::INFO::[_cplogging:55] [01/Aug/2015:19:30:06] ENGINE Bus STARTED 2015-08-01 19:30:06,525::INFO::[sABnzbd:1597] Starting SABnzbd.py-0.7.x 2015-08-01 19:30:06,526::INFO::[dirscanner:277] Dirscanner starting up 2015-08-01 19:30:06,526::INFO::[urlgrabber:77] URLGrabber starting up ideas? Link to comment
JustinChase Posted August 1, 2015 Share Posted August 1, 2015 okay, super weird. If I try to launch the docker from the docker page by clicking the icon, then WebUI, it fails to open. I can do this dozens of times over several minutes; all fail. If I open it from my bookmark, it opens fine. the address is exactly the same in both windows. Once I've opened it with a bookmark, the WebUI link starts working again. This is for both SABnzbd and Deluge. Same problem opening for several days. i only noticed the 'fix' because I had a tab with SABnzbd offscreen, and when I opened the tab, then went into settings, it worked, I could navigate around just fine. Then the WebUI started working. I tried Deluge, still wouldn't open, then opened the bookmark, worked fine, WebUI, worked fine. Not sure what's up; but there you go. Link to comment
binhex Posted August 2, 2015 Author Share Posted August 2, 2015 okay, super weird. If I try to launch the docker from the docker page by clicking the icon, then WebUI, it fails to open. I can do this dozens of times over several minutes; all fail. If I open it from my bookmark, it opens fine. the address is exactly the same in both windows. Once I've opened it with a bookmark, the WebUI link starts working again. This is for both SABnzbd and Deluge. Same problem opening for several days. i only noticed the 'fix' because I had a tab with SABnzbd offscreen, and when I opened the tab, then went into settings, it worked, I could navigate around just fine. Then the WebUI started working. I tried Deluge, still wouldn't open, then opened the bookmark, worked fine, WebUI, worked fine. Not sure what's up; but there you go. ok that IS odd, i have no idea whats going on there, must be some issues with the unraid webui i guess, very wierd, maybe if it happens again it might be worth checking the syslog also incase there are any clues in that. Link to comment
Kewjoe Posted August 3, 2015 Share Posted August 3, 2015 Hi All, First, thanks Binhex for the great docker apps! I'm all set up with the Deluge+VPN app, but I'm having some speed issues. I was on unRaid v5 with Transmission and VPN (PIA). On my 250mbit connection, I'd get down speeds around 80mbit. With unRaid v6 and Deluge+VPN, I'm only getting 2 mbit. I've been using the deluge container for about a month now, so it's not a small sample size. I'm using the same VPN server from PIA. I've tried others with no difference. I checked all my ports are mapped correctly. I went over my settings several times and they seem optimized for my connection. Anyone have any other ideas? Thanks! Link to comment
binhex Posted August 3, 2015 Author Share Posted August 3, 2015 Hi All, First, thanks Binhex for the great docker apps! I'm all set up with the Deluge+VPN app, but I'm having some speed issues. I was on unRaid v5 with Transmission and VPN (PIA). On my 250mbit connection, I'd get down speeds around 80mbit. With unRaid v6 and Deluge+VPN, I'm only getting 2 mbit. I've been using the deluge container for about a month now, so it's not a small sample size. I'm using the same VPN server from PIA. I've tried others with no difference. I checked all my ports are mapped correctly. I went over my settings several times and they seem optimized for my connection. Anyone have any other ideas? Thanks! one setting i know of that i had to tweak was "preferences/bandwidth/rate limit ip overhead", i unticked this option and i had dramatic speed improvements. i only have a 20Mb/s connection and am seeing approx 1.1 MB/s to 1.5 MB/s downloads, so approx a third loss when connected to VPN, i would assume with a very well seeded swarm you should be able to get 30-40 MB/s perhaps even higher, depending on which gateway your connected to. Link to comment
Sandimm Posted August 3, 2015 Share Posted August 3, 2015 Moved from 6.0 General Support Extremely new to UnRaid and very confused. Sorry, this will probably be long and maybe not as detailed as it should be as I'm still learning the ropes. I was able to follow the new install guide (very well written, thank you) and got the system up and running. Accidentally assigned 96GB SSD as a Data drive but was able to get the issue resolved and drives assigned correctly. Had a 2nd SSD that was added as an unassigned drive to store docker.img (10GB)and appdata. With long distance help from son was able to get that set up. Got all the docks I wanted installed (Plex, MiniDLNA, Couchpotato, Sonarr, Deluge & SABnzbd.) Got all configured but erred in defining /config(s) as /mnt/user/appdata/ rather than /mnt/cache/appdata/. Plex was installed by zipping laptop PMS files, copying to server, unzipping and copying to PlexMediaServer in appdata, per the directions I found on Plex forum. Everything worked for a couple of hours while I tried to get all the programs talking to each other correctly. Tried to make a change of some kind and received an error indicating I was out of space (sorry this was 2 days ago and didn't think to print screen the message.) Increased docker.img to 15GB and again it worked for a little while. Went to make another change (most likely a path as I struggled to get them right) and the webgui for docker would no longer load. That happened a 2nd time with a different docker and then I think Plex docker (limetech version) disappeared. In trying to figure out what was going on and since I thought the previous problem was caused by space problem, I discovered that the plexmediaserver folder in appdata had a "Size on Disk (36.3GB)" about 20 times greater than the "Size(2.09GB)" which may not have been a problem but sure looked like one to me since I only had 15Gb assigned for docker.img Next step was renaming docker.img and recreating, still couldn't get things working. So after discussing it, we (son and I) decided I would eliminate the 60GB ssd being used as an unassigned disk and just add it to the cache and create a cache pool. Which I did yesterday. Today I've spent the day reinstalling dockers, setting them up one by one, and making sure they work correctly before adding the next one and sending print screens to son to make sure I had it correct. /Configs were installed in /mnt/cache/appdata/. Installed SABnzbd, Sonarr, Couchpotata and tested each one making sure they worked and sent files to correct location. Then nstalled MiniDLNA, mainly just to have available and installed Deluge for when I get ready to figure it out. Then I attempted to install PLex (limetech) error at bottom said it couldn't be installed and there wasn't enough space. Looked at cache drive, looked at size of appdata, should be plenty of room, tried again. still no luck. Tried needo's Plex same result, tried binhex Plex same result. This is the actual error message for the last attempt. bcd10bc68599: Error downloading dependent layers 21182d18025f: Error pulling image (latest) from binhex/arch-plex, endpoint: https://registry-1.docker.io/v1/, ApplyLayer exit status 1 stdout: stderr: write /etc/group: no space left on device 21182d18025f: Error pulling image (latest) from binhex/arch-plex, ApplyLayer exit status 1 stdout: stderr: write /etc/group: no space left on device time="2015-08-02T14:50:06-05:00" level=fatal msg="Error pulling image (latest) from binhex/arch-plex, ApplyLayer exit status 1 stdout: stderr: write /etc/group: no space left on device" Son doesn't use Plex and isn't sure how to help. I don't know what other info I should include, hopefully hardware will show up in sig. Please tell me what other info you might need, still not sure of the terminology so I sometimes have trouble figuring out how to do something so I will problably need to be told how to get the info needed. I have not attempted anything since last try install Plex docker. Running dockers: SABnzbd, Sonarr, Couchpotato, Deluge, MiniDLNA Plugins: Community Applications, Unassigned Devices, Dynamix Auto Fan Control, Dynamix S3 Sleep, Dynamix Cache Directories, Dynamix Active Streams, Dynamix webGui, Dynamix System Statistics, Dynamix System Temperature Thanks for any direction you can give me. Additional info. I tried to just look at what other dockers were available (Community Applications ~ Media) and get this message: Warning: file_put_contents(): Only 8192 of 61617 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 694 Warning: usort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 423 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 448 tower-diagnostics-20150802-1645.zip Link to comment
Squid Posted August 3, 2015 Share Posted August 3, 2015 Warning: file_put_contents(): Only 8192 of 61617 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 694 Warning: usort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 423 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 448 As far as this error is concerned, it looks like your ram filled up for whatever reasons. Took me a little backtracking to figure out what was going on in exec.php since you're not on the current version of CA. The other errors followed due to the write failure to ram. A reboot will probably at least temporarily fix that issue. Link to comment
JustinChase Posted August 4, 2015 Share Posted August 4, 2015 Warning: file_put_contents(): Only 8192 of 61617 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 694 Warning: usort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 423 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 448 As far as this error is concerned, it looks like your ram filled up for whatever reasons. Took me a little backtracking to figure out what was going on in exec.php since you're not on the current version of CA. The other errors followed due to the write failure to ram. A reboot will probably at least temporarily fix that issue. Any way to figure out what's filling up RAM? Link to comment
m1ll3rt1m3 Posted August 4, 2015 Share Posted August 4, 2015 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. Link to comment
Squid Posted August 4, 2015 Share Posted August 4, 2015 Warning: file_put_contents(): Only 8192 of 61617 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 694 Warning: usort() expects parameter 1 to be array, null given in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 423 Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/community.applications/include/exec.php on line 448 As far as this error is concerned, it looks like your ram filled up for whatever reasons. Took me a little backtracking to figure out what was going on in exec.php since you're not on the current version of CA. The other errors followed due to the write failure to ram. A reboot will probably at least temporarily fix that issue. Any way to figure out what's filling up RAM? Somebody more versed in 'nix would probably be better qualified than myself to answer. Best guess initially would be to enter df at a terminal window and see what's at or close to 100%. And then we can go from there Link to comment
Sandimm Posted August 4, 2015 Share Posted August 4, 2015 Does this seem like the right info from the df command? Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 131072 2276 128796 2% /var/log /dev/sda1 7811056 77424 7733632 1% /boot /dev/md1 3905110812 2091556676 1813554136 54% /mnt/disk1 /dev/md2 1952560688 176246868 1776313820 10% /mnt/disk2 /dev/sdb1 76197208 16551468 42114196 29% /mnt/cache shfs 5857671500 2267803544 3589867956 39% /mnt/user0 shfs 5933868708 2284355012 3631982152 39% /mnt/user /dev/loop0 15728640 13936928 0 100% /var/lib/docker Link to comment
m1ll3rt1m3 Posted August 4, 2015 Share Posted August 4, 2015 Does this seem like the right info from the df command? Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 131072 2276 128796 2% /var/log /dev/sda1 7811056 77424 7733632 1% /boot /dev/md1 3905110812 2091556676 1813554136 54% /mnt/disk1 /dev/md2 1952560688 176246868 1776313820 10% /mnt/disk2 /dev/sdb1 76197208 16551468 42114196 29% /mnt/cache shfs 5857671500 2267803544 3589867956 39% /mnt/user0 shfs 5933868708 2284355012 3631982152 39% /mnt/user /dev/loop0 15728640 13936928 0 100% /var/lib/docker 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 Link to comment
Squid Posted August 4, 2015 Share Posted August 4, 2015 Does this seem like the right info from the df command? Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 131072 2276 128796 2% /var/log /dev/sda1 7811056 77424 7733632 1% /boot /dev/md1 3905110812 2091556676 1813554136 54% /mnt/disk1 /dev/md2 1952560688 176246868 1776313820 10% /mnt/disk2 /dev/sdb1 76197208 16551468 42114196 29% /mnt/cache shfs 5857671500 2267803544 3589867956 39% /mnt/user0 shfs 5933868708 2284355012 3631982152 39% /mnt/user /dev/loop0 15728640 13936928 0 100% /var/lib/docker 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 I think you're right. In which case since 15G should be more than sufficient for those containers running under normal circumstances, something is not correct with the settings of the containers. IE: SAB is downloading files within the container itself instead of outside the container to something like /mnt/user/downloads (mapped to something like /downloads) Link to comment
JustinChase Posted August 4, 2015 Share Posted August 4, 2015 I've had her send me the config screenshots of all her dockers, and they all seem right. Everything was working fine until she tried installing Plex, then it all went badly. Post the results of cd /var/lib/docker du I suspect docker.img file will need to be deleted and recreated. However, not just yet. Link to comment
JustinChase Posted August 4, 2015 Share Posted August 4, 2015 results of du are a page that scrolls for a long time, and she's unable to even see the top of the windows when finished. I suspect plex is/has started putting all it's files/folders here, for whatever reason. Unless there is some good way to manually remove these files/folders, I suspect killing/deleting the docker.img file and starting over is the way forward. If so, stop docker, check the delete image box, apply, turn on docker, leave the file location the same, then start by installing your dockers one at a time, and confirming they all work. Also, make sure the configurations of all docker config and internal docker programs point to locations that exist on the server. Best way is to click in the box and navigate to the folder, not manually type in the name. typing something in wrong, even wrong-case will cause these problems. Good luck. Link to comment
m1ll3rt1m3 Posted August 4, 2015 Share Posted August 4, 2015 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"? Link to comment
Sandimm Posted August 4, 2015 Share Posted August 4, 2015 Decided to start over with docker. Moved appdata off cache drive Deleted Docker.img using Settings/Docker Using Windows, checked Cache Drive which shows as empty in Windows. Tower/Main shows there is still 18GB used on the "empty" cache drive. Before starting over with Docker, I think I need to figure out what/where this 18GB is and eliminate it. Perfectly willing to reformat cache drive but not sure how to proceed with unRaid. I think I should Stop Array, remove cache disks, reboot, add disks back in and hope that gives me the option of reformating but not sure and not willing to proceed without someone that knows way more than I do confirming. Thanks in advance. Link to comment
m1ll3rt1m3 Posted August 5, 2015 Share Posted August 5, 2015 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. Anyone have any thoughts on this? Link to comment
m1ll3rt1m3 Posted August 5, 2015 Share Posted August 5, 2015 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. 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%. Link to comment
binhex Posted August 5, 2015 Author Share Posted August 5, 2015 quick heads up, for all you rich guys out there with plexpass account i've now created a plexpass docker image, you should see it listed in my docker repository, please let me know how you get on with it. cheers, binhex. p.s sorry for the lack of posts as of late, car troubles have kept me busy :'( edit - checked it and it works a treat for me, strangely i can run it even though my account isnt plexpass, obviously dont get the additional functionality of a plexpass account but it does mean im running pms 0.9.12.8 as opposed to 0.9.12.4, surprising but very cool Link to comment
mr-hexen Posted August 5, 2015 Share Posted August 5, 2015 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%. You will have to edit the 'auth' file in the deluge appdata folder and add a username/password. The syntax for this is: username:password:10 Dont forget to shutdown deluge to edit this file, then restart after. The '10' is the users privilege level, leave it at 10. Remember, CP connects directly to the daemon (port 58846) whereas Sonarr connects to the deluge mgmt service (port 8112). Set CP to connect to my.unraid.ip.address:58846 put the username and password you entered into the auth file. One last note, Labels don't seem to work between CP and Deluge right now. Link to comment
scottc Posted August 5, 2015 Share Posted August 5, 2015 Anyone else having problems with the latest update to DelugeVPN Updated to latest docker just a bit ago an now i can not connect to Deluge If i disable VPN by setting the VPN_ENABLED = no i can connect fine, but when i do VPN_ENABLED = yes and try to pull up deluge it can not connect Here is the log output from the docker root@Tower:~# docker logs binhex-delugevpn 2015-08-05 10:49:19,534 CRIT Set uid to user 0 2015-08-05 10:49:19,534 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing 2015-08-05 10:49:19,540 INFO supervisord started with pid 1 2015-08-05 10:49:20,543 INFO spawned: 'deluge' with pid 7 2015-08-05 10:49:20,547 INFO spawned: 'setip' with pid 8 2015-08-05 10:49:20,550 INFO spawned: 'start' with pid 9 2015-08-05 10:49:20,553 INFO spawned: 'webui' with pid 10 2015-08-05 10:49:20,555 INFO spawned: 'privoxy' with pid 11 2015-08-05 10:49:20,557 INFO spawned: 'setport' with pid 12 2015-08-05 10:49:20,558 DEBG 'deluge' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2015-08-05 10:49:20,558 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-05 10:49:20,558 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-05 10:49:20,559 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-05 10:49:20,559 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-08-05 10:49:20,561 DEBG 'start' stdout output: [info] VPN is enabled, beginning configuration of OpenVPN 2015-08-05 10:49:20,570 DEBG 'start' stdout output: [info] VPN provider defined as pia 2015-08-05 10:49:20,571 DEBG 'start' stdout output: [info] VPN provider defined as pia 2015-08-05 10:49:20,571 DEBG 'privoxy' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2015-08-05 10:49:20,575 DEBG 'start' stdout output: [info] VPN provider remote gateway and port defined as nl.privateinternetaccess.com 1194 2015-08-05 10:49:20,618 DEBG 'start' stdout output: [info] ip routing table 2015-08-05 10:49:20,619 DEBG 'start' stdout output: default via 172.17.42.1 dev eth0 2015-08-05 10:49:20,620 DEBG 'start' stdout output: 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.16 2015-08-05 10:49:20,620 DEBG 'start' stdout output: -------------------- 2015-08-05 10:49:20,660 DEBG 'start' stdout output: [info] iptables 2015-08-05 10:49:20,662 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 -p udp -m udp --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 -p udp -m udp --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-05 10:49:20,663 DEBG 'start' stdout output: -------------------- [info] nameservers 2015-08-05 10:49:20,664 DEBG 'start' stdout output: nameserver 8.8.8.8 nameserver 8.8.4.4 2015-08-05 10:49:20,664 DEBG 'start' stdout output: -------------------- [info] Starting OpenVPN... 2015-08-05 10:49:20,672 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. Use --help for more information. 2015-08-05 10:49:20,673 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47686693744080 for <Subprocess at 47686693742208 with name start in state RUNNING> (stdout)> 2015-08-05 10:49:20,673 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47686693744512 for <Subprocess at 47686693742208 with name start in state RUNNING> (stderr)> 2015-08-05 10:49:20,673 INFO exited: start (exit status 1; not expected) 2015-08-05 10:49:20,674 DEBG received SIGCLD indicating a child quit 2015-08-05 10:49:21,674 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-08-05 10:49:21,674 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) root@Tower:~# i think this is probably the issue 2015-08-05 10:49:20,672 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. Use --help for more information. 2015-08-05 10:49:20,673 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47686693744080 for <Subprocess at 47686693742208 with name start in state RUNNING> (stdout)> 2015-08-05 10:49:20,673 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47686693744512 for <Subprocess at 47686693742208 with name start in state RUNNING> (stderr)> 2015-08-05 10:49:20,673 INFO exited: start (exit status 1; not expected) 2015-08-05 10:49:20,674 DEBG received SIGCLD indicating a child quit Anyone have any thoughts Link to comment
binhex Posted August 5, 2015 Author Share Posted August 5, 2015 hi scottc, can you open your .ovpn file and remove any line that begins with ping, save the file and then restart the docker, let me know what the outcome is. Link to comment
Recommended Posts