King Li
King Li
I also encountered the same issue when resync from a clean slate
Hope it helps a fellow user, I was using wildcard domain and I have to add `--metrics-per-host=false` for this metric to work.
Any idea how do we work around this? Our node has been stuck for 2+ days. Quicksync doesn't work as described above
Any updates on this issue? My nodes have been getting worse performance with recent updates
Did you managed to resolve the issue? We are running into similar problems with our graphql deployment
> When we restart Bor on the non syncing server, it catches the top of the chain and then stops syncing, even when we let it run for hours. We...
We have the same issue. Switched to ELB classic, and the problem seems to go away. The only problem is ELB use is discouraged by AWS...