Arch Linux

x-yuri

Member

Registered: 2013-01-06

Posts: 160

deluge-gtk doesn't see running daemon

Hi,

I'm having a bit of a trouble with deluge. I enabled deluged service (systemctl enable deluged) and disabled "Classic mode", so that deluge would start on boot. But now deluge-gtk doesn't see the running daemon, judging from status in Connection Manager. Until I run it from within deluge-gtk. Actually, I'm not even sure if before I run the daemon from deluge-gtk, it seeds/downloads torrents. Is there a way to check it?

To add more details:

$ ps -ef | grep deluge
deluge     487     1  0 09:13 ?        00:00:32 /usr/bin/python2 /usr/bin/deluged -d
yuri      3530  2717  0 10:54 pts/0    00:00:00 grep --color=auto deluge
$ sudo ss -nlp | grep deluge
u_str  LISTEN     0      50     /home/yuri/.config/deluge/ipc/deluge-gtk 259201                 * 0     users:(("deluge-gtk",pid=3727,fd=3))
udp    UNCONN     0      0                      *:54763                 *:*      users:(("deluged",pid=487,fd=22))
udp    UNCONN     0      0                      *:65124                 *:*      users:(("deluged",pid=487,fd=14))
udp    UNCONN     0      0           192.168.0.21:6771                  *:*      users:(("deluged",pid=487,fd=26))
udp    UNCONN     0      0              127.0.0.1:6771                  *:*      users:(("deluged",pid=487,fd=24))
udp    UNCONN     0      0                      *:6771                  *:*      users:(("deluged",pid=487,fd=23))
udp    UNCONN     0      0           192.168.0.21:57988                 *:*      users:(("deluged",pid=487,fd=27))
udp    UNCONN     0      0              127.0.0.1:58373                 *:*      users:(("deluged",pid=487,fd=25))
udp    UNCONN     0      0                     :::65124                :::*      users:(("deluged",pid=487,fd=15))
tcp    LISTEN     0      5                      *:4433                  *:*      users:(("deluged",pid=487,fd=11))
tcp    LISTEN     0      50             127.0.0.1:58846                 *:*      users:(("deluged",pid=487,fd=9))
tcp    LISTEN     0      5                      *:65124                 *:*      users:(("deluged",pid=487,fd=10))
tcp    LISTEN     0      5                     :::4434                 :::*      users:(("deluged",pid=487,fd=13))
tcp    LISTEN     0      5                     :::65124                :::*      users:(("deluged",pid=487,fd=12))

<stop system daemon, start daemon from deluge-gtk>

$ ps -ef | grep deluge
yuri      3727   834  0 10:57 tty1     00:00:02 /usr/bin/python2 /usr/bin/deluge-gtk
yuri      4053     1 35 11:08 ?        00:00:08 /usr/bin/python2 /usr/bin/deluged --port=58846 --config=/home/yuri/.config/deluge
yuri      4074  2717  0 11:08 pts/0    00:00:00 grep --color=auto deluge
$ sudo ss -nlp | grep deluge
u_str  LISTEN     0      50     /home/yuri/.config/deluge/ipc/deluge-gtk 259201                 * 0     users:(("deluge-gtk",pid=3727,fd=3))
udp    UNCONN     0      0                      *:46981                 *:*      users:(("deluged",pid=4053,fd=24))
udp    UNCONN     0      0           192.168.0.21:6771                  *:*      users:(("deluged",pid=4053,fd=29))
udp    UNCONN     0      0              127.0.0.1:6771                  *:*      users:(("deluged",pid=4053,fd=27))
udp    UNCONN     0      0                      *:6771                  *:*      users:(("deluged",pid=4053,fd=25))
udp    UNCONN     0      0                      *:49815                 *:*      users:(("deluged",pid=4053,fd=14))
udp    UNCONN     0      0              127.0.0.1:54349                 *:*      users:(("deluged",pid=4053,fd=28))
udp    UNCONN     0      0           192.168.0.21:60638                 *:*      users:(("deluged",pid=4053,fd=30))
udp    UNCONN     0      0                     :::49815                :::*      users:(("deluged",pid=4053,fd=17))
tcp    LISTEN     0      5                      *:4433                  *:*      users:(("deluged",pid=4053,fd=11))
tcp    LISTEN     0      5                      *:49815                 *:*      users:(("deluged",pid=4053,fd=10))
tcp    LISTEN     0      50             127.0.0.1:58846                 *:*      users:(("deluged",pid=4053,fd=18))
tcp    LISTEN     0      5                     :::4434                 :::*      users:(("deluged",pid=4053,fd=13))
tcp    LISTEN     0      5                     :::49815                :::*      users:(("deluged",pid=4053,fd=12))

Am I doing it wrong? Is there a way to fix it?

bleach

Member

Registered: 2013-07-26

Posts: 264

Re: deluge-gtk doesn't see running daemon

i thinks you have to disable deluge-gtk's daemon and connect to the existing deamon.

its been a while but that is how I remember it.

x-yuri

Member

Registered: 2013-01-06

Posts: 160

Re: deluge-gtk doesn't see running daemon

Which is existing daemon? After I installed deluge, deluged daemon was not enabled. And the daemon didn't start when I ran deluge-gtk. Not that it didn't work. Then I decided to make it start on boot. For that, I disabled "Classic mode" and enabled deluged daemon (systemctl enable deluged). And now if I want to start deluge-gtk, I need to stop the daemon (systemctl stop deluged), so that deluge-gtk would start the daemon its way.

UPD. I've asked the same thing on deluge's forum.

Last edited by x-yuri (2014-10-18 16:24:32)

bleach

Member

Registered: 2013-07-26

Posts: 264

Re: deluge-gtk doesn't see running daemon

deluge-gtk has its own temporary daemon that is what you need to disable. when starting the gtk front end it should have a popup window showing user and port or somthing like that it has been a while I must say yet no one else has posted with current knowledge. the wiki says you need to create a new service and enable/start it. going to classic is disabling daemon mod via gtk interface. the wiki really says all you need arch wiki deluge systemd

edit: one thing you may want to do is make the user the user you are using within the service file which the wiki does suggest.

Last edited by bleach (2014-10-22 17:32:08)