[tor-consensus-health] Consensus issues

[Alex de Joode]

I've upgraded to the latest (debian) version of Tor, and now it looks
like everything swapped .. funny :)



On 6/24/18, atagar at torproject.org <atagar at torproject.org> wrote:
> WARNING: The consensuses published by the following directory authorities
> are more than one hour old and therefore not fresh anymore: moria1
> NOTICE: The following directory authorities recommend other client versions
> than the consensus: gabelmoo +0.3.2.8-rc
> WARNING: The certificate of the following directory authority expires within
> the next two weeks: Faravahar (2018-07-01 18-47-36)
> NOTICE: Consensus fetched from maatuska was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from longclaw was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from dizum was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from bastet was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from gabelmoo was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from moria1 was missing the following authority
> signatures: gabelmoo, maatuska, dizum
> NOTICE: Consensus fetched from dannenberg was missing the following
> authority signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: Consensus fetched from Faravahar was missing the following authority
> signatures: moria1, dannenberg, Faravahar, longclaw
> NOTICE: The following directory authorities are not reporting bandwidth
> scanner results: gabelmoo


-- 
Exit! Stage Left!