Opened 9 years ago

Closed 8 years ago

Last modified 7 years ago

#1352 closed defect (fixed)

Flood of "Received http status code 404" Warning

Reported by: BarkerJr Owned by:
Priority: Medium Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version: 0.2.2.10-alpha
Severity: Keywords:
Cc: BarkerJr, Sebastian, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by nickm)

Received this warning:

Apr 12 09:43:28.945 [warn] Received http status code 404 ("Not Found") from server '194.109.206.212:80' while fetching "/tor/status/all.z". I'll try again soon.

302 times between 09:43:24.788 and 09:43:28.945. This warning should be throttled.

[Automatically added by flyspray2trac: Operating System: Redhat/CentOS Linux]

Child Tickets

Change History (10)

comment:1 Changed 9 years ago by Sebastian

Adding this comment from bug 1353, which is otherwise a duplicate:

The relay disappeared from the consensus. It should failover to a working authority.

comment:2 Changed 9 years ago by nickm

Description: modified (diff)
Milestone: Tor: 0.2.2.x-final
Priority: minornormal

comment:3 Changed 8 years ago by Sebastian

in connection_dir_download_networkstatus_failed() it looks like we're blaming all authorities for a failed fetch. Instead we should make sure to retry using a different one.

comment:4 Changed 8 years ago by nickm

We should fix the thing sebastian notes above, rate-limit the warning, and figure out why it might not have failed-over, if we can.

comment:5 Changed 8 years ago by nickm

(or we could just rate-limit, fix the issue, and stop investigating, under the theory that this is itermittent, and we'll be killing v2 statuses some time in 0.2.3.)

comment:6 Changed 8 years ago by Sebastian

Do we really think we will manage to do that in 0.2.3? We currently still rely on v2 pretty heavily for voting

comment:7 Changed 8 years ago by nickm

Status: newneeds_review

We've got to move away from using v2 votes: There are only two v2 authorities still running.

Given the deprecatedness of v2 votes, I think that we can just add the rate-limiting on the v2 vote 404 warning and call this bug resolved.

See branch 1352?

comment:8 in reply to:  6 Changed 8 years ago by arma

Replying to Sebastian:

Do we really think we will manage to do that in 0.2.3? We currently still rely on v2 pretty heavily for voting

We're actually really close to just having the v3 authorities post opinions to each other at :40 of each hour. They already know how to form the opinions, and there's already a format for that. We just have to schedule it.

comment:9 Changed 8 years ago by nickm

Resolution: Nonefixed
Status: needs_reviewclosed

Still looks fine to me 2 weeks later. Merging.

comment:10 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.