mirror of
https://gitlab.isc.org/isc-projects/kea
synced 2025-08-30 21:45:37 +00:00
[master] regenerate xml from mes files
This commit is contained in:
Jeremy C. Reed
@@ -405,6 +405,27 @@ message associated with it has its own code.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="AUTH_RESPONSE_FAILURE">
|
||||
<term>AUTH_RESPONSE_FAILURE exception while building response to query: %1</term>
|
||||
<listitem><para>
|
||||
This is a debug message, generated by the authoritative server when an
|
||||
attempt to create a response to a received DNS packet has failed. The
|
||||
reason for the failure is given in the log message. A SERVFAIL response
|
||||
is sent back. The most likely cause of this is an error in the data
|
||||
source implementation; it is either creating bad responses or raising
|
||||
exceptions itself.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="AUTH_RESPONSE_FAILURE_UNKNOWN">
|
||||
<term>AUTH_RESPONSE_FAILURE_UNKNOWN unknown exception while building response to query</term>
|
||||
<listitem><para>
|
||||
This debug message is similar to AUTH_RESPONSE_FAILURE, but further
|
||||
details about the error are unknown, because it was signaled by something
|
||||
which is not an exception. This is definitely a bug.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="AUTH_RESPONSE_RECEIVED">
|
||||
<term>AUTH_RESPONSE_RECEIVED received response message, ignoring</term>
|
||||
<listitem><para>
|
||||
@@ -1618,6 +1639,15 @@ configuration is not stored.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="CFGMGR_RENAMED_CONFIG_FILE">
|
||||
<term>CFGMGR_RENAMED_CONFIG_FILE renamed configuration file %1 to %2, will create new %1</term>
|
||||
<listitem><para>
|
||||
BIND 10 has been started with the command to clear the configuration file.
|
||||
The existing file is backed up to the given file name, so that data is not
|
||||
immediately lost if this was done by accident.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="CFGMGR_STOPPED_BY_KEYBOARD">
|
||||
<term>CFGMGR_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down</term>
|
||||
<listitem><para>
|
||||
@@ -2943,8 +2973,10 @@ not have any DS record. This indicates problem with the provided data.
|
||||
<varlistentry id="DATASRC_QUERY_NO_ZONE">
|
||||
<term>DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'</term>
|
||||
<listitem><para>
|
||||
Lookup of domain failed because the data have no zone that contain the
|
||||
domain. Maybe someone sent a query to the wrong server for some reason.
|
||||
Debug information. Lookup of domain failed because the datasource
|
||||
has no zone that contains the domain. Maybe someone sent a query
|
||||
to the wrong server for some reason. This may also happen when
|
||||
looking in the datasource for addresses for NS records.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
@@ -3281,6 +3313,200 @@ generated.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_BACKUP">
|
||||
<term>DBUTIL_BACKUP created backup of %1 in %2</term>
|
||||
<listitem><para>
|
||||
A backup for the given database file was created. Same of original file and
|
||||
backup are given in the output message.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_CHECK_ERROR">
|
||||
<term>DBUTIL_CHECK_ERROR unable to check database version: %1</term>
|
||||
<listitem><para>
|
||||
There was an error while trying to check the current version of the database
|
||||
schema. The error is shown in the message.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_CHECK_NOCONFIRM">
|
||||
<term>DBUTIL_CHECK_NOCONFIRM --noconfirm is not compatible with --check</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was called with --check and --noconfirm. --noconfirm only has
|
||||
meaning with --upgrade, so this is considered an error.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_CHECK_OK">
|
||||
<term>DBUTIL_CHECK_OK this is the latest version of the database schema. No upgrade is required</term>
|
||||
<listitem><para>
|
||||
The database schema version has been checked, and is up to date.
|
||||
No action is required.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_CHECK_UPGRADE_NEEDED">
|
||||
<term>DBUTIL_CHECK_UPGRADE_NEEDED re-run this program with the --upgrade switch to upgrade</term>
|
||||
<listitem><para>
|
||||
The database schema version is not up to date, and an update is required.
|
||||
Please run the dbutil tool again, with the --upgrade argument.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_COMMAND_NONE">
|
||||
<term>DBUTIL_COMMAND_NONE must select one of --check or --upgrade</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was called with neither --check nor --upgrade. One action must be
|
||||
provided.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_COMMAND_UPGRADE_CHECK">
|
||||
<term>DBUTIL_COMMAND_UPGRADE_CHECK --upgrade is not compatible with --check</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was called with both the commands --upgrade and --check. Only one
|
||||
action can be performed at a time.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_DATABASE_MAY_BE_CORRUPT">
|
||||
<term>DBUTIL_DATABASE_MAY_BE_CORRUPT database file %1 may be corrupt, restore it from backup (%2)</term>
|
||||
<listitem><para>
|
||||
The upgrade failed while it was in progress; the database may now be in an
|
||||
inconsistent state, and it is advised to restore it from the backup that was
|
||||
created when b10-dbutil started.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_EXECUTE">
|
||||
<term>DBUTIL_EXECUTE Executing SQL statement: %1</term>
|
||||
<listitem><para>
|
||||
Debug message; the given SQL statement is executed
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_FILE">
|
||||
<term>DBUTIL_FILE Database file: %1</term>
|
||||
<listitem><para>
|
||||
The database file that is being checked.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_NO_FILE">
|
||||
<term>DBUTIL_NO_FILE must supply name of the database file to upgrade</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was called without a database file. Currently, it cannot find this
|
||||
file on its own, and it must be provided.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_STATEMENT_ERROR">
|
||||
<term>DBUTIL_STATEMENT_ERROR failed to execute %1: %2</term>
|
||||
<listitem><para>
|
||||
The given database statement failed to execute. The error is shown in the
|
||||
message.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_TOO_MANY_ARGUMENTS">
|
||||
<term>DBUTIL_TOO_MANY_ARGUMENTS too many arguments to the command, maximum of one expected</term>
|
||||
<listitem><para>
|
||||
There were too many command-line arguments to b10-dbutil
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_CANCELED">
|
||||
<term>DBUTIL_UPGRADE_CANCELED upgrade canceled; database has not been changed</term>
|
||||
<listitem><para>
|
||||
The user aborted the upgrade, and b10-dbutil will now exit.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_DBUTIL">
|
||||
<term>DBUTIL_UPGRADE_DBUTIL please get the latest version of b10-dbutil and re-run</term>
|
||||
<listitem><para>
|
||||
A database schema was found that was newer than this version of dbutil, which
|
||||
is apparently out of date and should be upgraded itself.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_FAILED">
|
||||
<term>DBUTIL_UPGRADE_FAILED upgrade failed: %1</term>
|
||||
<listitem><para>
|
||||
While the upgrade was in progress, an unexpected error occurred. The error
|
||||
is shown in the message.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_NOT_ATTEMPTED">
|
||||
<term>DBUTIL_UPGRADE_NOT_ATTEMPTED database upgrade was not attempted</term>
|
||||
<listitem><para>
|
||||
Due to the earlier failure, the database schema upgrade was not attempted,
|
||||
and b10-dbutil will now exit.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_NOT_NEEDED">
|
||||
<term>DBUTIL_UPGRADE_NOT_NEEDED database already at latest version, no upgrade necessary</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was told to upgrade the database schema, but it is already at the
|
||||
latest version.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_NOT_POSSIBLE">
|
||||
<term>DBUTIL_UPGRADE_NOT_POSSIBLE database at a later version than this utility can support</term>
|
||||
<listitem><para>
|
||||
b10-dbutil was told to upgrade the database schema, but it is at a higher
|
||||
version than this tool currently supports. Please update b10-dbutil and try
|
||||
again.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_PREPARATION_FAILED">
|
||||
<term>DBUTIL_UPGRADE_PREPARATION_FAILED upgrade preparation failed: %1</term>
|
||||
<listitem><para>
|
||||
An unexpected error occurred while b10-dbutil was preparing to upgrade the
|
||||
database schema. The error is shown in the message
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADE_SUCCESFUL">
|
||||
<term>DBUTIL_UPGRADE_SUCCESFUL database upgrade successfully completed</term>
|
||||
<listitem><para>
|
||||
The database schema update was completed successfully.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_UPGRADING">
|
||||
<term>DBUTIL_UPGRADING upgrading database from %1 to %2</term>
|
||||
<listitem><para>
|
||||
An upgrade is in progress, the versions of the current upgrade action are shown.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_VERSION_CURRENT">
|
||||
<term>DBUTIL_VERSION_CURRENT database version %1</term>
|
||||
<listitem><para>
|
||||
The current version of the database schema.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_VERSION_HIGH">
|
||||
<term>DBUTIL_VERSION_HIGH database is at a later version (%1) than this program can cope with (%2)</term>
|
||||
<listitem><para>
|
||||
The database schema is at a higher version than b10-dbutil knows about.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DBUTIL_VERSION_LOW">
|
||||
<term>DBUTIL_VERSION_LOW database version %1, latest version is %2.</term>
|
||||
<listitem><para>
|
||||
The database schema is not up to date, the current version and the latest
|
||||
version are in the message.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="DDNS_ACCEPT_FAILURE">
|
||||
<term>DDNS_ACCEPT_FAILURE error accepting a connection: %1</term>
|
||||
<listitem><para>
|
||||
@@ -4686,8 +4912,8 @@ This informational message is output when the resolver has shut down.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="RESOLVER_SHUTDOWN (1)">
|
||||
<term>RESOLVER_SHUTDOWN (1) asked to shut down, doing so</term>
|
||||
<varlistentry id="RESOLVER_SHUTDOWN_RECEIVED">
|
||||
<term>RESOLVER_SHUTDOWN_RECEIVED received command to shut down</term>
|
||||
<listitem><para>
|
||||
A debug message noting that the server was asked to terminate and is
|
||||
complying to the request.
|
||||
@@ -5264,6 +5490,35 @@ likely cause is a PYTHONPATH problem.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_IXFR_TRANSFER_SUCCESS">
|
||||
<term>XFRIN_IXFR_TRANSFER_SUCCESS incremental IXFR transfer of zone %1 succeeded (messages: %2, changesets: %3, deletions: %4, additions: %5, bytes: %6, run time: %7 seconds, %8 bytes/second)</term>
|
||||
<listitem><para>
|
||||
The IXFR transfer for the given zone was successful.
|
||||
The provided information contains the following values:
|
||||
</para><para>
|
||||
messages: Number of overhead DNS messages in the transfer.
|
||||
</para><para>
|
||||
changesets: Number of difference sequences.
|
||||
</para><para>
|
||||
deletions: Number of Resource Records deleted by all the changesets combined,
|
||||
including the SOA records.
|
||||
</para><para>
|
||||
additions: Number of Resource Records added by all the changesets combined,
|
||||
including the SOA records.
|
||||
</para><para>
|
||||
bytes: Full size of the transfer data on the wire.
|
||||
</para><para>
|
||||
run time: Time (in seconds) the complete ixfr took.
|
||||
</para><para>
|
||||
bytes/second: Transfer speed.
|
||||
</para><para>
|
||||
Note that there is no cross-checking of additions and deletions; if the same
|
||||
RR gets added and deleted in multiple changesets, it is counted each time;
|
||||
therefore, for each changeset, there should at least be 1 deletion and 1
|
||||
addition (the updated SOA record).
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_IXFR_UPTODATE">
|
||||
<term>XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating</term>
|
||||
<listitem><para>
|
||||
@@ -5330,6 +5585,25 @@ daemon will now shut down.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_TRANSFER_SUCCESS">
|
||||
<term>XFRIN_TRANSFER_SUCCESS full %1 transfer of zone %2 succeeded (messages: %3, records: %4, bytes: %5, run time: %6 seconds, %7 bytes/second)</term>
|
||||
<listitem><para>
|
||||
The AXFR transfer of the given zone was successful.
|
||||
The provided information contains the following values:
|
||||
</para><para>
|
||||
messages: Number of overhead DNS messages in the transfer
|
||||
</para><para>
|
||||
records: Number of Resource Records in the full transfer, excluding the
|
||||
final SOA record that marks the end of the AXFR.
|
||||
</para><para>
|
||||
bytes: Full size of the transfer data on the wire.
|
||||
</para><para>
|
||||
run time: Time (in seconds) the complete axfr took
|
||||
</para><para>
|
||||
bytes/second: Transfer speed
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_UNKNOWN_ERROR">
|
||||
<term>XFRIN_UNKNOWN_ERROR unknown error: %1</term>
|
||||
<listitem><para>
|
||||
@@ -5406,13 +5680,6 @@ the SOA record has been checked, and a zone transfer has been started.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_XFR_TRANSFER_SUCCESS">
|
||||
<term>XFRIN_XFR_TRANSFER_SUCCESS %1 transfer of zone %2 succeeded</term>
|
||||
<listitem><para>
|
||||
The XFR transfer of the given zone was successfully completed.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="XFRIN_ZONE_CREATED">
|
||||
<term>XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created</term>
|
||||
<listitem><para>
|
||||
@@ -6012,9 +6279,11 @@ a bug report.
|
||||
<term>ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager</term>
|
||||
<listitem><para>
|
||||
An XFRIN operation has failed but the zone that was the subject of the
|
||||
operation is not being managed by the zone manager. This may indicate
|
||||
an error in the program (as the operation should not have been initiated
|
||||
if this were the case). Please submit a bug report.
|
||||
operation is not being managed by the zone manager. This can be either the
|
||||
result of a bindctl command to transfer in a currently unknown (or mistyped)
|
||||
zone, or, if this error appears without the administrator giving transfer
|
||||
commands, it can indicate an error in the program, as it should not have
|
||||
initiated transfers of unknown zones on its own.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user