Skip to main content
Version: mainnet (v0.71)

How to restart data node from network history

Why would you start/restart your data node from network history?​

  • Your data node crashed
  • You are starting a data node when the network has a lot of blocks, and replaying from block 0 would be a long process (up to several days)
  • Your data node state got corrupted

What is network history?​

Network history is a mechanism in the data node software that allows for sharing chunks of information between other data nodes connected to the network. For example, when you are interested in a specific period of data from the Vega network, you can use network history to download this data from other nodes if they have it. Usually, you are interested in the last few blocks required to start a new data node or a data node after a crash - in those cases, you do not need the full network history.

Requirements​

Information you need to start or restart the data node from network history:

  • Tendermint RPC servers for the state sync
  • Trust block hash and height from one node you are going to sync with
  • Bootstrap peers for data node

This guide will explain how to get the trust block hash and height further down.

Start/restart node with network history​

Follow the steps below to start up, or restart, your data node using network history.

Data node must be configured

You must have a data node already configured and running. If you do not have one already, see the guide on setting up a data node.

1. Stop data node if it is running​

If you're using Visor, you must stop it to control your node.

Otherwise, you must stop the Vega and data node processes.

Example commands:

# visor:
systemctl stop vegavisor;

# non-visor:
systemctl stop data-node;
systemctl stop vega;

2. Use unsafe reset all to clear the state​

# remove data node state
rm -rf /home/vega/vega_home/state/data-node/

# remove Vega state
vega unsafe_reset_all --home <vega-home>

# remove Tendermint state
vega tm unsafe_reset_all --home <tendermint-home>

3. Update config​

a. Data node config​

Data node config is located in the <vega_home>/config/data-node/config.toml file.

Update the following parameters in your config.toml file for the mainnet data node:

AutoInitialiseFromNetworkHistory = true

[SQLStore]
  WipeOnStartup = true

[NetworkHistory]
  Enabled = true
  [NetworkHistory.Store]
    BootstrapPeers = ["/dns/api1.vega.community/tcp/4001/ipfs/12D3KooWDZrusS1p2XyJDbCaWkVDCk2wJaKi6tNb4bjgSHo9yi5Q","/dns/api2.vega.community/tcp/4001/ipfs/12D3KooWEH9pQd6P7RgNEpwbRyavWcwrAdiy9etivXqQZzd7Jkrh","/dns/api0.vega.community/tcp/4001/ipfs/12D3KooWAHkKJfX7rt1pAuGebP9g2BGTT5w7peFGyWd2QbpyZwaw","/dns/api7.vega.community/tcp/4001/ipfs/12D3KooWBqVQPjJur5EvjrizCyKG2d6eyCX8hxkvVXeUQHMjbWj9"]


  [NetworkHistory.Initialise]
    TimeOut = "4h"

b. Vega core node config​

The config is located in the <vega_home>/config/node/config.toml. Update the following parameters in your config.toml file for the Vega core for mainnet:

[Snapshot]
  StartHeight = -1

[Broker]
  [Broker.Socket]
    DialTimeout = "4h"

c. Tendermint config​

To update Tendermint, you need to know the trust block and height. To collect the above information, please visit one of the following links:

Then select one of the latest pairs for block height and hash.

Once you have the trusted block, you can update the following parameters in the <tendermint_home>/config/config.toml file:

[statesync]
enable = true
rpc_servers = "api0.vega.community:26657,api1.vega.community:26657,api2.vega.community:26657,api7.vega.community:26657"
trust_height = <height for collected block>
trust_hash = "<hash for collected block>"

Example config:

Sample data

Do not use the below block. Select a newer block!

[statesync]
enable = true
rpc_servers = "api0.vega.community:26657,api1.vega.community:26657,api2.vega.community:26657,api7.vega.community:26657"
trust_height = 3040600
trust_hash = "b4b500d8fc84cce3a42b141193db7ba23ff03cc80b70cc817f6536582ebd5eda"

Example config:

danger

Do not use the below block. Select a newer block!

[statesync]
enable = true
rpc_servers = "n00.validators-testnet.vega.rocks:26657,n02.validators-testnet.vega.rocks:26657"
trust_height = 3896400
trust_hash = "9edf8b5779aa79e96ac95256a7c671b855990be518a9c7cbb98eb8694918b004"

4. Start your node​

Start data node

If you are not using Visor, you MUST start your data node before starting the Vega core.

# with Visor
systemctl start vegavisor;

# without Visor
systemctl start data-node;
systemctl start vega;

Your node should start in a several minutes.

info

If you use Visor, you may see the following messages in the logs; please ignore them. It is just Visor checking if node has already started:

Jun 16 22:21:10 vega visor[1876]: 2023-06-16T22:21:10.125Z        DEBUG        visor        visor/visor.go:171        failed to get upgrade status from API        {"error": "failed to call protocolupgrade.UpgradeStatus method: failed to post data \"{\\\"method\\\":\\\"protocolupgrade.UpgradeStatus\\\",\\\"params\\\":[null],\\\"id\\\":8485730894528034258}\": Post \"http://unix/rpc\": dial unix /tmp/vega.sock: connect: no such file or directory"}
Jun 16 22:21:10 vega visor[1883]: 2023-06-16T22:21:10.242Z        ERROR        core.protocol.broker.socket-client        broker/socket_client.go:182        failed to connect, retrying        {"error": "dial tcp 127.0.0.1:3005: connect: connection refused", "peer": "tcp://127.0.0.1:3005"}

5. Revert required after your node has started​

Critical step to avoid corrupted node

This step is critical, otherwise you may end with a corrupted node after next restart or protocol upgrade.

a. Disable statesync in Tendermint config​

Open the <tendermint_home>/config/config.toml file and update the following parameter:

[statesync]
enable = false

b. Disable wiping the data node database​

Open the <vega_home>/config/data-node/config.toml file and update the following parmater:

[SQLStore]
  WipeOnStartup = false

Do not restart your node. You only need to update the config to avoid having issues in future restarts.