synchronization – What ought to I do about these messages in Bitcoin-core’s debug-log?

0
7


These messages could also be complicated, however there may be nothing improper. Let me go over them:

FlushStateToDisk: write cash cache to disk (cash, kB) accomplished (s) , OK

Because of this the contents of the validation state cache is written to disk. With out this, you’d want to begin over if Bitcoin Core have been to shutdown uncleanly (e.g. your machine crashing or energy loss).

This repeatedly occurs sometimes, or when the cache grows too large (see additional).

Imported mempool transactions from disk: X succeeded, X failed, X expired, X already there, X ready for preliminary broadcast

It is a log message informing you about the results of unconfirmed transactions being loaded from disk.

Cache measurement () exceeds whole area ()

That is giving the explanation why the validation cache state is being written to disk: the quantity saved in reminiscence grew bigger than how a lot reminiscence Bitcoin Core was configured to make use of. That is regular. You’ll be able to let Bitcoin Core develop the cache larger utilizing the -dbcache command line choice, the dbcache= configuration file choice, or the “Database cache” setting within the GUI.

ERROR: AcceptBlockHeader: prev block not discovered

A peer gave you a block header which Bitcoin Core could not interpret. Bitcoin Core merely ignores this.

Disconnecting outbound peer XXX for outdated chain, greatest recognized block =

A peer gave the impression to be on an invalid or outdated block, and did not appear to synchronize with what your Bitcoin Core believes to be the very best chain. There’s both one thing improper with that peer, or it is not following the identical guidelines. In both case, it isn’t a peer we’ll be taught something helpful from. As a result of the variety of connections Bitcoin Core makes is proscribed, it determined it is higher to disconnect this ineffective peer to create space for one more, probably higher, peer.

ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000XXX…XXX, bad-diffbits, incorrect proof of labor

A peer gave you an invalid block header. It’s ignored.

What do I’ve to do?

Nothing.

LEAVE A REPLY

Please enter your comment!
Please enter your name here