[ARCHIVE] binhex docker repository


Recommended Posts

Thanks man. verified working.

 

Moved my cache over to PCIE-based SSD and downloaded a known file with missing blocks.  Verify/repair slammed my both my vCPUs to 99% and hit Read/Write on the cache virtual disk at 150MB/s each concurrently.  I'll have to find some bigger files to really push the limit as it's rated for 1.1GB/s :D

 

Not sure if anyone would benefit from it, but IONice would be another possibly beneficial inclusion to prevent disk thrashing when doing verify/repair/unrar.  I used to have issues with buffering of video playback when a lot that stuff was going on in the background, but won't be an issue with the SSD, just thinking about others.

 

 

On a less related note, if I wanted an app that you don't support, can I just deploy your arch-base container, install an app and export to my own container/repo (generally speaking)?  I'm still not in the know with docker, haven't used it at work yet.

Link to comment

Thanks man. verified working.

 

Moved my cache over to PCIE-based SSD and downloaded a known file with missing blocks.  Verify/repair slammed my both my vCPUs to 99% and hit Read/Write on the cache virtual disk at 150MB/s each concurrently.  I'll have to find some bigger files to really push the limit as it's rated for 1.1GB/s :D

 

Not sure if anyone would benefit from it, but IONice would be another possibly beneficial inclusion to prevent disk thrashing when doing verify/repair/unrar.  I used to have issues with buffering of video playback when a lot that stuff was going on in the background, but won't be an issue with the SSD, just thinking about others.

 

 

On a less related note, if I wanted an app that you don't support, can I just deploy your arch-base container, install an app and export to my own container/repo (generally speaking)?  I'm still not in the know with docker, haven't used it at work yet.

 

hi dephcon, thanks for confirming it works, as to your comment regards using ionice, by the look of the sabnzbd ui you can specify ionice and also nice values, not sure if i need to include any additional libraries for this to work, have you tried defining some values to see if it works?.

 

on your second question, its relatively easy, firstly signup to github and get yourself an account, then signup to docker hub, then clone one of my existing dockers, pull it down to your dev machine and then look in the install.sh bash script (if installing an app present in the official arch repo) or look in the packer.sh bash script (if installing an app from the aur), simply replace the package name for the app your installing, save it, push it up to github, then goto docker hub and create a new public repo and link it with the github repo and it should then start building.

 

the tricky bit is working out what needs to be re-routed outside of the docker container, so you most probably will need to do some bash scripting to get config files/db's etc pointed to the volume for the docker (e.g. /config) , the other thing to keep in mind is the application process cannot be daemonised, so it must run as a foreground process, good luck!.

Link to comment

Looks they they're included out of the box now, the sab wiki still mentions that they need to be installed.  I added the recommended ionice parameters to my config and they did not throw an error then checked out the container:

 

root@Vault13:~# docker exec -i -t 6000ac5a022f bash
[root@6000ac5a022f /]# ionice -help

Usage:
ionice [options] -p <pid>...
ionice [options] -P <pgid>...
ionice [options] -u <uid>...
ionice [options] <command>

Show or change the I/O-scheduling class and priority of a process.

Options:
-c, --class <class>    name or number of scheduling class,
                          0: none, 1: realtime, 2: best-effort, 3: idle
-n, --classdata <num>  priority (0..7) in the specified scheduling class,
                          only for the realtime and best-effort classes
-p, --pid <pid>...     act on these already running processes
-P, --pgid <pgrp>...   act on already running processes in these groups
-t, --ignore           ignore failures
-u, --uid <uid>...     act on already running processes owned by these users

-h, --help     display this help and exit
-V, --version  output version information and exit

For more details see ionice(1).

[root@6000ac5a022f /]# nice --help
Usage: nice [OPTION] [COMMAND [ARG]...]
Run COMMAND with an adjusted niceness, which affects process scheduling.
With no COMMAND, print the current niceness.  Niceness values range from
-20 (most favorable to the process) to 19 (least favorable to the process).

Mandatory arguments to long options are mandatory for short options too.
  -n, --adjustment=N   add integer N to the niceness (default 10)
      --help     display this help and exit
      --version  output version information and exit

NOTE: your shell may have its own version of nice, which usually supersedes
the version described here.  Please refer to your shell's documentation
for details about the options it supports.

GNU coreutils online help: <http://www.gnu.org/software/coreutils/>
For complete documentation, run: info coreutils 'nice invocation'
[root@6000ac5a022f /]#

 

Hmm making docker containers sounds similar to what I've done with contextualization scripts on older versions of opennebula to deploy VMs on KVM... I hated doing that so hopefully this is more straight forward.  I'll take a stab at it once all the GTA V PC hullabaloo dies down.

 

PSA:

I would recommend that everyone using binhex's sabnzbd container leverage both multicore par2 and ionice.  It gives to the advantage of much faster verification/repair times AND wont cause any of the verification/repair/unrar from stealing diskIO from other server tasks, esp media streaming.  I've been using -t+ for my multicore par2 parameter for a couple years with great success and am now using -c2 -n4 for IONice as per the sabnzbd wiki recommendation.

Link to comment

PSA:

I would recommend that everyone using binhex's sabnzbd container leverage both multicore par2 and ionice.  It gives to the advantage of much faster verification/repair times AND wont cause any of the verification/repair/unrar from stealing diskIO from other server tasks, esp media streaming.  I've been using -t+ for my multicore par2 parameter for a couple years with great success and am now using -c2 -n4 for IONice as per the sabnzbd wiki recommendation.

I thought I had multicore enabled, but when I went in and looked at my config, it was not.  Added your values, but I get this when a repair is attempted:

 

PAR2 received incorrect options, check your Config->Switches settings

 

I entered the Docker container (binhex) and ran a par2 --help.  It does not list any of the -t as an option, nor can I find anything about it being the multicore version.  What am I doing wrong here?

Link to comment

Firstly, I just wanted to say nice work on the deluge+vpn container, almost exactly what I was looking for!! I was wondering though.. and I know it's probably kind of a big ask.. but would you possibly be inclined to make a similar transmission+vpn container?

 

I would hope it wouldn't take as long since you probably figured out the kinks/hurdles for the deluge one maybe..?

Link to comment

I thought I had multicore enabled, but when I went in and looked at my config, it was not.  Added your values, but I get this when a repair is attempted:

 

PAR2 received incorrect options, check your Config->Switches settings

 

I entered the Docker container (binhex) and ran a par2 --help.  It does not list any of the -t as an option, nor can I find anything about it being the multicore version.  What am I doing wrong here?

 

Is your host/vm multicore and did you update the docker container since binhex updated it?  as you can see my container has the multicore par2:

 

[root@6000ac5a022f /]# par2

Not enough command line arguments.

par2cmdline version 0.4, Copyright © 2003 Peter Brian Clements.

Modifications for concurrent processing, Unicode support, and hierarchial

directory support are Copyright © 2007-2014 Vincent Tan.

Concurrent processing utilises Intel Thread Building Blocks 4.3 Update 1,

 

 

Link to comment

Is your host/vm multicore and did you update the docker container since binhex updated it?  as you can see my container has the multicore par2:

 

[root@6000ac5a022f /]# par2

Not enough command line arguments.

par2cmdline version 0.4, Copyright © 2003 Peter Brian Clements.

Modifications for concurrent processing, Unicode support, and hierarchial

directory support are Copyright © 2007-2014 Vincent Tan.

Concurrent processing utilises Intel Thread Building Blocks 4.3 Update 1,

 

Maybe I need to wipe out the container and start over? I definitely updated it within the unRAID Docker page.  I ran nproc within the container and it is showing 2 cores.  Running par2 by itself doesn't give me anything of worth, and it looks like our versions are different.  Weird!

 

root@titan:~# docker exec -ti binhex-sabnzbd /bin/bash
[root@8e09a7ffbebc /]# nproc
2
[root@8e09a7ffbebc /]# par2
Not enough command line arguments.
[root@8e09a7ffbebc /]# par2 -V
par2cmdline version 0.6.11
[root@8e09a7ffbebc /]# 

 

Link to comment

Is your host/vm multicore and did you update the docker container since binhex updated it?  as you can see my container has the multicore par2:

 

[root@6000ac5a022f /]# par2

Not enough command line arguments.

par2cmdline version 0.4, Copyright © 2003 Peter Brian Clements.

Modifications for concurrent processing, Unicode support, and hierarchial

directory support are Copyright © 2007-2014 Vincent Tan.

Concurrent processing utilises Intel Thread Building Blocks 4.3 Update 1,

 

Maybe I need to wipe out the container and start over? I definitely updated it within the unRAID Docker page.  I ran nproc within the container and it is showing 2 cores.  Running par2 by itself doesn't give me anything of worth, and it looks like our versions are different.  Weird!

 

root@titan:~# docker exec -ti binhex-sabnzbd /bin/bash
[root@8e09a7ffbebc /]# nproc
2
[root@8e09a7ffbebc /]# par2
Not enough command line arguments.
[root@8e09a7ffbebc /]# par2 -V
par2cmdline version 0.6.11
[root@8e09a7ffbebc /]# 

 

that is odd!, def looks on the face of it like you don't have the latest image, can you click on the "reload info" button and see if the text for icon changes to blue to indicate an update is waiting?.

 

if it doesnt turn blue then yeah probably your best bet is to delete the docker image and container, then re-add (using your existing "my template") and see if that forces it.

Link to comment

that is odd!, def looks on the face of it like you don't have the latest image, can you click on the "reload info" button and see if the text for icon changes to blue to indicate an update is waiting?.

 

if it doesnt turn blue then yeah probably your best bet is to delete the docker image and container, then re-add (using your existing "my template") and see if that forces it.

It is odd, huh!  So I updated the container when I read that you incorporated the multicore par2, which it did successfully.  Both yesterday and today it is showing all my Dockers are up-to-date, even when I click the Check for Updates button.  I'm using the binhex/arch-sabnzbd:latest repo.

 

Not sure where the reload info button is, however, and I've been actively looking for it.  Do I need to disable Docker for that option to show up?

 

Edit: I just went ahead and deleted image and container, and re-added.  Now when I enter the container and run 'par2', I get the same version as Dephcon.  So strange how mine didn't update!  I wonder if its related to my lack of having this 'reload info' button.

Link to comment

PSA:

I would recommend that everyone using binhex's sabnzbd container leverage both multicore par2 and ionice.  It gives to the advantage of much faster verification/repair times AND wont cause any of the verification/repair/unrar from stealing diskIO from other server tasks, esp media streaming.  I've been using -t+ for my multicore par2 parameter for a couple years with great success and am now using -c2 -n4 for IONice as per the sabnzbd wiki recommendation.

 

After further testing I'm going to suggest that in addition to multicore par2 and IONice, Nice should also be used with the suggested value of -n10.  It can't hurt and will prevent sab from choking out other processes. 

 

I just noticed my unraid VM take a beating and figured it was worth implementing instead of adding more cores for now.  I'm down to a single 2core unraid VM from a single core unraid vm + 4core usenet app/tool vm and want to see how slim I can make this new dockerized version of unraid.

Link to comment

Hi binhex

 

I have installed you delugevpn application and when I go to the WebUI it errors out stating "the site cannot be found". Also has anyone successfully used your vpn with IPVanish?

 

Thanks in advance

 

can you post the supervisord.log file, please make sure to remove any sensitive info before, im assuming you have downloaded the ovpn file from ipvanish, yes?

Link to comment

2015-04-15 17:24:34,510 CRIT Set uid to user 0

2015-04-15 17:24:34,510 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 17:24:34,513 INFO supervisord started with pid 1

2015-04-15 17:24:35,515 INFO spawned: 'deluge' with pid 8

2015-04-15 17:24:35,517 INFO spawned: 'setip' with pid 9

2015-04-15 17:24:35,518 INFO spawned: 'start' with pid 10

2015-04-15 17:24:35,519 INFO spawned: 'webui' with pid 11

2015-04-15 17:24:35,521 INFO spawned: 'privoxy' with pid 12

2015-04-15 17:24:35,522 INFO spawned: 'setport' with pid 13

2015-04-15 17:24:35,539 DEBG 'start' stdout output:

[crit] VPN provider unknown, please specify airvpn, pia, or custom

 

2015-04-15 17:24:35,539 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 17:24:35,539 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 17:24:35,539 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 17:24:35,539 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 17:24:35,540 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47218701927776 for <Subprocess at 47218699688992 with name start in state RUNNING> (stderr)>

2015-04-15 17:24:35,540 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47218701927344 for <Subprocess at 47218699688992 with name start in state RUNNING> (stdout)>

2015-04-15 17:24:35,540 INFO exited: start (exit status 1; not expected)

2015-04-15 17:24:35,540 DEBG received SIGCLD indicating a child quit

2015-04-15 17:24:36,541 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 17:24:36,542 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 19:00:05,258 WARN received SIGTERM indicating exit request

2015-04-15 19:00:05,290 DEBG killing setport (pid 13) with signal SIGTERM

2015-04-15 19:00:05,319 INFO waiting for deluge, setip, webui, privoxy, setport to die

2015-04-15 19:00:05,346 DEBG fd 34 closed, stopped monitoring <POutputDispatcher at 47218701930368 for <Subprocess at 47218699688848 with name setport in state STOPPING> (stderr)>

2015-04-15 19:00:05,346 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 47218701929936 for <Subprocess at 47218699688848 with name setport in state STOPPING> (stdout)>

2015-04-15 19:00:05,346 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 19:00:05,346 INFO reaped unknown pid 5868

2015-04-15 19:00:05,346 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:05,346 DEBG killing privoxy (pid 12) with signal SIGTERM

2015-04-15 19:00:05,347 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 47218701929072 for <Subprocess at 47218699688560 with name privoxy in state STOPPING> (stdout)>

2015-04-15 19:00:05,347 DEBG fd 29 closed, stopped monitoring <POutputDispatcher at 47218701929504 for <Subprocess at 47218699688560 with name privoxy in state STOPPING> (stderr)>

2015-04-15 19:00:05,347 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 19:00:05,347 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:05,347 DEBG killing webui (pid 11) with signal SIGTERM

2015-04-15 19:00:05,347 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47218701928640 for <Subprocess at 47218699689136 with name webui in state STOPPING> (stderr)>

2015-04-15 19:00:05,348 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47218701928208 for <Subprocess at 47218699689136 with name webui in state STOPPING> (stdout)>

2015-04-15 19:00:05,348 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 19:00:05,348 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:05,398 INFO reaped unknown pid 5882

2015-04-15 19:00:05,398 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:05,398 DEBG killing setip (pid 9) with signal SIGTERM

2015-04-15 19:00:05,399 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 47218701926480 for <Subprocess at 47218699688704 with name setip in state STOPPING> (stdout)>

2015-04-15 19:00:05,399 DEBG fd 14 closed, stopped monitoring <POutputDispatcher at 47218701926912 for <Subprocess at 47218699688704 with name setip in state STOPPING> (stderr)>

2015-04-15 19:00:05,399 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 19:00:05,399 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:05,399 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 19:00:05,400 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47218699689568 for <Subprocess at 47218699688344 with name deluge in state STOPPING> (stderr)>

2015-04-15 19:00:05,400 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47218699689208 for <Subprocess at 47218699688344 with name deluge in state STOPPING> (stdout)>

2015-04-15 19:00:05,400 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 19:00:05,400 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:12,937 CRIT Set uid to user 0

2015-04-15 19:00:12,937 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 19:00:12,944 INFO supervisord started with pid 1

2015-04-15 19:00:13,946 INFO spawned: 'deluge' with pid 8

2015-04-15 19:00:13,947 INFO spawned: 'setip' with pid 9

2015-04-15 19:00:13,949 INFO spawned: 'start' with pid 10

2015-04-15 19:00:13,950 INFO spawned: 'webui' with pid 11

2015-04-15 19:00:13,951 INFO spawned: 'privoxy' with pid 12

2015-04-15 19:00:13,953 INFO spawned: 'setport' with pid 13

2015-04-15 19:00:14,024 DEBG 'start' stdout output:

[crit] VPN provider unknown, please specify airvpn, pia, or custom

 

2015-04-15 19:00:14,024 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:00:14,024 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:00:14,024 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:00:14,025 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:00:14,025 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47515205043552 for <Subprocess at 47515202804768 with name start in state RUNNING> (stderr)>

2015-04-15 19:00:14,025 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47515205043120 for <Subprocess at 47515202804768 with name start in state RUNNING> (stdout)>

2015-04-15 19:00:14,025 INFO exited: start (exit status 1; not expected)

2015-04-15 19:00:14,025 DEBG received SIGCLD indicating a child quit

2015-04-15 19:00:15,026 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 19:00:15,027 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 19:10:08,097 WARN received SIGTERM indicating exit request

2015-04-15 19:10:08,097 DEBG killing setport (pid 13) with signal SIGTERM

2015-04-15 19:10:08,097 INFO waiting for deluge, setip, webui, privoxy, setport to die

2015-04-15 19:10:08,097 DEBG fd 34 closed, stopped monitoring <POutputDispatcher at 47515205046144 for <Subprocess at 47515202804624 with name setport in state STOPPING> (stderr)>

2015-04-15 19:10:08,097 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 47515205045712 for <Subprocess at 47515202804624 with name setport in state STOPPING> (stdout)>

2015-04-15 19:10:08,097 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 19:10:08,097 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:08,098 DEBG killing privoxy (pid 12) with signal SIGTERM

2015-04-15 19:10:08,098 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 47515205044848 for <Subprocess at 47515202804336 with name privoxy in state STOPPING> (stdout)>

2015-04-15 19:10:08,098 DEBG fd 29 closed, stopped monitoring <POutputDispatcher at 47515205045280 for <Subprocess at 47515202804336 with name privoxy in state STOPPING> (stderr)>

2015-04-15 19:10:08,098 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 19:10:08,098 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:08,098 DEBG killing webui (pid 11) with signal SIGTERM

2015-04-15 19:10:08,098 DEBG fd 24 closed, stopped monitoring <POutputDispatcher at 47515205044416 for <Subprocess at 47515202804912 with name webui in state STOPPING> (stderr)>

2015-04-15 19:10:08,098 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 47515205043984 for <Subprocess at 47515202804912 with name webui in state STOPPING> (stdout)>

2015-04-15 19:10:08,099 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 19:10:08,099 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:08,101 INFO reaped unknown pid 10300

2015-04-15 19:10:08,101 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:08,101 DEBG killing setip (pid 9) with signal SIGTERM

2015-04-15 19:10:08,101 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 47515205042256 for <Subprocess at 47515202804480 with name setip in state STOPPING> (stdout)>

2015-04-15 19:10:08,101 DEBG fd 14 closed, stopped monitoring <POutputDispatcher at 47515205042688 for <Subprocess at 47515202804480 with name setip in state STOPPING> (stderr)>

2015-04-15 19:10:08,101 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 19:10:08,101 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:08,101 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 19:10:08,102 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47515202805344 for <Subprocess at 47515202804120 with name deluge in state STOPPING> (stderr)>

2015-04-15 19:10:08,102 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47515202804984 for <Subprocess at 47515202804120 with name deluge in state STOPPING> (stdout)>

2015-04-15 19:10:08,102 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 19:10:08,102 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:14,269 CRIT Set uid to user 0

2015-04-15 19:10:14,269 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 19:10:14,272 INFO supervisord started with pid 1

2015-04-15 19:10:15,274 INFO spawned: 'deluge' with pid 8

2015-04-15 19:10:15,274 INFO spawned: 'setip' with pid 9

2015-04-15 19:10:15,275 INFO spawned: 'start' with pid 10

2015-04-15 19:10:15,276 INFO spawned: 'webui' with pid 11

2015-04-15 19:10:15,277 INFO spawned: 'privoxy' with pid 12

2015-04-15 19:10:15,278 INFO spawned: 'setport' with pid 13

2015-04-15 19:10:15,292 DEBG 'start' stdout output:

[crit] VPN provider unknown, please specify airvpn, pia, or custom

 

2015-04-15 19:10:15,292 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:10:15,292 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:10:15,292 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:10:15,292 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 19:10:15,292 DEBG fd 19 closed, stopped monitoring <POutputDispatcher at 47604576085344 for <Subprocess at 47604573846560 with name start in state RUNNING> (stderr)>

2015-04-15 19:10:15,292 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 47604576084912 for <Subprocess at 47604573846560 with name start in state RUNNING> (stdout)>

2015-04-15 19:10:15,292 INFO exited: start (exit status 1; not expected)

2015-04-15 19:10:15,292 DEBG received SIGCLD indicating a child quit

2015-04-15 19:10:16,294 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 19:10:16,294 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

opvn & crt file in /mnt/cache/delugevpn/openvpn

 

cheers

Link to comment

excuse my limited knowledge, is not done by the WebUI which I can't access?

 

cheers

 

you cant access the webui because until the vpn tunnel is established deluge wont start, thus you get no webui. you need to fix the vpn provider first, then deluge will start and you will be able to access the webui

Link to comment

thanks, can I ask how you edit those settings?

 

using the unraid webui docker tab, the variables are defined there when you initially setup the docker, please keep in mind if your using beta 14 then you will probably need to do the following in order to see the instructions "Click the "Advanced View" toggle on the top right and fill in required fields e.g. volume data, environment variables etc".

Link to comment

Thanks for that! I feel I'm making progress still WebUI?

 

/usr/bin/docker logs --tail=350 -f binhex-delugevpn 2>&1

2015-04-15 20:43:14,349 CRIT Set uid to user 0

2015-04-15 20:43:14,349 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 20:43:14,351 INFO supervisord started with pid 1

2015-04-15 20:43:15,353 INFO spawned: 'deluge' with pid 8

2015-04-15 20:43:15,354 INFO spawned: 'setip' with pid 9

2015-04-15 20:43:15,354 INFO spawned: 'start' with pid 10

2015-04-15 20:43:15,355 INFO spawned: 'webui' with pid 11

2015-04-15 20:43:15,355 INFO spawned: 'privoxy' with pid 12

2015-04-15 20:43:15,356 INFO spawned: 'setport' with pid 13

2015-04-15 20:43:15,371 DEBG 'start' stdout output:

[info] VPN provider defined as custom

 

2015-04-15 20:43:15,371 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 20:43:15,371 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 20:43:15,371 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 20:43:15,371 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 20:43:15,576 DEBG 'start' stdout output:

[info] ip route

 

2015-04-15 20:43:15,577 DEBG 'start' stdout output:

default via 172.17.42.1 dev eth0

8.8.4.4 via 172.17.42.1 dev eth0

 

2015-04-15 20:43:15,577 DEBG 'start' stdout output:

8.8.8.8 via 172.17.42.1 dev eth0

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.22

173.245.0.0/16 via 172.17.42.1 dev eth0

--------------------

 

2015-04-15 20:43:15,589 DEBG 'start' stdout output:

[info] iptables

 

2015-04-15 20:43:15,590 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --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 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -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 -o eth0 -p udp -m udp --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 -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-04-15 20:43:15,590 DEBG 'start' stdout output:

--------------------

[info] nameservers

 

2015-04-15 20:43:15,590 DEBG 'start' stdout output:

nameserver 8.8.8.8

nameserver 8.8.4.4

 

2015-04-15 20:43:15,590 DEBG 'start' stdout output:

--------------------

[info] Starting OpenVPN...

 

2015-04-15 20:43:15,593 DEBG 'start' stdout output:

Wed Apr 15 20:43:15 2015 DEPRECATED OPTION: --tls-remote, please update your configuration

 

2015-04-15 20:43:15,593 DEBG 'start' stdout output:

Wed Apr 15 20:43:15 2015 OpenVPN 2.3.6 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 2 2014

Wed Apr 15 20:43:15 2015 library versions: OpenSSL 1.0.2 22 Jan 2015, LZO 2.09

 

2015-04-15 20:43:15,593 DEBG 'start' stderr output:

Enter Auth Username:

2015-04-15 20:43:16,594 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 20:43:16,595 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 21:03:02,198 WARN received SIGTERM indicating exit request

2015-04-15 21:03:02,199 DEBG killing setport (pid 13) with signal SIGTERM

2015-04-15 21:03:02,199 INFO waiting for deluge, setip, start, webui, privoxy, setport to die

2015-04-15 21:03:02,199 DEBG fd 34 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,199 DEBG fd 30 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,199 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 21:03:02,199 DEBG received SIGCLD indicating a child quit

2015-04-15 21:03:02,199 DEBG killing privoxy (pid 12) with signal SIGTERM

2015-04-15 21:03:02,199 DEBG fd 25 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,199 DEBG fd 29 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,199 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 21:03:02,199 DEBG received SIGCLD indicating a child quit

2015-04-15 21:03:02,199 DEBG killing webui (pid 11) with signal SIGTERM

2015-04-15 21:03:02,199 DEBG fd 24 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,200 DEBG fd 20 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,200 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 21:03:02,200 DEBG received SIGCLD indicating a child quit

2015-04-15 21:03:02,200 DEBG killing start (pid 10) with signal SIGTERM

2015-04-15 21:03:02,200 DEBG fd 19 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,200 DEBG fd 15 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,200 INFO stopped: start (terminated by SIGTERM)

2015-04-15 21:03:02,200 DEBG received SIGCLD indicating a child quit

2015-04-15 21:03:02,200 DEBG killing setip (pid 9) with signal SIGTERM

2015-04-15 21:03:02,200 DEBG fd 9 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,200 DEBG fd 14 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,200 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 21:03:02,200 INFO reaped unknown pid 138

2015-04-15 21:03:02,200 DEBG received SIGCLD indicating a child quit

2015-04-15 21:03:02,200 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 21:03:02,201 DEBG fd 8 closed, stopped monitoring (stderr)>

2015-04-15 21:03:02,201 DEBG fd 6 closed, stopped monitoring (stdout)>

2015-04-15 21:03:02,201 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 21:03:02,201 DEBG received SIGCLD indicating a child quit

2015-04-15 21:08:50,148 CRIT Set uid to user 0

2015-04-15 21:08:50,175 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 21:08:50,257 INFO supervisord started with pid 1

2015-04-15 21:08:51,259 INFO spawned: 'deluge' with pid 8

2015-04-15 21:08:51,331 INFO spawned: 'setip' with pid 11

2015-04-15 21:08:51,372 INFO spawned: 'start' with pid 15

2015-04-15 21:08:51,374 INFO spawned: 'webui' with pid 16

2015-04-15 21:08:51,375 INFO spawned: 'privoxy' with pid 17

2015-04-15 21:08:51,376 INFO spawned: 'setport' with pid 18

2015-04-15 21:08:51,921 DEBG 'start' stdout output:

[info] VPN provider defined as custom

 

2015-04-15 21:08:51,921 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:08:51,921 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:08:51,921 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:08:51,921 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:08:52,922 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 21:08:52,922 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 21:08:53,679 DEBG 'start' stdout output:

[info] ip route

 

2015-04-15 21:08:53,679 DEBG 'start' stdout output:

default via 172.17.42.1 dev eth0

8.8.4.4 via 172.17.42.1 dev eth0

 

2015-04-15 21:08:53,679 DEBG 'start' stdout output:

8.8.8.8 via 172.17.42.1 dev eth0

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.6

173.245.0.0/16 via 172.17.42.1 dev eth0

--------------------

 

2015-04-15 21:08:53,885 DEBG 'start' stdout output:

[info] iptables

 

2015-04-15 21:08:53,886 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --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 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -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 -o eth0 -p udp -m udp --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 -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-04-15 21:08:53,900 DEBG 'start' stdout output:

--------------------

[info] nameservers

nameserver 8.8.8.8

nameserver 8.8.4.4

--------------------

[info] Starting OpenVPN...

 

2015-04-15 21:08:54,054 DEBG 'start' stdout output:

Wed Apr 15 21:08:54 2015 DEPRECATED OPTION: --tls-remote, please update your configuration

 

2015-04-15 21:08:54,054 DEBG 'start' stdout output:

Wed Apr 15 21:08:54 2015 OpenVPN 2.3.6 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 2 2014

Wed Apr 15 21:08:54 2015 library versions: OpenSSL 1.0.2 22 Jan 2015, LZO 2.09

 

2015-04-15 21:08:54,054 DEBG 'start' stderr output:

Enter Auth Username:

2015-04-15 21:15:31,172 WARN received SIGTERM indicating exit request

2015-04-15 21:15:31,172 DEBG killing setport (pid 18) with signal SIGTERM

2015-04-15 21:15:31,172 INFO waiting for deluge, setip, start, webui, privoxy, setport to die

2015-04-15 21:15:31,172 DEBG fd 34 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,172 DEBG fd 30 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,172 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 21:15:31,173 DEBG received SIGCLD indicating a child quit

2015-04-15 21:15:31,173 DEBG killing privoxy (pid 17) with signal SIGTERM

2015-04-15 21:15:31,173 DEBG fd 25 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,173 DEBG fd 29 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,173 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 21:15:31,173 DEBG received SIGCLD indicating a child quit

2015-04-15 21:15:31,173 DEBG killing webui (pid 16) with signal SIGTERM

2015-04-15 21:15:31,174 DEBG fd 24 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,174 DEBG fd 20 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,174 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 21:15:31,174 DEBG received SIGCLD indicating a child quit

2015-04-15 21:15:31,174 DEBG killing start (pid 15) with signal SIGTERM

2015-04-15 21:15:31,174 DEBG fd 19 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,174 DEBG fd 15 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,174 INFO stopped: start (terminated by SIGTERM)

2015-04-15 21:15:31,174 DEBG received SIGCLD indicating a child quit

2015-04-15 21:15:31,175 DEBG killing setip (pid 11) with signal SIGTERM

2015-04-15 21:15:31,175 DEBG fd 9 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,175 DEBG fd 14 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,175 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 21:15:31,175 INFO reaped unknown pid 514

2015-04-15 21:15:31,175 DEBG received SIGCLD indicating a child quit

2015-04-15 21:15:31,175 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 21:15:31,176 DEBG fd 8 closed, stopped monitoring (stderr)>

2015-04-15 21:15:31,176 DEBG fd 6 closed, stopped monitoring (stdout)>

2015-04-15 21:15:31,176 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 21:15:31,176 DEBG received SIGCLD indicating a child quit

2015-04-15 21:17:18,203 CRIT Set uid to user 0

2015-04-15 21:17:18,203 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 21:17:18,207 INFO supervisord started with pid 1

2015-04-15 21:17:19,208 INFO spawned: 'deluge' with pid 8

2015-04-15 21:17:19,209 INFO spawned: 'setip' with pid 9

2015-04-15 21:17:19,210 INFO spawned: 'start' with pid 10

2015-04-15 21:17:19,210 INFO spawned: 'webui' with pid 11

2015-04-15 21:17:19,211 INFO spawned: 'privoxy' with pid 12

2015-04-15 21:17:19,212 INFO spawned: 'setport' with pid 13

2015-04-15 21:17:19,224 DEBG 'start' stdout output:

[info] VPN provider defined as custom

 

2015-04-15 21:17:19,224 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:17:19,224 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:17:19,224 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:17:19,224 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 21:17:20,218 DEBG 'start' stdout output:

[info] ip route

 

2015-04-15 21:17:20,218 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 21:17:20,218 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 21:17:20,219 DEBG 'start' stdout output:

default via 172.17.42.1 dev eth0

8.8.4.4 via 172.17.42.1 dev eth0

8.8.8.8 via 172.17.42.1 dev eth0

 

2015-04-15 21:17:20,219 DEBG 'start' stdout output:

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.7

173.245.0.0/16 via 172.17.42.1 dev eth0

--------------------

 

2015-04-15 21:17:20,238 DEBG 'start' stdout output:

[info] iptables

 

2015-04-15 21:17:20,239 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -j ACCEPT

-A INPUT -i eth0 -p udp -m udp --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 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -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 -o eth0 -p udp -m udp --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 -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-04-15 21:17:20,240 DEBG 'start' stdout output:

--------------------

 

2015-04-15 21:17:20,240 DEBG 'start' stdout output:

[info] nameservers

 

2015-04-15 21:17:20,240 DEBG 'start' stdout output:

nameserver 8.8.8.8

nameserver 8.8.4.4

 

2015-04-15 21:17:20,240 DEBG 'start' stdout output:

--------------------

[info] Starting OpenVPN...

 

2015-04-15 21:17:20,243 DEBG 'start' stdout output:

Wed Apr 15 21:17:20 2015 DEPRECATED OPTION: --tls-remote, please update your configuration

 

2015-04-15 21:17:20,243 DEBG 'start' stdout output:

Wed Apr 15 21:17:20 2015 OpenVPN 2.3.6 x86_64-unknown-linux-gnu [sSL (OpenSSL)] [LZO] [EPOLL] [MH] [iPv6] built on Dec 2 2014

Wed Apr 15 21:17:20 2015 library versions: OpenSSL 1.0.2 22 Jan 2015, LZO 2.09

 

2015-04-15 21:17:20,243 DEBG 'start' stderr output:

Enter Auth Username:

Link to comment

next problem :-)

 

Enter Auth Username:

 

you need to pass it your username and password, you can do this by putting a line in your ovpn file that then calls out to a file containing your username and password for your vpn provider, see here for example:-

 

try this solution

 

add this line to your openvpn clients config file (ovpn file)

 

auth-user-pass login.conf

 

create new file named login.conf and then add your clients username and password e.g.:-

 

fredbloggs
password123456

 

Link to comment

I think I went backwards on that move :'(

 

2015-04-15 22:08:05,168 WARN received SIGTERM indicating exit request

2015-04-15 22:08:05,169 DEBG killing setport (pid 13) with signal SIGTERM

2015-04-15 22:08:05,169 INFO waiting for deluge, setip, start, webui, privoxy, setport to die

2015-04-15 22:08:05,169 DEBG fd 34 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,169 DEBG fd 30 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,169 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 22:08:05,169 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:05,169 DEBG killing privoxy (pid 12) with signal SIGTERM

2015-04-15 22:08:05,169 DEBG fd 25 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,169 DEBG fd 29 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,169 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 22:08:05,169 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:05,169 DEBG killing webui (pid 11) with signal SIGTERM

2015-04-15 22:08:05,170 DEBG fd 24 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,170 DEBG fd 20 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,170 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 22:08:05,170 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:05,170 DEBG killing start (pid 10) with signal SIGTERM

2015-04-15 22:08:05,170 DEBG fd 19 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,170 DEBG fd 15 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,170 INFO stopped: start (terminated by SIGTERM)

2015-04-15 22:08:05,170 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:05,170 DEBG killing setip (pid 9) with signal SIGTERM

2015-04-15 22:08:05,170 DEBG fd 9 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,170 DEBG fd 14 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,170 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 22:08:05,170 INFO reaped unknown pid 320

2015-04-15 22:08:05,170 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:05,170 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 22:08:05,171 DEBG fd 8 closed, stopped monitoring (stderr)>

2015-04-15 22:08:05,171 DEBG fd 6 closed, stopped monitoring (stdout)>

2015-04-15 22:08:05,171 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 22:08:05,171 DEBG received SIGCLD indicating a child quit

2015-04-15 22:08:11,377 CRIT Set uid to user 0

2015-04-15 22:08:11,377 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 22:08:11,381 INFO supervisord started with pid 1

2015-04-15 22:08:12,383 INFO spawned: 'deluge' with pid 8

2015-04-15 22:08:12,384 INFO spawned: 'setip' with pid 9

2015-04-15 22:08:12,385 INFO spawned: 'start' with pid 10

2015-04-15 22:08:12,387 INFO spawned: 'webui' with pid 11

2015-04-15 22:08:12,388 INFO spawned: 'privoxy' with pid 12

2015-04-15 22:08:12,389 INFO spawned: 'setport' with pid 13

2015-04-15 22:08:12,417 DEBG 'start' stdout output:

[info] VPN provider defined as custom

 

2015-04-15 22:08:12,417 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:08:12,417 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:08:12,417 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:08:12,417 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:08:12,420 DEBG 'start' stderr output:

grep: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:12,444 DEBG 'start' stderr output:

sed: can't read /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:12,447 DEBG 'start' stderr output:

grep: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:12,450 DEBG 'start' stderr output:

sed: can't read /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:12,451 DEBG 'start' stderr output:

cat: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:12,455 DEBG 'start' stderr output:

cat: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:08:13,430 DEBG 'start' stdout output:

[info] ip route

 

2015-04-15 22:08:13,430 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 22:08:13,430 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 22:08:13,431 DEBG 'start' stdout output:

default via 172.17.42.1 dev eth0

8.8.4.4 via 172.17.42.1 dev eth0

8.8.8.8 via 172.17.42.1 dev eth0

 

2015-04-15 22:08:13,431 DEBG 'start' stdout output:

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.10

173.245.0.0/16 via 172.17.42.1 dev eth0

--------------------

 

2015-04-15 22:08:13,432 DEBG 'start' stderr output:

iptables v1.4.21: unknown protocol "--sport" specified

Try `iptables -h' or 'iptables --help' for more information.

 

2015-04-15 22:08:13,437 DEBG 'start' stderr output:

iptables v1.4.21: unknown protocol "--dport" specified

Try `iptables -h' or 'iptables --help' for more information.

 

2015-04-15 22:08:13,442 DEBG 'start' stdout output:

[info] iptables

 

2015-04-15 22:08:13,443 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -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 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -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 -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-04-15 22:08:13,443 DEBG 'start' stdout output:

--------------------

 

2015-04-15 22:08:13,443 DEBG 'start' stdout output:

[info] nameservers

 

2015-04-15 22:08:13,443 DEBG 'start' stdout output:

nameserver 8.8.8.8

nameserver 8.8.4.4

 

2015-04-15 22:08:13,444 DEBG 'start' stdout output:

--------------------

[info] Starting OpenVPN...

 

2015-04-15 22:08:13,445 DEBG 'start' stdout output:

Options error: In [CMD-LINE]:1: Error opening configuration file: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn

Use --help for more information.

 

2015-04-15 22:08:13,445 DEBG fd 15 closed, stopped monitoring (stdout)>

2015-04-15 22:08:13,445 DEBG fd 19 closed, stopped monitoring (stderr)>

2015-04-15 22:08:13,445 INFO exited: start (exit status 1; not expected)

2015-04-15 22:08:13,446 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,167 WARN received SIGTERM indicating exit request

2015-04-15 22:19:25,167 DEBG killing setport (pid 13) with signal SIGTERM

2015-04-15 22:19:25,167 INFO waiting for deluge, setip, webui, privoxy, setport to die

2015-04-15 22:19:25,167 DEBG fd 34 closed, stopped monitoring (stderr)>

2015-04-15 22:19:25,167 DEBG fd 30 closed, stopped monitoring (stdout)>

2015-04-15 22:19:25,167 INFO stopped: setport (terminated by SIGTERM)

2015-04-15 22:19:25,167 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,167 DEBG killing privoxy (pid 12) with signal SIGTERM

2015-04-15 22:19:25,167 DEBG fd 25 closed, stopped monitoring (stdout)>

2015-04-15 22:19:25,167 DEBG fd 29 closed, stopped monitoring (stderr)>

2015-04-15 22:19:25,167 INFO stopped: privoxy (terminated by SIGTERM)

2015-04-15 22:19:25,167 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,167 DEBG killing webui (pid 11) with signal SIGTERM

2015-04-15 22:19:25,168 DEBG fd 24 closed, stopped monitoring (stderr)>

2015-04-15 22:19:25,168 DEBG fd 20 closed, stopped monitoring (stdout)>

2015-04-15 22:19:25,168 INFO stopped: webui (terminated by SIGTERM)

2015-04-15 22:19:25,168 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,220 INFO reaped unknown pid 32193

2015-04-15 22:19:25,220 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,220 DEBG killing setip (pid 9) with signal SIGTERM

2015-04-15 22:19:25,220 DEBG fd 9 closed, stopped monitoring (stdout)>

2015-04-15 22:19:25,220 DEBG fd 14 closed, stopped monitoring (stderr)>

2015-04-15 22:19:25,220 INFO stopped: setip (terminated by SIGTERM)

2015-04-15 22:19:25,220 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:25,220 DEBG killing deluge (pid 8) with signal SIGTERM

2015-04-15 22:19:25,221 DEBG fd 8 closed, stopped monitoring (stderr)>

2015-04-15 22:19:25,221 DEBG fd 6 closed, stopped monitoring (stdout)>

2015-04-15 22:19:25,221 INFO stopped: deluge (terminated by SIGTERM)

2015-04-15 22:19:25,221 DEBG received SIGCLD indicating a child quit

2015-04-15 22:19:32,543 CRIT Set uid to user 0

2015-04-15 22:19:32,543 WARN Included extra file "/etc/supervisor/conf.d/delugevpn.conf" during parsing

2015-04-15 22:19:32,546 INFO supervisord started with pid 1

2015-04-15 22:19:33,546 INFO spawned: 'deluge' with pid 8

2015-04-15 22:19:33,547 INFO spawned: 'setip' with pid 9

2015-04-15 22:19:33,547 INFO spawned: 'start' with pid 10

2015-04-15 22:19:33,548 INFO spawned: 'webui' with pid 11

2015-04-15 22:19:33,549 INFO spawned: 'privoxy' with pid 12

2015-04-15 22:19:33,549 INFO spawned: 'setport' with pid 13

2015-04-15 22:19:33,564 DEBG 'start' stdout output:

[info] VPN provider defined as custom

 

2015-04-15 22:19:33,564 INFO success: setip entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:19:33,564 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:19:33,564 INFO success: privoxy entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:19:33,564 INFO success: setport entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)

2015-04-15 22:19:33,565 DEBG 'start' stderr output:

grep: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:33,567 DEBG 'start' stderr output:

sed: can't read /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:33,568 DEBG 'start' stderr output:

grep: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:33,570 DEBG 'start' stderr output:

sed: can't read /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:33,570 DEBG 'start' stderr output:

cat: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:33,572 DEBG 'start' stderr output:

cat: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn: No such file or directory

 

2015-04-15 22:19:34,573 INFO success: deluge entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 22:19:34,574 INFO success: webui entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2015-04-15 22:19:34,716 DEBG 'start' stdout output:

[info] ip route

 

2015-04-15 22:19:34,717 DEBG 'start' stdout output:

default via 172.17.42.1 dev eth0

8.8.4.4 via 172.17.42.1 dev eth0

8.8.8.8 via 172.17.42.1 dev eth0

 

2015-04-15 22:19:34,717 DEBG 'start' stdout output:

172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.11

173.245.0.0/16 via 172.17.42.1 dev eth0

--------------------

 

2015-04-15 22:19:34,718 DEBG 'start' stderr output:

iptables v1.4.21: unknown protocol "--sport" specified

Try `iptables -h' or 'iptables --help' for more information.

 

2015-04-15 22:19:34,723 DEBG 'start' stderr output:

iptables v1.4.21: unknown protocol "--dport" specified

Try `iptables -h' or 'iptables --help' for more information.

 

2015-04-15 22:19:34,729 DEBG 'start' stdout output:

[info] iptables

 

2015-04-15 22:19:34,730 DEBG 'start' stdout output:

-P INPUT DROP

-P FORWARD ACCEPT

-P OUTPUT DROP

-A INPUT -i tun0 -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 -i eth0 -p tcp -m tcp --dport 8118 -j ACCEPT

-A INPUT -i eth0 -p tcp -m tcp --sport 8118 -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 -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-04-15 22:19:34,731 DEBG 'start' stdout output:

--------------------

 

2015-04-15 22:19:34,731 DEBG 'start' stdout output:

[info] nameservers

 

2015-04-15 22:19:34,732 DEBG 'start' stdout output:

nameserver 8.8.8.8

nameserver 8.8.4.4

 

2015-04-15 22:19:34,732 DEBG 'start' stdout output:

--------------------

[info] Starting OpenVPN...

 

2015-04-15 22:19:34,734 DEBG 'start' stdout output:

Options error: In [CMD-LINE]:1: Error opening configuration file: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

/config/openvpn/._ipvanish-AU-Sydney-syd-a03.ovpn

Use --help for more information.

 

2015-04-15 22:19:34,734 DEBG fd 15 closed, stopped monitoring (stdout)>

2015-04-15 22:19:34,734 DEBG fd 19 closed, stopped monitoring (stderr)>

2015-04-15 22:19:34,734 INFO exited: start (exit status 1; not expected)

2015-04-15 22:19:34,734 DEBG received SIGCLD indicating a child quit

Link to comment

this is now the issue:-

 

2015-04-15 22:19:34,734 DEBG 'start' stdout output:
Options error: In [CMD-LINE]:1: Error opening configuration file: /config/openvpn/ipvanish-AU-Sydney-syd-a03.ovpn

 

so whatever you specifed at line 1 of the ovpn file is causing an issue, if line 1 is the newly inserted "auth-user-pass login.conf" line then try moving this line to the last line in the file, save and restart the docker

Link to comment
Guest
This topic is now closed to further replies.