Skip to content
GitLab
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
  • #14177
Closed
Open
Issue created Jan 12, 2015 by Linus Nordberg@linusDeveloper

bwauth spends some 40 minutes "updating rank history". Every hour.

This is a newly started, well Jan 07 around 01:00, bwauth with default settings.

[bwscanner@salsa ~/torflow/NetworkScanners/BwAuthority]$ tail -100000 data/scanner.1/bw.log  | egrep -A 1 'Updating rank history'
INFO[Mon Jan 12 00:03:37 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 00:42:20 2015]:Consensus history updated.
--
INFO[Mon Jan 12 00:44:36 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 01:23:38 2015]:Consensus history updated.
--
INFO[Mon Jan 12 01:54:48 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 02:34:08 2015]:Consensus history updated.
--
INFO[Mon Jan 12 02:36:32 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 03:16:12 2015]:Consensus history updated.
--
INFO[Mon Jan 12 03:38:51 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 04:18:45 2015]:Consensus history updated.
--
INFO[Mon Jan 12 04:21:06 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 05:00:14 2015]:Consensus history updated.
--
INFO[Mon Jan 12 05:03:46 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 05:43:08 2015]:Consensus history updated.
--
INFO[Mon Jan 12 05:45:15 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 06:25:19 2015]:Consensus history updated.
--
INFO[Mon Jan 12 07:09:36 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 07:48:50 2015]:Consensus history updated.
--
INFO[Mon Jan 12 08:06:39 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 08:46:14 2015]:Consensus history updated.
--
INFO[Mon Jan 12 08:59:29 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 09:39:40 2015]:Consensus history updated.
--
INFO[Mon Jan 12 09:42:26 2015]:Consensus change... Updating rank history
INFO[Mon Jan 12 10:22:41 2015]:Consensus history updated.
--
INFO[Mon Jan 12 10:54:23 2015]:Consensus change... Updating rank history

Don't know if this might be related to legacy/trac#4015 (moved). What does "freeze" mean there?

Assignee
Assign to
Time tracking