Opened 2 weeks ago
Last modified 2 weeks ago
#3648 new bug
[Windows] Deluge daemon does not shutdown
Reported by: | Doadin | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | needs verified |
Component: | Core | Version: | master |
Keywords: | Cc: |
Description (last modified by )
Running in daemon mode from with daemon and gtkui on same machine, going to file > quit and shutdown daemon, GTK-UI closes but daemon does NOT. This is what log with info level shows:
20:08:10.124 [INFO ][deluge.core.rpcserver :1672] Deluge Client connection made from: 127.0.0.1:63465 20:08:10.221 [INFO ][deluge.core.rpcserver :1672] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:08:11.773 [INFO ][deluge.core.rpcserver :1672] Deluge Client connection made from: 127.0.0.1:63473 20:08:30.415 [INFO ][deluge.core.daemon :1672] Deluge daemon shutting down, waiting for components to shutdown... 20:08:30.417 [INFO ][deluge.core.core :1672] Saving the session.state at: C:\Users\joshb\AppData\Roaming\deluge\session.state 20:08:30.681 [INFO ][deluge.core.rpcserver :1672] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:08:59.565 [INFO ][deluge.core.rpcserver :1672] Deluge Client connection made from: 127.0.0.1:63624 20:08:59.644 [INFO ][deluge.core.rpcserver :1672] Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost. 20:09:00.881 [INFO ][deluge.core.rpcserver :1672] Deluge Client connection made from: 127.0.0.1:63632
Since the daemon is still running (process can be seen in task manager) Trying to re-connect gives this:
20:09:01.004 [ERROR ][deluge.core.rpcserver :1672] Deluge client authentication error made from: 127.0.0.1:63632 (Username does not exist)
End task from task manager and restart the process can login etc etc but still won't shutdown.
Note:
See TracTickets
for help on using tickets.