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?
[SOLVED] Strange behaviour turning daemon on/off with YAST
-
- Member
- Posts: 21
- Joined: Fri Sep 27, 2013 5:21 pm
[SOLVED] Strange behaviour turning daemon on/off with YAST
Last edited by Thailandian on Sat Sep 28, 2013 8:22 am, edited 1 time in total.
-
- Member
- Posts: 21
- Joined: Fri Sep 27, 2013 5:21 pm
Re: Strange behaviour turning daemon on/off with YAST
I think I've worked this out myself, and it was a permissions problem. By enabling the daemon from YAST, it started as a root process so Deluge-gtk, which of course is owned by my normal user account, could not access it.
I just tried starting the daemon from a regular console (rather than YAST), and Deluge-gtk opened up with the daemon running and connected.
Hopefully, this may help someone else.
I would like to suggest that the user guide be modified to say:
I just tried starting the daemon from a regular console (rather than YAST), and Deluge-gtk opened up with the daemon running and connected.
Hopefully, this may help someone else.
I would like to suggest that the user guide be modified to say:
I'd be surprised if I'm the first person to have this type of problem. I generally think of daemons as running under root.Start DaemonCode: Select all
deluged #as a normal user