Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#2247 closed defect (duplicate)

"RRSIG is being added, but no RR of covered type found" should not be fatal

Reported by: jreed Owned by:
Priority: medium Milestone:
Component: data source Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 4 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

"AUTH_SERVER_FAILED server failed: RRSIG is being added, but no RR of covered type found" is fatal (via isc_throw) causing b10-auth and then bind10 to shutdown at startup. An error in a zone file should not cause the auth server to shutdown (since may server other working zones) and certainly should not shutdown boss (which makes it so you can't reconfigure).

This is from https://lists.isc.org/pipermail/bind10-users/2012-September/000393.html

The code is in
src/lib/datasrc/memory_datasrc.cc

Also to be discussed: why do we have log sentences hard-coded versus using unique logging messages. (This means we can't have explanations and can't do translations easily.)

Subtickets

Change History (6)

comment:1 Changed 7 years ago by muks

This should be reasonably easy to fix, but let's do it in the new load() implementation in src/lib/datasrc/memory/memory_client.cc to which we will switch to soon.

comment:2 Changed 7 years ago by vorner

Um, what is hardcoded?

comment:3 Changed 7 years ago by jelte

exception strings are hardcoded, which sometimes (like here) bubble up into the more general log error messages

comment:4 Changed 7 years ago by jinmei

This should have been solved as a side effect of background loading.

comment:5 Changed 7 years ago by jinmei

  • Resolution set to duplicate
  • Status changed from new to closed

comment:6 Changed 7 years ago by shane

  • Milestone New Tasks deleted
Note: See TracTickets for help on using tickets.