Aderks
Aderks
On `v0.13.0` we're also seeing similar logs and resource usage as the above. Mainly very high read usage.  Blocking p2p port `2121` didn't seem to help our bridge node....
Seeing large upload spikes as well. Last known version without the spikes was `v2.48.0`. Spikes seen all the up to latest `v2.53.1`. The following snippets show what upgrading 1 Sepolia...
> @Aderks it would be useful if you tell us which consensus client u are using, or if you are using internalcl My bad, we use Lighthouse `v4.5.0` on all...
Getting a ton of this on my IndexerAgent too... Looks like I am possibly receiving more after `[email protected]` Any luck fixing this? Wipe and make a fresh AgentDB? ``` 2020-12-05...
I nuked my DB, reallocated rules/costs and I still the error. Albeit I don't see as many of the errors, but they're still there.