Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #1206

Closed (moved)
Open
Opened 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
Tor: 0.2.2.x-final
Milestone
Tor: 0.2.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#1206