gtkui fail to connect to daemon

[Lukos]

Connecting to the daemon from deluge-gtk is not working, it look like deluge manage to connect to deluged but then immediately close the connection. It's possible to start the daemon but after deluge fail to connect does the gtkui fail to register that deluged is running, trying to start deluged again will cause the current deluged to hang, (isn't killed by 'kill $(pidof -x deluged)'). Deleting 'gtkui.conf' make it possible to run deluge as normal again, probably because it then uses 'classic mode'. When deluge fail to connect to the daemon, does the gui fail to register that any torrents are present, settings can't be edited, torrents can't be added.

Code: Select all

deluge --version
deluge: 1.3.3
libtorrent: 0.15.6.0

deluge log

Code: Select all

[INFO    ] 10:34:58 client:221 Connecting to daemon at 127.0.0.1:58846..
[INFO    ] 10:34:58 client:125 Connected to daemon at 127.0.0.1:58846..
[DEBUG   ] 10:34:58 connectionmanager:360 Status: Uppkopplad
[INFO    ] 10:34:58 client:228 Connection lost to daemon at 127.0.0.1:58846 reason: Connection was closed cleanly.
[INFO    ] 10:35:01 client:221 Connecting to daemon at 127.0.0.1:58846..
[DEBUG   ] 10:35:01 config:216 Setting 'hosts' to [] of <type 'list'>
[DEBUG   ] 10:35:01 config:423 Saving new config file /home/ubuntu/.config/deluge/hostlist.conf.1.2.new
[DEBUG   ] 10:35:01 config:436 Backing up old config file to /home/ubuntu/.config/deluge/hostlist.conf.1.2~
[DEBUG   ] 10:35:01 config:444 Moving new config file /home/ubuntu/.config/deluge/hostlist.conf.1.2.new to /home/ubuntu/.config/deluge/hostlist.conf.1.2..
[INFO    ] 10:35:01 client:125 Connected to daemon at 127.0.0.1:58846..
[DEBUG   ] 10:35:01 pluginmanager:88 Core has these plugins enabled: ('Blocklist',)
[DEBUG   ] 10:35:01 pluginbase:62 GtkPlugin initialized..
[DEBUG   ] 10:35:01 gtkui:48 Blocklist GtkUI enable..
[DEBUG   ] 10:35:01 pluginmanagerbase:156 Adding Blocklist to enabled_plugins list in config
[INFO    ] 10:35:01 pluginmanagerbase:158 Plugin Blocklist enabled..
[DEBUG   ] 10:35:02 config:423 Saving new config file /home/ubuntu/.config/deluge/gtkui.conf.new
[DEBUG   ] 10:35:02 config:436 Backing up old config file to /home/ubuntu/.config/deluge/gtkui.conf~
[DEBUG   ] 10:35:02 config:444 Moving new config file /home/ubuntu/.config/deluge/gtkui.conf.new to /home/ubuntu/.config/deluge/gtkui.conf..
[DEBUG   ] 10:35:07 torrentview:512 on_button_press_event
[DEBUG   ] 10:35:07 gtkui:272 sent: 1.9 Kb recv: 1.5 Mb
[DEBUG   ] 10:35:07 gtkui:280 sent rate: 0.0 KiB/s recv rate: 0.0 KiB/s
[DEBUG   ] 10:35:08 menubar:259 on_menuitem_quit_activate
[INFO    ] 10:35:08 client:228 Connection lost to daemon at 127.0.0.1:58846 reason: Connection to the other side was lost in a non-clean fashion: Connection lost.

deluged log

Code: Select all

[INFO    ] 10:34:58 rpcserver:203 Deluge Client connection made from: 127.0.0.1:34109
[INFO    ] 10:34:58 rpcserver:223 Deluge client disconnected: Connection was closed cleanly.
[INFO    ] 10:35:01 rpcserver:203 Deluge Client connection made from: 127.0.0.1:34110
[INFO    ] 10:35:08 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion.

[Cas]

Is the deluged local or remote? Can you try with a new config using '-c' parameter for both client and daemon.

[Lukos]

Is the deluged local or remote? Can you try with a new config using '-c' parameter for both client and daemon.

It's local, I don't think it's related to iptables because it's loopback interface. Deluge can work for a few times then suddenly out of the blue does it stop working and never work again until config files are removed, but a torrent client that can't save settings doesn't seem useful.