Shulou(Shulou.com)06/01 Report--

This article mainly explains "how to install and configure EOS". Interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to install and configure EOS.

First, install EOS node software

This article takes ubuntu16.04 as an example to introduce the installation method of EOS node software. Other operating systems can refer to the official website documentation.

1. Download

First, go to the official github to download the latest version of eosio software installation package:

~ $wget https://github.com/eosio/eos/releases/download/v1.6.2/eosio_1.6.2-1-ubuntu-16.04_amd64.deb

2. Installation

Download and install the local package:

~ $sudo apt install. / eosio_1.6.2-1-ubuntu-16.04_amd64.deb

3. Verification

Verify the software version after the installation is complete:

~ $nodeos-- versionv1.6.2 II. Configure EOS node software

First create a new directory as the working environment with an easy-to-understand name, such as:

~ $mkdir eos-main

1. Download the Genesis document of the main website

To connect to the main network, the EOS node needs to specify the creation file genesis.json of the main network when you start nodeos for the first time. You can download this file from the github of CryptoLions:

~ / eos-main$ wget https://github.com/CryptoLions/EOS-MainNet/blob/master/genesis.json

2. Download the configuration file of the main network

CryptoLions also provides the configuration file config.ini for the main network, which is also downloaded locally:

~ / eos-main$ wget https://github.com/CryptoLions/EOS-MainNet/blob/master/config.ini

3. Download the latest list of available nodes

Download the latest list of available EOS nodes from privex.io and save them to the peers.txt file

~ / eos-main$ wget https://eosnodes.privex.io/?config=1-O peers.txt

4. Update the list of nodes in the main network configuration file

In the configuration file config.ini, find all the p2p-peer-address configuration items, such as:

P2p-peer-address = bp.cryptolions.io:9876...p2p-peer-address = mainnet.eoseco.com:10010

Then replace it with the contents of the peers.txt.

III. Start for the first time

When you start nodeos for the first time, you need to specify the creation file and clean up the previous blocks:

~ / eos-main$ nodeos-config-dir. -- data-dir. -genesis-json genesis.json-delete-all-blocks

After startup, you can open another terminal to check the synchronization progress:

~ $cleos get info

The chain_id in the output is shown below as aca376..., which indicates that it has been connected to the main network:

{"server_version": "c8f26078", "chain_id": "aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906", "head_block_num": 3712, "last_irreversible_block_num": 3711, "last_irreversible_block_id": "00000e7f1b9d5b50256654921f5ca8a91aa3168f0c0a3e8ea3bbea1ba5c00fe2", "head_block_id": "00000e80a8c5b9e7acc9c063113668b7eae9025aa38a8c8ac3606df6256086e3", "head_block_time": "2018-06-09T12:29:10.500", "head_block_producer": "eosio", "virtual_block_cpu_limit": 2675279111 "virtual_block_net_limit": 42941084, "block_cpu_limit": 100000000, "block_net_limit": 1048576}

You can compare the head_block_num in the above information with the latest block number on eospark to know the progress of synchronization. When the two are consistent, it indicates that the node is synchronized with the EOS main network.

IV. Stop and restart of EOS nodes

Sometimes you may need to restart nodeos for a variety of reasons, so remember not to force nodeos to be killed and give it a chance to clean up. Nodeos should be notified to exit with the following command:

~ $pkill nodeos

Nodeos that is closed in this way will not have historical garbage, so it will be smooth to start again:

~ / eos-main$ nodeos-config-dir. -- data-dir.

Note that in the second and subsequent startup, do not use the _-delete-all-blocks__ parameter again, or you will start from scratch over and over again!

If you have to kill nodeos forcibly, such as using pkill-9 or restarting the machine while directly running, you will fail to start nodeos again and receive this prompt:

... database dirty flag set (likely due to unclean shutdown): replay required

At this point, we can either delete all blocks (using the-- delete-all-blocks parameter) and start all over again, or replay the transaction, such as hard replay:

~ / eos-main$ nodeos nodeos-config-dir. -- data-dir. -- hard-replay-blockchain

The problem with replay is that it also takes a long time, though it's a little better than deleting all the blocks.

So remember to be gentle when shutting down nodeos.

At this point, I believe you have a deeper understanding of "how to install and configure EOS". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.