Buy crypto anonymously on the Incognito pDEX   

[Solved] How to fix "intermediate block not recorded" error?

#1

This is a freshly synced vnode, and in the log it is reporting the follow error:

2021-05-20 09:25:27.158 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1215705; new height is 1221439, shardID 7
2021-05-20 09:25:28.378 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1216071; new height is 1221826, shardID 1
2021-05-20 09:25:28.598 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1213798; new height is 1219555, shardID 5
2021-05-20 09:25:28.733 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1213777; new height is 1219533, shardID 2
2021-05-20 09:25:28.892 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1213800; new height is 1219547, shardID 6
2021-05-20 09:25:30.455 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1210531; new height is 1216286, shardID 0
2021-05-20 09:25:30.531 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1213137; new height is 1218883, shardID 3
2021-05-20 09:25:30.556 estimatefee.go:218 [ERR] Mempool log: RegisterBlock: intermediate block not recorded; current height is 1213784; new height is 1219514, shardID 4

Every 30 seconds or so, the error just keeps repeating with the same values in the “current height”, and new values in the “new height”.

What is the impact of this error? Is there anything that I can do to fix this without doing a full sync again?

Any help is appreciated!

1 Like
#2

Tried stop and restart, doesn’t help.

#3

Hi, this error log is not important. It is from estimatefee component. Your node is still in good state.

#4

Thanks! So it is not affecting overall node operation, that is re-assuring. However, it is still indicating a bug, isn’t it?

#5

@quinto, thanks for reporting this.
If there is any other issue while running your node, please don’t hesitate to DM Support

1 Like