Opened 9 years ago

Closed 9 years ago

Last modified 6 years ago

#2813 closed bug (Fixed)

Connection Manager Showing Daemon Offline On First Start

Reported by: Doadin Owned by:
Priority: major Milestone: 2.0.0
Component: GTK UI Version: develop
Keywords: Cc:

Description (last modified by Calum)

Start deluged then gtkui and opening the connection manager will say the daemon is offline but if you hit connect then manually close the connection manager it connects fine.

And from there on if you disconnect from daemon or restart it or w.e. as long as you don't restart the gtkui it will see it online but if you close the ui you can still connect like before but it wont say online and you have to manually close the connection manager after hitting connect.(just like the first time)

Change History (7)

comment:1 by Calum, 9 years ago

Description: modified (diff)
Milestone: 2.0.x2.0

comment:2 by Doadin, 9 years ago

A little more info in logs it says

12:22:09.069 [DEBUG   ][deluge.ui.client            :259 ] sslproxy.connect()
12:22:09.069 [INFO    ][twisted                     :154 ] Starting factory <deluge.ui.client.DelugeRPCClientFactory instance at 0x0535A4B8>
12:22:09.085 [INFO    ][deluge.ui.client            :197 ] Connecting to daemon at "127.0.0.1:58846"...
12:22:09.085 [DEBUG   ][deluge.ui.gtkui.connectionmanager:399 ] Status: Offline
12:22:22.882 [DEBUG   ][deluge.ui.client            :259 ] sslproxy.connect()
12:22:22.882 [INFO    ][twisted                     :154 ] Starting factory <deluge.ui.client.DelugeRPCClientFactory instance at 0x0535A940>
12:22:22.882 [INFO    ][deluge.ui.client            :197 ] Connecting to daemon at "127.0.0.1:58846"...
12:23:42.163 [DEBUG   ][deluge.config               :194 ] Setting 'hosts' to [] of <type 'list'>
12:23:42.163 [DEBUG   ][deluge.config               :458 ] Saving new config file C:\Users\doadin\AppData\Roaming\deluge\hostlist.conf.1.2.new
12:23:42.194 [DEBUG   ][deluge.config               :471 ] Backing up old config file to C:\Users\doadin\AppData\Roaming\deluge\hostlist.conf.1.2.bak
12:23:42.194 [DEBUG   ][deluge.config               :479 ] Moving new config file C:\Users\doadin\AppData\Roaming\deluge\hostlist.conf.1.2.new to C:\Users\doadin\AppData\Roaming\deluge\hostlist.conf.1.2..
12:23:42.194 [WARNING ][deluge.ui.client            :201 ] Connection to daemon at "127.0.0.1:58846" failed: User timeout caused connection failure.
12:23:42.194 [DEBUG   ][deluge.ui.client            :556 ] on_connect_fail: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.TimeoutError'>: User timeout caused connection failure.
]
12:23:42.194 [DEBUG   ][deluge.ui.client            :275 ] sslproxy.disconnect()
12:23:42.194 [INFO    ][twisted                     :154 ] Stopping factory <deluge.ui.client.DelugeRPCClientFactory instance at 0x0535A4B8>
12:23:42.194 [WARNING ][deluge.ui.client            :201 ] Connection to daemon at "127.0.0.1:58846" failed: User timeout caused connection failure.
12:23:42.194 [DEBUG   ][deluge.ui.client            :556 ] on_connect_fail: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.TimeoutError'>: User timeout caused connection failure.

However if you just close then reopen connection manager it says:

12:23:43.569 [DEBUG   ][deluge.ui.client            :259 ] sslproxy.connect()
12:23:43.569 [INFO    ][twisted                     :154 ] Starting factory <deluge.ui.client.DelugeRPCClientFactory instance at 0x05352E40>
12:23:43.569 [INFO    ][deluge.ui.client            :197 ] Connecting to daemon at "127.0.0.1:58846"...
12:23:43.569 [DEBUG   ][deluge.ui.gtkui.connectionmanager:399 ] Status: Offline
12:23:43.569 [INFO    ][deluge.ui.client            :85  ] Connected to daemon at 127.0.0.1:58846..
12:23:43.569 [DEBUG   ][deluge.ui.client            :362 ] __on_connect called
12:23:43.663 [DEBUG   ][deluge.ui.client            :366 ] Got info from daemon: 2.0.0.dev641
12:23:43.663 [DEBUG   ][deluge.ui.client            :552 ] on_connected. Daemon version: 2.0.0.dev641

comment:3 by Doadin, 9 years ago

Sorry for the spam a little here but ive also noticed that no matter what order you start the ui or daemon in or if you have the connection manager open, if you set the conncection manager to not open at startup then manually open it at any time before or after starting the daemon doesnt matter itll work as intended.

Incase its releated this is built with twisted 15.4.

Version 1, edited 9 years ago by Doadin (previous) (next) (diff)

comment:4 by Doadin, 9 years ago

ok i found it https://github.com/doadin/deluge/commit/058b0e41d22b4f62c3edbcf6069793587d7ff8e9#diff-d0a8a088a0b54771b27593e01610186bR420 this portion(lines 420-435) need to be reverted or fixed in a better way. even in twisted 16.1 this code is needed.(not sure its a twisted bug as noted since it would appear this has been needed since twisted 12 and still needed in twisted 16.1.1)

Last edited 9 years ago by Doadin (previous) (diff)

comment:5 by Calum, 9 years ago

Thanks for tracking down the issue. I have fixed this in develop: [21789e0692d36]

Placing minor reference to old ticket #2148 here.

comment:6 by Calum, 9 years ago

Resolution: Fixed
Status: newclosed

comment:7 by Calum, 6 years ago

Milestone: 2.02.0.0

Milestone renamed

Note: See TracTickets for help on using tickets.