-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Ipfs gets into bad state after computer sleep #2777
Comments
@mythmon thanks for the report! This has been mentioned a few different times in IRC, this is the first time i've gotten a set of debug info about it though. |
Odd, theres nothing in the goroutine dump to indicate that anything is blocked. When this happens could you try manually using |
I can try this next time I see the problem. I don't have a direct way to reproduce the problem yet. I think it is probably more related to changing networks than sleeping the laptop. These events are conflated for me though, since I always sleep my laptop before changing networks (by changing locations). |
@mythmon yeah, that makes sense. I'll try it out on my way home today and see if i cant reproduce the issue. I can also try hopping between my phones tether and my home wifi |
While the problem was occuring, I tried to connect to my boot strap nodes with $ ipfs swarm connect /ip4/192.241.197.120/tcp/4001/ipfs/QmSGYB8socm1hcrFg4gibMYWNcjTh37xRLRVtgoU9vmg3w
Error: connect QmSGYB8socm1hcrFg4gibMYWNcjTh37xRLRVtgoU9vmg3w failure: dial attempt failed: failed to dial <peer.ID SGYB8s>
$ cat ~/.ipfs/config | jq -r '.Bootstrap[]' cmd
/ip4/192.241.197.120/tcp/4001/ipfs/QmSGYB8socm1hcrFg4gibMYWNcjTh37xRLRVtgoU9vmg3w
/ip4/104.131.131.82/tcp/4001/ipfs/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ
/ip4/104.236.176.52/tcp/4001/ipfs/QmSoLnSGccFuZQJzRadHn95W2CrSFmZuTdDWP8HXaHca9z
/ip4/104.236.179.241/tcp/4001/ipfs/QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM
/ip4/162.243.248.213/tcp/4001/ipfs/QmSoLueR4xBeUbY9WZ9xGUUxunbKWcrNFTDAadQJmocnWm
/ip4/128.199.219.111/tcp/4001/ipfs/QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu
/ip4/104.236.76.40/tcp/4001/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64
/ip4/178.62.158.247/tcp/4001/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd
/ip4/178.62.61.185/tcp/4001/ipfs/QmSoLMeWqB7YGVLJN3pNLQpmmEk35v6wYtsMGLzSr5QBU3
/ip4/104.236.151.122/tcp/4001/ipfs/QmSoLju6m7xTh3DuokvT3886QRYqxAzb1kShaanJgW36yx
$ cat ~/.ipfs/config | jq -r '.Bootstrap[]' | xargs -L 1 ipfs swarm connect
Error: connect QmSGYB8socm1hcrFg4gibMYWNcjTh37xRLRVtgoU9vmg3w failure: dial backoff
Error: connect QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ failure: dial backoff
Error: connect QmSoLnSGccFuZQJzRadHn95W2CrSFmZuTdDWP8HXaHca9z failure: dial backoff
Error: connect QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM failure: dial backoff
Error: connect QmSoLueR4xBeUbY9WZ9xGUUxunbKWcrNFTDAadQJmocnWm failure: dial backoff
Error: connect QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu failure: dial backoff
Error: connect QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64 failure: dial attempt failed: failed to dial <peer.ID SoLV4B>
Error: connect QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd failure: dial backoff
Error: connect QmSoLMeWqB7YGVLJN3pNLQpmmEk35v6wYtsMGLzSr5QBU3 failure: dial attempt failed: failed to dial <peer.ID SoLMeW>
Error: connect QmSoLju6m7xTh3DuokvT3886QRYqxAzb1kShaanJgW36yx failure: dial backoff |
@mythmon next time this happens could i get the output from |
When I run Is there something I can do to increase the logging verbosity? |
same problem. running with
|
same error here
|
Possibly libp2p/go-libp2p#1554 |
I suspect this happens after I sleep my laptop and/or change networks. I'll notice that IPFS doesn't work (I can't get content, and content I
ipfs add
isn't available on other nodes). In the logs, I'll see a message likeThe process is still running. I'm running this on a laptop, and using systemd (in user mode) to run ipfs.
I collected debugging information, and uploaded it here: ipfs-debug-20150531-republisher-failed.tar.gz.
The text was updated successfully, but these errors were encountered: