qBittorrent and SAM timeouts

[anikey-from-i2p]

When qBittorrent is running for a long time (like a day), all trackers start being marked as "timed out".

I've only started noticing this relatively recently. Probably when I updated i2pd to 2.60.

Has anyone experienced this? (There is one person on i2p forum that mentioned this not working on the SAM connection)

I'll try to run a test soon with a separate SAM program specifically for testing this.

Oh, and one more thing: i've noticed that whenever i restart qbittorrent to fix this timing out issue, the SAM session keeps being listed in the i2pd web ui, but when i try to open it, the page doesn't load and there's this error in the i2pd log: HTTPServer: Runtime exception: remote_endpoint: Transport endpoint is not connected (it doesn't refer to any i2pd source files, only boost asio source file)

[spotifyaccs]

I believe this is a session cleanup regression introduced in 2.60. The Transport endpoint is not connected error (ENOTCONN in Boost.Asio) means i2pd's HTTP server is trying to read the remote endpoint of an already-dead socket — the session is registered in the web UI but the underlying TCP connection is gone.
The tracker timeouts after long uptime are likely caused by this: qBittorrent's SAM session silently dies, but i2pd keeps it listed as active, so no new session is negotiated.

perhaps you could try restart i2pd itself (not just qBittorrent) to force-clear zombie sessions

[letko-dmitry]

Has anyone experienced this? (There is one person on i2p forum that mentioned this not working on the SAM connection)

I'm not able to get deep into details but I observe the same thing. And this behavior is stable. It always gets to "timed out" state and never gets back.

i2pd 2.60

[anikey-from-i2p]

Update:

Some time ago i ran a test script that connects to a site periodically, it stayed up for like a week. So the trigger has to be more complex than just "open a session and connect to things".

Also, i noticed that, even though the connections to trackers time out, things can still be seeding, so either:

• it stays connectable, just can't initiate connections on your own
• or maybe it just retains the connections that already existed

I haven't updated to 2.61 yet, though.

Update: it's still happening on 2.61. (I know I got suggested to update to latest commit, but still, at least now we know it's not been fixed in that time frame between 2.60 and 2.61, if we ever want to know the root cause).

Forgot to tell one interesting thing: when this timeout thing starts happening, if you try to use the SAM bridge with qBittorrent's ID (you can copy it from the i2pd webconsole) with netcat (manually typing the protocol), it can still connect to things, including the trackers qbt times out on.

[Vort]

There were many fixes already since 2.61. So it is better to test latest commit as well.