I have been having this issue every time I reboot the server or restart rtorrent. If I rehash all my torrents (over 100+) sometimes it will work sometimes my torrents stay in error status. I’ve verified DNS, the server is able to resolve every single tracker without issue. So it brings me to QB and the compiled version of rtorrent that QB is installing. Is QB installing rtorrent that has libcurl compiled with c-ares? Because this looks to be my problem and I have not found any information on your site that shows what QB is actually doing.
The script simply grabs version available at https://rakshasa.github.io/rtorrent/
libcurl >= 7.12.0
Am I the only one having this issue? There has to be others that are having the same problem with QB rtorrent.
QuickBox is not altering rtorrent. We simply pull it from source
Then what is different or what could be possibly causing this issue?
So I fixed my issue. It was exactly what was described in that link. I built c-ares and installed the latest version (1.12.0), then I rebuilt curl with the latest version(7.54.0) and enabled c-ares support. Instantly rtorrent started working again.
EDIT: Spoke too soon. I rebooted and I’m back to the same problem.
What is in your
you should remove all but the
126.96.36.199 and the
I agree, but I don’t think that’s the root cause.
Do you have IPv6 enabled? It looks like it from your resolv.conf. Try disabling IPv6(and not just in the resolv.conf).
Yea disabled ipv6, same thing.
I can do DNS queries all day long. And yea… I doubt all the private trackers are broke.
well if google was down then i would say that it was the server the only other thing is check you host file.
Only entries in my hosts file is my IPv4 IP, local host and all the ‘Blocked Public Tracker’ info that QB adds.
remove the blocks and see if your things work then.
Nope same issue.
I’m still convinced this is a curl or libcurl problem.
so I apt-get remove curl libcurl4-openssl and reinstalled and it’s working again. I’m afraid to reboot.
It’s possible your
libcurl dependencies had corrupted somehow, although, this is no fault of QuickBox as this issue isn’t being raised elsewhere. I have known a couple of server installs that I have helped with in the past where a few dependencies were corrupted (usually through interrupted
apt update and/or
apt upgrade). Those however, caused completely different issues wherein it affected pulling the updates via
git for QuickBox. I would say you can reboot, although, in most server instances there shouldn’t be need to reboot as it rarely fixes a problem in linux… and when it does… it’s a fluke.