[tor-consensus-health] Consensus issues

atagar at torproject.org atagar at torproject.org
Wed Jun 28 12:05:44 UTC 2017


ERROR: Unable to retrieve the consensus from tor26 (http://86.59.21.38:80/tor/status-vote/current/consensus.z): <urlopen error [Errno 111] Connection refused>
ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority.z): <urlopen error [Errno 111] Connection refused>
NOTICE: The following directory authorities recommend other client versions than the consensus: moria1 +0.3.1.4-alpha
NOTICE: The following directory authorities recommend other server versions than the consensus: moria1 +0.3.1.4-alpha
WARNING: The certificate of the following directory authority expires within the next week: Faravahar (2017-07-01 19-15-20)
NOTICE: Consensus fetched from maatuska was missing the following authority signatures: tor26
NOTICE: Consensus fetched from longclaw was missing the following authority signatures: tor26
NOTICE: Consensus fetched from dizum was missing the following authority signatures: tor26
NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: tor26
NOTICE: Consensus fetched from moria1 was missing the following authority signatures: tor26
NOTICE: Consensus fetched from dannenberg was missing the following authority signatures: tor26
NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: tor26
NOTICE: The following directory authorities are not reporting bandwidth scanner results: maatuska
WARNING: Unable to reach the ORPort of tor26 (2001:858:2:2:aabb:0:563b:1526, port 443): [Errno 113] No route to host


More information about the tor-consensus-health mailing list