protolambda
commented
2 months ago "missing trie node" happens when the node is started after an unclean shutdown. Try the "path" DB scheme instead of the "hash" DB scheme (see upstream geth docs) to not be as prone to this type of DB issue in geth, don't force-shutdown geth, and resync with snap-sync to get back up and running.
How to fix it？Thanks.
INFO [03-30|16:46:54.577] Starting work on payload id=0x2ee12e8e4aff5ccb WARN [03-30|16:46:54.584] Ignoring already known beacon payload number=118,065,912 hash=b9b53e..640b72 age=1d3m33s ERROR[03-30|16:46:54.598] Failed to create sealing context err="missing trie node caaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 (path ) state 0xcaaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 is not available, not found" ERROR[03-30|16:46:54.599] Failed to build payload err="missing trie node caaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 (path ) state 0xcaaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 is not available, not found" WARN [03-30|16:46:54.599] Served engine_forkchoiceUpdatedV3 conn=127.0.0.1:36876 reqid=45884 duration=1.419106ms err="Invalid payload attributes" errdata="{Error:missing trie node caaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 (path ) state 0xcaaea47db6e90c838efd2567c10837d066e634ec9eebb70ed9cb29128a966362 is not available, not found}"