[tor-consensus-health] Consensus issues

[Damian Johnson]

Since longclaw is running different BWAuth code do we only want to
compare it with others using the shiny new thing? Or should it be
similar to the others?

On Mon, Nov 5, 2018 at 1:07 PM <atagar at torproject.org> wrote:
>
> ERROR: Unable to retrieve the consensus from dizum (http://194.109.206.212:80/tor/status-vote/current/consensus): <urlopen error timed out>
> ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority): <urlopen error timed out>
> NOTICE: The following directory authorities recommend other client versions than the consensus: gabelmoo -0.3.5.4-alpha
> NOTICE: The following directory authorities recommend other server versions than the consensus: gabelmoo -0.3.5.4-alpha
> NOTICE: Consensus fetched from maatuska was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from longclaw was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from bastet was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from moria1 was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from dannenberg was missing the following authority signatures: dizum
> NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: dizum
> WARNING: The following authorities are missing from the consensus: dizum
> NOTICE: Bandwidth authorities have a substantially different number of measured entries: maatuska (7158), longclaw (5412), bastet (7152), gabelmoo (6972), moria1 (7162), Faravahar (7034)_______________________________________________
> tor-consensus-health mailing list
> tor-consensus-health at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-consensus-health