deluge-gtk doesn't see running daemon

General support for problems installing or using Deluge
Post Reply
x-yuri
New User
New User
Posts: 2
Joined: Sat Oct 18, 2014 4:02 pm

deluge-gtk doesn't see running daemon

Post by x-yuri »

Hi,

I installed deluge a while back. But then I decided to make it start on boot. So I disabled "Classic mode" and enabled corresponding daemon (systemctl enable deluged). But now deluge-gtk doesn't recognize the daemon as being running (daemon's status is red in Connection Manager). Every time I want to start deluge-gtk, I need to stop the daemon first (systemctl stop deluged) and start it from Connection Manager in deluge-gtk.

Some more details:

Code: Select all


<after boot>

$ 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))

$ systemctl stop deluged

<start deluged from Connection Manager>

$ 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))
I don't really know what this is supposed to mean. But I hope you do know. Thanks in advance for your replies.

P.S. I'm running Arch Linux, if anything. And just in case here's the corresponding topic on their forum.
Cas
Top Bloke
Top Bloke
Posts: 3679
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: deluge-gtk doesn't see running daemon

Post by Cas »

x-yuri
New User
New User
Posts: 2
Joined: Sat Oct 18, 2014 4:02 pm

Re: deluge-gtk doesn't see running daemon

Post by x-yuri »

So now, after boot deluged daemon (system one, running under deluge account) doesn't seem to use a config file. So it neither seeds torrents, nor downloads them, right?

And I can make deluged daemon use my config, by passing -c ~yuri/.config/deluge. But that might lead to permissions issues, or not?

Also, I can run deluged daemon under my account (systemctl --user). This seems like the best option to me for now. Supposedly, I should pass -d and -c options, port is likely to be 58846 by default.

What do you say?
Sentinel
Member
Member
Posts: 21
Joined: Sun Oct 26, 2008 10:41 pm

Re: deluge-gtk doesn't see running daemon

Post by Sentinel »

I'm having this issue as well. I checked and it's not the different users' config problem. It seems to have been introduced in the latest 1.3.10 client. I see the deluged client listening on the port, and I connect from another machine (which is running the 1.3.6 windows client) but I can't connect on the localhost that's running deluged w/ the 1.3.10 client. I'm on debian, and I've tried various ways of adding the deluged connection - localhost, 127.0.0.1, local IP address, but none of them work.

Any thoughts?
Sentinel
Member
Member
Posts: 21
Joined: Sun Oct 26, 2008 10:41 pm

Re: deluge-gtk doesn't see running daemon

Post by Sentinel »

ottoii
New User
New User
Posts: 5
Joined: Thu May 30, 2013 1:54 am

Re: deluge-gtk doesn't see running daemon

Post by ottoii »

what change i have to do when i self compile? i cant connect anymore to the deamon on the server with the client 1.3.10. What is the reason? I use debian jessie on my computer and debian wheezy on the server. had no error while compile. is there a problem with sslv3 i saw in the patch? thanky for help!
Cas
Top Bloke
Top Bloke
Posts: 3679
Joined: Mon Dec 07, 2009 6:04 am
Location: Scotland

Re: deluge-gtk doesn't see running daemon

Post by Cas »

Here is the patch debian is applying to their package: http://anonscm.debian.org/cgit/collab-m ... 68632b5ab4

I will fix this in our repo soon: http://dev.deluge-torrent.org/ticket/2555
Post Reply