#24044 closed defect (fixed)

Resolved [scrubbed] which was already resolved; ignoring

Reported by: mo Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.2.2-alpha
Severity: Normal Keywords: 033-triage-20180320, 033-removed-20180320
Cc: s7r Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm seeing lots of these warnings on Tor 0.3.2.2-alpha (git-cd94726331b8fc28 from the experimental repository) across various machines (exit relays). I should test this with 0.3.2.3-alpha too.

Oct 30 01:15:56: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:15:59: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:05: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:12: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:14: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:19: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:19: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:49: Resolved [scrubbed] which was already resolved; ignoring
Oct 30 01:16:59: Resolved [scrubbed] which was already resolved; ignoring

Child Tickets

Change History (12)

comment:1 Changed 23 months ago by arma

I wonder if anybody running an exit relay on Tor 0.3.1 sees these too?

comment:2 Changed 23 months ago by arma

What's happening here is that we're getting a dns answer when we don't think we asked a dns question.

comment:3 Changed 23 months ago by nickm

Milestone: Tor: 0.3.3.x-final

comment:4 Changed 23 months ago by arma

I wonder if our recent dns exit relay fixes will help this one.

comment:5 Changed 22 months ago by s7r

Cc: s7r added

Getting it as well and didn't use to on 0.3.2.2-alpha-dev (git-51e47481fc6f131d). I ll switch to latest git master and confirm if I still get it or not.

comment:6 Changed 22 months ago by Dhalgren

likely is #18580

message not mentioned in the ticket, but is the initial symptom appearing at the top of the two linked tor-relays posts

cause is volumes of Unbound responses appearing within the 120 second resolve effort, but long after eventdns discarded the requests

solution is upgrading to 0.3.2.4+ or tuning resolve.conf per

https://trac.torproject.org/projects/tor/wiki/doc/DnsResolver#TuningeventdnscomponentofTorDaemon

comment:7 Changed 18 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:8 Changed 18 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:9 Changed 18 months ago by nickm

Milestone: Tor: 0.3.3.x-finalTor: unspecified

These tickets were marked as removed, and nobody has said that they can fix them. Let's remember to look at 033-removed-20180320 as we re-evaluate our triage process, to see whether we're triaging out unnecessarily, and to evaluate whether we're deferring anything unnecessarily. But for now, we can't do these: we need to fix the 033-must stuff now.

comment:10 Changed 18 months ago by arma

mo, s7r, are you still seeing these messages with more recent versions of Tor? Specifically, ones that include the #18580 fix.

comment:11 Changed 18 months ago by mo

Not a single one! I would say we can close this ticket.

comment:12 Changed 18 months ago by s7r

Resolution: fixed
Status: newclosed

Not a single one as well. Still using unbound all around. Let's close it for now.

Note: See TracTickets for help on using tickets.