[tor-consensus-health] Consensus issues

Damian Johnson atagar at torproject.org
Mon Dec 17 19:07:27 UTC 2018


Thanks Roger! DocTor will no longer provide these notices [1]. I also
shot the network team a ticket to add the new flag to the spec [2].

[1] https://gitweb.torproject.org/doctor.git/commit/?id=757608c
[2] https://trac.torproject.org/projects/tor/ticket/28887

On Thu, Dec 13, 2018 at 12:49 PM Roger Dingledine <arma at mit.edu> wrote:
>
> On Thu, Dec 13, 2018 at 05:05:52PM +0000, atagar at torproject.org wrote:
> > NOTICE: maatuska had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: longclaw had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: dizum had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: bastet had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: gabelmoo had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: moria1 had 223 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: dannenberg had 0 StaleDesc flags in its vote but the consensus had 13
> > NOTICE: Faravahar had 0 StaleDesc flags in its vote but the consensus had 13
>
> Hi Damian,
>
> FYI, I think these particular lines are going to happen always now --
> moria1 is running the shiny new code that knows what a StaleDesc flag
> is, and the rest of the dir auths aren't. In this case moria1 was voting
> StaleDesc about 223 relays, only 13 of which it also voted the Running
> flag for (i.e. only 13 of the relays it gave the flag to made it into
> the consensus). And I guess since only moria1 expressed an opinion about
> the StaleDesc flag, then its opinion is the winner.
>
> --Roger
>


More information about the tor-consensus-health mailing list