Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33651

Closed (moved)
Open
Opened Mar 19, 2020 by Roger Dingledine@arma

Suspicious "fetched this many bytes" counts from #32720

Following #32720 (moved), now I have these log messages in my Tor client:

Mar 17 17:52:52.004 [notice] Bootstrapped 100% (done): Done
Mar 17 23:52:49.170 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 166.22 MB and received 5.25 GB.
Mar 17 23:52:49.178 [notice] While bootstrapping, fetched this many bytes:
Mar 17 23:52:49.178 [notice]     542559 (consensus network-status fetch)
Mar 17 23:52:49.178 [notice] While not bootstrapping, fetched this many bytes:
Mar 17 23:52:49.178 [notice]     542559 (consensus network-status fetch)
Mar 17 23:52:49.178 [notice] Average packaged cell fullness: 52.843%. TLS write overhead: 3%
Mar 18 17:01:52.177 [notice] Your system clock just jumped 44387 seconds forward; assuming established circuits no longer work.
Mar 18 18:12:33.010 [notice] Heartbeat: Tor's uptime is 11:59 hours, with 0 circuits open. I've sent 166.25 MB and received 5.25 GB.
Mar 18 18:12:33.011 [notice] While bootstrapping, fetched this many bytes:
Mar 18 18:12:33.011 [notice]     542559 (consensus network-status fetch)
Mar 18 18:12:33.011 [notice] While not bootstrapping, fetched this many bytes:
Mar 18 18:12:33.011 [notice]     542559 (consensus network-status fetch)
Mar 18 18:12:33.011 [notice] Average packaged cell fullness: 52.898%. TLS write overhead: 3%
Mar 19 00:12:33.013 [notice] Heartbeat: Tor's uptime is 17:59 hours, with 0 circuits open. I've sent 166.26 MB and received 5.25 GB.
Mar 19 00:12:33.013 [notice] While bootstrapping, fetched this many bytes:
Mar 19 00:12:33.013 [notice]     542559 (consensus network-status fetch)
Mar 19 00:12:33.013 [notice] While not bootstrapping, fetched this many bytes:
Mar 19 00:12:33.013 [notice]     542559 (consensus network-status fetch)
Mar 19 00:12:33.013 [notice] Average packaged cell fullness: 52.953%. TLS write overhead: 3%

I'm running

Tor 0.4.4.0-alpha-dev (git-d4595b344a1a3254) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd N/A.

It is surprising to me that I have the same number while bootstrapping and while not bootstrapping, and that number doesn't seem to go up.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.4.4.x-final
Milestone
Tor: 0.4.4.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33651