This chapter will introduce the solutions to common problems that may be encountered when using the BCF.exe version of the Biological Chain Forest data center. If you encounter a problem that is not listed in this chapter, please contact the BCF team (email address: service@bfmeta.org) for more support.
The data in the following folders are all important data, the details are as follows:
chaindata folder: chaindata saves all the data of the current node's blockchain.
logs folder: logs saves the running log of the current node. For the description of the log file, please refer to the noun explanation<log file name and content description>.
backup folder: backup saves the key checkpoint data, which is used to quickly start or restore the node. If the data in this folder is lost, the node can still start normally, but it will take more time to rebuild the area Block chain.
If users want to reset the blockchain, they can delete the directory chaindata and all the files in the directory.
If users want to change the log level displayed in the log file under logs, they can set the log level on the node. The specific steps are as follows:
/installation directory/conf/bfm-config-testnet.json. Modifying the parameters consoleLogLevel and fileLogLevel can realize the function of adjusting the log mode of console output and file output.
There are 3 types of log levels:
info: Information mode, provides the most effective information prompts, so that users can clearly understand the current running status of the node and the running process;
warn: Warning mode, the information in the information mode will no longer be output, only warning and error messages will be output;
error: Error mode, only output information about errors during node operation.
We recommend using the info mode, so that you can understand the running status of the node, and also capture errors that occur during the node's operation.
The following describes how to implement node automatic voting function
Modify the configuration file before running to realize the automatic voting function
Modify the configuration file, the configuration file path: /installation directory/conf/
Official network configuration file \bfm-config-mainnet.json\
Test network configuration file bfm-config-testnet.json\
Modify the enable configuration to true, and run it after saving it to realize the automatic voting function.
Automatic voting parameter description
| Parameter name | Parameter description | Parameter content description |
|---|---|---|
enable |
Whether to activate the automatic voting function | true: activate the automatic voting function false: do not activate the automatic voting function |
useConfigFee |
Whether to use configuration file setting fee | true: use configuration file fee false: do not use configuration file fee |
fee |
Default voting fee | Default voting fee for each voting event |
numberOfcheckTrsBlock |
The number of event confirmation blocks | The number of confirmation blocks for each voting event. If there is no confirmation vote for blocks exceeding this number, the vote will not be retryed |
maxNumberOfRecommended |
The upper limit of the number of recommended voters selected each time | The number of recommendations is between 0-maxNumberOfRecommended |
numberOfRounds |
Candidate recommender's selection round range | The selected end height is: if the current round is the first round, the end height is the latest block height, if it is greater than the first round, the end height is the previous one The last block of the round; the selected starting height: if the current latest block height is greater than the number of blocks calculated by numberOfRounds, the starting height is the latest block height-numberOfRounds * The number of blocks in each round, if the latest zone If the block height is less than or equal to the number of blocks calculated by numberOfRounds, the starting height is 2 (a block with a height of 1 is the genesis block packaged by the genesis account and is not included in the recommended list) |
productivityPercent |
The proportion of account online rate when calculating candidate recommenders | The number of recommenders selected according to the online rate ranking is: the total number of candidates * numerator/ denominator |
forgedBlocksPercent |
When calculating candidate recommenders, the proportion of account block number | The number of recommenders selected according to the number of blocks is: the total number of candidates * numerator/ denominator |
After running, modify the configuration file to realize the automatic voting function
According to the automatic voting field of <Set node configuration information>, the configuration information can be dynamically adjusted during the operation of the node. As shown in the figure below, you can turn on automatic voting.
TCP: Each chain uses a blockchain port by default. For BCF, the official network is 22000 and the test network is 19000. In addition, in order for the program to run normally, it is recommended to reserve the last ten ports of this port for use, such as 19000-19010. Open the configuration file of the chain that needs to be run. There are port configurations at the top of the file. If these ports conflict with other programs that the current node has started, you can configure them yourself. For details, please refer to the port configuration of <Configuration file description>.
UDP: Due to the existence of stunserver, udp ports of 49152-65535 need to be configured.
The following explains how to configure the ports that are open to the outside world.
Use the firewalld that comes with Centos7 for firewall configuration:
Open the tcp port of 22000-22007:
firewall-cmd --permanent --zone=public --add-port=22000-22007/tcpOpen the udp port of 49152-65535:
firewall-cmd --permanent --zone=public --add-port=49152-65535/udpRefresh the configuration to make it effective imimagestely:
firewall-cmd --reload
The following introduces several ways to check whether the node is running normally
Use <Get node status interface> to check the status of the node.
Use <Get current latest block of local node> to observe whether this node can maintain the same height as other nodes, If possible, the node is operating normally.
According to the log, check the log of the blocking process and search for the "error" keyword. If there is no error, the node is running normally. In general, when a node has an unrecoverable error, it can be reflected in the block process log. For details, please refer to <Log file name and content description>.
If the genesis block does not match as shown in the figure below, please check whether your genesis block matches. If the genesis block does not match, please specify your genesis block again. If you want to re-run a new chain, please uninstall and delete the data directory and reinstall it before using it.
If there is an error on the interface as shown in the figure below, it means that the node authorization has expired. Please contact the BCF team (email address: service@bfmeta.org) to re-authorize.
If there is an error on the interface in the following figure, it means that the node authorization is about to expire. Please contact the BCF team (email address: service@bfmeta.org) to obtain a new authorization before it expires.
