Bitcoin sync -> inconsistent db

[RemcoMi]

Bitcoin sync -> inconsistent db

[martinboehm]

This seems to me like a corrupt DB. I would completely clean the /opt/coins/data/bitcoin/blockbook/db folder and start again. However, do expect that the sync will take some time even on a fast hardware, over 1-2 days.

[RemcoMi]

Thanks. Would it make sense to use a higher dbcache (10GB?) and/or more workers to use the resources in a better way?

Even with a fresh start (bulk) after removing /opt/coins/data/bitcoin/blockbook/db, some input tx are not found. Would that mean that transactions are missing in the database? Or are these transactions revisited after other bulk operations are done?
W0817 14:17:03.340849 204853 baseparser.go:38] tx 4a5633ba5380f01f02012ecc6b367a0bbac06ffe1bb49c3608fd8a6b85d2b688, input tx b6825d55d08b5329fb17362c3373981033c6cd545d8a383ef6042f521267b94d not found in txAddresses

[martinboehm]

There should be no such warnings in the log. We just reindexed our Bitcoin and did not get any warnings.
Larger cache will almost certainly improve the situation, however I do not think it will be that substantial.

[RemcoMi]

To be sure, we restarted with 1 worker.
However, this will probably take a couple weeks as it currently (around block 350.000) processes 1.185 blocks/hour..

[martinboehm]

OK. We have no issues running sync in bulk mode, it is able to process about 6k late blocks/hour. The blocks around 350.000 are processed almost immediately.