Questions tagged [bootstrapping]

The tag has no usage guidance.

Filter by
Sorted by
Tagged with
1
vote
0answers
11 views

How to point to existing blockchain data in docker?

I moved my docker container to a new partition for more space and started the alphanet. It started syncing from the beginning instead of using the bootstrapped data I transferred in the container. How ...
3
votes
1answer
50 views

Unexpected error (validator) during bootstrapping

I recently brought up a new node via docker and saw it got stuck during bootstrapping. $ ./mainnet.sh client bootstrapped Current head: BMeUZ1D6FWZv (timestamp: 2019-06-20T16:54:00-00:00, validation:...
2
votes
0answers
58 views

Rebuilding Node and Syncing with snapshot [closed]

I had to spin up a new node...used a snapshot. How long should it take sync?
4
votes
2answers
63 views

Where can we find FILE.full publicly for bootstrapping from a snapshot?

In the Nomadic Labs post on Snapshots and History Modes (https://blog.nomadic-labs.com/introducing-snapshots-and-history-modes-for-the-tezos-node.html) , it talks about bootstrapping a Tezos node from ...
3
votes
1answer
84 views

`tezos-client bootstrapped`: why it quits too early, really without waiting bootstrapping to the network?

When we start a Tezos node from scratch, it takes long time to bootstrap. We can monitor the progress with tezos-client bootstrapped command. However, the command usually quits at a very early stage ...
4
votes
0answers
49 views

Strange behaviour running a node on Google Cloud

When trying to bootstrap a node in a VM on Google Cloud Platform I see the performance running fine for approximately 30 minutes before it completely tails off. You can see this from the graphs below ...
3
votes
1answer
162 views

Time for bootstrapping a node in alphanet

I have started a tezos node on my local machine in alphanet and it seems to take two hours to move head 12 days after downloading more than 800MB of data. The node seems to be actively getting data ...
4
votes
1answer
50 views

Starting Tezos node gives “Bus error: 10”

>./tezos-node run --rpc-addr 127.0.0.1:8732 --connections 10 Feb 10 20:56:31 - node.main: Starting the Tezos node... Feb 10 20:56:31 - node.main: Peer's global id: idqebupXmLLYzWb7tZ1eefRxQxUMTW ...