Hi all! Just this…I have a remote Deluge server I connect to with the Deluge thin client. The Deluge server is connected to all the -arr servers, which add the torrents to download. However a lot of downloads start crapping out every few hundred MBs. They get to speeds of 25MB/s (normal for my current connection), and then shortly after show an error. I do a forced check, and they end up on paused mode. I press play, and after less than ten seconds…error again. It’s a PITA to keep slowly pushing forward these torrents. Any idea what causes this, or how to fix it?
Is it possible you have a faulty disk?
I would second the bad disk. I thought bad permission but since since it seems intermittent, the bad disk is the better guess. It would be good to get more info like what’s it running on, is it an array, etc.
Maybe! I’d start checking dmesg logs and check the smart info provided you do regular tests. Otherwise do some SMART tests and check the results after.
it wouldn’t be bad to know what the error says
If you’re not working over a VPN, it may be your ISP trying to stop you from torrenting. Otherwise I have no guesses unfortunately.
Sadly I live in Asia where they couldn’t care less about what I download. Torrent is not blocked, and I download consistently at very high speeds.
…how can I see that? The torrent just goes “error” on the UI. Not sure where it saves logs on my container, or what to look for specifically.
Deleted
I would look into either a permissions issue (the daemon having no permissions to write in your target folder), or a faulty disk issue. I’ve had a similar issue in the past and the former was the cause.
Your description seems coherent with the torrent downloading normally until the memory buffer is full, and then failing when the data is attempted to be written to the disk.
Thanks. Your last sentence really makes sense. It’s writing to a NAS, and sometimes the download speed is clearly higher then the NAS max write speed.
have you updated deluge to the latest? many trackers block older versions so you have to keep it current.
Hmmm it’s on 2.0.3. Took me some fiddling back in the day updating from v1.x to 2.x…But there’s no further versions correct?
2.1.1 is the latest. I think that should be your next step. not sure how you installed it, but the process should be quick be it in windows. Docker or Linux.
In Linux with headless+specific libraries dependencies + remote client + remote client dependencies last time the upgrade was a royal pain in the butt… But I’ll look into it
