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

Closed (moved)
(moved)
Open
Created Nov 08, 2017 by teor@teor

Generated a networkstatus consensus we couldn't parse

During make test-network, seems to be timing dependent:

Warning: Couldn't generate a microdesc consensus at all! Number: 1
Warning: Couldn't generate a ns consensus at all! Number: 1
Warning: Couldn't generate any consensus flavors at all. Number: 1
Warning: Couldn't store my own vote! (I told myself, 'Bad valid-after time'.) Number: 1
Warning: ID on signature on network-status document does not match any declared directory source. Number: 2
Warning: Rejecting vote from 127.0.0.1 with valid-after time of 2017-11-08 02:05:40; we were expecting 2017-11-08 02:05:35 Number: 1
Warning: networkstatus_compute_consensus: Bug: Generated a networkstatus consensus we couldn't parse. (on Tor 0.3.2.4-alpha c58471325a48f818) Number: 2
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking