[tor-consensus-health] Consensus issues

Alex de Joode adejoode at gmail.com
Mon May 1 12:55:00 UTC 2017


esxi server crashed, rebooted.

On 5/1/17, atagar at torproject.org <atagar at torproject.org> wrote:
> ERROR: Unable to retrieve the consensus from dizum
> (http://194.109.206.212:80/tor/status-vote/current/consensus.z): <urlopen
> error timed out>
> ERROR: Unable to retrieve the vote from dizum
> (http://194.109.206.212:80/tor/status-vote/current/authority.z): <urlopen
> error timed out>
> NOTICE: Consensus fetched from maatuska was missing the following authority
> signatures: dizum
> NOTICE: Consensus fetched from tor26 was missing the following authority
> signatures: dizum
> NOTICE: Consensus fetched from longclaw 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
> NOTICE: The following directory authorities are not reporting bandwidth
> scanner results: maatuska
> WARNING: The following authorities are missing from the consensus: dizum


-- 
Exit! Stage Left!


More information about the tor-consensus-health mailing list