ipfs/kubo

Ipfs gets into bad state after computer sleep

Open

#2,777 opened on Jun 1, 2016

View on GitHub
 (10 comments) (3 reactions) (0 assignees)Go (2,725 forks)batch import
help wantedkind/bugstatus/deferredtopic/libp2p

Repository metrics

Stars
 (13,906 stars)
PR merge metrics
 (Avg merge 4d 2h) (28 merged PRs in 30d)

Description

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 like

19:41:54.117 ERROR ipns-repub: Republisher failed to republish: failed to find any peer in table repub.go:72

The 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.

Contributor guide

Research direction
Examine the republisher error in repub.go and trace how peer discovery fails after network changes or sleep. Look at the routing table and peer store to understand why it cannot find peers. Consider reproducing the issue in a controlled environment.
Tech stack
go
Domain
distributed systems
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70