Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I2P SAM connection is not reestablished when closed #7453

Open
Vort opened this issue Jun 18, 2023 · 5 comments
Open

I2P SAM connection is not reestablished when closed #7453

Vort opened this issue Jun 18, 2023 · 5 comments

Comments

@Vort
Copy link
Contributor

Vort commented Jun 18, 2023

Tested with client_test and i2pd.

  1. Start i2pd.
  2. Start client_test and verify that SAM session is active at http://127.0.0.1:7070/?page=sam_sessions.
  3. Stop i2pd (Force shutdown).
  4. Start i2pd again.

Expected behaviour: SAM session is recreated once i2pd is up again (after step 4).
Actual behaviour: no session is (re)created, SAM sessions page is empty.

Reason: i2pd crashes sometimes and it is more convenient for user to restart just i2pd and not both i2pd and torrent client.

libtorrent version (or branch): c2012b0
platform/architecture: Windows
compiler and compiler version: clang 15.0.7

@stale
Copy link

stale bot commented Sep 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@mpeter50
Copy link

mpeter50 commented Nov 6, 2023

I have a similar issue that I think could be caused by the same problem.

The short version is that when a libtorrent client's machine has been suspended (sleep/hibernate) for long enough, libtorrent loses the SAM connection until it is manually turned off and on again on the client side.
I have also found a clue that may mean that libtorrent tries to reconnect, but does that incorrectly.
It may be good to know that I have this problem with the Java implementation of the I2P router, not I2PD, so this may not be a router issue.

Details can be found at the above linked issue in the qBittorrent repo.
If it is preferred to also post the info to this issue or a separate one in the repo, please let me know.

@mpeter50
Copy link

mpeter50 commented Dec 6, 2023

I have disabled I2P functionality in qBittorrent a few weeks ago, and as it looks the frequent SAMBridge logs have stopped right there. Last such message was printed on 2023-11-09, almost a month ago. I don't remember exactly when did I turned off I2P functionality, but that date seems about right.

For now I won't turn it back on, as it wouldn't work anyway on my system.

@stale stale bot removed the stale label Dec 6, 2023
@arvidn
Copy link
Owner

arvidn commented Feb 19, 2024

I believe this is a missing feature. The SAM connection is triggered by setting a SAM hostname and port in the settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants