[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #20499 [Core Tor/Tor]: Relay/Bridge won't update the microdesc consensus while running

#20499: Relay/Bridge won't update the microdesc consensus while running
--------------------------+------------------------------------
 Reporter:  rubiate       |          Owner:
     Type:  defect        |         Status:  new
 Priority:  High          |      Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.2.9.4-alpha
 Severity:  Normal        |     Resolution:
 Keywords:  regression    |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by arma):

 This looks very similar to my "mystery 1" in #19969 -- so I am going to
 bring that discussion over here so we can keep the bugs separate.

 For me it happened on "Tor 0.2.9.3-alpha-dev (git-bfaded9143d127cb)"
 (which is alas not in a released version of Tor, because #20269 isn't
 merged yet, but suffice to say it's partway between 0.2.9.3 and 0.2.9.4).
 And this was just a client, not a bridge or relay.

 teor asked in #19969 what my "consensus download_status_t has for all its
 fields, particularly the attempt and failure counts." Here is what gdb
 says:
 {{{
 (gdb) print consensus_dl_status
 $8 = {{next_attempt_at = 0, n_download_failures = 0 '\000',
     n_download_attempts = 0 '\000', schedule = DL_SCHED_CONSENSUS,
     want_authority = DL_WANT_ANY_DIRSERVER,
     increment_on = DL_SCHED_INCREMENT_FAILURE,
     backoff = DL_SCHED_RANDOM_EXPONENTIAL, last_backoff_position = 0
 '\000',
     last_delay_used = 0}, {next_attempt_at = 1477296555,
     n_download_failures = 17 '\021', n_download_attempts = 17 '\021',
     schedule = DL_SCHED_CONSENSUS, want_authority = DL_WANT_ANY_DIRSERVER,
     increment_on = DL_SCHED_INCREMENT_FAILURE,
     backoff = DL_SCHED_RANDOM_EXPONENTIAL, last_backoff_position = 17
 '\021',
     last_delay_used = 387}}
 }}}

 The first half of that makes sense, since my Tor doesn't touch the non-
 microdesc consensus stuff. But for the second half... it looks like my
 next_attempt_at is ~6 days ago.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20499#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs