[tor-consensus-health] Consensus issues

atagar at torproject.org atagar at torproject.org
Thu Jun 15 20:06:42 UTC 2017


ERROR: Unable to retrieve the consensus from longclaw (http://199.254.238.52:80/tor/status-vote/current/consensus.z): <urlopen error [Errno 113] No route to host>
ERROR: Unable to retrieve the vote from longclaw (http://199.254.238.52:80/tor/status-vote/current/authority.z): <urlopen error [Errno 113] No route to host>
NOTICE: The certificate of the following directory authority expires within the next three weeks: tor26 (2017-07-01 00-00-00)
NOTICE: The certificate of the following directory authority expires within the next three weeks: dizum (2017-06-30 18-55-37)
NOTICE: The certificate of the following directory authority expires within the next three weeks: Faravahar (2017-07-01 19-15-20)
NOTICE: Consensus fetched from maatuska was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from tor26 was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from dizum was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from gabelmoo was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from moria1 was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from dannenberg was missing the following authority signatures: longclaw
NOTICE: Consensus fetched from Faravahar was missing the following authority signatures: longclaw
NOTICE: The following directory authorities are not reporting bandwidth scanner results: maatuska
WARNING: Unable to reach the ORPort of longclaw (2620:13:4000:8000:60:f3ff:fea1:7cff, port 443): [Errno 113] No route to host


More information about the tor-consensus-health mailing list