Hi All,
Firstly - I wanted to report this issue on the trac system but I cannot register. I enter my details, click register and then get told that they system thinks I may be spam and am presented with a captcha. There is no submit button, but I enter the captcha and hit return on my keyboard, only to be told that i have entered the captcha incorrectly. So I came to the forum instead.
Now to my real issue.
I just started using deluge today. Details:
Client: 1.3.11
libtorrent: 0.16.18.0
Windows 8.1
Using the windows GUI but also have auto add, web console and label plugins enabled.
Deluge picks up torrents that have been put in a black hole folder by SickRage, labels them and puts completed downloads in another folder for SR to then move to my series folder. This works fine.
What is now happening though, is that if I close Deluge for a while, and reopen it, all the incomplete torrents have disappeared.
At first I thought SR was somehow deleting pertinent data when collecting the completed downloads, so I separated all of the folders. In progress goes to D:/downloads, general completed goes to D:/Downloads/Completed and all SR labled (from black hole_ torrents go to D:/TVShows when completed, where SR cuts them out. **A note here, the first time SR took a completed torrent from deluge, deluge didn't complain or lose the torrent, it simply kept trying to seed the non existent file. (so I do not think SR is the cause)
So after splitting the folders to ensure no clashes, I figured I had solved the problem. I opened and closed deluge a few times to ensure the torrents were still there. It was fine and resumed downloading as expected. I then closed deluge for a few hours and after reopening it, all torrents had disappeared again.
To clarify, when I say disappeared, there are no in progress, completed or seeding torrents in the windows gui. Absolutely none. However, the partially completed files are still in D:/Downloads.
Also on the second iteration of this issue occurring, sickrage was completely shut down so I cannot find any reason to suspect that it is the culprit.
How could I go about debugging this?
Thanks
Tarn