Error `ruleNumber`
Duniter nodes are easily stuck in a fork when the frequency of forks increase.
The logs show Error: ruleNumber
:
2022-08-18T20:40:11+02:00 - e[32minfoe[39m: Block resolution: 1 potential blocks after current#551678...
2022-08-18T20:40:11+02:00 - e[31merrore[39m: Error: ruleNumber
at Function.checkBlock (/opt/duniter/app/lib/blockchain/DuniterBlockchain.js:63:19)
at process._tickCallback (internal/process/next_tick.js:68:7)
Along with NotFoundError: Key not found in database
:
2022-08-18T16:05:37+02:00 - [32minfo[39m: Block #551677 added to the blockchain in 246 ms
2022-08-18T16:05:39+02:00 - [32minfo[39m: Block #551677 added to the blockchain in 253 ms
2022-08-18T16:05:39+02:00 - [32minfo[39m: Block #551678 added to the blockchain in 70 ms
2022-08-18T16:05:39+02:00 - [31merror[39m: Unhandled rejection: NotFoundError: Key not found in database [1660828921]
2022-08-18T16:05:39+02:00 - [31merror[39m: NotFoundError: Key not found in database [1660828921]
at /opt/duniter/node_modules/levelup/lib/levelup.js:192:15
Actually, the ruleNumber
error is a symptom of the Key not found in database
error, which is a low level issue in the data access layer. A LevelDB key has been deleted whereas it is supposed to still exist.