Update Your Ethereum Client if You are Using Geth

20 Aug
2015

geth-updated-116522-fix

Ethereum has multiple options for clients that you can run in order to have your wallet and operate with Ether (ETH) coins as well as to have access to the network. This allows users to choose what client works best for them and what they prefer to stick with and can also help with issues like with the fork of the network earlier today. There was a consensus issue that occurred on the Frontier network at block 116522, mined on 2015-08-20 at 14:59:16+02:00 that has affected geth implementations up to and including versions 1.0.1, 1.1.0 and develop (“unstable 1.1.0”), while eth (C++) and pyethereum (Python) were unaffected. There was a fix released for the affected Ethereum clients released shortly after and users are required to update their geth client (source) if they are running it .

Since geth is our preferred Ethereum client software and we have been using it for our guides as well, if you also rely on geth you should update it with the fixed version of geth 1.0.2. We have provided a fixed Windows binary in our mining package below that you can download and update on your system. All you have to do is to stop the old client, replace the old geth.exe with the new one provided and run the new geth client software and you should be just fine. After the update it is Ok for you to see an error message like the one marked in red on the screenshot above, this is normal and the error message should disappear after a while when all clients update to fixed version of geth. You are seeing the error message as you are getting connected to a peer with an older version of geth, so once there are no more peers with the older non fixed version the message alert which will resolve itself. Exchanges and pools should update very soon if they have not yet updated to the fixed clients and should resume their normal operation, though there could be some delays in transactions and some issues with transactions sent during the problem with the network.

Download the fixed version of the geth client compiled for Windows and ready to be used…



Other Similar Publications:

2 Responses to Update Your Ethereum Client if You are Using Geth

Mr.X

August 21st, 2015 at 18:08

Today i download the new geth and became this?

I0821 18:07:44.634261 7428 downloader.go:254] Synchronisation failed: hash fe
tching canceled (requested)
I0821 18:07:47.397419 7428 chain_manager.go:660] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 8.0005ms. #78456 [1d9c0234 / 1d9c0234]
I0821 18:07:59.045086 7428 chain_manager.go:776] Bad block #78457 (c12830934f
c169871406f9b28516159460804fca739e181115be3856c5a128e1)
I0821 18:07:59.126090 7428 chain_manager.go:777] invalid merkle root. receive
d=cfbee37cf38456703df6ed4127d8114b157041c8f2d254e4f6b51ba08e663286 got=0202d738d
9612c211609d35cc1b4d62b6abce0e9b854a566a4f5c484d6f85391
I0821 18:07:59.221096 7428 downloader.go:254] Synchronisation failed: hash fe
tching canceled (requested)
I0821 18:08:00.739183 7428 chain_manager.go:660] imported 0 block(s) (0 queue
d 1 ignored) including 0 txs in 8.0005ms. #78456 [1d9c0234 / 1d9c0234]
I0821 18:08:00.813187 7428 chain_manager.go:776] Bad block #78457 (c12830934f
c169871406f9b28516159460804fca739e181115be3856c5a128e1)
I0821 18:08:00.814187 7428 chain_manager.go:777] invalid merkle root. receive
d=cfbee37cf38456703df6ed4127d8114b157041c8f2d254e4f6b51ba08e663286 got=0202d738d
9612c211609d35cc1b4d62b6abce0e9b854a566a4f5c484d6f85391
I0821 18:08:00.815187 7428 downloader.go:254] Synchronisation failed: hash fe
tching canceled (requested)

admin

August 21st, 2015 at 19:44

That is weird, works just fine here. It seems that you are way behind on the chain synchronizing at block 78457. It is possible that the fix for the problematic block 116522 could be interfering with some older blocks. You can try with a newer version from the development chain to see if the problem will persist: https://build.ethdev.com/builds/Windows%20Go%20develop%20branch/

If this does not help you can get back to an older version, get up to the block of the fork and then update to the latest version, this is confirmed to work already. Another possible alternative would be to delete the local blockchain data and download it again (make sure you backup your wallet).

Leave a Reply

Your email address will not be published. Required fields are marked *

top