APPENDIX A

Documentation

Search…

INTRODUCTION

USERS

DEVELOPMENT ENVIRONMENT

SOFTWARE MANUALS

DEVPORTAL

VALIDATORS

Testnet Installation Guide

Mainnet Connection Guide

Docker-Compose Start-up Instructions

APPENDIX A

APPENDIX B

Golos Blockchain Transit

How to join CyberWay for those who are interested in being validators ?

Stake Usage Guide

Regulations for CyberWay validators. Voting for Validators

APPENDIX A

Procedure for checking the connection of node to CyberWay Mainnet
As soon as the start_light.sh script finishes, you have to make sure that docker-composer and services are working properly on your server. Docker-compose logs process information into its internal file. To get and analyze the logged information you can use the following commands:
1
$ sudo docker logs -f nodeosd
2
$ sudo docker logs -f mongo
Copied!
or (to get a partial information)
1
$ sudo docker logs --tail 100 -f nodeosd
2
$ sudo docker logs --tail 100 -f mongo
Copied!
The options:
--tail — takes the last lines of text;
-f — means that it is necessary to monitor the update log file.
No error messages should be in the logged information.
A1 Monitoring the successful installation
Make sure that the nodeosd and mongo containers are successfully installed. It is recommended to run the following command:
1
$ sudo docker ps
Copied!
Containers are considered to be successfully installed if the following conditions are met:
no error messages in the log file;
the messages about installing containers with the names nodeosd and mongo;
the containers are in running state. 
A2 Monitoring the start of node synchronization
Make sure that the node has initiated block synchronization. The node is considered to have started this process if the log information contains a piece of text like this one:
1
info  2019-10-01T00:28:39.752 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block d7f859397b3f1220... #1214805 @ 2019-10-01T00:28:36.000 signed by kk5oxqhb2ird [trxs: 0, lib: 1214765, conf: 13, latency: 3752 ms]
2
info  2019-10-01T00:28:39.771 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block 9f560026df0a3394... #1214806 @ 2019-10-01T00:28:39.000 signed by yzpsff4dxom4 [trxs: 0, lib: 1214767, conf: 20, latency: 771 ms]
3
info  2019-10-01T00:28:42.038 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block b2141be6f9c671a3... #1214807 @ 2019-10-01T00:28:42.000 signed by 3ukodagt5qrc [trxs: 0, lib: 1214767, conf: 18, latency: 38 ms]
Copied!
The start_block field in the text indicates that the node has started processing blocks.
A3 Monitoring the node working state
Node synchronization process can take a long time. Therefore, you should monitor this process from time to time.
Make sure that the node does not hang. To get node status information, you can use the following command:
1
$ cleos get info
Copied!
The node is considered to be in working state if the received text contains information about processing head_block_num, like this one:
1
{
2
 "server_version": "27be611d",
3
 "chain_id": "591c8aa5cade588b1ce045d26e5f2a162c52486262bd2d7abcb7fa18247e17ec",
4
 "head_block_num": 2419294,
5
 "last_irreversible_block_num": 2419247,
6
 "last_irreversible_block_id": "0024ea2f63a1e7411b75362def0befaf4698235b17956f3d4ec000491f37d5f8",
7
 "head_block_id": "0024ea5e6223f4c8c5fadd87e0cb0e5df04cda7aeb9b8c8c9111b56a0e19e665",
8
 "head_block_time": "2019-11-14T08:17:45.000",
9
 "head_block_producer": "1avnch3wug2o",
10
 "virtual_block_cpu_limit": 1400000000,
11
 "virtual_block_net_limit": 1048576000,
12
 "block_cpu_limit": 1399900,
13
 "block_net_limit": 1048576,
14
 "server_version_string": "v2.0.2-37-g27be611d0"
15
}
Copied!
The head_block_num field indicates a current block being processed by the node.
A4 Monitoring the completion of node synchronization
The node is considered to be successfully synchronized if it began to receive blocks. The log file should contain a piece of text like this one:
1
info  2019-10-01T00:28:39.752 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block d7f859397b3f1220... #1214805 @ 2019-10-01T00:28:36.000 signed by kk5oxqhb2ird [trxs: 0, lib: 1214765, conf: 13, latency: 3752 ms]
2
info  2019-10-01T00:28:39.771 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block 9f560026df0a3394... #1214806 @ 2019-10-01T00:28:39.000 signed by yzpsff4dxom4 [trxs: 0, lib: 1214767, conf: 20, latency: 771 ms]
3
info  2019-10-01T00:28:42.038 nodeos    producer_plugin.cpp:339       on_incoming_block    ] Received block b2141be6f9c671a3... #1214807 @ 2019-10-01T00:28:42.000 signed by 3ukodagt5qrc [trxs: 0, lib: 1214767, conf: 18, latency: 38 ms]
Copied!
The on_incoming_block field indicates an incoming block being received by the node. Also, make sure that the log file contains information about the latency parameter with time less than 3000 ms.
Conclusion
The node is considered to be successfully synchronized, if the log file contains information similar to the one in this appendix.

Docker-Compose Start-up Instructions

APPENDIX B

Last modified 2yr ago

Copy link

Contents

Procedure for checking the connection of node to CyberWay Mainnet

A1 Monitoring the successful installation

A2 Monitoring the start of node synchronization

A3 Monitoring the node working state

A4 Monitoring the completion of node synchronization

Conclusion