Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #1300
Closed
Open
Issue created Mar 11, 2010 by Roger Dingledine@armaReporter

Authority that doesn't make a consensus never fetches one from elsewhere

If moria1 fails to participate in making the consensus (e.g. it's down, or it doesn't support the consensus method that is chosen for the consensus), then it doesn't have a consensus for that period. It should realize it doesn't have the newest consensus, and try to fetch one from the other authorities.

This bug is especially relevant while we have authorities that don't like the consensus method in use -- currently dizum and dannenberg haven't upgraded, so they never sign the consensus, so any clients (or relays!) who ask them for a consensus have to retry elsewhere. I imagine the bug slows down bootstrapping too.

[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