-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[BUG] unable to start Nerpa #5782
Comments
@travisperson any thoughts you could share would be much appreciated! |
Are many of the other daemons in the network syncing the chain started by preminer-0? This looks to be #5474 |
I tried adding I noticed something else instead on the bootstrap nodes:
I'm not sure where
|
Set |
@travisperson ohhhhh I did not understand the previous issue at all. |
Yep, the issue is that the sync manager is waiting on enough peers to inform it of the same tipset, and because only a single miner is producing blocks, it can never reach this threshold. To get around this we need at least BootstrapPeerThreshold number of peers to accept the chain from a single peer. |
The Nerpa-network has been depreciated, so this issue can probably be closed? #rengjøring |
Describe the bug
When resetting Nerpa, only the first miner (preminer-0) finishes the init process succesfully. The other preminers are stuck.
Logs from
preminer-1
(stuck during init):Previously, starting
lotus-miner
on preminer-0 was fixing the issue, however, right now preminer-0 mines new blocks succesfully, but the other ones are still stuck on the init process.Logs from
preminer-0
succesfully mining new blocks:Miner init systemd unit is the following:
Lotus binaries are compiled with
GOFLAGS+=-tags=nerpanet
from3be4984d9
.Version (run
lotus version
): lotus version 1.5.2+git.3be4984d9To Reproduce
Steps to reproduce the behavior:
GOFLAGS+=-tags=nerpanet
Expected behavior
All pre-miners should finish the init process successfully in order to reset/bootstrap the Nerpa network.
Logs
Please see in description.
The text was updated successfully, but these errors were encountered: