Custom Query (2449 matches)

Delude was up and running with 2 torrents seeding (from Ilovetorrents) and uploading intermitently, these have been running for over 24hrs. When trying to load another torrent the client crashed,the only thing you could do with it was minimise/restore. The only way I could then close Deluge was to "end process" via the Task Manager! Upon reloading the new torrent the client restarted ok,accepted the torrent and resumed the original 2 torrents. This has happened several times.

XP pro Sp2, 512 ram,celeron 2.6gz overclocked to 3.2gz,128gb Nvidia Geforce FX5900XT. Hope this is enough info.

If I close Deluge (1.3.6) then start Deluge again (Full close, ie: File-->Close) when I restart Deluge any torrents which have not completed will attempt to resume. Most often, any resumed torrents will go to "Error" status. Details say "Input/output error". Doing a "force recheck" on the torrent fixes the error status and "pauses" the torrent at the end of rechecking, after that I can resume downloading the torrent without problems but it is very annoying since I have to almost always close deluge before big downloads are finished, and the longer the download, the bigger the time to wait for the rechecking to be done. Given this I can't just start deluge and leave... I have to wait to see if the error happens, then recheck, then wait for the recheck to finish and then click resume the download.

I mostly download files to an external NTFS hdd but it also happens on ext4 because at first I thought that was the issue and downloaded a couple of files to ext4 and the error still occurred.

Someone suggested to put downloads in full allocation mode instead of compact allocation as a workaround on ticket: ​http://dev.deluge-torrent.org/ticket/858 but I haven't tested it yet.

I am using Deluge 1.3.5 with libtorrent 0.15.9.0 for the gtk frontend as well as for the server backend.

If I use ssh -L 58846:localhost:58846 server to forward the deluge port and connect to the server's deluged process with the gtk frontend, and then try to set the download directory, it lets me browse the directory tree on the client, not on the server.

Worse, it the download directory that has been set does not exist on the client, the client changes it.