ERROR: Unable to retrieve the consensus from maatuska (http://171.25.193.9:443/tor/status-vote/current/consensus): timed out NOTICE: Downloading the consensus from longclaw took 13.2s. Median download time is 1.7s: longclaw => 13.2s, dizum => 0.9s, bastet => 1.9s, gabelmoo => 0.8s, moria1 => 637.0s, dannenberg => 0.9s, Faravahar => 1.7s NOTICE: Downloading the consensus from moria1 took 637.0s. Median download time is 1.7s: longclaw => 13.2s, dizum => 0.9s, bastet => 1.9s, gabelmoo => 0.8s, moria1 => 637.0s, dannenberg => 0.9s, Faravahar => 1.7s ERROR: Unable to retrieve the vote from maatuska (http://171.25.193.9:443/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: longclaw, dizum, bastet, gabelmoo, moria1, dannenberg, Faravahar
Hi Damian,
We've seen a lot of these for maatuska, especially votes, the last couple of days.
ERROR: Unable to retrieve the consensus from maatuska
...
ERROR: Unable to retrieve the vote from maatuska
I'm puzzled and wonder if you have any further information that could help debugging this? From where are you fetching? Do you know if the network provider at that place are experiencing any network issues?
Thanks, Linus
Hi Linus,
On 14. Jan 2020, at 20:18, Linus Nordberg linus@nordberg.se wrote:
We've seen a lot of these for maatuska, especially votes, the last couple of days.
ERROR: Unable to retrieve the consensus from maatuska
...
ERROR: Unable to retrieve the vote from maatuska
I'm puzzled and wonder if you have any further information that could help debugging this? From where are you fetching? Do you know if the network provider at that place are experiencing any network issues?
I think the more likely explanation is that maatuska has bad connectivity (intermittently?). See these logs from gabelmoo:
Jan 15 00:24:55.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 00:00:00; we were expecting 2020-01-15 01:00:00 Jan 15 01:26:23.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 01:00:00; we were expecting 2020-01-15 02:00:00 Jan 15 02:38:26.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 02:00:00; we were expecting 2020-01-15 03:00:00 Jan 15 03:29:11.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 03:00:00; we were expecting 2020-01-15 04:00:00 Jan 15 04:18:10.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 04:00:00; we were expecting 2020-01-15 05:00:00
Cheers Sebastian
Sebastian Hahn mail@sebastianhahn.net wrote Wed, 15 Jan 2020 06:14:33 +0100:
Hi Linus,
On 14. Jan 2020, at 20:18, Linus Nordberg linus@nordberg.se wrote:
We've seen a lot of these for maatuska, especially votes, the last couple of days.
ERROR: Unable to retrieve the consensus from maatuska
...
ERROR: Unable to retrieve the vote from maatuska
I'm puzzled and wonder if you have any further information that could help debugging this? From where are you fetching? Do you know if the network provider at that place are experiencing any network issues?
I think the more likely explanation is that maatuska has bad connectivity (intermittently?). See these logs from gabelmoo:
Jan 15 00:24:55.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 00:00:00; we were expecting 2020-01-15 01:00:00 Jan 15 01:26:23.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 01:00:00; we were expecting 2020-01-15 02:00:00 Jan 15 02:38:26.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 02:00:00; we were expecting 2020-01-15 03:00:00 Jan 15 03:29:11.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 03:00:00; we were expecting 2020-01-15 04:00:00 Jan 15 04:18:10.000 [warn] Rejecting vote from 171.25.193.9 with valid-after time of 2020-01-15 04:00:00; we were expecting 2020-01-15 05:00:00
Thanks Sebastian. I had done a bad job at diagnosing before asking Damian. My apologies.
This seems to be my tor. Looking into it.
tor-consensus-health@lists.torproject.org