[warn] Received http status code 404 ("Consensus is too old") from server '194.109.206.212:80' while fetching consensus directory.

[toralf]

the local time is ok :

date -u
Sat Mar  3 16:18:01 UTC 2018

cat </dev/tcp/time.nist.gov/13

ntpdate -q 2.de.pool.ntp.org
server 2a01:4f8:172:326b::2, stratum 2, offset -0.000140, delay 0.02594
server 2a01:4f8:221:3b02::101:1, stratum 2, offset -0.000601, delay 0.02594
server 2a01:238:439c:1900::3:1, stratum 2, offset 0.000477, delay 0.04520
server 2a02:16d0:0:4::4, stratum 2, offset -0.002245, delay 0.03976
server 90.187.7.5, stratum 2, offset -0.002271, delay 0.04788
server 129.70.132.36, stratum 2, offset 0.002152, delay 0.04262
server 145.239.3.131, stratum 2, offset 0.001487, delay 0.03177
server 85.236.36.4, stratum 2, offset -0.000501, delay 0.03650
 3 Mar 17:18:09 ntpdate[18195]: adjust time server 2a01:4f8:221:3b02::101:1 offset -0.000601 sec

And I still get once a day or so _:

Mar 03 17:18:01.000 [warn] Received http status code 404 ("Consensus is too old") from server '194.109.206.212:80' while fetching consensus directory.
Mar 03 17:18:01.000 [notice] Tor 0.3.4.0-alpha-dev (git-efc105716283bbdf) opening log file.
Mar 03 17:18:02.000 [warn] Received http status code 404 ("Consensus is too old") from server '194.109.206.212:80' while fetching consensus directory.

tor version is 0.3.4-alpha-dev

[teor]

This is a problem with the remote relay, not with your relay. You can contact the operator of that relay and let them know if you want.

I think we should downgrade this message from warn to notice, because there's nothing that relay operators or clients can do about it.

[arma]

Is it always dizum that gives you this issue? Or does it happen with other dir auths too?

[arma]

Ah ha -- this isn't a time issue, it's an issue of whether that dir authority has a consensus it's willing to give you.

This response from dizum was added in #20511.

And it could plausibly come from a dir auth that's been down for a while and then comes back and doesn't have a fresh consensus to serve quite yet.

I think teor is right that there's nothing the relay operator can do when this happens. I'm tempted to wonder if we can move it to info, since notice will still make some people worried. But on the flip side, I'd only want to move it to info if we're confident Tor will always tolerate the situation well.

[teor]

I'd like it at notice, so we find out if Tor gets stuck after receiving a 404.
Maybe we can say "that's ok", or "trying another directory server".

[arma]

sounds good to me

[nickm]

Per our triage process, these tickets are pending removal from 0.3.4.

[nickm]

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

[teor]

0.3.1 is end of life, there are no more backports.
Tagging with 031-unreached-backport instead.

[teor]

0.3.2 is end of life, so 032-backport is now 032-unreached-backport.

[teor]

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

[teor]

Hmm, I guess they should still get 033-backport-unreached

[teor]

Fix 033-unreached-backport spelling.