评论(0) 浏览量(187)

Q: How can make sure that the node have accessed the blockchain normally?
A: Under the catalogue of peersafed.exe,open the command prompt,enter peersafed.exe  server_info,and make sure complete_ledgers is not empty but like the form of ‘1-100’ in the response.

Q: Wether it can write data on the chain, and not configure on the local database connection?
A: Yes. There is no local database connection in default state, but it should configure when query a table.

Q: How to configure the sync tables?
A: Modify sync tables in configuration files, input addresses of tables owners,tables names,the time point that needs to be synchronized or LedgerIndex,you can refer to relevant specific configurations.

Q: Why no real table generated in the database during create table operation?
A: 1> Check whether the setting below sync db in the configuration file is correct;
    2>Check whether created database type specified by db parameters under sync_db;
    3> Check whether the local node has accessed the blockchain;

Q: What is SyncTableState?

A: SyncTableState is a kind of synchronous state table, mainly records the synchronous index information. Users need to focus the correspondence between the stored TableName and real TableNameInDB after hashing.

Q: Why is the table name in the database inconsistent with the table name created?
A: The table name in the database is processed by Hash, and you can find the correspondence with table names inputed by users in SyncTableState table.

Q: How to check the data in synchronized table?
A: Open SyncTableState table, find corresponding real name of table name, and then find the corresponding real name.

Q: Why can’t find table configured under sync_tables in database?
A: 1> Check whether the stable is really created successfully;
    2> The corresponding ledger serial number of generate tables is very large,and synchronizing a new table needs to start researching from the serial number of 1;so it need wait for a while.
    3> Make sure the database is in the normal work;

Q: Is it possible to watch the table without configuration reboot?
A: Open automatically synchronous switch in the configuration file(set as 1).

Q:How to make sure the database work normally?
A: Open synctablestate to check whether all the LedgerSeq are updating.

Q:Why always no response after I sent the API command?
A: 1>Check whether the network status is good;
    2> Whether the firewall of target points is open;
    3>If the status of target points firewall is open, confirm that whether port 6006 is disabled by the firewall;

Q: Why the node can’t connect the blockchain?
A: Confirm whether the IP and port under configuration file , validators and validation_quorum are correct.

Q: Why did not return any content when execute the select API interface?
A: 1>Confirm whether SQL statement is correct;
    2> Confirm whether executive table is really exist;
    3> Confirm whether there is a table in the local database. The select operation is directly to search the local database operation, and not to access data in the blockchain.

Q: Can I modify the forms created by other users?
A: Yes, founder needs to give users the corresponding authorization.

Q: Why do some tables not update anymore in SyncTableState after start the local node?。
A: Confirm during the down time of this node, whether the founder has changed the name or sets corresponding the signal of deleted as 1.

Q: What is the brief introduction of the ChainSQL database operations process?
A: ChainSQL will check the legitimacy and authority of the operation locally, after the check passed then write to the local database by transaction, then send operation to blockchain to participate in the consensus. Commit the transaction after consensus, otherwise the transaction will be rolled back.

Q:What kinds of circumstance will firstly importing and then consensus?
A: When the table that users want to synchronize has caught up with the progress of the entire network, the write operation of this node for the table will be first import to local database, and then have consensus on the chain. If the result of consensus is not the same with expectation, go back to the write operation and do normal synchronization process. This function is opened by default, it can set value of firststorage as 0(off) to close.