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

[BUG] Benchmark failed: Flux does not have sufficient peers #928

Closed
dramirezRT opened this issue Jan 31, 2023 · 0 comments
Closed

[BUG] Benchmark failed: Flux does not have sufficient peers #928

dramirezRT opened this issue Jan 31, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@dramirezRT
Copy link
Contributor

Describe the bug

I am getting sometimes the error of "Benchmark failed: Flux does not have sufficient peers"
I am self hosting.
This is happening right after the ISPS provides a new external IP. My ISP provides a new IP every 24 hours, without possibility of static IP.

  • Some nodes are able to recover.
  • No error if node is rebooted when benchmark first fails.
  • Node that is not rebooted expires from the Flux network and needs to be manually fixed.

This was not happening on the previous version for the Flux OS

Expected behavior
Right after the IP change Flux OS to be able to reconfigured the new IP and recover as soon as possible to avoid any downtime.

Environment:

  • OS: Ubuntu Server 20.04
  • Version FluxOS 3.33.0
  • Daemon 6000050
  • Benchmark Flux Bench version 3.7.3
@dramirezRT dramirezRT added the bug Something isn't working label Jan 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants