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.

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-cluster Routing not found #222

Open
ehsan6sha opened this issue Mar 19, 2024 · 2 comments
Open

ipfs-cluster Routing not found #222

ehsan6sha opened this issue Mar 19, 2024 · 2 comments

Comments

@ehsan6sha
Copy link
Member

ipfs-cluster does not add peer to cluster complaininig routing not found, however the underlying ipfs can ping and connect to the peer target:

ubuntu@pool-4:~$ curl -X POST http://127.0.0.1:5001/api/v0/routing/findpeer?arg=12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS
{"Extra":"","ID":"","Responses":[{"ID":"12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS","Addrs":["/ip4/45.130.104.233/udp/4001/quic-v1/p2p/12D3KooWNaR6pKmLt93oi3YyfsSRSeLPHMK1utVNpU9rJEmKm5vW/p2p-circuit","/ip4/51.81.243.144/tcp/4001/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip6/2604:2dc0:200:f90::/tcp/4001/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip4/51.81.243.144/udp/4001/quic-v1/webtransport/certhash/uEiAxM5W30eIsRnIOhmcMmhpDgSm1sTejbWiV004WNSgzJA/certhash/uEiDG2m2_cz0SkmAGZ1eEH2CWkpKujeoW-eRhFkfWJKyRbQ/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip6/2604:2dc0:200:f90::/udp/4001/quic-v1/webtransport/certhash/uEiAxM5W30eIsRnIOhmcMmhpDgSm1sTejbWiV004WNSgzJA/certhash/uEiDG2m2_cz0SkmAGZ1eEH2CWkpKujeoW-eRhFkfWJKyRbQ/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip6/2604:2dc0:200:f90::/udp/4001/quic-v1/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip4/45.130.104.233/udp/4001/quic/p2p/12D3KooWNaR6pKmLt93oi3YyfsSRSeLPHMK1utVNpU9rJEmKm5vW/p2p-circuit","/ip4/51.81.243.144/udp/4001/quic-v1/p2p/12D3KooWPRGH84dHpLedqFqK62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit","/ip4/45.130.104.233/udp/4001/quic-v1/webtransport/certhash/uEiB2C2u0560eYgPa5k7885SbR2qJKtvFPZudGMmgn9KsOw/certhash/uEiAoJUfsbCICrAVv_pokPKNI30bQUnaMM6TiKMRdAEakbQ/p2p/12D3KooWNaR6pKmLt93oi3YyfsSRSeLPHMK1utVNpU9rJEmKm5vW/p2p-circuit"]}],"Type":2}
ubuntu@pool-4:~$ curl -X POST http://127.0.0.1:5001/api/v0/routing/findpeer -H "Content-Type: application/json" -d '{"peer_id":"12D3K
ooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS"}'
argument "peerID" is required
ubuntu@pool-4:~$ curl -X POST http://127.0.0.1:9094/peers -H "Content-Type: application/json" -d '{"peer_id":"12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS"}'
{"code":500,"message":"routing: not found"}

We do not have any code that directly calls this, but hte issue was that when a new peer was added to the pool, ipfs cluster was not showing it as peers, so I think this is the underlying cause of htat

@ehsan6sha
Copy link
Member Author

even when the underlying ipfs is connected it throws the smae error:

ubuntu@pool-4:~$ curl -X POST "http://127.0.0.1:5001/api/v0/swarm/connect?arg=/ip4/51.81.243.144/tcp/4001/p2p/12D3KooWPRGH84dHpLedqFq
K62m42zcdPV8fCsRStSYJCwZdTeaj/p2p-circuit/p2p/12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS"
{"Strings":["connect 12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS success"]}
ubuntu@pool-4:~$ curl -X POST http://127.0.0.1:9094/peers -H "Content-Type: application/json" -d '{"peer_id":"12D3KooWScK4y7q6JdCSCNE3RLAwHkzpf1i2o6uiYs4aaFBwYZmS"}'
{"code":500,"message":"routing: not found"}

@ehsan6sha
Copy link
Member Author

I did a test and it seems isue is in bootstraping the ipfs-cluster

2024-03-19T12:04:04.564-0400    ERROR   cluster ipfs-cluster/cluster.go:1049    failed to dial: failed to dial 12D3KooWFfj9VawA9KFeectbkWpmM2hhpfpeLewfmX8YBPQmHrm3: all dials failed
  * [/ip4/34.29.196.54/tcp/9096] failed to negotiate security protocol: read tcp4 172.22.102.163:9096->34.29.196.54:9096: read: connection reset by peer
2024-03-19T12:04:04.564-0400    ERROR   service ipfs-cluster-service/daemon.go:264      bootstrap to /dns4/1.pools.functionyard.fula.network/tcp/9096/p2p/12D3KooWFfj9VawA9KFeectbkWpmM2hhpfpeLewfmX8YBPQmHrm3 failed: failed to dial: failed to dial 12D3KooWFfj9VawA9KFeectbkWpmM2hhpfpeLewfmX8YBPQmHrm3: all dials failed
  * [/ip4/34.29.196.54/tcp/9096] failed to negotiate security protocol: read tcp4 172.22.102.163:9096->34.29.196.54:9096: read: connection reset by peer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant