WARNING: dannenberg is missing the server descriptor of dannenberg WARNING: The certificate of the following directory authority expires within the next two weeks: dizum (2018-12-25 09-06-23) NOTICE: The following directory authorities are not reporting bandwidth scanner results: Faravahar 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 NOTICE: Authorities disagree about the BadExit flag for 36FECC5DB5A01866E6769BD964839F4F5D675EF0 (with flag: moria1, longclaw, maatuska, Faravahar, without flag: dannenberg) NOTICE: Authorities disagree about the BadExit flag for F1382A893EFF47533AEA580871B0F82155D701BD (with flag: moria1, longclaw, maatuska, Faravahar, without flag: dannenberg)
On Thu, Dec 13, 2018 at 05:05:52PM +0000, atagar@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
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@mit.edu wrote:
On Thu, Dec 13, 2018 at 05:05:52PM +0000, atagar@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
tor-consensus-health@lists.torproject.org
-
atagar＠torproject.org -
Damian Johnson
-
Roger Dingledine