Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

rtorrent injected torrents pause after ~10-20%

See original GitHub issue

I’ve been seeing behavior where torrents injected via rtorrent start checking as they’re injected, but then pause after 10-20% and aren’t able to be checked. If I manually force recheck them the same thing happens. Sometimes when I manually recheck them they make it to 100%, but then when I start them they still end up pausing after a short period. The only thing that’s able to get them to work is to download the .torrents via the rutorrent interface, delete the torrents, and then readd/move/recheck the torrents. Still an improvement over not cross seeding at all, but it’s a bit less automated than I’d like it to be 😃

It sounded somewhat similar to https://github.com/JohnDoee/autotorrent/issues/31, but I wasn’t able to figure out the issue from there. I also found some threads citing autowatch, so I disabled the autotools plugin entirely but that didn’t seem to do it.

I’m using this: https://github.com/crazy-max/docker-rtorrent-rutorrent as my rtorrent/rutorrent setup, so my thought was that it could be an issue on the rtorrent/rutorrent configuration side rather than cross-seed. Does anyone happen to know if https://github.com/crazy-max/docker-rtorrent-rutorrent/blob/master/rootfs/tpls/.rtorrent.rc or https://github.com/crazy-max/docker-rtorrent-rutorrent/blob/master/rootfs/tpls/etc/rtorrent/.rtlocal.rc do anything that would interact weirdly with the method cross-seed uses to inject torrents?

I’m going to continue investigating to see if I can uncover anything - as I said I don’t even know which side the issue is on. If anyone has ideas I’d love to hear them!