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 WARNING: dizum is missing the server descriptor of longclaw NOTICE: The following directory authorities are not reporting bandwidth scanner results: gabelmoo NOTICE: Authorities disagree about the BadExit flag for 311FC272D5B8DCE8A6E05C9D347ADD5627AF228C (with flag: gabelmoo, longclaw, maatuska, Faravahar, without flag: moria1)
On Tue, Apr 10, 2018 at 04:46:38AM +0000, atagar@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
Hi Roger, this was discussed briefly last week. What's happening is that DocTor is spending a looooong time trying to download from tor26 after fetching other consensuses, causing it to seem out of date when it gets to the check. I should adjust this.
On Mon, Apr 9, 2018 at 9:49 PM, Roger Dingledine arma@mit.edu wrote:
On Tue, Apr 10, 2018 at 04:46:38AM +0000, atagar@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
Hi Roger. Dug into this a bit this morning and unfortunately I'm having trouble getting to the root cause of the hanging, but I did correct a bug that should cut down on the impact...
https://gitweb.torproject.org/stem.git/commit/?id=e43a168
I'll look into this more later.
Cheers! -Damian
On Mon, Apr 9, 2018 at 10:19 PM, Damian Johnson atagar@torproject.org wrote:
Hi Roger, this was discussed briefly last week. What's happening is that DocTor is spending a looooong time trying to download from tor26 after fetching other consensuses, causing it to seem out of date when it gets to the check. I should adjust this.
On Mon, Apr 9, 2018 at 9:49 PM, Roger Dingledine arma@mit.edu wrote:
On Tue, Apr 10, 2018 at 04:46:38AM +0000, atagar@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
tor-consensus-health@lists.torproject.org
-
atagar＠torproject.org -
Damian Johnson
-
Roger Dingledine