-
Notifications
You must be signed in to change notification settings - Fork 676
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
FATAL: called a nakamoto function outside of epoch 3 #5502
Comments
Hey, thank you for reporting this! Do you happen to know the node's last reported Stacks and Bitcoin block heights? Also, do you happen to have logs from the node from right before the crash? Were you running a genesis sync, or were you booting from a chain snapshot. Thanks in advance! |
Of course, there is a response from API about latest blocks: "server_version": "stacks-blockchain-api v8.2.2 (master:c75e9fb15)",
"status": "ready",
"pox_v1_unlock_height": 781552,
"pox_v2_unlock_height": 787652,
"pox_v3_unlock_height": 840361,
"chain_tip": {
"block_height": 128620,
"block_hash": "0x6a90c750c89a29e7be4e3678a5d84eb14808d018300bcc20fee2fce37f8bb2bd",
"index_block_hash": "0xfca14f7824785316d82598bf23e61a6d5e96114fdf81f291d0b0926be3b5f2ec",
"burn_block_height": 816867
} And here is a full log with information before the crash:
Yes, I'm running a genesis sync, using bootstrap nodes:
Is there any chain archive that I can just download and unpack? |
Yes, please see https://docs.hiro.so/stacks/archive/guides/stacks-blockchain |
Describe the bug
On running Stacks node using docker with image release:3.0.0.0.3 node crashes with panic:
FATAL: called a nakamoto function outside of epoch 3
Steps To Reproduce
It is not clear if it is reproducible or not. However, the suggestion to resync the node to try reproducing it could be challenging at the moment due to the node's slow syncing speed
Environment (please complete the following information):
Additional context
Logs:
The text was updated successfully, but these errors were encountered: