btcd: "REORGANIZE: Block is causing a reorganize" causing btcd to crash on testnet

My testnet instance is crashing repeatedly trying to sync block 1,608,354 with following log CHAN: REORGANIZE: Block 00000000d9356478290d6b51b176e0c7b320e4de22090f5c1f0b4b9ff80cbcae is causing a reorganize.. I’m running 0.20.1 with --addrindex enabled.

Here an excerpt from the logs:

019-11-14 10:36:31.975 [INF] RPCS: RPC server listening on 0.0.0.0:18334
2019-11-14 10:36:32.076 [INF] AMGR: Loaded 8694 addresses from file '/datadrive/btcddata/testnet/peers.json'
2019-11-14 10:36:32.092 [INF] CMGR: Server listening on 0.0.0.0:18333
2019-11-14 10:36:32.092 [INF] CMGR: Server listening on [::]:18333
2019-11-14 10:36:32.106 [INF] CMGR: 5 addresses found from DNS seed testnet-seed.bluematt.me
2019-11-14 10:36:32.118 [INF] SYNC: New valid peer 54.37.194.57:18333 (outbound) (/Satoshi:0.17.1/)
2019-11-14 10:36:32.118 [INF] SYNC: Syncing to block height 1608410 from peer 54.37.194.57:18333
2019-11-14 10:36:32.123 [INF] SYNC: New valid peer 159.65.121.59:18333 (outbound) (/Satoshi:0.18.1/)
2019-11-14 10:36:32.125 [INF] CMGR: DNS discovery failed on seed testnet-seed.bitcoin.schildbach.de: lookup testnet-seed.bitcoin.schildbach.de: no such host
2019-11-14 10:36:32.210 [INF] CMGR: 38 addresses found from DNS seed seed.tbtc.petertodd.org
2019-11-14 10:36:32.557 [INF] SYNC: New valid peer 89.40.14.228:18333 (outbound) (/Satoshi:0.18.1/)
2019-11-14 10:36:32.557 [INF] SYNC: New valid peer 165.227.101.132:18333 (outbound) (/Satoshi:0.18.1/)
2019-11-14 10:36:32.557 [INF] SYNC: New valid peer 52.24.233.86:18333 (outbound) (/Satoshi:0.16.2/)
2019-11-14 10:36:32.557 [INF] SYNC: New valid peer 13.229.242.210:18333 (outbound) (/Satoshi:0.13.2/)
2019-11-14 10:36:32.588 [INF] CHAN: REORGANIZE: Block 00000000d9356478290d6b51b176e0c7b320e4de22090f5c1f0b4b9ff80cbcae is causing a reorganize.
2019-11-14 10:37:28.738 [INF] BTCD: Version 0.20.1-beta
2019-11-14 10:37:28.763 [INF] BTCD: Loading block database from '/datadrive/btcddata/testnet/blocks_ffldb'
2019-11-14 10:37:28.857 [INF] BCDB: Detected unclean shutdown - Repairing...
2019-11-14 10:37:28.882 [INF] BCDB: Database sync complete
2019-11-14 10:37:28.882 [INF] BTCD: Block database loaded
2019-11-14 10:37:28.896 [INF] INDX: Transaction index enabled because it is required by the address index
2019-11-14 10:37:28.897 [INF] INDX: Address index is enabled
2019-11-14 10:37:28.897 [INF] INDX: Committed filter index is enabled
2019-11-14 10:37:28.898 [INF] CHAN: Loading block index...
2019-11-14 10:37:52.094 [WRN] CHAN: Unknown new rules activated (bit 1)
2019-11-14 10:37:52.094 [INF] CHAN: Chain state (height 1608353, hash 0000000000259199d1d9bef707e1894e5216a8db6a5a5b593b6fd5e7df7c90a4, totaltx 52906301, work 562889333512071099
2940)
2019-11-14 10:37:52.243 [INF] RPCS: RPC server listening on 0.0.0.0:18334
2019-11-14 10:37:52.318 [INF] AMGR: Loaded 8694 addresses from file '/datadrive/btcddata/testnet/peers.json'
2019-11-14 10:37:52.320 [INF] CMGR: 38 addresses found from DNS seed seed.tbtc.petertodd.org
2019-11-14 10:37:52.339 [INF] CMGR: Server listening on 0.0.0.0:18333
2019-11-14 10:37:52.339 [INF] CMGR: Server listening on [::]:18333
2019-11-14 10:37:52.342 [INF] CMGR: DNS discovery failed on seed testnet-seed.bitcoin.schildbach.de: lookup testnet-seed.bitcoin.schildbach.de: no such host
2019-11-14 10:37:52.506 [INF] CMGR: 5 addresses found from DNS seed testnet-seed.bluematt.me
2019-11-14 10:37:52.663 [INF] SYNC: New valid peer 34.222.102.24:18333 (outbound) (/Satoshi:0.18.0/)
2019-11-14 10:37:52.664 [INF] SYNC: Syncing to block height 1608410 from peer 34.222.102.24:18333
2019-11-14 10:37:52.675 [INF] SYNC: Lost peer 34.222.102.24:18333 (outbound)
2019-11-14 10:37:52.675 [WRN] SYNC: No sync peer candidates available
2019-11-14 10:37:52.865 [INF] SYNC: New valid peer 13.73.0.194:18333 (outbound) (/Satoshi:0.15.0/)
2019-11-14 10:37:52.865 [WRN] SYNC: No sync peer candidates available
2019-11-14 10:37:52.986 [INF] SYNC: New valid peer 35.240.254.96:18333 (outbound) (/Satoshi:0.17.0/)
2019-11-14 10:37:52.986 [INF] SYNC: Syncing to block height 1608410 from peer 35.240.254.96:18333
2019-11-14 10:37:53.041 [INF] SYNC: New valid peer 103.76.36.113:18333 (outbound) (/Satoshi:0.17.0.1(bitcoin-testnet)/)
2019-11-14 10:37:53.737 [INF] CHAN: REORGANIZE: Block 00000000d9356478290d6b51b176e0c7b320e4de22090f5c1f0b4b9ff80cbcae is causing a reorganize.

It seems to be an issue with only one of my identically configured nodes (Ubuntu 18.04.3 LTS)

About this issue

Original URL
State: open
Created 5 years ago
Reactions: 1
Comments: 16

Most upvoted comments

@cubancorona can you please let me know if you have a fix for the mempool code? Is this something you are actively working on?

Also, I would assume it isn’t just a negative index. Usually go will output that error explicitly!

~/Downloads » go run test.go
panic: runtime error: index out of range [-1]

goroutine 1 [running]:
main.main()
	/Users/joshellithorpe/Downloads/test.go:8 +0x1f
exit status 2

zquestz on Nov 18, 2019