[Node Operator Question] op-geth is consistently 12 hours behind #68
-
Issue Descriptiondocker run -d --name op-node docker run -d --name op-geth The op-geth being 12 hours behind has been going on for many days now, I followed the official stable setup parameters and earlier on it has been running fine, I don't know what the problem is? And it looks like the batcher submission for this batch_epoch was not recognized. Each batch_epoch is exactly 12 hours Node Logs11|op-geth | INFO [11-13|21:54:52.139] Starting work on payload id=0x05b3b397be5bb129 t=2023-11-14T05:07:26+0000 lvl=info msg="Generating next batch" epoch=0x534f83e93d37f981cb73501ebaf816cbd41d166b610ab5b64854e4f7b86b7d1d:18564349 timestamp=1,699,895,041 |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 12 replies
-
Hey @cheneyweb, I'm going to get a little time with client engineers today. I'll ask them about this and see if we can uncover anything. |
Beta Was this translation helpful? Give feedback.
-
The information that I got from a client engineer is that your node is likely following the wrong chain. You can confirm this by checking your blocks are in sync with what etherscan is reporting. You'll likely see a mismatch. I suspect the root cause of this issue is that your node was not initialized with our data directory and started producing blocks that are off. You can find more information on this in our docs: |
Beta Was this translation helpful? Give feedback.
-
I have similar issue, my node head is also around 12h late. I did create simple benchmark script to test which node is the fastest and what is the current head value:
Test was running 5 minutes and as you can see its saying that our node is not delayed which is not true, it just never retreive the current head so its never calculated. As you can see head in our node is 20k heads late. I am running node from official website, initialized via data directory and run from source. Thank you for your help. I can provide more info if needed. |
Beta Was this translation helpful? Give feedback.
-
I was able to chat with a couple other client engineers and they noted:
To resolve the issue, you'll probably need to remove the database and resync your node. |
Beta Was this translation helpful? Give feedback.
-
Hey @cheneyweb, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community. |
Beta Was this translation helpful? Give feedback.
I was able to chat with a couple other client engineers and they noted: