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.

Sign up for GitHub

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

Jump to bottom

ipfs swarm2 got error on dial, etc #6357

Closed
tmcw opened this issue May 21, 2019 · 3 comments
Closed

ipfs swarm2 got error on dial, etc #6357

tmcw opened this issue May 21, 2019 · 3 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@tmcw
Copy link

tmcw commented May 21, 2019 •
edited
Loading

Version information:

go-ipfs version: 0.4.20-
Repo version: 7
System version: arm/linux
Golang version: go1.12.4

Description:

Process:

  1. Install ipfs on a Raspberry PI: run ipfs init -p lowpower to try and cater to the PI hardware. (Note that I've also tried running ipfs init, without the lowpower profile. The same thing happens.
  2. Run ipfs daemon in one terminal.
  3. Run ipfs log level all info in another terminal, to make the demon loud.
  4. Run any ipfs command. In my case, cat'ing the readme seems to do it: ipfs cat QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG/readme, as well as anything else that interacts with the network.

And you'll get this output:

pi@raspberrypi:~ $ ipfs daemon
Initializing daemon...
go-ipfs version: 0.4.20-
Repo version: 7
System version: arm/linux
Golang version: go1.12.4
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/192.168.42.10/tcp/4001
Swarm listening on /ip6/::1/tcp/4001
Swarm listening on /p2p-circuit
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/192.168.42.10/tcp/4001
Swarm announcing /ip6/::1/tcp/4001
API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway (readonly) server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready
04:57:05.408  INFO core/comma: Changed log level of '*' to 'info'
 log.go:70
04:57:30.583  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*wMKPnu> (/ip6/2400:6180:0:d0::151:6001/tcp/4001) dial attempt failed: dial tcp6 [2400:6180:0:d0::151:6001]:4001: connect: network is unreachable swarm_dial.go:412
04:57:32.200  INFO      relay: new relay stream from: <peer.ID Qm*wMKPnu> relay.go:251
04:57:32.216  INFO       core: bootstrapped with <peer.ID Qm*wMKPnu> bootstrap.go:186
04:58:00.815  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/udp/4001/quic/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial attempt failed: no good addresses swarm_dial.go:412
04:58:00.817  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.80.33/udp/4001/quic/ipfs/QmSn4heyhN27h8QX6hEgWeLw2kMo75ZEwj1ECk1c4khUPN/p2p-circuit) dial attempt failed: dial attempt failed: no good addresses swarm_dial.go:381
04:58:00.819  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/tcp/37280/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.821  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.80.33/tcp/40536/ipfs/QmSn4heyhN27h8QX6hEgWeLw2kMo75ZEwj1ECk1c4khUPN/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.869  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.80.33/tcp/43914/ipfs/QmSn4heyhN27h8QX6hEgWeLw2kMo75ZEwj1ECk1c4khUPN/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:412
04:58:00.872  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/tcp/42744/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.874  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.80.33/tcp/4001/ipfs/QmSn4heyhN27h8QX6hEgWeLw2kMo75ZEwj1ECk1c4khUPN/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.898  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*2DaSyA> (/ip6/2001:41d0:52:800::1154/tcp/4001) dial attempt failed: dial tcp6 [2001:41d0:52:800::1154]:4001: connect: network is unreachable swarm_dial.go:412
04:58:00.927  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/147.75.84.57/udp/4001/quic/ipfs/QmZP8NCi1L2LS8K2DoG175tH4mSe8Z4ygcVXkwFxnyeMLL/p2p-circuit) dial attempt failed: dial attempt failed: no good addresses swarm_dial.go:412
04:58:00.929  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/139.178.69.15/udp/4001/quic/ipfs/QmTg7DdGo519B7KdzFppTaK5i8WGWu9erGhxsLafxRd6gp/p2p-circuit) dial attempt failed: dial attempt failed: no good addresses swarm_dial.go:381
04:58:00.931  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/147.75.84.57/tcp/4001/ipfs/QmZP8NCi1L2LS8K2DoG175tH4mSe8Z4ygcVXkwFxnyeMLL/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.934  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/147.75.84.57/tcp/46528/ipfs/QmZP8NCi1L2LS8K2DoG175tH4mSe8Z4ygcVXkwFxnyeMLL/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.936  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/139.178.69.15/tcp/4001/ipfs/QmTg7DdGo519B7KdzFppTaK5i8WGWu9erGhxsLafxRd6gp/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.947  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/tcp/4001/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:412
04:58:00.948  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/tcp/49222/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.951  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.80.33/tcp/49514/ipfs/QmSn4heyhN27h8QX6hEgWeLw2kMo75ZEwj1ECk1c4khUPN/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:381
04:58:00.957  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*nrqQKB> (/ip4/147.75.84.57/tcp/43648/ipfs/QmZP8NCi1L2LS8K2DoG175tH4mSe8Z4ygcVXkwFxnyeMLL/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:412
04:58:00.964  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*CVGGKZ> (/ip4/147.75.105.219/tcp/55098/ipfs/QmTtFWmQ3qrp166m96ibL2jW2Doz4tJjo2CwQfYNaFb3XZ/p2p-circuit) dial attempt failed: dial backoff swarm_dial.go:412
04:58:01.012  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*vcbydY> (/ip4/139.178.69.3/tcp/52380) dial attempt failed: dial tcp4 139.178.69.3:52380: connect: connection refused swarm_dial.go:412
04:58:01.049  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*WgBvJK> (/ip4/139.178.69.3/tcp/52380/ipfs/QmdGQoGuK3pao6bRDqGSDvux5SFHa4kC2XNFfHFcvcbydY/p2p-circuit) dial attempt failed: dial attempt failed: 1 error occurred:
	* <peer.ID Qm*jqWzjy> --> <peer.ID Qm*vcbydY> (/ip4/139.178.69.3/tcp/52380) dial attempt failed: dial tcp4 139.178.69.3:52380: connect: connection refused

 swarm_dial.go:412
04:58:01.054  INFO     swarm2: got error on dial: <peer.ID Qm*jqWzjy> --> <peer.ID Qm*WgBvJK> (/ip4/139.178.69.3/tcp/43658/ipfs/QmdGQoGuK3pao6bRDqGSDvux5SFHa4kC2XNFfHFcvcbydY/p2p-circuit) dial attempt failed: dial attempt failed: 1 error occurred:
	* <peer.ID Qm*jqWzjy> --> <peer.ID Qm*vcbydY> (/ip4/139.178.69.3/tcp/52380) dial attempt failed: dial tcp4 139.178.69.3:52380: connect: connection refused

The dial attempt failed messages proceed in lightning-quick success, several per second.

My initial issue was that ipfs pin add hangs on this machine, and I noticed this output, but now realize that the error is the same regardless of which command I run. This admittedly may be the same as #6350, but that seems to be more specific to a particular command.
@Stebalien Stebalien added the kind/bug A bug in existing code (including security flaws) label May 21, 2019
@Stebalien
Copy link
Member

I believe the "no good addresses" error is coming from nodes that are only listening on localhost, port 4001. We say "no good addresses" because we know that we're listening on that address so we refuse to dial it.

Looks like libp2p/go-libp2p-kad-dht#330.

@tmcw
Copy link
Author

tmcw commented May 27, 2019

Is there anything in particular about my setup that might be triggering this bug? And is this likely to be the root cause behind IPFS being unable to add a pin? I'm trying to get this server set up to pin my website, and this is a blocker. If there's a different approach that would make IPFS work, I'd love to try it.

@Stebalien
Copy link
Member

(working through my backlog)

Is there anything in particular about my setup that might be triggering this bug?

No.

Those messages aren't directly responsible for anything, they just indicate a deeper problem in the DHT.

And is this likely to be the root cause behind IPFS being unable to add a pin?

Are you trying to pin content stored on a remote node? If so, maybe? The underlying issue is #6383.

If there's a different approach that would make IPFS work, I'd love to try it.

The different approach is, for now, to manually connect all nodes that need to share content (ipfs swarm connect ...).

I'm going to close this as DHT/content routing issues are tracked in the above bug and being worked on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tmcw @Stebalien