error message:
########## BAD BLOCK #########
Chain config: {ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Byzantium: 4370000 Constantinople: 7280000 Petersburg: 7280000 Istanbul: 9069000, Muir Glacier: 9200000, Engine: ethash}
Number: 9069000
Hash: 0x072cf1df374159c5f23087750d8a2f3201542da196939ce446ff2c5c390fe5f6
·································································
·································································
·································································
·································································
·································································
Error: invalid gas used (remote: 6395997 local: 6449093)
##############################
WARN [12-10|12:01:11.813] Synchronisation failed, dropping peer peer=106a4c4cba9167bf err="retrieved hash chain is invalid"
environment
Geth
Version: 1.9.7
Architecture: amd64
Protocol Versions: [64 63]
Go Version: go1.13.1
Operating System: Linux
cause:
ethereum update 2.0, starting with block 9069000, found on github that this error
occurs with version 1.9.8 1.9.7
scheme:
updates geth to version 1.9.9. The following provides an update method
centos7 environment
- select the latest version to download geth download address
wget -c https://github.com/ethereum/go-ethereum/archive/v1.9.9.zip
- download good, unzip (no unzip download a unzip)
unzip v1.9.9.zip
- then enter the directory, make geth
cd go-ethereum-1.9.9
make geth
- if make geth for a long time no response, probably is the problem of the network, add a proxy, command line input:
export GOPROXY=https://goproxy.cn
-
and then re-make geth is ok.
-
after loading, check the version of geth. If it is still the original version, delete the original geth command
export PATH=$PATH:~/go-ethereum-1.9.9/build/bin/
$PATH:for your geth command
vim /etc/profile- and then refresh
source /etc/profilecheck the next version should be ok
and then back on track, pull block
Read More:
- SqlSession was not registered for synchronization because synchronization is not active
- The Ethereum private chain is built, and the block information cannot be synchronized. The error is resolved: Node data write error err=”state node failed with all peers(1 tries, 1 peers)
- Hash conflict and four solutions
- Hash verification failed for CDH5.8.2 installation
- Error: can’t access JTAG chain problem solving method
- [Two Sigma OA] Longest Chain
- keytool error: java.lang.Exception: Failed to establish chain from reply
- python root:code for Hash MD5 was not found. Error
- When using freemaker template to get values, an error is reported when the attribute is empty
- Failed to find target with hash string ‘android-25’ in:D:\SDK
- cURL error 60: SSL certificate problem: self signed certificate in certificate chain
- Android Error | Failed to find target with hash string ”android-23′ in…
- Rsync client synchronization error
- An import error is reported in the python. The solution to setting. Pylintrc is invalid
- [error summary] Rsync remote synchronization: error password file must not be other accessible
- Rselenium packet capture chain home network (Part 2: data storage and fault tolerance management)
- The background object of thymeleaf is null, which solves the problem of error when the object is empty to get the property value
- Servicetask synchronization failed to set automatic retrying
- Solution to the segmentation fault of single chain table in C language
- Canal synchronization error target column: name not matched