Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #1206
Closed (moved) (moved)
Open
Created Jan 10, 2010 by Sebastian Hahn@sebastian

Fluxe3 is not a guard

Fluxe3 isn't considered a guard (only one of the authorities votes for it). It has been up for 13 days, before that it had a downtime for ~30 minutes, and before that it was running for a week. Before that it was offline.

There are a few things that seem to be strange. When arma looked at what moria thinks about fluxe3 three days ago, moria thought that fluxe3's uptime was 18 days. It somehow missed the fact that the descriptor changed to reflect the new uptime.

The other question is, does this influence why Fluxe3 is not a guard? Or are there other issues?

[Automatically added by flyspray2trac: Operating System: All]

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking