Fullnode working on testnet takes in the wrong chain

Technical Support
1

I upgraded the version to v0.21.2 and tried to resync all blocks for the extension blocks.

what I did

rm -rf blocks
rm -rf chainstate

./litecoind -conf=./litecoin.conf

config is the following

testnet=1
server=1
txindex=1

[test]
rpcbind=127.0.0.1
rpcbind=*******************
rpcallowip=0.0.0.0/0
rpcuser=*******
rpcpassword=*******
rpcport=*******
port=*******

rpcworkqueue=32767

zmqpubhashblock=tcp://=*******************
zmqpubrawtx=tcp://=*******************

but got the following log

2022-05-17T10:45:35Z UpdateTip: new best=21a7e837ad9f7d3dbd2e5e323dda616f2b911f3220e1a638a865c13c8059dbc7 height=2330170 version=0x20000014 log2_work=55.258820 tx=5877447 date='2022-05-17T10:45:07Z' progress=1.000000 cache=0.0MiB(48txo)
2022-05-17T10:46:10Z UpdateTip: new best=63f77dd71609983adef87b3478d4b3093d2692a230d2a7ddc00d116ae8b69338 height=2330171 version=0x20000014 log2_work=55.258822 tx=5877449 date='2022-05-17T10:45:34Z' progress=1.000000 cache=0.0MiB(49txo)
2022-05-17T10:46:50Z UpdateTip: new best=d84523d915b20592338f66af089f11dade3b530c8aa88c7c936491b2f84c732b height=2330172 version=0x20000014 log2_work=55.258824 tx=5877451 date='2022-05-17T10:46:10Z' progress=1.000000 cache=0.0MiB(50txo)
2022-05-17T10:47:26Z UpdateTip: new best=32dacb45e2568bba61cdbcc80a21340814544de8ff33c0a98f8b50902398075a height=2330173 version=0x20000014 log2_work=55.258826 tx=5877453 date='2022-05-17T10:46:49Z' progress=1.000000 cache=0.0MiB(51txo)
2022-05-17T10:48:14Z UpdateTip: new best=6b6ce9a6ecb8fa88c39160ae120d7e288436d579b333363561fdd9d1054b41d9 height=2330174 version=0x20000014 log2_work=55.258828 tx=5877455 date='2022-05-17T10:47:26Z' progress=0.999999 cache=0.0MiB(52txo)
2022-05-17T10:49:10Z UpdateTip: new best=31fd5bd73df7c3ecb1694661f356059a53bad0e5cb199a09e717843ebe081fc6 height=2330175 version=0x20000014 log2_work=55.258830 tx=5877457 date='2022-05-17T10:48:14Z' progress=0.999999 cache=0.0MiB(53txo)
2022-05-17T10:49:15Z UpdateTip: new best=b1f684675565f0e65784a8f35cb7478eeab5be4be49798db0ee4eb7f76b52fbd height=2330176 version=0x20000014 log2_work=55.258832 tx=5877459 date='2022-05-17T10:49:10Z' progress=1.000000 cache=0.0MiB(54txo)
2022-05-17T10:50:26Z ERROR: AcceptBlock: mweb-missing, MWEB activated but extension block not found
2022-05-17T10:50:26Z ERROR: ProcessNewBlock: AcceptBlock FAILED (mweb-missing, MWEB activated but extension block not found)
2022-05-17T10:50:26Z Disconnecting and discouraging peer 172!
2022-05-17T10:50:30Z ERROR: AcceptBlock: mweb-missing, MWEB activated but extension block not found
2022-05-17T10:50:30Z ERROR: ProcessNewBlock: AcceptBlock FAILED (mweb-missing, MWEB activated but extension block not found)
2022-05-17T10:50:30Z Disconnecting and discouraging peer 173!

it seems the wrong chain.
could you some advice?

2

As far as I know, someone started mining a fork on the testnet. I recommend asking your question in this Telegram group:

I think it was already answered. Maybe this was the solution, though this was for 0.18.1 nodes, but I did not follow closely:

so open console and run invalidateblock c863de49fba3a52e26758fbd232864110e540ae95c97c6cd55c968d5ccd98a79
That should invalidate the bad fork and if you are talking to 0.21.2 nodes, you will get the right chain

1 Like
3

thank you!
I tried this, but something wrong…

2022-05-18T06:25:58Z CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2022-05-18T06:28:38Z New outbound peer connected: version: 70016, blocks=2330472, peer=85 (full-relay)
2022-05-18T06:30:03Z New outbound peer connected: version: 70016, blocks=2330472, peer=89 (full-relay)
2022-05-18T06:31:00Z UpdateTip: new best=410c2ce37201658c6bb4f9f98f1723da98e39b705b20fcec069c927a939ff331 height=2330473 version=0x20000000 log2_work=55.258987 tx=5878215 date='2022-05-18T06:30:55Z' progress=1.000000 cache=0.0MiB(12txo)
2022-05-18T06:31:00Z CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.

I’ll ask in Telegram.