Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T torflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • torflow
  • Issues
  • #24242

Closed
Open
Created Nov 11, 2017 by teor@teor

Resolve warnings on NEWCONSENSUS / NEWDESC events

I see hundreds of warnings like this whenever a new consensus arrives in the bandwidth scanner:

WARN[Sat Nov 11 23:03:55 2017]:Need to getinfo ns/id for router desc: 5EED8CE170B8889F6C041C26C934304FCCF02955
WARN[Sat Nov 11 23:03:55 2017]:NS map count of 6618 is below consensus count 6619
WARN[Sat Nov 11 23:03:55 2017]:No router desc for 602239BF846FA9A201E0ADA89FF83DC3E1F9766E after NEWDESC

We should either:

  • fix the underlying issues that are causing these warnings, or
  • downgrade them to NOTICE or INFO
Assignee
Assign to
Time tracking