Opened 7 months ago

Closed 7 months ago

#33651 closed defect (fixed)

Suspicious "fetched this many bytes" counts from #32720

Reported by: arma Owned by: nickm
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points: 0
Parent ID: Points:
Reviewer: dgoulet Sponsor:

Description

Following #32720, 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.

Child Tickets

Change History (8)

comment:1 Changed 7 months ago by arma

I should clarify that I'm running with safelogging 0.

comment:2 Changed 7 months ago by nickm

Milestone: Tor: 0.4.4.x-final
Owner: set to nickm
Status: newaccepted

comment:3 Changed 7 months ago by nickm

Actual Points: 0
Status: acceptedneeds_review

okay, this looks like a simple mistake. Fix is in bug33651 with PR at https://github.com/torproject/tor/pull/1810

comment:4 Changed 7 months ago by nickm

(If there are two commits in this PR, then it's safe to ignore the first one: It's already been merged to master.)

comment:5 Changed 7 months ago by arma

Looking promising!

Mar 20 05:59:37.013 [notice] Heartbeat: Tor's uptime is 3:31 hours, with 14 circuits open. I've sent 366 kB and received 1.20 MB.
Mar 20 05:59:37.014 [notice] While bootstrapping, fetched this many bytes:
Mar 20 05:59:37.014 [notice]     394532 (microdescriptor fetch)
Mar 20 05:59:37.014 [notice] While not bootstrapping, fetched this many bytes:
Mar 20 05:59:37.014 [notice]     212736 (consensus network-status fetch)
Mar 20 05:59:37.014 [notice]     5935 (hidden-service v2 descriptor fetch)
Mar 20 05:59:37.014 [notice]     55871 (microdescriptor fetch)

comment:6 Changed 7 months ago by dgoulet

Reviewer: dgoulet
Status: needs_reviewmerge_ready

For some reasons, one of Appveyor builds failed with:

https://ci.appveyor.com/project/torproject/tor/builds/31574905/job/7nyl60kltec1gs4h

  FAIL ../src/test/test_crypto.c:237: OpenSSL library version 1.1.1d did not begin with header version 1.1.1e.

Seems unrelated so apart from that, lgtm. Feel free to merge.

comment:7 Changed 7 months ago by nickm

That appveyor failure is #33643

comment:8 Changed 7 months ago by nickm

Resolution: fixed
Status: merge_readyclosed

Merged to master. No changes entry, since the bug has not been in any stable release.

Note: See TracTickets for help on using tickets.