-
Notifications
You must be signed in to change notification settings - Fork 990
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
Aborting PIBD error. restart fast sync v5.2.0-beta.3 #3767
Comments
From logs you have no PIBD peers, so tried to switch to non-PIBD |
I found some weird issue with peers. I restarted my node frequently from single IP address and now after more than 24 hours I can find only 2-3 peers with same IPs.. Moreover, after cleaning and restarting the node I am getting |
How to switch to non-PIBD TxHashsetDownload? Is there a parameter to trigger it? |
It switches automatically when you have no peers with PIBD capability after timeout. |
I also see that the CPU usage seemingly consumed much during the step 3-4/7. Maybe to verify the data or package. |
Its OK. |
Describe the bug
I tried to rebuilt some grin nodes with new version v5.2.0-beta.3. After cleaning up the chain_data, it synced from the scratch and usually got error at step PIBD or stuck in the middle.
To Reproduce
Steps to reproduce the behavior:
Relevant Information
Here is example log
OS version:
The text was updated successfully, but these errors were encountered: