use deluge-console -c ~/some/folder/ and set variables like paths, disable dht, allow remote connections,etc.
pkill deluged. I try to load deluge with the command above. No luck. I check the config dir and no core.conf is there.
If I change up the port, then pkill deluged, I get a core conf where it should be. I try loading deluged with deluged -c ~/some/folder/ and it doesn't start.
I try changing the port again and get it to launch (confirmed with ps aux or ps aux | grep 'deluge') but yet the deluge-console -c ~/some/folder/ wont launch a console connected to a daemon.
If I try to connect manually I get errors like invalid user or invalid password.
Last edited by Cas on Mon Oct 15, 2012 11:26 pm, edited 1 time in total.
Reason:please make posts readable by using formatting
Sorry 1.3.5. I would like to use nightly builds but seems that PPA was never used, and I prefer not to build from source.
As for the log, nothing at all. Maybe I need to bump up the logging level? Not sure if it matters but I specified a specific location to put the log rather then the default.
http://pastebin.com/R4530ZWN
The box has 4 different ips. Three are running from virtual interfaces. I changed some ip's and such to make it a bit more anonymous. Log level was set to debug. I can turn it down if needed.
Oh and I have a fully working daemon on the server already, but I need to change my set up. I need to run a few daemons under one user. I launched the original working daemon, and tried deluge-console c- /full/path/.config with my original daemon and new daemon running I get this error:
[ERROR ] 23:15:38 client:395 RPCError Message Received!
--------------------------------------------------------------------------------
RPCRequest: daemon.login(localclient, 7b7a590bef51256cb95bdb5728e783dc1d3ec478)
--------------------------------------------------------------------------------
File "/usr/lib/python2.7/dist-packages/deluge/core/rpcserver.py", line 259, in dispatch
ret = component.get("AuthManager").authorize(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/deluge/core/authmanager.py", line 93, in authorize
raise BadLoginError("Password does not match")
BadLoginError: Password does not match
--------------------------------------------------------------------------------
Yes I realize it was non-standard ports but if the non-standard daemon port is listed in the conf file, wouldn;t the console pick up on this when doing deluge-console -c ~/some/folder/ ?
Anyways I finally got it. For those with similar needs, try this:
deluged &
It will output something like [12345]
Then: deluged -p 12345 -u 123.4.5.6 and any other options.
deluged-console
connect
config -s daemon_port 1234
exit
pkill deluged
deluged &
deluged -p 7.8.9.1
deluge-console
connect
config -s daemon_port 5678
exit
pkill deluged
and repeat as needed.
Then to launch them, from a standard terminal enter:
deluged -p 1234[enter key]
deluged -p 5678[enter key]
And of course you can add other deluged options as well.