bitcoin: Can't sync signet using 0.21-rc3
I downloaded bitcoin-0.21.0rc3-x86_64-linux-gnu.tar.gz from bitcoincore.org/bin/… and ran it with no prior .bitcoin folder. Output:
$ ./bitcoind -signet
2020-12-12T15:39:04Z Bitcoin Core version v0.21.0rc3 (release build)
2020-12-12T15:39:04Z Signet derived magic (message start): 0a03cf40
2020-12-12T15:39:04Z Assuming ancestors of block 0000002a1de0f46379358c1fd09906f7ac59adf3712323ed90eb59e4c183c020 have valid signatures.
2020-12-12T15:39:04Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000000000000019fd16269a
2020-12-12T15:39:04Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2020-12-12T15:39:04Z Using RdSeed as additional entropy source
2020-12-12T15:39:04Z Using RdRand as an additional entropy source
2020-12-12T15:39:04Z Default data directory /home/twitch/.bitcoin
2020-12-12T15:39:04Z Using data directory /home/twitch/.bitcoin/signet
2020-12-12T15:39:04Z Config file: /home/twitch/.bitcoin/bitcoin.conf (not found, skipping)
2020-12-12T15:39:04Z Command-line arg: signet=""
2020-12-12T15:39:04Z Using at most 125 automatic connections (1024 file descriptors available)
2020-12-12T15:39:04Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2020-12-12T15:39:04Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2020-12-12T15:39:04Z Script verification uses 7 additional threads
2020-12-12T15:39:05Z scheduler thread start
2020-12-12T15:39:05Z HTTP: creating work queue of depth 16
2020-12-12T15:39:05Z Using random cookie authentication.
2020-12-12T15:39:05Z Generated RPC authentication cookie /home/twitch/.bitcoin/signet/.cookie
2020-12-12T15:39:05Z HTTP: starting 4 worker threads
2020-12-12T15:39:05Z Using wallet directory /home/twitch/.bitcoin/signet/wallets
2020-12-12T15:39:05Z init message: Verifying wallet(s)...
2020-12-12T15:39:05Z init message: Loading banlist...
2020-12-12T15:39:05Z ERROR: DeserializeFileDB: Failed to open file /home/twitch/.bitcoin/signet/banlist.dat
2020-12-12T15:39:05Z Invalid or missing banlist.dat; recreating
2020-12-12T15:39:05Z SetNetworkActive: true
2020-12-12T15:39:05Z Using /16 prefix for IP bucketing
2020-12-12T15:39:05Z Cache configuration:
2020-12-12T15:39:05Z * Using 2.0 MiB for block index database
2020-12-12T15:39:05Z * Using 8.0 MiB for chain state database
2020-12-12T15:39:05Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2020-12-12T15:39:05Z init message: Loading block index...
2020-12-12T15:39:05Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2020-12-12T15:39:05Z Opening LevelDB in /home/twitch/.bitcoin/signet/blocks/index
2020-12-12T15:39:05Z Opened LevelDB successfully
2020-12-12T15:39:05Z Using obfuscation key for /home/twitch/.bitcoin/signet/blocks/index: 0000000000000000
2020-12-12T15:39:05Z LoadBlockIndexDB: last block file = 0
2020-12-12T15:39:05Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=0, size=0, heights=0...0, time=1970-01-01...1970-01-01)
2020-12-12T15:39:05Z Checking all blk files are present...
2020-12-12T15:39:05Z Initializing databases...
2020-12-12T15:39:05Z Pre-allocating up to position 0x1000000 in blk00000.dat
2020-12-12T15:39:05Z Opening LevelDB in /home/twitch/.bitcoin/signet/chainstate
2020-12-12T15:39:05Z Opened LevelDB successfully
2020-12-12T15:39:05Z Wrote new obfuscate key for /home/twitch/.bitcoin/signet/chainstate: 170005111e9356f3
2020-12-12T15:39:05Z Using obfuscation key for /home/twitch/.bitcoin/signet/chainstate: 170005111e9356f3
2020-12-12T15:39:05Z init message: Rewinding blocks...
2020-12-12T15:39:05Z block index 34ms
2020-12-12T15:39:05Z loadblk thread start
2020-12-12T15:39:05Z UpdateTip: new best=00000008819873e925422c1ff0f99f7cc9bbb232af63a077a480a3633bee1ef6 height=0 version=0x00000001 log2_work=22.206105 tx=1 date='2020-09-01T00:00:00Z' progress=0.000064 cache=0.0MiB(0txo)
2020-12-12T15:39:05Z block tree size = 1
2020-12-12T15:39:05Z nBestHeight = 0
2020-12-12T15:39:05Z Failed to open mempool file from disk. Continuing anyway.
2020-12-12T15:39:05Z loadblk thread exit
2020-12-12T15:39:05Z torcontrol thread start
2020-12-12T15:39:05Z Bound to [::]:38333
2020-12-12T15:39:05Z Bound to 0.0.0.0:38333
2020-12-12T15:39:05Z Bound to 127.0.0.1:38334
2020-12-12T15:39:05Z init message: Loading P2P addresses...
2020-12-12T15:39:05Z ERROR: DeserializeFileDB: Failed to open file /home/twitch/.bitcoin/signet/peers.dat
2020-12-12T15:39:05Z Invalid or missing peers.dat; recreating
2020-12-12T15:39:05Z ERROR: DeserializeFileDB: Failed to open file /home/twitch/.bitcoin/signet/anchors.dat
2020-12-12T15:39:05Z 0 block-relay-only anchors will be tried for connections.
2020-12-12T15:39:05Z init message: Starting network threads...
2020-12-12T15:39:05Z dnsseed thread start
2020-12-12T15:39:05Z Loading addresses from DNS seed 2a01:7c8:d005:390::5
2020-12-12T15:39:05Z net thread start
2020-12-12T15:39:05Z init message: Done loading
2020-12-12T15:39:05Z opencon thread start
2020-12-12T15:39:05Z addcon thread start
2020-12-12T15:39:05Z msghand thread start
2020-12-12T15:39:05Z Loading addresses from DNS seed 178.128.221.177
2020-12-12T15:39:05Z Loading addresses from DNS seed ntv3mtqw5wt63red.onion:38333
2020-12-12T15:39:05Z 0 addresses found from DNS seeds
2020-12-12T15:39:05Z dnsseed thread exit
2020-12-12T15:39:06Z New outbound peer connected: version: 70016, blocks=15726, peer=0 (full-relay)
2020-12-12T15:39:06Z Cannot create socket for ntv3mtqw5wt63red.onion:38333: unsupported network
2020-12-12T15:40:06Z Adding fixed seed nodes as DNS doesn't seem to be available.
If I switch back to rc2 it works fine.
I expect rc3 to sync, but it doesn’t.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 30 (23 by maintainers)
178.128.221.177
upgraded to latestaj/202009-signet-generate
(69c6e47a3f929478a7f842ca3880bcae3c28a134)@MarcoFalke that’s a good point, although I think it’d be good to re-test this before final gets tagged to see if there’s a reasonable availability of >=rc3 nodes for the release. I’d prefer to either delay final until signet works reliably or add a warning to the release notes about this possible complication.
Ah this finally makes sense to me. I had already upgraded my two Signet seeds nodes to
rc3
, so I didn’t understand why people were having problems. But I use IPv6 and (flaky) Tor, so folks with IPv4 (@jonatack?) needed @kallewoof to upgrade too. Such decentralized.Thanks @kallewoof. It works for me with rc3 now.
This is expected. Signet doesn’t have a stable p2p network yet and all nodes use pre-release versions, which are incompatible with each other.
It will fix itself as the existing signet nodes upgrade to rc3 and then later to the final release.
If you need to sync in the meantime, you can apply a temporary local patch:
Yes, reproduced. Restarted from rc2, sync returned, then restarted from rc3 and it syncs as well.
Re-tested and it’s now resolved for me as well.
I don’t think issues that strictly only affect test networks should be blocker or need mention in release notes…
One of my nodes (not a hardcoded seed but that’s been around a while) is updated to not disconnect if
sendaddrv2
is received late, which should at least allow the seeds to be updated without risking a netsplit.