SYSTEM account [SOLVED]

[MarkusKramer]

For the benefit of controlling Deluge remotely, it needs to run under the SYSTEM account.

The SYSTEM account (C:\Windows\System32\config\systemprofile) is not the administrator account (C:\Users\Administrator).
Administrator can fully operate Deluge.
SYSTEM cannot, in particular not the daemon (deluged.exe).


I opened a shell as SYSTEM (run "PSEXEC -i -s CMD" as administrator)

SYSTEM> deluge-1.3.10-win32-setup.exe ---> Success (but AppData\Roaming\deluge is missing)

SYSTEM> deluged.exe ---> FAILURE (no error message, no event log)

Administrator> deluged.exe ---> Success

SYSTEM> deluge.exe ---> Only classic mode, cannot connect to deluged

SYSTEM> deluge-console info

[ERROR ] 09:16:46 client:391 RPCError Message Received!
--------------------------------------------------------------------------------
RPCRequest: daemon.login(localclient, 0d36d4d609acdd8dfad33cf24de573f0797dd24f)
--------------------------------------------------------------------------------
File "deluge\core\rpcserver.py", line 259, in dispatch
File "deluge\core\authmanager.py", line 93, in authorize

BadLoginError: Password does not match
--------------------------------------------------------------------------------
Failed to connect to 127.0.0.1:58846 with reason: Password does not match

There is a folder C:\Users\Administrator\AppData\Roaming\deluge
There is no such folder in C:\Windows\System32\config\systemprofile\AppData\Roaming


How can SYSTEM start (and connect to) deluged?
Why is the AppData\Roaming\deluge folder missing?
Is SYSTEM intended to run Deluge?
Does the solution involves configuration or programming?

[MarkusKramer]

From the description at
http://dev.deluge-torrent.org/wiki/UserGuide/Service
one can build a deluged run by SYSTEM (local admin).

For a deluge-console run by SYSTEM I have no idea.

[Cas]

http://dev.deluge-torrent.org/wiki/User ... alUIClient

[MarkusKramer]

Hi Cas,
deluge-console happily contacts deluged, both run as SYSTEM (nt authority\system).
Nice, but configuration must be sorted out.

I created a deluged service with nssm.
Arguments: -c C:\Windows\System32\config\systemprofile\AppData\Roaming\deluge
(Looks complicated, but is %APPDATA%\deluge)
This folder remains empty
I found the folder here:
c:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\deluge\

`deluge-console add lubuntu.iso.torrent` works and saves to
c:\Windows\SysWOW64\config\systemprofile\Downloads\

Nice, but I cannot change the configuration.

`deluge-console info` says
download_location: C:\Windows\system32\config\systemprofile\Downloads

I edited download_location in
c:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\deluge\core.conf
but my changes are ignored.

I entered the SysWOW64 path in the -c setting of nssm, restarted the service.
No change.

Is this only the configuration of deluged?
Where does deluge-console take its configuration from?

Have you run deluge-console as SYSTEM before?

[Cas]

It sounds like you have two deluged running (with different config locations)

[MarkusKramer]

Thank you - today changing the configuration is working like a charm.

Problem was: I did not stopped the daemon *before* editing core.conf - I was not aware that stopping writes back core.conf.