[SOLVED] Strange behaviour turning daemon on/off with YAST
Posted: Fri Sep 27, 2013 6:17 pm
I've recently migrated to Deluge from utorrent. One of the reasons I chose Deluge is the daemon/thin-client architecture. I normally run an old desktop as a server, and access it from my laptop.
When I tried to install Deluge from the Downloads area, I got an error (my OS is Opensuse 12.3); however, I was able to install it from an OpenSuse community repository. I started the Deluge daemon with YAST, then tried to open the ui without success. After a bit of googling, I discovered that I also needed to download deluge-gtk. After installing that, I could run Deluge, and I used it for a day or two in "classic" mode.
However, when I tried to change to thin-client mode, and opened the connection manager, I got the red indicator, even on the default localhost daemon. I tried pressing the "Start Daemon" button, but with no effect.
Then, I tried various things with firewalls, port-forwarding and so forth, without success (makes sense as these should not interfere with the localhost). Finally, in desperation, I turned the daemon off in YAST, and surprisingly I was able to start the daemon from Deluge-gtk with the "Start Daemon" button.
To check that this was in fact the problem, I tried enabling the daemon again from YAST and found Deluge had disconnected and the red indicator was back on.
So, Deluge is working fine now, but I'm still curious. Can anyone explain this weird behaviour?
When I tried to install Deluge from the Downloads area, I got an error (my OS is Opensuse 12.3); however, I was able to install it from an OpenSuse community repository. I started the Deluge daemon with YAST, then tried to open the ui without success. After a bit of googling, I discovered that I also needed to download deluge-gtk. After installing that, I could run Deluge, and I used it for a day or two in "classic" mode.
However, when I tried to change to thin-client mode, and opened the connection manager, I got the red indicator, even on the default localhost daemon. I tried pressing the "Start Daemon" button, but with no effect.
Then, I tried various things with firewalls, port-forwarding and so forth, without success (makes sense as these should not interfere with the localhost). Finally, in desperation, I turned the daemon off in YAST, and surprisingly I was able to start the daemon from Deluge-gtk with the "Start Daemon" button.
To check that this was in fact the problem, I tried enabling the daemon again from YAST and found Deluge had disconnected and the red indicator was back on.
So, Deluge is working fine now, but I'm still curious. Can anyone explain this weird behaviour?