[tor-consensus-health] Consensus issues

Roger Dingledine arma at mit.edu
Tue Apr 10 04:49:28 UTC 2018


On Tue, Apr 10, 2018 at 04:46:38AM +0000, atagar at torproject.org wrote:
> ERROR: Unable to retrieve the consensus from tor26 (http://86.59.21.38:80/tor/status-vote/current/consensus): [Errno 104] Connection reset by peer
> ERROR: Unable to retrieve the vote from tor26 (http://86.59.21.38:80/tor/status-vote/current/authority): timed out
> ERROR: The consensuses published by the following directory authorities are more than one hour old and therefore not fresh anymore: maatuska, longclaw, dizum, bastet, gabelmoo, moria1, dannenberg, Faravahar

Hi Damian,

This "more than one hour old" message seems to show up each time
consensus-health can't reach tor26, and I don't think it's an accurate
message. That is, I think we are serving a fine consensus right now. I
wonder if there's a bug?

Thanks,
--Roger



More information about the tor-consensus-health mailing list