to be honest, I'm already tired of fighting with the eternal geth bugs. Now, after a hosting failure, the node, which had been working normally for weeks, stopped syncing and hung on "Syncing: state healing in progress"
. In the geth console, web3.eth.blockNumber
returns 0. Prysm beacon client is fine, and continues approving blocks. I studied this problem on the Internet, and tried everything that was offered to me, including changing geth builds to unstable. None of this helped me. I notice that only block headers are imported, and block receipts are imported a little bit at node startup, but then I only see such messages:
Feb 19 10:25:27 Imported new block headers count=1 elapsed="364.699µs" number=16,661,727 hash=ee51c8..aabdb1
Feb 19 10:25:27 Downloader queue stats receiptTasks=0 blockTasks=0 itemSize=276.22KiB throttle=950
Feb 19 10:25:35 Syncing: state healing in progress accounts=19734@1.09MiB slots=88381@6.82MiB codes=1597@11.07MiB nodes=18,720,858@4.89GiB pending=14404
Feb 19 10:25:37 Forkchoice requested sync to new head number=16,661,728 hash=e33a23..70c586
Feb 19 10:25:39 Imported new block headers count=1 elapsed=4.820ms number=16,661,728 hash=e33a23..70c586
Feb 19 10:25:43 Syncing: state healing in progress accounts=19851@1.09MiB slots=88597@6.83MiB codes=1597@11.07MiB nodes=18,722,242@4.89GiB pending=14328
Feb 19 10:25:48 Forkchoice requested sync to new head number=16,661,729 hash=55444d..ef9584
Feb 19 10:25:51 Imported new block headers count=1 elapsed="404.091µs" number=16,661,729 hash=55444d..ef9584
Feb 19 10:25:51 Syncing: state healing in progress accounts=20027@1.10MiB slots=88831@6.85MiB codes=1598@11.08MiB nodes=18,723,875@4.89GiB pending=14227
here is the command I use to launch the node:
/geth/geth/geth --cache 2048 --maxpeers 16 --syncmode full --datadir /ethereum/execution --http --http.api eth,net,engine,admin,web3