What Can I Do If the Block Height Is Inconsistent Between Peers Due to Gossip Exceptions?

Run the following command to check the block height of the peer and then compare it with that of other peers. If there is a difference, block retrieving may have stopped or delayed.
peer channel getinfo –c {Channel Name}
Restart the peer and obtain the blocks again. If the fault persists, proceed to steps 3 to 5.
Go to the peer container. In the /etc/hyperledger/fabric/ directory, configure the following parameters in the core.yaml file to synchronize blocks from the orderer to the peer:
```
useLeaderElection: false
orgLeader: true
```
Run the following command to query the process ID of peer node start:
ps –ef
Run the following command to restart the peer process:
kill -9 {pid}

Parent topic: Other Issues

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.