-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line parameter suggestion to run a stable archival node #72
Comments
hi, maybe i can give you some useful advice, It has little to do with the startup command. Your startup command seems to be fine. It may be related to the following two factors.
In my case, it used to always be behind blocks because my data source was from https://github.com/ledgerwatch/erigon/ . Later, I followed the advice, re-downloaded the snapshot data and restarted synchronizing. It has been more than a week now, and I have never been behind by more than 3 minutes (I have a monitor, and when it is more than 3 minutes behind, it will send an alarm) |
It seem work stable for our mainnet archive node.
For bsc testnet, suggest to specify static node, add this: |
I am in the process of redeploying my instances but two people confirmed removing |
On v1.0.5 it's still acting up using the existing data which was a fresh unpack of the main snapshot which tried v1.0.2, v1.0.3, and v1.0.4. First time after on v.1.0.5 was repeating stage 5 over and over; restarted and now it's just stuck on |
Our nodes often lag behind blocks,and restart erigon then erigon sync started again.
|
pls refer: https://github.com/node-real/bsc-erigon#faq |
That's great |
Hi, Just curious to see if anyone would be willing to share their command line if they are running a stable archival node. My node is constantly trailing behind and I find myself frequently rebooting it to stay synced.
My current setup
Docker image
ghcr.io/node-real/bsc-erigon:1.0.3
The text was updated successfully, but these errors were encountered: