2

Help, with bitcoin core : AFTER the Rescan :

1 - rescan

2 - response output, on the debug file out:

3 - FlushStateToDisk: write coins cache to disk (coins, kB) completed (s) , OK

4 - Imported mempool transactions from disk: X succeeded, X failed, X expired, X already there, X waiting for initial broadcast

problems that I don't understand, problems that I can't solve :

5 - Problem one : Cache size () exceeds total space ()

6 - Problem two : ERROR: AcceptBlockHeader: prev block not found

7 - with => Disconnecting outbound peer XXX for old chain, best known block =

8 - and with => ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000XXX...XXX, bad-diffbits, incorrect proof of work

Sorry for my bad english !

What do I have to do ? Help me Please Thanks !

1 Answer 1

3

These messages may be confusing, but there is nothing wrong. Let me go over them:

FlushStateToDisk: write coins cache to disk (coins, kB) completed (s) , OK

This means that the contents of the validation state cache is written to disk. Without this, you'd need to start over if Bitcoin Core were to shutdown uncleanly (e.g. your machine crashing or power loss).

This regularly happens from time to time, or when the cache grows too big (see further).

Imported mempool transactions from disk: X succeeded, X failed, X expired, X already there, X waiting for initial broadcast

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

Cache size () exceeds total space ()

This is giving the reason why the validation cache state is being written to disk: the amount stored in memory grew larger than how much memory Bitcoin Core was configured to use. This is normal. You can let Bitcoin Core grow the cache bigger using the -dbcache command line option, the dbcache= configuration file option, or the "Database cache" setting in the GUI.

ERROR: AcceptBlockHeader: prev block not found

A peer gave you a block header which Bitcoin Core couldn't interpret. Bitcoin Core simply ignores this.

Disconnecting outbound peer XXX for old chain, best known block =

A peer seemed to be on an invalid or old block, and didn't seem to synchronize with what your Bitcoin Core believes to be the best chain. There is either something wrong with that peer, or it isn't following the same rules. In either case, it's not a peer we'll learn anything useful from. Because the number of connections Bitcoin Core makes is limited, it decided it's better to disconnect this useless peer to make space for another, potentially better, peer.

ERROR: AcceptBlockHeader: Consensus::ContextualCheckBlockHeader: 000XXX...XXX, bad-diffbits, incorrect proof of work

A peer gave you an invalid block header. It is ignored.

What do I have to do?

Nothing.

16
  • 1
    If the problem is that your funds haven't shown up because you're still rescanning or synchronization: yes, they'll only show up when that is done. None of the log messages you quote are related to this at all. May 19 at 17:42
  • 2
    I'm sorry, but I have no idea what you are trying to say or ask. May 20 at 20:56
  • 2
    You just need to wait until it is synchronized. May 21 at 2:58
  • 2
    log2_work is just a metric for the amount of hashrate the chain has had. It has nothing to do with progress of synchronization, nor does it contribute to it. Jun 4 at 19:30
  • 1
    This isn't a discussion box. If you have more questions, ask them as questions, but please be respective of the time and effort of the volunteers who answer here. Please get someone to translate for you, or it'll get only more frustrating for everyone. Jun 28 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.