Commit 4f82e3bd authored by Stephen Morris's avatar Stephen Morris

[trac1035] Changes to message descriptions

... and correct a couple of IDs missed first time round.
parent 6661b327
......@@ -276,7 +276,7 @@ class NameserverEntry::ResolverCallback :
// If we found it, use it. If not, create a new one.
entries.push_back(found ? *found : AddressEntry(
IOAddress(address), 1));
LOG_DEBUG(nsas_logger, NSAS_DBG_RESULTS, NSAS_NSLKUPSUCC)
LOG_DEBUG(nsas_logger, NSAS_DBG_RESULTS, NSAS_FOUND_ADDRESS)
.arg(address).arg(entry_->getName());
}
......@@ -322,7 +322,7 @@ class NameserverEntry::ResolverCallback :
* So mark the current address family as unreachable.
*/
virtual void failure() {
LOG_DEBUG(nsas_logger, NSAS_DBG_RESULTS, NSAS_NSLKUPFAIL)
LOG_DEBUG(nsas_logger, NSAS_DBG_RESULTS, NSAS_NS_LOOKUP_FAIL)
.arg(type_).arg(entry_->getName());
Lock lock(entry_->mutex_);
failureInternal(lock);
......
......@@ -14,47 +14,54 @@
$NAMESPACE isc::nsas
% NSAS_INVALID_RESPONSE queried for %1 but got invalid response
This message indicates an internal error in the nameserver address store
component (NSAS) of the resolver. The NSAS made a query for a RR for the
specified nameserver but received an invalid response. Either the success
function was called without a DNS message or the message was invalid on some
way. (In the latter case, the error should have been picked up elsewhere in
the processing logic, hence the raising of the error here.)
% NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1
A debug message issued when the NSAS (nameserver address store - part
of the resolver) is making a callback into the resolver to retrieve the
address records for the specified nameserver.
% NSAS_FOUND_ADDRESS found address %1 for %2
A debug message issued when the NSAS (nameserver address store - part
of the resolver) has retrieved the given address for the specified
nameserver through an external query.
% NSAS_INVALID_RESPONSE queried for %1 but got invalid response
The NSAS made a query for a RR for the specified nameserver but received
an invalid response. Either the success function was called without a
DNS message or the message was invalid on some way. (In the latter case,
the error should have been picked up elsewhere in the processing logic,
hence the raising of the error here.)
% NSAS_WRONG_ANSWER queried for %1 RR of type/class %2/%3, received response %4/%5
This message indicates an internal error in the nameserver address store
component (NSAS) of the resolver. The NSAS made a query for the given RR
type and class, but instead received an answer with the given type and class.
% NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled
A debug message, this is output when a NSAS (nameserver address store -
part of the resolver) lookup for a zone has been canceled.
% NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1
A debug message, this is output when a call is made to the nameserver address
store (part of the resolver) to obtain the nameservers for the specified zone.
% NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1
A debug message, the NSAS (nameserver address store - part of the resolver) is
making a callback into the resolver to retrieve the address records for the
specified nameserver.
% NSAS_NSLKUPFAIL failed to lookup any %1 for %2
A debug message, the NSAS (nameserver address store - part of the resolver)
has been unable to retrieve the specified resource record for the specified
nameserver. This is not necessarily a problem - the nameserver may be
unreachable, in which case the NSAS will try other nameservers in the zone.
% NSAS_NSLKUPSUCC found address %1 for %2
A debug message, the NSAS (nameserver address store - part of the resolver)
has retrieved the given address for the specified nameserver through an
external query.
% NSAS_UPDATE_RTT update RTT for %1: was %2 ms, is now %3 ms
component (NSAS) of the resolver. Please raise a bug report.
% NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled
A debug message issued when an NSAS (nameserver address store - part of
the resolver) lookup for a zone has been canceled.
% NSAS_NS_LOOKUP_FAIL failed to lookup any %1 for %2
A debug message issued when the NSAS (nameserver address store - part of
the resolver) has been unable to retrieve the specified resource record
for the specified nameserver. This is not necessarily a problem - the
nameserver may be unreachable, in which case the NSAS will try other
nameservers in the zone.
% NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1
A debug message output when a call is made to the nameserver address store
(part of the resolver) to obtain the nameservers for the specified zone.
% NSAS_UPDATE_RTT update RTT for %1: was %2 ms, is now %3 ms
A NSAS (nameserver address store - part of the resolver) debug message
reporting the round-trip time (RTT) for a query made to the specified
nameserver. The RTT has been updated using the value given and the new RTT is
displayed. (The RTT is subject to a calculation that damps out sudden
changes. As a result, the new RTT is not necessarily equal to the RTT
reported.)
reporting the update of a round-trip time (RTT) for a query made to the
specified nameserver. The RTT has been updated using the value given
and the new RTT is displayed. (The RTT is subject to a calculation that
damps out sudden changes. As a result, the new RTT used by the NSAS in
future decisions of which nameserver to use is not necessarily equal to
the RTT reported.)
% NSAS_WRONG_ANSWER queried for %1 RR of type/class %2/%3, received response %4/%5
A NSAS (nameserver address store - part of the resolver) made a query for
a resource record of a particular type and class, but instead received
an answer with a different given type and class.
This message indicates an internal error in the nameserver address store
component (NSAS) of the resolver. Please riase a bug report.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment