Deluge Forum

Posted: **Thu Mar 26, 2015 4:28 pm**

Hi Folks.

I´ve been using Deluge for a long time now.
Lately, a friend wanted to join in on the fun, so i got him access - but he flooded it with torrents and i was annoyed.
So i wanted to create a second instance of deluge(d and -web) for him to use on that machine.

So i picked me another user, and wanted to start the second deamon:

Code: Select all

deluged -d -p 58848 -L info -c /home/janus/.config/deluge

Only log output i get is:

Code: Select all

[INFO    ] 17:13:13 configmanager:70 Setting config directory to: /home/janus/.config/deluge
[INFO    ] 17:13:13 daemon:124 Deluge daemon 1.3.10
[INFO    ] 17:13:13 configmanager:70 Setting config directory to: /home/janus/.config/deluge
[INFO    ] 17:13:13 core:80 Starting libtorrent 0.15.10.0 session..
[INFO    ] 17:13:13 rpcserver:367 Starting DelugeRPC server localhost:58848
[INFO    ] 17:13:13 rpcserver:375 Daemon already running or port not available..
[ERROR   ] 17:13:13 rpcserver:376 [('PEM routines', 'PEM_read_bio', 'no start line'), ('SSL routines', 'SSL_CTX_use_certificate_file', 'PEM lib')]

I think the problem lies somewhere with "[INFO ] 17:13:13 rpcserver:375 Daemon already running or port not available..".
So the port is not used, i looked that up and even changed it to some others. So i guess its about the deamon.

I have looked that up also, most threads come to the conclusion, that the config file is not writable or something similar.
The file is writable. The whole directory is writable. So im breaking up this new thread, because i dont seem to get it to work with what i found.

By the way: The second web-interface starts up smoothly after creating the folders it needed.
Just when i want to connect to the other daemon it just will show it as offline. Which seems logically, since its not running.
Im running a debian machine.

Any help or links i may have overlooked would be very appreciated.
Thank you in advance.

Posted: **Fri Apr 10, 2015 3:07 pm**

I have two instances working on Ubuntu 14.04. Here's how I do it. Not sure if it is exactly what you are looking for:

1. Set up first deluge daemon using these steps:
http://dev.deluge-torrent.org/wiki/User ... buntuInitd
For this, I left the /etc/init.d/ file alone and just modified the /etc/default file per the instructions

2. For the second server, do the same thing, but make separate files. So in /etc/init.d, you may have deluge-daemon and deluge-daemon-friend. Same thing in /etc/default. I have a seperate linux user for each daemon, like in your case, so be sure to update the files in /etc/default

3. In at least one of the /etc/init.d/ files, you will need to change a few things. Near the top, you should see this:

Code: Select all

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DESC="Deluge Daemon"
NAME1="deluged"
NAME2="deluge"
DAEMON1=/usr/bin/deluged
DAEMON1_ARGS="-d"             # Consult `man deluged` for more options
DAEMON2=/usr/bin/deluge-web
DAEMON2_ARGS=""               # Consult `man deluge-web` for more options
PIDFILE1=/var/run/$NAME1.pid
PIDFILE2=/var/run/$NAME2.pid
UMASK=022                     # Change this to 0 if running deluged as its own user
PKGNAME=deluge-daemon
SCRIPTNAME=/etc/init.d/$PKGNAME

You will need to change NAME1, NAME2, and PKGNAME to something else, so that they are different between the two server files. I am not sure if PKGNAME needs to have the same name as the script file, but that's what I did.
So

Code: Select all

...
NAME1="deluged-friend"
NAME2="deluge-friend"
...
PKGNAME=deluge-daemon-friend
...

4. Make sure each daemon is on a different port. So I left my default one at 58846, and I set my auxiliary one to 58847. If you are using WebUI, you will want those to have different ports as well.

Hope this helps. Let me know if you have any questions about my setup.

Cory

Deluge Forum

Deluge 1.3.10 deamon, two instances, second one wont start.

Deluge 1.3.10 deamon, two instances, second one wont start.

Re: Deluge 1.3.10 deamon, two instances, second one wont sta