[tor-consensus-health] Consensus issues

Damian Johnson atagar at torproject.org
Fri Jan 9 15:59:49 UTC 2015


Thanks for taking a peek Jake. Over the year I've see these on
occasion from all authorities so probably just a tor bug where on
occasion an authority doesn't vote. It would be neat if there was logs
or something for Nick to work with though. Maybe tor needs more
logging in this area.


On Fri, Jan 9, 2015 at 7:53 AM, Jacob Appelbaum <jacob at appelbaum.net> wrote:
> Heya,
>
> I have no idea why this happened - urras seems to be completely fine.
>
> Urras appears to be voting as of a minute ago as well.
>
> On 1/9/15, atagar at torproject.org <atagar at torproject.org> wrote:
>> NOTICE: Consensus fetched from maatuska was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from tor26 was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from urras was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from longclaw was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from dizum was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from gabelmoo was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from moria1 was missing the following authority
>> signatures: urras
>> NOTICE: Consensus fetched from dannenberg was missing the following
>> authority signatures: urras
>> NOTICE: Consensus fetched from Faravahar was missing the following authority
>> signatures: urras
>> WARNING: The following directory authorities are not reporting bandwidth
>> scanner results: maatuska


More information about the tor-consensus-health mailing list