Opened 9 years ago

Closed 6 years ago

#1092 closed defect (wontfix)

NSAS_INVALID_RESPONSE is internal error?

Reported by: jreed Owned by: UnAssigned
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: High
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 3 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

My resolver logs are full of entries like the following:

2011-07-05 15:58:30.997 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for l.gtld-servers.net. but got invalid response
2011-07-05 15:58:31.000 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for aloe.arin.net. but got invalid response
2011-07-05 15:58:31.001 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for y.arin.net. but got invalid response
2011-07-05 15:58:31.019 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for e2.nstld.com. but got invalid response
...
2011-07-05 16:34:07.448 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for ns1.pbi.NET. but got invalid response
2011-07-05 16:34:07.451 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for NS2.SWBELL.NET. but got invalid response
2011-07-05 16:34:07.451 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for NS1.SWBELL.NET. but got invalid response
2011-07-05 16:34:07.534 ERROR [b10-resolver.nsas] NSAS_INVALID_RESPONSE queried for NS3.SBCGLOBAL.NET. but got invalid response

I looked in log messages guide since this error was too vague to be useful to me.

The messages guide says "This message indicates an internal error in the NSAS. Please raise a
bug report."

So here is the report :)

Subtickets

Change History (19)

comment:1 Changed 9 years ago by shane

  • Defect Severity changed from N/A to High
  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 9 years ago by stephen

  • Milestone changed from Year 3 Task Backlog to Sprint-20110816

comment:3 Changed 9 years ago by zhanglikun

  • Owner set to zhanglikun
  • Status changed from new to assigned

comment:4 Changed 9 years ago by jelte

  • Estimated Difficulty changed from 0.0 to 3

comment:5 Changed 9 years ago by zhanglikun

  • Owner changed from zhanglikun to UnAssigned
  • Status changed from assigned to reviewing

I think the behavior is normal, just we should refine the error message to make it more readable.

NSAS try to get the address(AAAA and A) for each name server, if the answer message has other rcode except NOERROR, or rrset count of answer section is zero, it will report the error "NSAS_INVALID_RESPONSE queried for ns1.pbi.NET. but got invalid response".

most name servers don't have IPv6 address(AAAA), so when it is asked for AAAA record, the error message will printed out.

My suggestion for the new error message is:

  • change the type to "WARNING", instead of ERROR.
  • NSAS_INVALID_RESPONSE queried for a.edu-servers.net.(type:AAAA) but got invalid response(rcode: NOERROR, answer section: empty).

comment:6 Changed 9 years ago by vorner

  • Owner changed from UnAssigned to vorner

comment:7 Changed 9 years ago by vorner

  • Owner changed from vorner to zhanglikun

Hello

Thanks for the investigation. If it is really as you say (which is possible, whoever wrote the description might have gotten confused by the failureInternal, so he said it is internal error), the message is safe.

Maybe if the thing is common (as you say, most NSs don't have an AAAA record), it should maybe be even INFO, not WARN (for one, we don't want to make admins panic, and for another, they can do nothing about these WARNs and this will be very common message, so to avoid SPAMing).

I think the „short“ message you propose with the parenthesis doesn't help much. Does it mean the one we got is with NOERROR and empty? Or that the one we wanted should be NOERROR and empty? Or should the NOERROR and empty be result of replacement and not this exact verbatim message? Maybe say something like „queried for $NAME/$TYPE, but got no useful data as answer (rcode: $RCODE, count of RRs: $RRCOUNT)“?

Anyway, the long description should be updated as well (while the short one is not very helpful, the long one is plain wrong). Any suggestions?

Thank you

comment:8 Changed 9 years ago by zhanglikun

  • Owner changed from zhanglikun to vorner

Yeah, I think your message maybe more informational. but I think the message should be used for debug(it means it should in high log level), admins maybe not be interested in with it, since it's too common if with low log level.

comment:9 Changed 9 years ago by vorner

  • Owner changed from vorner to zhanglikun

I can agree that the exact wording of the short one is less relevant in this case.

However, what about the long one? That one really needs to be solved.

comment:10 Changed 8 years ago by jelte

  • Milestone changed from Sprint-20110927 to Sprint-20111011

comment:11 Changed 8 years ago by jelte

  • Milestone changed from Sprint-20111011 to Sprint-20111025

comment:12 Changed 8 years ago by jinmei

What's the current status of this ticket? It's not been updated for over 2 months and is still in review queue.
If it's not going to be solved pretty soon, IMO it should at least be moved back to normal queue (also make it
unassigned so that someone can take it over if necessary).

comment:13 Changed 8 years ago by zhanglikun

  • Owner changed from zhanglikun to UnAssigned

Left the ticket be unassigned for getting different options.

comment:14 Changed 8 years ago by jelte

  • Milestone changed from Sprint-20111025 to Sprint-20111108

comment:15 Changed 8 years ago by jelte

  • Milestone changed from Sprint-20111108 to Year 3 Task Backlog

Oops, should not have moved this to sprint yet, I'll discuss this ticket offline with Likun.

comment:16 Changed 8 years ago by jelte

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

Okay so it seems there has only been some discussion on this, and no actual changes yet. I'm putting this as new work on the next-sprint-proposed queue.

I think either removing the log message completely or setting it to a very high debug level is fine, btw

comment:17 Changed 7 years ago by shane

  • Owner changed from UnAssigned to shane
  • Status changed from reviewing to accepted

Comments indicate this is not actually in review.

comment:18 Changed 7 years ago by shane

  • Owner changed from shane to UnAssigned
  • Status changed from accepted to assigned

comment:19 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from assigned to closed

Kea project is DHCP only. Closing stale DNS-related tickets.

If you're interested in DNS, please see Bundy project http://bundy-dns.de

Note: See TracTickets for help on using tickets.