Deluge Forum

Hello All,

I've recently been experimenting with setting up a raspberry pi to run crashplan and deluged, both headless. The short version is there's a reason people don't use SD cards as disk drives for real applications but that's not relevant to this forum.

So I did it again using a Mac Mini (G4) running Ubuntu PPC Server. By then I'd had several experiences with deluged installing just fine and running great from the web UI, but got a red dot from the remote client no matter what I did. Ended up uninstalling and reinstalling and it worked. in fact, I've had three or four experiences now where I ended up reinstalling deluged again. In fact, I've been through the headless setup so many times I can do it without needing documentation.

Then I tried also running a TOR middle relay. Got that set up with little trouble but when I was done my deluged stopped working. In a nutshell, I can add a torrent just fine via the client or the web UI, and it just sits there forever at 0%.

Scratch that. I added a torrent from the web UI and it's running. So it looks like I can add a torrent from the web UI but not the thin client. FWIW, I touch the headless server from two clients, one running Windows 7 and the other Mint/Ubuntu, with the same results.

So the point of this ramble is, what could make it so I can do everything OK from the thin client except add a torrent?

What version of deluge are you using on clients/server?

You should not need to reinstall deluge at all. The only files that matter are in the config directory, which you can remove/move to reset to defaults.

Enabling logging for deluged might show some errors.

deluged 1.3.5 running headless on Ubuntu 12.10 server PPC

deluge 1.3.5 on Mint 14

Found a clue on my earlier red dot problems when I started noodling with my /etc/init.d/deluge-daemon script to bump up logging. The version I took from the howto had only the -d argument included when launching the daemon. Found another version that included -l and the name of the log file and a flag for all events warning or worse. Changed that to info.

But the longer version also included a "-c /var/lib/deluge" flag in the arguments variable. Running deluged --help tells me this sets the config folder. It also results in a red dot from the thin client. But if I remove it I can connect. But isn't the default /var/lib/deluge anyway?

So I'm running with the arguments "-d -l /var/log/deluge.log -L info" and everything seems to be OK. But added torrents just sit there. The log shows them being added. But hours later there's no change.

Change the log level to debug?

Also, deluged --help also says the -d argument makes it NOT run as a daemon. Don't I want it to be running as a daemon?

You are editing the wrong config for the user running deluged in the init. The config you need to edit is in /var/lib/deluge and put that option back into the init script.

The init script uses start-stop-daemon command which controls daemonizing the process so when running deluged from start-stop-daemon we don't want it to fork.

-d makes sense. And the red dot makes sense, with the -c I was looking for an auth file other than the one created when I launched deluged as the deluge user.

Logging is now at debug, which doesn't appear to be any more verbose than info. I can see the torrent being added from the web interface or the client. Then nothing else happens for hours or days.

Thought I might have a port forwarding problem but if I try clearing all my existing upnp entries I can see new ones being created (I'll worry about dialing down security after I'm running). On that note, the "test" button on the network settings has always returned a yellow bang, even when torrents are working. Should that be working?

Maybe should change the title of this thread, whatever the problem is it doesn't appear to matter whether I add a torrent from the web or client interface.

In the past I've been in the habit of finding my torrents at kat.ph, and I've associated the .torrent file extension with the deluge client. I find the torrent I'm looking for, click on the file, and the add dialog for the deluge client pops up.

If I add a torrent from another site it appears to launch. But I do like kat, their advertising is marginally less freaky and I can ignore the lame fake adobe pop-up (I'm running linux anyway, most malware won't even stick).

Why would only kat.ph torrents sit idle forever?

Can anyone recommend a one-stop torrent site I might try that might work with my deluge cilent?

Another thing to consider. I'm proxying through btguard. Could that be a cause? But why only for one torrent site?