Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #25396

Closed (moved)
(moved)
Open
Created Mar 01, 2018 by George Kadianakis@asn

Consensus health reports wrong latest valid-after time

Over the past days a few people have reported that consensus health reports the wrong latest valid-after time.

As an example, it currently says:

Consensus was published 2018-03-01 17:00:00. Note that it takes up to 15 minutes to learn about new consensus and votes and process them.

but there is a valid 19:00 consensus:

$ curl -kis http://199.58.81.140/tor/status-vote/current/consensus-microdesc | grep valid-after
valid-after 2018-03-01 19:00:00
$ date --utc
Thu  1 Mar 19:33:43 UTC 2018
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking