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

Repeated swarm connects may be causing connectivity issues #6145

Open
obo20 opened this issue Mar 28, 2019 · 3 comments
Open

Repeated swarm connects may be causing connectivity issues #6145

obo20 opened this issue Mar 28, 2019 · 3 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@obo20
Copy link

obo20 commented Mar 28, 2019

Version information:

go-ipfs version: 0.4.19-
Repo version: 7
System version: amd64/linux
Golang version: go1.11.5

Type:

  • "bug": If what you are filing is a bug.

Description:

I ran into an issue where repeated swarm connects between two nodes may have caused connectivity issues.

Essentially, I was running the following system service every 1 minute on my host node

[Unit]
Description=Job that periodically connects this IPFS node to the gateway node
[Service]
ExecStart=/home/yourUserName/go/bin/ipfs swarm connect /ip4/GGG.GGG.GGG.GGG/tcp/4001/ipfs/gatewayID
Environment="IPFS_PATH=/ipfs"

I was then running a complementary version of this service on the gateway node, connecting it to the host node.

Initially on node reboots, things appeared to be working fine, but then after around 30 minutes or so, the network was essentially unable to find new content as it was added to the host node.

Disabling the system service above seems to have fixed my problems, although I filed this bug report at the request of @Stebalien so he could look into a hunch he had.

@Stebalien
Copy link
Member

So, my hunch was incorrect. I'm not sure why this makes a difference.

@Stebalien Stebalien added the kind/bug A bug in existing code (including security flaws) label Mar 28, 2019
@Stebalien
Copy link
Member

Could you try setting the IPFS_REUSEPORT environment variable to false (in your daemon's environment). I've run into some interesting reconnect delays here with respect to reuseport.

@momack2 momack2 added this to Inbox in ipfs/go-ipfs May 9, 2019
@autonome
Copy link

autonome commented Jun 5, 2020

@obo20 Is this still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
No open projects
Development

No branches or pull requests

3 participants