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 (13,906 stars) (2,725 forks)batch import
help wantedkind/bugstatus/deferredtopic/libp2p

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

Tech stack
go
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Go programmingIPFS conceptsunderstanding of peer to peer networkingdebugging distributed systems
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
The issue describes a problem where IPFS enters a bad state after computer sleep or network changes, with the error 'Republisher failed to republish: failed to find any peer in table' in logs. The debugging tarball (ipfs debug 20150531 republisher failed.tar.gz) may contain helpful logs and state. Investigate the IPNS republisher logic in 'repub.go' and how it handles network transitions. Look for related issues or PRs that discuss systemd integration or sleep/wake handling. Consider testing on a laptop with network changes to reproduce. The scope of a fix is unclear; it may require changes to the republisher's peer discovery or reconnection logic.