-
Notifications
You must be signed in to change notification settings - Fork 113
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
After submit block, AION node has no result. #1158
Comments
So for your case in the kernel basically only 2 scenarios could happen. The kernel chain database just re-branching (follow the network highest chain). We can fix this issue in the next release (By returning the meaningful log) The kernel will cache the last 64 mining block templates (we use LRU map to drop the aged block template), but it’s unlikely to happen unless the pool software is too aggressive to request the block mining info from the kernel under some misbehave settings. |
After upgrading to 1.6.1, this problem became more serious.Abnormal log:20-12-09 09:42:06.082 DEBUG API [XNIO-1 task-25]: <request mth=[submitblock] params=["00000000000000000000000000040e2b00000033000000000000000042010000","00b37fc49c08d157a3 Normal log:20-12-09 09:59:32.469 DEBUG API [XNIO-1 task-9]: <request mth=[submitblock] params=["000000000000000000000000000452b00000005a000000000000000076020000","001fefdf9ba48500a0d 20-12-09 09:59:32.469 INFO API [XNIO-1 task-9]: Unable to submit block via api <num=7387860, hash=d565be, diff=9624550, tx=0>20-12-09 09:59:32.469 DEBUG API [XNIO-1 task-9]: <request mth=[submitblock] rpc-process time: [531.2 μs]> After submit_block, the result should be returned: Unable to submit blockOR block submitted via apiBut, often there are neither of these. I looked at the source code of node, the function is: public boolean submitBlockNeither logSealedBlock nor logFailedSealedBlock is executed, but it returns true. So why does this happen? Can this problem be solved? |
Description
When my pool submit a solution, node should print the log:
block submitted via api OR
Unable to submit block via api.
But it is often the case that the node does not follow.
So, the block I dug out became a orphan block.
Why does this happen? Can this problem be solved?
System Information
I'm running:
The text was updated successfully, but these errors were encountered: