Open noobvie opened 1 year ago
From logs you have no PIBD peers, so tried to switch to non-PIBD TxHashsetDownload
and got an error.
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 segmentation fault
error on launch.
How to switch to non-PIBD TxHashsetDownload? Is there a parameter to trigger it? I tried at least 5 vps in 3 continents (eu,us,asia) all had issue with PIBD. Took more than one day to have full sync after multiple times to restart grin node .
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 have issue with peers now also, so it can be related to this problem.
I also see that the CPU usage seemingly consumed much during the step 3-4/7. Maybe to verify the data or package.
I also see that the CPU usage seemingly consumed much
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: