Skip to content

GitLab

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

Closed
Open
Created Jan 10, 2022 by juga@jugaMaintainer

Change log about missing descriptor's observed bandwidth

As @sebastian reported by irc, sbws logs Jan 02 05:41:20 v3bwfile[377088]: <WARNING> (MainThread) Descriptor observed bandwidth is None.

That line was added in #33871 (closed) to report the case and do not scale relay's missing that bandwidth value.

It's possible that this case happen cause sbws is configured to gett "early", "useless" descriptors or it doesn't check the running (and others) flag or relay in dormant mode (#33166 (moved)).

I'd create a different issue to try to figure out why this happen in a later version and for now lower the level to info so that there aren't too many email notifications when configuring sbws as explained in #40110 (closed).

Assignee
Assign to
Time tracking