-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“The worker got stuck at a certain block height and kept reporting this error: ‘Failed to fetch seqno 40100000: [Error : 651 : (0,9000000000000000,45432823): ltdb: block not found]’ #73
Comments
Hello, in this case please restart worker. |
Do you know the reason? Do you have a plan to fix this? Restarting is not a long-term solution. |
Yes, the problem is identified and the fix is in #74. It'll be merged to main very soon. Thanks for reporting. |
I had the same problem Whether can modify https://github.com/toncenter/ton-indexer gitsubmodule as soon as possible |
I encountered a similar problem, submitted in toncenter/ton-indexer#79 Can you help me with that |
@duktig666 based on your screenshot you're trying to index old blocks (seqno 340). Make sure that you have archival node. Otherwise use flag |
@dungeon-master-666 So which block should I start indexing? Or how can I find suitable information? I run FullNode+Liteserver, not an archive node. |
With synchronized node you can start safely from the current blockchain state: https://toncenter.com/api/v2/getMasterchainInfo. |
@dungeon-master-666 If start indexing from the current most recent block state, have problems querying historical data. I understand that indexing starts at 1 and needs to run the archive node instead of the full node. That should do it? |
There is still this problem[ 2][t 6][2024-12-16 04:35:41.293204115][IndexScheduler.cpp:142][!indexscheduler] Rescheduling seqno 42992316 There is still this problem |
I can confirm that the node is synchronizing blocks, and I can see that the last_known_seqno is increasing. However, it consistently fails to retrieve the block (0,9000000000000000,45432823), continuously throwing this error until I restart the worker, after which it runs normally. Is this a bug? Could it be fixed quickly, or can you tell me where the problem might be? Many thanks!
The text was updated successfully, but these errors were encountered: