#25416: [warn] Received http status code 404 ("Consensus is too old") from server '194.109.206.212:80' while fetching consensus directory. -------------------------------------------------+------------------------- Reporter: toralf | Owner: (none) Type: defect | Status: new Priority: Medium | Milestone: Tor: | 0.3.4.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: tor-log, easy, intro, 033-backport, | Actual Points: 032-backport, 031-backport, 029-backport- | maybe | Parent ID: | Points: 0.1 Reviewer: | Sponsor: -------------------------------------------------+-------------------------
Comment (by 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. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25416#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs