search

atomicals / atomicals-electrumx

Electrumx Atomicals Indexer Server
MIT License
186 stars 56 forks source link

too many mints detected in db (1.3.8.4) #109

Closed Mitochondria7 closed 4 months ago

Mitochondria7 commented 9 months ago

using the latest 1.3.8.4 release. After running python3 electrumx_server, the program terminated due the following error

line 2595, in create_or_delete_decentralized_mint_output raise IndexError(f'create_or_delete_decentralized_mint_outputs: Fatal IndexError decentralized_mints > max_mints for {location_id_bytes_to_compact(dmt_mint_atomical_id)}. Too many mints detected in db') IndexError: create_or_delete_decentralized_mint_outputs: Fatal IndexError decentralized_mints > max_mints for 0d5e64d42e4520e17bc204fe25662b0cf2d2a65c350766d6171facaadccb371bi0. Too many mints detected in db

AnyNodes commented 9 months ago

we encountered exactly the same error in v1.3.8.4

atomicals commented 9 months ago

Can you confirm what version you were running before? What if you sync from 808080?

Mitochondria7 commented 9 months ago

Can you confirm what version you were running before? What if you sync from 808080?

I was using 1.3.7.5 previously and it was running fine. After updating to 1.3.8.0 it's still OK. the problem happens after updating to 1.3.8.4 (Or maybe it's because infinite mining was recently activated? ) Also from this error message it's clear that token "infinity" triggers this error.

I'm not super familiar with electrumx server control, would you mind letting me know how to sync from 808080?

AI-Chef commented 9 months ago

same problem with upgrade from 1.3.7.5 => 1.3.8.0 => 1.3.8.4 => 1.3.9.0

AI-Chef commented 9 months ago

Can you confirm what version you were running before? What if you sync from 808080?

I was using 1.3.7.5 previously and it was running fine. After updating to 1.3.8.0 it's still OK. the problem happens after updating to 1.3.8.4 (Or maybe it's because infinite mining was recently activated? ) Also from this error message it's clear that token "infinity" triggers this error.

I'm not super familiar with electrumx server control, would you mind letting me know how to sync from 808080?

if you have no backup before 808080, you can download snapshot from https://github.com/atomicals/atomicals-electrumx/releases/tag/v1.3.7.5

AnyNodes commented 9 months ago

I tried to index from block 807483 again. After sync up, the issue is gone.

MatrixA commented 9 months ago

I tried to index from block 807483 again. After sync up, the issue is gone.

would you tell me how to do that, you mean totally resync from the beginning? or does it have the command such as reindex from specific block?

AI-Chef commented 9 months ago

I tried to index from block 807483 again. After sync up, the issue is gone.

me too, resync solved.

AI-Chef commented 9 months ago

I tried to index from block 807483 again. After sync up, the issue is gone.

would you tell me how to do that, you mean totally resync from the beginning? or does it have the command such as reindex from specific block?

if you have no backup before 808080, you can download snapshot from https://github.com/atomicals/atomicals-electrumx/releases/tag/v1.3.7.5

fishTsai20 commented 9 months ago

Can you confirm what version you were running before? What if you sync from 808080?

how to reindex from block 807483. can this set in env or cmd?

AnyNodes commented 9 months ago

Can you confirm what version you were running before? What if you sync from 808080?

how to reindex from block 807483. can this set in env or cmd?

Basically you need to download the snapshot, replace your local electrumx db files with the snapshot.

The step 2 in this guide is how we download the 807483 snapshot and sync from 807483 block height. It is a snapshot saved on iCloud. https://docs.anynodes.org/nodes/mainnet/bitcoin/atomicals/atomicals-electrumx

Next time when we need to re-sync again, we will try the 808080 snapshot and update the guide.