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

getting bootstrap peers: network doesn't have any configured bootstrappers #827

Open
akashsenta13 opened this issue May 3, 2021 · 6 comments

Comments

@akashsenta13
Copy link

I have tried running localnet and its working fine. but when i tried to run mainnet i am getting bellow mentioned issue and powergate instance is keep going down multiple times. please help

image

@jsign
Copy link
Contributor

jsign commented May 3, 2021

The 8th line there says that your lotus node is trying to connect to testnetnet, not mainnet.
Also, considering your WARN log line I can already imagine what's happening.

You're trying to sync a lotus node from scratch.. which at first that network was called testnetnet before mainnet launch.

You should import a snapshot in the Lotus node to have it synced.
https://docs.textile.io/powergate/mainnet/#bootstrap-a-clean-lotus-node-from-a-snapshot

@akashsenta13
Copy link
Author

@jsign Thanks for sharing. started importing it. but its 26GB around data !! is it necessary ?
Also i need to use private IPFS node with powergate/filecoin if can suggest any suitable documentation or tutorial would be fine.

@jsign
Copy link
Contributor

jsign commented May 3, 2021

Well, actually I think today's snapshots are already at the ~40GiB size. Unfortunately, there isn't much we can do about that since its the space needed to run a Lotus node.

Our docker-compose setup already runs a go-ipfs node since Powergate and Lotus make use of it for the data persistence layer.

@ChristianOConnor
Copy link

Since I'm away from my PC today I tried to start a node with my mac and I got this exact same error. I followed the recommended steps to avoid this but the error persists. I did:
cd docker
put command: ["lotus", "daemon", "--import-snapshot", "https://fil-chain-snapshots-fallback.s3.amazonaws.com/mainnet/minimal_finality_stateroots_latest.car"] into the docker-compose.yaml file between lines 32 and 33
make up
wait for the blockchain to finish downloading in the lotus logs
then ^C and make down
remove the import snapshot line I added in docker-compose.yaml
make up
then I get the same errors as OP got. Terminal also said "Detected Lotus node connected to network: testnetnet"

Is it possible that I didn't wait long enough for the snapshot to sync? I waited until at least 5-10 minute after the lotus logs printed " / " what do you think the problem is?

@jsign
Copy link
Contributor

jsign commented Aug 3, 2021

Importing a snapshot can take 20 or 30 min, so most probably your importing didn't finish. The logs usually show some progress of the importing and you can signal when finished by taking a look at it.

@ChristianOConnor
Copy link

ChristianOConnor commented Aug 4, 2021

I left my docker stack syncing all day and it downloaded the blockchain snapshot 3 times then ran out of space and failed.

But I did it again this time with extra space added to docker and it synced 3 times and worked lol.

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

3 participants