Go-filecoin daemon is not connecting to bootstrap addresses

Hello,

I have just downloaded the latest go-filecoin codes from github and built go-filecoin with the instructions provided on the Gettig Started Guide here:

https://go.filecoin.io/go-filecoin-tutorial/Getting-Started.html#start-running-filecoin

, from which I followed (with my interpretation of the incomplete doc) with the steps below:

login as root and get to the homedir

cd /root

remove the previous go-filecoin codes

rm -rf go-filecoin

clone the go-filecoin code from git:

git clone https://github.com/filecoin-project/go-filecoin.git

change into the go-filecoin directory created by the above git command

cd go-filecoin

load all git modules while inside the go-filecoin/ directory

git submodule update --init --recursive

init the build dependencies

make deps

build the binary

make

building and testing together

go run ./build best

[note] during the process, I encountered a failed test on this:

?       github.com/filecoin-project/go-filecoin/internal/pkg/protocol/storage   [no test files]
--- FAIL: TestRepoAPIFile (1.00s)
    --- FAIL: TestRepoAPIFile/SetAPI_fails_if_unable_to_create_API_file (0.18s)
        fsrepo_test.go:324:
                Error Trace:    fsrepo_test.go:324
                                                        fsrepo_test.go:371
                                                        fsrepo_test.go:317
                Error:          An error is expected but got nil.
                Test:           TestRepoAPIFile/SetAPI_fails_if_unable_to_create_API_file
FAIL
FAIL    github.com/filecoin-project/go-filecoin/internal/pkg/repo       1.817s

but that didn’t cause issue with building the ‘go-filecoin’ binary

NOW, to start the go-filecoin daemon:

clean up the previous .filecoin directory in /root/

rm -rf ~/.filecoin

initialize go-filecoin:

go-filecoin init --genesisfile=https://ipfs.io/ipfs/QmXZQeezX1x8uRQX9EUaYxnyivUpTfJqQTvszk3c8SnFPN/testnet.car --network=testnet

start the daemon!

go-filecoin daemon

ERRORs about connected to wrong peer keeps on displaying over and over and over:

2020-06-22T21:24:46.579-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 All 1 tables opened in 0s

2020-06-22T21:24:46.580-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replaying file id: 0 at offset: 278818

2020-06-22T21:24:46.580-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replay took: 2.089µs

2020-06-22T21:24:46.585-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 All 1 tables opened in 0s

2020-06-22T21:24:46.586-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replaying file id: 0 at offset: 163

2020-06-22T21:24:46.586-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replay took: 2.881µs

2020-06-22T21:24:46.592-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 All 1 tables opened in 0s

2020-06-22T21:24:46.593-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replaying file id: 0 at offset: 356

2020-06-22T21:24:46.593-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replay took: 20.084µs

2020-06-22T21:24:46.598-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 All 0 tables opened in 0s

2020-06-22T21:24:46.599-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replaying file id: 0 at offset: 0

2020-06-22T21:24:46.599-0700 INFO badger v2@v2.0.1-rc1.0.20200120142413-c3333a5a830e/logger.go:46 Replay took: 2.08µs

“My peer ID is QmRg7J9MKX31feCFTB2bBPUWHoaWatpvXCE7fogZqpWZrJ\n”
“Swarm listening on: /ip4/127.0.0.1/tcp/6000\n”
“Swarm listening on: /ip4/192.168.5.230/tcp/6000\n”
2020-06-22T21:24:46.610-0700 INFO chain.store chain/store.go:145 start loading chain at tipset: { bafy2bzacedajjxea4zfdef46bgqnntygqsmv6f2ntabrldkznpt7livxdmg6m }, height: 0
2020-06-22T21:24:46.610-0700 INFO chain.store chain/store.go:190 finished loading 0 tipsets from { bafy2bzacedajjxea4zfdef46bgqnntygqsmv6f2ntabrldkznpt7livxdmg6m }
2020-06-22T21:24:57.019-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWKNF7vNFEhnvB45E9mw2B5z6t419W3ziZPLdUDVnLLKGs: [/ip4/86.109.15.57/tcp/1347]}: failed to dial 12D3KooWKNF7vNFEhnvB45E9mw2B5z6t419W3ziZPLdUDVnLLKGs: all dials failed

  • [/ip4/86.109.15.57/tcp/1347] failed to negotiate security protocol: connected to wrong peer
    2020-06-22T21:25:07.055-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWGPDJAw3HW4uVU3JEQBfFaZ1kdpg4HvvwRMVpUYbzhsLQ: [/dns4/bootstrap-1-fra.fil-test.net/tcp/1347]}: failed to dial 12D3KooWGPDJAw3HW4uVU3JEQBfFaZ1kdpg4HvvwRMVpUYbzhsLQ: all dials failed
  • [/ip4/136.144.49.131/tcp/1347] failed to negotiate security protocol: connected to wrong peer
    2020-06-22T21:25:17.041-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWC7MD6m7iNCuDsYtNr7xVtazihyVUizBbhmhEiyMAm9ym: [/dns4/bootstrap-0-fra.fil-test.net/tcp/1347]}: failed to dial 12D3KooWC7MD6m7iNCuDsYtNr7xVtazihyVUizBbhmhEiyMAm9ym: all dials failed
  • [/ip4/136.144.49.17/tcp/1347] failed to negotiate security protocol: connected to wrong peer
    2020-06-22T21:25:31.612-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWLB3RR8frLAmaK4ntHC2dwrAjyGzQgyUzWxAum1FxyyqD: [/ip4/139.178.84.41/tcp/1347]}: failed to dial 12D3KooWLB3RR8frLAmaK4ntHC2dwrAjyGzQgyUzWxAum1FxyyqD: all dials failed
  • [/ip4/139.178.84.41/tcp/1347] dial tcp4 0.0.0.0:6000->139.178.84.41:1347: i/o timeout
    2020-06-22T21:25:36.612-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWLB3RR8frLAmaK4ntHC2dwrAjyGzQgyUzWxAum1FxyyqD: [/ip4/139.178.84.41/tcp/1347]}: dial backoff
    2020-06-22T21:25:46.794-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWECJTm7RUPyGfNbRwm6y2fK4wA7EB8rDJtWsq5AKi7iDr: [/dns4/bootstrap-0-dfw.fil-test.net/tcp/1347]}: failed to dial 12D3KooWECJTm7RUPyGfNbRwm6y2fK4wA7EB8rDJtWsq5AKi7iDr: all dials failed
  • [/ip4/139.178.84.45/tcp/1347] failed to negotiate security protocol: connected to wrong peer
    2020-06-22T21:26:01.612-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWD8eYqsKcEMFax6EbWN3rjA7qFsxCez2rmN8dWqkzgNaN: [/ip4/86.109.15.55/tcp/1347]}: failed to dial 12D3KooWD8eYqsKcEMFax6EbWN3rjA7qFsxCez2rmN8dWqkzgNaN: all dials failed
  • [/ip4/86.109.15.55/tcp/1347] dial tcp4 0.0.0.0:6000->86.109.15.55:1347: i/o timeout
    2020-06-22T21:26:11.612-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWLB3RR8frLAmaK4ntHC2dwrAjyGzQgyUzWxAum1FxyyqD: [/ip4/139.178.84.41/tcp/1347]}: failed to dial 12D3KooWLB3RR8frLAmaK4ntHC2dwrAjyGzQgyUzWxAum1FxyyqD: all dials failed
  • [/ip4/139.178.84.41/tcp/1347] dial tcp4 0.0.0.0:6000->139.178.84.41:1347: i/o timeout
    2020-06-22T21:26:17.018-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWKNF7vNFEhnvB45E9mw2B5z6t419W3ziZPLdUDVnLLKGs: [/ip4/86.109.15.57/tcp/1347]}: failed to dial 12D3KooWKNF7vNFEhnvB45E9mw2B5z6t419W3ziZPLdUDVnLLKGs: all dials failed
  • [/ip4/86.109.15.57/tcp/1347] failed to negotiate security protocol: connected to wrong peer
    2020-06-22T21:26:26.939-0700 ERROR net.bootstrap discovery/bootstrap.go:141 got error trying to connect to bootstrap node {12D3KooWGPDJAw3HW4uVU3JEQBfFaZ1kdpg4HvvwRMVpUYbzhsLQ: [/dns4/bootstrap-1-fra.fil-test.net/tcp/1347]}: failed to dial 12D3KooWGPDJAw3HW4uVU3JEQBfFaZ1kdpg4HvvwRMVpUYbzhsLQ: all dials failed

What went wrong here? It appears that the bootstrap addresses in

/root/.filecoin/config.json

are invalid.

Background Info:
Event Date: 2020-06-22
Go-filecoin version: “16d8e39e8f8cfcd6fcd3a9ab8c5ffad31ff44be6”
Server OS: Ubuntu 20.04LTS

– I can telnet to those bootstrap addresses’ 1347 port successfully.
– This issue started after the testnet reset not too long ago; I have been trying with new code downloads from git and resetting/rebuilding go-filecoin with no avail.

Hi @Mstry, Please use lotus Filecoin for now.

Why did you chose go-filecoin over lotus? Was there a place in the docs where you decided to use go-filecoin?

I was using Lotus, but I wanted to try go-filecoin per Testnet Phase 2.

Is go-filecoin still not recommended for testing on the Testnet?

@Mstry

As described in the recent roadmap update go-filecoin is being graduated to community maintenance as a dev grant RFP.

I see! Thank you for the reply and the information.
It really helped.

I will return to using the latest Lotus and try go-filecoin another time.