Skip to content
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

Unexpected failed to connect to bootstrap nodes warning #3109

Closed
StephenButtolph opened this issue Jun 12, 2024 · 0 comments · Fixed by #3156
Closed

Unexpected failed to connect to bootstrap nodes warning #3109

StephenButtolph opened this issue Jun 12, 2024 · 0 comments · Fixed by #3156
Assignees
Labels
bug Something isn't working monitoring This primarily focuses on logs, metrics, and/or tracing
Milestone

Comments

@StephenButtolph
Copy link
Contributor

Avalanchego will incorrectly report that the beacon nodes are unreachable when running a node with reduced performance.

avalanchego/node/node.go

Lines 622 to 625 in 41e46d1

n.Log.Warn("failed to connect to bootstrap nodes",
zap.Stringer("bootstrappers", n.bootstrappers),
zap.Duration("duration", n.Config.BootstrapBeaconConnectionTimeout),
)

This issue is able to be replicated consistently on nodes with high performance by extending the time to initialize the platformvm.

For example, modifying

chainCtx.Log.Verbo("initializing platform chain")
. To:

+	time.Sleep(time.Minute)
+
	chainCtx.Log.Verbo("initializing platform chain")
@StephenButtolph StephenButtolph added the bug Something isn't working label Jun 12, 2024
@StephenButtolph StephenButtolph added this to the v1.11.9 milestone Jun 12, 2024
@StephenButtolph StephenButtolph added the monitoring This primarily focuses on logs, metrics, and/or tracing label Jun 12, 2024
@joshua-kim joshua-kim self-assigned this Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working monitoring This primarily focuses on logs, metrics, and/or tracing
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants