Can No Longer Connect to Running Daemon

[btr74]

After upgrading to deluge 1.3.12-1 and Arch 4.2.1-1 and restarting my machine, I can't connect to my running daemon anymore.

systemctl status deluged:

Code: Select all

$ systemctl status deluged
● deluged.service - Deluge Daemon
   Loaded: loaded (/usr/lib/systemd/system/deluged.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2015-09-29 18:18:56 EDT; 17min ago
 Main PID: 285 (deluged)
   CGroup: /system.slice/deluged.service
           └─285 /usr/bin/python2 /usr/bin/deluged -d

and ps aux | grep deluge:

Code: Select all

deluge     285  0.4  0.8 503268 65368 ?        Ssl  18:18   0:08 /usr/bin/python2 /usr/bin/deluged -d
deluge     288  0.3  0.7 311032 59876 ?        Ssl  18:18   0:07 /usr/bin/python2 /usr/bin/deluge-web

both show that my daemon is running, but my clients (remote GTK and web-ui) both show it as offline.

Through deluge-console -c /etc/deluge I get:

Code: Select all

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

nmap shows 127.0.0.1:58846 (and localhost:58846) as open.

in /etc/deluge/auth:

Code: Select all

1 localclient:9932c288a7218142385ada73ec4beabab6c9b1c3:10
 2 my username:mypassword:10

daemon.log is empty since I restarted the machine, and the last entry is in daemon.log.1 from just before the the restart and if it's giving me any crucial info, I don't understand it:

Code: Select all

407 [INFO    ] 16:58:49 rpcserver:224 Deluge client disconnected: Connection to
    the other side was lost in a non-clean fashion: Connection lost.
408 [INFO    ] 16:58:49 daemon:187 Waiting for components to shutdown..
409 [INFO    ] 16:58:50 pluginmanagerbase:170 Plugin Execute disabled..
410 [INFO    ] 16:58:50 pluginmanagerbase:170 Plugin Label disabled..
411 [INFO    ] 16:58:50 daemon:187 Waiting for components to shutdown..

I'm at a loss. Can anyone help me to connect to my daemon again? Thanks.

[Cas]

Are you sure the daemon is using /etc/deluge config location?

[btr74]

Thank you, Cas. I have updated my service config files with:

Code: Select all

-c /etc/deluge

and after reloading the services, things are working splendidly again. Your advice is much appreciated!