<p>After an error with LevelDB (corrupted) I did a reindex and after that bitcoind automatically start a new synchronization. This seems much faster some times, it started from genesis and in 1 hour it reached 2015 but it seems strange to me that it's doing a resynchronization... Can anyone tell me if this is normal? Thanks in advance</p>

CC BY-SA 4.0
2023-05-03T12:15:49.193Z
With new “synchronization” do you mean it did a _rescan_, or do you mean that it immediately did another _reindex_? Did you add `reindex=1` to your node configuration? If so, it would do it on every startup.
Murch
CC BY-SA 4.0
2023-05-03T12:20:09.030Z
After the reindex process, it immediately starts with a new sync of the blockchain like the first installation of the node... I do not have this string in my .conf because following a guide I used `txindex = 1`. I am going to edit it but now what I have to do with this? I have to stop it? Thanks
nico
CC BY-SA 4.0
2023-05-03T12:35:59.483Z
`txindex` means that your node keeps an index of where each transaction is found in your blockchain data. It should have no bearing on your reindexing issue. Could you please check the log and see whether there was some information between finishing the first reindex and starting the resync then?
Murch
CC BY-SA 4.0
2023-05-03T12:48:33.330Z
Thanks for the clarification. I no longer have the logs from 24 hours ago, the last one is from this morning but I was at the console when the reindex finished and didn't notice any errors... Could it be a reindex phase? I'll try to explain better: Immediately after the reindex, the same message appeared in the log that appeared during the sync phase with the progress, height and other info... What do you think? Thanks for your patience
nico
<bitcoind><full-node><bitcoin-cli><nodes><reindex>
New resync after a complete reindex
nico
# New resync after a complete reindex

(Asked by: username_0 on 2023-05-03)

After an error with LevelDB (corrupted) I did a reindex and after that bitcoind automatically start a new synchronization. This seems much faster some times, it started from genesis and in 1 hour it reached 2015 but it seems strange to me that it's doing a resynchronization... Can anyone tell me if this is normal? Thanks in advance

**Tags:** bitcoind, full-node, bitcoin-cli, nodes, reindex

> **Comments:**
> **username_1**: With new “synchronization” do you mean it did a _rescan_, or do you mean that it immediately did another _reindex_? Did you add `reindex=1` to your node configuration? If so, it would do it on every startup.  
> **username_0**: After the reindex process, it immediately starts with a new sync of the blockchain like the first installation of the node... I do not have this string in my .conf because following a guide I used `txindex = 1`. I am going to edit it but now what I have to do with this? I have to stop it? Thanks  
> **username_1**: `txindex` means that your node keeps an index of where each transaction is found in your blockchain data. It should have no bearing on your reindexing issue. Could you please check the log and see whether there was some information between finishing the first reindex and starting the resync then?  
> **username_0**: Thanks for the clarification. I no longer have the logs from 24 hours ago, the last one is from this morning but I was at the console when the reindex finished and didn't notice any errors... Could it be a reindex phase? I'll try to explain better: Immediately after the reindex, the same message appeared in the log that appeared during the sync phase with the progress, height and other info... What do you think? Thanks for your patience  

---

## 0 answers

