Hi guys! It’s been a long while, and I still struggle with Deluge catching brand new releases of movies that just about everyone’s downloading.
A bit of background, I have 1Gbps connection, and Deluge in headless mode (that’s why I chose Deluge, for headless you get either Deluge or Transmission…AFAIK those are the only two supporting it).
So, whenever my -arr servers catch the latest release of the very latest movie or TV show, Deluge catches it, and faceplants it with a download error immediately. I can either “force check” or “resume”. Either way (doesn’t matter which), it will error again in a second or two. This struggle continues for a while of resume/error/resume, until it finally starts to download a larger chunk…for it to error again a minute or two later, after downloading several hundred MB. And then another section of constant errors. Finally, it will get stuck at the end at 99%, where it really needs a “force check” to find whatever data was corrupted, redownload that, and finish.
Any idea why this happens? Any way to fix/avoid it? I’m not sure deluge is connecting to fake seeders giving it corrupted data and it fails to catch/fix it. Any help would be very welcome. Thanks!
The behavior isn’t normal - Without the error message itself it’s hard to say. You’re not seeing any tracker errors or anything like that within Deluge right?
Otherwise shut down Deluge, enable logging, then re-start it. See “Enable Deluge Logging” in https://deluge-torrent.org/troubleshooting
Maybe you want to set the log level to “error” or “warning”, if those don’t yield anything new then set it to “info” to log whatever error it is.
Also maybe update your post with your OS and Deluge / LibTorrent version.
For what it’s worth in the past I’ve sometimes seen Deluge error on a brand new private tracker torrent, sometimes the private tracker needs a few seconds or a minute to update the tracker and show seeds/etc. - in those random cases Deluge ends up talking to the private tracker before all that & that results in it displaying some error like torrent not found at tracker, I forget exactly what the error was. It’s a bit odd since I’ve never seen rTorrent/ruTorrent have that issue, seemed like a Deluge thing. Been a while since i’ve dealt with that and can’t remember how I fixed it, think it involved having a delay before Deluge attempted to load/start the torrent.
The paid Seedbox providers usually default to rTorrent/ruTorrent for headless torrenting on their Linux based systems. Deluge/Transmission are the alternative clients in those cases.
Nowadays qBittorrent with webui enabled behaves pretty well on a headless system otherwise qbittorrent-nox is also an option.
Thanks…I don’t think think I have considered rTorrent before. But this one doesn’t have a remote GUI client the way deluge and transmission allow their UI to connect to a remote daemon, right?
Regarding all the troubleshooting steps, thanks a lot. I’m going to go about enabling logging by default on the service, which is disabled and definitely doesn’t help. I’m also considering to rebuild the whole thing, since it’s running off of an older Ubuntu 20.04 container. I might as well take the chance to do it on 24.04. We’ll see.
Correct. You’re referring to the thin client, offhand I think it’s just Transmission and Deluge that have that. You don’t need a thin client for a headless torrent client setup, plenty of people do fine with a web ui. But I get it, if you prefer using a thin client then yeah Deluge or Transmission are your options for that.
re: Deluge once you have logging enabled it’ll be easier to troubleshoot things. Always seemed a bit odd that Deluge doesn’t at least enable error/warning logging by default but that’s a Deluge thing.