[tor-consensus-health] Consensus issues

atagar at torproject.org atagar at torproject.org
Mon Jun 4 13:06:38 UTC 2018


NOTICE: Downloading the consensus from dizum took 51.1s. Median download time is 1.6s: maatuska => 1.4s, longclaw => 1.5s, dizum => 51.1s, bastet => 2.1s, gabelmoo => 0.9s, moria1 => 2.5s, dannenberg => 1.4s, Faravahar => 1.6s
NOTICE: The system clock of dizum is 49 seconds off
ERROR: Unable to retrieve the vote from dizum (http://194.109.206.212:80/tor/status-vote/current/authority): HTTP Error 404: Not found
WARNING: The consensuses published by the following directory authorities are more than one hour old and therefore not fresh anymore: dizum
NOTICE: The following directory authorities recommend other client versions than the consensus: gabelmoo -0.3.3.7 -0.3.4.2-alpha
NOTICE: The following directory authorities recommend other server versions than the consensus: gabelmoo -0.3.3.7 -0.3.4.2-alpha
NOTICE: The certificate of the following directory authority expires within the next three weeks: dannenberg (2018-06-24 13-17-32)
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
NOTICE: The following directory authorities are not reporting bandwidth scanner results: gabelmoo
WARNING: The following authorities are missing from the consensus: dizum


More information about the tor-consensus-health mailing list