Deluge removing torrents before completion

[RogueElement]

Any luck figuring out possible causes or solutions? In the meantime, I've switched back to using Ktorrent until I can figure out why Deluge is losing my torrents.

[RogueElement]

As i said before we really need logs to determine what is happening. We also need to know whether you are using any plugins and how you have setup Deluge i.e. have you setup deluged or are you simply running as standalone

It's been over 3 months since I provided the logs you asked for, but I haven't had a response. Does anyone know what's going on here??

[gazpachoking]

Looks like a permissions problem with your config folder to me. Make sure the user deluge is running as has read/write permission to the config folder.

[RogueElement]

After getting fed up and frustrated with this problem, I switched back to Ktorrent for a while and only recently decided to give Deluge another try with Ubuntu 10.10. I wiped out the Deluge configuration directory and let Deluge rebuild it. Everything worked fine for a couple of days and then the problems started all over again.

Per previous posts, I assumed this was a permissions problem but when I attempt to change the permissions of the torrents.state.new file, I get an "input/output" error. Apparently there's some sort of file corruption happening--and happening consistently.

I'm using the Ext4 filesystem with full disk allocation. There shouldn't be any type of file corruption, yet there is.

[Corwin]

The most common cause of this problem I've been able to figure out so far is this scenario:

Torrent 1: Ubuntu 10.10
Torrent 2: Ubuntu 10.04

both iso images are in a directory named ubuntu. When the first torrent finishes, deluge copies the entire directory containing BOTH iso images over to the completed directory, even though the second is not finished.

Just recreate the directory in incoming and copy the files back, then under error when you hit resume it will usually continue.

[RogueElement]

The problem for me was corruption of one of the state files. For reasons unknown, the file would become corrupted and instead of dealing with the problem, Deluge would just pretend nothing was wrong and not process the existing torrents. If I manually deleted the corrupted file, Deluge acted as if nothing had happened.

I have no idea what was causing the problem, but I haven't had an issue (or at least noticed one) in a couple of months so I'm assuming it was due to a bug either with Deluge or another package that affected how data was written to the disk.