Sreeram J

We are also getting a similar error, we are on geth 1.10.23 and beacon chain is on prysm 3.1.1 -- Warning remains as below Merge is configured, but previously seen...

Similar scenarios in my node as well. I have 2 geth archival nodes connected to 2 beacon nodes and both seems to have completed merge. But the nodes seems to...

Thanks for the update @holiman Is there anyway to increase the import time, I am already using an 16TB SSD and the nodes are in AKS as well. Any sol...

@holiman Got it fixed and I started running. But I get this INFO for blocks multiple times for a same block. --GETH-- INFO [09-22|13:01:36.034] Imported new potential chain segment blocks=1...

@Yvelo The issue is mine is an archival sync node :D So I think I need a lot more patience. Happily it has reached 6 hours behind

> ``` > INFO [04-05|06:05:25.335] Imported new potential chain segment number=19,582,762 hash=837eae..b93dbc blocks=1 txs=66 mgas=4.271 elapsed=10.167s mgasps=0.420 age=16h24m14s triedirty=0.00B > ``` > > This means your node is syncing, but...

> ``` > INFO [04-05|06:05:25.335] Imported new potential chain segment number=19,582,762 hash=837eae..b93dbc blocks=1 txs=66 mgas=4.271 elapsed=10.167s mgasps=0.420 age=16h24m14s triedirty=0.00B > ``` > > This means your node is syncing, but...

> You're running an archive node? Yes, this node was running till 5 days back. Suddenly it started deteriorating. So we had another node from which we took the snapshot...