I have searched around on the forums and see quite a few complaints about the GTK client disconnecting from the daemon. I have the occasional issue as well (maybe once every day or 2) and was wondering if it could be related to using 2 simultaneous GTK clients. Is anyone using more than 1 client at a time and how is it working out for you? The disconnects are random just like everyone else, but I did notice that most times it is 1 client or the other and not both at the same time. Was the system designed to have multiple connections or was it mainly designed just for headless systems so it could be controlled remotely?
My current setup is a desktop running the daemon + client as well as a laptop on wifi running the client.
Both are Windows 7x64.
Both are Deluge 1.3.11 py 2.7
The Daemon is libtorrent 1.0.5 and I have tried some of the other versions as well.
Using LabelPlus and YaRSS2 plugins.
Anyone Using ThinClient With Multiple GTK Interfaces?
Re: Anyone Using ThinClient With Multiple GTK Interfaces?
I've done it a few times... haven't seen any issues, though I normally only have 2 clients connected for a few hours. The first client stays connected 24/7.
Re: Anyone Using ThinClient With Multiple GTK Interfaces?
Thanks for the reply. I enabled debugging right after I posted this and all was well for a couple days and then this happened:lordkappa wrote:I've done it a few times... haven't seen any issues, though I normally only have 2 clients connected for a few hours. The first client stays connected 24/7.
[INFO ] 18:36:54 client:224 Connection lost to daemon at 192.168.1.100:58846 reason: Connection was closed cleanly.
I haven't enabled debug on the daemon yet, so maybe that will yield more info.