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

Pinning stops receiving blocks and requires manual reconnect constantly #5360

Closed
victorb opened this issue Aug 9, 2018 · 2 comments
Closed
Labels
kind/bug A bug in existing code (including security flaws) status/duplicate This issue or pull request already exists

Comments

@victorb
Copy link
Member

victorb commented Aug 9, 2018

Version information:

Local

go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/linux
Golang version: go1.10.3

Remote

go-ipfs version: 0.4.13-
Repo version: 6
System version: amd64/linux
Golang version: go1.9.2

Type:

Bug?

Description:

I have a archive I'm trying to transfer to a remote machine (QmYMfSnEREWgPAbpbNByyE7xrZgbY6DrGxJxt3Do6c9DEt). I have a daemon locally and remotely running fine without any crashes. However, after starting the pinning process, it gets hung and stops downloading new blocks. This usually takes an hour or something like that to happen.

Not until I connect them manually with a swarm connect do the pinning continue. Even then, after ~1 hour, it hangs again and requires a swarm connect again to continue. This repeats until the pinning is done.

@victorb
Copy link
Member Author

victorb commented Aug 9, 2018

Made a short demonstration of it in action, observe the bottom-right pane where it doesn't continue until I run swarm connect in the bottom-left pane https://ipfs.io/ipfs/QmNyKRL1cTNB3o3JNYRKCihQY1YtSpJf2raphPRnaur5wT/pinning-hang.mp4

@Stebalien
Copy link
Member

Closing in favor of #5183. It may not be the same issue, but it looks like it.

@Stebalien Stebalien added kind/bug A bug in existing code (including security flaws) status/duplicate This issue or pull request already exists labels Sep 11, 2018
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) status/duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants