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
  • #20909

Closed (moved)
Open
Opened Dec 07, 2016 by teor@teor

Tor 0.2.9.5-alpha still delivers outdated consensuses

I found one relay on 0.2.9.5-alpha that still has this bug, after scanning about ~400 relays.

WARNING::Consensus download: 1.8s outdated consensus, expired 44855s ago from snowfall (192.160.102.164:80) 823AA81E277F366505545522CEDC2F529CE4DC3F, max download time 15.0s.

https://atlas.torproject.org/#details/823AA81E277F366505545522CEDC2F529CE4DC3F

The microdesc consensus is ~12 hours out of date: http://192.160.102.164/tor/status-vote/current/consensus-microdesc

The full consensus is fine: http://192.160.102.164/tor/status-vote/current/consensus

It was fine yesterday when I scanned it.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#20909