On 2025-02-10 18:34, Atanas Vladimirov wrote:
Hello misc,

I'm seeking for help on how to debug this issue further. Any help will be greatly appreciated!

For the last few months I started to use torrents on my home-server/router box (last time it was a few years back, dmesg at the end). I started using `qbittorrent-nox` because I really liked the feature to manage it over WebUI.

Something, that I noticed after a while was that some torrents just stall and never start to download while there are peers(seeders) - I'm sure because when I load the torrent file on a Linux machine with `qbittorrent` it start to download immediately.

I lived with that for a while. I tried to change some of the `qbittorrent-nox` settings but without any luck.

While recently I found this thread in ports - https://marc.info/?l=openbsd-ports&m=172825509909069&w=2

The description of the Bug 2 is exactly what I'm experiencing, quoting it here:

Bug 2:
After some uneven time (0-15 minutes), SOME torrents just get Stalled after
downloading (although I think that some never even get started).
I could not find any correlation between settings and whatnot.
The network is not at fault, and neither is the tracker.
Not only has this been tested against different internet accesses and ISPs, it has also been tested with clearnet and I2P, and I2P is anonymous so ISP can't
even figure out if torrenting is happening even if they wanted to.

As you can see there is no any progress on the thread, so I thought that I will just leave the `qbittorrent-nox` client and try another one. So, I chose the `rtorrent` (I recall that I was very happy with it in the past :)

I could say that `rtorrent` behaves a little bit better - the torrents download pretty good or atleast I didn't noticed the same stalles like `qbittorrent-nox`. But it has upload problems - it is very strange that it is not uploading once the torrents are completed.

But why I'm writing all of this :)? Because I found a very strange correlation how the OpenBSD server behaves while the torrent client is running (and it is visible with both torrent clients).

The whole server starts to lags and stall execution of commands. I'm not sure how to describe it better but for example my SSH session to the server starts to lag like you're connected to a server on the other part of the Globe :).

If I try to `less` a file or run `systat` and just switch between its views, it happens so slow and after a while. Then there is a period while the things are okay, and again stalls.

It doesn't matter if there is an active torrent that is downloading or just a few torrents that are seeding (but no one is actually downloading from me, as I said above).

The server hosts a few small websites (nginx, php, Wordpress) and as I said it is my home router (natting my home LAN). And when it hits the state I describe all LAN devices (PCs, laptops, TVs, etc) start to suffer an extra lag. There is no packet loss but the RTT rises drastically, for example from 2-3ms to 1800ms. Online calls (google meet, telegram/messenger video calls) are suffering most visibly.

And the problem disappear immediately after I stop the torrent client. That's it.

I'm not sure if I managed to describe the problem with all the required details, but please do not hesitate to write me with any questions.

Any help will be appreciated :). I really want to debug this further and find what is going on.


Hello again,

Any thoughts on this behavior? Anyone using torrents with OpenBSD and can try to reproduce the same issue?
Could this be something special in my setup?

The truth is that I'm not sure where I can start debugging this. Is it something with the kernel, in the network stack, or somewhere in the userland and torrent client(s)?

Best wishes,
Atanas

Reply via email to