Skip to main content

Problem Removal

Programme Configuration​

Compiler failure​

You need to make sure that the dependency libraries are complete and check that all necessary libraries are installed. If you are missing libraries, you need to download the appropriate libraries. If some of the libraries report errors, you can delete the relevant compiled libraries and compile them again.

Handling bz2 libraries: If you have a bz2 library, you need to enable it, in the CMakeLists.txt file.

target_link_libraries(${PROJECT_NAME} bz2)

If you don't have the bz2 library, you can comment out this line:

#target_link_libraries(${PROJECT_NAME} bz2)

Programme start-up failure​

Insufficient number of file opens due to an oversized database​

	Checking the number of file opens with ulimit -n
	You can temporarily change the number of file opens to 65535 with ulimit -n 65535.
	It can also be changed permanently by
	Edit the /etc/security/limits.conf file to set file descriptor limits for specific users or for all users.

The database version is not correct​

You can delete the database, go to the official website and re-download the new database, or restart and wait for the data to be downloaded from zero sync.

Configuration file problem​

Check the format and version of the config configuration file. You can delete the config file, restart the programme to automatically generate a new config configuration file, and then configure it.

Node software version incompatibility or incomplete installation​

Check the version of the programme to make sure that you are using a version that is suitable for the required environment, e.g. a normal machine programme version will not start on a mining machine.

Dependent libraries or environment variables are not set correctly​

Dependency libraries and environment variables are set to ensure that all dependency libraries have been installed correctly and that environment variables have been configured correctly.

Node cannot join the network​

Problem with config file​

Check the IP, port, and scout node configurations in the config file, you can delete the config file and restart the program to automatically generate a new config file for configuration.

Node connects and disconnects from the network​

Check if you are using duplicate accounts. If you have multiple accounts that are used in different nodes, make sure that each account can only be used by one node. You cannot use the same account for multiple nodes.

Network misconfiguration or firewall blocking​

Configure firewall rules to allow node port communication.

Transaction Failure​

Network problem:​

Ensure that the node has a stable network connection and access to the Internet. There are no network blocks or delays, and ensure that the network bandwidth is sufficient to support high-frequency trading and data transfer.

Transaction Parameter Issues​

Check that the transaction parameters meet the specified requirements. For example, make sure that the transmitted address is in the correct, the transaction amount is within the allowable range, and the Gas fee is set reasonably.

Program version inconsistency​

There may be large differences between different versions of the programme, leading to compatibility problems. You can query the programme version of your own node and other nodes through the GetVersion method in the Ppc interface to ensure that it is consistent with the programme version of other nodes.

Insufficient account assets​

Insufficient account assets may result in insufficient transfer amount or Gas charges, which in turn may cause the transaction to fail. Account assets can be queried via menu option 7 or the GetBalance method in the Rpc interface to ensure that there are sufficient funds in the account to avoid transaction failure.

Node height not synchronized​

Node heights that are not in sync with the network-wide nodes will result in nodes not being able to do up trades, query the height of the node via menu option 7 or query the height of the node via the GetBlockNumber method in the interface. If the height of the node is not consistent, wait until the node synchronisation is complete before making the transaction

Nodes are not delegated and staked​

If the node joins the network after the 500 height of the nodes in the whole network, it needs to be delegated and staked before the transaction can be done. You can delegate and stake by using option 2 and option 5 in the menu.

Failure to trade directly after node start-up​

Nodes need time to establish connections and register with other nodes before trading after the programme starts, about 100 seconds to ensure that the connections and registration between nodes are complete before trading can begin.

Successive transactions lead to transaction failure​

Transactions take time to be uploaded to the chain, usually 1-5 seconds (depending on the network). Executing transactions consecutively within a short period of time may result in failure. It is recommended that each transaction is successfully uploaded before proceeding to the next transaction. You can query whether the transaction is successfully uplinked through the ConfirmTransaction method in the Rpc interface.

Insufficient hardware resources​

Insufficient hardware resources where the node is located, such as insufficient CPU, memory, or storage space to handle the computation and storage requirements needed for the transaction. To increase the hardware resources of the node to ensure sufficient computing power and storage space.

Contract trading issues​

Check whether the contract deployment and contract invocation parameters are correct, and ensure that the contract byte code is correct.

Node time inconsistency​

The system time of the nodes is not synchronised, which will lead to transaction failure. Ensure that the system time of the nodes is consistent with the network time by configuring the NTP service. You can use the following command to update the time:

ntpdate Pool.ntp.org

Nodes are not synchronised​

If the node is not synchronised to the highest height for a long time, it may be that the node fails to read data from its own database, you can delete your own database, go to the official website to download the latest database, or start synchronising from zero.

Other​

If the programme opens without a menu

Start the programme with the -m parameter: make sure that the programme starts with a menu displayed.

Rpc interface use error

Make sure that RPC uses Post requests with the correct json format and that the port matches the http port in the config file.

Logging off and on

If you want to view logs, there is an option to enable logging in the config configuration file and you can set the logging level to view and analyse the log files.