Quote from: apogio on January 27, 2025, 06:32:05 PM

Quote from: fairmuffin on January 27, 2025, 02:00:39 AM

So I synced Fulcrum from scratch and now it's stuck like this (for three hours now):

Code:

[2025-01-27 00:42:51.127] <Controller> Processed height: 606000, 68.8%, 18.0 blocks/sec, 38790.7 txs/sec, 136442.5 addrs/sec
[2025-01-27 00:42:51.637] <Controller> Processed 606011 new blocks with 479411650 txs (1178064770 inputs, 1278776241 outputs, 1810346733 addresses), verified ok.
[2025-01-27 00:42:51.637] <Controller> Initial sync ended, flushing and deleting UTXO Cache ...
[2025-01-27 00:42:51.637] <Controller> Storage UTXO Cache: Flushing to DB ...

Looking at the task manager it's not using disk space apparently, and just some memory (RAM) so I think it's safe to stay it's not doing anything? Also the Processed height: 606000, 68.8% makes me think that Fulcrum is aware that my Bitcoin node was stopped at a specific block height that's missing a lot of recent blocks. Not sure what to do with this thing now really, I'd be happy to have it work correctly with up toblock height 606,010 (which is where I have turned connect=0 for my node), but I don't know if that's doable.

You need to wait for flushing to finish. Painful and long, but it will pass. [1]

[1] https://bitcoin.stackexchange.com/questions/116776/why-is-there-a-need-to-flush-the-utxo-set-when-you-prune-blk-dat-and-rev-dat-f

I have restarted the process again but with utxo_cache = 0. I also left my node (while Fulcrum was closed) to sync up to block height 650,543 and then I stopped it again with connect=0. After around 9-11 hours, it's stuck here:

Code:

[2025-01-28 05:03:18.834] <Controller> Processed height: 641000, 72.8%, 5.92 blocks/sec, 13515.6 txs/sec, 58349.8 addrs/sec
[2025-01-28 05:06:15.310] <Controller> Processed height: 642000, 72.9%, 5.67 blocks/sec, 12933.7 txs/sec, 56693.3 addrs/sec
[2025-01-28 05:09:17.796] <Controller> Processed height: 643000, 73.0%, 5.48 blocks/sec, 11590.1 txs/sec, 53866.4 addrs/sec
[2025-01-28 05:11:55.158] <Controller> Processed height: 644000, 73.1%, 6.35 blocks/sec, 13634.1 txs/sec, 60727.5 addrs/sec
[2025-01-28 05:14:34.317] <Controller> Processed height: 645000, 73.2%, 6.28 blocks/sec, 14011.8 txs/sec, 61212.1 addrs/sec
[2025-01-28 05:17:14.472] <Controller> Processed height: 646000, 73.3%, 6.24 blocks/sec, 13882.7 txs/sec, 60763.5 addrs/sec
[2025-01-28 05:20:07.502] <Controller> Processed height: 647000, 73.4%, 5.78 blocks/sec, 12677.3 txs/sec, 56857.9 addrs/sec
[2025-01-28 05:22:45.779] <Controller> Processed height: 648000, 73.5%, 6.32 blocks/sec, 12950.7 txs/sec, 59231.9 addrs/sec
[2025-01-28 05:25:16.626] <Controller> Processed height: 649000, 73.7%, 6.63 blocks/sec, 13106.6 txs/sec, 59100.7 addrs/sec
[2025-01-28 05:27:57.033] <Controller> Processed height: 650000, 73.8%, 6.23 blocks/sec, 13441.1 txs/sec, 59500.2 addrs/sec
[2025-01-28 05:29:20.571] <Controller> Processed 650544 new blocks with 572976592 txs (1411013606 inputs, 1523970373 outputs, 2185459747 addresses), verified ok.

So even if I avoid having it flushing it, it does stop at the block height of my node, but then it does nothing.