-
Notifications
You must be signed in to change notification settings - Fork 13
tzindex path change leads to broken data #51
Comments
Hi, I think the problem is unrelated to changing the path. It looks like your I'm interested: Did you use the TzIndex snapshot feature to create a backup copy. If yes, then this could be a bug in this feature. |
hi, nope, no backup. Docker container was stop with 60sec grace time and sigint. I do have filebackup, can I somehow check that state.db for corruption? |
You could use I have checked code paths for saving chaintip & indexer tips and found both pieces are not atomic. Moreover in combination with snapshots this will lead to a broken statedb. I have a fix ready soon, but this won't help with your current database unfortunately. |
hey,
situation:
we had data in
/somedir-tzindex
... I've stopped tzindex (17.0.1), moved to/some-dir/tzindex
, changed mount volumes in docker etc (it's/some-dir
to/data
) and restarted... it ended up withrunning params:
if I remove all the .db files in that folder and restarted tzindex, it works - and creates all the same files ("just" empty)..
The text was updated successfully, but these errors were encountered: