Rippled 1.7.3 with a lot of LedgerHistory:ERR MISMATCH errors

[mangekyousharingan]

Hey,

I am running rippled node v1.7.3 on EC2 c5.4xlarge, recently I am facing issue that there are a lot of errors like: LedgerHistory:ERR MISMATCH: seq=67808257 validated:13CCBE851F2D7514B6FCF317E51A3875E211F29B670C828F0C51EA1BAE06FFB4 then:B544FD44B1AF80C1AB2C93F25CEB04BA81F87D688D1BE0EF1126BC1F705CC920 and LedgerHistory:ERR MISMATCH on prior ledger

then I am either restarting the node or deleting node data and restarting it, for some time it helps, but then those issues come back again and again which i causing node being out of sync.

Is there any known solution or advice to fix this? Thanks!

[amrendraw3]

I am also facing the InsufficientNetworkMode problem since the past upgrade. The reason is still unknown. I tried multiple solutions available on the internet and even created a new instance for this but the issue is still there.

I am running an instance of 32GB RAM and 300 GB SSD config.

The rippled server_state stays on connected and sometimes it went to proposing but again it is in a connected state for more than 20 hours.

The instance was working fine 3 days ago, and I upgraded the rippled server yesterday only.

[gkardava]

We have the same problem. For us, the bottleneck is disk IO. Check it and boost it if you have any option to do it.

[mangekyousharingan]

@gkardava I did boost IOPS, but unfortunately it did not help :(