Skip to content

Instantly share code, notes, and snippets.

@holiman holiman/veox.md Secret
Created Nov 27, 2018

Embed
What would you like to do?

From parsing the log provided by @veox, during the stureby reorg. Logs <-- warning, large)

Restarts:

INFO [11-24|22:20:38.916] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

INFO [11-24|22:41:09.347] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

INFO [11-24|23:50:06.221] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

INFO [11-25|14:20:07.069] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

INFO [11-25|18:35:02.858] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

INFO [11-26|23:29:52.627] Starting peer-to-peer node               instance=Geth/v1.8.15-stable-89451f7c/linux-amd64/go1.10.3

Then mining started, and continued until a bad block at 40000 First there were many bad blocks which were all 40000. First one at 08:59

Then you got this, several hours later (11:51). Meanwhile, you're mining away at 40134 (on a 1.8.15)

########## BAD BLOCK #########
Chain config: {ChainID: 314158 Homestead: 10000 DAO: <nil> DAOSupport: false EIP150: 15000 EIP155: 23000 EIP158: 23000 Byzantium: 30000 Constantinople: 40000 Engine: ethash}

Number: 33633
Hash: 0x1271ed57084f99df03afd1057f1c3290fab15e98c02b96d1f01dff6e9a3969c1


Error: invalid merkle root (remote: dccc3b603ec9152c749f2cd719528f8cf212c0fc8442c5c183b92aa686b1c752 local: bddd93e57c71df00ca3c7da1bc1a375dd71be3c66b681d5d02961716150f9fbd)
##############################

And that is truly odd, because two days earlier you had already imported that block:

INFO [11-25|20:41:15.786] Imported new chain segment               blocks=1    txs=0  mgas=0.000 elapsed=5.608ms   mgasps=0.000 number=33633 hash=1271ed…3969c1 cache=381.98kB

And some minutes later, anoter one:

ERROR[11-27|11:57:54.309] 
########## BAD BLOCK #########
Chain config: {ChainID: 314158 Homestead: 10000 DAO: <nil> DAOSupport: false EIP150: 15000 EIP155: 23000 EIP158: 23000 Byzantium: 30000 Cons
tantinople: 40000 Engine: ethash}

Number: 38964
Hash: 0x1b29fa9a3faecf1b19d6d45d262b96a148370f8fe62050583b2416c3acc31b52
	&{[] 1 21000 [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] [] [98 33 190 109 69 159 
205 81 237 219 27 207 191 200 9 11 226 20 199 131 224 188 12 238 145 48 191 148 22 153 60 225] [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] 210
00}

... receipts...

Error: invalid merkle root (remote: 3b2f1e86301002923b66841487f667a73c6c65d9faa6b984e9256aed3d321806 local: 8474d43f2c24d039350fb472ad201a78
d961e6c51e27b27262bdd8adeeab3224)
##############################

The actual blocks that were reported as bad, were:

Number: 29763
Number: 30443
Number: 30467
Number: 31386
Number: 31673
Number: 31922
Number: 32277
Number: 32860
Number: 33255
Number: 33487
Number: 33633
Number: 34227
Number: 34289
Number: 34430
Number: 34658
Number: 34675
Number: 34809
Number: 34843
Number: 35067
Number: 35179
Number: 35181
Number: 35417
Number: 35465
Number: 35532
Number: 35873
Number: 36368
Number: 36384
Number: 37103
Number: 37210
Number: 37408
Number: 37415
Number: 38118
Number: 38355
Number: 38719
Number: 38964
Number: 39598
Number: 39930
Number: 40000

@veox

This comment has been minimized.

Copy link

veox commented Nov 27, 2018

Note: my local time zone is UTC+2.

@veox

This comment has been minimized.

Copy link

veox commented Nov 27, 2018

The restarts might look like unexpected crashes, but they're not.

This was running on "bare metal" (my workstation), an Arch Linux machine, and for some reason that's how the distro-provided binary responds to CTRL+C.

I've had to shut the node down several times, since it was using the port number and socket location that a few other applications were expecting to be main-net.

(I now regret not having set up a run-of-the-mill Ubuntu VM, especially since I could've cloned one from the parity VM that I was also running.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.