I’ve configured an ipfs node (using the go ipfs distribution, version 0.4.17), and as far as I can tell the basics work – the daemon is running, there are 800+ swarm peers, stuff is getting logged, I can access the test readme, etc. However, given some hashes that are (in theory) on another ipfs node on campus, attempts to ipfs get
or ipfs object stat
or do other things never produces a result: the ipfs
command-line comman seems to hang indefinitely. My question is, how do I go about debugging why this is happening?
When I turn on ipfs logging at the debug level, start a tail+grep looking for a specific hash, and do ipfs get {hash}
, I see things like the following in the log file,
16:01:07.335 DEBUG cmds/http: incoming API request: /get?arg=QmeC1CGZ6yFGBiCutjEL3s438eciw8rMAYJ5FZHdFY8yfo&encoding=json&stream-channels=true handler.go:88
16:01:07.335 DEBUG blockservi: BlockService GetBlock: 'QmeC1CGZ6yFGBiCutjEL3s438eciw8rMAYJ5FZHdFY8yfo' blockservice.go:201
16:01:07.335 INFO bitswap: want blocks: [QmeC1CGZ6yFGBiCutjEL3s438eciw8rMAYJ5FZHdFY8yfo] wantmanager.go:81
but that’s it; the command never returns after a long time (30+ minutes) even though the ipfs daemon is plainly running.
Suggestions for what to try next are welcome.