BIND 10 Messages Manual

This is the messages manual for BIND 10 version 1.2.0.

Abstract

This is the messages manual for BIND 10 version 1.2.0. The most up-to-date version of this document, along with other documents for BIND 10, can be found at http://bind10.isc.org/docs.


Table of Contents

1. Introduction
2. BIND 10 Messages

Chapter 1. Introduction

This document lists each message that can be logged by the programs in the BIND 10 package. Each entry in this manual is of the form:

IDENTIFICATION message-text

... where "IDENTIFICATION" is the message identification included in each message logged and "message-text" is the accompanying message text. The "message-text" may include placeholders of the form "%1", "%2" etc.; these parameters are replaced by relevant values when the message is logged.

Each entry is also accompanied by a description giving more information about the circumstances that result in the message being logged.

For information on configuring and using BIND 10 logging, refer to the BIND 10 Guide.

Chapter 2. BIND 10 Messages

ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1

A debug message informing about installing a file descriptor as a server. The file descriptor number is noted.

ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1

A debug message informing about installing a file descriptor as a server. The file descriptor number is noted.

ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed

A debug message, this records that the upstream fetch (a query made by the resolver on behalf of its client) to the specified address has completed.

ASIODNS_FETCH_STOPPED upstream fetch to %1(%2) has been stopped

An external component has requested the halting of an upstream fetch. This is an allowed operation, and the message should only appear if debug is enabled.

ASIODNS_OPEN_SOCKET error %1 opening %2 socket to %3(%4)

The asynchronous I/O code encountered an error when trying to open a socket of the specified protocol in order to send a message to the target address. The number of the system error that caused the problem is given in the message.

ASIODNS_READ_DATA error %1 reading %2 data from %3(%4)

The asynchronous I/O code encountered an error when trying to read data from the specified address on the given protocol. The number of the system error that caused the problem is given in the message.

ASIODNS_READ_TIMEOUT receive timeout while waiting for data from %1(%2)

An upstream fetch from the specified address timed out. This may happen for any number of reasons and is most probably a problem at the remote server or a problem on the network. The message will only appear if debug is enabled.

ASIODNS_SEND_DATA error %1 sending data using %2 to %3(%4)

The asynchronous I/O code encountered an error when trying to send data to the specified address on the given protocol. The number of the system error that caused the problem is given in the message.

ASIODNS_SYNC_UDP_CLOSE_FAIL failed to close a DNS/UDP socket: %1

This is the same to ASIODNS_UDP_CLOSE_FAIL but happens on the "synchronous UDP server", mainly used for the authoritative DNS server daemon.

ASIODNS_TCP_ACCEPT_FAIL failed to accept TCP DNS connection: %1

Accepting a TCP connection from a DNS client failed due to an error that could happen but should be rare. The reason for the error is included in the log message. The server still keeps accepting new connections, so unless it happens often it's probably okay to ignore this error. If the shown error indicates something like "too many open files", it's probably because the run time environment is too restrictive on this limitation, so consider adjusing the limit using a tool such as ulimit. If you see other types of errors too often, there may be something overlooked; please file a bug report in that case.

ASIODNS_TCP_CLEANUP_CLOSE_FAIL failed to close a DNS/TCP socket on port cleanup: %1

A TCP DNS server tried to close a TCP socket (one created on accepting a new connection or is already unused) as a step of cleaning up the corresponding listening port, but it failed to do that. This is generally an unexpected event and so is logged as an error. See also the description of ASIODNS_TCP_CLOSE_ACCEPTOR_FAIL.

ASIODNS_TCP_CLOSE_ACCEPTOR_FAIL failed to close listening TCP socket: %1

A TCP DNS server tried to close a listening TCP socket (for accepting new connections) as a step of cleaning up the corresponding listening port (e.g., on server shutdown or updating port configuration), but it failed to do that. This is generally an unexpected event and so is logged as an error. See ASIODNS_TCP_CLOSE_FAIL on the implication of related system resources.

ASIODNS_TCP_CLOSE_FAIL failed to close DNS/TCP socket with a client: %1

A TCP DNS server tried to close a TCP socket used to communicate with a client, but it failed to do that. While closing a socket should normally be an error-free operation, there have been known cases where this happened with a "connection reset by peer" error. This might be because of some odd client behavior, such as sending a TCP RST after establishing the connection and before the server closes the socket, but how exactly this could happen seems to be system dependent (i.e, it's not part of the standard socket API), so it's difficult to provide a general explanation. In any case, it is believed that an error on closing a socket doesn't mean leaking system resources (the kernel should clean up any internal resource related to the socket, just reporting an error detected in the close call), but, again, it seems to be system dependent. This message is logged at a debug level as it's known to happen and could be triggered by a remote node and it would be better to not be too verbose, but you might want to increase the log level and make sure there's no resource leak or other system level troubles when it's logged.

ASIODNS_TCP_CLOSE_NORESP_FAIL failed to close DNS/TCP socket with a client: %1

A TCP DNS server tried to close a TCP socket used to communicate with a client without returning an answer (which normally happens for zone transfer requests), but it failed to do that. See ASIODNS_TCP_CLOSE_FAIL for more details.

ASIODNS_TCP_GETREMOTE_FAIL failed to get remote address of a DNS TCP connection: %1

A TCP DNS server tried to get the address and port of a remote client on a connected socket but failed. It's expected to be rare but can still happen. See also ASIODNS_TCP_READLEN_FAIL.

ASIODNS_TCP_READDATA_FAIL failed to get DNS data on a TCP socket: %1

A TCP DNS server tried to read a DNS message (that follows a 2-byte length field) but failed. It's expected to be rare but can still happen. See also ASIODNS_TCP_READLEN_FAIL.

ASIODNS_TCP_READLEN_FAIL failed to get DNS data length on a TCP socket: %1

A TCP DNS server tried to get the length field of a DNS message (the first 2 bytes of a new chunk of data) but failed. This is generally expected to be rare but can still happen, e.g, due to an unexpected reset of the connection. A specific reason for the failure is included in the log message.

ASIODNS_TCP_WRITE_FAIL failed to send DNS message over a TCP socket: %1

A TCP DNS server tried to send a DNS message to a remote client but failed. It's expected to be rare but can still happen. See also ASIODNS_TCP_READLEN_FAIL.

ASIODNS_UDP_ASYNC_SEND_FAIL Error sending UDP packet to %1: %2

The low-level ASIO library reported an error when trying to send a UDP packet in asynchronous UDP mode. This can be any error reported by send_to(), and can indicate problems such as too high a load on the network, or a problem in the underlying library or system. This packet is dropped and will not be sent, but service should resume normally. If you see a single occurrence of this message, it probably does not indicate any significant problem, but if it is logged often, it is probably a good idea to inspect your network traffic.

ASIODNS_UDP_CLOSE_FAIL failed to close a DNS/UDP socket: %1

A UDP DNS server tried to close its UDP socket, but failed to do that. This is generally an unexpected event and so is logged as an error.

ASIODNS_UDP_RECEIVE_FAIL failed to receive UDP DNS packet: %1

Receiving a UDP packet from a DNS client failed due to an error that could happen but should be very rare. The server still keeps receiving UDP packets on this socket. The reason for the error is included in the log message. This log message is basically not expected to appear at all in practice; if it does, there may be some system level failure and other system logs may have to be checked.

ASIODNS_UDP_SYNC_RECEIVE_FAIL failed to receive UDP DNS packet: %1

This is the same to ASIODNS_UDP_RECEIVE_FAIL but happens on the "synchronous UDP server", mainly used for the authoritative DNS server daemon.

ASIODNS_UDP_SYNC_SEND_FAIL Error sending UDP packet to %1: %2

The low-level ASIO library reported an error when trying to send a UDP packet in synchronous UDP mode. See ASIODNS_UDP_ASYNC_SEND_FAIL for more information.

ASIODNS_UNKNOWN_ORIGIN unknown origin for ASIO error code %1 (protocol: %2, address %3)

An internal consistency check on the origin of a message from the asynchronous I/O module failed. This may indicate an internal error; please submit a bug report.

ASIODNS_UNKNOWN_RESULT unknown result (%1) when IOFetch::stop() was executed for I/O to %2(%3)

An internal error indicating that the termination method of the resolver's upstream fetch class was called with an unknown result code (which is given in the message). Please submit a bug report.

AUTH_AXFR_PROBLEM error handling AXFR request: %1

This is a debug message produced by the authoritative server when it has encountered an error processing an AXFR request. The message gives the reason for the error, and the server will return a SERVFAIL code to the sender.

AUTH_AXFR_UDP AXFR query received over UDP

This is a debug message output when the authoritative server has received an AXFR query over UDP. Use of UDP for AXFRs is not permitted by the protocol, so the server will return a FORMERR error to the sender.

AUTH_COMMAND_FAILED execution of command channel instruction '%1' failed: %2

Execution of the specified command by the authoritative server failed. The message contains the reason for the failure.

AUTH_CONFIG_CHANNEL_CREATED configuration session channel created

This is a debug message indicating that authoritative server has created the channel to the configuration manager. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_CONFIG_CHANNEL_ESTABLISHED configuration session channel established

This is a debug message indicating that authoritative server has established communication the configuration manager over the previously-created channel. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_CONFIG_CHANNEL_STARTED configuration session channel started

This is a debug message, issued when the authoritative server has posted a request to be notified when new configuration information is available. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1

An attempt to configure the server with information from the configuration database during the startup sequence has failed. The server will continue its initialization although it may not be configured in the desired way. The reason for the failure is given in the message. One common reason is that the server failed to acquire a socket bound to a privileged port (53 for DNS). In that case the reason in the log message should show something like "permission denied", and the solution would be to restart BIND 10 as a super (root) user.

AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1

At attempt to update the configuration the server with information from the configuration database has failed, the reason being given in the message.

AUTH_DATASRC_CLIENTS_BUILDER_COMMAND data source builder received command: %1

A debug message, showing when the separate thread for maintaining data source clients receives a command from the manager.

AUTH_DATASRC_CLIENTS_BUILDER_COMMAND_ERROR command execution failure: %1

The separate thread for maintaining data source clients failed to complete a command given by the main thread. In most cases this is some kind of configuration or temporary error such as an attempt to load a non-existent zone or a temporary DB connection failure. So the event is just logged and the thread keeps running. In some rare cases, however, this may indicate an internal bug and it may be better to restart the entire program, so the log message should be carefully examined.

AUTH_DATASRC_CLIENTS_BUILDER_FAILED data source builder thread stopped due to an exception: %1

The separate thread for maintaining data source clients has been terminated due to some uncaught exception. When this happens, the thread immediately terminates the entire process because the manager cannot always catch this condition in a timely fashion and it would be worse to keep running with such a half-broken state. This is really an unexpected event and should generally indicate an internal bug. It's advisable to file a bug report when this message is logged (and b10-auth subsequently stops).

AUTH_DATASRC_CLIENTS_BUILDER_FAILED_UNEXPECTED data source builder thread stopped due to an unexpected exception

This is similar to AUTH_DATASRC_CLIENTS_BUILDER_FAILED, but the exception type indicates it's not thrown either within the BIND 10 implementation or other standard-compliant libraries. This may rather indicate some run time failure than program errors. As in the other failure case, the thread terminates the entire process immediately after logging this message.

AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE loaded zone %1/%2

This debug message is issued when the separate thread for maintaining data source clients successfully loaded the named zone of the named class as a result of the 'loadzone' command.

AUTH_DATASRC_CLIENTS_BUILDER_LOAD_ZONE_NOCACHE skipped loading zone %1/%2 due to no in-memory cache

This debug message is issued when the separate thread for maintaining data source clients received a command to reload a zone but skipped it because the specified zone is not loaded in-memory (but served from an underlying data source). This could happen if the loadzone command is manually issued by a user but the zone name is misspelled, but a more likely cause is that the command is sent from another BIND 10 module (such as xfrin or DDNS). In the latter case it can be simply ignored because there is no need for explicit reloading.

AUTH_DATASRC_CLIENTS_BUILDER_RECONFIGURE_CONFIG_ERROR Error in data source configuration: %1

The thread for maintaining data source clients has received a command to reconfigure, but the parameter data (the new configuration) contains an error. The most likely cause is that the datasource-specific configuration data is not what the data source expects. The system is still running with the data sources that were previously configured (i.e. as if the configuration has not changed), and the configuration data needs to be checked. The specific problem is printed in the log message.

AUTH_DATASRC_CLIENTS_BUILDER_RECONFIGURE_DATASRC_ERROR Error setting up data source: %1

The thread for maintaining data source clients has received a command to reconfigure, but a data source failed to set up. This may be a problem with the data that is configured (e.g. unreadable files, inconsistent data, parser problems, database connection problems, etc.), but it could be a bug in the data source implementation as well. The system is still running with the data sources that were previously configured (i.e. as if the configuration has not changed). The specific problem is printed in the log message.

AUTH_DATASRC_CLIENTS_BUILDER_RECONFIGURE_ERROR Internal error setting up data source: %1

The thread for maintaining data source clients has received a command to reconfigure, but raised an exception while setting up data sources. This is most likely an internal error in a data source, or a bug in the data source or the system itself, but it is probably a good idea to verify the configuration first. The system is still running with the data sources that were previously configured (i.e. as if the configuration has not changed). The specific problem is printed in the log message.

AUTH_DATASRC_CLIENTS_BUILDER_RECONFIGURE_STARTED data source reconfiguration started

The thread for maintaining data source clients has received a command to reconfigure, and has now started this process.

AUTH_DATASRC_CLIENTS_BUILDER_RECONFIGURE_SUCCESS data source reconfiguration completed successfully

The thread for maintaining data source clients has finished reconfiguring the data source clients, and is now running with the new configuration.

AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_BAD_CLASS invalid RRclass %1 at segment update

A memory segment update message was sent to the authoritative server. But the class contained there is invalid. This means that the system is in an inconsistent state and the authoritative server aborts to minimize the problem. This is likely caused by a bug in the code.

AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_ERROR error updating the memory segment: %1

The authoritative server tried to update the memory segment, but the update failed. The authoritative server aborts to avoid system inconsistency. This is likely caused by a bug in the code.

AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_NO_DATASRC there's no data source named %2 in class %1

The authoritative server was asked to update the memory segment of the given data source, but no data source by that name was found. The authoritative server aborts because this indicates that the system is in an inconsistent state. This is likely caused by a bug in the code.

AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_UNKNOWN_CLASS unknown class %1 at segment update

A memory segment update message was sent to the authoritative server. The class name for which the update should happen is valid, but no client lists are configured for that class. The system is in an inconsistent state and the authoritative server aborts. This may be caused by a bug in the code.

AUTH_DATASRC_CLIENTS_BUILDER_STARTED data source builder thread started

A separate thread for maintaining data source clients has been started.

AUTH_DATASRC_CLIENTS_BUILDER_STOPPED data source builder thread stopped

The separate thread for maintaining data source clients has been stopped.

AUTH_DATASRC_CLIENTS_BUILDER_WAKE_ERR failed to wake up main thread: %1

A low-level error happened when trying to send data to the main thread to wake it up. Terminating to prevent inconsistent state and possiblu hang ups.

AUTH_DATASRC_CLIENTS_SHUTDOWN_ERROR error on waiting for data source builder thread: %1

This indicates that the separate thread for maintaining data source clients had been terminated due to an uncaught exception, and the manager notices that at its own termination. This is not an expected event, because the thread is implemented so it catches all exceptions internally. So, if this message is logged it's most likely some internal bug, and it would be nice to file a bug report.

AUTH_DATASRC_CLIENTS_SHUTDOWN_UNEXPECTED_ERROR Unexpected error on waiting for data source builder thread

Some exception happens while waiting for the termination of the separate thread for maintaining data source clients. This shouldn't happen in normal conditions; it should be either fatal system level errors such as severe memory shortage or some internal bug. If that happens, and if it's not in the middle of terminating b10-auth, it's probably better to stop and restart it.

AUTH_DATA_SOURCE data source database file: %1

This is a debug message produced by the authoritative server when it accesses a database data source, listing the file that is being accessed.

AUTH_DNS_SERVICES_CREATED DNS services created

This is a debug message indicating that the component that will handling incoming queries for the authoritative server (DNSServices) has been successfully created. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_HEADER_PARSE_FAIL unable to parse header in received DNS packet: %1

This is a debug message, generated by the authoritative server when an attempt to parse the header of a received DNS packet has failed. (The reason for the failure is given in the message.) The server will drop the packet.

AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified

An error was encountered when the authoritative server specified statistics data which is invalid for the auth specification file.

AUTH_LOAD_TSIG loading TSIG keys

This is a debug message indicating that the authoritative server has requested the keyring holding TSIG keys from the configuration database. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_MEM_DATASRC_DISABLED memory data source is disabled for class %1

This is a debug message reporting that the authoritative server has discovered that the memory data source is disabled for the given class.

AUTH_MEM_DATASRC_ENABLED memory data source is enabled for class %1

This is a debug message reporting that the authoritative server has discovered that the memory data source is enabled for the given class.

AUTH_MESSAGE_FORWARD_ERROR failed to forward %1 request from %2: %3

The authoritative server tried to forward some type DNS request message to a separate process (e.g., forwarding dynamic update requests to b10-ddns) to handle it, but it failed. The authoritative server returns SERVFAIL to the client on behalf of the separate process. The error could be configuration mismatch between b10-auth and the recipient component, or it may be because the requests are coming too fast and the recipient process cannot keep up with the rate, or some system level failure. In either case this means the BIND 10 system is not working as expected, so the administrator should look into the cause and address the issue. The log message includes the client's address (and port), and the error message sent from the lower layer that detects the failure.

AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY

This debug message is logged by the authoritative server when it receives a NOTIFY packet that contains zero or more than one question. (A valid NOTIFY packet contains one question.) The server will return a FORMERR error to the sender.

AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY

This debug message is logged by the authoritative server when it receives a NOTIFY packet that an RR type of something other than SOA in the question section. (The RR type received is included in the message.) The server will return a FORMERR error to the sender.

AUTH_NO_XFRIN received NOTIFY but XFRIN session is not running

This is a debug message produced by the authoritative server when it receives a NOTIFY packet but the XFRIN process is not running. The packet will be dropped and nothing returned to the sender.

AUTH_PACKET_PARSE_FAILED unable to parse received DNS packet: %1

This is a debug message, generated by the authoritative server when an attempt to parse a received DNS packet has failed due to something other than a protocol error. The reason for the failure is given in the message; the server will return a SERVFAIL error code to the sender.

AUTH_PACKET_PROTOCOL_FAILURE DNS packet protocol error: %1. Returning %2

This is a debug message, generated by the authoritative server when an attempt to parse a received DNS packet has failed due to a protocol error. The reason for the failure is given in the message, as is the error code that will be returned to the sender.

AUTH_PACKET_RECEIVED message received:\n%1

This is a debug message output by the authoritative server when it receives a valid DNS packet.

Note: This message includes the packet received, rendered in the form of multiple lines of text. For this reason, it is suggested that this log message not be routed to the syslog file, where the multiple lines could confuse programs that expect a format of one message per line.

AUTH_PROCESS_FAIL message processing failure: %1

This message is generated by the authoritative server when it has encountered an internal error whilst processing a received packet: the cause of the error is included in the message.

The server will return a SERVFAIL error code to the sender of the packet. This message indicates a potential error in the server. Please open a bug ticket for this issue.

AUTH_RECEIVED_COMMAND command '%1' received

This is a debug message issued when the authoritative server has received a command on the command channel.

AUTH_RECEIVED_NOTIFY received incoming NOTIFY for zone %1/%2 from %3

This is a debug message reporting that an incoming NOTIFY was received.

AUTH_RECEIVED_NOTIFY_NOTAUTH received bad NOTIFY for zone %1/%2 from %3

The authoritative server received a NOTIFY message, but the specified zone doesn't match any of the zones served by the server. The server doesn't process the message further, and returns a response with the Rcode being NOTAUTH. Note: RFC 1996 does not specify the server behavior in this case; responding with Rcode of NOTAUTH follows BIND 9's behavior.

AUTH_RESPONSE_FAILURE exception while building response to query: %1

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.

AUTH_RESPONSE_FAILURE_UNKNOWN unknown exception while building response to query

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.

AUTH_RESPONSE_RECEIVED received response message, ignoring

This is a debug message, this is output if the authoritative server receives a DNS packet with the QR bit set, i.e. a DNS response. The server ignores the packet as it only responds to question packets.

AUTH_SEND_ERROR_RESPONSE sending an error response (%1 bytes):\n%2

This is a debug message recording that the authoritative server is sending an error response to the originator of the query. A previous message will have recorded details of the failure.

Note: This message includes the packet sent, rendered in the form of multiple lines of text. For this reason, it is suggested that this log message not be routed to the syslog file, where the multiple lines could confuse programs that expect a format of one message per line.

AUTH_SEND_NORMAL_RESPONSE sending a normal response (%1 bytes):\n%2

This is a debug message recording that the authoritative server is sending a response to the originator of a query.

Note: This message includes the packet sent, rendered in the form of multiple lines of text. For this reason, it is suggested that this log message not be routed to the syslog file, where the multiple lines could confuse programs that expect a format of one message per line.

AUTH_SERVER_CREATED server created

An informational message indicating that the authoritative server process has been created and is initializing. The AUTH_SERVER_STARTED message will be output when initialization has successfully completed and the server starts accepting queries.

AUTH_SERVER_EXITING exiting

The authoritative server is exiting.

AUTH_SERVER_FAILED server failed: %1

The authoritative server has encountered a fatal error and is terminating. The reason for the failure is included in the message.

AUTH_SERVER_STARTED server started

Initialization of the authoritative server has completed successfully and it is entering the main loop, waiting for queries to arrive.

AUTH_SHUTDOWN asked to stop, doing so

This is a debug message indicating the server was asked to shut down and it is complying to the request.

AUTH_SQLITE3 nothing to do for loading sqlite3

This is a debug message indicating that the authoritative server has found that the data source it is loading is an SQLite3 data source, so no further validation is needed.

AUTH_START_DDNS_FORWARDER DDNS UPDATE handling started

This is a debug message indicating that b10-auth has received a message that it should internally forward UPDATE message to b10-ddns. When b10-ddns is not running, b10-auth will respond to UPDATE requests with rcode NOTIMP. When b10-ddns is running, b10-ddns will handle and respond to the UPDATE message.

AUTH_STOP_DDNS_FORWARDER DDNS UPDATE handling stopped

This is a debug message indicating that b10-auth has received a message that it should stop internally forwarding UPDATE message to b10-ddns. b10-auth will no longer forward UPDATE messages to b10-ddns, but will respond itself with error code NOTIMP. This message is also logged when the forwarding is restarted (for instance if b10-ddns is restarted and the internal connection needs to be created again), in which case it should be followed by AUTH_START_DDNS_FORWARDER.

AUTH_UNSUPPORTED_OPCODE unsupported opcode %1 received from %2

This is a debug message, produced when a received DNS packet being processed by the authoritative server has been found to contain an unsupported opcode. (The opcode and sender details are included in the message.) The server will return an error code of NOTIMPL to the sender.

AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created

This is a debug message indicating that the authoritative server has created a channel to the XFRIN (Transfer-in) process. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_XFRIN_CHANNEL_ESTABLISHED XFRIN session channel established

This is a debug message indicating that the authoritative server has established communication over the previously-created channel to the XFRIN (Transfer-in) process. It is issued during server startup is an indication that the initialization is proceeding normally.

AUTH_ZONEMGR_COMMS error communicating with zone manager: %1

This is an internal error during the processing of a NOTIFY request. An error (listed in the message) has been encountered whilst communicating with the zone manager. The NOTIFY request will not be honored. This may be some temporary failure, but is generally an unexpected event and is quite likely a bug. It's probably worth filing a report.

AUTH_ZONEMGR_ERROR received error response from zone manager: %1

The zone manager component has been informed of the request, but has returned an error response (which is included in the message). The NOTIFY request will not be honored. As of this writing, this can only happen due to a bug inside the Zonemgr implementation. Zonemgr itself may log more detailed cause of this, and these are probably worth filing a bug report.

AUTH_ZONEMGR_NOTEXIST received NOTIFY but Zonemgr does not exist

This is a debug message produced by the authoritative server when it receives a NOTIFY message but the Zonemgr component is not running at that time. Not running Zonemgr is completely valid for, e.g., primary only servers, so this is not necessarily a problem. If this message is logged even if Zonemgr is supposed to be running, it's encouraged to check other logs to identify why that happens. It may or may not be a real problem (for example, if it's immediately after the system startup, it's possible that Auth has started up and is running but Zonemgr is not yet). Even if this is indeed an unexpected case, Zonemgr should normally be restarted by the Init process, so unless this repeats too often it may be negligible in practice (still it's worth filing a bug report). In any case, the authoritative server simply drops the NOTIFY message; if it's a temporary failure or delayed startup, subsequently resent messages will eventually reach Zonemgr.

BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running

The b10-init process is starting up and will now check if the message bus daemon is already running. If so, it will not be able to start, as it needs a dedicated message bus.

BIND10_COMPONENT_FAILED component %1 (pid %2) failed: %3

The process terminated, but b10-init didn't expect it to, which means it must have failed.

BIND10_COMPONENT_RESTART component %1 is about to restart

The named component failed previously and we will try to restart it to provide as flawless service as possible, but it should be investigated what happened, as it could happen again.

BIND10_COMPONENT_SHUTDOWN_ERROR An error occured stopping component %1

An attempt to gracefully shutdown a component failed.

BIND10_COMPONENT_START component %1 is starting

The named component is about to be started by the b10-init process.

BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2

An exception (mentioned in the message) happened during the startup of the named component. The component is not considered started and further actions will be taken about it.

BIND10_COMPONENT_STOP component %1 is being stopped

A component is about to be asked to stop willingly by the b10-init.

BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed

A component failed for some reason (see previous messages). It is either a core component or needed component that was just started. In any case, the system can't continue without it and will terminate.

BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2'

A debug message. This indicates that the configurator is building a plan how to change configuration from the older one to newer one. This does no real work yet, it just does the planning what needs to be done.

BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only %1 of %2 done

There was an exception during some planned task. The plan will not continue and only some tasks of the plan were completed. The rest is aborted. The exception will be propagated.

BIND10_CONFIGURATOR_RECONFIGURE reconfiguring running components

A different configuration of which components should be running is being installed. All components that are no longer needed will be stopped and newly introduced ones started. This happens at startup, when the configuration is read the first time, or when an operator changes configuration of the b10-init.

BIND10_CONFIGURATOR_RUN running plan of %1 tasks

A debug message. The configurator is about to execute a plan of actions it computed previously.

BIND10_CONFIGURATOR_START bind10 component configurator is starting up

The part that cares about starting and stopping the right component from the b10-init process is starting up. This happens only once at the startup of the b10-init process. It will start the basic set of processes now (the ones b10-init needs to read the configuration), the rest will be started after the configuration is known.

BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down

The part that cares about starting and stopping processes in the b10-init is shutting down. All started components will be shut down now (more precisely, asked to terminate by their own, if they fail to comply, other parts of the b10-init process will try to force them).

BIND10_CONFIGURATOR_TASK performing task %1 on %2

A debug message. The configurator is about to perform one task of the plan it is currently executing on the named component.

BIND10_CONNECTING_TO_CC_FAIL failed to connect to configuration/command channel; try -v to see output from msgq

The b10-init process tried to connect to the communication channel for commands and configuration updates during initialization, but it failed. This is a fatal startup error, and process will soon terminate after some cleanup. There can be several reasons for the failure, but the most likely cause is that the msgq daemon failed to start, and the most likely cause of the msgq failure is that it doesn't have a permission to create a socket file for the communication. To confirm that, you can see debug messages from msgq by starting BIND 10 with the -v command line option. If it indicates permission problem for msgq, make sure the directory where the socket file is to be created is writable for the msgq process. Note that if you specify the -u option to change process users, the directory must be writable for that user.

BIND10_INVALID_STATISTICS_DATA invalid specification of statistics data specified

An error was encountered when the b10-init module specified statistics data which is invalid for the b10-init specification file.

BIND10_INVALID_USER invalid user: %1

The b10-init process was started with the -u option, to drop root privileges and continue running as the specified user, but the user is unknown.

BIND10_KILLING_ALL_PROCESSES killing all started processes

The b10-init module was not able to start every process it needed to start during startup, and will now kill the processes that did get started.

BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed

A connection from one of the applications which requested a socket was closed. This means the application has terminated, so all the sockets it was using are now closed and bind10 process can release them as well, unless the same sockets are used by yet another application.

BIND10_MSGQ_ALREADY_RUNNING msgq daemon already running, cannot start

There already appears to be a message bus daemon running. Either an old process was not shut down correctly, and needs to be killed, or another instance of BIND10, with the same msgq domain socket, is running, which needs to be stopped.

BIND10_MSGQ_DISAPPEARED msgq channel disappeared

While listening on the message bus channel for messages, it suddenly disappeared. The msgq daemon may have died. This might lead to an inconsistent state of the system, and BIND 10 will now shut down.

BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2

An error occurred when the bind10 process was asked to send a socket file descriptor. The error is mentioned, most common reason is that the request is invalid and may not come from bind10 process at all.

BIND10_PROCESS_ENDED process %2 of %1 ended with status %3

This indicates a process started previously terminated. The process id and component owning the process are indicated, as well as the exit code. This doesn't distinguish if the process was supposed to terminate or not.

BIND10_READING_INIT_CONFIGURATION reading b10-init configuration

The b10-init process is starting up, and will now process the initial configuration, as received from the configuration manager.

BIND10_RECEIVED_COMMAND received command: %1

The b10-init module received a command and shall now process it. The command is printed.

BIND10_RECEIVED_NEW_CONFIGURATION received new configuration: %1

The b10-init module received a configuration update and is going to apply it now. The new configuration is printed.

BIND10_RECEIVED_SIGNAL received signal %1

The b10-init module received the given signal.

BIND10_RECONFIGURE_ERROR Error applying new config: %1

A new configuration was received, but there was an error doing the re-configuration.

BIND10_RESTART_COMPONENT_SKIPPED Skipped restarting a component %1

The b10-init module tried to restart a component after it failed (crashed) unexpectedly, but the b10-init then found that the component had been removed from its local configuration of components to run. This is an unusual situation but can happen if the administrator removes the component from the configuration after the component's crash and before the restart time. The b10-init module simply skipped restarting that module, and the whole system went back to the expected state (except that the crash itself is likely to be a bug).

BIND10_RESURRECTED_PROCESS resurrected %1 (PID %2)

The given process has been restarted successfully, and is now running with the given process id.

BIND10_RESURRECTING_PROCESS resurrecting dead %1 process...

The given process has ended unexpectedly, and is now restarted.

BIND10_SELECT_ERROR error in select() call: %1

There was a fatal error in the call to select(), used to see if a child process has ended or if there is a message on the message bus. This should not happen under normal circumstances and is considered fatal, so BIND 10 will now shut down. The specific error is printed.

BIND10_SEND_SIGKILL sending SIGKILL to %1 (PID %2)

The b10-init module is sending a SIGKILL signal to the given process.

BIND10_SEND_SIGNAL_FAIL sending %1 to %2 (PID %3) failed: %4

The b10-init module sent a single (either SIGTERM or SIGKILL) to a process, but it failed due to some system level error. There are two major cases: the target process has already terminated but the b10-init module had sent the signal before it noticed the termination. In this case an error message should indicate something like "no such process". This can be safely ignored. The other case is that the b10-init module doesn't have the privilege to send a signal to the process. It can typically happen when the b10-init module started as a privileged process, spawned a subprocess, and then dropped the privilege. It includes the case for the socket creator when the b10-init process runs with the -u command line option. In this case, the b10-init module simply gives up to terminate the process explicitly because it's unlikely to succeed by keeping sending the signal. Although the socket creator is implemented so that it will terminate automatically when the b10-init process exits (and that should be the case for any other future process running with a higher privilege), but it's recommended to check if there's any remaining BIND 10 process if this message is logged. For all other cases, the b10-init module will keep sending the signal until it confirms all child processes terminate. Although unlikely, this could prevent the b10-init module from exiting, just keeping sending the signals. So, again, it's advisable to check if it really terminates when this message is logged.

BIND10_SEND_SIGTERM sending SIGTERM to %1 (PID %2)

The b10-init module is sending a SIGTERM signal to the given process.

BIND10_SETGID setting GID to %1

The b10-init switches the process group ID to the given value. This happens when BIND 10 starts with the -u option, and the group ID will be set to that of the specified user.

BIND10_SETUID setting UID to %1

The b10-init switches the user it runs as to the given UID.

BIND10_SHUTDOWN stopping the server

The b10-init process received a command or signal telling it to shut down. It will send a shutdown command to each process. The processes that do not shut down will then receive a SIGTERM signal. If that doesn't work, it shall send SIGKILL signals to the processes still alive.

BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete

All child processes have been stopped, and the b10-init process will now stop itself.

BIND10_SOCKCREATOR_BAD_CAUSE unknown error cause from socket creator: %1

The socket creator reported an error when creating a socket. But the function which failed is unknown (not one of 'S' for socket or 'B' for bind).

BIND10_SOCKCREATOR_BAD_RESPONSE unknown response for socket request: %1

The b10-init requested a socket from the creator, but the answer is unknown. This looks like a programmer error.

BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator

There should be more data from the socket creator, but it closed the socket. It probably crashed.

BIND10_SOCKCREATOR_INIT initializing socket creator parser

The b10-init module initializes routines for parsing the socket creator protocol.

BIND10_SOCKCREATOR_KILL killing the socket creator

The socket creator is being terminated the aggressive way, by sending it sigkill. This should not happen usually.

BIND10_SOCKCREATOR_TERMINATE terminating socket creator

The b10-init module sends a request to terminate to the socket creator.

BIND10_SOCKCREATOR_TRANSPORT_ERROR transport error when talking to the socket creator: %1

Either sending or receiving data from the socket creator failed with the given error. The creator probably crashed or some serious OS-level problem happened, as the communication happens only on local host.

BIND10_SOCKET_CREATED successfully created socket %1

The socket creator successfully created and sent a requested socket, it has the given file number.

BIND10_SOCKET_ERROR error on %1 call in the creator: %2/%3

The socket creator failed to create the requested socket. It failed on the indicated OS API function with given error.

BIND10_SOCKET_GET requesting socket [%1]:%2 of type %3 from the creator

The b10-init forwards a request for a socket to the socket creator.

BIND10_STARTED_CC started configuration/command session

Debug message given when BIND 10 has successfully started the object that handles configuration and commands.

BIND10_STARTED_PROCESS started %1

The given process has successfully been started.

BIND10_STARTED_PROCESS_PID started %1 (PID %2)

The given process has successfully been started, and has the given PID.

BIND10_STARTING starting BIND10: %1

Informational message on startup that shows the full version.

BIND10_STARTING_CC starting configuration/command session

Informational message given when BIND 10 is starting the session object that handles configuration and commands.

BIND10_STARTING_PROCESS starting process %1

The b10-init module is starting the given process.

BIND10_STARTING_PROCESS_PORT starting process %1 (to listen on port %2)

The b10-init module is starting the given process, which will listen on the given port number.

BIND10_STARTING_PROCESS_PORT_ADDRESS starting process %1 (to listen on %2)

The b10-init module is starting the given process, which will listen on the given address and port number (written as <address>:<port>).

BIND10_STARTUP_COMPLETE BIND 10 started

All modules have been successfully started, and BIND 10 is now running.

BIND10_STARTUP_ERROR error during startup: %1

There was a fatal error when BIND10 was trying to start. The error is shown, and BIND10 will now shut down.

BIND10_STARTUP_UNEXPECTED_MESSAGE unrecognised startup message %1

During the startup process, a number of messages are exchanged between the Init process and the processes it starts. This error is output when a message received by the Init process is recognised as being of the correct format but is unexpected. It may be that processes are starting of sequence.

BIND10_STARTUP_UNRECOGNISED_MESSAGE unrecognised startup message %1

During the startup process, a number of messages are exchanged between the Init process and the processes it starts. This error is output when a message received by the Init process is not recognised.

BIND10_STOP_PROCESS asking %1 to shut down

The b10-init module is sending a shutdown command to the given module over the message channel.

BIND10_UNKNOWN_CHILD_PROCESS_ENDED unknown child pid %1 exited

An unknown child process has exited. The PID is printed, but no further action will be taken by the b10-init process.

BIND10_WAIT_CFGMGR waiting for configuration manager process to initialize

The configuration manager process is so critical to operation of BIND 10 that after starting it, the Init module will wait for it to initialize itself before continuing. This debug message is produced during the wait and may be output zero or more times depending on how long it takes the configuration manager to start up. The total length of time Init will wait for the configuration manager before reporting an error is set with the command line --wait switch, which has a default value of ten seconds.

CACHE_ENTRY_MISSING_RRSET missing RRset to generate message for %1

The cache tried to generate the complete answer message. It knows the structure of the message, but some of the RRsets to be put there are not in cache (they probably expired already). Therefore it pretends the message was not found.

CACHE_LOCALZONE_FOUND found entry with key %1 in local zone data

Debug message, noting that the requested data was successfully found in the local zone data of the cache.

CACHE_LOCALZONE_UNKNOWN entry with key %1 not found in local zone data

Debug message. The requested data was not found in the local zone data.

CACHE_LOCALZONE_UPDATE updating local zone element at key %1

Debug message issued when there's update to the local zone section of cache.

CACHE_MESSAGES_DEINIT deinitialized message cache

Debug message. It is issued when the server deinitializes the message cache.

CACHE_MESSAGES_EXPIRED found an expired message entry for %1 in the message cache

Debug message. The requested data was found in the message cache, but it already expired. Therefore the cache removes the entry and pretends it found nothing.

CACHE_MESSAGES_FOUND found a message entry for %1 in the message cache

Debug message. We found the whole message in the cache, so it can be returned to user without any other lookups.

CACHE_MESSAGES_INIT initialized message cache for %1 messages of class %2

Debug message issued when a new message cache is issued. It lists the class of messages it can hold and the maximum size of the cache.

CACHE_MESSAGES_REMOVE removing old instance of %1/%2/%3 first

Debug message. This may follow CACHE_MESSAGES_UPDATE and indicates that, while updating, the old instance is being removed prior of inserting a new one.

CACHE_MESSAGES_UNCACHEABLE not inserting uncacheable message %1/%2/%3

Debug message, noting that the given message can not be cached. This is because there's no SOA record in the message. See RFC 2308 section 5 for more information.

CACHE_MESSAGES_UNKNOWN no entry for %1 found in the message cache

Debug message. The message cache didn't find any entry for the given key.

CACHE_MESSAGES_UPDATE updating message entry %1/%2/%3

Debug message issued when the message cache is being updated with a new message. Either the old instance is removed or, if none is found, new one is created.

CACHE_RESOLVER_DEEPEST looking up deepest NS for %1/%2

Debug message. The resolver cache is looking up the deepest known nameserver, so the resolution doesn't have to start from the root.

CACHE_RESOLVER_INIT initializing resolver cache for class %1

Debug message. The resolver cache is being created for this given class.

CACHE_RESOLVER_INIT_INFO initializing resolver cache for class %1

Debug message, the resolver cache is being created for this given class. The difference from CACHE_RESOLVER_INIT is only in different format of passed information, otherwise it does the same.

CACHE_RESOLVER_LOCAL_MSG message for %1/%2 found in local zone data

Debug message. The resolver cache found a complete message for the user query in the zone data.

CACHE_RESOLVER_LOCAL_RRSET RRset for %1/%2 found in local zone data

Debug message. The resolver cache found a requested RRset in the local zone data.

CACHE_RESOLVER_LOOKUP_MSG looking up message in resolver cache for %1/%2

Debug message. The resolver cache is trying to find a message to answer the user query.

CACHE_RESOLVER_LOOKUP_RRSET looking up RRset in resolver cache for %1/%2

Debug message. The resolver cache is trying to find an RRset (which usually originates as internally from resolver).

CACHE_RESOLVER_NO_QUESTION answer message for %1/%2 has empty question section

The cache tried to fill in found data into the response message. But it discovered the message contains no question section, which is invalid. This is likely a programmer error, please submit a bug report.

CACHE_RESOLVER_UNKNOWN_CLASS_MSG no cache for class %1

Debug message. While trying to lookup a message in the resolver cache, it was discovered there's no cache for this class at all. Therefore no message is found.

CACHE_RESOLVER_UNKNOWN_CLASS_RRSET no cache for class %1

Debug message. While trying to lookup an RRset in the resolver cache, it was discovered there's no cache for this class at all. Therefore no data is found.

CACHE_RESOLVER_UPDATE_MSG updating message for %1/%2/%3

Debug message. The resolver is updating a message in the cache.

CACHE_RESOLVER_UPDATE_RRSET updating RRset for %1/%2/%3

Debug message. The resolver is updating an RRset in the cache.

CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_MSG no cache for class %1

Debug message. While trying to insert a message into the cache, it was discovered that there's no cache for the class of message. Therefore the message will not be cached.

CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_RRSET no cache for class %1

Debug message. While trying to insert an RRset into the cache, it was discovered that there's no cache for the class of the RRset. Therefore the message will not be cached.

CACHE_RRSET_EXPIRED found expired RRset %1/%2/%3

Debug message. The requested data was found in the RRset cache. However, it is expired, so the cache removed it and is going to pretend nothing was found.

CACHE_RRSET_INIT initializing RRset cache for %1 RRsets of class %2

Debug message. The RRset cache to hold at most this many RRsets for the given class is being created.

CACHE_RRSET_LOOKUP looking up %1/%2/%3 in RRset cache

Debug message. The resolver is trying to look up data in the RRset cache.

CACHE_RRSET_NOT_FOUND no RRset found for %1/%2/%3 in cache

Debug message which can follow CACHE_RRSET_LOOKUP. This means the data is not in the cache.

CACHE_RRSET_REMOVE_OLD removing old RRset for %1/%2/%3 to make space for new one

Debug message which can follow CACHE_RRSET_UPDATE. During the update, the cache removed an old instance of the RRset to replace it with the new one.

CACHE_RRSET_UNTRUSTED not replacing old RRset for %1/%2/%3, it has higher trust level

Debug message which can follow CACHE_RRSET_UPDATE. The cache already holds the same RRset, but from more trusted source, so the old one is kept and new one ignored.

CACHE_RRSET_UPDATE updating RRset %1/%2/%3 in the cache

Debug message. The RRset is updating its data with this given RRset.

CC_ASYNC_READ_FAILED asynchronous read failed (error code = %1)

This marks a low level error, we tried to read data from the message queue daemon asynchronously, but the ASIO library returned an error.

CC_CONN_ERROR error connecting to message queue (%1)

It is impossible to reach the message queue daemon for the reason given. It is unlikely there'll be reason for whatever program this currently is to continue running, as the communication with the rest of BIND 10 is vital for the components.

CC_DISCONNECT disconnecting from message queue daemon

The library is disconnecting from the message queue daemon. This debug message indicates that the program is trying to shut down gracefully.

CC_ESTABLISH trying to establish connection with message queue daemon at %1

This debug message indicates that the command channel library is about to connect to the message queue daemon, which should be listening on the UNIX-domain socket listed in the output.

CC_ESTABLISHED successfully connected to message queue daemon

This debug message indicates that the connection was successfully made, this should follow CC_ESTABLISH.

CC_GROUP_RECEIVE trying to receive a message with seq %1

Debug message, noting that a message is expected to come over the command channel.

CC_GROUP_RECEIVED message arrived ('%1', '%2')

Debug message, noting that we successfully received a message (its envelope and payload listed). This follows CC_GROUP_RECEIVE, but might happen some time later, depending if we waited for it or just polled.

CC_GROUP_SEND sending message '%1' to group '%2'

Debug message, we're about to send a message over the command channel.

CC_INVALID_LENGTHS invalid length parameters (%1, %2)

This happens when garbage comes over the command channel or some kind of confusion happens in the program. The data received from the socket make no sense if we interpret it as lengths of message. The first one is total length of the message; the second is the length of the header. The header and its length (2 bytes) is counted in the total length.

CC_LENGTH_NOT_READY length not ready

There should be data representing the length of message on the socket, but it is not there.

CC_LNAME_RECEIVED received local name: %1

Debug message: the local module received its unique identifier (name) from msgq on completion of establishing the session with msgq.

CC_NO_MESSAGE no message ready to be received yet

The program polled for incoming messages, but there was no message waiting. This is a debug message which may happen only after CC_GROUP_RECEIVE.

CC_NO_MSGQ unable to connect to message queue (%1)

It isn't possible to connect to the message queue daemon, for reason listed. It is unlikely any program will be able continue without the communication.

CC_READ_ERROR error reading data from command channel (%1)

A low level error happened when the library tried to read data from the command channel socket. The reason is listed.

CC_READ_EXCEPTION error reading data from command channel (%1)

We received an exception while trying to read data from the command channel socket. The reason is listed.

CC_REPLY replying to message from '%1' with '%2'

Debug message, noting we're sending a response to the original message with the given envelope.

CC_SET_TIMEOUT setting timeout to %1ms

Debug message. A timeout for which the program is willing to wait for a reply is being set.

CC_START_READ starting asynchronous read

Debug message. From now on, when a message (or command) comes, it'll wake the program and the library will automatically pass it over to correct place.

CC_SUBSCRIBE subscribing to communication group %1

Debug message. The program wants to receive messages addressed to this group.

CC_TIMEOUT timeout reading data from command channel

The program waited too long for data from the command channel (usually when it sent a query to different program and it didn't answer for whatever reason).

CC_UNSUBSCRIBE unsubscribing from communication group %1

Debug message. The program no longer wants to receive messages addressed to this group.

CC_WRITE_ERROR error writing data to command channel (%1)

A low level error happened when the library tried to write data to the command channel socket.

CC_ZERO_LENGTH invalid message length (0)

The library received a message length being zero, which makes no sense, since all messages must contain at least the envelope.

CFGMGR_AUTOMATIC_CONFIG_DATABASE_UPDATE Updating configuration database from version %1 to %2

An older version of the configuration database has been found, from which there was an automatic upgrade path to the current version. These changes are now applied, and no action from the administrator is necessary.

CFGMGR_BACKED_UP_CONFIG_FILE Config file %1 was removed; a backup was made at %2

BIND 10 has been started with the command to clear the configuration file. The existing file has been backed up (moved) to the given file name. A new configuration file will be created in the original location when necessary.

CFGMGR_BAD_UPDATE_RESPONSE_FROM_MODULE Unable to parse response from module %1: %2

The configuration manager sent a configuration update to a module, but the module responded with an answer that could not be parsed. The answer message appears to be invalid JSON data, or not decodable to a string. This is likely to be a problem in the module in question. The update is assumed to have failed, and will not be stored.

CFGMGR_CC_SESSION_ERROR Error connecting to command channel: %1

The configuration manager daemon was unable to connect to the messaging system. The most likely cause is that msgq is not running.

CFGMGR_CONFIG_FILE Configuration manager starting with configuration file: %1

The configuration manager is starting, reading and saving the configuration settings to the shown file.

CFGMGR_CONFIG_UPDATE_BOSS_AND_INIT_FOUND Configuration found for both 'Boss' and 'Init', ignoring 'Boss'

In the process of updating the configuration from version 2 to version 3, the configuration manager has found that there are existing configurations for both the old value 'Boss' and the new value 'Init'. This should in theory not happen, as in older versions 'Init' does not exist, and in newer versions 'Boss' does not exist. The configuration manager will continue with the update process, leaving the values for both as they are, so as not to overwrite any settings. However, the values for 'Boss' are ignored by BIND 10, and it is probably wise to check the configuration file manually.

CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1

There was a problem reading the persistent configuration data as stored on disk. The file may be corrupted, or it is of a version from where there is no automatic upgrade path. The file needs to be repaired or removed. The configuration manager daemon will now shut down.

CFGMGR_IOERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1

There was an IO error from the system while the configuration manager was trying to write the configuration database to disk. The specific error is given. The most likely cause is that the directory where the file is stored does not exist, or is not writable. The updated configuration is not stored.

CFGMGR_OSERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1

There was an OS error from the system while the configuration manager was trying to write the configuration database to disk. The specific error is given. The most likely cause is that the system does not have write access to the configuration database file. The updated configuration is not stored.

CFGMGR_STOPPED_BY_COMMAND received shutdown command, shutting down

The configuration manager received a shutdown command, and is exiting.

CFGMGR_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the cfgmgr daemon. The daemon will now shut down.

CMDCTL_BAD_CONFIG_DATA error in config data: %1

There was an error reading the updated configuration data. The specific error is printed.

CMDCTL_BAD_PASSWORD bad password for user: %1

A login attempt was made to b10-cmdctl, but the password was wrong. Users can be managed with the tool b10-cmdctl-usermgr.

CMDCTL_CC_SESSION_ERROR error reading from cc channel: %1

There was a problem reading from the command and control channel. The most likely cause is that the message bus daemon is not running.

CMDCTL_CC_SESSION_TIMEOUT timeout on cc channel

A timeout occurred when waiting for essential data from the cc session. This usually occurs when b10-cfgmgr is not running or not responding. Since we are waiting for essential information, this is a fatal error, and the cmdctl daemon will now shut down.

CMDCTL_COMMAND_ERROR error in command %1 to module %2: %3

An error was encountered sending the given command to the given module. Either there was a communication problem with the module, or the module was not able to process the command, and sent back an error. The specific error is printed in the message.

CMDCTL_COMMAND_SENT command '%1' to module '%2' was sent

This debug message indicates that the given command has been sent to the given module.

CMDCTL_EXITING exiting

The b10-cmdctl daemon is exiting.

CMDCTL_NO_SUCH_USER username not found in user database: %1

A login attempt was made to b10-cmdctl, but the username was not known. Users can be added with the tool b10-cmdctl-usermgr.

CMDCTL_NO_USER_ENTRIES_READ failed to read user information, all users will be denied

The b10-cmdctl daemon was unable to find any user data in the user database file. Either it was unable to read the file (in which case this message follows a message CMDCTL_USER_DATABASE_READ_ERROR containing a specific error), or the file was empty. Users can be added with the tool b10-cmdctl-usermgr.

CMDCTL_SEND_COMMAND sending command %1 to module %2

This debug message indicates that the given command is being sent to the given module.

CMDCTL_SSL_SETUP_FAILURE_READING_CERT failed to read certificate or key: %1

The b10-cmdctl daemon is unable to read either the certificate file or the private key file, and is therefore unable to accept any SSL connections. The specific error is printed in the message. The administrator should solve the issue with the files, or recreate them with the b10-certgen tool.

CMDCTL_SSL_SETUP_FAILURE_USER_DENIED failed to create an SSL connection (user denied): %1

The user was denied because the SSL connection could not successfully be set up. The specific error is given in the log message. Possible causes may be that the ssl request itself was bad, or the local key or certificate file could not be read.

CMDCTL_STARTED cmdctl is listening for connections on %1:%2

The cmdctl daemon has started and is now listening for connections.

CMDCTL_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the cmdctl daemon. The daemon will now shut down.

CMDCTL_UNCAUGHT_EXCEPTION uncaught exception: %1

The b10-cmdctl daemon encountered an uncaught exception and will now shut down. This is indicative of a programming error and should not happen under normal circumstances. The exception message is printed.

CMDCTL_USER_DATABASE_READ_ERROR failed to read user database file %1: %2

The b10-cmdctl daemon was unable to read the user database file. The file may be unreadable for the daemon, or it may be corrupted. In the latter case, it can be recreated with b10-cmdctl-usermgr. The specific error is printed in the log message.

CONFIG_CCSESSION_MSG error in CC session message: %1

There was a problem with an incoming message on the command and control channel. The message does not appear to be a valid command, and is missing a required element or contains an unknown data format. This most likely means that another BIND10 module is sending a bad message. The message itself is ignored by this module.

CONFIG_CCSESSION_MSG_INTERNAL error handling CC session message: %1

There was an internal problem handling an incoming message on the command and control channel. An unexpected exception was thrown, details of which are appended to the message. The module will continue to run, but will not send back an answer.

The most likely cause of this error is a programming error. Please raise a bug report.

CONFIG_CCSESSION_STOPPING error sending stopping message: %1

There was a problem when sending a message signaling that the module using this CCSession is stopping. This message is sent so that the rest of the system is aware that the module is no longer running. Apart from logging this message, the error itself is ignored, and the ModuleCCSession is still stopped. The specific exception message is printed.

CONFIG_CCSESSION_STOPPING_UNKNOWN unknown error sending stopping message

Similar to CONFIG_CCSESSION_STOPPING, but in this case the exception that is seen is not a standard exception, and further information is unknown. This is a bug.

CONFIG_GET_FAIL error getting configuration from cfgmgr: %1

The configuration manager returned an error when this module requested the configuration. The full error message answer from the configuration manager is appended to the log error. The most likely cause is that the module is of a different (command specification) version than the running configuration manager.

CONFIG_GET_FAILED error getting configuration from cfgmgr: %1

The configuration manager returned an error response when the module requested its configuration. The full error message answer from the configuration manager is appended to the log error.

CONFIG_JSON_PARSE JSON parse error in %1: %2

There was an error parsing the JSON file. The given file does not appear to be in valid JSON format. Please verify that the filename is correct and that the contents are valid JSON.

CONFIG_LOG_CONFIG_ERRORS error(s) in logging configuration: %1

There was a logging configuration update, but the internal validator for logging configuration found that it contained errors. The errors are shown, and the update is ignored.

CONFIG_LOG_EXPLICIT will use logging configuration for explicitly-named logger %1

This is a debug message. When processing the "loggers" part of the configuration file, the configuration library found an entry for the named logger that matches the logger specification for the program. The logging configuration for the program will be updated with the information.

CONFIG_LOG_IGNORE_EXPLICIT ignoring logging configuration for explicitly-named logger %1

This is a debug message. When processing the "loggers" part of the configuration file, the configuration library found an entry for the named logger. As this does not match the logger specification for the program, it has been ignored.

CONFIG_LOG_IGNORE_WILD ignoring logging configuration for wildcard logger %1

This is a debug message. When processing the "loggers" part of the configuration file, the configuration library found the named wildcard entry (one containing the "*" character) that matched a logger already matched by an explicitly named entry. The configuration is ignored.

CONFIG_LOG_WILD_MATCH will use logging configuration for wildcard logger %1

This is a debug message. When processing the "loggers" part of the configuration file, the configuration library found the named wildcard entry (one containing the "*" character) that matches a logger specification in the program. The logging configuration for the program will be updated with the information.

CONFIG_MOD_SPEC_FORMAT module specification error in %1: %2

The given file does not appear to be a valid specification file: details are included in the message. Please verify that the filename is correct and that its contents are a valid BIND10 module specification.

CONFIG_MOD_SPEC_REJECT module specification rejected by cfgmgr: %1

The specification file for this module was rejected by the configuration manager. The full error message answer from the configuration manager is appended to the log error. The most likely cause is that the module is of a different (specification file) version than the running configuration manager.

CONFIG_OPEN_FAIL error opening %1: %2

There was an error opening the given file. The reason for the failure is included in the message.

CONFIG_RPC_SEQ RPC call %1 to %2 with seq %3

Debug message, saying there's a RPC call of given command to given module. It has internal sequence number as listed in the message.

CONFIG_SESSION_STOPPING_FAILED error sending stopping message: %1

There was a problem when sending a message signaling that the module using this CCSession is stopping. This message is sent so that the rest of the system is aware that the module is no longer running. Apart from logging this message, the error itself is ignored, and the ModuleCCSession is still stopped. The specific exception message is printed.

DATASRC_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'

The software refuses to load NSEC3 records into a wildcard domain or the owner name has two or more labels below the zone origin. It isn't explicitly forbidden, but no sane zone wouldn have such names for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is compatible with BIND 9.

DATASRC_CACHE_CREATE creating the hotspot cache

This is a debug message issued during startup when the hotspot cache is created.

DATASRC_CACHE_DESTROY destroying the hotspot cache

Debug information. The hotspot cache is being destroyed.

DATASRC_CACHE_DISABLE disabling the hotspot cache

A debug message issued when the hotspot cache is disabled.

DATASRC_CACHE_ENABLE enabling the hotspot cache

A debug message issued when the hotspot cache is enabled.

DATASRC_CACHE_EXPIRED item '%1' in the hotspot cache has expired

A debug message issued when a hotspot cache lookup located the item but it had expired. The item was removed and the program proceeded as if the item had not been found.

DATASRC_CACHE_FOUND the item '%1' was found

Debug information. An item was successfully located in the hotspot cache.

DATASRC_CACHE_FULL hotspot cache is full, dropping oldest

Debug information. After inserting an item into the hotspot cache, the maximum number of items was exceeded, so the least recently used item will be dropped. This should be directly followed by CACHE_REMOVE.

DATASRC_CACHE_INSERT inserting item '%1' into the hotspot cache

A debug message indicating that a new item is being inserted into the hotspot cache.

DATASRC_CACHE_NOT_FOUND the item '%1' was not found in the hotspot cache

A debug message issued when hotspot cache was searched for the specified item but it was not found.

DATASRC_CACHE_OLD_FOUND older instance of hotspot cache item '%1' found, replacing

Debug information. While inserting an item into the hotspot cache, an older instance of an item with the same name was found; the old instance will be removed. This will be directly followed by CACHE_REMOVE.

DATASRC_CACHE_REMOVE removing '%1' from the hotspot cache

Debug information. An item is being removed from the hotspot cache.

DATASRC_CACHE_SLOTS setting the hotspot cache size to '%1', dropping '%2' items

The maximum allowed number of items of the hotspot cache is set to the given number. If there are too many, some of them will be dropped. The size of 0 means no limit.

DATASRC_CACHE_ZONE_NOTFOUND Zone %1/%2 not found on data source '%3' to cache

During data source configuration, a zone is to be loaded (cached) in to memory from the underlying data source, but the zone is not found in the data source. This particular zone was not loaded, but data source configuration continues, possibly loading other zones into memory. This is basically some kind of configuration or operation error: either the name is incorrect in the configuration, or the zone has been removed from the data source without updating the configuration.

DATASRC_CHECK_ERROR post-load check of zone %1/%2 failed: %3

The zone was loaded into the data source successfully, but the content fails basic sanity checks. See the message if you want to know what exactly is wrong with the data. The data can not be used and previous version, if any, will be preserved.

DATASRC_CHECK_WARNING %1/%2: %3

The zone was loaded into the data source successfully, but there's some problem with the content. The problem does not stop the new version from being used (though there may be other problems that do, see DATASRC_CHECK_ERROR), but it should still be checked and fixed. See the message to know what exactly is wrong with the data.

DATASRC_DATABASE_ADDDIFF updated diff table for add: %1 %2 %3

Debug message. A difference record for adding a record to the zone is being appended to the difference table. The name, type and rdata of the record is logged.

DATASRC_DATABASE_ADDNSEC3 added NSEC3 RR: %1 %2

Debug message. A new NSEC3 record is added to the table. The hash and the rdata is logged.

DATASRC_DATABASE_ADDRR added RR: %1 %2 %3

Debug message. A new resource record is added to the table. The name, type and rdata is logged.

DATASRC_DATABASE_COVER_NSEC_UNSUPPORTED %1 doesn't support DNSSEC when asked for NSEC data covering %2

The datasource tried to provide an NSEC proof that the named domain does not exist, but the database backend doesn't support DNSSEC. No proof is included in the answer as a result.

DATASRC_DATABASE_DELETEDIFF updated diff table for delete: %1 %2 %3

Debug message. A difference record for removing a record from the zone is being appended to the difference table. The name, type and rdata of the record is logged.

DATASRC_DATABASE_DELETENSEC3 deleted NSEC3 RR: %1 %2

Debug message. An NSEC3 record is removed from the table. The name, type and rdata is logged.

DATASRC_DATABASE_DELETERR deleted RR: %1 %2 %3

Debug message. A resource record is removed from the table. The name, type and rdata is logged.

DATASRC_DATABASE_FINDNSEC3 Looking for NSEC3 for %1 in %2 mode

Debug information. A search in an database data source for NSEC3 that matches or covers the given name is being started.

DATASRC_DATABASE_FINDNSEC3_COVER found a covering NSEC3 for %1 at label count %2: %3

Debug information. An NSEC3 that covers the given name is found and being returned. The found NSEC3 RRset is also displayed. When the shown label count is smaller than that of the given name, the matching NSEC3 is for a superdomain of the given name (see DATASRC_DATABSE_FINDNSEC3_TRYHASH). The found NSEC3 RRset is also displayed.

DATASRC_DATABASE_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3

Debug information. An NSEC3 that matches (a possibly superdomain of) the given name is found and being returned. When the shown label count is smaller than that of the given name, the matching NSEC3 is for a superdomain of the given name (see DATASRC_DATABSE_FINDNSEC3_TRYHASH). The found NSEC3 RRset is also displayed.

DATASRC_DATABASE_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3)

Debug information. In an attempt of finding an NSEC3 for the give name, (a possibly superdomain of) the name is hashed and searched for in the NSEC3 name space. When the shown label count is smaller than that of the shown name, the search tries the superdomain name that share the shown (higher) label count of the shown name (e.g., for www.example.com. with shown label count of 3, example.com. is being tried, as "." is 1 label long).

DATASRC_DATABASE_FINDNSEC3_TRYHASH_PREV looking for previous NSEC3 for %1 at label count %2 (hash %3)

Debug information. An exact match on hash (see DATASRC_DATABASE_FINDNSEC3_TRYHASH) was unsuccessful. We get the previous hash to that one instead.

DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4

Debug information. The database data source is looking up records with the given name and type in the database.

DATASRC_DATABASE_FIND_TTL_MISMATCH TTL values differ in %1 for elements of %2/%3/%4, setting to %5

The datasource backend provided resource records for the given RRset with 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_ANY search in datasource %1 resulted in returning all records of %2

The data returned by the database backend contained data for the given domain name, so all the RRsets of the domain are returned.

DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5

When searching the domain for a name a CNAME was found at that name. Even though it was not the RR type being sought, it is returned. (The caller may want to continue the lookup by replacing the query name with the canonical name and restarting the query with the original RR type.)

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.

DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5

The program found the domain requested, but it is a delegation point to a different zone, therefore it is not authoritative for this domain name. It will return the NS record instead.

DATASRC_DATABASE_FOUND_DNAME Found DNAME at %2 in %1

When searching for a domain, the program met a DNAME redirection to a different place in the domain space at the given domain name. It will return that one instead.

DATASRC_DATABASE_FOUND_EMPTY_NONTERMINAL empty non-terminal %2 in %1

The domain name does not have any RRs associated with it, so it doesn't exist in the database. However, it has a subdomain, so it does exist in the DNS address space. This type of domain is known as an "empty non-terminal" and so we return NXRRSET instead of NXDOMAIN.

DATASRC_DATABASE_FOUND_NXDOMAIN search in datasource %1 resulted in NXDOMAIN for %2/%3/%4

The data returned by the database backend did not contain any data for the given domain name, class and type.

DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET

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

A search in the database for RRs for the specified name, type and class has located RRs that match the name and class but not the type. DNSSEC information has been requested and returned.

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_ITERATE iterating zone %1

The program is reading the whole zone, eg. not searching for data, but going through each of the RRsets there.

DATASRC_DATABASE_ITERATE_END iterating zone finished

While iterating through the zone, the program reached end of the data.

DATASRC_DATABASE_ITERATE_NEXT next RRset in zone is %1/%2

While iterating through the zone, the program extracted next RRset from it. The name and RRtype of the RRset is indicated in the message.

DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4

While iterating through the zone, the time to live for RRs of the given RRset were found to be different. Since an RRset cannot have multiple TTLs, we set it to the lowest value we found (but we don't modify the database). This is what the client would do when such RRs were given in a DNS response according to RFC2181. The data in database should be checked and fixed.

DATASRC_DATABASE_JOURNALREADER_BADDATA failed to convert a diff to RRset in %1/%2 on %3 between %4 and %5: %6

This is an error message indicating that a zone's diff is broken and the data source library failed to convert it to a valid RRset. The most likely cause of this is that someone has manually modified the zone's diff in the database and inserted invalid data as a result. The zone's name and class, database name, and the start and end serials, and an additional detail of the error are shown in the message. The administrator should examine the diff in the database to find any invalid data and fix it.

DATASRC_DATABASE_JOURNALREADER_END %1/%2 on %3 from %4 to %5

This is a debug message indicating that the program (successfully) reaches the end of sequences of a zone's differences. The zone's name and class, database name, and the start and end serials are shown in the message.

DATASRC_DATABASE_JOURNALREADER_NEXT %1/%2 in %3/%4 on %5

This is a debug message indicating that the program retrieves one difference in difference sequences of a zone and successfully converts it to an RRset. The zone's name and class, database name, and the name and RR type of the retrieved diff are shown in the message.

DATASRC_DATABASE_JOURNALREADER_START %1/%2 on %3 from %4 to %5

This is a debug message indicating that the program starts reading a zone's difference sequences from a database-based data source. The zone's name and class, database name, and the start and end serials are shown in the message.

DATASRC_DATABASE_NO_MATCH not match for %2/%3/%4 in %1

No match (not even a wildcard) was found in the named data source for the given name/type/class in the data source.

DATASRC_DATABASE_TRANSACTION_ROLLBACKFAIL failed to roll back transaction on %1: %2

A transaction on the database was rolled back without committing the changes to the database, but the rollback itself 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.

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_ANY search in datasource %1 resulted in wildcard match type ANY on %2

The database doesn't contain directly matching name. When searching for a wildcard match, a wildcard record matching the name of the query containing some RRsets was found. All the RRsets of the node are returned.

DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1)

The database was queried to provide glue data and it didn't find direct match. It could create it from given wildcard, but matching wildcards is forbidden under a zone cut, which was found. Therefore the delegation will be returned instead.

DATASRC_DATABASE_WILDCARD_CANCEL_SUB wildcard %2 can't be used to construct %3 because %4 exists in %1

The answer could be constructed using the wildcard, but the given subdomain exists, therefore this name is something like empty non-terminal (actually, from the protocol point of view, it is empty non-terminal, but the code discovers it differently).

DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6

The database doesn't contain directly matching name. When searching for a wildcard match, a CNAME RR was found at a wildcard record matching the name. This is returned as the result of the search.

DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1

The given wildcard matches the name being sough but it as an empty nonterminal (e.g. there's nothing at *.example.com but something like subdomain.*.example.org, do exist: so *.example.org exists in the namespace but has no RRs associated with it). This will produce NXRRSET.

DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %2 with RRset %3

The database doesn't contain directly matching name. When searching for a wildcard match, a wildcard record matching the name and type of the query was found. The data at this point is returned.

DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6

The database doesn't contain directly matching name. When searching for a wildcard match, an NS RR was found at a wildcard record matching the name. This is returned as the result of the search.

DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5

The database doesn't contain directly matching name. When searching for a wildcard match, a matching wildcard entry was found but it did not contain RRs the requested type. AN NXRRSET indication is returned.

DATASRC_DO_QUERY handling query for '%1/%2'

A debug message indicating that a query for the given name and RR type is being processed.

DATASRC_LIBRARY_ERROR failure loading %1 datasource library for class %2: %3

There was a problem loading the dynamic library for a data source. This backend is hence not available, and any data sources that use this backend will not be available.

DATASRC_LIST_CACHE_PENDING in-memory cache for data source '%1' is not yet writable, pending load

While (re)configuring data source clients, zone data of the shown data source cannot be loaded to in-memory cache at that point because the cache is not yet ready for writing. This can happen for shared-memory type of cache, in which case the cache will be reset later, either by a higher level application or by a command from other module.

DATASRC_LIST_NOT_CACHED zones in data source %1 for class %2 not cached, cache disabled globally. Will not be available.

The process disabled caching of RR data completely. However, this data source is provided from a master file and it can be served from memory cache only. Therefore, the entire data source will not be available for this process. If this is a problem, you should configure the zones of that data source to some database backend (sqlite3, for example) and use it from there.

DATASRC_LOAD_ZONE_ERROR Error loading zone %1/%2 on data source '%3': %4

During data source configuration, an error was found in the zone data when it was being loaded in to memory on the shown data source. This particular zone was not loaded, but data source configuration continues, possibly loading other zones into memory. Subsequent lookups will treat this zone as broken. The specific error is shown in the message, and should be addressed.

DATASRC_MASTER_LOAD_ERROR %1:%2: Zone '%3/%4' contains error: %5

There's an error in the given master file. The zone won't be loaded for this reason. Parsing might follow, so you might get further errors and warnings to fix everything at once. But in case the error is serious enough, the parser might just give up or get confused and generate false errors afterwards.

DATASRC_MASTER_LOAD_WARN %1:%2: Zone '%3/%4' has a potential problem: %5

There's something suspicious in the master file. This is a warning only. It may be a problem or it may be harmless, but it should be checked. This problem does not stop the zone from being loaded.

DATASRC_MEMORY_ANY_SUCCESS ANY query for '%1' successful

Debug information. The domain was found and an ANY type query is being answered by providing everything found inside the domain.

DATASRC_MEMORY_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'

The software refuses to load NSEC3 records into a wildcard domain or the owner name has two or more labels below the zone origin. It isn't explicitly forbidden, but no sane zone wouldn have such names for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is compatible with BIND 9.

DATASRC_MEMORY_CHECK_ERROR post-load check of zone %1/%2 failed: %3

The zone was loaded into the data source successfully, but the content fails basic sanity checks. See the message if you want to know what exactly is wrong with the data. The data can not be used and previous version, if any, will be preserved.

DATASRC_MEMORY_CHECK_WARNING %1/%2: %3

The zone was loaded into the data source successfully, but there's some problem with the content. The problem does not stop the new version from being used (though there may be other problems that do, see DATASRC_MEMORY_CHECK_ERROR), but it should still be checked and fixed. See the message to know what exactly is wrong with the data.

DATASRC_MEMORY_CNAME CNAME at the domain '%1'

Debug information. The requested domain is an alias to a different domain, returning the CNAME instead.

DATASRC_MEMORY_DELEG_FOUND delegation found at '%1'

Debug information. A delegation point was found above the requested record.

DATASRC_MEMORY_DNAME_ENCOUNTERED encountered a DNAME

Debug information. While searching for the requested domain, a DNAME was encountered on the way. This may lead to redirection to a different domain and stop the search.

DATASRC_MEMORY_DNAME_FOUND DNAME found at '%1'

Debug information. A DNAME was found instead of the requested information.

DATASRC_MEMORY_DOMAIN_EMPTY requested domain '%1' is empty

Debug information. The requested domain exists in the tree of domains, but it is empty. Therefore it doesn't contain the requested resource type.

DATASRC_MEMORY_EXACT_DELEGATION delegation at the exact domain '%1'

Debug information. There's a NS record at the requested domain. This means this zone is not authoritative for the requested domain, but a delegation should be followed. The requested domain is an apex of some zone.

DATASRC_MEMORY_FINDNSEC3 finding NSEC3 for %1, mode %2

Debug information. A search in an in-memory data source for NSEC3 that matches or covers the given name is being started.

DATASRC_MEMORY_FINDNSEC3_COVER found a covering NSEC3 for %1: %2

Debug information. An NSEC3 that covers the given name is found and being returned. The found NSEC3 RRset is also displayed.

DATASRC_MEMORY_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3

Debug information. An NSEC3 that matches (a possibly superdomain of) the given name is found and being returned. When the shown label count is smaller than that of the given name, the matching NSEC3 is for a superdomain of the given name (see DATASRC_MEMORY_FINDNSEC3_TRYHASH). The found NSEC3 RRset is also displayed.

DATASRC_MEMORY_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3)

Debug information. In an attempt of finding an NSEC3 for the give name, (a possibly superdomain of) the name is hashed and searched for in the NSEC3 name space. When the shown label count is smaller than that of the shown name, the search tries the superdomain name that share the shown (higher) label count of the shown name (e.g., for www.example.com. with shown label count of 3, example.com. is being tried).

DATASRC_MEMORY_FIND_TYPE_AT_ORIGIN origin query for type %1 in in-memory zone %2/%3 successful

Debug information. A specific type RRset is requested at a zone origin of an in-memory zone and it is found.

DATASRC_MEMORY_MEM_ADD_EMPTY_ZONE adding an empty zone '%1/%2'

Debug information. An "empty" zone is being added into the in-memory data source. This is conceptual data indicating the state where the zone exists but its content isn't available. That would be the case, for example, a broken zone specified in the configuration.

DATASRC_MEMORY_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'

Debug information. An RRset is being added to the in-memory data source.

DATASRC_MEMORY_MEM_ADD_WILDCARD adding wildcards for '%1'

This is a debug message issued during the processing of a wildcard name. The internal domain name tree is scanned and some nodes are specially marked to allow the wildcard lookup to succeed.

DATASRC_MEMORY_MEM_ADD_ZONE adding zone '%1/%2'

Debug information. A zone is being added into the in-memory data source.

DATASRC_MEMORY_MEM_CNAME_COEXIST can't add data to CNAME in domain '%1'

This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the other way around -- adding some other data to CNAME.

DATASRC_MEMORY_MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1'

Someone or something tried to add a CNAME into a domain that already contains some other data. But the protocol forbids coexistence of CNAME with anything (RFC 1034, section 3.6.2). This indicates a problem with provided data.

DATASRC_MEMORY_MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1'

A request was made for DNAME and NS records to be put into the same domain which is not the apex (the top of the zone). This is forbidden by RFC 2672 (section 3) and indicates a problem with provided data.

DATASRC_MEMORY_MEM_DUP_RRSET duplicate RRset '%1/%2'

An RRset is being inserted into in-memory data source for a second time. The original version must be removed first. Note that loading master files where an RRset is split into multiple locations is not supported yet.

DATASRC_MEMORY_MEM_FIND_ZONE looking for zone '%1'

Debug information. A zone object for this zone is being searched for in the in-memory data source.

DATASRC_MEMORY_MEM_LOAD_FROM_DATASRC loading zone '%1/%2' from other data source

Debug information. The content of another data source is being loaded into the memory.

DATASRC_MEMORY_MEM_LOAD_FROM_FILE loading zone '%1/%2' from file '%3'

Debug information. The content of master file is being loaded into the memory.

DATASRC_MEMORY_MEM_NO_NSEC3PARAM NSEC3PARAM is missing for NSEC3-signed zone %1/%2

The in-memory data source has loaded a zone signed with NSEC3 RRs, but it doesn't have a NSEC3PARAM RR at the zone origin. It's likely that the zone is somehow broken, but this RR is not necessarily needed for handling lookups with NSEC3 in this data source, so it accepts the given content of the zone. Nevertheless the administrator should look into the integrity of the zone data.

DATASRC_MEMORY_MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2'

It was attempted to add the domain into a zone that shouldn't have it (eg. the domain is not subdomain of the zone origin). This indicates a problem with provided data.

DATASRC_MEMORY_MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2'

Some resource types are singletons -- only one is allowed in a domain (for example CNAME or SOA). This indicates a problem with provided data.

DATASRC_MEMORY_MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1'

The software refuses to load DNAME records into a wildcard domain. It isn't explicitly forbidden, but the protocol is ambiguous about how this should behave and BIND 9 refuses that as well. Please describe your intention using different tools.

DATASRC_MEMORY_MEM_WILDCARD_NS NS record in wildcard domain '%1'

The software refuses to load NS records into a wildcard domain. It isn't explicitly forbidden, but the protocol is ambiguous about how this should behave and BIND 9 refuses that as well. Please describe your intention using different tools.

DATASRC_MEMORY_NOT_FOUND requested domain '%1' not found

Debug information. The requested domain does not exist.

DATASRC_MEMORY_NS_ENCOUNTERED encountered a NS

Debug information. While searching for the requested domain, a NS was encountered on the way (a delegation). This may lead to stop of the search.

DATASRC_MEMORY_SUCCESS query for '%1/%2' successful

Debug information. The requested record was found.

DATASRC_MEMORY_SUPER_STOP stopped as '%1' is superdomain of a zone node, meaning it's empty

Debug information. The search stopped because the requested domain was detected to be a superdomain of some existing node of zone (while there was no exact match). This means that the domain is an empty nonterminal, therefore it is treated as NXRRSET case (eg. the domain exists, but it doesn't have the requested record type).

DATASRC_MEMORY_WILDCARD_CANCEL wildcard match canceled for '%1'

Debug information. A domain above wildcard was reached, but there's something below the requested domain. Therefore the wildcard doesn't apply here. This behaviour is specified by RFC 1034, section 4.3.3.

DATASRC_META_ADD adding a data source into meta data source

This is a debug message issued during startup or reconfiguration. Another data source is being added into the meta data source.

DATASRC_META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2'

It was attempted to add a data source into a meta data source, but their classes do not match.

DATASRC_META_REMOVE removing data source from meta data source

Debug information. A data source is being removed from meta data source.

DATASRC_QUERY_ADD_NSEC adding NSEC record for '%1'

Debug information. A NSEC record covering this zone is being added.

DATASRC_QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1'

Debug information. A NSEC3 record for the given zone is being added to the response message.

DATASRC_QUERY_ADD_RRSET adding RRset '%1/%2' to message

Debug information. An RRset is being added to the response message.

DATASRC_QUERY_ADD_SOA adding SOA of '%1'

Debug information. A SOA record of the given zone is being added to the authority section of the response message.

DATASRC_QUERY_AUTH_FAIL the underlying data source failed with %1

The underlying data source failed to answer the authoritative query. 1 means some error, 2 is not implemented. The data source should have logged the specific error already.

DATASRC_QUERY_BAD_REFERRAL bad referral to '%1'

The domain lives in another zone. But it is not possible to generate referral information for it.

DATASRC_QUERY_CACHED data for %1/%2 found in hotspot cache

Debug information. The requested data were found in the hotspot cache, so no query is sent to the real data source.

DATASRC_QUERY_CHECK_CACHE checking hotspot cache for '%1/%2'

Debug information. While processing a query, lookup to the hotspot cache is being made.

DATASRC_QUERY_COPY_AUTH copying authoritative section into message

Debug information. The whole referral information is being copied into the response message.

DATASRC_QUERY_DELEGATION looking for delegation on the path to '%1'

Debug information. The software is trying to identify delegation points on the way down to the given domain.

DATASRC_QUERY_EMPTY_CNAME CNAME at '%1' is empty

A CNAME chain was being followed and an entry was found that pointed to a domain name that had no RRsets associated with it. As a result, the query cannot be answered. This indicates a problem with supplied data.

DATASRC_QUERY_EMPTY_DNAME the DNAME on '%1' is empty

During an attempt to synthesize CNAME from this DNAME it was discovered the DNAME is empty (it has no records). This indicates problem with supplied data.

DATASRC_QUERY_FAIL query failed

Some subtask of query processing failed. The reason should have been reported already and a SERVFAIL will be returned to the querying system.

DATASRC_QUERY_FOLLOW_CNAME following CNAME at '%1'

Debug information. The domain is a CNAME (or a DNAME and a CNAME for it has already been created) and the search is following this chain.

DATASRC_QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2'

Debug information. While processing a query, a MX record was met. It references the mentioned address, so A/AAAA records for it are looked up and put it into the additional section.

DATASRC_QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2'

Debug information. While processing a query, a NS record was met. It references the mentioned address, so A/AAAA records for it are looked up and put it into the additional section.

DATASRC_QUERY_GLUE_FAIL the underlying data source failed with %1

The underlying data source failed to answer the glue query. 1 means some error, 2 is not implemented. The data source should have logged the specific error already.

DATASRC_QUERY_INVALID_OP invalid query operation requested

This indicates a programmer error. The DO_QUERY was called with unknown operation code.

DATASRC_QUERY_IS_AUTH auth query (%1/%2)

Debug information. The last DO_QUERY is an auth query.

DATASRC_QUERY_IS_GLUE glue query (%1/%2)

Debug information. The last DO_QUERY is a query for glue addresses.

DATASRC_QUERY_IS_NOGLUE query for non-glue addresses (%1/%2)

Debug information. The last DO_QUERY is a query for addresses that are not glue.

DATASRC_QUERY_IS_REF query for referral (%1/%2)

Debug information. The last DO_QUERY is a query for referral information.

DATASRC_QUERY_IS_SIMPLE simple query (%1/%2)

Debug information. The last DO_QUERY is a simple query.

DATASRC_QUERY_MISPLACED_TASK task of this type should not be here

This indicates a programming error. A task was found in the internal task queue, but this kind of task wasn't designed to be inside the queue (it should be handled right away, not queued).

DATASRC_QUERY_MISSING_NS missing NS records for '%1'

NS records should have been put into the authority section. However, this zone has none. This indicates problem with provided data.

DATASRC_QUERY_MISSING_SOA the zone '%1' has no SOA

The answer should have been a negative one (eg. of nonexistence of something). To do so, a SOA record should be put into the authority section, but the zone does not have one. This indicates problem with provided data.

DATASRC_QUERY_NOGLUE_FAIL the underlying data source failed with %1

The underlying data source failed to answer the no-glue query. 1 means some error, 2 is not implemented. The data source should have logged the specific error already.

DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring hotspot cache for ANY query (%1/%2 in %3 class)

Debug information. The hotspot cache is ignored for authoritative ANY queries for consistency reasons.

DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring hotspot cache for ANY query (%1/%2 in %3 class)

Debug information. The hotspot cache is ignored for ANY queries for consistency reasons.

DATASRC_QUERY_NO_DS_NSEC there's no DS record in the '%1' zone

An attempt to add a NSEC record into the message failed, because the zone does not have any DS record. This indicates problem with the provided data.

DATASRC_QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone

An attempt to add a NSEC3 record into the message failed, because the zone does not have any DS record. This indicates problem with the provided data.

DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'

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.

DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class

Debug information. A sure query is being processed now.

DATASRC_QUERY_PROVE_NX_FAIL unable to prove nonexistence of '%1'

The user wants DNSSEC and we discovered the entity doesn't exist (either domain or the record). But there was an error getting NSEC/NSEC3 record to prove the nonexistence.

DATASRC_QUERY_REF_FAIL the underlying data source failed with %1

The underlying data source failed to answer the query for referral information. 1 means some error, 2 is not implemented. The data source should have logged the specific error already.

DATASRC_QUERY_RRSIG unable to answer RRSIG query for %1

The server is unable to answer a direct query for RRSIG type, but was asked to do so.

DATASRC_QUERY_SIMPLE_FAIL the underlying data source failed with %1

The underlying data source failed to answer the simple query. 1 means some error, 2 is not implemented. The data source should have logged the specific error already.

DATASRC_QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1'

This is a debug message. While answering a query, a DNAME was encountered. The DNAME itself will be returned, along with a synthesized CNAME for clients that do not understand the DNAME RR.

DATASRC_QUERY_TASK_FAIL task failed with %1

The query subtask failed. The reason should have been reported by the subtask already. The code is 1 for error, 2 for not implemented.

DATASRC_QUERY_TOO_MANY_CNAMES CNAME chain limit exceeded at '%1'

A CNAME led to another CNAME and it led to another, and so on. After 16 CNAMEs, the software gave up. Long CNAME chains are discouraged, and this might possibly be a loop as well. Note that some of the CNAMEs might have been synthesized from DNAMEs. This indicates problem with supplied data.

DATASRC_QUERY_UNKNOWN_RESULT unknown result of subtask

This indicates a programmer error. The answer of subtask doesn't look like anything known.

DATASRC_QUERY_WILDCARD looking for a wildcard covering '%1'

Debug information. A direct match wasn't found, so a wildcard covering the domain is being looked for now.

DATASRC_QUERY_WILDCARD_FAIL error processing wildcard for '%1'

During an attempt to cover the domain by a wildcard an error happened. The exact kind was hopefully already reported.

DATASRC_QUERY_WILDCARD_PROVE_NX_FAIL unable to prove nonexistence of '%1' (%2)

While processing a wildcard, it wasn't possible to prove nonexistence of the given domain or record. The code is 1 for error and 2 for not implemented.

DATASRC_QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2)

While processing a wildcard, a referral was met. But it wasn't possible to get 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_COMPATIBLE_VERSION database schema V%1.%2 not up to date (expecting V%3.%4) but is compatible

The version of the SQLite3 database schema used to hold the zone data is not the latest one - the current version of BIND 10 was written with a later schema version in mind. However, the database is compatible with the current version of BIND 10, and BIND 10 will run without any problems.

Consult the release notes for your version of BIND 10. Depending on the changes made to the database schema, it is possible that improved performance could result if the database were upgraded.

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.

DATASRC_SQLITE_DESTROY SQLite data source destroyed

Debug information. An instance of SQLite data source is being destroyed.

DATASRC_SQLITE_DROPCONN SQLite3 database '%1' is being closed

The object around a database connection is being destroyed. If the SQLite3 database file was open, it will be closed now.

DATASRC_SQLITE_ENCLOSURE looking for zone containing '%1'

Debug information. The SQLite data source is trying to identify which zone should hold this domain.

DATASRC_SQLITE_ENCLOSURE_NOT_FOUND no zone contains '%1'

Debug information. The last SQLITE_ENCLOSURE query was unsuccessful; there's no such zone in our data.

DATASRC_SQLITE_FIND looking for RRset '%1/%2'

Debug information. The SQLite data source is looking up a resource record set.

DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'

Debug information. The data source is looking up the addresses for given domain name.

DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')

The SQLite data source was looking up A/AAAA addresses, but the data source contains different class than the query was for.

DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2'

Debug information. The SQLite data source is looking up an exact resource record.

DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')

The SQLite data source was looking up an exact RRset, but the data source contains different class than the query was for.

DATASRC_SQLITE_FINDREC looking for record '%1/%2'

Debug information. The SQLite data source is looking up records of given name and type in the database.

DATASRC_SQLITE_FINDREF looking for referral at '%1'

Debug information. The SQLite data source is identifying if this domain is a referral and where it goes.

DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')

The SQLite data source was trying to identify if there's a referral. But it contains different class than the query was for.

DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')

The SQLite data source was looking up an RRset, but the data source contains different class than the query was for.

DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'

Debug information. We're trying to look up a NSEC3 record in the SQLite data source.

DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'

The SQLite data source was asked to provide a NSEC3 record for given zone. But it doesn't contain that zone.

DATASRC_SQLITE_INCOMPATIBLE_VERSION database schema V%1.%2 incompatible with version (V%3.%4) expected

The version of the SQLite3 database schema used to hold the zone data is incompatible with the version expected by BIND 10. As a result, BIND 10 is unable to run using the database file as the data source.

The database should be updated using the means described in the BIND 10 documentation.

DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized

A wrapper object to hold database connection is being initialized.

DATASRC_SQLITE_OPEN opening SQLite database '%1'

Debug information. The SQLite data source is loading an SQLite database in the provided file.

DATASRC_SQLITE_PREVIOUS looking for name previous to '%1'

This is a debug message. The name given was not found, so the program is searching for the next name higher up the hierarchy (e.g. if www.example.com were queried for and not found, the software searches for the "previous" name, example.com).

DATASRC_SQLITE_PREVIOUS_NO_ZONE no zone containing '%1'

The name given was not found, so the program is searching for the next name higher up the hierarchy (e.g. if www.example.com were queried for and not found, the software searches for the "previous" name, example.com). However, this name is not contained in any zone in the data source. This is an error since it indicates a problem in the earlier processing of the query.

DATASRC_SQLITE_SETUP setting up new SQLite3 database in '%1'

The database for SQLite data source was found empty. It is assumed this is the first run and it is being initialized with current schema. It'll still contain no data, but it will be ready for use. If this is indeed the first run of BIND 10, it is to be expected and completely harmless. If you just configured a data source to point to an existing file and you see this, you may have misspelled the file name.

DATASRC_SQLITE_SETUP_OLD_API setting up new SQLite database

The database for SQLite data source was found empty. It is assumed this is the first run and it is being initialized with current schema. It'll still contain no data, but it will be ready for use. This is similar to DATASRC_SQLITE_SETUP message, but it is logged from the old API. You should never see it, since the API is deprecated.

DATASRC_STATIC_CLASS_NOT_CH static data source can handle CH class only

An error message indicating that a query requesting a RR for a class other that CH was sent to the static data source (which only handles CH queries).

DATASRC_STATIC_CREATE creating the static datasource

Debug information. The static data source (the one holding stuff like version.bind) is being created.

DATASRC_STATIC_FIND looking for '%1/%2'

Debug information. This resource record set is being looked up in the static data source.

DATASRC_UNEXPECTED_QUERY_STATE unexpected query state

This indicates a programming error. An internal task of unknown type was generated.

DBUTIL_BACKUP created backup of %1 in %2

A backup for the given database file was created. Same of original file and backup are given in the output message.

DBUTIL_CHECK_ERROR unable to check database version: %1

There was an error while trying to check the current version of the database schema. The error is shown in the message.

DBUTIL_CHECK_NOCONFIRM --noconfirm is not compatible with --check

b10-dbutil was called with --check and --noconfirm. --noconfirm only has meaning with --upgrade, so this is considered an error.

DBUTIL_CHECK_OK this is the latest version of the database schema. No upgrade is required

The database schema version has been checked, and is up to date. No action is required.

DBUTIL_CHECK_UPGRADE_NEEDED re-run this program with the --upgrade switch to upgrade

The database schema version is not up to date, and an update is required. Please run the dbutil tool again, with the --upgrade argument.

DBUTIL_COMMAND_NONE must select one of --check or --upgrade

b10-dbutil was called with neither --check nor --upgrade. One action must be provided.

DBUTIL_COMMAND_UPGRADE_CHECK --upgrade is not compatible with --check

b10-dbutil was called with both the commands --upgrade and --check. Only one action can be performed at a time.

DBUTIL_DATABASE_MAY_BE_CORRUPT database file %1 may be corrupt, restore it from backup (%2)

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.

DBUTIL_EXECUTE Executing SQL statement: %1

Debug message; the given SQL statement is executed.

DBUTIL_FILE Database file: %1

The database file that is being checked.

DBUTIL_NO_FILE must supply name of the database file to upgrade

b10-dbutil was called without a database file. Currently, it cannot find this file on its own, and it must be provided.

DBUTIL_STATEMENT_ERROR failed to execute %1: %2

The given database statement failed to execute. The error is shown in the message.

DBUTIL_TOO_MANY_ARGUMENTS too many arguments to the command, maximum of one expected

There were too many command-line arguments to b10-dbutil.

DBUTIL_UPGRADE_CANCELED upgrade canceled; database has not been changed

The user aborted the upgrade, and b10-dbutil will now exit.

DBUTIL_UPGRADE_DBUTIL please get the latest version of b10-dbutil and re-run

A database schema was found that was newer than this version of dbutil, which is apparently out of date and should be upgraded itself.

DBUTIL_UPGRADE_FAILED upgrade failed: %1

While the upgrade was in progress, an unexpected error occurred. The error is shown in the message.

DBUTIL_UPGRADE_NOT_ATTEMPTED database upgrade was not attempted

Due to the earlier failure, the database schema upgrade was not attempted, and b10-dbutil will now exit.

DBUTIL_UPGRADE_NOT_NEEDED database already at latest version, no upgrade necessary

b10-dbutil was told to upgrade the database schema, but it is already at the latest version.

DBUTIL_UPGRADE_NOT_POSSIBLE database at a later version than this utility can support

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.

DBUTIL_UPGRADE_PREPARATION_FAILED upgrade preparation failed: %1

An unexpected error occurred while b10-dbutil was preparing to upgrade the database schema. The error is shown in the message.

DBUTIL_UPGRADE_SUCCESFUL database upgrade successfully completed

The database schema update was completed successfully.

DBUTIL_UPGRADING upgrading database from %1 to %2

An upgrade is in progress, the versions of the current upgrade action are shown.

DBUTIL_VERSION_CURRENT database version %1

The current version of the database schema.

DBUTIL_VERSION_HIGH database is at a later version (%1) than this program can cope with (%2)

The database schema is at a higher version than b10-dbutil knows about.

DBUTIL_VERSION_LOW database version %1, latest version is %2.

The database schema is not up to date, the current version and the latest version are in the message.

DCTL_CCSESSION_ENDING %1 ending control channel session

This debug message is issued just before the controller attempts to disconnect from its session with the BIND10 control channel.

DCTL_CCSESSION_STARTING %1 starting control channel session, specfile: %2

This debug message is issued just before the controller attempts to establish a session with the BIND10 control channel.

DCTL_COMMAND_RECEIVED %1 received command: %2, arguments: %3

A debug message listing the command (and possible arguments) received from the BIND10 control system by the controller.

DCTL_CONFIG_COMPLETE server has completed configuration: %1

This is an informational message announcing the successful processing of a new configuration. It is output during server startup, and when an updated configuration is committed by the administrator. Additional information may be provided.

DCTL_CONFIG_LOAD_FAIL %1 configuration failed to load: %2

This critical error message indicates that the initial application configuration has failed. The service will start, but will not process requests until the configuration has been corrected.

DCTL_CONFIG_START parsing new configuration: %1

A debug message indicating that the application process has received an updated configuration and has passed it to its configuration manager for parsing.

DCTL_CONFIG_STUB %1 configuration stub handler called

This debug message is issued when the dummy handler for configuration events is called. This only happens during initial startup.

DCTL_CONFIG_UPDATE %1 updated configuration received: %2

A debug message indicating that the controller has received an updated configuration from the BIND10 configuration system.

DCTL_DISCONNECT_FAIL %1 controller failed to end session with BIND10: %2

This message indicates that while shutting down, the Dhcp-Ddns controller encountered an error terminating communication with the BIND10. The service will still exit. While theoretically possible, this situation is rather unlikely.

DCTL_INIT_PROCESS %1 initializing the application

This debug message is issued just before the controller attempts to create and initialize its application instance.

DCTL_INIT_PROCESS_FAIL %1 application initialization failed: %2

This error message is issued if the controller could not initialize the application and will exit.

DCTL_NOT_RUNNING %1 application instance is not running

A warning message is issued when an attempt is made to shut down the application when it is not running.

DCTL_ORDER_ERROR configuration contains more elements than the parsing order

An error message which indicates that configuration being parsed includes element ids not specified the configuration manager's parse order list. This is a programmatic error.

DCTL_ORDER_NO_ELEMENT element: %1 is in the parsing order but is missing from the configuration

An error message output during a configuration update. The program is expecting an item but has not found it in the new configuration. This may mean that the BIND 10 configuration database is corrupt.

DCTL_PARSER_FAIL configuration parsing failed for configuration element: %1, reason: %2

On receipt of message containing details to a change of its configuration, the server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The reason for the failure is given in the message.

DCTL_PROCESS_FAILED %1 application execution failed: %2

The controller has encountered a fatal error while running the application and is terminating. The reason for the failure is included in the message.

DCTL_RUN_PROCESS %1 starting application event loop

This debug message is issued just before the controller invokes the application run method.

DCTL_SESSION_FAIL %1 controller failed to establish BIND10 session: %1

The controller has failed to establish communication with the rest of BIND 10 and will exit.

DCTL_STANDALONE %1 skipping message queue, running standalone

This is a debug message indicating that the controller is running in the application in standalone mode. This means it will not connected to the BIND10 message queue. Standalone mode is only useful during program development, and should not be used in a production environment.

DCTL_STARTING %1 controller starting, pid: %2

This is an informational message issued when controller for the service first starts.

DCTL_STOPPING %1 controller is exiting

This is an informational message issued when the controller is exiting following a shut down (normal or otherwise) of the service.

DDNS_ACCEPT_FAILURE error accepting a connection: %1

There was a low-level error when we tried to accept an incoming connection (probably coming from b10-auth). We continue serving on whatever other connections we already have, but this connection is dropped. The reason is logged.

DDNS_AUTH_DBFILE_UPDATE updated auth DB file to %1

b10-ddns was notified of updates to the SQLite3 DB file that b10-auth uses for the underlying data source and on which b10-ddns needs to make updates. b10-ddns then updated its internal setup so further updates would be made on the new DB.

DDNS_CC_SESSION_ERROR error reading from cc channel: %1

There was a problem reading from the command and control channel. The most likely cause is that the msgq process is not running.

DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response

There was a problem reading a response from another module over the command and control channel. The most likely cause is that the configuration manager b10-cfgmgr is not running.

DDNS_CONFIG_ERROR error found in configuration data: %1

The ddns process encountered an error when installing the configuration at startup time. Details of the error are included in the log message.

DDNS_CONFIG_HANDLER_ERROR failed to update ddns configuration: %1

An update to b10-ddns configuration was delivered but an error was found while applying them. None of the delivered updates were applied to the running b10-ddns system, and the server will keep running with the existing configuration. If this happened in the initial configuration setup, the server will be running with the default configurations.

DDNS_DROP_CONN dropping connection on file descriptor %1 because of error %2

There was an error on a connection with the b10-auth server (or whatever connects to the ddns daemon). This might be OK, for example when the authoritative server shuts down, the connection would get closed. It also can mean the system is busy and can't keep up or that the other side got confused and sent bad data.

DDNS_GET_REMOTE_CONFIG_FAIL failed to get %1 module configuration %2 times: %3

b10-ddns tried to get configuration of some remote modules for its operation, but it failed. The most likely cause of this is that the remote module has not fully started up and b10-ddns couldn't get the configuration in a timely fashion. b10-ddns attempts to retry it a few times, imposing a short delay, hoping it eventually succeeds if it's just a timing issue. The number of total failed attempts is also logged. If it reaches an internal threshold b10-ddns considers it a fatal error and terminates. Even in that case, if b10-ddns is configured as a "dispensable" component (which is the default), the parent ("init") process will restart it, and there will be another chance of getting the remote configuration successfully. These are not the optimal behavior, but it's believed to be sufficient in practice (there would normally be no failure in the first place). If it really causes an operational trouble other than having a few of these log messages, please submit a bug report; there can be several ways to make it more sophisticated. Another, less likely reason for having this error is because the remote modules are not actually configured to run. If that's the case fixing the configuration should solve the problem - either by making sure the remote module will run or by not running b10-ddns (without these remote modules b10-ddns is not functional, so there's no point in running it in this case).

DDNS_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1

There was a problem in the lower level module handling configuration and control commands. This could happen for various reasons, but the most likely cause is that the configuration database contains a syntax error and ddns failed to start at initialization. A detailed error message from the module will also be displayed.

DDNS_NEW_CONN new connection on file descriptor %1 from %2

Debug message. We received a connection and we are going to start handling requests from it. The file descriptor number and the address where the request comes from is logged. The connection is over a unix domain socket and is likely coming from a b10-auth process.

DDNS_RECEIVED_AUTH_UPDATE received configuration updates from auth server

b10-ddns is notified of updates to b10-auth configuration (including a report of the initial configuration) that b10-ddns might be interested in.

DDNS_RECEIVED_SHUTDOWN_COMMAND shutdown command received

The ddns process received a shutdown command from the command channel and will now shut down.

DDNS_RECEIVED_ZONEMGR_UPDATE received configuration updates from zonemgr

b10-ddns is notified of updates to b10-zonemgr's configuration (including a report of the initial configuration). It may possibly contain changes to the secondary zones, in which case b10-ddns will update its internal copy of that configuration.

DDNS_REQUEST_PARSE_FAIL failed to parse update request: %1

b10-ddns received an update request via b10-auth, but the received data failed to pass minimum validation: it was either broken wire format data for a valid DNS message (e.g. it's shorter than the fixed-length header), or the opcode is not update, or TSIG is included in the request but it fails to validate. Since b10-auth should have performed this level of checks, such an error shouldn't be detected at this stage and should rather be considered an internal bug. This event is therefore logged at the error level, and the request is simply dropped. Additional information of the error is also logged.

DDNS_REQUEST_TCP_QUOTA reject TCP update client %1 (%2 running)

b10-ddns received a new update request from a client over TCP, but the number of TCP clients being handled by the server already reached the configured quota, so the latest client was rejected by closing the connection. The administrator may want to check the status of b10-ddns, and if this happens even if the server is not very busy, the quota may have to be increased. Or, if it's more likely to be malicious or simply bogus clients that somehow keep the TCP connection open for a long period, maybe they should be rejected with an appropriate ACL configuration or some lower layer filtering. The number of existing TCP clients are shown in the log, which should be identical to the current quota.

DDNS_RESPONSE_SOCKET_SEND_FAILED failed to send update response to %1: %2

Network I/O error happens in sending an update response. The client's address that caused the error and error details are also logged.

DDNS_RESPONSE_TCP_SOCKET_SEND_FAILED failed to complete sending update response to %1 over TCP

b10-ddns had tried to send an update response over TCP, and it hadn't been completed at that time, and a follow-up attempt to complete the send operation failed due to some network I/O error. While a network error can happen any time, this event is quite unexpected for two reasons. First, since the size of a response to an update request should be generally small, it's unlikely that the initial attempt didn't fail but wasn't completed. Second, since the first attempt succeeded and the TCP connection had been established in the first place, it's more likely for the subsequent attempt to succeed. In any case, there may not be able to do anything to fix it at the server side, but the administrator may want to check the general reachability with the client address.

DDNS_SECONDARY_ZONES_UPDATE updated secondary zone list (%1 zones are listed)

b10-ddns has successfully updated the internal copy of secondary zones obtained from b10-zonemgr, based on a latest update to zonemgr's configuration. The number of newly configured (unique) secondary zones is logged.

DDNS_SECONDARY_ZONES_UPDATE_FAIL failed to update secondary zone list: %1

An error message. b10-ddns was notified of updates to a list of secondary zones from b10-zonemgr and tried to update its own internal copy of the list, but it failed. This can happen if the configuration contains an error, and b10-zonemgr should also reject that update. Unfortunately, in the current implementation there is no way to ensure that both zonemgr and ddns have consistent information when an update contains an error; further, as of this writing zonemgr has a bug that it could partially update the list of secondary zones if part of the list has an error (see Trac ticket #2038). b10-ddns still keeps running with the previous configuration, but it's strongly advisable to check log messages from zonemgr, and if it indicates there can be inconsistent state, it's better to restart the entire BIND 10 system (just restarting b10-ddns wouldn't be enough, because zonemgr can have partially updated configuration due to bug #2038). The log message contains an error description, but it's intentionally kept simple as it's primarily a matter of zonemgr. To know the details of the error, log messages of zonemgr should be consulted.

DDNS_SESSION session arrived on file descriptor %1

A debug message, informing there's some activity on the given file descriptor. It will be either a request or the file descriptor will be closed. See following log messages to see what of it.

DDNS_SHUTDOWN ddns server shutting down

The ddns process is shutting down. It will no longer listen for new commands or updates. Any command or update that is being addressed at this moment will be completed, after which the process will exit.

DDNS_STARTED ddns server is running and listening for updates

The ddns process has successfully started and is now ready to receive commands and updates.

DDNS_START_FORWARDER_ERROR Error from b10-auth when requesting DDNS UPDATE forwarding: %1

There was an error response from b10-auth to the command to start forwarding DDNS UPDATE messages to b10-ddns. It is almost certain that DDNS UPDATE messages are not handled now, and that they will be responded to with a NOTIMP error code, even though b10-ddns is running. The error message is printed, and additional information may be found in the b10-auth log output. Since this is an error that is sent by the b10-auth module, it should have more information as to what the actual problem was.

DDNS_START_FORWARDER_FAIL Error sending request for DDNS UPDATE forwarding to b10-auth: %1

There was an error when attempting to send b10-auth the request to forward DDNS UPDATE messages to the b10-ddns module. This points to an internal problem using the inter-module messaging system. This needs to be inspected, as it is almost certain that DDNS UPDATE messages are not handled now. The specific error is printed in the log message.

DDNS_STOPPED ddns server has stopped

The ddns process has successfully stopped and is no longer listening for or handling commands or updates, and will now exit.

DDNS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the ddns process. The process will now shut down.

DDNS_STOP_FORWARDER_ERROR Error from b10-auth when requesting to stop DDNS UPDATE forwarding: %1

There was an error response from b10-auth to the command to stop forwarding DDNS UPDATE messages to b10-ddns. This specific error may not be fatal; instead of returning NOTIMP for future DDNS UPDATE messages, it will return SERVFAIL. However, this does point to an underlying problem in the messaging system, and should be inspected. The error message is printed, and additional information may be found in the b10-auth log output.

DDNS_STOP_FORWARDER_FAIL Error sending request to stop DDNS UPDATE forwarding to b10-auth: %1

There was an error when attempting to send b10-auth the request to stop forwarding DDNS UPDATE messages to the b10-ddns module. This points to an internal problem using the inter-module messaging system. This specific error may not be fatal; instead of returning NOTIMP for future DDNS UPDATE messages, it will return SERVFAIL. However, this does point to an underlying problem in the messaging system, and should be inspected. The specific error is printed in the log message.

DDNS_UPDATE_NOTIFY notified %1 of updates to %2

Debug message. b10-ddns has made updates to a zone based on an update request and has successfully notified an external module of the updates. The notified module will use that information for updating its own state or any necessary protocol action such as zone reloading or sending notify messages to secondary servers.

DDNS_UPDATE_NOTIFY_FAIL failed to notify %1 of updates to %2: %3

b10-ddns has made updates to a zone based on an update request and tried to notify an external component of the updates, but the notification fails. One possible cause of this is that the external component is not really running, although it will be less likely to happen in practice because these components will normally be configured to run when the server provides the authoritative DNS service; ddns is rather optional among them. Severity of this error for the receiving components depends on the type of the component. If it's b10-xfrout, this means DNS notify messages won't be sent to secondary servers of the zone. It's suboptimal, but not necessarily critical as the secondary servers will try to check the zone's status periodically. If it's b10-auth and the notification was needed to have it reload the corresponding zone, it's more serious because b10-auth won't be able to serve the new version of the zone unless some explicit recovery action is taken. So the administrator needs to examine this message and takes an appropriate action. In either case, this notification is generally expected to succeed; so the fact it fails itself means there's something wrong in the BIND 10 system, and it would be advisable to check other log messages.

DHCP4_ACTIVATE_INTERFACE activating interface %1

This message is printed when DHCPv4 server enabled an interface to be used to receive DHCPv4 traffic. IPv4 socket on this interface will be opened once Interface Manager starts up procedure of opening sockets.

DHCP4_CCSESSION_STARTED control channel session started on socket %1

A debug message issued during startup after the DHCPv4 server has successfully established a session with the BIND 10 control channel.

DHCP4_CCSESSION_STARTING starting control channel session, specfile: %1

This debug message is issued just before the DHCPv4 server attempts to establish a session with the BIND 10 control channel.

DHCP4_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1

This debug message informs that incoming packet has been assigned to specified class or classes. This is a norma

DHCP4_CLASS_PROCESSING_FAILED client class specific processing failed

This debug message means that the server processing that is unique for each client class has reported a failure. The response packet will not be sent.

DHCP4_CLIENT_NAME_PROC_FAIL failed to process the fqdn or hostname sent by a client: %1

This debug message is issued when the DHCP server was unable to process the FQDN or Hostname option sent by a client. This is likely because the client's name was malformed or due to internal server error.

DHCP4_COMMAND_RECEIVED received command %1, arguments: %2

A debug message listing the command (and possible arguments) received from the BIND 10 control system by the DHCPv4 server.

DHCP4_CONFIG_COMPLETE DHCPv4 server has completed configuration: %1

This is an informational message announcing the successful processing of a new configuration. It is output during server startup, and when an updated configuration is committed by the administrator. Additional information may be provided.

DHCP4_CONFIG_LOAD_FAIL failed to load configuration: %1

This critical error message indicates that the initial DHCPv4 configuration has failed. The server will start, but nothing will be served until the configuration has been corrected.

DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1

This is an informational message reporting that the configuration has been extended to include the specified IPv4 subnet.

DHCP4_CONFIG_OPTION_DUPLICATE multiple options with the code %1 added to the subnet %2

This warning message is issued on an attempt to configure multiple options with the same option code for a particular subnet. Adding multiple options is uncommon for DHCPv4, but is not prohibited.

DHCP4_CONFIG_START DHCPv4 server is processing the following configuration: %1

This is a debug message that is issued every time the server receives a configuration. That happens at start up and also when a server configuration change is committed by the administrator.

DHCP4_CONFIG_UPDATE updated configuration received: %1

A debug message indicating that the DHCPv4 server has received an updated configuration from the BIND 10 configuration system.

DHCP4_DB_BACKEND_STARTED lease database started (type: %1, name: %2)

This informational message is printed every time DHCPv4 server is started and gives both the type and name of the database being used to store lease and other information.

DHCP4_DDNS_REQUEST_SEND_FAILED failed sending a request to b10-dhcp-ddns, error: %1, ncr: %2

This error message indicates that DHCP4 server attempted to send a DDNS update reqeust to the DHCP-DDNS server. This is most likely a configuration or networking error.

DHCP4_DEACTIVATE_INTERFACE deactivate interface %1

This message is printed when DHCPv4 server disables an interface from being used to receive DHCPv4 traffic. Sockets on this interface will not be opened by the Interface Manager until interface is enabled.

DHCP4_DHCID_COMPUTE_ERROR failed to compute the DHCID for lease: %1, reason: %2

This error message is logged when the attempt to compute DHCID for a specified lease has failed. The lease details and reason for failure is logged in the message.

DHCP4_EMPTY_HOSTNAME received empty hostname from the client, skipping processing of this option

This debug message is issued when the server received an empty Hostname option from a client. Server does not process empty Hostname options and therefore option is skipped.

DHCP4_HOOKS_LIBS_RELOAD_FAIL reload of hooks libraries failed

A "libreload" command was issued to reload the hooks libraries but for some reason the reload failed. Other error messages issued from the hooks framework will indicate the nature of the problem.

DHCP4_HOOK_BUFFER_RCVD_SKIP received DHCPv4 buffer was dropped because a callout set the skip flag.

This debug message is printed when a callout installed on buffer4_receive hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet.

DHCP4_HOOK_BUFFER_SEND_SKIP prepared DHCPv4 response was dropped because a callout set the skip flag.

This debug message is printed when a callout installed on buffer4_send hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. Server completed all the processing (e.g. may have assigned, updated or released leases), but the response will not be send to the client.

DHCP4_HOOK_LEASE4_RELEASE_SKIP DHCPv4 lease was not released because a callout set the skip flag.

This debug message is printed when a callout installed on lease4_release hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not release a lease.

DHCP4_HOOK_PACKET_RCVD_SKIP received DHCPv4 packet was dropped, because a callout set the skip flag.

This debug message is printed when a callout installed on the pkt4_receive hook point sets the skip flag. For this particular hook point, the setting of the flag instructs the server to drop the packet.

DHCP4_HOOK_PACKET_SEND_SKIP prepared DHCPv6 response was not sent, because a callout set skip flag.

This debug message is printed when a callout installed on the pkt4_send hook point sets the skip flag. For this particular hook point, the setting of the flag instructs the server to drop the packet. This means that the client will not get any response, even though the server processed client's request and acted on it (e.g. possibly allocated a lease).

DHCP4_HOOK_SUBNET4_SELECT_SKIP no subnet was selected, because a callout set skip flag.

This debug message is printed when a callout installed on the subnet4_select hook point sets the skip flag. For this particular hook point, the setting of the flag instructs the server not to choose a subnet, an action that severely limits further processing; the server will be only able to offer global options - no addresses will be assigned.

DHCP4_LEASE_ADVERT lease %1 advertised (client client-id %2, hwaddr %3)

This debug message indicates that the server successfully advertised a lease. It is up to the client to choose one server out of othe advertised and continue allocation with that server. This is a normal behavior and indicates successful operation.

DHCP4_LEASE_ADVERT_FAIL failed to advertise a lease for client client-id %1, hwaddr %2, client sent yiaddr %3

This message indicates that the server has failed to offer a lease to the specified client after receiving a DISCOVER message from it. There are many possible reasons for such a failure.

DHCP4_LEASE_ALLOC lease %1 has been allocated for client-id %2, hwaddr %3

This debug message indicates that the server successfully granted a lease in response to client's REQUEST message. This is a normal behavior and indicates successful operation.

DHCP4_LEASE_ALLOC_FAIL failed to grant a lease for client-id %1, hwaddr %2, client sent yiaddr %3

This message indicates that the server failed to grant a lease to the specified client after receiving a REQUEST message from it. There are many possible reasons for such a failure. Additional messages will indicate the reason.

DHCP4_NAME_GEN_UPDATE_FAIL failed to update the lease after generating name for a client: %1

This message indicates the failure when trying to update the lease and/or options in the server's response with the hostname generated by the server from the acquired address. The message argument indicates the reason for the failure.

DHCP4_NCR_CREATION_FAILED failed to generate name change requests for DNS: %1

This message indicates that server was unable to generate NameChangeRequests which should be sent to the b10-dhcp_ddns module to create new DNS records for the lease being acquired or to update existing records for the renewed lease. The reason for the failure is printed in the logged message.

DHCP4_NOT_RUNNING DHCPv4 server is not running

A warning message is issued when an attempt is made to shut down the DHCPv4 server but it is not running.

DHCP4_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic

This warning message is issued when current server configuration specifies no interfaces that server should listen on, or specified interfaces are not configured to receive the traffic.

DHCP4_NO_SUBNET_FOR_DIRECT_CLIENT no suitable subnet configured for a direct client sending packet with transaction id %1, on interface %2, received message is dropped

This info messsage is logged when received a message from a directly connected client but there is no suitable subnet configured for the interface on which this message has been received. The IPv4 address assigned on this interface must belong to one of the configured subnets. Otherwise received message is dropped.

DHCP4_OPEN_SOCKET opening sockets on port %1

A debug message issued during startup, this indicates that the DHCPv4 server is about to open sockets on the specified port.

DHCP4_OPEN_SOCKET_FAIL failed to create socket: %1

A warning message issued when IfaceMgr fails to open and bind a socket. The reason for the failure is appended as an argument of the log message.

DHCP4_PACKET_DROP_NO_TYPE packet received on interface %1 dropped, because of missing msg-type option

This is a debug message informing that incoming DHCPv4 packet did not have mandatory DHCP message type option and thus was dropped.

DHCP4_PACKET_NOT_FOR_US received DHCPv4 message (transid=%1, iface=%2) dropped because it contains foreign server identifier

This debug message is issued when received DHCPv4 message is dropped because it is addressed to a different server, i.e. a server identifier held by this message doesn't match the identifier used by our server. The arguments of this message hold the name of the transaction id and interface on which the message has been received.

DHCP4_PACKET_PARSE_FAIL failed to parse incoming packet: %1

The DHCPv4 server has received a packet that it is unable to interpret. The reason why the packet is invalid is included in the message.

DHCP4_PACKET_PROCESS_FAIL failed to process packet received from %1: %2

This is a general catch-all message indicating that the processing of a received packet failed. The reason is given in the message. The server will not send a response but will instead ignore the packet.

DHCP4_PACKET_RECEIVED %1 (type %2) packet received on interface %3

A debug message noting that the server has received the specified type of packet on the specified interface. Note that a packet marked as UNKNOWN may well be a valid DHCP packet, just a type not expected by the server (e.g. it will report a received OFFER packet as UNKNOWN).

DHCP4_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1

The DHCPv4 server tried to receive a packet but an error occurred during this attempt. The reason for the error is included in the message.

DHCP4_PACKET_SEND_FAIL failed to send DHCPv4 packet: %1

This error is output if the DHCPv4 server fails to send an assembled DHCP message to a client. The reason for the error is included in the message.

DHCP4_PARSER_COMMIT_EXCEPTION parser failed to commit changes

On receipt of message containing details to a change of the DHCPv4 server configuration, a set of parsers were successfully created, but one of them failed to commit its changes due to a low-level system exception being raised. Additional messages may be output indicating the reason.

DHCP4_PARSER_COMMIT_FAIL parser failed to commit changes: %1

On receipt of message containing details to a change of the DHCPv4 server configuration, a set of parsers were successfully created, but one of them failed to commit its changes. The reason for the failure is given in the message.

DHCP4_PARSER_CREATED created parser for configuration element %1

A debug message output during a configuration update of the DHCPv4 server, notifying that the parser for the specified configuration element has been successfully created.

DHCP4_PARSER_EXCEPTION failed to create or run parser for configuration element %1

On receipt of message containing details to a change of its configuration, the DHCPv4 server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The message has been output in response to a non-BIND 10 exception being raised. Additional messages may give further information.

DHCP4_PARSER_FAIL failed to create or run parser for configuration element %1: %2

On receipt of message containing details to a change of its configuration, the DHCPv4 server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The reason for the failure is given in the message.

DHCP4_QUERY_DATA received packet type %1, data is <%2>

A debug message listing the data received from the client.

DHCP4_QUEUE_NCR name change request to %1 DNS entry queued: %2

A debug message which is logged when the NameChangeRequest to add or remove a DNS entries for a particular lease has been queued. The first parameter of this log message indicates whether the DNS entry is to be added or removed. The second parameter carries the details of the NameChangeRequest.

DHCP4_RELEASE address %1 belonging to client-id %2, hwaddr %3 was released properly.

This debug message indicates that an address was released properly. It is a normal operation during client shutdown.

DHCP4_RELEASE_EXCEPTION exception %1 while trying to release address %2

This message is output when an error was encountered during an attempt to process a RELEASE message. The error will not affect the client, which does not expect any response from the server for RELEASE messages. Depending on the nature of problem, it may affect future server operation.

DHCP4_RELEASE_FAIL failed to remove lease for address %1 for duid %2, hwaddr %3

This error message indicates that the software failed to remove a lease from the lease database. It is probably due to an error during a database operation: resolution will most likely require administrator intervention (e.g. check if DHCP process has sufficient privileges to update the database). It may also be triggered if a lease was manually removed from the database during RELEASE message processing.

DHCP4_RELEASE_FAIL_NO_LEASE client (client-id %1, hwaddr %2) tried to release address, %3, but there is no such lease.

This warning message is printed when client attempts to release a lease, but no such lease is known to the server.

DHCP4_RELEASE_FAIL_WRONG_CLIENT_ID client (client-id %2) tried to release address %1, but it belongs to client (client-id %3)

This warning message indicates that client tried to release an address that belongs to a different client. This should not happen in normal circumstances and may indicate a misconfiguration of the client. However, since the client releasing the address will stop using it anyway, there is a good chance that the situation will correct itself.

DHCP4_RELEASE_FAIL_WRONG_HWADDR client (client-id %2) tried to release address %1, but sent from a wrong hardware address (%3)

This warning message indicates that client tried to release an address that does belong to it, but the lease information was associated with a different hardware address. One possible reason for using different hardware address is that a cloned virtual machine was not updated and both clones use the same client-id.

DHCP4_RESPONSE_DATA responding with packet type %1, data is <%2>

A debug message listing the data returned to the client.

DHCP4_SERVER_FAILED server failed: %1

The DHCPv4 server has encountered a fatal error and is terminating. The reason for the failure is included in the message.

DHCP4_SESSION_FAIL failed to establish BIND 10 session (%1), running stand-alone

The server has failed to establish communication with the rest of BIND 10 and is running in stand-alone mode. (This behavior will change once the DHCPv4 server is properly integrated with the rest of BIND 10.)

DHCP4_SHUTDOWN server shutdown

The DHCPv4 server has terminated normally.

DHCP4_SHUTDOWN_REQUEST shutdown of server requested

This debug message indicates that a shutdown of the DHCPv4 server has been requested via a call to the 'shutdown' method of the core Dhcpv4Srv object.

DHCP4_SRV_CONSTRUCT_ERROR error creating Dhcpv4Srv object, reason: %1

This error message indicates that during startup, the construction of a core component within the DHCPv4 server (the Dhcpv4 server object) has failed. As a result, the server will exit. The reason for the failure is given within the message.

DHCP4_STANDALONE skipping message queue, running standalone

This is a debug message indicating that the DHCPv4 server is running in standalone mode, not connected to the message queue. Standalone mode is only useful during program development, and should not be used in a production environment.

DHCP4_STARTING server starting

This informational message indicates that the DHCPv4 server has processed any command-line switches and is starting.

DHCP4_START_INFO pid: %1, port: %2, verbose: %3, standalone: %4

This is a debug message issued during the DHCPv4 server startup. It lists some information about the parameters with which the server is running.

DHCP4_SUBNET_SELECTED the %1 subnet was selected for client assignment

This is a debug message noting the selection of a subnet to be used for address and option assignment. Subnet selection is one of the early steps in the processing of incoming client message.

DHCP4_SUBNET_SELECTION_FAILED failed to select a subnet for incoming packet, src: %1, type: %2

This warning message is output when a packet was received from a subnet for which the DHCPv4 server has not been configured. The most probable cause is a misconfiguration of the server.

DHCP4_UNRECOGNIZED_RCVD_PACKET_TYPE received message (transaction id %1) has unrecognized type %2 in option 53

This debug message indicates that the message type carried in DHCPv4 option 53 is unrecognized by the server. The valid message types are listed on the IANA website: http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml#message-type-53. The message will not be processed by the server.

DHCP4_UNSUPPORTED_RCVD_PACKET_TYPE received message (transaction id %1), having type %2 is not supported

This debug message indicates that the message type carried in DHCPv4 option 53 is valid but the message will not be processed by the server. This includes messages being normally sent by the server to the client, such as Offer, ACK, NAK etc.

DHCP6_ACTIVATE_INTERFACE activating interface %1

This message is printed when DHCPv6 server enabled an interface to be used to receive DHCPv6 traffic. IPv6 socket on this interface will be opened once Interface Manager starts up procedure of opening sockets.

DHCP6_CCSESSION_STARTED control channel session started on socket %1

A debug message issued during startup after the IPv6 DHCP server has successfully established a session with the BIND 10 control channel.

DHCP6_CCSESSION_STARTING starting control channel session, specfile: %1

This debug message is issued just before the IPv6 DHCP server attempts to establish a session with the BIND 10 control channel.

DHCP6_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1

This debug message informs that incoming packet has been assigned to specified class or classes. This is a norma

DHCP6_CLIENTID_MISSING mandatory client-id option is missing, message from %1 dropped

This error message indicates that the received message is being dropped because it does not include the mandatory client-id option necessary for address assignment. The most likely cause is a problem with the client.

DHCP6_COMMAND_RECEIVED received command %1, arguments: %2

A debug message listing the command (and possible arguments) received from the BIND 10 control system by the IPv6 DHCP server.

DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: %1

This is an informational message announcing the successful processing of a new configuration. it is output during server startup, and when an updated configuration is committed by the administrator. Additional information may be provided.

DHCP6_CONFIG_LOAD_FAIL failed to load configuration: %1

This critical error message indicates that the initial DHCPv6 configuration has failed. The server will start, but nothing will be served until the configuration has been corrected.

DHCP6_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1

This is an informational message reporting that the configuration has been extended to include the specified subnet.

DHCP6_CONFIG_OPTION_DUPLICATE multiple options with the code: %1 added to the subnet: %2

This warning message is issued on an attempt to configure multiple options with the same option code for the particular subnet. Adding multiple options is uncommon for DHCPv6, but it is not prohibited.

DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1

This is a debug message that is issued every time the server receives a configuration. That happens start up and also when a server configuration change is committed by the administrator.

DHCP6_CONFIG_UPDATE updated configuration received: %1

A debug message indicating that the IPv6 DHCP server has received an updated configuration from the BIND 10 configuration system.

DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2)

This informational message is printed every time the IPv6 DHCP server is started. It indicates what database backend type is being to store lease and other information.

DHCP6_DDNS_CREATE_ADD_NAME_CHANGE_REQUEST created name change request: %1

This debug message is logged when the new Name Change Request has been created to perform the DNS Update, which adds new RRs.

DHCP6_DDNS_CREATE_REMOVE_NAME_CHANGE_REQUEST created name change request: %1

This debug message is logged when the new Name Change Request has been created to perform the DNS Update, which removes RRs from the DNS.

DHCP6_DDNS_LEASE_ASSIGN_FQDN_CHANGE FQDN for the allocated lease: %1 has changed. New values: hostname = %2, reverse mapping = %3, forward mapping = %4

This debug message is logged when FQDN mapping for a particular lease has been changed by the recent Request message. This mapping will be changed in DNS.

DHCP6_DDNS_LEASE_RENEW_FQDN_CHANGE FQDN for the renewed lease: %1 has changed

New values: hostname = %2, reverse mapping = %3, forward mapping = %4 This debug message is logged when FQDN mapping for a particular lease has been changed by the recent Renew message. This mapping will be changed in DNS.

DHCP6_DDNS_RECEIVE_FQDN received DHCPv6 Client FQDN Option: %1

This debug message is logged when server has found the DHCPv6 Client FQDN Option sent by a client and started processing it.

DHCP6_DDNS_REMOVE_INVALID_HOSTNAME invalid FQDN: %1 for the lease: %2 when removing DNS bindings

This error message is issued when a lease being deleted contains an indication that the DNS Update has been performed for it, but the FQDN held in the lease database has invalid format and can't be transformed to the canonical on-wire format.

DHCP6_DDNS_REQUEST_SEND_FAILED failed sending a request to b10-dhcp-ddns, error: %1, ncr: %2

This error message indicates that IPv6 DHCP server failed to send a DDNS update reqeust to the DHCP-DDNS server. This is most likely a configuration or networking error.

DHCP6_DDNS_SEND_FQDN sending DHCPv6 Client FQDN Option to the client: %1

This debug message is logged when server includes an DHCPv6 Client FQDN Option in its response to the client.

DHCP6_DEACTIVATE_INTERFACE deactivate interface %1

This message is printed when DHCPv6 server disables an interface from being used to receive DHCPv6 traffic. Sockets on this interface will not be opened by the Interface Manager until interface is enabled.

DHCP6_EXTEND_LEASE_SUBNET_SELECTED the %1 subnet was selected for client extending its lease

This is a debug message informing that a given subnet was selected. It will be used for extending lifetime of the lease. This is one of the early steps in the processing of incoming client message.

DHCP6_EXTEND_LEASE_SUBNET_SELECT_FAILED failed to select a subnet for received %1: src=%2 type=%3

This warning message is output when a Renew or Rebind was received from a subnet for which the DHCPv6 server has not been configured. The cause is most likely due to a misconfiguration of the server. The packet processing will continue, but the response will only contain generic configuration parameters and no addresses or prefixes.

DHCP6_EXTEND_NA_UNKNOWN received unknown IA_NA from client (duid=%1, iaid=%2) in subnet %3

This warning message is printed when client attempts to extend the lease for the address (in the IA_NA option) but no such lease is known by the server. It typically means that client has attempted to use its lease past its lifetime: causes of this include a adjustment of the client's date/time setting or poor support on the client for sleep/recovery. A properly implemented client will recover from such a situation by restarting the lease allocation process after receiving a negative reply from the server.

An alternative cause could be that the server has lost its database recently and does not recognize its well-behaving clients. This is more probable if you see many such messages. Clients will recover from this, but they will most likely get a different IP addresses and experience a brief service interruption.

DHCP6_EXTEND_NA_UNKNOWN_SUBNET %1 message received from client on unknown subnet (duid=%2, iaid=%3)

A warning message indicating that a client is attempting to extend lease lifetime for the address, but the server does not have any information about the subnet this client belongs to. This may mean that faulty the mobile client changed its location and is trying to renew its old address (client is supposed to send confirm, not rewew in such cases, according to RFC3315) or the server configuration has changed and information about existing subnet was removed. Note that in a sense this is worse case of DHCP6_EXTEND_NA_UNKNOWN, as not only the lease is unknown, but also the subnet is. Depending on the reasons of this condition, it may or may not correct on its own.

DHCP6_EXTEND_PD_NO_BINDING client sent a %1 message to extend lifetimes of prefixes for an unknown binding: duid=%2, iaid=%3, subnet=%4

This warning message is logged when a client attempts to extend the lifetime of the prefix it is using, but the server was unable to find the binding to which this lease belongs. This error condition has different implications for the Renew and Rebind messages. For the former, the server will respond with NoBinding status code. For the latter, the server will discard the message.

DHCP6_EXTEND_PD_UNKNOWN_SUBNET %1 message received from client on unknown subnet (duid=%2, iaid=%3)

A warning message indicating that a client is attempting to extend lease lifetime for the prefix, but the server doesn't have any information about the subnet this client belongs to.

DHCP6_HOOKS_LIBS_RELOAD_FAIL reload of hooks libraries failed

A "libreload" command was issued to reload the hooks libraries but for some reason the reload failed. Other error messages issued from the hooks framework will indicate the nature of the problem.

DHCP6_HOOK_BUFFER_RCVD_SKIP received DHCPv6 buffer was dropped because a callout set the skip flag

This debug message is printed when a callout installed on buffer6_receive hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet.

DHCP6_HOOK_BUFFER_SEND_SKIP prepared DHCPv6 response was dropped because a callout set the skip flag

This debug message is printed when a callout installed on buffer6_send hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. Server completed all the processing (e.g. may have assigned, updated or released leases), but the response will not be send to the client.

DHCP6_HOOK_LEASE6_EXTEND_SKIP DHCPv6 lease lifetime was not extended because a callout set the skip flag for message %1

or lease6_rebind hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not extend the lifetime for a lease. If client requested renewal of multiples leases (by sending multiple IA options), the server will skip the renewal of the one in question and will proceed with other renewals as usual.

DHCP6_HOOK_LEASE6_RELEASE_NA_SKIP DHCPv6 address lease was not released because a callout set the skip flag

This debug message is printed when a callout installed on the lease6_release hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not release a lease. If a client requested the release of multiples leases (by sending multiple IA options), the server will retain this particular lease and proceed with other releases as usual.

DHCP6_HOOK_LEASE6_RELEASE_PD_SKIP DHCPv6 prefix lease was not released because a callout set the skip flag

This debug message is printed when a callout installed on lease6_release hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not release a lease. If client requested release of multiples leases (by sending multiple IA options), the server will retains this particular lease and will proceed with other renewals as usual.

DHCP6_HOOK_LEASE6_RENEW_SKIP DHCPv6 lease was not renewed because a callout set the skip flag

This debug message is printed when a callout installed on lease6_renew hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not renew a lease. If client requested renewal of multiples leases (by sending multiple IA options), the server will skip the renewal of the one in question and will proceed with other renewals as usual.

DHCP6_HOOK_PACKET_RCVD_SKIP received DHCPv6 packet was dropped because a callout set the skip flag

This debug message is printed when a callout installed on the pkt6_receive hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet.

DHCP6_HOOK_PACKET_SEND_SKIP prepared DHCPv6 response was not sent because a callout set the skip flag

This debug message is printed when a callout installed on the pkt6_send hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. This effectively means that the client will not get any response, even though the server processed client's request and acted on it (e.g. possibly allocated a lease).

DHCP6_HOOK_SUBNET6_SELECT_SKIP no subnet was selected because a callout set the skip flag

This debug message is printed when a callout installed on the subnet6_select hook point set the skip flag. For this particular hook point, the setting of the flag instructs the server not to choose a subnet, an action that severely limits further processing; the server will be only able to offer global options - no addresses or prefixes will be assigned.

DHCP6_LEASE_ADVERT address lease %1 advertised (client duid=%2, iaid=%3)

This debug message indicates that the server successfully advertised an address lease. It is up to the client to choose one server out of the advertised servers and continue allocation with that server. This is a normal behavior and indicates successful operation.

DHCP6_LEASE_ADVERT_FAIL failed to advertise an address lease for client duid=%1, iaid=%2

This message indicates that in response to a received SOLICIT, the server failed to advertise a non-temporary lease for a given client. There may be many reasons for such failure. Each failure is logged in a separate log entry.

DHCP6_LEASE_ALLOC address lease %1 has been allocated (client duid=%2, iaid=%3)

This debug message indicates that in response to a client's REQUEST message, the server successfully granted an non-temporary address lease. This is a normal behavior and indicates successful operation.

DHCP6_LEASE_ALLOC_FAIL failed to grant an address lease for client duid=%1, iaid=%2

This message indicates that in response to a received REQUEST, the server failed to grant a non-temporary address lease for the client. There may be many reasons for such failure. Each failure is logged in a separate log entry.

DHCP6_LEASE_NA_WITHOUT_DUID address lease for address %1 does not have a DUID

This error message indicates a database consistency problem. The lease database has an entry indicating that the given address is in use, but the lease does not contain any client identification. This is most likely due to a software error: please raise a bug report. As a temporary workaround, manually remove the lease entry from the database.

DHCP6_LEASE_PD_WITHOUT_DUID prefix lease for address %1 does not have a DUID

This error message indicates a database consistency failure. The lease database has an entry indicating that the given prefix is in use, but the lease does not contain any client identification. This is most likely due to a software error: please raise a bug report. As a temporary workaround, manually remove the lease entry from the database.

DHCP6_NAME_GEN_UPDATE_FAIL failed to update the lease using address %1, after generating FQDN for a client, reason: %2

This message indicates the failure when trying to update the lease and/or options in the server's response with the hostname generated by the server from the acquired address.

DHCP6_NOT_RUNNING IPv6 DHCP server is not running

A warning message is issued when an attempt is made to shut down the IPv6 DHCP server but it is not running.

DHCP6_NO_INTERFACES failed to detect any network interfaces

During startup the IPv6 DHCP server failed to detect any network interfaces and is therefore shutting down.

DHCP6_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic

This warning message is issued when current server configuration specifies no interfaces that server should listen on, or specified interfaces are not configured to receive the traffic.

DHCP6_OPEN_SOCKET opening sockets on port %1

A debug message issued during startup, this indicates that the IPv6 DHCP server is about to open sockets on the specified port.

DHCP6_OPEN_SOCKET_FAIL failed to create socket: %1

A warning message issued when IfaceMgr fails to open and bind a socket. The reason for the failure is appended as an argument of the log message.

DHCP6_PACKET_MISMATCH_SERVERID_DROP dropping packet %1 (transid=%2, interface=%3) having mismatched server identifier

A debug message noting that server has received message with server identifier option that not matching server identifier that server is using.

DHCP6_PACKET_PARSE_FAIL failed to parse incoming packet

The IPv6 DHCP server has received a packet that it is unable to interpret.

DHCP6_PACKET_PROCESS_FAIL processing of %1 message received from %2 failed: %3

This is a general catch-all message indicating that the processing of the specified packet type from the indicated address failed. The reason is given in the message. The server will not send a response but will instead ignore the packet.

DHCP6_PACKET_RECEIVED %1 packet received

A debug message noting that the server has received the specified type of packet. Note that a packet marked as UNKNOWN may well be a valid DHCP packet, just a type not expected by the server (e.g. it will report a received OFFER packet as UNKNOWN).

DHCP6_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1

The IPv6 DHCP server tried to receive a packet but an error occurred during this attempt. The reason for the error is included in the message.

DHCP6_PACKET_SEND_FAIL failed to send DHCPv6 packet: %1

This error is output if the IPv6 DHCP server fails to send an assembled DHCP message to a client. The reason for the error is included in the message.

DHCP6_PACK_FAIL failed to assemble response correctly

This error is output if the server failed to assemble the data to be returned to the client into a valid packet. The reason is most likely to be to a programming error: please raise a bug report.

DHCP6_PARSER_COMMIT_EXCEPTION parser failed to commit changes

On receipt of message containing details to a change of the IPv6 DHCP server configuration, a set of parsers were successfully created, but one of them failed to commit its changes due to a low-level system exception being raised. Additional messages may be output indicating the reason.

DHCP6_PARSER_COMMIT_FAIL parser failed to commit changes: %1

On receipt of message containing details to a change of the IPv6 DHCP server configuration, a set of parsers were successfully created, but one of them failed to commit its changes. The reason for the failure is given in the message.

DHCP6_PARSER_CREATED created parser for configuration element %1

A debug message output during a configuration update of the IPv6 DHCP server, notifying that the parser for the specified configuration element has been successfully created.

DHCP6_PARSER_EXCEPTION failed to create or run parser for configuration element %1

On receipt of message containing details to a change of its configuration, the IPv6 DHCP server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The message has been output in response to a non-BIND 10 exception being raised. Additional messages may give further information.

The most likely cause of this is that the specification file for the server (which details the allowable contents of the configuration) is not correct for this version of BIND 10. This may be the result of an interrupted installation of an update to BIND 10.

DHCP6_PARSER_FAIL failed to create or run parser for configuration element %1: %2

On receipt of message containing details to a change of its configuration, the IPv6 DHCP server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The reason for the failure is given in the message.

DHCP6_PD_LEASE_ADVERT prefix lease %1/%2 advertised (client duid=%3, iaid=%4)

This debug message indicates that the server successfully advertised a prefix lease. It is up to the client to choose one server out of the advertised servers and continue allocation with that server. This is a normal behavior and indicates successful operation.

DHCP6_PD_LEASE_ADVERT_FAIL failed to advertise a prefix lease for client duid=%1, iaid=%2

This message indicates that in response to a received SOLICIT, the server failed to advertise a prefix lease for the client. There may be many reasons for such failure. Each failure is logged in a separate log entry.

DHCP6_PD_LEASE_ALLOC prefix lease %1/%2 has been allocated (client duid=%3, iaid=%4)

This debug message indicates that in response to a client's REQUEST message, the server successfully granted a prefix delegation lease. This is a normal behavior and indicates successful operation.

DHCP6_PD_LEASE_ALLOC_FAIL failed to grant a prefix lease for client duid=%1, iaid=%2

This message indicates that the server failed to grant (in response to received REQUEST) a prefix lease for a given client. There may be many reasons for such failure. Each failure is logged in a separate log entry.

DHCP6_PROCESS_IA_NA_REQUEST server is processing IA_NA option (duid=%1, iaid=%2, hint=%3)

This is a debug message that indicates the processing of a received IA_NA option. It may optionally contain an address that may be used by the server as a hint for possible requested address.

DHCP6_PROCESS_IA_PD_REQUEST server is processing IA_PD option (duid=%1, iaid=%2, hint=%3)

This is a debug message that indicates a processing of received IA_PD option. It may optionally contain an prefix that may be used by the server as a hint for possible requested prefix.

DHCP6_QUERY_DATA received packet length %1, data length %2, data is %3

A debug message listing the data received from the client or relay.

DHCP6_RELEASE_MISSING_CLIENTID client (address=%1) sent RELEASE message without mandatory client-id

This warning message indicates that client sent RELEASE message without mandatory client-id option. This is most likely caused by a buggy client (or a relay that malformed forwarded message). This request will not be processed and a response with error status code will be sent back.

DHCP6_RELEASE_NA address %1 belonging to client duid=%2, iaid=%3 was released properly

This debug message indicates that an address was released properly. It is a normal operation during client shutdown.

DHCP6_RELEASE_NA_FAIL failed to remove address lease for address %1 for duid=%2, iaid=%3

This error message indicates that the software failed to remove an address lease from the lease database. It probably due to an error during a database operation: resolution will most likely require administrator intervention (e.g. check if DHCP process has sufficient privileges to update the database). It may also be triggered if a lease was manually removed from the database during RELEASE message processing.

DHCP6_RELEASE_NA_FAIL_WRONG_DUID client (duid=%1) tried to release address %2, but it belongs to another client (duid=%3)

This warning message indicates that a client tried to release an address that belongs to a different client. This should not happen in normal circumstances and may indicate a misconfiguration of the client. However, since the client releasing the address will stop using it anyway, there is a good chance that the situation will correct itself.

DHCP6_RELEASE_NA_FAIL_WRONG_IAID client (duid=%1) tried to release address %2, but it used wrong IAID (expected %3, but got %4)

This warning message indicates that client tried to release an address that does belong to it, but the address was expected to be in a different IA (identity association) container. This probably means that the client's support for multiple addresses is flawed.

DHCP6_RELEASE_PD prefix %1 belonging to client duid=%2, iaid=%3 was released properly

This debug message indicates that a prefix was released properly. It is a normal operation during client shutdown.

DHCP6_RELEASE_PD_FAIL failed to remove prefix lease for address %1 for duid=%2, iaid=%3

This error message indicates that the software failed to remove a prefix lease from the lease database. It probably due to an error during a database operation: resolution will most likely require administrator intervention (e.g. check if DHCP process has sufficient privileges to update the database). It may also be triggered if a lease was manually removed from the database during RELEASE message processing.

DHCP6_RELEASE_PD_FAIL_WRONG_DUID client (duid=%1) tried to release prefix %2, but it belongs to another client (duid=%3)

This warning message indicates that client tried to release a prefix that belongs to a different client. This should not happen in normal circumstances and may indicate a misconfiguration of the client. However, since the client releasing the prefix will stop using it anyway, there is a good chance that the situation will correct itself.

DHCP6_RELEASE_PD_FAIL_WRONG_IAID client (duid=%1) tried to release prefix %2, but it used wrong IAID (expected %3, but got %4)

This warning message indicates that client tried to release a prefix that does belong to it, but the address was expected to be in a different IA (identity association) container. This probably means that the client's support for multiple prefixes is flawed.

DHCP6_REQUIRED_OPTIONS_CHECK_FAIL %1 message received from %2 failed the following check: %3

This message indicates that received DHCPv6 packet is invalid. This may be due to a number of reasons, e.g. the mandatory client-id option is missing, the server-id forbidden in that particular type of message is present, there is more than one instance of client-id or server-id present, etc. The exact reason for rejecting the packet is included in the message.

DHCP6_RESPONSE_DATA responding with packet type %1 data is %2

A debug message listing the data returned to the client.

DHCP6_SERVERID_GENERATED server-id %1 has been generated and will be stored in %2

This informational messages indicates that the server was not able to read its server identifier (DUID) and has generated a new one. This server-id will be stored in a file and will be read and used during next restart. It is normal behavior when the server is started for the first time. If this message is printed every start, please check that the server have sufficient permission to write its server-id file and that the file is not corrupt.

Changing the server identifier in a production environment is not recommended as existing clients will not recognize the server and may go through a rebind phase. However, they should be able to recover without losing their leases.

DHCP6_SERVERID_LOADED server-id %1 has been loaded from file %2

This debug message indicates that the server loaded its server identifier. That value is sent in all server responses and clients use it to discriminate between servers. This is a part of normal startup or reconfiguration procedure.

DHCP6_SERVERID_WRITE_FAIL server was not able to write its ID to file %1

This warning message indicates that server was not able to write its server identifier (DUID) to a file. This likely indicates lack of write permission to a given file or directory. This is not cricital and the server will continue to operate, but server will generate different DUID during every start and clients will need to go through a rebind phase to recover.

DHCP6_SERVER_FAILED server failed: %1

The IPv6 DHCP server has encountered a fatal error and is terminating. The reason for the failure is included in the message.

DHCP6_SESSION_FAIL failed to establish BIND 10 session (%1), running stand-alone

The server has failed to establish communication with the rest of BIND 10 and is running in stand-alone mode. (This behavior will change once the IPv6 DHCP server is properly integrated with the rest of BIND 10.)

DHCP6_SHUTDOWN server shutdown

The IPv6 DHCP server has terminated normally.

DHCP6_SHUTDOWN_REQUEST shutdown of server requested

This debug message indicates that a shutdown of the IPv6 server has been requested via a call to the 'shutdown' method of the core Dhcpv6Srv object.

DHCP6_SOCKET_UNICAST server is about to open socket on address %1 on interface %2

This is a debug message that inform that a unicast socket will be opened.

DHCP6_SRV_CONSTRUCT_ERROR error creating Dhcpv6Srv object, reason: %1

This error message indicates that during startup, the construction of a core component within the IPv6 DHCP server (the Dhcpv6 server object) has failed. As a result, the server will exit. The reason for the failure is given within the message.

DHCP6_STANDALONE skipping message queue, running standalone

This is a debug message indicating that the IPv6 server is running in standalone mode, not connected to the message queue. Standalone mode is only useful during program development, and should not be used in a production environment.

DHCP6_STARTING server starting

This informational message indicates that the IPv6 DHCP server has processed any command-line switches and is starting.

DHCP6_START_INFO pid: %1, port: %2, verbose: %3, standalone: %4

This is a debug message issued during the IPv6 DHCP server startup. It lists some information about the parameters with which the server is running.

DHCP6_SUBNET_SELECTED the %1 subnet was selected for client assignment

This is a debug message informing that a given subnet was selected. It will be used for address and option assignment. This is one of the early steps in the processing of incoming client message.

DHCP6_SUBNET_SELECTION_FAILED failed to select a subnet for incoming packet, src=%1 type=%2

This warning message is output when a packet was received from a subnet for which the DHCPv6 server has not been configured. The cause is most likely due to a misconfiguration of the server. The packet processing will continue, but the response will only contain generic configuration parameters and no addresses or prefixes.

DHCP6_UNKNOWN_MSG_RECEIVED received unknown message (type %d) on interface %2

This debug message is printed when server receives a message of unknown type. That could either mean missing functionality or invalid or broken relay or client. The list of formally defined message types is available here: http://www.iana.org/assignments/dhcpv6-parameters.

DHCP6_UNKNOWN_RELEASE_NA received RELEASE from unknown client (IA_NA, duid=%1, iaid=%2)

This warning message is printed when client attempts to release an address lease, but no such lease is known by the server. See the explanation of the status code DHCP6_UNKNOWN_RENEW_NA for possible reasons for such behavior.

DHCP6_UNKNOWN_RELEASE_PD received RELEASE from unknown client (IA_PD, duid=%1, iaid=%2)

This warning message is printed when client attempts to release an prefix lease, but no such lease is known by the server. See the explanation of the status code DHCP6_UNKNOWN_RENEW_PD for possible reasons for such behavior.

DHCPSRV_ADDRESS4_ALLOC_ERROR error during attempt to allocate an IPv4 address: %1

An error occurred during an attempt to allocate an IPv4 address, the reason for the failure being contained in the message. The server will return a message to the client refusing a lease.

DHCPSRV_ADDRESS4_ALLOC_FAIL failed to allocate an IPv4 address after %1 attempt(s)

THE DHCP allocation engine gave up trying to allocate an IPv4 address after the specified number of attempts. This probably means that the address pool from which the allocation is being attempted is either empty, or very nearly empty. As a result, the client will have been refused a lease.

This message may indicate that your address pool is too small for the number of clients you are trying to service and should be expanded. Alternatively, if the you know that the number of concurrently active clients is less than the addresses you have available, you may want to consider reducing the lease lifetime. In this way, addresses allocated to clients that are no longer active on the network will become available available sooner.

DHCPSRV_ADDRESS6_ALLOC_ERROR error during attempt to allocate an IPv6 address: %1

An error occurred during an attempt to allocate an IPv6 address, the reason for the failure being contained in the message. The server will return a message to the client refusing a lease.

DHCPSRV_ADDRESS6_ALLOC_FAIL failed to allocate an IPv6 address after %1 attempt(s)

The DHCP allocation engine gave up trying to allocate an IPv6 address after the specified number of attempts. This probably means that the address pool from which the allocation is being attempted is either empty, or very nearly empty. As a result, the client will have been refused a lease.

This message may indicate that your address pool is too small for the number of clients you are trying to service and should be expanded. Alternatively, if the you know that the number of concurrently active clients is less than the addresses you have available, you may want to consider reducing the lease lifetime. In this way, addresses allocated to clients that are no longer active on the network will become available available sooner.

DHCPSRV_CFGMGR_ADD_IFACE adding listening interface %1

A debug message issued when new interface is being added to the collection of interfaces on which server listens to DHCP messages.

DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet %1

A debug message reported when the DHCP configuration manager is adding the specified IPv4 subnet to its database.

DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet %1

A debug message reported when the DHCP configuration manager is adding the specified IPv6 subnet to its database.

DHCPSRV_CFGMGR_ALL_IFACES_ACTIVE enabling listening on all interfaces

A debug message issued when server is being configured to listen on all interfaces.

DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to: %1

A debug message issued when the server's DHCP-DDNS settings are changed.

DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces

A debug message issued when configuration manager clears the internal list of active interfaces. This doesn't prevent the server from listening to the DHCP traffic through open sockets, but will rather be used by Interface Manager to select active interfaces when sockets are re-opened.

DHCPSRV_CFGMGR_DELETE_SUBNET4 deleting all IPv4 subnets

A debug message noting that the DHCP configuration manager has deleted all IPv4 subnets in its database.

DHCPSRV_CFGMGR_DELETE_SUBNET6 deleting all IPv6 subnets

A debug message noting that the DHCP configuration manager has deleted all IPv6 subnets in its database.

DHCPSRV_CFGMGR_NO_SUBNET4 no suitable subnet is defined for address hint %1

This debug message is output when the DHCP configuration manager has received a request for an IPv4 subnet for the specified address, but no such subnet exists.

DHCPSRV_CFGMGR_NO_SUBNET6 no suitable subnet is defined for address hint %1

This debug message is output when the DHCP configuration manager has received a request for an IPv6 subnet for the specified address, but no such subnet exists.

DHCPSRV_CFGMGR_ONLY_SUBNET4 retrieved subnet %1 for address hint %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv4 subnet when given the address hint specified because it is the only subnet defined.

DHCPSRV_CFGMGR_ONLY_SUBNET6 retrieved subnet %1 for address hint %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv6 subnet when given the address hint specified because it is the only subnet defined.

DHCPSRV_CFGMGR_SUBNET4 retrieved subnet %1 for address hint %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv4 subnet when given the address hint specified as the address is within the subnet.

DHCPSRV_CFGMGR_SUBNET4_RELAY selected subnet %1, because of matching relay addr %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv4 subnet, because detected relay agent address matches value specified for this subnet.

DHCPSRV_CFGMGR_SUBNET6 retrieved subnet %1 for address hint %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv6 subnet when given the address hint specified as the address is within the subnet.

DHCPSRV_CFGMGR_SUBNET6_IFACE selected subnet %1 for packet received over interface %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv6 subnet for a packet received over given interface. This particular subnet was selected, because it was specified as being directly reachable over given interface. (see 'interface' parameter in the subnet6 definition).

DHCPSRV_CFGMGR_SUBNET6_IFACE_ID selected subnet %1 (interface-id match) for incoming packet

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv6 subnet for a received packet. This particular subnet was selected, because value of interface-id option matched what was configured in server's interface-id option for that selected subnet6. (see 'interface-id' parameter in the subnet6 definition).

DHCPSRV_CFGMGR_SUBNET6_RELAY selected subnet %1, because of matching relay addr %2

This is a debug message reporting that the DHCP configuration manager has returned the specified IPv6 subnet, because detected relay agent address matches value specified for this subnet.

DHCPSRV_CLOSE_DB closing currently open %1 database

This is a debug message, issued when the DHCP server closes the currently open lease database. It is issued at program shutdown and whenever the database access parameters are changed: in the latter case, the server closes the currently open database, and opens a database using the new parameters.

DHCPSRV_DHCP_DDNS_ERROR_EXCEPTION error handler for DHCP_DDNS IO generated an expected exception: %1

This is an error message that occurs when an attempt to send a request to b10-dhcp-ddns fails there registered error handler threw an uncaught exception. This is a programmatic error which should not occur. By convention, the error handler should not propagate exceptions. Please report this error.

DHCPSRV_DHCP_DDNS_HANDLER_NULL error handler for DHCP_DDNS IO is not set.

This is an error message that occurs when an attempt to send a request to b10-dhcp-ddns fails and there is no registered error handler. This is a programmatic error which should never occur and should be reported.

DHCPSRV_DHCP_DDNS_NCR_REJECTED NameChangeRequest rejected by the sender: %1, ncr: %2

This is an error message indicating that NameChangeSender used to deliver DDNS update requests to b10-dhcp-ddns rejected the request. This most likely cause is the sender's queue has reached maximum capacity. This would imply that requests are being generated faster than they can be delivered.

DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to b10-dhcp-ddns: %1

A debug message issued when a NameChangeRequest has been successfully sent to b10-dhcp-ddns.

DHCPSRV_DHCP_DDNS_SENDER_STARTED NameChangeRequest sender has been started: %1

A informational message issued when a communications with b10-dhcp-ddns has been successfully started.

DHCPSRV_DHCP_DDNS_SENDER_STOPPED NameChangeRequest sender has been stopped.

A informational message issued when a communications with b10-dhcp-ddns has been stopped. This normally occurs during reconfiguration and as part of normal shutdown. It may occur if b10-dhcp-ddns communications breakdown.

DHCPSRV_DHCP_DDNS_SUSPEND_UPDATES DHCP_DDNS updates are being suspended.

This is a warning message indicating the DHCP_DDNS updates have been turned off. This should only occur if IO errors communicating with b10-dhcp-ddns have been experienced. Any such errors should have preceding entries in the log with details. No further attempts to communicate with b10-dhcp-ddns will be made without intervention.

DHCPSRV_HOOK_LEASE4_RENEW_SKIP DHCPv4 lease was not renewed because a callout set the skip flag.

This debug message is printed when a callout installed on lease4_renew hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not renew a lease. The server will use existing lease as it is, without extending its lifetime.

DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.

This debug message is printed when a callout installed on lease4_select hook point sets the skip flag. It means that the server was told that no lease4 should be assigned. The server will not put that lease in its database and the client will get a NAK packet.

DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.

This debug message is printed when a callout installed on lease6_select hook point sets the skip flag. It means that the server was told that no lease6 should be assigned. The server will not put that lease in its database and the client will get a NoAddrsAvail for that IA_NA option.

DHCPSRV_INVALID_ACCESS invalid database access string: %1

This is logged when an attempt has been made to parse a database access string and the attempt ended in error. The access string in question - which should be of the form 'keyword=value keyword=value...' is included in the message.

DHCPSRV_MEMFILE_ADD_ADDR4 adding IPv4 lease with address %1

A debug message issued when the server is about to add an IPv4 lease with the specified address to the memory file backend database.

DHCPSRV_MEMFILE_ADD_ADDR6 adding IPv6 lease with address %1

A debug message issued when the server is about to add an IPv6 lease with the specified address to the memory file backend database.

DHCPSRV_MEMFILE_COMMIT committing to memory file database

The code has issued a commit call. For the memory file database, this is a no-op.

DHCPSRV_MEMFILE_DB opening memory file lease database: %1

This informational message is logged when a DHCP server (either V4 or V6) is about to open a memory file lease database. The parameters of the connection including database name and username needed to access it (but not the password if any) are logged.

DHCPSRV_MEMFILE_DELETE_ADDR deleting lease for address %1

A debug message issued when the server is attempting to delete a lease for the specified address from the memory file database for the specified address.

DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1

A debug message issued when the server is attempting to obtain an IPv4 lease from the memory file database for the specified address.

DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1

A debug message issued when the server is attempting to obtain an IPv6 lease from the memory file database for the specified address.

DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the memory file database for a client with the specified client identification.

DHCPSRV_MEMFILE_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3

A debug message issued when the server is attempting to obtain an IPv4 lease from the memory file database for a client with the specified client ID, hardware address and subnet ID.

DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the memory file database for a client with the specified hardware address.

DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2

A debug message issued when the server is attempting to obtain a set of IPv6 lease from the memory file database for a client with the specified IAID (Identity Association ID) and DUID (DHCP Unique Identifier).

DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2 and DUID %3

A debug message issued when the server is attempting to obtain an IPv6 lease from the memory file database for a client with the specified IAID (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).

DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the memory file database for a client with the specified subnet ID and client ID.

DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the memory file database for a client with the specified subnet ID and hardware address.

DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information

A debug message issued when the server is about to obtain schema version information from the memory file database.

DHCPSRV_MEMFILE_LEASES_RELOAD4 reloading leases from %1

An info message issued when server is about to start reading DHCPv4 leases from the lease file. All leases currently held in the memory will be replaced by those read from the file.

DHCPSRV_MEMFILE_LEASES_RELOAD6 reloading leases from %1

An info message issued when server is about to start reading DHCPv6 leases from the lease file. All leases currently held in the memory will be replaced by those read from the file.

DHCPSRV_MEMFILE_LEASE_LOAD4 loading lease %1

A debug message issued when DHCPv4 lease is being loaded from the file to memory.

DHCPSRV_MEMFILE_LEASE_LOAD6 loading lease %1

A debug message issued when DHCPv6 lease is being loaded from the file to memory.

DHCPSRV_MEMFILE_NO_STORAGE running in non-persistent mode, leases will be lost after restart

A warning message issued when writes of leases to disk have been disabled in the configuration. This mode is useful for some kinds of performance testing but should not be enabled in normal circumstances. Non-persistence mode is enabled when 'persist4=no persist6=no' parameters are specified in the database access string.

DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database

The code has issued a rollback call. For the memory file database, this is a no-op.

DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1

A debug message issued when the server is attempting to update IPv4 lease from the memory file database for the specified address.

DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1

A debug message issued when the server is attempting to update IPv6 lease from the memory file database for the specified address.

DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %1

A debug message issued when the server is about to add an IPv4 lease with the specified address to the MySQL backend database.

DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2

A debug message issued when the server is about to add an IPv6 lease with the specified address to the MySQL backend database.

DHCPSRV_MYSQL_COMMIT committing to MySQL database

The code has issued a commit call. All outstanding transactions will be committed to the database. Note that depending on the MySQL settings, the committal may not include a write to disk.

DHCPSRV_MYSQL_DB opening MySQL lease database: %1

This informational message is logged when a DHCP server (either V4 or V6) is about to open a MySQL lease database. The parameters of the connection including database name and username needed to access it (but not the password if any) are logged.

DHCPSRV_MYSQL_DELETE_ADDR deleting lease for address %1

A debug message issued when the server is attempting to delete a lease for the specified address from the MySQL database for the specified address.

DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %1

A debug message issued when the server is attempting to obtain an IPv4 lease from the MySQL database for the specified address.

DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2

A debug message issued when the server is attempting to obtain an IPv6 lease from the MySQL database for the specified address.

DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the MySQL database for a client with the specified client identification.

DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the MySQL database for a client with the specified hardware address.

DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3

A debug message issued when the server is attempting to obtain a set of IPv6 lease from the MySQL database for a client with the specified IAID (Identity Association ID) and DUID (DHCP Unique Identifier).

DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4

A debug message issued when the server is attempting to obtain an IPv6 lease from the MySQL database for a client with the specified IAID (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).

DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the MySQL database for a client with the specified subnet ID and client ID.

DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the MySQL database for a client with the specified subnet ID and hardware address.

DHCPSRV_MYSQL_GET_VERSION obtaining schema version information

A debug message issued when the server is about to obtain schema version information from the MySQL database.

DHCPSRV_MYSQL_ROLLBACK rolling back MySQL database

The code has issued a rollback call. All outstanding transaction will be rolled back and not committed to the database.

DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1

A debug message issued when the server is attempting to update IPv4 lease from the MySQL database for the specified address.

DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2

A debug message issued when the server is attempting to update IPv6 lease from the MySQL database for the specified address.

DHCPSRV_NOTYPE_DB no 'type' keyword to determine database backend: %1

This is an error message, logged when an attempt has been made to access a database backend, but where no 'type' keyword has been included in the access string. The access string (less any passwords) is included in the message.

DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %1

A debug message issued when the server is about to add an IPv4 lease with the specified address to the PostgreSQL backend database.

DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1

A debug message issued when the server is about to add an IPv6 lease with the specified address to the PostgreSQL backend database.

DHCPSRV_PGSQL_COMMIT committing to MySQL database

The code has issued a commit call. All outstanding transactions will be committed to the database. Note that depending on the PostgreSQL settings, the committal may not include a write to disk.

DHCPSRV_PGSQL_DB opening PostgreSQL lease database: %1

This informational message is logged when a DHCP server (either V4 or V6) is about to open a PostgreSQL lease database. The parameters of the connection including database name and username needed to access it (but not the password if any) are logged.

DHCPSRV_PGSQL_DEALLOC_ERROR An error occured deallocating SQL statements while closing the PostgreSQL lease database: %1

This is an error message issued when a DHCP server (either V4 or V6) experienced and error freeing database SQL resources as part of closing its connection to the Postgresql database. The connection is closed as part of normal server shutdown. This error is most likely a programmatic issue that is highly unlikely to occur or negatively impact server operation.

DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1

A debug message issued when the server is attempting to delete a lease for the specified address from the PostgreSQL database for the specified address.

DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %1

A debug message issued when the server is attempting to obtain an IPv4 lease from the PostgreSQL database for the specified address.

DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)

A debug message issued when the server is attempting to obtain an IPv6 lease from the PostgreSQL database for the specified address.

DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the PostgreSQL database for a client with the specified client identification.

DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1

A debug message issued when the server is attempting to obtain a set of IPv4 leases from the PostgreSQL database for a client with the specified hardware address.

DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3

A debug message issued when the server is attempting to obtain a set of IPv6 lease from the PostgreSQL database for a client with the specified IAID (Identity Association ID) and DUID (DHCP Unique Identifier).

DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4

A debug message issued when the server is attempting to obtain an IPv6 lease from the PostgreSQL database for a client with the specified IAID (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).

DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the PostgreSQL database for a client with the specified subnet ID and client ID.

DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2

A debug message issued when the server is attempting to obtain an IPv4 lease from the PostgreSQL database for a client with the specified subnet ID and hardware address.

DHCPSRV_PGSQL_GET_VERSION obtaining schema version information

A debug message issued when the server is about to obtain schema version information from the PostgreSQL database.

DHCPSRV_PGSQL_ROLLBACK rolling back PostgreSQL database

The code has issued a rollback call. All outstanding transaction will be rolled back and not committed to the database.

DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1

A debug message issued when the server is attempting to update IPv4 lease from the PostgreSQL database for the specified address.

DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1

A debug message issued when the server is attempting to update IPv6 lease from the PostgreSQL database for the specified address.

DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'

The parameters for access the lease database were passed to the server through the named configuration parameter, but the code was expecting them to be passed via the parameter named "lease-database". If the database opens successfully, there is no impact on server operation. However, as this does indicate an error in the source code, please submit a bug report.

DHCPSRV_UNKNOWN_DB unknown database type: %1

The database access string specified a database type (given in the message) that is unknown to the software. This is a configuration error.

DHCP_DDNS_ADD_FAILED DHCP_DDNS Transaction outcome: %1

This is an error message issued after DHCP_DDNS attempts to submit DNS mapping entry additions have failed. The precise reason for the failure should be documented in preceding log entries.

DHCP_DDNS_ADD_SUCCEEDED DHCP_DDNS successfully added the DNS mapping addition for this request: %1

This is an informational message issued after DHCP_DDNS has submitted DNS mapping additions which were received and accepted by an appropriate DNS server.

DHCP_DDNS_AT_MAX_TRANSACTIONS application has %1 queued requests but has reached maximum number of %2 concurrent transactions

This is a debug message that indicates that the application has DHCP_DDNS requests in the queue but is working as many concurrent requests as allowed.

DHCP_DDNS_CLEARED_FOR_SHUTDOWN application has met shutdown criteria for shutdown type: %1

This is an informational message issued when the application has been instructed to shutdown and has met the required criteria to exit.

DHCP_DDNS_COMMAND command directive received, command: %1 - args: %2

This is a debug message issued when the Dhcp-Ddns application command method has been invoked.

DHCP_DDNS_CONFIGURE configuration update received: %1

This is a debug message issued when the Dhcp-Ddns application configure method has been invoked.

DHCP_DDNS_FAILED application experienced a fatal error: %1

This is a debug message issued when the Dhcp-Ddns application encounters an unrecoverable error from within the event loop.

DHCP_DDNS_FORWARD_ADD_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while adding a forward address mapping for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was adding a forward address mapping. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_FORWARD_ADD_BUILD_FAILURE DNS udpate message to add a forward DNS entry could not be constructed for this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting a forward address addition. This is due to invalid data contained in the NameChangeRequest. The request will be aborted. This is most likely a configuration issue.

DHCP_DDNS_FORWARD_ADD_IO_ERROR DHCP_DDNS encountered an IO error sending a forward mapping add for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a forward address update. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_ADD_REJECTED DNS Server, %1, rejected a DNS update request to add the address mapping for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_FORWARD_ADD_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while adding forward address mapping for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to add a forward address mapping, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_REMOVE_ADDRS_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while removing a forward address mapping for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was removing a forward address mapping. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_FORWARD_REMOVE_ADDRS_BUILD_FAILURE DNS udpate message to remove a forward DNS Address entry could not be constructed for this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting a forward address (A or AAAA) removal. This is due to invalid data contained in the NameChangeRequest. The request will be aborted. This is most likely a configuration issue.

DHCP_DDNS_FORWARD_REMOVE_ADDRS_IO_ERROR DHCP_DDNS encountered an IO error sending a forward mapping address removal for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a forward address remove. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_REMOVE_ADDRS_REJECTED DNS Server, %1, rejected a DNS update request to remove the forward address mapping for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_FORWARD_REMOVE_ADDRS_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while removing forward address mapping for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to remove a forward address mapping, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_REMOVE_RRS_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while removing forward RRs for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was removing forward RRs. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_FORWARD_REMOVE_RRS_BUILD_FAILURE DNS udpate message to remove forward DNS RR entries could not be constructed for this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting forward RR (DHCID RR) removal. This is due to invalid data contained in the NameChangeRequest. The request will be aborted.This is most likely a configuration issue.

DHCP_DDNS_FORWARD_REMOVE_RRS_IO_ERROR DHCP_DDNS encountered an IO error sending a forward RR removal for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a forward RR remove. The application will retry against the same server.

DHCP_DDNS_FORWARD_REMOVE_RRS_REJECTED DNS Server, %1, rejected a DNS update request to remove forward RR entries for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_FORWARD_REMOVE_RRS_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while removing forward RRs for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to remove forward RRs mapping, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_REPLACE_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while replacing forward address mapping for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was replacing a forward address mapping. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_FORWARD_REPLACE_BUILD_FAILURE DNS update message to replace a forward DNS entry could not be constructed from this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting a forward address replacement. This is due to invalid data contained in the NameChangeRequest. The request will be aborted. This is most likely a configuration issue.

DHCP_DDNS_FORWARD_REPLACE_IO_ERROR DHCP_DDNS encountered an IO error sending a forward mapping replace for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a forward address update. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FORWARD_REPLACE_REJECTED DNS Server, %1, rejected a DNS update request to replace the address mapping for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_FORWARD_REPLACE_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while replacing forward address mapping for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to replace a forward address mapping, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_FWD_REQUEST_IGNORED Forward updates are disabled, the forward portion of request will be ignored: %1

This is a debug message issued when forward DNS updates are disabled and DHCP_DDNS receives an update request containing a forward DNS update. The forward update will not performed.

DHCP_DDNS_INVALID_NCR application received an invalid DNS update request: %1

This is an error message that indicates that an invalid request to update a DNS entry was received by the application. Either the format or the content of the request is incorrect. The request will be ignored.

DHCP_DDNS_INVALID_RESPONSE received response to DNS Update message is malformed: %1

This is a debug message issued when the DHCP-DDNS application encountered an error while decoding a response to DNS Update message. Typically, this error will be encountered when a response message is malformed.

DHCP_DDNS_NCR_FLUSH_IO_ERROR DHCP-DDNS Last send before stopping did not complete successfully: %1

This is an error message that indicates the DHCP-DDNS client was unable to complete the last send prior to exiting send mode. This is a programmatic error, highly unlikely to occur, and should not impair the application's ability to process requests.

DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR application encountered an error while closing the listener used to receive NameChangeRequests : %1

This is an error message that indicates the application was unable to close the listener connection used to receive NameChangeRequests. Closure may occur during the course of error recovery or during normal shutdown procedure. In either case the error is unlikely to impair the application's ability to process requests but it should be reported for analysis.

DHCP_DDNS_NCR_RECV_NEXT_ERROR application could not initiate the next read following a request receive.

This is a error message indicating that NameChangeRequest listener could not start another read after receiving a request. While possible, this is highly unlikely and is probably a programmatic error. The application should recover on its own.

DHCP_DDNS_NCR_SEND_CLOSE_ERROR DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests: %1

This is an error message that indicates the DHCP-DDNS client was unable to close the connection used to send NameChangeRequests. Closure may occur during the course of error recovery or during normal shutdown procedure. In either case the error is unlikely to impair the client's ability to send requests but it should be reported for analysis.

DHCP_DDNS_NCR_SEND_NEXT_ERROR DHCP-DDNS client could not initiate the next request send following send completion: %1

This is a error message indicating that NameChangeRequest sender could not start another send after completing the send of the previous request. While possible, this is highly unlikely and is probably a programmatic error. The application should recover on its own.

DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UDP watch socket failed to clear: %1

This is an error message that indicates the application was unable to reset the UDP NCR sender ready status after completing a send. This is programmatic error that should be reported. The application may or may not continue to operate correctly.

DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests: %1

This is an informational message indicating that the listening over a UDP socket for DNS update requests has been canceled. This is a normal part of suspending listening operations.

DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1

This is an error message indicating that an IO error occurred while listening over a UDP socket for DNS update requests. This could indicate a network connectivity or system resource issue.

DHCP_DDNS_NCR_UDP_SEND_CANCELED UDP socket send was canceled while sending a DNS Update request to DHCP_DDNS: %1

This is an informational message indicating that sending requests via UDP socket to DHCP_DDNS has been interrupted. This is a normal part of suspending send operations.

DHCP_DDNS_NCR_UDP_SEND_ERROR UDP socket send error while sending a DNS Update request: %1

This is an error message indicating that an IO error occurred while sending a DNS update request to DHCP_DDNS over a UDP socket. This could indicate a network connectivity or system resource issue.

DHCP_DDNS_NOT_ON_LOOPBACK the DHCP-DDNS server has been configured to listen on %1 which is not the local loopback. This is an insecure configuration supported for testing purposes only

This is a warning message issued when the DHCP-DDNS server is configured to listen at an address other than the loopback address (127.0.0.1 or ::1). It is possible for a malicious attacker to send bogus NameChangeRequests to it and change entries in the DNS. For this reason, addresses other than the IPv4 or IPv6 loopback addresses should only be used for testing purposes. A future version of Kea will implement authentication to guard against such attacks.

DHCP_DDNS_NO_ELIGIBLE_JOBS although there are queued requests, there are pending transactions for each Queue count: %1 Transaction count: %2

This is a debug message issued when all of the queued requests represent clients for which there is a an update already in progress. This may occur under normal operations but should be temporary situation.

DHCP_DDNS_NO_FWD_MATCH_ERROR the configured list of forward DDNS domains does not contain a match for: %1 The request has been discarded.

This is an error message that indicates that DHCP_DDNS received a request to update a the forward DNS information for the given FQDN but for which there are no configured DDNS domains in the DHCP_DDNS configuration. Either the DHCP_DDNS configuration needs to be updated or the source of the FQDN itself should be investigated.

DHCP_DDNS_NO_MATCH No DNS servers match FQDN %1

This is warning message issued when there are no domains in the configuration which match the cited fully qualified domain name (FQDN). The DNS Update request for the FQDN cannot be processed.

DHCP_DDNS_NO_REV_MATCH_ERROR the configured list of reverse DDNS domains does not contain a match for: %1 The request has been discarded.

This is an error message that indicates that DHCP_DDNS received a request to update a the reverse DNS information for the given FQDN but for which there are no configured DDNS domains in the DHCP_DDNS configuration. Either the DHCP_DDNS configuration needs to be updated or the source of the FQDN itself should be investigated.

DHCP_DDNS_PROCESS_INIT application init invoked

This is a debug message issued when the Dhcp-Ddns application enters its init method.

DHCP_DDNS_QUEUE_MGR_QUEUE_FULL application request queue has reached maximum number of entries %1

This an error message indicating that DHCP-DDNS is receiving DNS update requests faster than they can be processed. This may mean the maximum queue needs to be increased, the DHCP-DDNS clients are simply generating too many requests too quickly, or perhaps upstream DNS servers are experiencing load issues.

DHCP_DDNS_QUEUE_MGR_RECONFIGURING application is reconfiguring the queue manager

This is an informational message indicating that DHCP_DDNS is reconfiguring the queue manager as part of normal startup or in response to a new configuration.

DHCP_DDNS_QUEUE_MGR_RECOVERING application is attempting to recover from a queue manager IO error

This is an informational message indicating that DHCP_DDNS is attempting to restart the queue manager after it suffered an IO error while receiving requests.

DHCP_DDNS_QUEUE_MGR_RECV_ERROR application's queue manager was notified of a request receive error by its listener.

This is an error message indicating that the NameChangeRequest listener used by DHCP-DDNS to receive requests encountered a IO error. There should be corresponding log messages from the listener layer with more details. This may indicate a network connectivity or system resource issue.

DHCP_DDNS_QUEUE_MGR_RESUME_ERROR application could not restart the queue manager, reason: %1

This is an error message indicating that DHCP_DDNS's Queue Manager could not be restarted after stopping due to a full receive queue. This means that the application cannot receive requests. This is most likely due to DHCP_DDNS configuration parameters referring to resources such as an IP address or port, that is no longer unavailable. DHCP_DDNS will attempt to restart the queue manager if given a new configuration.

DHCP_DDNS_QUEUE_MGR_RESUMING application is resuming listening for requests now that the request queue size has reached %1 of a maximum %2 allowed

This is an informational message indicating that DHCP_DDNS, which had stopped accepting new requests, has processed enough entries from the receive queue to resume accepting requests.

DHCP_DDNS_QUEUE_MGR_STARTED application's queue manager has begun listening for requests.

This is a debug message indicating that DHCP_DDNS's Queue Manager has successfully started and is now listening for NameChangeRequests.

DHCP_DDNS_QUEUE_MGR_START_ERROR application could not start the queue manager, reason: %1

This is an error message indicating that DHCP_DDNS's Queue Manager could not be started. This means that the application cannot receive requests. This is most likely due to DHCP_DDNS configuration parameters referring to resources such as an IP address or port, that are unavailable. DHCP_DDNS will attempt to restart the queue manager if given a new configuration.

DHCP_DDNS_QUEUE_MGR_STOPPED application's queue manager has stopped listening for requests.

This is an informational message indicating that DHCP_DDNS's Queue Manager has stopped listening for NameChangeRequests. This may be because of normal event such as reconfiguration or as a result of an error. There should be log messages preceding this one to indicate why it has stopped.

DHCP_DDNS_QUEUE_MGR_STOPPING application is stopping the queue manager for %1

This is an informational message indicating that DHCP_DDNS is stopping the queue manager either to reconfigure it or as part of application shutdown.

DHCP_DDNS_QUEUE_MGR_STOP_ERROR application encountered an error stopping the queue manager: %1

This is an error message indicating that DHCP_DDNS encountered an error while trying to stop the queue manager. This error is unlikely to occur or to impair the application's ability to function but it should be reported for analysis.

DHCP_DDNS_QUEUE_MGR_UNEXPECTED_HANDLER_ERROR application's queue manager request receive handler experienced an unexpected exception %1:

This is an error message indicating that an unexpected error occurred within the DHCP_DDNS's Queue Manager request receive completion handler. This is most likely a programmatic issue that should be reported. The application may recover on its own.

DHCP_DDNS_QUEUE_MGR_UNEXPECTED_STOP application's queue manager receive was

aborted unexpectedly while queue manager state is: %1 This is an error message indicating that DHCP_DDNS's Queue Manager request receive was unexpected interrupted. Normally, the read is receive is only interrupted as a normal part of stopping the queue manager. This is most likely a programmatic issue that should be reported.

DHCP_DDNS_REMOVE_FAILED DHCP_DDNS Transaction outcome: %1

This is an error message issued after DHCP_DDNS attempts to submit DNS mapping entry removals have failed. The precise reason for the failure should be documented in preceding log entries.

DHCP_DDNS_REMOVE_SUCCEEDED DHCP_DDNS successfully removed the DNS mapping addition for this request: %1

This is an informational message issued after DHCP_DDNS has submitted DNS mapping removals which were received and accepted by an appropriate DNS server.

DHCP_DDNS_REQUEST_DROPPED Request contains no enabled update requests and will be dropped: %1

This is a debug message issued when DHCP_DDNS receives a request which does not contain updates in a direction that is enabled. In other words, if only forward updates are enabled and request is recevied that asks only for reverse updates then the request is dropped.

DHCP_DDNS_REVERSE_REMOVE_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while removing reverse address mapping for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was removing a reverse address mapping. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_REVERSE_REMOVE_BUILD_FAILURE DNS update message to remove a reverse DNS entry could not be constructed from this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting a reverse PTR removal. This is due to invalid data contained in the NameChangeRequest. The request will be aborted. This is most likely a configuration issue.

DHCP_DDNS_REVERSE_REMOVE_IO_ERROR DHCP_DDNS encountered an IO error sending a reverse mapping remove for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a reverse address update. The application will retry against the same server or others as appropriate.

DHCP_DDNS_REVERSE_REMOVE_REJECTED DNS Server, %1, rejected a DNS update request to remove the reverse mapping for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_REVERSE_REMOVE_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while removing reverse address mapping for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to remove a reverse address, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_REVERSE_REPLACE_BAD_DNSCLIENT_STATUS DHCP_DDNS received an unknown DNSClient status: %1, while replacing reverse address mapping for FQDN %2 to DNS server %3

This is an error message issued when DNSClient returns an unrecognized status while DHCP_DDNS was replacing a reverse address mapping. The request will be aborted. This is most likely a programmatic issue and should be reported.

DHCP_DDNS_REVERSE_REPLACE_BUILD_FAILURE DNS update message to replace a reverse DNS entry could not be constructed from this request: %1, reason: %2

This is an error message issued when an error occurs attempting to construct the server bound packet requesting a reverse PTR replacement. This is due to invalid data contained in the NameChangeRequest. The request will be aborted. This is most likely a configuration issue.

DHCP_DDNS_REVERSE_REPLACE_IO_ERROR DHCP_DDNS encountered an IO error sending a reverse mapping replacement for FQDN %1 to DNS server %2

This is an error message issued when a communication error occurs while DHCP_DDNS is carrying out a reverse address update. The application will retry against the same server or others as appropriate.

DHCP_DDNS_REVERSE_REPLACE_REJECTED DNS Server, %1, rejected a DNS update request to replace the reverse mapping for FQDN, %2, with an RCODE: %3

This is an error message issued when an update was rejected by the DNS server it was sent to for the reason given by the RCODE. The rcode values are defined in RFC 2136.

DHCP_DDNS_REVERSE_REPLACE_RESP_CORRUPT DHCP_DDNS received a corrupt response from the DNS server, %1, while replacing reverse address mapping for FQDN, %2

This is an error message issued when the response received by DHCP_DDNS, to a update request to replace a reverse address, is mangled or malformed. The application will retry against the same server or others as appropriate.

DHCP_DDNS_REV_REQUEST_IGNORED Reverse updates are disabled, the reverse portion of request will be ignored: %1

This is a debug message issued when reverse DNS updates are disabled and DHCP_DDNS receives an update request containing a reverse DNS update. The reverse update will not performed.

DHCP_DDNS_RUN_ENTER application has entered the event loop

This is a debug message issued when the Dhcp-Ddns application enters its run method.

DHCP_DDNS_RUN_EXIT application is exiting the event loop

This is a debug message issued when the Dhcp-Ddns exits the in event loop.

DHCP_DDNS_SHUTDOWN application received shutdown command with args: %1

This is informational message issued when the application has been instructed to shut down by the controller.

DHCP_DDNS_STARTING_TRANSACTION Transaction Key: %1

This is a debug message issued when DHCP-DDNS has begun a transaction for a given request.

DHCP_DDNS_STATE_MODEL_UNEXPECTED_ERROR application encountered an unexpected error while carrying out a NameChangeRequest: %1

This is error message issued when the application fails to process a NameChangeRequest correctly. Some or all of the DNS updates requested as part of this update did not succeed. This is a programmatic error and should be reported.

DHCP_DDNS_TRANS_SEND_ERROR application encountered an unexpected error while attempting to send a DNS update: %1

This is error message issued when the application is able to construct an update message but the attempt to send it suffered a unexpected error. This is most likely a programmatic error, rather than a communications issue. Some or all of the DNS updates requested as part of this request did not succeed.

DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR unexpected exception thrown from the application receive completion handler: %1

This is an error message that indicates that an exception was thrown but not caught in the application's request receive completion handler. This is a programmatic error that needs to be reported. Dependent upon the nature of the error the application may or may not continue operating normally.

DHCP_DDNS_UNCAUGHT_NCR_SEND_HANDLER_ERROR unexpected exception thrown from the DHCP-DDNS client send completion handler: %1

This is an error message that indicates that an exception was thrown but not caught in the application's send completion handler. This is a programmatic error that needs to be reported. Dependent upon the nature of the error the client may or may not continue operating normally.

DHCP_DDNS_UPDATE_REQUEST_SENT %1 for transaction key: %2 to server: %3

This is a debug message issued when DHCP_DDNS sends a DNS request to a DNS server.

DHCP_DDNS_UPDATE_RESPONSE_RECEIVED for transaction key: %1 to server: %2 status: %3

This is a debug message issued when DHCP_DDNS receives sends a DNS update response from a DNS server.

DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1

This is an error message that indicates the application was unable to close the inbound side of a NCR sender's watch socket. While technically possible this error is highly unlikely to occur and should not impair the application's ability to process requests.

DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1

This is an error message that indicates the application was unable to close the outbound side of a NCR sender's watch socket. While technically possible this error is highly unlikely to occur and should not impair the application's ability to process requests.

HOOKS_ALL_CALLOUTS_DEREGISTERED hook library at index %1 removed all callouts on hook %2

A debug message issued when all callouts on the specified hook registered by the library with the given index were removed. This is similar to the HOOKS_CALLOUTS_REMOVED message (and the two are likely to be seen together), but is issued at a lower-level in the hook framework.

HOOKS_CALLOUTS_REMOVED callouts removed from hook %1 for library %2

This is a debug message issued during library unloading. It notes that one of more callouts registered by that library have been removed from the specified hook. This is similar to the HOOKS_DEREGISTER_ALL_CALLOUTS message (and the two are likely to be seen together), but is issued at a higher-level in the hook framework.

HOOKS_CALLOUT_CALLED hooks library with index %1 has called a callout on hook %2 that has address %3

Only output at a high debugging level, this message indicates that a callout on the named hook registered by the library with the given index (in the list of loaded libraries) has been called and returned a success state. The address of the callout is given in the message

HOOKS_CALLOUT_DEREGISTERED hook library at index %1 deregistered a callout on hook %2

A debug message issued when all instances of a particular callouts on the hook identified in the message that were registered by the library with the given index have been removed.

HOOKS_CALLOUT_ERROR error returned by callout on hook %1 registered by library with index %2 (callout address %3)

If a callout returns an error status when called, this error message is issued. It identifies the hook to which the callout is attached, the index of the library (in the list of loaded libraries) that registered it and the address of the callout. The error is otherwise ignored.

HOOKS_CALLOUT_EXCEPTION exception thrown by callout on hook %1 registered by library with index %2 (callout address %3): %4

If a callout throws an exception when called, this error message is issued. It identifies the hook to which the callout is attached, the index of the library (in the list of loaded libraries) that registered it and the address of the callout. The error is otherwise ignored.

HOOKS_CALLOUT_REGISTRATION hooks library with index %1 registering callout for hook '%2'

This is a debug message, output when a library (whose index in the list of libraries (being) loaded is given) registers a callout.

HOOKS_CLOSE_ERROR failed to close hook library %1: %2

BIND 10 has failed to close the named hook library for the stated reason. Although this is an error, this should not affect the running system other than as a loss of resources. If this error persists, you should restart BIND 10.

HOOKS_HOOK_LIST_RESET the list of hooks has been reset

This is a message indicating that the list of hooks has been reset. While this is usual when running the BIND 10 test suite, it should not be seen when running BIND 10 in a producion environment. If this appears, please report a bug through the usual channels.

HOOKS_INCORRECT_VERSION hook library %1 is at version %2, require version %3

BIND 10 has detected that the named hook library has been built against a version of BIND 10 that is incompatible with the version of BIND 10 running on your system. It has not loaded the library.

This is most likely due to the installation of a new version of BIND 10 without rebuilding the hook library. A rebuild and re-install of the library should fix the problem in most cases.

HOOKS_LIBRARY_LOADED hooks library %1 successfully loaded

This information message is issued when a user-supplied hooks library has been successfully loaded.

HOOKS_LIBRARY_LOADING loading hooks library %1

This is a debug message output just before the specified library is loaded. If the action is successfully, it will be followed by the HOOKS_LIBRARY_LOADED informational message.

HOOKS_LIBRARY_UNLOADED hooks library %1 successfully unloaded

This information message is issued when a user-supplied hooks library has been successfully unloaded.

HOOKS_LIBRARY_UNLOADING unloading library %1

This is a debug message called when the specified library is being unloaded. If all is successful, it will be followed by the HOOKS_LIBRARY_UNLOADED informational message.

HOOKS_LIBRARY_VERSION hooks library %1 reports its version as %2

A debug message issued when the version check on the hooks library has succeeded.

HOOKS_LOAD_ERROR 'load' function in hook library %1 returned error %2

A "load" function was found in the library named in the message and was called. The function returned a non-zero status (also given in the message) which was interpreted as an error. The library has been unloaded and no callouts from it will be installed.

HOOKS_LOAD_EXCEPTION 'load' function in hook library %1 threw an exception

A "load" function was found in the library named in the message and was called. The function threw an exception (an error indication) during execution, which is an error condition. The library has been unloaded and no callouts from it will be installed.

HOOKS_LOAD_FRAMEWORK_EXCEPTION 'load' function in hook library %1 threw an exception: reason %2

A "load" function was found in the library named in the message and was called. Either the hooks framework or the function threw an exception (an error indication) during execution, which is an error condition; the cause of the exception is recorded in the message. The library has been unloaded and no callouts from it will be installed.

HOOKS_LOAD_SUCCESS 'load' function in hook library %1 returned success

This is a debug message issued when the "load" function has been found in a hook library and has been successfully called.

HOOKS_NO_LOAD no 'load' function found in hook library %1

This is a debug message saying that the specified library was loaded but no function called "load" was found in it. Providing the library contained some "standard" functions (i.e. functions with the names of the hooks for the given server), this is not an issue.

HOOKS_NO_UNLOAD no 'unload' function found in hook library %1

This is a debug message issued when the library is being unloaded. It merely states that the library did not contain an "unload" function.

HOOKS_NO_VERSION no 'version' function found in hook library %1

The shared library named in the message was found and successfully loaded, but BIND 10 did not find a function named "version" in it. This function is required and should return the version of BIND 10 against which the library was built. The value is used to check that the library was built against a compatible version of BIND 10. The library has not been loaded.

HOOKS_OPEN_ERROR failed to open hook library %1: %2

BIND 10 failed to open the specified hook library for the stated reason. The library has not been loaded. BIND 10 will continue to function, but without the services offered by the library.

HOOKS_STD_CALLOUT_REGISTERED hooks library %1 registered standard callout for hook %2 at address %3

This is a debug message, output when the library loading function has located a standard callout (a callout with the same name as a hook point) and registered it. The address of the callout is indicated.

HOOKS_UNLOAD_ERROR 'unload' function in hook library %1 returned error %2

During the unloading of a library, an "unload" function was found. It was called, but returned an error (non-zero) status, resulting in the issuing of this message. The unload process continued after this message and the library has been unloaded.

HOOKS_UNLOAD_EXCEPTION 'unload' function in hook library %1 threw an exception

During the unloading of a library, an "unload" function was found. It was called, but in the process generated an exception (an error indication). The unload process continued after this message and the library has been unloaded.

HOOKS_UNLOAD_FRAMEWORK_EXCEPTION 'unload' function in hook library %1 threw an exception, reason %2

During the unloading of a library, an "unload" function was found. It was called, but in the process either it or the hooks framework generated an exception (an error indication); the cause of the error is recorded in the message. The unload process continued after this message and the library has been unloaded.

HOOKS_UNLOAD_SUCCESS 'unload' function in hook library %1 returned success

This is a debug message issued when an "unload" function has been found in a hook library during the unload process, called, and returned success.

HOOKS_VERSION_EXCEPTION 'version' function in hook library %1 threw an exception

This error message is issued if the version() function in the specified hooks library was called and generated an exception. The library is considered unusable and will not be loaded.

LIBDDNS_DATASRC_ERROR update client %1 failed due to data source error: %2

An update attempt failed due to some error in the corresponding data source. This is generally an unexpected event, but can still happen for various reasons such as DB lock contention or a failure of the backend DB server. The cause of the error is also logged. It's advisable to check the message, and, if necessary, take an appropriate action (e.g., restarting the DB server if it dies). If this message is logged the data source isn't modified due to the corresponding update request. When used by the b10-ddns, the server will return a response with an RCODE of SERVFAIL.

LIBDDNS_PREREQ_FORMERR update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL.

The prerequisite with the given name, class and type is not well-formed. The specific prerequisite is shown. In this case, it has a non-zero TTL value. A FORMERR error response is sent to the client.

LIBDDNS_PREREQ_FORMERR_ANY update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL or rdata found.

The prerequisite with the given name, class and type is not well-formed. The specific prerequisite is shown. In this case, it either has a non-zero TTL value, or has rdata fields. A FORMERR error response is sent to the client.

LIBDDNS_PREREQ_FORMERR_CLASS update client %1 for zone %2: Format error in prerequisite (%3). Bad class.

The prerequisite with the given name, class and type is not well-formed. The specific prerequisite is shown. In this case, the class of the prerequisite should either match the class of the zone in the Zone Section, or it should be ANY or NONE, and it is not. A FORMERR error response is sent to the client.

LIBDDNS_PREREQ_FORMERR_NONE update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL or rdata found.

The prerequisite with the given name, class and type is not well-formed. The specific prerequisite is shown. In this case, it either has a non-zero TTL value, or has rdata fields. A FORMERR error response is sent to the client.

LIBDDNS_PREREQ_NAME_IN_USE_FAILED update client %1 for zone %2: 'Name is in use' prerequisite not satisfied (%3), rcode: %4

A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that was not satisfied is shown. The client is sent an error response with the given rcode. In this case, the specific prerequisite is 'Name is in use'. From RFC2136: Name is in use. At least one RR with a specified NAME (in the zone and class specified by the Zone Section) must exist. Note that this prerequisite is NOT satisfied by empty nonterminals.

LIBDDNS_PREREQ_NAME_NOT_IN_USE_FAILED update client %1 for zone %2: 'Name is not in use' (%3) prerequisite not satisfied, rcode: %4

A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that was not satisfied is shown. The client is sent an error response with the given rcode. In this case, the specific prerequisite is 'Name is not in use'. From RFC2136: Name is not in use. No RR of any type is owned by a specified NAME. Note that this prerequisite IS satisfied by empty nonterminals.

LIBDDNS_PREREQ_NOTZONE update client %1 for zone %2: prerequisite not in zone (%3)

A DDNS UPDATE prerequisite has a name that does not appear to be inside the zone specified in the Zone section of the UPDATE message. The specific prerequisite is shown. A NOTZONE error response is sent to the client.

LIBDDNS_PREREQ_RRSET_DOES_NOT_EXIST_FAILED update client %1 for zone %2: 'RRset does not exist' (%3) prerequisite not satisfied, rcode: %4

A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that was not satisfied is shown. The client is sent an error response with the given rcode. In this case, the specific prerequisite is 'RRset does not exist'. From RFC2136: RRset does not exist. No RRs with a specified NAME and TYPE (in the zone and class denoted by the Zone Section) can exist.

LIBDDNS_PREREQ_RRSET_EXISTS_FAILED update client %1 for zone %2: 'RRset exists (value independent)' (%3) prerequisite not satisfied, rcode: %4

A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that was not satisfied is shown. The client is sent an error response with the given rcode. In this case, the specific prerequisite is 'RRset exists (value independent)'. From RFC2136: RRset exists (value dependent). A set of RRs with a specified NAME and TYPE exists and has the same members with the same RDATAs as the RRset specified here in this Section.

LIBDDNS_PREREQ_RRSET_EXISTS_VAL_FAILED update client %1 for zone %2: 'RRset exists (value dependent)' (%3) prerequisite not satisfied, rcode: %4

A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that was not satisfied is shown. The client is sent an error response with the given rcode. In this case, the specific prerequisite is 'RRset exists (value dependent)'. From RFC2136: RRset exists (value independent). At least one RR with a specified NAME and TYPE (in the zone and class specified by the Zone Section) must exist.

LIBDDNS_UPDATE_ADD_BAD_TYPE update client %1 for zone %2: update addition RR bad type: %3

The Update section of a DDNS update message contains a statement that tries to add a record of an invalid type. Most likely the record has an RRType that is considered a 'meta' type, which cannot be zone content data. The specific record is shown. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_APPROVED update client %1 for zone %2 approved

Debug message. An update request was approved in terms of the zone's update ACL.

LIBDDNS_UPDATE_BAD_CLASS update client %1 for zone %2: bad class in update RR: %3

The Update section of a DDNS update message contains an RRset with a bad class. The class of the update RRset must be either the same as the class in the Zone Section, ANY, or NONE. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DATASRC_COMMIT_FAILED error in datasource during DDNS update: %1

An error occurred while committing the DDNS update changes to the datasource. The specific error is printed. A SERVFAIL response is sent back to the client.

LIBDDNS_UPDATE_DELETE_BAD_TYPE update client %1 for zone %2: update deletion RR bad type: %3

The Update section of a DDNS update message contains a statement that tries to delete an rrset of an invalid type. Most likely the record has an RRType that is considered a 'meta' type, which cannot be zone content data. The specific record is shown. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DELETE_NONZERO_TTL update client %1 for zone %2: update deletion RR has non-zero TTL: %3

The Update section of a DDNS update message contains a 'delete rrset' statement with a non-zero TTL. This is not allowed by the protocol. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DELETE_RRSET_NOT_EMPTY update client %1 for zone %2: update deletion RR contains data %3

The Update section of a DDNS update message contains a 'delete rrset' statement with a non-empty RRset. This is not allowed by the protocol. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DELETE_RR_BAD_TYPE update client %1 for zone %2: update deletion RR bad type: %3

The Update section of a DDNS update message contains a statement that tries to delete one or more rrs of an invalid type. Most likely the records have an RRType that is considered a 'meta' type, which cannot be zone content data. The specific record is shown. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DELETE_RR_NONZERO_TTL update client %1 for zone %2: update deletion RR has non-zero TTL: %3

The Update section of a DDNS update message contains a 'delete rrs' statement with a non-zero TTL. This is not allowed by the protocol. A FORMERR response is sent back to the client.

LIBDDNS_UPDATE_DENIED update client %1 for zone %2 denied

Informational message. An update request was denied because it was rejected by the zone's update ACL. When this library is used by b10-ddns, the server will respond to the request with an RCODE of REFUSED as described in Section 3.3 of RFC2136.

LIBDDNS_UPDATE_DROPPED update client %1 for zone %2 dropped

Informational message. An update request was denied because it was rejected by the zone's update ACL. When this library is used by b10-ddns, the server will then completely ignore the request; no response will be sent.

LIBDDNS_UPDATE_FORWARD_FAIL update client %1 for zone %2: update forwarding not supported

Debug message. An update request is sent to a secondary server. This is not necessarily invalid, but this implementation does not yet support update forwarding as specified in Section 6 of RFC2136 and it will simply return a response with an RCODE of NOTIMP to the client. The client's address and the zone name/class are logged.

LIBDDNS_UPDATE_NOTAUTH update client %1 for zone %2: not authoritative for update zone

Debug message. An update request was received for a zone for which the receiving server doesn't have authority. In theory this is an unexpected event, but there are client implementations that could send update requests carelessly, so it may not necessarily be so uncommon in practice. If possible, you may want to check the implementation or configuration of those clients to suppress the requests. As specified in Section 3.1 of RFC2136, the receiving server will return a response with an RCODE of NOTAUTH.

LIBDDNS_UPDATE_NOTZONE update client %1 for zone %2: update RR out of zone %3

A DDNS UPDATE record has a name that does not appear to be inside the zone specified in the Zone section of the UPDATE message. The specific update record is shown. A NOTZONE error response is sent to the client.

LIBDDNS_UPDATE_PREREQUISITE_FAILED prerequisite failed in update client %1 for zone %2: result code %3

The handling of the prerequisite section (RFC2136 Section 3.2) found that one of the prerequisites was not satisfied. The result code should give more information on what prerequisite type failed. If the result code is FORMERR, the prerequisite section was not well-formed. An error response with the given result code is sent back to the client.

LIBDDNS_UPDATE_PROCESSING_FAILED update client %1 for zone %2: %3

Debug message. An error is found in processing a dynamic update request. This log message is used for general errors that are not normally expected to happen. So, in general, it would mean some problem in the client implementation or an interoperability issue with this implementation. The client's address, the zone name and class, and description of the error are logged.

LIBDDNS_UPDATE_UNCAUGHT_EXCEPTION update client %1 for zone %2: uncaught exception while processing update section: %3

An uncaught exception was encountered while processing the Update section of a DDNS message. The specific exception is shown in the log message. To make sure DDNS service is not interrupted, this problem is caught instead of reraised; The update is aborted, and a SERVFAIL is sent back to the client. This is most probably a bug in the DDNS code, but *could* be caused by the data source.

LIBDDNS_ZONE_INVALID_ERROR Newly received zone data %1/%2 fails validation: %3

The zone data was received successfully, but the zone when updated with this zone data fails validation.

LIBDDNS_ZONE_INVALID_WARN Newly received zone data %1/%2 has a problem: %3

The zone data was received successfully, but when checking the zone when updated with this zone data, it was discovered there's some issue with it. It might be correct, but it should be checked and possibly fixed. The problem does not stop the zone from being used.

LIBMEMMGR_BUILDER_BAD_COMMAND_ERROR MemorySegmentBuilder received bad command '%1'

The MemorySegmentBuilder has received a bad command in its input command queue. This is likely a programming error. If the builder runs in a separate thread, this would cause it to exit the thread.

LIBMEMMGR_BUILDER_GET_ZONE_WRITER_ERROR Unable to get zone writer for zone '%1', data source '%2'. Skipping.

The MemorySegmentBuilder was unable to get a ZoneWriter for the specified zone when handling the load command. This zone will be skipped.

LIBMEMMGR_BUILDER_ZONE_WRITER_LOAD_1_ERROR Error loading zone '%1', data source '%2': '%3'

The MemorySegmentBuilder failed to load the specified zone when handling the load command. This zone will be skipped.

LIBMEMMGR_BUILDER_ZONE_WRITER_LOAD_2_ERROR Error loading zone '%1', data source '%2': '%3'

An exception occured when the MemorySegmentBuilder tried to load the specified zone when handling the load command. This zone will be skipped.

LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1.

The xfrin module received an update containing multiple rdata changes for the same RRset. But the TTLs of these don't match each other. As we combine them together, the latter one gets overwritten to the earlier one in the sequence.

LIBXFRIN_NO_JOURNAL disabled journaling for updates to %1 on %2

An attempt was made to create a Diff object with journaling enabled, but the underlying data source didn't support journaling (while still allowing updates) and so the created object has it disabled. At a higher level this means that the updates will be applied to the zone but subsequent IXFR requests will result in a full zone transfer (i.e., an AXFR-style IXFR). Unless the overhead of the full transfer is an issue this message can be ignored; otherwise you may want to check why the journaling wasn't allowed on the data source and either fix the issue or use a different type of data source.

LOADZONE_ARGUMENT_ERROR Error in command line arguments: %1

Some semantics error in command line arguments or options to b10-loadzone is detected. b10-loadzone does effectively nothing and immediately terminates.

LOADZONE_CANCEL_CREATE_ZONE Creation of new zone %1/%2 was canceled

b10-loadzone has created a new zone in the data source (see LOADZONE_ZONE_CREATED), but the loading operation has subsequently failed. The newly created zone has been removed from the data source, so that the data source will go back to the original state.

LOADZONE_DONE Loaded %1 RRs into zone %2/%3 in %4 seconds

b10-loadzone has successfully loaded the specified zone. If there was an old version of the zone in the data source, it is now deleted. It also prints the number of RRs that have been loaded and the time spent for the loading.

LOADZONE_EMPTY_DONE Completed emptying zone %1/%2

b10-loadzone has successfully emptied content of the specified zone. This includes the case where the content didn't previously exist, in which case it just still reamins empty.

LOADZONE_LOAD_ERROR Failed to load zone %1/%2: %3

Loading a zone by b10-loadzone fails for some reason in the middle of the loading. This is most likely due to an error in the specified arguments to b10-loadzone (such as non-existent zone file) or an error in the zone file. When this happens, the RRs loaded so far are effectively deleted from the zone, and the old version (if exists) will still remain valid for operations.

LOADZONE_SQLITE3_USING_DEFAULT_CONFIG Using default configuration with SQLite3 DB file %1

The SQLite3 data source is specified as the data source type without a data source configuration. b10-loadzone uses the default configuration with the default DB file for the BIND 10 system.

LOADZONE_UNEXPECTED_FAILURE Unexpected exception: %1

b10-loadzone encounters an unexpected failure and terminates itself. This is generally a bug of b10-loadzone itself or the underlying data source library, so it's advisable to submit a bug report if this message is logged. The incomplete attempt of loading should have been cleanly canceled in this case, too.

LOADZONE_ZONE_CREATED Zone %1/%2 does not exist in the data source, newly created

The specified zone to b10-loadzone to load does not exist in the specified data source. b10-loadzone has created a new empty zone in the data source.

LOADZONE_ZONE_UPDATING Started updating zone %1/%2 with removing old data (this can take a while)

b10-loadzone started loading a new version of the zone as specified, beginning with removing the current contents of the zone (in a transaction, so the removal won't take effect until and unless the entire load is completed successfully). If the old version of the zone is large, this can take time, such as a few minutes or more, without any visible feedback. This is not a problem as long as the b10-loadzone process is working at a moderate load.

LOGIMPL_ABOVE_MAX_DEBUG debug level of %1 is too high and will be set to the maximum of %2

A message from the interface to the underlying logger implementation reporting that the debug level (as set by an internally-created string DEBUGn, where n is an integer, e.g. DEBUG22) is above the maximum allowed value and has been reduced to that value. The appearance of this message may indicate a programming error - please submit a bug report.

LOGIMPL_BAD_DEBUG_STRING debug string '%1' has invalid format

A message from the interface to the underlying logger implementation reporting that an internally-created string used to set the debug level is not of the correct format (it should be of the form DEBUGn, where n is an integer, e.g. DEBUG22). The appearance of this message indicates a programming error - please submit a bug report.

LOGIMPL_BELOW_MIN_DEBUG debug level of %1 is too low and will be set to the minimum of %2

A message from the interface to the underlying logger implementation reporting that the debug level (as set by an internally-created string DEBUGn, where n is an integer, e.g. DEBUG22) is below the minimum allowed value and has been increased to that value. The appearance of this message may indicate a programming error - please submit a bug report.

LOG_BAD_DESTINATION unrecognized log destination: %1

A logger destination value was given that was not recognized. The destination should be one of "console", "file", or "syslog".

LOG_BAD_SEVERITY unrecognized log severity: %1

A logger severity value was given that was not recognized. The severity should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE".

LOG_BAD_STREAM bad log console output stream: %1

Logging has been configured so that output is written to the terminal (console) but the stream on which it is to be written is not recognised. Allowed values are "stdout" and "stderr".

LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code

During start-up, BIND 10 detected that the given message identification had been defined multiple times in the BIND 10 code. This indicates a programming error; please submit a bug report.

LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found

When reading a message file, more than one $NAMESPACE directive was found. (This directive is used to set a C++ namespace when generating header files during software development.) Such a condition is regarded as an error and the read will be abandoned.

LOG_INPUT_OPEN_FAIL unable to open message file %1 for input: %2

The program was not able to open the specified input message file for the reason given.

LOG_INVALID_MESSAGE_ID line %1: invalid message identification '%2'

An invalid message identification (ID) has been found during the read of a message file. Message IDs should comprise only alphanumeric characters and the underscore, and should not start with a digit.

LOG_LOCK_TEST_MESSAGE this is a test message.

This is a log message used in testing.

LOG_NAMESPACE_EXTRA_ARGS line %1: $NAMESPACE directive has too many arguments

The $NAMESPACE directive in a message file takes a single argument, a namespace in which all the generated symbol names are placed. This error is generated when the compiler finds a $NAMESPACE directive with more than one argument.

LOG_NAMESPACE_INVALID_ARG line %1: $NAMESPACE directive has an invalid argument ('%2')

The $NAMESPACE argument in a message file should be a valid C++ namespace. This message is output if the simple check on the syntax of the string carried out by the reader fails.

LOG_NAMESPACE_NO_ARGS line %1: no arguments were given to the $NAMESPACE directive

The $NAMESPACE directive in a message file takes a single argument, a C++ namespace in which all the generated symbol names are placed. This error is generated when the compiler finds a $NAMESPACE directive with no arguments.

LOG_NO_MESSAGE_ID line %1: message definition line found without a message ID

Within a message file, message are defined by lines starting with a "%". The rest of the line should comprise the message ID and text describing the message. This error indicates the message compiler found a line in the message file comprising just the "%" and nothing else.

LOG_NO_MESSAGE_TEXT line %1: line found containing a message ID ('%2') and no text

Within a message file, message are defined by lines starting with a "%". The rest of the line should comprise the message ID and text describing the message. This error indicates the message compiler found a line in the message file comprising just the "%" and message identification, but no text.

LOG_NO_SUCH_MESSAGE could not replace message text for '%1': no such message

During start-up a local message file was read. A line with the listed message identification was found in the file, but the identification is not one contained in the compiled-in message dictionary. This message may appear a number of times in the file, once for every such unknown message identification.

There may be several reasons why this message may appear:

- The message ID has been mis-spelled in the local message file.

- The program outputting the message may not use that particular message (e.g. it originates in a module not used by the program).

- The local file was written for an earlier version of the BIND 10 software and the later version no longer generates that message.

Whatever the reason, there is no impact on the operation of BIND 10.

LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2

Originating within the logging code, the program was not able to open the specified output file for the reason given.

LOG_PREFIX_EXTRA_ARGS line %1: $PREFIX directive has too many arguments

Within a message file, the $PREFIX directive takes a single argument, a prefix to be added to the symbol names when a C++ file is created. This error is generated when the compiler finds a $PREFIX directive with more than one argument.

Note: the $PREFIX directive is deprecated and will be removed in a future version of BIND 10.

LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')

Within a message file, the $PREFIX directive takes a single argument, a prefix to be added to the symbol names when a C++ file is created. As such, it must adhere to restrictions on C++ symbol names (e.g. may only contain alphanumeric characters or underscores, and may nor start with a digit). A $PREFIX directive was found with an argument (given in the message) that violates those restrictions.

Note: the $PREFIX directive is deprecated and will be removed in a future version of BIND 10.

LOG_READING_LOCAL_FILE reading local message file %1

This is an informational message output by BIND 10 when it starts to read a local message file. (A local message file may replace the text of one or more messages; the ID of the message will not be changed though.)

LOG_READ_ERROR error reading from message file %1: %2

The specified error was encountered reading from the named message file.

LOG_UNRECOGNISED_DIRECTIVE line %1: unrecognised directive '%2'

Within a message file, a line starting with a dollar symbol was found (indicating the presence of a directive) but the first word on the line (shown in the message) was not recognised.

LOG_WRITE_ERROR error writing to %1: %2

The specified error was encountered by the message compiler when writing to the named output file.

MEMMGR_CONFIG_FAIL failed to apply configuration updates: %1

The memmgr daemon tried to apply configuration updates but found an error. The cause of the error is included in the message. None of the received updates applied, and the daemon keeps running with the previous configuration.

MEMMGR_CONFIG_UPDATE received new configuration

A debug message. The memmgr daemon receives configuratiopn updates and is now applying them to its running configurations.

MEMMGR_DATASRC_CONFIG_ERROR failed to update data source configuration: %1

Configuration for the global data sources is updated, but the update cannot be applied to memmgr. The memmgr module will still keep running with the previous configuration, but the cause of the failure and other log messages must be carefully examined because if only memmgr rejects the new configuration then the entire BIND 10 system will have inconsistent state among different modules. If other modules accept the update but memmgr produces this error, it's quite likely that the system isn't working as expected, and is probably better to be shut down to figure out and fix the cause.

MEMMGR_DATASRC_RECONFIGURED data source configuration has been updated, generation ID %1

The memmgr daemon received a new version of data source configuration, and has successfully applied it to the local state. Loading of new zone data into memory will possibly take place.

MEMMGR_NO_DATASRC_CONF failed to add data source configuration: %1

The memmgr daemon tried to incorporate data source configuration on its startup but failed to do so. Due to internal implementation details this shouldn't happen as long as the BIND 10 system has been installed correctly. So, if this error message is logged, you should probably reinstall the entire system, preferably from the scratch, and see if it still happens. The memmgr daemon cannot do any meaningful work without data sources, so it immediately terminates itself.

MSGQ_ALREADY_RUNNING Another copy of b10-msgq is already running.

Only a single instance of b10-msgq should ever be run at one time. This instance will now terminate.

MSGQ_CFGMGR_SUBSCRIBED The config manager subscribed to message queue

This is a debug message. The message queue has little bit of special handling for the configuration manager. This special handling is happening now.

MSGQ_CLOSE_ON_RECV Reading from socket canceled as it's closed: FD=%1

A debug message. The msgq daemon was notified of a read event on a socket, but its initial read operation failed because the remote client has closed its socket. This is possible in a normal operation when a module shuts down.

MSGQ_CLOSE_ON_SEND Sending to socket failed as already closed (okay to ignore on shutdown): FD=%1

The msgq daemon tries to send some data to a client module, but it failed because the socket has been closed. This normally means the client terminates (for some reason - either gracefully or as a crash) while other modules try to send a message to the terminated module. Since msgq doesn't keep track of the status of client modules, this can happen and is not really an error for msgq; however, it can still be an unexpected event for the BIND 10 system as a whole in that this particular message is lost, so it's logged as a warning. If this message is logged for a running BIND 10 system, it's suggested to check other log messages; there may be an error from other modules reporting a missing response message. One common, less critical case where this message is logged is during shutdown. The ordering of process shutdown is basically arbitrary at this moment, so it's possible that some module tries to send a "quitting" message to some other module but the latter has already shut down. Such cases are generally non critical, but you may want to check other possible error messages.

MSGQ_COMMAND Running command %1 with arguments %2

Debug message. The message queue received a command and it is running it.

MSGQ_COMMAND_UNKNOWN Unknown command '%1'

The message queue received a command from other module, but it doesn't recognize it. This is probably either a coding error or inconsistency between the message queue version and version of the module.

MSGQ_CONFIG_DATA Received configuration update for the msgq: %1

Debug message. The message queue received a configuration update, handling it.

MSGQ_EXITING exiting

The msgq daemon is exiting.

MSGQ_HDR_DECODE_ERROR Error decoding header received from socket %1: %2

The socket with mentioned file descriptor sent a packet. However, it was not possible to decode the routing header of the packet. The packet is ignored. This may be caused by a programmer error (one of the components sending invalid data) or possibly by incompatible version of msgq and the component (but that's unlikely, as the protocol is not changed often).

MSGQ_INVALID_CMD Received invalid command: %1

An unknown command listed in the log has been received. It is ignored. This indicates either a programmer error (eg. a typo in the command name) or incompatible version of a module and message queue daemon.

MSGQ_LISTENER_FAILED Failed to initialize listener on socket file '%1': %2

The message queue daemon tried to listen on a file socket (the path is in the message), but it failed. The error from the operating system is logged.

MSGQ_LISTENER_SETUP Starting to listen on socket file '%1'

Debug message. The listener is trying to open a listening socket.

MSGQ_LISTENER_STARTED Successfully started to listen

Debug message. The message queue successfully opened a listening socket and waits for incoming connections.

MSGQ_RECV_ERROR Error reading from socket %1: %2

There was a low-level error when reading from a socket. The error is logged and the corresponding socket is dropped. The errors include receiving broken or (non empty but) incomplete data. In either case it usually suggests something unexpected happens within the BIND 10 system; it's probably better to restart the system, and if it continues it should be reported as a bug. One known, probably non critical case is the "connection reset by peer" (or its variants) socket error appearing on shutdown. It's known this happens when the remote client closes the connection as part of shutdown process. Such cases are normally expected to be reported as receiving empty data (which we log it at the debug level as the MSGQ_CLOSE_ON_RECV message), but for some (yet) unknown reason it can also be reported as the system error. At shutdown time it's expected that connections are closed, so it's probably safe to ignore these messages in such a case. We still log them as an error as we've not figured out how exactly that can happen. In future, we may make the shutdown process more robust so the msgq daemon can explicitly know when a client shuts down more reliably. If and when it's implemented this error message won't appear on shutdown unless there's really something unexpected.

MSGQ_RECV_HDR Received header: %1

Debug message. This message includes the whole routing header of a packet.

MSGQ_SELECT_ERROR Error while waiting for events: %1

A low-level error happened when waiting for events, the error is logged. The reason for this varies, but it usually means the system is short on some resources.

MSGQ_SEND_ERROR Error while sending to socket %1: %2

There was a low-level error when sending data to a socket. The error is logged and the corresponding socket is dropped.

MSGQ_SHUTDOWN Stopping Msgq

Debug message. The message queue is shutting down.

MSGQ_SOCKET_REGISTERED Registered a socket descriptor %1 with lname %2

Debug message. The msgq daemon accepted a session request on the shown descriptor of socket and assigned a unique identifier (lname) for the client on that socket.

MSGQ_SOCKET_TIMEOUT_ERROR Killing socket %1 because timeout exceeded (%2)

Outgoing data was queued up on a socket connected to msgq, but the other side is not reading it. It could be deadlocked, or may not be monitoring it. Both cases are programming errors and should be corrected. The socket is closed on the msgq side.

MSGQ_SOCK_CLOSE Closing socket fd %1

Debug message. Closing the mentioned socket.

MSGQ_START Msgq version %1 starting

Debug message. The message queue is starting up.

MSGQ_START_FAIL Error during startup: %1

There was an error during early startup of the daemon. More concrete error is in the log. The daemon terminates as a result.

MSGQ_SUBS_APPEND_TARGET Appending to existing target for subscription to group '%1' for instance '%2'

Debug message. Creating a new subscription by appending it to already existing data structure.

MSGQ_SUBS_NEW_TARGET Creating new target for subscription to group '%1' for instance '%2'

Debug message. Creating a new subscription. Also creating a new data structure to hold it.

NOTIFY_OUT_DATASRC_ACCESS_FAILURE failed to get access to data source: %1

notify_out failed to get access to one of configured data sources. Detailed error is shown in the log message. This can be either a configuration error or installation setup failure.

NOTIFY_OUT_DATASRC_ZONE_NOT_FOUND Zone %1 is not found

notify_out attempted to get slave information of a zone but the zone isn't found in the expected data source. This shouldn't happen, because notify_out first identifies a list of available zones before this process. So this means some critical inconsistency in the data source or software bug.

NOTIFY_OUT_INVALID_ADDRESS invalid address %1: %2

The notify_out library tried to send a notify message to the given address, but it appears to be an invalid address. The configuration for secondary nameservers might contain a typographic error, or a different BIND 10 module has forgotten to validate its data before sending this module a notify command. As such, this should normally not happen, and points to an oversight in a different module.

NOTIFY_OUT_REPLY_BAD_OPCODE bad opcode in notify reply from %1: %2

The notify_out library sent a notify message to the nameserver at the given address, but the response did not have the opcode set to NOTIFY. The opcode in the response is printed. Since there was a response, no more notifies will be sent to this server for this notification event.

NOTIFY_OUT_REPLY_BAD_QID bad QID in notify reply from %1: got %2, should be %3

The notify_out library sent a notify message to the nameserver at the given address, but the query id in the response does not match the one we sent. Since there was a response, no more notifies will be sent to this server for this notification event.

NOTIFY_OUT_REPLY_BAD_QUERY_NAME bad query name in notify reply from %1: got %2, should be %3

The notify_out library sent a notify message to the nameserver at the given address, but the query name in the response does not match the one we sent. Since there was a response, no more notifies will be sent to this server for this notification event.

NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1

The notify_out library sent a notify message to the namesever at the given address, but the reply did not have the QR bit set to one. Since there was a response, no more notifies will be sent to this server for this notification event.

NOTIFY_OUT_REPLY_RECEIVED Zone %1/%2: notify response from %3: %4

The notify_out library sent a notify message to the nameserver at the given address, and received a response. Its Rcode will be shown, too.

NOTIFY_OUT_REPLY_UNCAUGHT_EXCEPTION uncaught exception: %1

There was an uncaught exception in the handling of a notify reply message, either in the message parser, or while trying to extract data from the parsed message. The error is printed, and notify_out will treat the response as a bad message, but this does point to a programming error, since all exceptions should have been caught explicitly. Please file a bug report. Since there was a response, no more notifies will be sent to this server for this notification event.

NOTIFY_OUT_RETRY_EXCEEDED notify to %1: number of retries (%2) exceeded

The maximum number of retries for the notify target has been exceeded. Either the address of the secondary nameserver is wrong, or it is not responding.

NOTIFY_OUT_SENDING_NOTIFY sending notify to %1

A notify message is sent to the secondary nameserver at the given address.

NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1: %2

There was a network error while trying to send a notify message to the given address. The address might be unreachable. The socket error is printed and should provide more information.

NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1: %2

There was a network error while trying to read a notify reply message from the given address. The socket error is printed and should provide more information.

NOTIFY_OUT_TIMEOUT retry notify to %1

The notify message to the given address (noted as address:port) has timed out, and the message will be resent until the max retry limit is reached.

NOTIFY_OUT_ZONE_BAD_SOA Zone %1 is invalid in terms of SOA

This is a warning issued when the notify_out module finds a zone that doesn't have an SOA RR or has multiple SOA RRs. Notify message won't be sent to such a zone.

NOTIFY_OUT_ZONE_NO_NS Zone %1 doesn't have NS RR

This is a warning issued when the notify_out module finds a zone that doesn't have an NS RR. Notify message won't be sent to such a zone.

NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section

The NSAS (nameserver address store - part of the resolver) made a query for information it needed. The query completed successfully but the answer section in the response was empty.

NSAS_ERROR_RESPONSE error response of %1 returned in query for %2

The NSAS (nameserver address store - part of the resolver) made a query for information it needed. The query completed successfully but the RCODE in the response was something other than NOERROR.

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_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_NULL_RESPONSE got null message in success callback for query for %1

The NSAS (nameserver address store - part of the resolver) made a query for information it needed. The query completed successfully, but the message passed to the callback was null.

This message indicates an internal error in the NSAS. Please raise a bug report.

NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1

A debug message output when a call is made to the NSAS (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 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 NSAS. Please raise a bug report.

PYCC_LNAME_RECEIVED received local name: %1

Debug message: the local module received its unique identifier (name) from msgq on completion of establishing the session with msgq.

PYSERVER_COMMON_COMMAND %1 server has received '%2' command

The server process received the shown name of command from other module.

PYSERVER_COMMON_DNS_TCP_SEND_DONE completed sending TCP message to %1 (%2 bytes in total)

Debug message. A complete DNS message has been successfully transmitted over a TCP connection, possibly after multiple send operations. The destination address and the total size of the message (including the 2-byte length field) are shown in the log message.

PYSERVER_COMMON_DNS_TCP_SEND_FAILED failed to send TCP message to %1 (%2/%3 bytes sent): %4

A DNS message has been attempted to be sent out over a TCP connection, but it failed due to some network error. Although it's not expected to happen too often, it can still happen for various reasons. The administrator may want to examine the cause of the failure, which is included in the log message, to see if it requires some action to be taken at the server side. When this message is logged, the corresponding TCP connection was closed immediately after the error was detected.

PYSERVER_COMMON_DNS_TCP_SEND_PENDING sent part TCP message to %1 (up to %2/%3 bytes)

Debug message. A part of DNS message has been transmitted over a TCP connection, and it's suspended because further attempt would block. The destination address and the total size of the message that has been transmitted so far (including the 2-byte length field) are shown in the log message.

PYSERVER_COMMON_SERVER_FATAL %1 server has encountered a fatal error: %2

The BIND 10 server process encountered a fatal error (normally specific to the particular program), and is forcing itself to shut down.

PYSERVER_COMMON_SERVER_STARTED %1 server has started

The server process has successfully started and is now ready to receive commands and configuration updates.

PYSERVER_COMMON_SERVER_STOPPED %1 server has started

The server process has successfully stopped and is no longer listening for or handling commands. Normally the process will soon exit.

PYSERVER_COMMON_TSIG_KEYRING_DEINIT Deinitializing global TSIG keyring

A debug message noting that the global TSIG keyring is being removed from memory. Most programs don't do that, they just exit, which is OK.

PYSERVER_COMMON_TSIG_KEYRING_INIT Initializing global TSIG keyring

A debug message noting the TSIG keyring storage is being prepared. It should appear at most once in the lifetime of a program. The keyring still needs to be loaded from configuration.

PYSERVER_COMMON_TSIG_KEYRING_UPDATE Updating global TSIG keyring

A debug message. The TSIG keyring is being (re)loaded from configuration. This happens at startup or when the configuration changes. The old keyring is removed and new one created with all the keys.

PYSERVER_COMMON_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2

The BIND 10 server process encountered an uncaught exception and will now shut down. This is indicative of a programming error and should not happen under normal circumstances. The exception type and message are printed.

PYTHON_UNHANDLED_EXCEPTION program terminated with exception %1: %2. More info in %3

A program encountered an unexpected situation and terminated because it didn't know how to handle it. The exact problem is logged in the message. This might be caused by a bug in the program, a broken installation, or just a very rare condition which wasn't handled in the code. A full stack trace is left in the generated file. If you report a bug for this exception, please include that file. The file will not be deleted automatically and you may want to remove it when you no longer need the information there.

RESLIB_ANSWER answer received in response to query for <%1>

A debug message reporting that an answer has been received to an upstream query for the specified question. Previous debug messages will have indicated the server to which the question was sent.

RESLIB_CNAME CNAME received in response to query for <%1>

A debug message recording that CNAME response has been received to an upstream query for the specified question. Previous debug messages will have indicated the server to which the question was sent.

RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2

A debug message, a cache lookup did not find the specified <name, class, type> tuple in the cache; instead, the deepest delegation found is indicated.

RESLIB_EMPTY_RESPONSE empty response received to query for <%1>

A debug message, the response to the specified query from an upstream nameserver did not contain anything in the answer or authority sections, although in all other respects it was a valid response. A SERVFAIL will be returned to the system making the original query.

RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1>

A debug message, the response to the specified query to an upstream nameserver indicated that the response was classified as an erroneous response, but that the nature of the error cannot be identified. A SERVFAIL will be returned to the system making the original query.

RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1>

A debug message indicating that the response to the specified query from an upstream nameserver contained too much data. This can happen if an ANY query was sent and the answer section in the response contained multiple RRs with different names. A SERVFAIL will be returned to the system making the original query.

RESLIB_FOLLOW_CNAME following CNAME chain to <%1>

A debug message, a CNAME response was received and another query is being issued for the <name, class, type> tuple.

RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1>

A debug message, the response to the specified query from an upstream nameserver (as identified by the ID of the response) contained either an answer not matching the query name or an answer having a different class to that queried for. A SERVFAIL will be returned to the system making the original query.

RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1>

A debug message, the response to the specified query from an upstream nameserver (as identified by the ID of the response) contained a name in the question section that did not match that of the query. A SERVFAIL will be returned to the system making the original query.

RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1>

A debug message, the response to the specified query from an upstream nameserver (as identified by the ID of the response) contained an invalid type field. A SERVFAIL will be returned to the system making the original query.

RESLIB_LONG_CHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded

A debug message recording that a CNAME response has been received to an upstream query for the specified question (Previous debug messages will have indicated the server to which the question was sent). However, receipt of this CNAME has meant that the resolver has exceeded the CNAME chain limit (a CNAME chain is where on CNAME points to another) and so an error is being returned.

RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes

A debug message reporting that the response to an upstream query for the specified name contained multiple RRsets in the answer and not all were of the same class. This is a violation of the standard and so a SERVFAIL will be returned.

RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response

A debug message, the response to the specified query from an upstream nameserver was a CNAME that had multiple RRs in the RRset. This is an invalid response according to the standards so a SERVFAIL will be returned to the system making the original query.

RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1>

A debug message, the response to the specified query from an upstream nameserver (as identified by the ID of the response) did not contain one name in the question section as required by the standard. A SERVFAIL will be returned to the system making the original query.

RESLIB_NOT_RESPONSE response to query for <%1> was not a response

A debug message, the response to the specified query from an upstream nameserver (as identified by the ID of the response) did not have the QR bit set (thus indicating that the packet was a query, not a response). A SERVFAIL will be returned to the system making the original query.

RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1>

A debug message, this indicates that a response was received for the specified query and was categorized as a referral. However, the received message did not contain any NS RRsets. This may indicate a programming error in the response classification code.

RESLIB_NSAS_LOOKUP looking up nameserver for zone %1 in the NSAS

A debug message, the RunningQuery object is querying the NSAS for the nameservers for the specified zone.

RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <%1>

A debug message recording that either a NXDOMAIN or an NXRRSET response has been received to an upstream query for the specified question. Previous debug messages will have indicated the server to which the question was sent.

RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode

A debug message, the response to the specified query from an upstream nameserver was a response that did not have the opcode set to that of a query. According to the standards, this is an invalid response to the query that was made, so a SERVFAIL will be returned to the system making the original query.

RESLIB_PROTOCOL protocol error in answer for %1: %3

A debug message indicating that a protocol error was received. As there are no retries left, an error will be reported.

RESLIB_PROTOCOL_RETRY protocol error in answer for %1: %2 (retries left: %3)

A debug message indicating that a protocol error was received and that the resolver is repeating the query to the same nameserver. After this repeated query, there will be the indicated number of retries left.

RESLIB_RCODE_RETURNED response to query for <%1> returns RCODE of %2

A debug message, the response to the specified query indicated an error that is not covered by a specific code path. A SERVFAIL will be returned.

RESLIB_RECQ_CACHE_FIND found <%1> in the cache (resolve() instance %2)

This is a debug message and indicates that a RecursiveQuery object found the specified <name, class, type> tuple in the cache. The instance number at the end of the message indicates which of the two resolve() methods has been called.

RESLIB_RECQ_CACHE_NO_FIND did not find <%1> in the cache, starting RunningQuery (resolve() instance %2)

This is a debug message and indicates that the look in the cache made by the RecursiveQuery::resolve() method did not find an answer, so a new RunningQuery object has been created to resolve the question. The instance number at the end of the message indicates which of the two resolve() methods has been called.

RESLIB_REFERRAL referral received in response to query for <%1>

A debug message recording that a referral response has been received to an upstream query for the specified question. Previous debug messages will have indicated the server to which the question was sent.

RESLIB_REFER_ZONE referred to zone %1

A debug message indicating that the last referral message was to the specified zone.

RESLIB_RESOLVE asked to resolve <%1> (resolve() instance %2)

A debug message, the RecursiveQuery::resolve method has been called to resolve the specified <name, class, type> tuple. The first action will be to lookup the specified tuple in the cache. The instance number at the end of the message indicates which of the two resolve() methods has been called.

RESLIB_RRSET_FOUND found single RRset in the cache when querying for <%1> (resolve() instance %2)

A debug message, indicating that when RecursiveQuery::resolve queried the cache, a single RRset was found which was put in the answer. The instance number at the end of the message indicates which of the two resolve() methods has been called.

RESLIB_RTT round-trip time of last query calculated as %1 ms

A debug message giving the round-trip time of the last query and response.

RESLIB_RUNQ_CACHE_FIND found <%1> in the cache

This is a debug message and indicates that a RunningQuery object found the specified <name, class, type> tuple in the cache.

RESLIB_RUNQ_CACHE_LOOKUP looking up <%1> in the cache

This is a debug message and indicates that a RunningQuery object has made a call to its doLookup() method to look up the specified <name, class, type> tuple, the first action of which will be to examine the cache.

RESLIB_RUNQ_FAIL failure callback - nameservers are unreachable

A debug message indicating that a RunningQuery's failure callback has been called because all nameservers for the zone in question are unreachable.

RESLIB_RUNQ_SUCCESS success callback - sending query to %1

A debug message indicating that a RunningQuery's success callback has been called because a nameserver has been found, and that a query is being sent to the specified nameserver.

RESLIB_TCP_TRUNCATED TCP response to query for %1 was truncated

This is a debug message logged when a response to the specified query to an upstream nameserver returned a response with the TC (truncation) bit set. This is treated as an error by the code.

RESLIB_TEST_SERVER setting test server to %1(%2)

This is a warning message only generated in unit tests. It indicates that all upstream queries from the resolver are being routed to the specified server, regardless of the address of the nameserver to which the query would normally be routed. If seen during normal operation, please submit a bug report.

RESLIB_TEST_UPSTREAM sending upstream query for <%1> to test server at %2

This is a debug message and should only be seen in unit tests. A query for the specified <name, class, type> tuple is being sent to a test nameserver whose address is given in the message.

RESLIB_TIMEOUT query <%1> to %2 timed out

A debug message indicating that the specified upstream query has timed out and there are no retries left.

RESLIB_TIMEOUT_RETRY query <%1> to %2 timed out, re-trying (retries left: %3)

A debug message indicating that the specified query has timed out and that the resolver is repeating the query to the same nameserver. After this repeated query, there will be the indicated number of retries left.

RESLIB_TRUNCATED response to query for <%1> was truncated, re-querying over TCP

A debug message, this indicates that the response to the specified query was truncated and that the resolver will be re-querying over TCP. There are various reasons why responses may be truncated, so this message is normal and gives no cause for concern.

RESLIB_UPSTREAM sending upstream query for <%1> to %2

A debug message indicating that a query for the specified <name, class, type> tuple is being sent to a nameserver whose address is given in the message.

RESOLVER_AXFR_TCP AXFR request received over TCP

This is a debug message output when the resolver received a request for an AXFR (full transfer of a zone) over TCP. Only authoritative servers are able to handle AXFR requests, so the resolver will return an error message to the sender with the RCODE set to NOTIMP.

RESOLVER_AXFR_UDP AXFR request received over UDP

This is a debug message output when the resolver received a request for an AXFR (full transfer of a zone) over UDP. Only authoritative servers are able to handle AXFR requests (and in any case, an AXFR request should be sent over TCP), so the resolver will return an error message to the sender with the RCODE set to NOTIMP.

RESOLVER_CLIENT_TIME_SMALL client timeout of %1 is too small

During the update of the resolver's configuration parameters, the value of the client timeout was found to be too small. The configuration update was abandoned and the parameters were not changed.

RESOLVER_CONFIG_CHANNEL configuration channel created

This is a debug message output when the resolver has successfully established a connection to the configuration channel.

RESOLVER_CONFIG_ERROR error in configuration: %1

An error was detected in a configuration update received by the resolver. This may be in the format of the configuration message (in which case this is a programming error) or it may be in the data supplied (in which case it is a user error). The reason for the error, included in the message, will give more details. The configuration update is not applied and the resolver parameters were not changed.

RESOLVER_CONFIG_LOADED configuration loaded

This is a debug message output when the resolver configuration has been successfully loaded.

RESOLVER_CONFIG_UPDATED configuration updated: %1

This is a debug message output when the resolver configuration is being updated with the specified information.

RESOLVER_CREATED main resolver object created

This is a debug message indicating that the main resolver object has been created.

RESOLVER_DNS_MESSAGE_RECEIVED DNS message received: %1

This is a debug message from the resolver listing the contents of a received DNS message.

RESOLVER_DNS_MESSAGE_SENT DNS message of %1 bytes sent: %2

This is a debug message containing details of the response returned by the resolver to the querying system.

RESOLVER_FAILED resolver failed, reason: %1

This is an error message output when an unhandled exception is caught by the resolver. After this, the resolver will shut itself down. Please submit a bug report.

RESOLVER_FORWARD_ADDRESS setting forward address %1(%2)

If the resolver is running in forward mode, this message will appear during startup to list the forward address. If multiple addresses are specified, it will appear once for each address.

RESOLVER_FORWARD_QUERY processing forward query

This is a debug message indicating that a query received by the resolver has passed a set of checks (message is well-formed, it is allowed by the ACL, it is a supported opcode, etc.) and is being forwarded to upstream servers.

RESOLVER_HEADER_PROCESSING_FAILED message received, exception when processing header: %1

This is a debug message from the resolver noting that an exception occurred during the processing of a received packet. The packet has been dropped.

RESOLVER_IXFR IXFR request received

This is a debug message indicating that the resolver received a request for an IXFR (incremental transfer of a zone). Only authoritative servers are able to handle IXFR requests, so the resolver will return an error message to the sender with the RCODE set to NOTIMP.

RESOLVER_LOOKUP_TIME_SMALL lookup timeout of %1 is too small

During the update of the resolver's configuration parameters, the value of the lookup timeout was found to be too small. The configuration update will not be applied.

RESOLVER_MESSAGE_PROCESSING_FAILED error parsing received message: %1 - returning %2

This is a debug message noting that parsing of the body of a received message by the resolver failed due to some error (although the parsing of the header succeeded). The message parameters give a textual description of the problem and the RCODE returned.

RESOLVER_NEGATIVE_RETRIES negative number of retries (%1) specified in the configuration

This error is issued when a resolver configuration update has specified a negative retry count: only zero or positive values are valid. The configuration update was abandoned and the parameters were not changed.

RESOLVER_NON_IN_PACKET non-IN class (%1) request received, returning REFUSED message

This debug message is issued when resolver has received a DNS packet that was not IN (Internet) class. The resolver cannot handle such packets, so is returning a REFUSED response to the sender.

RESOLVER_NORMAL_QUERY processing normal query

This is a debug message indicating that the query received by the resolver has passed a set of checks (message is well-formed, it is allowed by the ACL, it is a supported opcode, etc.) and is being processed by the resolver.

RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative

The resolver has received a NOTIFY message. As the server is not authoritative it cannot process it, so it returns an error message to the sender with the RCODE set to NOTAUTH.

RESOLVER_NOT_ONE_QUESTION query contained %1 questions, exactly one question was expected

This debug message indicates that the resolver received a query that contained the number of entries in the question section detailed in the message. This is a malformed message, as a DNS query must contain only one question. The resolver will return a message to the sender with the RCODE set to FORMERR.

RESOLVER_NO_ROOT_ADDRESS no root addresses available

A warning message issued during resolver startup, this indicates that no root addresses have been set. This may be because the resolver will get them from a priming query.

RESOLVER_PRINT_COMMAND print message command, arguments are: %1

This debug message is logged when a "print_message" command is received by the resolver over the command channel.

RESOLVER_PROTOCOL_BODY_PARSE_FAILED protocol error parsing received message: %1 - returning %2

This is a debug message noting that the resolver received a message and the parsing of the body of the message failed due to some protocol error (although the parsing of the header succeeded). The message parameters give a textual description of the problem and the RCODE returned.

RESOLVER_QUERY_ACCEPTED query accepted: '%1/%2/%3' from %4

This debug message is produced by the resolver when an incoming query is accepted in terms of the query ACL. The log message shows the query in the form of <query name>/<query type>/<query class>, and the client that sends the query in the form of <Source IP address>#<source port>.

RESOLVER_QUERY_DROPPED query dropped: '%1/%2/%3' from %4

This is an informational message that indicates an incoming query has been dropped by the resolver because of the query ACL. Unlike the RESOLVER_QUERY_REJECTED case, the server does not return any response. The log message shows the query in the form of <query name>/<query type>/<query class>, and the client that sends the query in the form of <Source IP address>#<source port>.

RESOLVER_QUERY_REJECTED query rejected: '%1/%2/%3' from %4

This is an informational message that indicates an incoming query has been rejected by the resolver because of the query ACL. This results in a response with an RCODE of REFUSED. The log message shows the query in the form of <query name>/<query type>/<query class>, and the client that sends the query in the form of <Source IP address>#<source port>.

RESOLVER_QUERY_SETUP query setup

This is a debug message noting that the resolver is creating a RecursiveQuery object.

RESOLVER_QUERY_SHUTDOWN query shutdown

This is a debug message noting that the resolver is destroying a RecursiveQuery object.

RESOLVER_QUERY_TIME_SMALL query timeout of %1 is too small

During the update of the resolver's configuration parameters, the value of the query timeout was found to be too small. The configuration parameters were not changed.

RESOLVER_RECEIVED_MESSAGE resolver has received a DNS message

This is a debug message indicating that the resolver has received a DNS message. Depending on the debug settings, subsequent log output will indicate the nature of the message.

RESOLVER_RECURSIVE running in recursive mode

This is an informational message that appears at startup noting that the resolver is running in recursive mode.

RESOLVER_SERVICE_CREATED service object created

This debug message is output when resolver creates the main service object (which handles the received queries).

RESOLVER_SET_PARAMS query timeout: %1, client timeout: %2, lookup timeout: %3, retry count: %4

This debug message lists the parameters being set for the resolver. These are: query timeout: the timeout (in ms) used for queries originated by the resolver to upstream servers. Client timeout: the interval to resolve a query by a client: after this time, the resolver sends back a SERVFAIL to the client whilst continuing to resolve the query. Lookup timeout: the time at which the resolver gives up trying to resolve a query. Retry count: the number of times the resolver will retry a query to an upstream server if it gets a timeout.

The client and lookup timeouts require a bit more explanation. The resolution of the client query might require a large number of queries to upstream nameservers. Even if none of these queries timeout, the total time taken to perform all the queries may exceed the client timeout. When this happens, a SERVFAIL is returned to the client, but the resolver continues with the resolution process; data received is added to the cache. However, there comes a time - the lookup timeout - when even the resolver gives up. At this point it will wait for pending upstream queries to complete or timeout and drop the query.

RESOLVER_SET_QUERY_ACL query ACL is configured

This debug message is generated when a new query ACL is configured for the resolver.

RESOLVER_SET_ROOT_ADDRESS setting root address %1(%2)

This message gives the address of one of the root servers used by the resolver. It is output during startup and may appear multiple times, once for each root server address.

RESOLVER_SHUTDOWN resolver shutdown complete

This informational message is output when the resolver has shut down.

RESOLVER_SHUTDOWN_RECEIVED received command to shut down

A debug message noting that the server was asked to terminate and is complying to the request.

RESOLVER_STARTED resolver started

This informational message is output by the resolver when all initialization has been completed and it is entering its main loop.

RESOLVER_STARTING starting resolver with command line '%1'

An informational message, this is output when the resolver starts up.

RESOLVER_UNEXPECTED_RESPONSE received unexpected response, ignoring

This is a debug message noting that the resolver received a DNS response packet on the port on which is it listening for queries. The packet has been ignored.

RESOLVER_UNSUPPORTED_OPCODE opcode %1 not supported by the resolver

This is debug message output when the resolver received a message with an unsupported opcode (it can only process QUERY opcodes). It will return a message to the sender with the RCODE set to NOTIMP.

SOCKETREQUESTOR_CREATED Socket requestor created for application %1

Debug message. A socket requestor (client of the socket creator) is created for the corresponding application. Normally this should happen at most one time throughout the lifetime of the application.

SOCKETREQUESTOR_DESTROYED Socket requestor destroyed

Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED has been destroyed. This event is generally unexpected other than in test cases.

SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6

Debug message. The socket requestor for the corresponding application has requested a socket for a set of address, port and protocol (shown in the log message) and successfully got it from the creator. The corresponding file descriptor and the associated "token" (an internal ID used between the creator and requestor) are shown in the log message.

SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1

Debug message. The socket requestor has released a socket passed by the creator. The associated token of the socket is shown in the log message. If the corresponding SOCKETREQUESTOR_GETSOCKET was logged more detailed information of the socket can be identified by matching the token.

SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1

This points to an error in configuration. What was supposed to be a list of IP address - port pairs isn't a list at all but something else.

SRVCOMM_ADDRESS_FAIL failed to listen on addresses (%1)

The server failed to bind to one of the address/port pair it should according to configuration, for reason listed in the message (usually because that pair is already used by other service or missing privileges). The server will try to recover and bind the address/port pairs it was listening to before (if any).

SRVCOMM_ADDRESS_MISSING address specification is missing "address" or "port" element in %1

This points to an error in configuration. An address specification in the configuration is missing either an address or port and so cannot be used. The specification causing the error is given in the message.

SRVCOMM_ADDRESS_TYPE address specification type is invalid in %1

This points to an error in configuration. An address specification in the configuration malformed. The specification causing the error is given in the message. A valid specification contains an address part (which must be a string and must represent a valid IPv4 or IPv6 address) and port (which must be an integer in the range valid for TCP/UDP ports on your system).

SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1)

The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for the reason listed.

The condition indicates problems with the server and/or the system on which it is running. The server will continue running to allow reconfiguration, but will not be listening on any address or port until an administrator does so.

SRVCOMM_ADDRESS_VALUE address to set: %1:%2

Debug message. This lists one address and port value of the set of addresses we are going to listen on (eg. there will be one log message per pair). This appears only after SRVCOMM_SET_LISTEN, but might be hidden, as it has higher debug level.

SRVCOMM_EXCEPTION_ALLOC exception when allocating a socket: %1

The process tried to allocate a socket using the socket creator, but an error occurred. But it is not one of the errors we are sure are "safe". In this case it is unclear if the unsuccessful communication left the process and the bind10 process in inconsistent state, so the process is going to abort to prevent further problems in that area.

This is probably a bug in the code, but it could be caused by other unusual conditions (like insufficient memory, deleted socket file used for communication).

SRVCOMM_KEYS_DEINIT deinitializing TSIG keyring

Debug message indicating that the server is deinitializing the TSIG keyring.

SRVCOMM_KEYS_INIT initializing TSIG keyring

Debug message indicating that the server is initializing the global TSIG keyring. This should be seen only at server start.

SRVCOMM_KEYS_UPDATE updating TSIG keyring

Debug message indicating new keyring is being loaded from configuration (either on startup or as a result of configuration update).

SRVCOMM_PORT_RANGE port out of valid range (%1 in %2)

This points to an error in configuration. The port in an address specification is outside the valid range of 0 to 65535.

SRVCOMM_SET_LISTEN setting addresses to listen to

Debug message, noting that the server is about to start listening on a different set of IP addresses and ports than before.

SRVCOMM_UNKNOWN_EXCEPTION_ALLOC unknown exception when allocating a socket

The situation is the same as in the SRVCOMM_EXCEPTION_ALLOC case, but further details about the error are unknown, because it was signaled by throwing something not being an exception. This is definitely a bug.

STATSHTTPD_BAD_OPTION_VALUE bad command line argument: %1

The stats-httpd module was called with a bad command-line argument and will not start.

STATSHTTPD_CC_SESSION_ERROR error connecting to message bus: %1

The stats-httpd module was unable to connect to the BIND 10 command and control bus. A likely problem is that the message bus daemon (b10-msgq) is not running. The stats-httpd module will now shut down.

STATSHTTPD_CLOSING closing %1

The stats-httpd daemon will stop listening for requests on the given address and port number.

STATSHTTPD_CLOSING_CC_SESSION stopping cc session

Debug message indicating that the stats-httpd module is disconnecting from the command and control bus.

STATSHTTPD_EXITING exiting

The stats HTTP server is exiting.

STATSHTTPD_HANDLE_CONFIG reading configuration: %1

The stats-httpd daemon has received new configuration data and will now process it. The (changed) data is printed.

STATSHTTPD_HTTPLOG %1 %2

Debug HTTP log message. These are the messages logged by the http server instance. For most logs, the message shows HTTP client and query information like HTTP method, URI, and status code, but the http server can also log other information, such as extended status reports.

STATSHTTPD_RECEIVED_SHUTDOWN_COMMAND shutdown command received

A shutdown command was sent to the stats-httpd module, and it will now shut down.

STATSHTTPD_RECEIVED_STATUS_COMMAND received command to return status

A status command was sent to the stats-httpd module, and it will respond with 'Stats Httpd is up.' and its PID.

STATSHTTPD_RECEIVED_UNKNOWN_COMMAND received unknown command: %1

An unknown command has been sent to the stats-httpd module. The stats-httpd module will respond with an error, and the command will be ignored.

STATSHTTPD_SERVER_DATAERROR HTTP server data error: %1

An internal error occurred while handling an HTTP request. An HTTP 404 response will be sent back, and the specific error is printed. This is an error condition that likely points the specified data corresponding to the requested URI is incorrect.

STATSHTTPD_SERVER_ERROR HTTP server error: %1

An internal error occurred while handling an HTTP request. An HTTP 500 response will be sent back, and the specific error is printed. This is an error condition that likely points to a module that is not responding correctly to statistics requests.

STATSHTTPD_SERVER_INIT_ERROR HTTP server initialization error: %1

There was a problem initializing the HTTP server in the stats-httpd module upon receiving its configuration data. The most likely cause is a port binding problem or a bad configuration value. The specific error is printed in the message. The new configuration is ignored, and an error is sent back.

STATSHTTPD_SHUTDOWN shutting down

The stats-httpd daemon is shutting down.

STATSHTTPD_STARTED listening on %1

The stats-httpd daemon will now start listening for requests on the given address and port number.

STATSHTTPD_STARTING_CC_SESSION starting cc session

Debug message indicating that the stats-httpd module is connecting to the command and control bus.

STATSHTTPD_START_SERVER_INIT_ERROR HTTP server initialization error: %1

There was a problem initializing the HTTP server in the stats-httpd module upon startup. The most likely cause is that it was not able to bind to the listening port. The specific error is printed, and the module will shut down.

STATSHTTPD_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the stats-httpd daemon. The daemon will now shut down.

STATSHTTPD_UNKNOWN_CONFIG_ITEM unknown configuration item: %1

The stats-httpd daemon received a configuration update from the configuration manager. However, one of the items in the configuration is unknown. The new configuration is ignored, and an error is sent back. As possible cause is that there was an upgrade problem, and the stats-httpd version is out of sync with the rest of the system.

STATS_BAD_OPTION_VALUE bad command line argument: %1

The stats module was called with a bad command-line argument and will not start.

STATS_CC_SESSION_ERROR error connecting to message bus: %1

The stats module was unable to connect to the BIND 10 command and control bus. A likely problem is that the message bus daemon (b10-msgq) is not running. The stats module will now shut down.

STATS_EXITING exiting

The stats module process is exiting.

STATS_RECEIVED_INVALID_STATISTICS_DATA received invalid statistics data from %1

Invalid statistics data has been received from the module while polling and it has been discarded.

STATS_RECEIVED_NEW_CONFIG received new configuration: %1

This debug message is printed when the stats module has received a configuration update from the configuration manager.

STATS_RECEIVED_SHOWSCHEMA_ALL_COMMAND received command to show all statistics schema

The stats module received a command to show all statistics schemas of all modules.

STATS_RECEIVED_SHOWSCHEMA_NAME_COMMAND received command to show statistics schema for %1

The stats module received a command to show the specified statistics schema of the specified module.

STATS_RECEIVED_SHOW_ALL_COMMAND received command to show all statistics

The stats module received a command to show all statistics that it has collected.

STATS_RECEIVED_SHOW_NAME_COMMAND received command to show statistics for %1

The stats module received a command to show the statistics that it has collected for the given item.

STATS_RECEIVED_SHUTDOWN_COMMAND shutdown command received

A shutdown command was sent to the stats module and it will now shut down.

STATS_RECEIVED_STATUS_COMMAND received command to return status

A status command was sent to the stats module. It will return a response indicating that it is running normally.

STATS_RECEIVED_UNKNOWN_COMMAND received unknown command: %1

An unknown command has been sent to the stats module. The stats module will respond with an error and the command will be ignored.

STATS_SEND_STATISTICS_REQUEST requesting %1 to send statistics

This debug message is printed when a request is sent to the module to send its data to the stats module.

STATS_SKIP_COLLECTING skipped collecting statistics from %1

The stats module temporarily encountered an internal messaging bus error while collecting statistics from the module, then it skipped collecting statistics from it and will try to collect from the next module. The lack of statistics will be recovered at the next polling round.

STATS_SKIP_POLLING skipped polling statistics to modules

The stats module temporarily encountered an internal messaging bus error while collecting initial information to collect statistics from the init module, then it skipped polling statistics and will try to do next time.

STATS_STARTING starting

The stats module will be now starting.

STATS_START_ERROR stats module error: %1

An internal error occurred while starting the stats module. The stats module will be now shutting down.

STATS_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the stats module. The daemon will now shut down.

STATS_UNKNOWN_COMMAND_IN_SPEC unknown command in specification file: %1

The specification file for the stats module contains a command that is unknown in the implementation. The most likely cause is an installation problem, where the specification file stats.spec is from a different version of BIND 10 than the stats module itself. Please check your installation.

USER_CHK_HOOK_LOAD_ERROR DHCP UserCheckHook could not be loaded: %1

This is an error message issued when the DHCP UserCheckHook could not be loaded. The exact cause should be explained in the log message. User subnet selection will revert to default processing.

USER_CHK_HOOK_UNLOAD_ERROR DHCP UserCheckHook an error occurred unloading the library: %1

This is an error message issued when an error occurs while unloading the UserCheckHook library. This is unlikely to occur and normal operations of the library will likely resume when it is next loaded.

USER_CHK_SUBNET4_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet4_select callout: %1

This is an error message issued when the DHCP UserCheckHook subnet4_select hook encounters an unexpected error. The message should contain a more detailed explanation.

USER_CHK_SUBNET4_SELECT_REGISTRY_NULL DHCP UserCheckHook UserRegistry has not been created.

This is an error message issued when the DHCP UserCheckHook subnet4_select hook has been invoked but the UserRegistry has not been created. This is a programmatic error and should not occur.

USER_CHK_SUBNET6_SELECT_ERROR DHCP UserCheckHook an unexpected error occured in subnet6_select callout: %1

This is an error message issued when the DHCP UserCheckHook subnet6_select hook encounters an unexpected error. The message should contain a more detailed explanation.

USER_CHK_SUBNET6_SELECT_REGISTRY_NULL DHCP UserCheckHook UserRegistry has not been created.

This is an error message issued when the DHCP UserCheckHook subnet6_select hook has been invoked but the UserRegistry has not been created. This is a programmatic error and should not occur.

XFRIN_AUTH_LOADZONE sending Auth loadzone for origin=%1, class=%2

There was a successful zone transfer. We send the "loadzone" command for the zone to b10-auth.

XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received

The serial fields of the first and last SOAs of AXFR (including AXFR-style IXFR) are not the same. According to RFC 5936 these two SOAs must be the "same" (not only for the serial), but it is still not clear what the receiver should do if this condition does not hold. There was a discussion about this at the IETF dnsext working group: http://www.ietf.org/mail-archive/web/dnsext/current/msg07908.html and the general feeling seems that it would be better to reject the transfer if a mismatch is detected. On the other hand, also as noted in that email thread, neither BIND 9 nor NSD performs any comparison on the SOAs. For now, we only check the serials (ignoring other fields) and only leave a warning log message when a mismatch is found. If it turns out to happen with a real world primary server implementation and that server actually feeds broken data (e.g. mixed versions of zone), we can consider a stricter action.

XFRIN_BAD_MASTER_ADDR_FORMAT bad format for master address: %1

The given master address is not a valid IP address.

XFRIN_BAD_MASTER_PORT_FORMAT bad format for master port: %1

The master port as read from the configuration is not a valid port number.

XFRIN_BAD_TSIG_KEY_STRING bad TSIG key string: %1

The TSIG key string as read from the configuration does not represent a valid TSIG key. The key is ignored.

XFRIN_BAD_ZONE_CLASS Invalid zone class: %1

The zone class as read from the configuration is not a valid DNS class.

XFRIN_CC_SESSION_ERROR error reading from cc channel: %1

There was a problem reading from the command and control channel. The most likely cause is that xfrin the msgq daemon is not running.

XFRIN_COMMAND_ERROR error while executing command '%1': %2

There was an error while the given command was being processed. The error is given in the log message.

XFRIN_CONNECT_MASTER error connecting to master at %1 for %2: %3

There was an error opening a connection to the master for the specified zone. The error is shown in the log message.

XFRIN_DATASRC_CONFIG_ERROR failed to update data source configuration: %1

Configuration for the global data sources is updated, but the update cannot be applied to xfrin. The xfrin module will still keep running with the previous configuration, but the cause of the failure and other log messages must be carefully examined because if only xfrin rejects the new configuration then the entire BIND 10 system will have inconsistent state among different modules. If other modules accept the update but xfrin produces this error, the xfrin module should probably be restarted.

XFRIN_DATASRC_UNKNOWN data source to transfer %1 to is unknown

The xfrin daemon received a command that would trigger a transfer, but could not find a data source where the specified zone belongs. There can be several reasons for this error: it may be a simple misspelling in the xfrin or zonemgr configuration, or in the user supplied parameter if it is triggered by an external command (such as from bindctl). Another possibility is that this is the initial transfer for a newly setup secondary zone. In this case at least an initial empty zone must be created in one of configured data sources. This can be done by the -e option of b10-loadzone.

XFRIN_EXITING exiting

The xfrin daemon is exiting.

XFRIN_GOT_INCREMENTAL_RESP got incremental response for %1

In an attempt of IXFR processing, the beginning SOA of the first difference (following the initial SOA that specified the final SOA for all the differences) was found. This means a connection for xfrin tried IXFR and really got a response for incremental updates.

XFRIN_GOT_NONINCREMENTAL_RESP got nonincremental response for %1

Non incremental transfer was detected at the "first data" of a transfer, which is the RR following the initial SOA. Non incremental transfer is either AXFR or AXFR-style IXFR. In the latter case, it means that in a response to IXFR query the first data is not SOA or its SOA serial is not equal to the requested SOA serial.

XFRIN_IMPORT_DNS error importing python DNS module: %1

There was an error importing the python DNS module pydnspp. The most likely cause is a PYTHONPATH problem.

XFRIN_INITIAL_AXFR no SOA available for %1 yet, requesting AXFR of initial version from %2

On starting the zone transfer, it's detected that there is no SOA record available for the zone. This is always the case for the very first transfer or if the administrator has removed the locally copied data by hand for some reason. In this case trying IXFR does not make sense for the obvious reason, so AXFR will be used from the beginning, regardless of the request_ixfr configuration (even if "only" is specified).

XFRIN_INITIAL_IXFR requesting IXFR for %1 from %2

IXFR will be used for the initial request type for the specified zone transfer. It will fall back to AXFR if the initial request fails (and unless specified not to do so by configuration).

XFRIN_INITIAL_IXFR_DISABLED IXFR disabled for %1, requesting AXFR from %2

The use of IXFR is disabled by configuration for the specified zone, so only AXFR will be tried.

XFRIN_INVALID_ZONE_DATA zone %1 received from %2 is broken and unusable

The zone was received, but it failed sanity validation. The previous version of zone (if any is available) will be used. Look for previous XFRIN_ZONE_INVALID messages to see the exact problem(s).

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)

The IXFR transfer for the given zone was successful. The provided information contains the following values:

messages: Number of overhead DNS messages in the transfer.

changesets: Number of difference sequences.

deletions: Number of Resource Records deleted by all the changesets combined, including the SOA records.

additions: Number of Resource Records added by all the changesets combined, including the SOA records.

bytes: Full size of the transfer data on the wire.

run time: Time (in seconds) the complete ixfr took.

bytes/second: Transfer speed.

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).

XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating

The first SOA record in an IXFR response indicates the zone's serial at the primary server is not newer than the client's. This is basically unexpected event because normally the client first checks the SOA serial by an SOA query, but can still happen if the transfer is manually invoked or (although unlikely) there is a rapid change at the primary server between the SOA and IXFR queries. The client implementation confirms the whole response is this single SOA, and aborts the transfer just like a successful case.

XFRIN_MSGQ_SEND_ERROR (with TSIG %1) error while contacting %2 and %3

There was a problem sending a message to the xfrout module or the zone manager. This most likely means that the msgq daemon has quit or was killed.

XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER (with TSIG %1) error while contacting %2

There was a problem sending a message to the zone manager. This most likely means that the msgq daemon has quit or was killed.

XFRIN_NOTIFY_UNKNOWN_MASTER got notification to retransfer zone %1 from %2, expected %3

The system received a notify for the given zone, but the address it came from does not match the master address in the Xfrin configuration. The notify is ignored. This may indicate that the configuration for the master is wrong, that a wrong machine is sending notifies, or that fake notifies are being sent.

XFRIN_RECEIVED_COMMAND received command: %1

The xfrin daemon received a command on the command channel.

XFRIN_RETRANSFER_UNKNOWN_ZONE got notification to retransfer unknown zone %1

There was an internal command to retransfer the given zone, but the zone is not known to the system. This may indicate that the configuration for xfrin is incomplete, or there was a typographical error in the zone name in the configuration.

XFRIN_STARTED xfrin started

This informational message is output by xfrin when all initialization has been completed and it is entering its main loop.

XFRIN_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the xfrin daemon. The daemon will now shut down.

XFRIN_TRANSFER_SUCCESS full %1 transfer of zone %2 succeeded (messages: %3, records: %4, bytes: %5, run time: %6 seconds, %7 bytes/second)

The AXFR transfer of the given zone was successful. The provided information contains the following values:

messages: Number of overhead DNS messages in the transfer.

records: Number of Resource Records in the full transfer, excluding the final SOA record that marks the end of the AXFR.

bytes: Full size of the transfer data on the wire.

run time: Time (in seconds) the complete axfr took.

bytes/second: Transfer speed.

XFRIN_TSIG_KEY_NOT_FOUND TSIG key not found in key ring: %1

An attempt to start a transfer with TSIG was made, but the configured TSIG key name was not found in the TSIG key ring (configuration option tsig_keys/keys). The transfer is aborted. The key name that could not be found is shown in the log message. Check the configuration and the TSIG key ring.

XFRIN_UNKNOWN_ERROR unknown error: %1

An uncaught exception was raised while running the xfrin daemon. The exception message is printed in the log message.

XFRIN_XFR_OTHER_FAILURE %1 transfer of zone %2 failed: %3

The XFR transfer for the given zone has failed due to a problem outside of the xfrin module. Possible reasons are a broken DNS message or failure in database connection. The error is shown in the log message. One common cause of this error could be a locked database; especially when using sqlite3 where a single transaction involving write operations blocks any other read or write transactions. This is not a critical error, and the transfer will be attempted again at the next retry time.

XFRIN_XFR_PROCESS_FAILURE %1 transfer of zone %2/%3 failed: %4

An XFR session failed outside the main protocol handling. This includes an error at the data source level at the initialization phase, unexpected failure in the network connection setup to the master server, or even more unexpected failure due to unlikely events such as memory allocation failure. Details of the error are shown in the log message. In general, these errors are not really expected ones, and indicate an installation error or a program bug. The session handler thread tries to clean up all intermediate resources even on these errors, but it may be incomplete. So, if this log message continuously appears, system resource consumption should be checked, and you may even want to disable the corresponding transfers. You may also want to file a bug report if this message appears so often.

XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4

The XFR transfer for the given zone has failed due to an internal error. The error is shown in the log message.

XFRIN_XFR_TRANSFER_FALLBACK (with TSIG %1) falling back from IXFR to AXFR for %2

The IXFR transfer of the given zone failed. This might happen in many cases, such that the remote server doesn't support IXFR, we don't have the SOA record (or the zone at all), we are out of sync, etc. In many of these situations, AXFR could still work. Therefore we try that one in case it helps.

XFRIN_XFR_TRANSFER_FALLBACK_DISABLED (with TSIG %1) suppressing fallback from IXFR to AXFR for %2

An IXFR transfer of the given zone failed. By default AXFR will be tried next, but this fallback is disabled by configuration, so the whole transfer attempt failed at that point. If the reason for the failure (which should be logged separately) is temporary, this is probably harmless or even desired as another IXFR will take place some time later (without falling back to the possibly expensive AXFR). If this is a permanent error (e.g., some change at the master server completely disables IXFR), the secondary zone will eventually expire, so the configuration should be changed to allow AXFR.

XFRIN_XFR_TRANSFER_PROTOCOL_VIOLATION %1 transfer of zone %2 with %3 failed: %4

The XFR transfer for the given zone has failed due to a protocol error, such as an unexpected response from the primary server. The error is shown in the log message. It may be because the primary server implementation is broken or (although less likely) there was some attack attempt, but it can also happen due to configuration mismatch such as the remote server does not have authority for the zone any more but the local configuration hasn't been updated. So it is recommended to check the primary server configuration.

XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started

A connection to the master server has been made, the serial value in the SOA record has been checked, and a zone transfer has been started.

XFRIN_ZONE_INVALID Newly received zone %1/%2 fails validation: %3

The zone was received successfully, but it failed validation. The problem is severe enough that the new version of zone is discarded and the old version, if any, will stay in use. New transfer will be attempted after some time. The problem needs to be fixed in the zone data on the remote server.

XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs

On starting an xfrin session, it is identified that the zone to be transferred has multiple SOA RRs. Such a zone is broken, but could be accidentally configured especially in a data source using "non captive" backend database. The implementation ignores entire SOA RRs and tries to continue processing as if the zone were empty. This also means AXFR will be used unconditionally, regardless of the configured value for request_ixfr of the zone.

XFRIN_ZONE_NO_SOA Zone %1 does not have SOA

On starting an xfrin session, it is identified that the zone to be transferred does not have an SOA RR in the data source. This is not necessarily an error; if a secondary DNS server first tries to perform transfer from a primary server, the zone can be empty, and therefore doesn't have an SOA. Subsequent AXFR will fill in the zone; if the attempt is IXFR it will fail in query creation.

XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4)

The response to an SOA query prior to xfr indicated that the zone's SOA serial at the primary server is smaller than that of the xfrin client. This is not necessarily an error especially if that particular primary server is another secondary server which hasn't got the latest version of the zone. But if the primary server is known to be the real source of the zone, some unexpected inconsistency may have happened, and you may want to take a closer look. In this case xfrin doesn't perform subsequent zone transfer.

XFRIN_ZONE_WARN Newly received zone %1/%2 has a problem: %3

The zone was received successfully, but when checking it, it was discovered there's some issue with it. It might be correct, but it should be checked and possibly fixed on the remote server. The problem is described in the message. The problem does not stop the zone from being used.

XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1

The TSIG key string as read from the configuration does not represent a valid TSIG key.

XFROUT_CC_SESSION_ERROR error reading from cc channel: %1

There was a problem reading from the command and control channel. The most likely cause is that the msgq daemon is not running.

XFROUT_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response

There was a problem reading a response from another module over the command and control channel. The most likely cause is that the configuration manager b10-cfgmgr is not running.

XFROUT_CONFIG_ERROR error found in configuration data: %1

The xfrout process encountered an error when installing the configuration at startup time. Details of the error are included in the log message.

XFROUT_EXITING exiting

The xfrout daemon is exiting.

XFROUT_FETCH_REQUEST_ERROR socket error while fetching a request from the auth daemon

There was a socket error while contacting the b10-auth daemon to fetch a transfer request. The auth daemon may have shutdown.

XFROUT_HANDLE_QUERY_ERROR error while handling query: %1

There was a general error handling an xfrout query. The error is shown in the message. In principle this error should not appear, and points to an oversight catching exceptions in the right place. However, to ensure the daemon keeps running, this error is caught and reported.

XFROUT_IMPORT error importing python module: %1

There was an error importing a python module. One of the modules needed by xfrout could not be found. This suggests that either some libraries are missing on the system, or the PYTHONPATH variable is not correct. The specific place where this library needs to be depends on your system and your specific installation.

XFROUT_IXFR_MULTIPLE_SOA IXFR client %1: authority section has multiple SOAs

An IXFR request was received with more than one SOA RRs in the authority section. The xfrout daemon rejects the request with an RCODE of FORMERR.

XFROUT_IXFR_NO_JOURNAL_SUPPORT IXFR client %1, %2: journaling not supported in the data source, falling back to AXFR

An IXFR request was received but the underlying data source did not support journaling. The xfrout daemon fell back to AXFR-style IXFR.

XFROUT_IXFR_NO_SOA IXFR client %1: missing SOA

An IXFR request was received with no SOA RR in the authority section. The xfrout daemon rejects the request with an RCODE of FORMERR.

XFROUT_IXFR_NO_VERSION IXFR client %1, %2: version (%3 to %4) not in journal, falling back to AXFR

An IXFR request was received, but the requested range of differences were not found in the data source. The xfrout daemon fell back to AXFR-style IXFR.

XFROUT_IXFR_NO_ZONE IXFR client %1, %2: zone not found with journal

The requested zone in IXFR was not found in the data source even though the xfrout daemon successfully found the SOA RR of the zone in the data source. This can happen if the administrator removed the zone from the data source within the small duration between these operations, but it's more likely to be a bug or broken data source. Unless you know why this message was logged, and especially if it happens often, it's advisable to check whether the data source is valid for this zone. The xfrout daemon considers it a possible, though unlikely, event, and returns a response with an RCODE of NOTAUTH.

XFROUT_IXFR_UPTODATE IXFR client %1, %2: client version is new enough (theirs=%3, ours=%4)

An IXFR request was received, but the client's SOA version is the same as or newer than that of the server. The xfrout server responds to the request with the answer section being just one SOA of that version.

XFROUT_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1

There was a problem in the lower level module handling configuration and control commands. This could happen for various reasons, but the most likely cause is that the configuration database contains a syntax error and xfrout failed to start at initialization. A detailed error message from the module will also be displayed.

XFROUT_NEW_CONFIG Update xfrout configuration

New configuration settings have been sent from the configuration manager. The xfrout daemon will now apply them.

XFROUT_NEW_CONFIG_DONE Update xfrout configuration done

The xfrout daemon is now done reading the new configuration settings received from the configuration manager.

XFROUT_NOTIFY_COMMAND received command to send notifies for %1/%2

The xfrout daemon received a command on the command channel that NOTIFY packets should be sent for the given zone.

XFROUT_PARSE_QUERY_ERROR error parsing query: %1

There was a parse error while reading an incoming query. The parse error is shown in the log message. A remote client sent a packet we do not understand or support. The xfrout request will be ignored. In general, this should only occur for unexpected problems like memory allocation failures, as the query should already have been parsed by the b10-auth daemon, before it was passed here.

XFROUT_PROCESS_REQUEST_ERROR error processing transfer request: %1

There was an error in receiving a transfer request from b10-auth. This is generally an unexpected event, but is possible when, for example, b10-auth terminates in the middle of forwarding the request. When this happens it's unlikely to be recoverable with the same communication session with b10-auth, so b10-xfrout drops it and waits for a new session. In any case, this error indicates that there's something very wrong in the system, so it's advisable to check the over all status of the BIND 10 system.

XFROUT_QUERY_DROPPED %1 client %2: request to transfer %3 dropped

The xfrout process silently dropped a request to transfer zone to given host. This is required by the ACLs. The %2 represents the IP address and port of the peer requesting the transfer, and the %3 represents the zone name and class.

XFROUT_QUERY_QUOTA_EXCEEDED %1 client %2: request denied due to quota (%3)

The xfr request was rejected because the server was already handling the maximum number of allowable transfers as specified in the transfers_out configuration parameter, which is also shown in the log message. The request was immediately responded and terminated with an RCODE of REFUSED. This can happen for a busy xfrout server, and you may want to increase this parameter; if the server is being too busy due to requests from unexpected clients you may want to restrict the legitimate clients with ACL.

XFROUT_QUERY_REJECTED %1 client %2: request to transfer %3 rejected

The xfrout process rejected (by REFUSED rcode) a request to transfer zone to given host. This is because of ACLs. The %2 represents the IP address and port of the peer requesting the transfer, and the %3 represents the zone name and class.

XFROUT_RECEIVED_GETSTATS_COMMAND received command to send statistics data: %1

The xfrout daemon received a command on the command channel that statistics data should be sent to the stats daemon.

XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received

The xfrout daemon received a shutdown command from the command channel and will now shut down.

XFROUT_RECEIVE_FD_FAILED error receiving the file descriptor for an XFR connection

There was an error receiving the file descriptor for the transfer request from b10-auth. There can be several reasons for this, but the most likely cause is that b10-auth terminates for some reason (maybe it's a bug of b10-auth, maybe it's an intentional restart by the administrator), so depending on how this happens it may or may not be a serious error. But in any case this is not expected to happen frequently, and it's advisable to figure out how this happened if this message is logged. Even if this error happens xfrout will reset its internal state and will keep receiving further requests. So if it's just a temporary restart of b10-auth the administrator does not have to do anything.

XFROUT_REMOVE_OLD_UNIX_SOCKET_FILE_ERROR error removing unix socket file %1: %2

The unix socket file xfrout needs for contact with the auth daemon already exists, and needs to be removed first, but there is a problem removing it. It is likely that we do not have permission to remove this file. The specific error is show in the log message. The xfrout daemon will shut down.

XFROUT_REMOVE_UNIX_SOCKET_FILE_ERROR error clearing unix socket file %1: %2

When shutting down, the xfrout daemon tried to clear the unix socket file used for communication with the auth daemon. It failed to remove the file. The reason for the failure is given in the error message.

XFROUT_SOCKET_SELECT_ERROR error while calling select() on request socket: %1

There was an error while calling select() on the socket that informs the xfrout daemon that a new xfrout request has arrived. This should be a result of rare local error such as memory allocation failure and shouldn't happen under normal conditions. The error is included in the log message.

XFROUT_STARTED xfrout started

This informational message is output by xfrout when all initialization has been completed and it is entering its main loop.

XFROUT_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the xfrout daemon. The daemon will now shut down.

XFROUT_STOPPING the xfrout daemon is shutting down

The current transfer is aborted, as the xfrout daemon is shutting down.

XFROUT_UNIX_SOCKET_FILE_IN_USE another xfrout process seems to be using the unix socket file %1

While starting up, the xfrout daemon tried to clear the unix domain socket needed for contacting the b10-auth daemon to pass requests on, but the file is in use. The most likely cause is that another xfrout daemon process is still running. This xfrout daemon (the one printing this message) will not start.

XFROUT_XFR_TRANSFER_CHECK_ERROR %1 client %2: check for transfer of %3 failed: %4

Pre-response check for an incoming XFR request failed unexpectedly. The most likely cause of this is that some low level error in the data source, but it may also be other general (more unlikely) errors such as memory shortage. Some detail of the error is also included in the message. The xfrout server tries to return a SERVFAIL response in this case.

XFROUT_XFR_TRANSFER_DONE %1 client %2: transfer of %3 complete

The transfer of the given zone has been completed successfully, or was aborted due to a shutdown event.

XFROUT_XFR_TRANSFER_ERROR %1 client %2: error transferring zone %3: %4

An uncaught exception was encountered while sending the response to an AXFR query. The error message of the exception is included in the log message, but this error most likely points to incomplete exception handling in the code.

XFROUT_XFR_TRANSFER_FAILED %1 client %2: transfer of %3 failed, rcode: %4

A transfer out for the given zone failed. An error response is sent to the client. The given rcode is the rcode that is set in the error response. This is either NOTAUTH (we are not authoritative for the zone), SERVFAIL (our internal database is missing the SOA record for the zone), or REFUSED (the limit of simultaneous outgoing AXFR transfers, as specified by the configuration value Xfrout/max_transfers_out, has been reached).

XFROUT_XFR_TRANSFER_STARTED %1 client %2: transfer of zone %3 has started

A transfer out of the given zone has started.

ZONEMGR_CCSESSION_ERROR command channel session error: %1

An error was encountered on the command channel. The message indicates the nature of the error.

ZONEMGR_DATASRC_CONFIG_ERROR failed to update data source configuration: %1

Configuration for the global data sources is updated, but the update cannot be applied to zonemgr. The zonemgr module will still keep running with the previous configuration, but the cause of the failure and other log messages must be carefully examined because if only zonemgr rejects the new configuration then the entire BIND 10 system will have inconsistent state among different modules. If other modules accept the update but zonemgr produces this error, the zonemgr module should probably be restarted.

ZONEMGR_JITTER_TOO_BIG refresh_jitter is too big, setting to 0.5

The value specified in the configuration for the refresh jitter is too large so its value has been set to the maximum of 0.5.

ZONEMGR_KEYBOARD_INTERRUPT exiting zonemgr process as result of keyboard interrupt

An informational message output when the zone manager was being run at a terminal and it was terminated via a keyboard interrupt signal.

ZONEMGR_LOAD_ZONE loading zone %1 (class %2)

This is a debug message indicating that the zone of the specified class is being loaded.

ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master

A command received by the zone manager from the Auth module did not contain the address of the master server from which a NOTIFY message was received. This may be due to an internal programming error; please submit a bug report.

ZONEMGR_NO_SOA zone %1 (class %2) does not have an SOA record

When loading the named zone of the specified class the zone manager discovered that the data did not contain an SOA record. The load has been abandoned.

ZONEMGR_NO_TIMER_THREAD trying to stop zone timer thread but it is not running

An attempt was made to stop the timer thread (used to track when zones should be refreshed) but it was not running. This may indicate an internal program error. Please submit a bug report.

ZONEMGR_NO_ZONE_CLASS internal BIND 10 command did not contain class of zone

A command received by the zone manager from another BIND 10 module did not contain the class of the zone on which the zone manager should act. This may be due to an internal programming error; please submit a bug report.

ZONEMGR_NO_ZONE_NAME internal BIND 10 command did not contain name of zone

A command received by the zone manager from another BIND 10 module did not contain the name of the zone on which the zone manager should act. This may be due to an internal programming error; please submit a bug report.

ZONEMGR_RECEIVE_NOTIFY received NOTIFY command for zone %1 (class %2)

This is a debug message indicating that the zone manager has received a NOTIFY command over the command channel. The command is sent by the Auth process when it is acting as a slave server for the zone and causes the zone manager to record the master server for the zone and start a timer; when the timer expires, the master will be polled to see if it contains new data.

ZONEMGR_RECEIVE_SHUTDOWN received SHUTDOWN command

This is a debug message indicating that the zone manager has received a SHUTDOWN command over the command channel from the Init process. It will act on this command and shut down.

ZONEMGR_RECEIVE_UNKNOWN received unknown command '%1'

This is a warning message indicating that the zone manager has received the stated command over the command channel. The command is not known to the zone manager and although the command is ignored, its receipt may indicate an internal error. Please submit a bug report.

ZONEMGR_RECEIVE_XFRIN_FAILED received XFRIN FAILED command for zone %1 (class %2)

This is a debug message indicating that the zone manager has received an XFRIN FAILED command over the command channel. The command is sent by the Xfrin process when a transfer of zone data into the system has failed, and causes the zone manager to schedule another transfer attempt.

ZONEMGR_RECEIVE_XFRIN_SUCCESS received XFRIN SUCCESS command for zone %1 (class %2)

This is a debug message indicating that the zone manager has received an XFRIN SUCCESS command over the command channel. The command is sent by the Xfrin process when the transfer of zone data into the system has succeeded, and causes the data to be loaded and served by BIND 10.

ZONEMGR_REFRESH_ZONE refreshing zone %1 (class %2)

The zone manager is refreshing the named zone of the specified class with updated information.

ZONEMGR_SELECT_ERROR error with select(): %1

An attempt to wait for input from a socket failed. The failing operation is a call to the operating system's select() function, which failed for the given reason.

ZONEMGR_SEND_FAIL failed to send command to %1, session has been closed

The zone manager attempted to send a command to the named BIND 10 module, but the send failed. The session between the modules has been closed.

ZONEMGR_SESSION_ERROR unable to establish session to command channel daemon

The zonemgr process was not able to be started because it could not connect to the command channel daemon. The most usual cause of this problem is that the daemon is not running.

ZONEMGR_SESSION_TIMEOUT timeout on session to command channel daemon

The zonemgr process was not able to be started because it timed out when connecting to the command channel daemon. The most usual cause of this problem is that the daemon is not running.

ZONEMGR_SHUTDOWN zone manager has shut down

The zone manager has shut down completely.

ZONEMGR_STARTED zonemgr started

This informational message is output by zonemgr when all initialization has been completed and it is entering its main loop.

ZONEMGR_STARTING zone manager starting

A debug message output when the zone manager starts up.

ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running

This message is issued when an attempt is made to start the timer thread (which keeps track of when zones need a refresh) but one is already running. It indicates either an error in the program logic or a problem with stopping a previous instance of the timer. Please submit a bug report.

ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager

An XFRIN operation has failed but the zone that was the subject of the 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.

ZONEMGR_UNKNOWN_ZONE_SUCCESS zone %1 (class %2) is not known to the zone manager

An XFRIN operation has succeeded but the zone received 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.

ZONEMGR_ZONE_NOTIFY_NOT_SECONDARY notify for zone %1/%2 from %3 received but not in secondaries

A NOTIFY was received but the zone is not listed in the configured secondary zones of the zone manager. The most common reason for this is that it's simply received by a primary server of the zone. Another possibility is a configuration error that it's not configured as a secondary while it should be. In either case, the zone manager does not take action in terms of zone management, and the authoritative server will respond to it like in the secondary case. If this is a configuration error, it will be noticed by the fact that the zone isn't updated even after a change is made in the primary server.