|
@@ -78,6 +78,9 @@ different TTL values. This isn't allowed on the wire and is considered
|
|
|
an error, so we set it to the lowest value we found (but we don't modify the
|
|
|
database). The data in database should be checked and fixed.
|
|
|
|
|
|
+% DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 resulted in CNAME %5
|
|
|
+(TBD)
|
|
|
+
|
|
|
% DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1
|
|
|
When searching for a domain, the program met a delegation to a different zone
|
|
|
at the given domain name. It will return that one instead.
|
|
@@ -105,17 +108,14 @@ domain name, class and type.
|
|
|
The data returned by the database backend contained data for the given domain
|
|
|
name and class, but not for the given type.
|
|
|
|
|
|
+% DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5
|
|
|
+(TBD)
|
|
|
+
|
|
|
% DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %2
|
|
|
The data returned by the database backend contained data for the given domain
|
|
|
name, and it either matches the type or has a relevant type. The RRset that is
|
|
|
returned is printed.
|
|
|
|
|
|
-% DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 resulted in CNAME %5
|
|
|
-(TBD)
|
|
|
-
|
|
|
-% DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5
|
|
|
-(TBD)
|
|
|
-
|
|
|
% DATASRC_DATABASE_ITERATE iterating zone %1
|
|
|
The program is reading the whole zone, eg. not searching for data, but going
|
|
|
through each of the RRsets there.
|
|
@@ -133,6 +133,41 @@ were found to be different. This isn't allowed on the wire and is considered
|
|
|
an error, so we set it to the lowest value we found (but we don't modify the
|
|
|
database). The data in database should be checked and fixed.
|
|
|
|
|
|
+% DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3
|
|
|
+Debug information. A set of updates to a zone has been successfully
|
|
|
+committed to the corresponding database backend. The zone name,
|
|
|
+its class and the database name are printed.
|
|
|
+
|
|
|
+% DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3
|
|
|
+Debug information. A zone updater object is created to make updates to
|
|
|
+the shown zone on the shown backend database.
|
|
|
+
|
|
|
+% DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3
|
|
|
+Debug information. A zone updater object is destroyed, either successfully
|
|
|
+or after failure of, making updates to the shown zone on the shown backend
|
|
|
+database.
|
|
|
+
|
|
|
+% DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3
|
|
|
+A zone updater is being destroyed without committing the changes.
|
|
|
+This would typically mean the update attempt was aborted due to some
|
|
|
+error, but may also be a bug of the application that forgets committing
|
|
|
+the changes. The intermediate changes made through the updater won't
|
|
|
+be applied to the underlying database. The zone name, its class, and
|
|
|
+the underlying database name are shown in the log message.
|
|
|
+
|
|
|
+% DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4
|
|
|
+A zone updater is being destroyed without committing the changes to
|
|
|
+the database, and attempts to rollback incomplete updates, but it
|
|
|
+unexpectedly fails. The higher level implementation does not expect
|
|
|
+it to fail, so this means either a serious operational error in the
|
|
|
+underlying data source (such as a system failure of a database) or
|
|
|
+software bug in the underlying data source implementation. In either
|
|
|
+case if this message is logged the administrator should carefully
|
|
|
+examine the underlying data source to see what exactly happens and
|
|
|
+whether the data is still valid. The zone name, its class, and the
|
|
|
+underlying database name as well as the error message thrown from the
|
|
|
+database module are shown in the log message.
|
|
|
+
|
|
|
% DATASRC_DATABASE_WILDCARD constructing RRset %3 from wildcard %2 in %1
|
|
|
The database doesn't contain directly matching domain, but it does contain a
|
|
|
wildcard one which is being used to synthesize the answer.
|
|
@@ -493,12 +528,12 @@ enough information for it. The code is 1 for error, 2 for not implemented.
|
|
|
% DATASRC_SQLITE_CLOSE closing SQLite database
|
|
|
Debug information. The SQLite data source is closing the database file.
|
|
|
|
|
|
-% DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1'
|
|
|
-The database file is being opened so it can start providing data.
|
|
|
-
|
|
|
% DATASRC_SQLITE_CONNCLOSE Closing sqlite database
|
|
|
The database file is no longer needed and is being closed.
|
|
|
|
|
|
+% DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1'
|
|
|
+The database file is being opened so it can start providing data.
|
|
|
+
|
|
|
% DATASRC_SQLITE_CREATE SQLite data source created
|
|
|
Debug information. An instance of SQLite data source is being created.
|
|
|
|
|
@@ -601,38 +636,3 @@ data source.
|
|
|
% DATASRC_UNEXPECTED_QUERY_STATE unexpected query state
|
|
|
This indicates a programming error. An internal task of unknown type was
|
|
|
generated.
|
|
|
-
|
|
|
-% DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3
|
|
|
-Debug information. A zone updater object is created to make updates to
|
|
|
-the shown zone on the shown backend database.
|
|
|
-
|
|
|
-% DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3
|
|
|
-Debug information. A zone updater object is destroyed, either successfully
|
|
|
-or after failure of, making updates to the shown zone on the shown backend
|
|
|
-database.
|
|
|
-
|
|
|
-%DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3
|
|
|
-A zone updater is being destroyed without committing the changes.
|
|
|
-This would typically mean the update attempt was aborted due to some
|
|
|
-error, but may also be a bug of the application that forgets committing
|
|
|
-the changes. The intermediate changes made through the updater won't
|
|
|
-be applied to the underlying database. The zone name, its class, and
|
|
|
-the underlying database name are shown in the log message.
|
|
|
-
|
|
|
-%DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4
|
|
|
-A zone updater is being destroyed without committing the changes to
|
|
|
-the database, and attempts to rollback incomplete updates, but it
|
|
|
-unexpectedly fails. The higher level implementation does not expect
|
|
|
-it to fail, so this means either a serious operational error in the
|
|
|
-underlying data source (such as a system failure of a database) or
|
|
|
-software bug in the underlying data source implementation. In either
|
|
|
-case if this message is logged the administrator should carefully
|
|
|
-examine the underlying data source to see what exactly happens and
|
|
|
-whether the data is still valid. The zone name, its class, and the
|
|
|
-underlying database name as well as the error message thrown from the
|
|
|
-database module are shown in the log message.
|
|
|
-
|
|
|
-% DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3
|
|
|
-Debug information. A set of updates to a zone has been successfully
|
|
|
-committed to the corresponding database backend. The zone name,
|
|
|
-its class and the database name are printed.
|