The database access string with password redacted is logged, along with the
error and details for the reconnect procedure.
+DCTL_DEPRECATED_OUTPUT_OPTIONS
+==============================
+
+.. code-block:: text
+
+ The output_options parameter is deprecated. Use output-options parameter instead.
+
+This warning message is displayed when deprecated output_options is used instead
+of output-options.
+
DCTL_DEVELOPMENT_VERSION
========================
before the classification was added to Kea is used, or class naming is
inconsistent.
-DHCP4_CLASS_UNDEFINED
-=====================
-
-.. code-block:: text
-
- required class %1 has no definition
-
-Logged at debug log level 40.
-This debug message informs that a class is listed for required evaluation but
-has no definition.
-
-DHCP4_CLASS_UNTESTABLE
-======================
-
-.. code-block:: text
-
- required class %1 has no test expression
-
-Logged at debug log level 40.
-This debug message informs that a class was listed for required evaluation but
-its definition does not include a test expression to evaluate.
-
DHCP4_CLIENTID_IGNORED_FOR_LEASES
=================================
been successfully evaluated. The client class name and the result value of the
evaluation are printed.
+DHCP4_REQUIRED_CLASS_NO_TEST
+============================
+
+.. code-block:: text
+
+ required class %1 has no test expression, adding it to client's classes unconditionally
+
+Logged at debug log level 40.
+This debug message informs that a class was listed for required evaluation but
+its definition does not include a test expression to evaluate. The class is
+unconditionally added to the query.
+
+DHCP4_REQUIRED_CLASS_UNDEFINED
+==============================
+
+.. code-block:: text
+
+ required class %1 has no definition
+
+Logged at debug log level 40.
+This debug message informs that a class is listed for required evaluation but
+has no definition. The class is ignored.
+
DHCP4_RESERVATIONS_LOOKUP_FIRST_ENABLED
=======================================
before the classification was added to Kea is used, or class naming is
inconsistent.
-DHCP6_CLASS_UNDEFINED
-=====================
-
-.. code-block:: text
-
- required class %1 has no definition
-
-Logged at debug log level 40.
-This debug message informs that a class is listed for required evaluation but
-has no definition.
-
-DHCP6_CLASS_UNTESTABLE
-======================
-
-.. code-block:: text
-
- required class %1 has no test expression
-
-Logged at debug log level 40.
-This debug message informs that a class was listed for required evaluation but
-its definition does not include a test expression to evaluate.
-
DHCP6_CONFIG_COMPLETE
=====================
been successfully evaluated. The client class name and the result value of the
evaluation are printed.
+DHCP6_REQUIRED_CLASS_NO_TEST
+============================
+
+.. code-block:: text
+
+ required class %1 has no test expression, adding it to client's classes unconditionally
+
+Logged at debug log level 40.
+This debug message informs that a class was listed for required evaluation but
+its definition does not include a test expression to evaluate. The class is
+unconditionally added to the query.
+
+DHCP6_REQUIRED_CLASS_UNDEFINED
+==============================
+
+.. code-block:: text
+
+ required class %1 has no definition
+
+Logged at debug log level 40.
+This debug message informs that a class is listed for required evaluation but
+has no definition. The class is ignored.
+
DHCP6_REQUIRED_OPTIONS_CHECK_FAIL
=================================
the connection including database name and username needed to access it
(but not the password if any) are logged.
-DHCPSRV_MEMFILE_DELETE_ADDR
-===========================
+DHCPSRV_MEMFILE_DELETE_ADDR4
+============================
+
+.. code-block:: text
+
+ deleting lease for address %1
+
+Logged at debug log level 50.
+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_DELETE_ADDR6
+============================
.. code-block:: text
the same DHCP message multiple times, as it will be received by each socket
individually.
-DHCPSRV_MYSQL_ADD_ADDR4
-=======================
+DHCPSRV_NOTYPE_DB
+=================
.. code-block:: text
- adding IPv4 lease with address %1
+ no 'type' keyword to determine database backend: %1
-Logged at debug log level 50.
-A debug message issued when the server is about to add an IPv4 lease
-with the specified address to the MySQL backend database.
+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_MYSQL_ADD_ADDR6
+DHCPSRV_NO_SOCKETS_OPEN
=======================
.. code-block:: text
- adding IPv6 lease with address %1, lease type %2
+ no interface configured to listen to DHCP traffic
-Logged at debug log level 50.
-A debug message issued when the server is about to add an IPv6 lease
-with the specified address to the MySQL backend database.
+This warning message is issued when the current server configuration specifies
+no interfaces that the server should listen on, or when the specified interfaces are not
+configured to receive the traffic.
-DHCPSRV_MYSQL_COMMIT
-====================
+DHCPSRV_OPEN_SOCKET_FAIL
+========================
.. code-block:: text
- committing to MySQL database
+ failed to open socket: %1
-Logged at debug log level 50.
-The code has issued a commit call. All outstanding transactions will be
-committed to the database. Note that depending on the MySQL settings,
-the commit may not include a write to disk.
+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.
-DHCPSRV_MYSQL_DB
-================
+DHCPSRV_QUEUE_NCR
+=================
.. code-block:: text
- opening MySQL lease database: %1
+ %1: Name change request to %2 DNS entry queued: %3
-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.
+Logged at debug log level 55.
+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 argument
+includes the client identification information. The second argument
+indicates whether the DNS entry is to be added or removed. The third
+argument carries the details of the NameChangeRequest.
-DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED
-=======================================
+DHCPSRV_QUEUE_NCR_FAILED
+========================
.. code-block:: text
- deleted %1 reclaimed leases from the database
+ %1: queuing %2 name change request failed for lease %3: %4
-Logged at debug log level 50.
-A debug message issued when the server has removed a number of reclaimed
-leases from the database. The number of removed leases is included in the
-message.
+This error message is logged when sending a NameChangeRequest
+to DHCP DDNS failed. The first argument includes the client identification
+information. The second argument indicates whether the DNS entry is to be
+added or removed. The third argument specifies the leased address. The
+last argument provides the reason for failure.
-DHCPSRV_MYSQL_DELETE_ADDR
-=========================
+DHCPSRV_QUEUE_NCR_SKIP
+======================
.. code-block:: text
- deleting lease for address %1
+ %1: skip queuing name change request for lease: %2
Logged at debug log level 50.
-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.
+This debug message is issued when the server decides to not queue the name
+change request because the lease doesn't include the FQDN, the forward and
+reverse update is disabled for this lease or the DNS updates are disabled
+in the configuration. The first argument includes the client identification
+information. The second argument includes the leased address.
-DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4
-=======================================
+DHCPSRV_SUBNET4O6_SELECT_FAILED
+===============================
.. code-block:: text
- deleting reclaimed IPv4 leases that expired more than %1 seconds ago
+ Failed to select any subnet for the DHCPv4o6 packet
-Logged at debug log level 50.
-A debug message issued when the server is removing reclaimed DHCPv4
-leases which have expired longer than a specified period of time.
-The argument is the amount of time Kea waits after a reclaimed
-lease expires before considering its removal.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select any subnet for the
+DHCPv4o6 packet.
-DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED6
-=======================================
+DHCPSRV_SUBNET4_SELECT_BY_ADDRESS_NO_MATCH
+==========================================
.. code-block:: text
- deleting reclaimed IPv6 leases that expired more than %1 seconds ago
+ No subnet matches address: %1
-Logged at debug log level 50.
-A debug message issued when the server is removing reclaimed DHCPv6
-leases which have expired longer than a specified period of time.
-The argument is the amount of time Kea waits after a reclaimed
-lease expires before considering its removal.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified address.
-DHCPSRV_MYSQL_GET4
-==================
+DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH
+============================================
.. code-block:: text
- obtaining all IPv4 leases
+ No subnet matches interface: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
-leases from the MySQL database.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified interface name.
-DHCPSRV_MYSQL_GET6
-==================
+DHCPSRV_SUBNET4_SELECT_BY_RELAY_ADDRESS_NO_MATCH
+================================================
.. code-block:: text
- obtaining all IPv6 leases
+ No subnet matches relay address: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
-leases from the MySQL database.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified relay address.
-DHCPSRV_MYSQL_GET_ADDR4
-=======================
+DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS
+=====================================
.. code-block:: text
- obtaining IPv4 lease for address %1
+ No RAI options found to use for subnet selection.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain an IPv4
-lease from the MySQL database for the specified address.
+Logged at debug log level 40.
+A debug message issued by the server when the client query does not include RAI
+options suitable for use with subnet selection.
-DHCPSRV_MYSQL_GET_ADDR6
-=======================
+DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS
+=======================================
.. code-block:: text
- obtaining IPv6 lease for address %1, lease type %2
+ Relay address (giaddr) in client packet is empty.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain an IPv6
-lease from the MySQL database for the specified address.
+Logged at debug log level 40.
+A debug message issued when no relay address was specified to use for subnet
+selection.
-DHCPSRV_MYSQL_GET_CLIENTID
-==========================
+DHCPSRV_SUBNET4_SELECT_NO_USABLE_ADDRESS
+========================================
.. code-block:: text
- obtaining IPv4 leases for client ID %1
+ No subnet selected because no suitable address to use for subnet selection was found.
-Logged at debug log level 50.
-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.
+Logged at debug log level 40.
+A debug message issued when the server was find a suitable address to use for
+subnet selection.
-DHCPSRV_MYSQL_GET_DUID
-======================
+DHCPSRV_SUBNET6_SELECT_BY_ADDRESS_NO_MATCH
+==========================================
.. code-block:: text
- obtaining IPv6 lease for duid %1,
+ No subnet matches address: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain an IPv6
-lease from the MySQL database for the specified duid.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified address.
-DHCPSRV_MYSQL_GET_EXPIRED4
-==========================
+DHCPSRV_SUBNET6_SELECT_BY_INTERFACE_ID_NO_MATCH
+===============================================
.. code-block:: text
- obtaining maximum %1 of expired IPv4 leases
+ No subnet matches interface id: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain expired
-IPv4 leases to reclaim them. The maximum number of leases to be retrieved
-is logged in the message.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified interface id.
-DHCPSRV_MYSQL_GET_EXPIRED6
-==========================
+DHCPSRV_SUBNET6_SELECT_BY_INTERFACE_NO_MATCH
+============================================
.. code-block:: text
- obtaining maximum %1 of expired IPv6 leases
+ No subnet matches interface: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain expired
-IPv6 leases to reclaim them. The maximum number of leases to be retrieved
-is logged in the message.
+Logged at debug log level 40.
+A debug message issued when the server was unable to select a subnet using
+the specified interface name.
-DHCPSRV_MYSQL_GET_HOSTNAME4
+DHCPSRV_TEMPLATE_EVAL_ERROR
===========================
.. code-block:: text
- obtaining IPv4 leases for hostname %1
+ %1: Expression '%2' evaluated to %3
-Logged at debug log level 50.
-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
-hostname.
+This error message indicates that there a problem was encountered while
+evaluating an expression of a template client class.
+A description of the problem is printed.
-DHCPSRV_MYSQL_GET_HOSTNAME6
-===========================
+DHCPSRV_TEMPLATE_EVAL_RESULT
+============================
.. code-block:: text
- obtaining IPv6 leases for hostname %1
+ %1: Expression '%2' evaluated to %3
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
-of IPv6 leases from the MySQL database for a client with the specified
-hostname.
+This debug message indicates that the expression of a template client class has
+been successfully evaluated. The client class name and the result value of the
+evaluation are printed.
-DHCPSRV_MYSQL_GET_HWADDR
-========================
+DHCPSRV_TIMERMGR_CALLBACK_FAILED
+================================
.. code-block:: text
- obtaining IPv4 leases for hardware address %1
+ running handler for timer %1 caused exception: %2
-Logged at debug log level 50.
-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.
+This error message is emitted when the timer elapsed and the
+operation associated with this timer has thrown an exception.
+The timer name and the reason for exception is logged.
-DHCPSRV_MYSQL_GET_IAID_DUID
-===========================
+DHCPSRV_TIMERMGR_REGISTER_TIMER
+===============================
.. code-block:: text
- obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
+ registering timer: %1, using interval: %2 ms
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set of IPv6
-leases from the MySQL database for a client with the specified IAID (Identity
-Association ID) and DUID (DHCP Unique Identifier).
+Logged at debug log level 40.
+A debug message issued when the new interval timer is registered in
+the Timer Manager. This timer will have a callback function
+associated with it, and this function will be executed according
+to the interval specified. The unique name of the timer and the
+interval at which the callback function will be executed is
+included in the message.
-DHCPSRV_MYSQL_GET_IAID_SUBID_DUID
-=================================
+DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION
+====================================
.. code-block:: text
- obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
+ running operation for timer: %1
Logged at debug log level 50.
-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).
+A debug message issued when the Timer Manager is about to
+run a periodic operation associated with the given timer.
+An example of such operation is a periodic cleanup of
+expired leases. The name of the timer is included in the
+message.
-DHCPSRV_MYSQL_GET_PAGE4
-=======================
+DHCPSRV_TIMERMGR_START_TIMER
+============================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2
+ starting timer: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page
-of leases beginning with the specified address.
+Logged at debug log level 40.
+A debug message issued when the registered interval timer is
+being started. If this operation is successful the timer will
+periodically execute the operation associated with it. The
+name of the started timer is included in the message.
-DHCPSRV_MYSQL_GET_PAGE6
-=======================
+DHCPSRV_TIMERMGR_STOP_TIMER
+===========================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2
+ stopping timer: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page
-of leases beginning with the specified address.
+Logged at debug log level 40.
+A debug message issued when the registered interval timer is
+being stopped. The timer remains registered and can be restarted
+if necessary. The name of the timer is included in the message.
-DHCPSRV_MYSQL_GET_RELAYID4
-==========================
+DHCPSRV_TIMERMGR_UNREGISTER_ALL_TIMERS
+======================================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2 with relay id %3 and cltt between %4 and %5
+ unregistering all timers
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv4 leases beginning with the specified address with a relay id and client
-transaction time between start and end dates.
+Logged at debug log level 40.
+A debug message issued when all registered interval timers are
+being unregistered from the Timer Manager.
-DHCPSRV_MYSQL_GET_RELAYID6
-==========================
+DHCPSRV_TIMERMGR_UNREGISTER_TIMER
+=================================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
+ unregistering timer: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases beginning with the specified address with a relay id.
+Logged at debug log level 40.
+A debug message issued when one of the registered interval timers
+is unregistered from the Timer Manager. The name of the timer is
+included in the message.
-DHCPSRV_MYSQL_GET_REMOTEID4
-===========================
+****
+DHCP
+****
+
+DHCP_DDNS_ADD_FAILED
+====================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2 with remote id %3 and cltt between %4 and %5
+ DHCP_DDNS Request ID %1: Transaction outcome %2
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv4 leases beginning with the specified address with a remote id and client
-transaction time between start and end dates.
+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.
-DHCPSRV_MYSQL_GET_REMOTEID6
-===========================
+DHCP_DDNS_ADD_SUCCEEDED
+=======================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
+ DHCP_DDNS Request ID %1: successfully added the DNS mapping addition for this request: %2
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases beginning with the specified address with a remote id.
+This is an informational message issued after DHCP_DDNS has submitted DNS
+mapping additions which were received and accepted by an appropriate DNS server.
-DHCPSRV_MYSQL_GET_SUBID4
-========================
+DHCP_DDNS_AT_MAX_TRANSACTIONS
+=============================
.. code-block:: text
- obtaining IPv4 leases for subnet ID %1
+ application has %1 queued requests but has reached maximum number of %2 concurrent transactions
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
-leases for a given subnet identifier from the MySQL database.
+Logged at debug log level 55.
+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.
-DHCPSRV_MYSQL_GET_SUBID6
-========================
+DHCP_DDNS_CLEARED_FOR_SHUTDOWN
+==============================
.. code-block:: text
- obtaining IPv6 leases for subnet ID %1
+ application has met shutdown criteria for shutdown type: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
-leases for a given subnet identifier from the MySQL database.
+Logged at debug log level 0.
+This is a debug message issued when the application has been instructed
+to shutdown and has met the required criteria to exit.
-DHCPSRV_MYSQL_GET_SUBID_CLIENTID
-================================
+DHCP_DDNS_CONFIGURE
+===================
.. code-block:: text
- obtaining IPv4 lease for subnet ID %1 and client ID %2
+ configuration %1 received: %2
-Logged at debug log level 50.
-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.
+Logged at debug log level 40.
+This is a debug message issued when the DHCP-DDNS application configure method
+has been invoked.
-DHCPSRV_MYSQL_GET_SUBID_HWADDR
-==============================
+DHCP_DDNS_CONFIGURED_CALLOUT_DROP
+=================================
.. code-block:: text
- obtaining IPv4 lease for subnet ID %1 and hardware address %2
+ configuration was rejected because a callout set the next step to 'drop': %1
-Logged at debug log level 50.
-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.
+This error message indicates that the DHCP-DDNS had failed configuration
+attempt because the next step of the configured callout was set to 'drop'
+by a hook library. The error message provided by the hook library is displayed.
-DHCPSRV_MYSQL_GET_SUBID_PAGE6
-=============================
+DHCP_DDNS_CONFIG_CHECK_FAIL
+===========================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
+ DHCP-DDNS server configuration check failed: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases from the MySQL database beginning with the specified address
-for the specified subnet identifier.
+This error message indicates that the DHCP-DDNS had failed configuration
+check. Details are provided. Additional details may be available
+in earlier log entries, possibly on lower levels.
-DHCPSRV_MYSQL_GET_VERSION
-=========================
+DHCP_DDNS_CONFIG_FAIL
+=====================
.. code-block:: text
- obtaining schema version information
+ DHCP-DDNS server configuration failed: %1
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the MySQL database.
+This error message indicates that the DHCP-DDNS had failed configuration
+attempt. Details are provided. Additional details may be available
+in earlier log entries, possibly on lower levels.
-DHCPSRV_MYSQL_HOST_DB
-=====================
+DHCP_DDNS_CONFIG_SYNTAX_WARNING
+===============================
.. code-block:: text
- opening MySQL hosts database: %1
+ DHCP-DDNS server configuration syntax warning: %1
-Logged at debug log level 50.
-This informational message is logged when a DHCP server (either V4 or
-V6) is about to open a MySQL hosts database. The parameters of the
-connection including database name and username needed to access it
-(but not the password if any) are logged.
+This warning message indicates that the DHCP-DDNS configuration had a minor
+syntax error. The error was displayed and the configuration parsing resumed.
-DHCPSRV_MYSQL_HOST_DB_GET_VERSION
-=================================
+DHCP_DDNS_FAILED
+================
.. code-block:: text
- obtaining schema version information for the MySQL hosts database
+ application experienced a fatal error: %1
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the MySQL hosts database.
+This is a debug message issued when the DHCP-DDNS application encounters an
+unrecoverable error from within the event loop.
-DHCPSRV_MYSQL_HOST_DB_READONLY
-==============================
+DHCP_DDNS_FORWARD_ADD_BAD_DNSCLIENT_STATUS
+==========================================
.. code-block:: text
- MySQL host database opened for read access only
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while adding a forward address mapping for FQDN %3 to DNS server %4
-This informational message is issued when the user has configured the MySQL
-database in read-only mode. Kea will not be able to insert or modify
-host reservations but will be able to retrieve existing ones and
-assign them to the clients communicating with the server.
+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.
-DHCPSRV_MYSQL_HOST_DB_RECONNECT_ATTEMPT_FAILED
-==============================================
+DHCP_DDNS_FORWARD_ADD_BUILD_FAILURE
+===================================
.. code-block:: text
- database reconnect failed: %1
+ DNS Request ID %1: update message to add a forward DNS entry could not be constructed for this request: %2, reason: %3
-An error message issued when an attempt to reconnect has failed.
+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.
-DHCPSRV_MYSQL_HOST_DB_RECONNECT_ATTEMPT_SCHEDULE
-================================================
+DHCP_DDNS_FORWARD_ADD_IO_ERROR
+==============================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping add for FQDN %2 to DNS server %3
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+This is an error message issued when a communication error occurs while
+DHCP_DDNS is carrying out a forward address add. The application will
+retry against the same server or others as appropriate.
-DHCPSRV_MYSQL_HOST_DB_RECONNECT_FAILED
-======================================
+DHCP_DDNS_FORWARD_ADD_REJECTED
+==============================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ DNS Request ID %1: Server, %2, rejected a DNS update request to add the address mapping for FQDN, %3, with an RCODE: %4
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+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.
-DHCPSRV_MYSQL_LEASE_DB_RECONNECT_ATTEMPT_FAILED
-===============================================
+DHCP_DDNS_FORWARD_ADD_RESP_CORRUPT
+==================================
.. code-block:: text
- database reconnect failed: %1
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while adding forward address mapping for FQDN, %3
-An error message issued when an attempt to reconnect has failed.
+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.
-DHCPSRV_MYSQL_LEASE_DB_RECONNECT_ATTEMPT_SCHEDULE
-=================================================
+DHCP_DDNS_FORWARD_ADD_TIMEOUT
+=============================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping add for FQDN %2 to DNS server %3
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a forward address add. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_MYSQL_LEASE_DB_RECONNECT_FAILED
-=======================================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_BAD_DNSCLIENT_STATUS
+===================================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing a forward address mapping for FQDN %3 to DNS server %4
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+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.
-DHCPSRV_MYSQL_NEGATIVE_LEASES_STAT
-==================================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_BUILD_FAILURE
+============================================
.. code-block:: text
- recount of leases returned a negative value
+ DNS Request ID %1: update message to remove a forward DNS Address entry could not be constructed for this request: %2, reason: %3
-This warning message is issued when the recount of leases using counters
-in the MySQL database returned a negative value. This shows a problem
-which can be fixed only by an offline direct recount on the database.
-This message is issued only once.
+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.
+/*sar*/
-DHCPSRV_MYSQL_NO_TLS
-====================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_IO_ERROR
+=======================================
.. code-block:: text
- TLS was required but is not used
+ DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping address removal for FQDN %2 to DNS server %3
-This error message is issued when TLS for the connection was required but
-TLS is not used.
+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.
-DHCPSRV_MYSQL_ROLLBACK
-======================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_REJECTED
+=======================================
.. code-block:: text
- rolling back MySQL database
+ DNS Request ID %1: Server, %2, rejected a DNS update request to remove the forward address mapping for FQDN, %3, with an RCODE: %4
-Logged at debug log level 50.
-The code has issued a rollback call. All outstanding transaction will
-be rolled back and not committed to the database.
+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.
-DHCPSRV_MYSQL_TLS_CIPHER
-========================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_RESP_CORRUPT
+===========================================
.. code-block:: text
- TLS cipher: %1
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing forward address mapping for FQDN, %3
-Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
-The TLS cipher name is logged.
+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.
-DHCPSRV_MYSQL_UPDATE_ADDR4
-==========================
+DHCP_DDNS_FORWARD_REMOVE_ADDRS_TIMEOUT
+======================================
.. code-block:: text
- updating IPv4 lease for address %1
+ DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping address removal for FQDN %2 to DNS server %3
-Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv4
-lease from the MySQL database for the specified address.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a forward mapping address removal. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_MYSQL_UPDATE_ADDR6
-==========================
+DHCP_DDNS_FORWARD_REMOVE_RRS_BAD_DNSCLIENT_STATUS
+=================================================
.. code-block:: text
- updating IPv6 lease for address %1, lease type %2
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing forward RRs for FQDN %3 to DNS server %4
-Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv6
-lease from the MySQL database for the specified address.
+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.
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4
-====================================
+DHCP_DDNS_FORWARD_REMOVE_RRS_BUILD_FAILURE
+==========================================
.. code-block:: text
- upgrading IPv4 leases done in %1 pages with %2 updated leases
+ DNS Request ID %1: update message to remove forward DNS RR entries could not be constructed for this request: %2, reason: %3
-Logged at debug log level 40.
-The server upgraded extended info. The number of pages and the final count of
-updated leases are displayed.
+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.
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4_ERROR
-==========================================
+DHCP_DDNS_FORWARD_REMOVE_RRS_IO_ERROR
+=====================================
.. code-block:: text
- upgrading extending info for IPv4 lease at %1 failed with %2
+ DHCP_DDNS Request ID %1: encountered an IO error sending a forward RR removal for FQDN %2 to DNS server %3
-Logged at debug log level 40.
-A debug message issued when the server failed to upgrade an extended info.
-The address of the lease and the error message are displayed.
+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.
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4_PAGE
-=========================================
+DHCP_DDNS_FORWARD_REMOVE_RRS_REJECTED
+=====================================
.. code-block:: text
- upgrading IPv4 lease extended info at page %1 starting at %2 (updated %3)
+ DNS Request ID %1: Server, %2, rejected a DNS update request to remove forward RR entries for FQDN, %3, with an RCODE: %4
-Logged at debug log level 50.
-A debug message issued when the server upgrades IPv4 lease extended info.
-The page number and started address, and the count of already updated leases
-are displayed.
+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.
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6
-====================================
+DHCP_DDNS_FORWARD_REMOVE_RRS_RESP_CORRUPT
+=========================================
.. code-block:: text
- upgrading IPv6 leases done in %1 pages with %2 updated leases
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing forward RRs for FQDN, %3
-Logged at debug log level 40.
-The server upgraded extended info. The number of pages and the final count of
-updated leases are displayed.
+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.
+/*sar*/
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6_ERROR
-==========================================
+DHCP_DDNS_FORWARD_REMOVE_RRS_TIMEOUT
+====================================
.. code-block:: text
- upgrading extending info for IPv6 lease at %1 failed with %2
+ DHCP_DDNS Request ID %1: timed out waiting for response to forward RR removal for FQDN %2 to DNS server %3
-Logged at debug log level 40.
-A debug message issued when the server failed to upgrade the extended info
-for a lease. The address of the lease and the error message are displayed.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a forward RR removal. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6_PAGE
-=========================================
+DHCP_DDNS_FORWARD_REPLACE_BAD_DNSCLIENT_STATUS
+==============================================
.. code-block:: text
- upgrading IPv6 lease extended info at page %1 starting at %2 (updated %3)
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while replacing forward address mapping for FQDN %3 to DNS server %4
-Logged at debug log level 50.
-A debug message issued when the server upgrades IPv6 lease extended info.
-The page number and started address, and the count of already updated leases
-are displayed.
+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.
-DHCPSRV_NOTYPE_DB
-=================
+DHCP_DDNS_FORWARD_REPLACE_BUILD_FAILURE
+=======================================
.. code-block:: text
- no 'type' keyword to determine database backend: %1
+ DNS Request ID %1: update message to replace a forward DNS entry could not be constructed from this request: %2, reason: %3
-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.
+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.
-DHCPSRV_NO_SOCKETS_OPEN
-=======================
+DHCP_DDNS_FORWARD_REPLACE_IO_ERROR
+==================================
.. code-block:: text
- no interface configured to listen to DHCP traffic
+ DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping replace for FQDN %2 to DNS server %3
-This warning message is issued when the current server configuration specifies
-no interfaces that the server should listen on, or when the specified interfaces are not
-configured to receive the traffic.
+This is an error message issued when a communication error occurs while
+DHCP_DDNS is carrying out a forward mapping replace. The application will
+retry against the same server or others as appropriate.
-DHCPSRV_OPEN_SOCKET_FAIL
-========================
+DHCP_DDNS_FORWARD_REPLACE_REJECTED
+==================================
.. code-block:: text
- failed to open socket: %1
+ DNS Request ID %1: Server, %2, rejected a DNS update request to replace the address mapping for FQDN, %3, with an RCODE: %4
-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.
+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.
-DHCPSRV_PGSQL_ADD_ADDR4
-=======================
+DHCP_DDNS_FORWARD_REPLACE_RESP_CORRUPT
+======================================
.. code-block:: text
- adding IPv4 lease with address %1
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while replacing forward address mapping for FQDN, %3
-Logged at debug log level 50.
-A debug message issued when the server is about to add an IPv4 lease
-with the specified address to the PostgreSQL backend database.
+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.
-DHCPSRV_PGSQL_ADD_ADDR6
-=======================
+DHCP_DDNS_FORWARD_REPLACE_TIMEOUT
+=================================
.. code-block:: text
- adding IPv6 lease with address %1, lease type %2
+ DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping replace for FQDN %2 to DNS server %3
-Logged at debug log level 50.
-A debug message issued when the server is about to add an IPv6 lease
-with the specified address to the PostgreSQL backend database.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a forward mapping replace. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_PGSQL_COMMIT
-====================
+DHCP_DDNS_FWD_REQUEST_IGNORED
+=============================
.. code-block:: text
- committing to PostgreSQL database
+ Request ID %1: Forward updates are disabled, the forward portion of request will be ignored: %2
-Logged at debug log level 50.
-The code has issued a commit call. All outstanding transactions will be
-committed to the database. Note that depending on the PostgreSQL settings,
-the commit may not include a write to disk.
+Logged at debug log level 55.
+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.
-DHCPSRV_PGSQL_DB
-================
+DHCP_DDNS_INVALID_NCR
+=====================
.. code-block:: text
- opening PostgreSQL lease database: %1
+ application received an invalid DNS update request: %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.
+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.
-DHCPSRV_PGSQL_DELETE_ADDR
-=========================
+DHCP_DDNS_INVALID_RESPONSE
+==========================
.. code-block:: text
- deleting lease for address %1
+ received response to DNS Update message is malformed: %1
Logged at debug log level 50.
-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.
+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.
-DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED4
-=======================================
+DHCP_DDNS_LISTENING_ON_ALL_INTERFACES
+=====================================
.. code-block:: text
- deleting reclaimed IPv4 leases that expired more than %1 seconds ago
+ the DHCP-DDNS server has been configured to listen on %1. This is an insecure configuration supported for testing purposes only
-Logged at debug log level 50.
-A debug message issued when the server is removing reclaimed DHCPv4
-leases which have expired longer than a specified period of time.
-The argument is the amount of time Kea waits after a reclaimed
-lease expires before considering its removal.
+This is a warning message issued when the DHCP-DDNS server is configured to
+listen at either `0.0.0.0` or `::`. It is possible for a malicious attacker to send
+bogus NameChangeRequests to it and change entries in the DNS. For this reason,
+listening on all interfaces should only be used when deploying in containers
+or for testing purposes. A future version of Kea will disable this ability by
+default.
-DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED6
-=======================================
+DHCP_DDNS_NCR_FLUSH_IO_ERROR
+============================
.. code-block:: text
- deleting reclaimed IPv6 leases that expired more than %1 seconds ago
+ DHCP-DDNS Last send before stopping did not complete successfully: %1
-Logged at debug log level 50.
-A debug message issued when the server is removing reclaimed DHCPv6
-leases which have expired longer than a specified period of time.
-The argument is the amount of time Kea waits after a reclaimed
-lease expires before considering its removal.
+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.
-DHCPSRV_PGSQL_GET4
-==================
+DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR
+================================
.. code-block:: text
- obtaining all IPv4 leases
+ application encountered an error while closing the listener used to receive NameChangeRequests : %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
-leases from the PostgreSQL database.
+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.
-DHCPSRV_PGSQL_GET6
-==================
+DHCP_DDNS_NCR_RECV_NEXT_ERROR
+=============================
.. code-block:: text
- obtaining all IPv6 leases
+ application could not initiate the next read following a request receive.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
-leases from the PostgreSQL database.
+This is an 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.
-DHCPSRV_PGSQL_GET_ADDR4
-=======================
+DHCP_DDNS_NCR_SEND_CLOSE_ERROR
+==============================
.. code-block:: text
- obtaining IPv4 lease for address %1
+ DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain an IPv4
-lease from the PostgreSQL database for the specified address.
+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.
-DHCPSRV_PGSQL_GET_ADDR6
-=======================
+DHCP_DDNS_NCR_SEND_NEXT_ERROR
+=============================
.. code-block:: text
- obtaining IPv6 lease for address %1 (lease type %2)
+ DHCP-DDNS client could not initiate the next request send following send completion: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain an IPv6
-lease from the PostgreSQL database for the specified address.
+This is an 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.
-DHCPSRV_PGSQL_GET_CLIENTID
-==========================
+DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR
+===================================
.. code-block:: text
- obtaining IPv4 leases for client ID %1
+ NCR UDP watch socket failed to clear: %1
-Logged at debug log level 50.
-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.
+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.
-DHCPSRV_PGSQL_GET_DUID
-======================
+DHCP_DDNS_NCR_UDP_RECV_CANCELED
+===============================
.. code-block:: text
- obtaining IPv6 leases for DUID %1,
+ UDP socket receive was canceled while listening for DNS Update requests
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set of IPv6
-leases from the PostgreSQL database for a client with the specified DUID (DHCP Unique Identifier).
+Logged at debug log level 40.
+This is a debug message indicating that the listening on a UDP socket
+for DNS update requests has been canceled. This is a normal part of
+suspending listening operations.
-DHCPSRV_PGSQL_GET_EXPIRED4
-==========================
+DHCP_DDNS_NCR_UDP_RECV_ERROR
+============================
.. code-block:: text
- obtaining maximum %1 of expired IPv4 leases
+ UDP socket receive error while listening for DNS Update requests: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain expired
-IPv4 leases to reclaim them. The maximum number of leases to be retrieved
-is logged in the message.
+This is an error message indicating that an I/O error occurred while listening
+over a UDP socket for DNS update requests. This could indicate a network
+connectivity or system resource issue.
-DHCPSRV_PGSQL_GET_EXPIRED6
-==========================
+DHCP_DDNS_NCR_UDP_SEND_CANCELED
+===============================
.. code-block:: text
- obtaining maximum %1 of expired IPv6 leases
+ UDP socket send was canceled while sending a DNS Update request to DHCP_DDNS: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain expired
-IPv6 leases to reclaim them. The maximum number of leases to be retrieved
-is logged in the message.
+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.
-DHCPSRV_PGSQL_GET_HOSTNAME4
-===========================
+DHCP_DDNS_NCR_UDP_SEND_ERROR
+============================
.. code-block:: text
- obtaining IPv4 leases for hostname %1
+ UDP socket send error while sending a DNS Update request: %1
-Logged at debug log level 50.
-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
-hostname.
+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.
-DHCPSRV_PGSQL_GET_HOSTNAME6
-===========================
+DHCP_DDNS_NOT_ON_LOOPBACK
+=========================
.. code-block:: text
- obtaining IPv6 leases for hostname %1
+ 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
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
-of IPv6 leases from the PostgreSQL database for a client with the specified
-hostname.
+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.
-DHCPSRV_PGSQL_GET_HWADDR
-========================
+DHCP_DDNS_NO_ELIGIBLE_JOBS
+==========================
.. code-block:: text
- obtaining IPv4 leases for hardware address %1
+ although there are queued requests, there are pending transactions for each, Queue count: %1 Transaction count: %2
-Logged at debug log level 50.
-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.
+Logged at debug log level 55.
+This is a debug message issued when all of the queued requests represent clients
+for which there is an update already in progress. This may occur under
+normal operations but should be temporary situation.
-DHCPSRV_PGSQL_GET_IAID_DUID
-===========================
+DHCP_DDNS_NO_FWD_MATCH_ERROR
+============================
.. code-block:: text
- obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
+ Request ID %1: the configured list of forward DDNS domains does not contain a match for: %2 The request has been discarded.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set of IPv6
-leases from the PostgreSQL database for a client with the specified IAID
-(Identity Association ID) and DUID (DHCP Unique Identifier).
+This is an error message that indicates that DHCP_DDNS received a request to
+update 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.
-DHCPSRV_PGSQL_GET_IAID_SUBID_DUID
-=================================
+DHCP_DDNS_NO_MATCH
+==================
.. code-block:: text
- obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
+ No DNS servers match FQDN %1
-Logged at debug log level 50.
-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).
+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.
-DHCPSRV_PGSQL_GET_PAGE4
-=======================
+DHCP_DDNS_NO_REV_MATCH_ERROR
+============================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2
+ Request ID %1: the configured list of reverse DDNS domains does not contain a match for: %2 The request has been discarded.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page
-of leases beginning with the specified address.
+This is an error message that indicates that DHCP_DDNS received a request to
+update 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.
-DHCPSRV_PGSQL_GET_PAGE6
-=======================
+DHCP_DDNS_QUEUE_MGR_QUEUE_FULL
+==============================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2
+ application request queue has reached maximum number of entries %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page
-of leases beginning with the specified address.
+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.
-DHCPSRV_PGSQL_GET_RELAYID4
-==========================
+DHCP_DDNS_QUEUE_MGR_QUEUE_RECEIVE
+=================================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2 with relay id %3 and cltt between %4 and %5
+ Request ID %1: received and queued a request.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv4 leases beginning with the specified address with a relay id and client
-transaction time between start and end dates.
+Logged at debug log level 55.
+This is an informational message indicating that the NameChangeRequest listener used
+by DHCP-DDNS to receive a request has received a request and queued it for further
+processing.
-DHCPSRV_PGSQL_GET_RELAYID6
-==========================
+DHCP_DDNS_QUEUE_MGR_RECONFIGURING
+=================================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
+ application is reconfiguring the queue manager
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases beginning with the specified address with a relay id.
+Logged at debug log level 40.
+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.
-DHCPSRV_PGSQL_GET_REMOTEID4
-===========================
+DHCP_DDNS_QUEUE_MGR_RECOVERING
+==============================
.. code-block:: text
- obtaining at most %1 IPv4 leases starting from address %2 with remote id %3 and cltt between %4 and %5
+ application is attempting to recover from a queue manager IO error
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv4 leases beginning with the specified address with a remote id and client
-transaction time between start and end dates.
+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.
-DHCPSRV_PGSQL_GET_REMOTEID6
-===========================
+DHCP_DDNS_QUEUE_MGR_RECV_ERROR
+==============================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
+ application's queue manager was notified of a request receive error by its listener.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases beginning with the specified address with a remote id.
+This is an error message indicating that the NameChangeRequest listener used by
+DHCP-DDNS to receive requests encountered an 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.
-DHCPSRV_PGSQL_GET_SUBID4
-========================
+DHCP_DDNS_QUEUE_MGR_RESUME_ERROR
+================================
.. code-block:: text
- obtaining IPv4 leases for subnet ID %1
+ application could not restart the queue manager, reason: %1
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
-leases for a given subnet identifier from the PostgreSQL database.
+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.
-DHCPSRV_PGSQL_GET_SUBID6
-========================
+DHCP_DDNS_QUEUE_MGR_RESUMING
+============================
.. code-block:: text
- obtaining IPv6 leases for subnet ID %1
+ application is resuming listening for requests now that the request queue size has reached %1 of a maximum %2 allowed
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
-leases for a given subnet identifier from the PostgreSQL database.
+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.
-DHCPSRV_PGSQL_GET_SUBID_CLIENTID
-================================
+DHCP_DDNS_QUEUE_MGR_STARTED
+===========================
.. code-block:: text
- obtaining IPv4 lease for subnet ID %1 and client ID %2
+ application's queue manager has begun listening for requests.
-Logged at debug log level 50.
-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.
+Logged at debug log level 0.
+This is a debug message indicating that DHCP_DDNS's Queue Manager has
+successfully started and is now listening for NameChangeRequests.
-DHCPSRV_PGSQL_GET_SUBID_HWADDR
-==============================
+DHCP_DDNS_QUEUE_MGR_START_ERROR
+===============================
.. code-block:: text
- obtaining IPv4 lease for subnet ID %1 and hardware address %2
+ application could not start the queue manager, reason: %1
-Logged at debug log level 50.
-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.
+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.
-DHCPSRV_PGSQL_GET_SUBID_PAGE6
-=============================
+DHCP_DDNS_QUEUE_MGR_STOPPED
+===========================
.. code-block:: text
- obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
+ application's queue manager has stopped listening for requests.
-Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a page of
-IPv6 leases from the PostgreSQL database beginning with the specified address
-for the specified subnet identifier.
+Logged at debug log level 40.
+This is a debug 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.
-DHCPSRV_PGSQL_GET_VERSION
-=========================
+DHCP_DDNS_QUEUE_MGR_STOPPING
+============================
.. code-block:: text
- obtaining schema version information
+ application is stopping the queue manager for %1
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the PostgreSQL database.
+Logged at debug log level 0.
+This is an informational message indicating that DHCP_DDNS is stopping the
+queue manager either to reconfigure it or as part of application shutdown.
-DHCPSRV_PGSQL_HOST_DB
-=====================
+DHCP_DDNS_QUEUE_MGR_STOP_ERROR
+==============================
.. code-block:: text
- opening PostgreSQL hosts database: %1
+ application encountered an error stopping the queue manager: %1
-Logged at debug log level 50.
-This informational message is logged when a DHCP server (either V4 or
-V6) is about to open a PostgreSQL hosts database. The parameters of the
-connection including database name and username needed to access it
-(but not the password if any) are logged.
+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.
-DHCPSRV_PGSQL_HOST_DB_GET_VERSION
-=================================
+DHCP_DDNS_QUEUE_MGR_UNEXPECTED_HANDLER_ERROR
+============================================
.. code-block:: text
- obtaining schema version information for the PostgreSQL hosts database
+ application's queue manager request receive handler experienced an unexpected exception %1:
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the PostgreSQL hosts database.
+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.
-DHCPSRV_PGSQL_HOST_DB_READONLY
-==============================
+DHCP_DDNS_QUEUE_MGR_UNEXPECTED_STOP
+===================================
.. code-block:: text
- PostgreSQL host database opened for read access only
+ application's queue manager receive was
-This informational message is issued when the user has configured the PostgreSQL
-database in read-only mode. Kea will not be able to insert or modify
-host reservations but will be able to retrieve existing ones and
-assign them to the clients communicating with the server.
+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.
-DHCPSRV_PGSQL_HOST_DB_RECONNECT_ATTEMPT_FAILED
-==============================================
+DHCP_DDNS_REMOVE_FAILED
+=======================
.. code-block:: text
- database reconnect failed: %1
+ DHCP_DDNS Request ID %1: Transaction outcome: %2
-An error message issued when an attempt to reconnect has failed.
+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.
-DHCPSRV_PGSQL_HOST_DB_RECONNECT_ATTEMPT_SCHEDULE
-================================================
+DHCP_DDNS_REMOVE_SUCCEEDED
+==========================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ DHCP_DDNS Request ID %1: successfully removed the DNS mapping addition for this request: %2
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+This is an informational message issued after DHCP_DDNS has submitted DNS
+mapping removals which were received and accepted by an appropriate DNS server.
-DHCPSRV_PGSQL_HOST_DB_RECONNECT_FAILED
-======================================
+DHCP_DDNS_REQUEST_DROPPED
+=========================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ Request ID %1: Request contains no enabled update requests and will be dropped: %2
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 55.
+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 received that asks only for reverse updates
+then the request is dropped.
-DHCPSRV_PGSQL_LEASE_DB_RECONNECT_ATTEMPT_FAILED
-===============================================
+DHCP_DDNS_REVERSE_REMOVE_BAD_DNSCLIENT_STATUS
+=============================================
.. code-block:: text
- database reconnect failed: %1
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing reverse address mapping for FQDN %3 to DNS server %4
-An error message issued when an attempt to reconnect has failed.
+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.
-DHCPSRV_PGSQL_LEASE_DB_RECONNECT_ATTEMPT_SCHEDULE
-=================================================
+DHCP_DDNS_REVERSE_REMOVE_BUILD_FAILURE
+======================================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ DNS Request ID %1: update message to remove a reverse DNS entry could not be constructed from this request: %2, reason: %3
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+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.
-DHCPSRV_PGSQL_LEASE_DB_RECONNECT_FAILED
-=======================================
+DHCP_DDNS_REVERSE_REMOVE_IO_ERROR
+=================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ DHCP_DDNS Request ID %1: encountered an IO error sending a reverse mapping remove for FQDN %2 to DNS server %3
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+This is an error message issued when a communication error occurs while
+DHCP_DDNS is carrying out a reverse mapping remove. The application will
+retry against the same server or others as appropriate.
-DHCPSRV_PGSQL_NEGATIVE_LEASES_STAT
-==================================
+DHCP_DDNS_REVERSE_REMOVE_REJECTED
+=================================
.. code-block:: text
- recount of leases returned a negative value
+ DNS Request ID %1: Server, %2, rejected a DNS update request to remove the reverse mapping for FQDN, %3, with an RCODE: %4
-This warning message is issued when the recount of leases using counters
-in the PostgreSQL database returned a negative value. This shows a problem
-which can be fixed only by an offline direct recount on the database.
-This message is issued only once.
+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.
-DHCPSRV_PGSQL_NO_TLS_SUPPORT
-============================
+DHCP_DDNS_REVERSE_REMOVE_RESP_CORRUPT
+=====================================
.. code-block:: text
- Attempt to configure TLS (unsupported for PostgreSQL): %1
-
-This error message is printed when TLS support was required in the Kea
-configuration: Kea was built with this feature disabled for PostgreSQL.
-The parameters of the connection are logged.
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing reverse address mapping for FQDN, %3
-DHCPSRV_PGSQL_ROLLBACK
-======================
-
-.. code-block:: text
-
- rolling back PostgreSQL database
-
-Logged at debug log level 50.
-The code has issued a rollback call. All outstanding transaction will
-be rolled back and not committed to the database.
+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.
-DHCPSRV_PGSQL_TLS_SUPPORT
-=========================
+DHCP_DDNS_REVERSE_REMOVE_TIMEOUT
+================================
.. code-block:: text
- Attempt to configure TLS: %1
+ DHCP_DDNS Request ID %1: timed out waiting for a response to reverse mapping remove for FQDN %2 to DNS server %3
-This informational message is printed when TLS support was required in
-the Kea configuration: The TLS support in PostgreSQL will be initialized but
-its configuration is fully managed outside the C API.
-The parameters of the connection are logged.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a reverse mapping remove. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_PGSQL_UPDATE_ADDR4
-==========================
+DHCP_DDNS_REVERSE_REPLACE_BAD_DNSCLIENT_STATUS
+==============================================
.. code-block:: text
- updating IPv4 lease for address %1
+ DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while replacing reverse address mapping for FQDN %3 to DNS server %4
-Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv4
-lease from the PostgreSQL database for the specified address.
+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.
-DHCPSRV_PGSQL_UPDATE_ADDR6
-==========================
+DHCP_DDNS_REVERSE_REPLACE_BUILD_FAILURE
+=======================================
.. code-block:: text
- updating IPv6 lease for address %1, lease type %2
+ DNS Request ID %1: update message to replace a reverse DNS entry could not be constructed from this request: %2, reason: %3
-Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv6
-lease from the PostgreSQL database for the specified address.
+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.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4
-====================================
+DHCP_DDNS_REVERSE_REPLACE_IO_ERROR
+==================================
.. code-block:: text
- upgrading IPv4 leases done in %1 pages with %2 updated leases
+ DHCP_DDNS Request ID %1: encountered an IO error sending a reverse mapping replacement for FQDN %2 to DNS server %3
-Logged at debug log level 40.
-The server upgraded extended info. The number of pages and the final count of
-updated leases are displayed.
+This is an error message issued when a communication error occurs while
+DHCP_DDNS is carrying out a reverse mapping replacement. The application will
+retry against the same server or others as appropriate.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4_ERROR
-==========================================
+DHCP_DDNS_REVERSE_REPLACE_REJECTED
+==================================
.. code-block:: text
- upgrading extending info for IPv4 lease at %1 failed with %2
+ DNS Request ID %1: Server, %2, rejected a DNS update request to replace the reverse mapping for FQDN, %3, with an RCODE: %4
-Logged at debug log level 40.
-A debug message issued when the server failed to upgrade an extended info.
-The address of the lease and the error message are displayed.
+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.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4_PAGE
-=========================================
+DHCP_DDNS_REVERSE_REPLACE_RESP_CORRUPT
+======================================
.. code-block:: text
- upgrading IPv4 lease extended info at page %1 starting at %2 (updated %3)
+ DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while replacing reverse address mapping for FQDN, %3
-Logged at debug log level 50.
-A debug message issued when the server upgrades IPv4 lease extended info.
-The page number and started address, and the count of already updated leases
-are displayed.
+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.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6
-====================================
+DHCP_DDNS_REVERSE_REPLACE_TIMEOUT
+=================================
.. code-block:: text
- upgrading IPv6 leases done in %1 pages with %2 updated leases
+ DHCP_DDNS Request ID %1: timed out waiting for a response to reverse mapping replacement for FQDN %2 to DNS server %3
-Logged at debug log level 40.
-The server upgraded extended info. The number of pages and the final count of
-updated leases are displayed.
+This is an error message issued when no response is received from the DNS
+server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
+a reverse mapping replacement. The application will retry against the same
+server or others as appropriate.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6_ERROR
-==========================================
+DHCP_DDNS_REV_REQUEST_IGNORED
+=============================
.. code-block:: text
- upgrading extending info for IPv6 lease at %1 failed with %2
+ Request ID %1: Reverse updates are disabled, the reverse portion of request will be ignored: %2
-Logged at debug log level 40.
-A debug message issued when the server failed to upgrade the extended info
-for a lease. The address of the lease and the error message are displayed.
+Logged at debug log level 55.
+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.
-DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6_PAGE
-=========================================
+DHCP_DDNS_RUN_EXIT
+==================
.. code-block:: text
- upgrading IPv6 lease extended info at page %1 starting at %2 (updated %3)
+ application is exiting the event loop
-Logged at debug log level 50.
-A debug message issued when the server upgrades IPv6 lease extended info.
-The page number and started address, and the count of already updated leases
-are displayed.
+Logged at debug log level 0.
+This is a debug message issued when the DHCP-DDNS server exits its
+event lo
-DHCPSRV_QUEUE_NCR
-=================
+DHCP_DDNS_SHUTDOWN_COMMAND
+==========================
.. code-block:: text
- %1: Name change request to %2 DNS entry queued: %3
+ application received shutdown command with args: %1
-Logged at debug log level 50.
-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 argument
-includes the client identification information. The second argument
-indicates whether the DNS entry is to be added or removed. The third
-argument carries the details of the NameChangeRequest.
+Logged at debug log level 0.
+This is a debug message issued when the application has been instructed
+to shut down by the controller.
-DHCPSRV_QUEUE_NCR_FAILED
-========================
+DHCP_DDNS_STARTED
+=================
.. code-block:: text
- %1: queuing %2 name change request failed for lease %3: %4
+ Kea DHCP-DDNS server version %1 started
-This error message is logged when sending a NameChangeRequest
-to DHCP DDNS failed. The first argument includes the client identification
-information. The second argument indicates whether the DNS entry is to be
-added or removed. The third argument specifies the leased address. The
-last argument provides the reason for failure.
+This informational message indicates that the DHCP-DDNS server has
+processed all configuration information and is ready to begin processing.
+The version is also printed.
-DHCPSRV_QUEUE_NCR_SKIP
-======================
+DHCP_DDNS_STARTING_TRANSACTION
+==============================
.. code-block:: text
- %1: skip queuing name change request for lease: %2
+ Request ID %1:
Logged at debug log level 50.
-This debug message is issued when the server decides to not queue the name
-change request because the lease doesn't include the FQDN, the forward and
-reverse update is disabled for this lease or the DNS updates are disabled
-in the configuration. The first argument includes the client identification
-information. The second argument includes the leased address.
+This is a debug message issued when DHCP-DDNS has begun a transaction for
+a given request.
-DHCPSRV_SUBNET4O6_SELECT_FAILED
-===============================
+DHCP_DDNS_STATE_MODEL_UNEXPECTED_ERROR
+======================================
.. code-block:: text
- Failed to select any subnet for the DHCPv4o6 packet
+ Request ID %1: application encountered an unexpected error while carrying out a NameChangeRequest: %2
-Logged at debug log level 40.
-A debug message issued when the server was unable to select any subnet for the
-DHCPv4o6 packet.
+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.
-DHCPSRV_SUBNET4_SELECT_BY_ADDRESS_NO_MATCH
-==========================================
+DHCP_DDNS_TRANS_SEND_ERROR
+==========================
.. code-block:: text
- No subnet matches address: %1
+ Request ID %1: application encountered an unexpected error while attempting to send a DNS update: %2
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified address.
+This is error message issued when the application is able to construct an update
+message but the attempt to send it suffered an 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.
-DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH
-============================================
+DHCP_DDNS_UDP_SENDER_WATCH_SOCKET_CLOSE_ERROR
+=============================================
.. code-block:: text
- No subnet matches interface: %1
+ watch socket failed to close: %1
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified interface name.
+This is an error message that indicates the application was unable to close
+the inbound or outbound side of a NCR sender's watch socket. While technically
+possible the error is highly unlikely to occur and should not impair the
+application's ability to process requests.
-DHCPSRV_SUBNET4_SELECT_BY_RELAY_ADDRESS_NO_MATCH
-================================================
+DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR
+=========================================
.. code-block:: text
- No subnet matches relay address: %1
+ unexpected exception thrown from the application receive completion handler: %1
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified relay address.
+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.
-DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS
-=====================================
+DHCP_DDNS_UPDATE_REQUEST_SENT
+=============================
.. code-block:: text
- No RAI options found to use for subnet selection.
+ Request ID %1: %2 to server: %3
-Logged at debug log level 40.
-A debug message issued by the server when the client query does not include RAI
-options suitable for use with subnet selection.
+Logged at debug log level 50.
+This is a debug message issued when DHCP_DDNS sends a DNS request to a DNS
+server.
-DHCPSRV_SUBNET4_SELECT_NO_RELAY_ADDRESS
-=======================================
+****
+EVAL
+****
+
+EVAL_DEBUG_AND
+==============
.. code-block:: text
- Relay address (giaddr) in client packet is empty.
+ %1: Popping %2 and %3 pushing %4
-Logged at debug log level 40.
-A debug message issued when no relay address was specified to use for subnet
-selection.
+Logged at debug log level 55.
+This debug message indicates that two values are popped from
+the value stack. Then are then combined via logical and and
+the result is pushed onto the value stack.
-DHCPSRV_SUBNET4_SELECT_NO_USABLE_ADDRESS
-========================================
+EVAL_DEBUG_BRANCH
+=================
.. code-block:: text
- No subnet selected because no suitable address to use for subnet selection was found.
+ Branching to %1
-Logged at debug log level 40.
-A debug message issued when the server was find a suitable address to use for
-subnet selection.
+Logged at debug log level 55.
+This debug message indicates that an unconditional branch is performed
+to the displayed target.
-DHCPSRV_SUBNET6_SELECT_BY_ADDRESS_NO_MATCH
-==========================================
+EVAL_DEBUG_CONCAT
+=================
.. code-block:: text
- No subnet matches address: %1
+ %1: Popping %2 and %3 pushing %4
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified address.
+Logged at debug log level 55.
+This debug message indicates that the two strings are being popped off
+of the stack. They are then concatenated and the resulting string is
+pushed onto the stack. The strings are displayed in hex.
-DHCPSRV_SUBNET6_SELECT_BY_INTERFACE_ID_NO_MATCH
-===============================================
+EVAL_DEBUG_EQUAL
+================
.. code-block:: text
- No subnet matches interface id: %1
+ %1: Popping %2 and %3 pushing result %4
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified interface id.
+Logged at debug log level 55.
+This debug message indicates that the two strings are being popped off
+of the value stack and the result of comparing them is being pushed onto
+the value stack. The strings are displayed in hex.
-DHCPSRV_SUBNET6_SELECT_BY_INTERFACE_NO_MATCH
-============================================
+EVAL_DEBUG_HEXSTRING
+====================
.. code-block:: text
- No subnet matches interface: %1
+ %1: Pushing hex string %2
-Logged at debug log level 40.
-A debug message issued when the server was unable to select a subnet using
-the specified interface name.
+Logged at debug log level 55.
+This debug message indicates that the given binary string is being pushed
+onto the value stack. The string is displayed in hex.
-DHCPSRV_TEMPLATE_EVAL_ERROR
-===========================
+EVAL_DEBUG_IFELSE_FALSE
+=======================
.. code-block:: text
- %1: Expression '%2' evaluated to %3
+ %1: Popping %2 (false) and %3, leaving %4
-This error message indicates that there a problem was encountered while
-evaluating an expression of a template client class.
-A description of the problem is printed.
+Logged at debug log level 55.
+This debug message indicates that the condition is false so
+the iftrue branch value is removed and the ifelse branch value
+is left on the value stack.
-DHCPSRV_TEMPLATE_EVAL_RESULT
-============================
+EVAL_DEBUG_IFELSE_TRUE
+======================
.. code-block:: text
- %1: Expression '%2' evaluated to %3
+ %1: Popping %2 (true) and %3, leaving %4
-Logged at debug log level 50.
-This debug message indicates that the expression of a template client class has
-been successfully evaluated. The client class name and the result value of the
-evaluation are printed.
+Logged at debug log level 55.
+This debug message indicates that the condition is true so
+the ifelse branch value is removed and the iftrue branch value
+is left on the value stack.
-DHCPSRV_TIMERMGR_CALLBACK_FAILED
-================================
+EVAL_DEBUG_INT16TOTEXT
+======================
.. code-block:: text
- running handler for timer %1 caused exception: %2
+ %1: Pushing Int16 %2
-This error message is emitted when the timer elapsed and the
-operation associated with this timer has thrown an exception.
-The timer name and the reason for exception is logged.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents a 16 bit integer.
-DHCPSRV_TIMERMGR_REGISTER_TIMER
-===============================
+EVAL_DEBUG_INT32TOTEXT
+======================
.. code-block:: text
- registering timer: %1, using interval: %2 ms
+ %1: Pushing Int32 %2
-Logged at debug log level 40.
-A debug message issued when the new interval timer is registered in
-the Timer Manager. This timer will have a callback function
-associated with it, and this function will be executed according
-to the interval specified. The unique name of the timer and the
-interval at which the callback function will be executed is
-included in the message.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents a 32 bit integer.
-DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION
-====================================
+EVAL_DEBUG_INT8TOTEXT
+=====================
.. code-block:: text
- running operation for timer: %1
+ %1: Pushing Int8 %2
-Logged at debug log level 50.
-A debug message issued when the Timer Manager is about to
-run a periodic operation associated with the given timer.
-An example of such operation is a periodic cleanup of
-expired leases. The name of the timer is included in the
-message.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents an 8 bit integer.
-DHCPSRV_TIMERMGR_START_TIMER
-============================
+EVAL_DEBUG_IPADDRESS
+====================
.. code-block:: text
- starting timer: %1
+ %1: Pushing IPAddress %2
-Logged at debug log level 40.
-A debug message issued when the registered interval timer is
-being started. If this operation is successful the timer will
-periodically execute the operation associated with it. The
-name of the started timer is included in the message.
+Logged at debug log level 55.
+This debug message indicates that the given binary string is being pushed
+onto the value stack. This represents either an IPv4 or IPv6 address.
+The string is displayed in hex.
-DHCPSRV_TIMERMGR_STOP_TIMER
-===========================
+EVAL_DEBUG_IPADDRESSTOTEXT
+==========================
.. code-block:: text
- stopping timer: %1
+ %1: Pushing IPAddress %2
-Logged at debug log level 40.
-A debug message issued when the registered interval timer is
-being stopped. The timer remains registered and can be restarted
-if necessary. The name of the timer is included in the message.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents either an IPv4 or IPv6
+address.
-DHCPSRV_TIMERMGR_UNREGISTER_ALL_TIMERS
-======================================
+EVAL_DEBUG_LCASE
+================
.. code-block:: text
- unregistering all timers
+ %1: Popping string %2 and pushing converted value to lower case %3
-Logged at debug log level 40.
-A debug message issued when all registered interval timers are
-being unregistered from the Timer Manager.
+Logged at debug log level 55.
+This debug message indicates that the given string representation is being
+converted to lower case and pushed onto the value stack.
-DHCPSRV_TIMERMGR_UNREGISTER_TIMER
-=================================
+EVAL_DEBUG_MATCH
+================
.. code-block:: text
- unregistering timer: %1
-
-Logged at debug log level 40.
-A debug message issued when one of the registered interval timers
-is unregistered from the Timer Manager. The name of the timer is
-included in the message.
+ Matching '%1' on %2, result %3
-****
-DHCP
-****
+Logged at debug log level 55.
+This debug message indicates that the given regular expression was matched
+with the popped value. The result was pushed onto the value stack.
-DHCP_DDNS_ADD_FAILED
-====================
+EVAL_DEBUG_MATCH_ERROR
+======================
.. code-block:: text
- DHCP_DDNS Request ID %1: Transaction outcome %2
+ Matching '%1' on %2 raised an error: %3
-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.
+This error message indicates that an error occurred while evaluating the given
+regular expression against the popped value.
-DHCP_DDNS_ADD_SUCCEEDED
-=======================
+EVAL_DEBUG_MEMBER
+=================
.. code-block:: text
- DHCP_DDNS Request ID %1: successfully added the DNS mapping addition for this request: %2
+ %1: Checking membership of '%2', pushing result %3
-This is an informational message issued after DHCP_DDNS has submitted DNS
-mapping additions which were received and accepted by an appropriate DNS server.
+Logged at debug log level 55.
+This debug message indicates that the membership of the packet for
+the client class was checked.
-DHCP_DDNS_AT_MAX_TRANSACTIONS
-=============================
+EVAL_DEBUG_NOT
+==============
.. code-block:: text
- application has %1 queued requests but has reached maximum number of %2 concurrent transactions
+ %1: Popping %2 pushing %3
Logged at debug log level 55.
-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.
+This debug message indicates that the first value is popped from
+the value stack, negated and then pushed onto the value stack.
+The string is displayed in text.
-DHCP_DDNS_CLEARED_FOR_SHUTDOWN
-==============================
+EVAL_DEBUG_OPTION
+=================
.. code-block:: text
- application has met shutdown criteria for shutdown type: %1
+ %1: Pushing option %2 with value %3
-Logged at debug log level 0.
-This is a debug message issued when the application has been instructed
-to shutdown and has met the required criteria to exit.
+Logged at debug log level 55.
+This debug message indicates that the given string representing the
+value of the requested option is being pushed onto the value stack.
+The string may be the text or binary value of the string based on the
+representation type requested (.text or .hex) or "true" or "false" if
+the requested type is .exists. The option code may be for either an
+option or a sub-option as requested in the classification statement.
-DHCP_DDNS_CONFIGURE
-===================
+EVAL_DEBUG_OR
+=============
.. code-block:: text
- configuration %1 received: %2
+ %1: Popping %2 and %3 pushing %4
-Logged at debug log level 40.
-This is a debug message issued when the DHCP-DDNS application configure method
-has been invoked.
+Logged at debug log level 55.
+This debug message indicates that two values are popped from
+the value stack. Then are then combined via logical or and
+the result is pushed onto the value stack. The string is displayed
+in text.
-DHCP_DDNS_CONFIGURED_CALLOUT_DROP
-=================================
+EVAL_DEBUG_PKT
+==============
.. code-block:: text
- configuration was rejected because a callout set the next step to 'drop': %1
+ %1: Pushing PKT meta data %2 with value %3
-This error message indicates that the DHCP-DDNS had failed configuration
-attempt because the next step of the configured callout was set to 'drop'
-by a hook library. The error message provided by the hook library is displayed.
+Logged at debug log level 55.
+This debug message indicates that the given binary string representing
+the value of the requested meta data is being pushed onto the value stack.
+The string is displayed in hex at the exception of interface name.
-DHCP_DDNS_CONFIG_CHECK_FAIL
-===========================
+EVAL_DEBUG_PKT4
+===============
.. code-block:: text
- DHCP-DDNS server configuration check failed: %1
+ %1: Pushing PKT4 field %2 with value %3
-This error message indicates that the DHCP-DDNS had failed configuration
-check. Details are provided. Additional details may be available
-in earlier log entries, possibly on lower levels.
+Logged at debug log level 55.
+This debug message indicates that the given binary string representing
+the value of the requested field is being pushed onto the value stack.
+The string is displayed in hex.
-DHCP_DDNS_CONFIG_FAIL
-=====================
+EVAL_DEBUG_PKT6
+===============
.. code-block:: text
- DHCP-DDNS server configuration failed: %1
+ %1: Pushing PKT6 field %2 with value %3
-This error message indicates that the DHCP-DDNS had failed configuration
-attempt. Details are provided. Additional details may be available
-in earlier log entries, possibly on lower levels.
+Logged at debug log level 55.
+This debug message indicates that the given binary string representing
+the value of the requested field is being pushed onto the value stack.
+The string is displayed in hex.
-DHCP_DDNS_CONFIG_SYNTAX_WARNING
+EVAL_DEBUG_POP_AND_BRANCH_FALSE
===============================
.. code-block:: text
- DHCP-DDNS server configuration syntax warning: %1
+ Value is false: branching to %1
-This warning message indicates that the DHCP-DDNS configuration had a minor
-syntax error. The error was displayed and the configuration parsing resumed.
+Logged at debug log level 55.
+This debug message indicates that a branch on false condition is performed
+to the displayed target.
-DHCP_DDNS_FAILED
-================
+EVAL_DEBUG_POP_OR_BRANCH_FALSE
+==============================
.. code-block:: text
- application experienced a fatal error: %1
+ Value is false: keeping it and branching to %1
-This is a debug message issued when the DHCP-DDNS application encounters an
-unrecoverable error from within the event loop.
+Logged at debug log level 55.
+This debug message indicates that a branch on false condition is performed
+to the displayed target.
-DHCP_DDNS_FORWARD_ADD_BAD_DNSCLIENT_STATUS
-==========================================
+EVAL_DEBUG_POP_OR_BRANCH_TRUE
+=============================
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while adding a forward address mapping for FQDN %3 to DNS server %4
+ Value is true: keeping it and branching to %1
-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.
+Logged at debug log level 55.
+This debug message indicates that a branch on true condition is performed
+to the displayed target.
-DHCP_DDNS_FORWARD_ADD_BUILD_FAILURE
-===================================
+EVAL_DEBUG_RELAY6
+=================
.. code-block:: text
- DNS Request ID %1: update message to add a forward DNS entry could not be constructed for this request: %2, reason: %3
+ %1: Pushing PKT6 relay field %2 nest %3 with value %4
-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.
+Logged at debug log level 55.
+This debug message indicates that the given binary string representing
+the value of the requested field is being pushed onto the value stack.
+The string is displayed in hex.
-DHCP_DDNS_FORWARD_ADD_IO_ERROR
-==============================
+EVAL_DEBUG_RELAY6_RANGE
+=======================
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping add for FQDN %2 to DNS server %3
+ %1: Pushing PKT6 relay field %2 nest %3 with value %4
-This is an error message issued when a communication error occurs while
-DHCP_DDNS is carrying out a forward address add. The application will
-retry against the same server or others as appropriate.
+Logged at debug log level 55.
+This debug message is generated if the nest field is out of range. The
+empty string will always be the value pushed onto the stack.
-DHCP_DDNS_FORWARD_ADD_REJECTED
-==============================
+EVAL_DEBUG_SPLIT
+================
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to add the address mapping for FQDN, %3, with an RCODE: %4
+ %1: Popping field %2, delimiters %3, string %4, pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that three values are being popped from the stack
+and a result is being pushed onto the stack. The values being popped are the
+field, delimiter and string. The result is the extracted field which is pushed
+onto the stack. The strings are displayed in hex.
-DHCP_DDNS_FORWARD_ADD_RESP_CORRUPT
-==================================
+EVAL_DEBUG_SPLIT_DELIM_EMPTY
+============================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while adding forward address mapping for FQDN, %3
+ %1: Popping field %2, delimiters %3, string %4, pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that the delimiter popped from the stack was empty
+and so the result will be the entire string. The field, delimiter and string
+are still popped from the stack and the result is still pushed.
-DHCP_DDNS_FORWARD_ADD_TIMEOUT
-=============================
+EVAL_DEBUG_SPLIT_EMPTY
+======================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping add for FQDN %2 to DNS server %3
+ %1: Popping field %2, delimiters %3, string %4, pushing result %5
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a forward address add. The application will retry against the same
-server or others as appropriate.
+Logged at debug log level 55.
+This debug message indicates that the string popped from the stack was empty
+and so the result will also be empty. The field, delimiter and string are
+still popped from the stack and the result is still pushed.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_BAD_DNSCLIENT_STATUS
-===================================================
+EVAL_DEBUG_SPLIT_FIELD_OUT_OF_RANGE
+===================================
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing a forward address mapping for FQDN %3 to DNS server %4
+ %1: Popping field %2, delimiters %3, string %4, pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that the field is either less than one or larger
+than the number of fields in the string popped from the stack. The result will
+be empty. The field, delimiter and string are still popped from the stack and
+the result is still pushed.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_BUILD_FAILURE
-============================================
+EVAL_DEBUG_STRING
+=================
.. code-block:: text
- DNS Request ID %1: update message to remove a forward DNS Address entry could not be constructed for this request: %2, reason: %3
+ %1: Pushing text string %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.
-/*sar*/
+Logged at debug log level 55.
+This debug message indicates that the given text string is being pushed
+onto the value stack. The string is displayed in text.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_IO_ERROR
-=======================================
+EVAL_DEBUG_SUBSTRING
+====================
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping address removal for FQDN %2 to DNS server %3
+ %1: Popping length %2, start %3, string %4 pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that three values are being popped from
+the value stack and a result is being pushed onto the value stack. The
+values being popped are the starting point and length of a substring to
+extract from the given string. The resulting string is pushed onto
+the stack. The strings are displayed in hex.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_REJECTED
-=======================================
+EVAL_DEBUG_SUBSTRING_EMPTY
+==========================
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to remove the forward address mapping for FQDN, %3, with an RCODE: %4
+ %1: Popping length %2, start %3, string %4 pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that the string popped from the stack was empty
+and so the result will also be empty. The start, length and string are
+still popped from the stack and the result is still pushed.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_RESP_CORRUPT
-===========================================
+EVAL_DEBUG_SUBSTRING_RANGE
+==========================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing forward address mapping for FQDN, %3
+ %1: Popping length %2, start %3, string %4 pushing result %5
-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.
+Logged at debug log level 55.
+This debug message indicates that the value of start is outside of the
+string and an empty result will be pushed onto the stack. The start,
+length and string are still popped from the stack and the result is
+still pushed. The strings are displayed in hex.
-DHCP_DDNS_FORWARD_REMOVE_ADDRS_TIMEOUT
-======================================
+EVAL_DEBUG_SUB_OPTION
+=====================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping address removal for FQDN %2 to DNS server %3
+ %1: Pushing option %2 sub-option %3 with value %4
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a forward mapping address removal. The application will retry against the same
-server or others as appropriate.
+This debug message indicates that the given string representing the
+value of the requested sub-option of the requested parent option is
+being pushed onto the value stack. The string may be the text or
+binary value of the string based on the representation type requested
+(.text or .hex) or "true" or "false" if the requested type is .exists.
+The codes are the parent option and the sub-option codes as requested
+in the classification statement.
-DHCP_DDNS_FORWARD_REMOVE_RRS_BAD_DNSCLIENT_STATUS
-=================================================
+EVAL_DEBUG_SUB_OPTION_NO_OPTION
+===============================
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing forward RRs for FQDN %3 to DNS server %4
+ %1: Requested option %2 sub-option %3, but the parent option is not present, pushing result %4
-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.
+This debug message indicates that the parent option was not found.
+The codes are the parent option and the sub-option codes as requested
+in the classification statement.
-DHCP_DDNS_FORWARD_REMOVE_RRS_BUILD_FAILURE
-==========================================
+EVAL_DEBUG_TOHEXSTRING
+======================
.. code-block:: text
- DNS Request ID %1: update message to remove forward DNS RR entries could not be constructed for this request: %2, reason: %3
+ %1: Popping binary value %2 and separator %3, pushing result %4
-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.
+Logged at debug log level 55.
+This debug message indicates that two values are being popped from
+the value stack and a result is being pushed onto the value stack.
+The values being popped are the binary value to convert and the separator.
+The binary value is converted to its hexadecimal string representation
+and pushed onto the stack. The binary value is displayed in hex.
-DHCP_DDNS_FORWARD_REMOVE_RRS_IO_ERROR
-=====================================
+EVAL_DEBUG_UCASE
+================
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a forward RR removal for FQDN %2 to DNS server %3
+ %1: Popping string %2 and pushing converted value to upper case %3
-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.
+Logged at debug log level 55.
+This debug message indicates that the given string representation is being
+converted to upper case and pushed onto the value stack.
-DHCP_DDNS_FORWARD_REMOVE_RRS_REJECTED
-=====================================
+EVAL_DEBUG_UINT16TOTEXT
+=======================
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to remove forward RR entries for FQDN, %3, with an RCODE: %4
+ %1: Pushing UInt16 %2
-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.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents a 16 bit unsigned integer.
-DHCP_DDNS_FORWARD_REMOVE_RRS_RESP_CORRUPT
-=========================================
+EVAL_DEBUG_UINT32TOTEXT
+=======================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing forward RRs for FQDN, %3
-
-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.
-/*sar*/
+ %1: Pushing UInt32 %2
-DHCP_DDNS_FORWARD_REMOVE_RRS_TIMEOUT
-====================================
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents a 32 bit unsigned integer.
+
+EVAL_DEBUG_UINT8TOTEXT
+======================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for response to forward RR removal for FQDN %2 to DNS server %3
+ %1: Pushing UInt8 %2
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a forward RR removal. The application will retry against the same
-server or others as appropriate.
+Logged at debug log level 55.
+This debug message indicates that the given address string representation is
+being pushed onto the value stack. This represents an 8 bit unsigned integer.
-DHCP_DDNS_FORWARD_REPLACE_BAD_DNSCLIENT_STATUS
-==============================================
+EVAL_DEBUG_VENDOR_CLASS_DATA
+============================
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while replacing forward address mapping for FQDN %3 to DNS server %4
+ %1: Data %2 (out of %3 received) in vendor class found, pushing result '%4'
-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.
+Logged at debug log level 55.
+This debug message indicates that vendor class option was found and passed
+enterprise-id checks and has sufficient number of data chunks. The total number
+of chunks and value pushed are reported as debugging aid.
-DHCP_DDNS_FORWARD_REPLACE_BUILD_FAILURE
-=======================================
+EVAL_DEBUG_VENDOR_CLASS_DATA_NOT_FOUND
+======================================
.. code-block:: text
- DNS Request ID %1: update message to replace a forward DNS entry could not be constructed from this request: %2, reason: %3
+ %1: Requested data index %2, but option with enterprise-id %3 has only %4 data tuple(s), pushing result '%5'
-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.
+Logged at debug log level 55.
+This debug message indicates that vendor class option was found and passed
+enterprise-id checks, but does not have sufficient number of data chunks.
+Note that the index starts at 0, so there has to be at least (index + 1)
+data chunks.
-DHCP_DDNS_FORWARD_REPLACE_IO_ERROR
-==================================
+EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID
+=====================================
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a forward mapping replace for FQDN %2 to DNS server %3
+ %1: Pushing enterprise-id %2 as result 0x%3
-This is an error message issued when a communication error occurs while
-DHCP_DDNS is carrying out a forward mapping replace. The application will
-retry against the same server or others as appropriate.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated and vendor
+class option was found and its enterprise-id is being reported.
-DHCP_DDNS_FORWARD_REPLACE_REJECTED
-==================================
+EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID_MISMATCH
+==============================================
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to replace the address mapping for FQDN, %3, with an RCODE: %4
+ %1: Was looking for %2, option had %3, pushing result '%4'
-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.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated
+and vendor class option was found, but has different enterprise-id than specified
+in the expression.
-DHCP_DDNS_FORWARD_REPLACE_RESP_CORRUPT
-======================================
+EVAL_DEBUG_VENDOR_CLASS_EXISTS
+==============================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while replacing forward address mapping for FQDN, %3
+ %1: Option with enterprise-id %2 found, pushing result '%3'
-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.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated and vendor
+class option was found.
-DHCP_DDNS_FORWARD_REPLACE_TIMEOUT
+EVAL_DEBUG_VENDOR_CLASS_NO_OPTION
=================================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for a response to forward mapping replace for FQDN %2 to DNS server %3
+ %1: Option with code %2 missing, pushing result '%3'
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a forward mapping replace. The application will retry against the same
-server or others as appropriate.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated
+and vendor class option was not found.
-DHCP_DDNS_FWD_REQUEST_IGNORED
-=============================
+EVAL_DEBUG_VENDOR_ENTERPRISE_ID
+===============================
.. code-block:: text
- Request ID %1: Forward updates are disabled, the forward portion of request will be ignored: %2
+ %1: Pushing enterprise-id %2 as result 0x%3
Logged at debug log level 55.
-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.
+This debug message indicates that the expression has been evaluated and vendor
+option was found and its enterprise-id is being reported.
-DHCP_DDNS_INVALID_NCR
-=====================
+EVAL_DEBUG_VENDOR_ENTERPRISE_ID_MISMATCH
+========================================
.. code-block:: text
- application received an invalid DNS update request: %1
+ %1: Was looking for %2, option had %3, pushing result '%4'
-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.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated
+and vendor option was found, but has different enterprise-id than specified
+in the expression.
-DHCP_DDNS_INVALID_RESPONSE
-==========================
+EVAL_DEBUG_VENDOR_EXISTS
+========================
.. code-block:: text
- received response to DNS Update message is malformed: %1
+ %1: Option with enterprise-id %2 found, pushing result '%3'
-Logged at debug log level 50.
-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.
+Logged at debug log level 55.
+This debug message indicates that the expression has been evaluated and vendor
+option was found.
-DHCP_DDNS_LISTENING_ON_ALL_INTERFACES
-=====================================
+****
+FLEX
+****
+
+FLEX_ID_EXPRESSION_EMPTY
+========================
.. code-block:: text
- the DHCP-DDNS server has been configured to listen on %1. This is an insecure configuration supported for testing purposes only
+ Specified identifier-expression is empty
-This is a warning message issued when the DHCP-DDNS server is configured to
-listen at either `0.0.0.0` or `::`. It is possible for a malicious attacker to send
-bogus NameChangeRequests to it and change entries in the DNS. For this reason,
-listening on all interfaces should only be used when deploying in containers
-or for testing purposes. A future version of Kea will disable this ability by
-default.
+This warning message is printed when the flex-id library is being loaded,
+but the expression used to generate the identifier is empty. The library
+will load, but will not generate any identifiers. Please make sure that
+the identifier-expression parameter is specified.
-DHCP_DDNS_NCR_FLUSH_IO_ERROR
+FLEX_ID_EXPRESSION_EVALUATED
============================
.. code-block:: text
- DHCP-DDNS Last send before stopping did not complete successfully: %1
+ Expression evaluated for packet to "%1" (size: %2)
-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.
+Logged at debug log level 40.
+This debug message is printed every time a packet evaluation is successful.
+This means that the identifier expression has been generated. Note that
+depending on the expression and content of the incoming packet, the
+expression may be evaluated to an empty string.
-DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR
-================================
+FLEX_ID_EXPRESSION_EVALUATED_NP
+===============================
.. code-block:: text
- application encountered an error while closing the listener used to receive NameChangeRequests : %1
+ Expression evaluated for packet to 0x%1 (size: %2)
-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.
+This debug message is printed every time a packet evaluation is successful.
+This means that the identifier expression has been generated. As it is
+not printable it is converted to hexadecimal.
-DHCP_DDNS_NCR_RECV_NEXT_ERROR
-=============================
+FLEX_ID_EXPRESSION_HEX
+======================
.. code-block:: text
- application could not initiate the next read following a request receive.
+ evaluated expression in hexadecimal form "%1"
-This is an 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.
+Logged at debug log level 40.
+This debug message provides a hexadecimal representation of the evaluated
+expression. This is useful for debugging purposes because further logs use
+hexadecimal format for logging.
-DHCP_DDNS_NCR_SEND_CLOSE_ERROR
-==============================
+FLEX_ID_EXPRESSION_INVALID_JSON_TYPE
+====================================
.. code-block:: text
- DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests: %1
+ The identifier-expression is %1, but expected JSON string
-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.
+This error message is printed when the flex-id library is being loaded,
+but the expression used to generate the identifier is malformed. It has
+a different JSON type (e.g. is a map) rather than expected string.
-DHCP_DDNS_NCR_SEND_NEXT_ERROR
-=============================
+FLEX_ID_EXPRESSION_NOT_DEFINED
+==============================
.. code-block:: text
- DHCP-DDNS client could not initiate the next request send following send completion: %1
+ Expression (identifier-expression) is not defined.
-This is an 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.
+This warning message is printed when the flex-id library is loaded, but the
+expression used to generate the identifier is not specified. The library
+will load, but will not generate any identifiers. Please make sure that
+the identifier-expression parameter is specified for your library.
-DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR
-===================================
+FLEX_ID_EXPRESSION_PARSE_FAILED
+===============================
.. code-block:: text
- NCR UDP watch socket failed to clear: %1
+ The identifier-expression is [%1], but fails to parse with error: %2
-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.
+This error message is printed when the flex-id library is being loaded,
+but the expression used to generate the identifier is malformed. It failed
+to parse.
-DHCP_DDNS_NCR_UDP_RECV_CANCELED
-===============================
+FLEX_ID_IGNORE_IAID_APPLIED_ON_NA
+=================================
.. code-block:: text
- UDP socket receive was canceled while listening for DNS Update requests
+ the ignore-iaid has changed IAID (%1) to 0 for the IA_NA option.
Logged at debug log level 40.
-This is a debug message indicating that the listening on a UDP socket
-for DNS update requests has been canceled. This is a normal part of
-suspending listening operations.
+This DEBUG message is printed when the flex-id library did apply the ignore-iaid
+flag and changed IAID to 0 because the received packet contains exactly one
+IA_NA.
-DHCP_DDNS_NCR_UDP_RECV_ERROR
-============================
+FLEX_ID_IGNORE_IAID_APPLIED_ON_PD
+=================================
.. code-block:: text
- UDP socket receive error while listening for DNS Update requests: %1
+ the ignore-iaid has changed IAID (%1) to 0 for the IA_PD option.
-This is an error message indicating that an I/O error occurred while listening
-over a UDP socket for DNS update requests. This could indicate a network
-connectivity or system resource issue.
+Logged at debug log level 40.
+This DEBUG message is printed when the flex-id library did apply the ignore-iaid
+flag and changed IAID to 0 because the received packet contains exactly one
+IA_PD.
-DHCP_DDNS_NCR_UDP_SEND_CANCELED
-===============================
+FLEX_ID_IGNORE_IAID_ENABLED
+===========================
.. code-block:: text
- UDP socket send was canceled while sending a DNS Update request to DHCP_DDNS: %1
+ the ignore-iaid is set. It only has an effect on clients with at most one IA_NA and one IA_PD.
-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.
+This WARNING message is printed when the flex-id library is being loaded,
+and the ignore-iaid parameter is set. This flag will enable the server to drop
+packets which contain more than one IA_NA and one IA_PD.
-DHCP_DDNS_NCR_UDP_SEND_ERROR
-============================
+FLEX_ID_IGNORE_IAID_JSON_TYPE
+=============================
.. code-block:: text
- UDP socket send error while sending a DNS Update request: %1
+ the ignore-iaid is %1 but expected boolean value
-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.
+This error message is printed when the flex-id library is being loaded,
+but the ignore-iaid parameter is malformed, i.e. it has a different
+type than expected. It is expected to be a boolean value.
-DHCP_DDNS_NOT_ON_LOOPBACK
-=========================
+FLEX_ID_IGNORE_IAID_NOT_APPLIED_ON_NA
+=====================================
.. code-block:: text
- 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
+ the ignore-iaid was not applied on the packet because it contains more than one IA_NA.
-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.
+Logged at debug log level 40.
+This WARNING message is printed when the flex-id library did not apply the
+ignore-iaid flag because the received packet contains more than one IA_NA.
-DHCP_DDNS_NO_ELIGIBLE_JOBS
-==========================
+FLEX_ID_IGNORE_IAID_NOT_APPLIED_ON_PD
+=====================================
.. code-block:: text
- although there are queued requests, there are pending transactions for each, Queue count: %1 Transaction count: %2
+ the ignore-iaid was not applied on the packet because it contains more than one IA_PD.
-Logged at debug log level 55.
-This is a debug message issued when all of the queued requests represent clients
-for which there is an update already in progress. This may occur under
-normal operations but should be temporary situation.
+Logged at debug log level 40.
+This WARNING message is printed when the flex-id library did not apply the
+ignore-iaid flag because the received packet contains more than one IA_PD.
-DHCP_DDNS_NO_FWD_MATCH_ERROR
-============================
+FLEX_ID_LOAD_ERROR
+==================
.. code-block:: text
- Request ID %1: the configured list of forward DDNS domains does not contain a match for: %2 The request has been discarded.
+ An error occurred loading the library %1
-This is an error message that indicates that DHCP_DDNS received a request to
-update 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.
+This error message will be printed when an error is encountered during
+loading of the library. Details of the problem are printed as parameter
+to this message.
-DHCP_DDNS_NO_MATCH
-==================
+FLEX_ID_REPLACE_CLIENT_ID_JSON_TYPE
+===================================
.. code-block:: text
- No DNS servers match FQDN %1
+ the replace-client-id is %1 but expected boolean value
-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.
+This error message is printed when the flex-id library is being loaded,
+but the replace-client-id parameter is malformed, i.e. it has a different
+type than expected. It is expected to be a boolean value.
-DHCP_DDNS_NO_REV_MATCH_ERROR
-============================
+FLEX_ID_RESTORE_CLIENT_ID
+=========================
.. code-block:: text
- Request ID %1: the configured list of reverse DDNS domains does not contain a match for: %2 The request has been discarded.
+ restoring original client identifier '%1' in the response
-This is an error message that indicates that DHCP_DDNS received a request to
-update 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.
+Logged at debug log level 40.
+This debug message is issued when the original (client supplied) client identifier
+is restored into the server's response.
-DHCP_DDNS_QUEUE_MGR_QUEUE_FULL
-==============================
+FLEX_ID_RESTORE_DUID
+====================
.. code-block:: text
- application request queue has reached maximum number of entries %1
+ restoring original DUID "%1" in the response
-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.
+Logged at debug log level 40.
+This debug message is issued when the original (client supplied) client identifier
+is restored into the server"s response.
-DHCP_DDNS_QUEUE_MGR_QUEUE_RECEIVE
-=================================
+FLEX_ID_UNLOAD
+==============
.. code-block:: text
- Request ID %1: received and queued a request.
+ Flex-id library has been unloaded.
-Logged at debug log level 55.
-This is an informational message indicating that the NameChangeRequest listener used
-by DHCP-DDNS to receive a request has received a request and queued it for further
-processing.
+This informational message signifies that the flexible-identifier library has been
+unloaded.
-DHCP_DDNS_QUEUE_MGR_RECONFIGURING
-=================================
+FLEX_ID_USED_AS_CLIENT_ID
+=========================
.. code-block:: text
- application is reconfiguring the queue manager
+ using flexible identifier "%1" as client identifier
Logged at debug log level 40.
-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.
+This debug message is issued to indicate that the library is removing client
+supplied client identifier from the received message and is inserting flexible
+identifier based client identifier instead. The server will use this new client
+identifier for processing the packet. The original client identifier will be
+restored in the pkt4_send callout and sent back to the client.
-DHCP_DDNS_QUEUE_MGR_RECOVERING
-==============================
+FLEX_OPTION_LOAD_ERROR
+======================
.. code-block:: text
- application is attempting to recover from a queue manager IO error
+ loading Flex Option hooks library failed: %1
-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.
+This error message indicates an error during loading the Flex Option
+hooks library. The details of the error are provided as argument of
+the log message.
-DHCP_DDNS_QUEUE_MGR_RECV_ERROR
-==============================
+FLEX_OPTION_PROCESS_ADD
+=======================
.. code-block:: text
- application's queue manager was notified of a request receive error by its listener.
+ Added the option code %1 with value %2
-This is an error message indicating that the NameChangeRequest listener used by
-DHCP-DDNS to receive requests encountered an 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.
+Logged at debug log level 40.
+This debug message is printed when an option was added into the response
+packet. The option code and the value (between quotes if printable, in
+hexadecimal if not) are provided.
-DHCP_DDNS_QUEUE_MGR_RESUME_ERROR
+FLEX_OPTION_PROCESS_CLIENT_CLASS
================================
.. code-block:: text
- application could not restart the queue manager, reason: %1
+ Skip processing of the option code %1 for class '%2'
-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.
+Logged at debug log level 40.
+This debug message is printed when the processing for an option is skipped
+because the query does not belongs to the client class. The option code and
+the client class name are provided.
-DHCP_DDNS_QUEUE_MGR_RESUMING
-============================
+FLEX_OPTION_PROCESS_ERROR
+=========================
.. code-block:: text
- application is resuming listening for requests now that the request queue size has reached %1 of a maximum %2 allowed
+ An error occurred processing query %1: %2
-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.
+This error message indicates an error during processing of a query
+by the Flex Option hooks library. The client identification information
+from the query and the details of the error are provided as arguments
+of the log message.
-DHCP_DDNS_QUEUE_MGR_STARTED
-===========================
+FLEX_OPTION_PROCESS_REMOVE
+==========================
.. code-block:: text
- application's queue manager has begun listening for requests.
+ Removed option code %1
-Logged at debug log level 0.
-This is a debug message indicating that DHCP_DDNS's Queue Manager has
-successfully started and is now listening for NameChangeRequests.
+Logged at debug log level 40.
+This debug message is printed when an option was removed from the response
+packet. The option code is provided.
-DHCP_DDNS_QUEUE_MGR_START_ERROR
-===============================
+FLEX_OPTION_PROCESS_SUB_ADD
+===========================
.. code-block:: text
- application could not start the queue manager, reason: %1
+ Added the sub-option code %1 in option code %2 with value %3
-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.
+Logged at debug log level 40.
+This debug message is printed when an sub-option was added into the response
+packet. The sub-option and container option codes, and the value
+(between quotes if printable, in hexadecimal if not) are provided.
-DHCP_DDNS_QUEUE_MGR_STOPPED
-===========================
+FLEX_OPTION_PROCESS_SUB_CLIENT_CLASS
+====================================
.. code-block:: text
- application's queue manager has stopped listening for requests.
+ Skip processing of the sub-option code %1 in option code %2 for class '%3'
Logged at debug log level 40.
-This is a debug 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.
+This debug message is printed when the processing for a sub-option is skipped
+because the query does not belongs to the client class. The sub-option and
+container option codes, and the client class name are provided.
-DHCP_DDNS_QUEUE_MGR_STOPPING
-============================
+FLEX_OPTION_PROCESS_SUB_REMOVE
+==============================
.. code-block:: text
- application is stopping the queue manager for %1
+ Removed sub-option code %1 in option code %2
-Logged at debug log level 0.
-This is an informational message indicating that DHCP_DDNS is stopping the
-queue manager either to reconfigure it or as part of application shutdown.
+Logged at debug log level 40.
+This debug message is printed when a sub-option was removed from the response
+packet. The sub-option and container option codes are provided.
-DHCP_DDNS_QUEUE_MGR_STOP_ERROR
-==============================
+FLEX_OPTION_PROCESS_SUB_SUPERSEDE
+=================================
.. code-block:: text
- application encountered an error stopping the queue manager: %1
+ Supersedes the sub-option code %1 in option code %2 with value %3
-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.
+Logged at debug log level 40.
+This debug message is printed when a sub-option was superseded into the
+response packet. The sub-option and container option codes, and the value
+(between quotes if printable, in hexadecimal if not) are provided.
-DHCP_DDNS_QUEUE_MGR_UNEXPECTED_HANDLER_ERROR
-============================================
+FLEX_OPTION_PROCESS_SUPERSEDE
+=============================
.. code-block:: text
- application's queue manager request receive handler experienced an unexpected exception %1:
+ Supersedes the option code %1 with value %2
-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.
+Logged at debug log level 40.
+This debug message is printed when an option was superseded into the response
+packet. The option code and the value (between quotes if printable, in
+hexadecimal if not) are provided.
-DHCP_DDNS_QUEUE_MGR_UNEXPECTED_STOP
-===================================
+FLEX_OPTION_PROCESS_VENDOR_ID_MISMATCH
+======================================
.. code-block:: text
- application's queue manager receive was
+ Skip processing of vendor option code %1 with vendor id %2 not matching wanted %3
-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.
+Logged at debug log level 40.
+This debug message is printed when a sub-option of a vendor option is
+processed but vendor ids do not match. The code of the vendor option
+and the two vendor ids are provided.
-DHCP_DDNS_REMOVE_FAILED
-=======================
+****
+FUZZ
+****
+
+FUZZ_DATA_READ
+==============
.. code-block:: text
- DHCP_DDNS Request ID %1: Transaction outcome: %2
+ read %1 byte(s) from AFL via stdin
-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.
+Logged at debug log level 50.
+A debug message output to indicate how much data has been received from
+the fuzzer via stdin
-DHCP_DDNS_REMOVE_SUCCEEDED
-==========================
+FUZZ_INIT_COMPLETE
+==================
.. code-block:: text
- DHCP_DDNS Request ID %1: successfully removed the DNS mapping addition for this request: %2
+ fuzz initialization complete: interface %1, address %2, port %3, max loops %4
-This is an informational message issued after DHCP_DDNS has submitted DNS
-mapping removals which were received and accepted by an appropriate DNS server.
+An informational message output when the fuzzing initialization function has
+completed successfully. The parameters listed are those which must be/can be
+set via environment variables.
-DHCP_DDNS_REQUEST_DROPPED
-=========================
+FUZZ_INIT_FAIL
+==============
.. code-block:: text
- Request ID %1: Request contains no enabled update requests and will be dropped: %2
+ fuzz initialization failure, reason: %1
-Logged at debug log level 55.
-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 received that asks only for reverse updates
-then the request is dropped.
+An error message reported if the fuzzing initialization failed. The reason
+for the failure is given in the message.
-DHCP_DDNS_REVERSE_REMOVE_BAD_DNSCLIENT_STATUS
-=============================================
+FUZZ_READ_FAIL
+==============
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing reverse address mapping for FQDN %3 to DNS server %4
+ error reading input from fuzzer: %1
-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.
+This error is reported if the read of data from the fuzzer (which is
+received over stdin) fails, or if a read returns zero bytes. If this
+occurs, the thread will sleep for a short period before retrying the read.
+The message includes the reason for the failure.
-DHCP_DDNS_REVERSE_REMOVE_BUILD_FAILURE
-======================================
+FUZZ_SEND
+=========
.. code-block:: text
- DNS Request ID %1: update message to remove a reverse DNS entry could not be constructed from this request: %2, reason: %3
+ sent %1 byte(s) to the socket connected to the Kea interface
-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.
+Logged at debug log level 50.
+A debug message stating that the sendto() call in the main fuzzing function
+has successfully completed and reporting the number of bytes sent. This
+call sends data received from AFL to the port on which Kea is listening.
-DHCP_DDNS_REVERSE_REMOVE_IO_ERROR
-=================================
+FUZZ_SEND_ERROR
+===============
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a reverse mapping remove for FQDN %2 to DNS server %3
+ failed to send data to Kea input socket: %1
-This is an error message issued when a communication error occurs while
-DHCP_DDNS is carrying out a reverse mapping remove. The application will
-retry against the same server or others as appropriate.
+This error will be reported if the sendto() call in the fuzzing thread (which
+sends data received from AFL to the socket on which Kea is listening) fails.
+The reason for the failure is given in the message. The fuzzing code will
+attempt to continue from this, but it may cause the fuzzing process to fail.
-DHCP_DDNS_REVERSE_REMOVE_REJECTED
-=================================
+FUZZ_SHORT_SEND
+===============
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to remove the reverse mapping for FQDN, %3, with an RCODE: %4
+ expected to send %1 bytes to Kea input socket but only sent %2
-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.
+A warning message that is output if the sendto() call (used to send data
+from the fuzzing thread to the main Kea processing) did not send as much
+data as that read from AFL. This may indicate a problem in the underlying
+communications between the fuzzing thread and the main Kea processing.
-DHCP_DDNS_REVERSE_REMOVE_RESP_CORRUPT
-=====================================
+***
+GSS
+***
+
+GSS_TSIG_COMMAND_PROCESSED_FAILED
+=================================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while removing reverse address mapping for FQDN, %3
+ command_processed callout failed: %1.
-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.
+This error message is issued when the callout for the command_processed
+callout point failed. The argument contains a reason for the error.
-DHCP_DDNS_REVERSE_REMOVE_TIMEOUT
-================================
+GSS_TSIG_LOAD_FAILED
+====================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for a response to reverse mapping remove for FQDN %2 to DNS server %3
+ GSS-TSIG hooks library failed to load: %1.
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a reverse mapping remove. The application will retry against the same
-server or others as appropriate.
+This error message indicates that an error occurred attempting to
+load the GSS-TSIG hooks library. The argument details the error.
-DHCP_DDNS_REVERSE_REPLACE_BAD_DNSCLIENT_STATUS
-==============================================
+GSS_TSIG_LOAD_OK
+================
.. code-block:: text
- DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while replacing reverse address mapping for FQDN %3 to DNS server %4
+ GSS-TSIG hooks library loaded successfully.
-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.
+This info message indicates that the GSS-TSIG hooks library has
+been loaded successfully.
-DHCP_DDNS_REVERSE_REPLACE_BUILD_FAILURE
-=======================================
+GSS_TSIG_MANAGER_STARTED
+========================
.. code-block:: text
- DNS Request ID %1: update message to replace a reverse DNS entry could not be constructed from this request: %2, reason: %3
+ hooks library GSS-TSIG key periodic manager started.
-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.
+Logged at debug log level 40.
+This debug message is issued when the GSS-TSIG key periodic manager has started.
-DHCP_DDNS_REVERSE_REPLACE_IO_ERROR
-==================================
+GSS_TSIG_MANAGER_STOPPED
+========================
.. code-block:: text
- DHCP_DDNS Request ID %1: encountered an IO error sending a reverse mapping replacement for FQDN %2 to DNS server %3
+ hooks library GSS-TSIG key periodic manager stopped.
-This is an error message issued when a communication error occurs while
-DHCP_DDNS is carrying out a reverse mapping replacement. The application will
-retry against the same server or others as appropriate.
+Logged at debug log level 40.
+This debug message is issued when the GSS-TSIG key periodic manager has stopped.
-DHCP_DDNS_REVERSE_REPLACE_REJECTED
-==================================
+GSS_TSIG_MANAGER_STOP_ERROR
+===========================
.. code-block:: text
- DNS Request ID %1: Server, %2, rejected a DNS update request to replace the reverse mapping for FQDN, %3, with an RCODE: %4
+ manager stop error: %1
-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.
+This error message is issued when the GSS-TSIG key periodic manager has stopped
+but an error is detected. The error message in the argument gives details about
+the problem.
-DHCP_DDNS_REVERSE_REPLACE_RESP_CORRUPT
-======================================
+GSS_TSIG_MANAGER_STOP_GENERAL_ERROR
+===================================
.. code-block:: text
- DHCP_DDNS Request ID %1: received a corrupt response from the DNS server, %2, while replacing reverse address mapping for FQDN, %3
+ manager stop general error
-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.
+This error message is issued when the GSS-TSIG key periodic manager has stopped
+but a general error is detected.
-DHCP_DDNS_REVERSE_REPLACE_TIMEOUT
-=================================
+GSS_TSIG_NEW_KEY
+================
.. code-block:: text
- DHCP_DDNS Request ID %1: timed out waiting for a response to reverse mapping replacement for FQDN %2 to DNS server %3
+ new GSS-TSIG key '%1' was created.
-This is an error message issued when no response is received from the DNS
-server before exceeding dns-server-timeout while DHCP_DDNS is carrying out
-a reverse mapping replacement. The application will retry against the same
-server or others as appropriate.
+Logged at debug log level 40.
+This info message indicates that the GSS-TSIG hooks library has
+created a new GSS-TSIG key. The name of the new key is displayed.
-DHCP_DDNS_REV_REQUEST_IGNORED
+GSS_TSIG_NEW_KEY_SETUP_FAILED
=============================
.. code-block:: text
- Request ID %1: Reverse updates are disabled, the reverse portion of request will be ignored: %2
+ new GSS-TSIG key '%1' setup failed: %2.
-Logged at debug log level 55.
-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.
+This warning message is issued when the setup of a new GSS-TSIG key failed.
+The name of the new key and the error are displayed.
-DHCP_DDNS_RUN_EXIT
-==================
+GSS_TSIG_NEW_KEY_SETUP_SUCCEED
+==============================
.. code-block:: text
- application is exiting the event loop
+ new GSS-TSIG key '%1' setup succeed.
-Logged at debug log level 0.
-This is a debug message issued when the DHCP-DDNS server exits its
-event lo
+Logged at debug log level 40.
+This debug message is issued when the setup of a new GSS-TSIG key
+successfully finished. The name of the new key is displayed.
-DHCP_DDNS_SHUTDOWN_COMMAND
-==========================
+GSS_TSIG_OLD_KEY_REMOVED
+========================
.. code-block:: text
- application received shutdown command with args: %1
+ %1 old GSS-TSIG keys were removed
-Logged at debug log level 0.
-This is a debug message issued when the application has been instructed
-to shut down by the controller.
+Logged at debug log level 40.
+This debug message is issued when some old keys (older than 2 times the maximum
+TKEY lifetime) were removed. The number of removed keys is displayed.
-DHCP_DDNS_STARTED
-=================
+GSS_TSIG_UNLOAD_OK
+==================
.. code-block:: text
- Kea DHCP-DDNS server version %1 started
-
-This informational message indicates that the DHCP-DDNS server has
-processed all configuration information and is ready to begin processing.
-The version is also printed.
+ GSS-TSIG hooks library unloaded successfully.
-DHCP_DDNS_STARTING_TRANSACTION
-==============================
+This info message indicates that the GSS-TSIG hooks library has
+been unloaded successfully.
+
+GSS_TSIG_VERIFIED
+=================
.. code-block:: text
- Request ID %1:
+ GSS-TSIG verify successed.
-Logged at debug log level 50.
-This is a debug message issued when DHCP-DDNS has begun a transaction for
-a given request.
+Logged at debug log level 40.
+A debug message issued when GSS-TSIG verification succeeded.
-DHCP_DDNS_STATE_MODEL_UNEXPECTED_ERROR
-======================================
+GSS_TSIG_VERIFY_FAILED
+======================
.. code-block:: text
- Request ID %1: application encountered an unexpected error while carrying out a NameChangeRequest: %2
+ GSS-TSIG verify failed: %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.
+This info message indicates that GSS-TSIG verification failed.
+The argument details the error.
-DHCP_DDNS_TRANS_SEND_ERROR
-==========================
+**
+HA
+**
+
+HA_BUFFER4_RECEIVE_FAILED
+=========================
.. code-block:: text
- Request ID %1: application encountered an unexpected error while attempting to send a DNS update: %2
+ buffer4_receive callout failed: %1
-This is error message issued when the application is able to construct an update
-message but the attempt to send it suffered an 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.
+This error message is issued when the callout for the buffer4_receive hook
+point failed. This may occur as a result of an internal server error.
+The argument contains a reason for the error.
-DHCP_DDNS_UDP_SENDER_WATCH_SOCKET_CLOSE_ERROR
-=============================================
+HA_BUFFER4_RECEIVE_NOT_FOR_US
+=============================
.. code-block:: text
- watch socket failed to close: %1
+ %1: dropping query to be processed by another server
-This is an error message that indicates the application was unable to close
-the inbound or outbound side of a NCR sender's watch socket. While technically
-possible the error is highly unlikely to occur and should not impair the
-application's ability to process requests.
+Logged at debug log level 40.
+This debug message is issued when the received DHCPv4 query is dropped
+by this server because it should be served by another server. This
+is the case when the remote server was designated to process the packet
+as a result of load balancing or because it is a primary server in the
+hot standby configuration. The argument provides client identification
+information retrieved from the query.
-DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR
+HA_BUFFER4_RECEIVE_PACKET_OPTIONS_SKIPPED
=========================================
.. code-block:: text
- unexpected exception thrown from the application receive completion handler: %1
+ an error unpacking an option, caused subsequent options to be skipped: %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.
+Logged at debug log level 40.
+A debug message issued when an option failed to unpack correctly, making it
+impossible to unpack the remaining options in the DHCPv4 query. The server
+will still attempt to service the packet. The sole argument provides a
+reason for unpacking error.
-DHCP_DDNS_UPDATE_REQUEST_SENT
-=============================
+HA_BUFFER4_RECEIVE_UNPACK_FAILED
+================================
.. code-block:: text
- Request ID %1: %2 to server: %3
-
-Logged at debug log level 50.
-This is a debug message issued when DHCP_DDNS sends a DNS request to a DNS
-server.
+ failed to parse query from %1 to %2, received over interface %3, reason: %4
-****
-EVAL
-****
+Logged at debug log level 40.
+This debug message is issued when received DHCPv4 query is malformed and
+can't be parsed by the buffer4_receive callout. The query will be
+dropped by the server. The first three arguments specify source IP address,
+destination IP address and the interface. The last argument provides a
+reason for failure.
-EVAL_DEBUG_AND
-==============
+HA_BUFFER6_RECEIVE_FAILED
+=========================
.. code-block:: text
- %1: Popping %2 and %3 pushing %4
+ buffer6_receive callout failed: %1
-Logged at debug log level 55.
-This debug message indicates that two values are popped from
-the value stack. Then are then combined via logical and and
-the result is pushed onto the value stack.
+This error message is issued when the callout for the buffer6_receive hook
+point failed. This may occur as a result of an internal server error.
+The argument contains a reason for the error.
-EVAL_DEBUG_BRANCH
-=================
+HA_BUFFER6_RECEIVE_NOT_FOR_US
+=============================
.. code-block:: text
- Branching to %1
+ %1: dropping query to be processed by another server
-Logged at debug log level 55.
-This debug message indicates that an unconditional branch is performed
-to the displayed target.
+Logged at debug log level 40.
+This debug message is issued when the received DHCPv6 query is dropped
+by this server because it should be served by another server. This
+is the case when the remote server was designated to process the packet
+as a result of load balancing or because it is a primary server in the
+hot standby configuration. The argument provides client identification
+information retrieved from the query.
-EVAL_DEBUG_CONCAT
-=================
+HA_BUFFER6_RECEIVE_PACKET_OPTIONS_SKIPPED
+=========================================
.. code-block:: text
- %1: Popping %2 and %3 pushing %4
+ an error unpacking an option, caused subsequent options to be skipped: %1
-Logged at debug log level 55.
-This debug message indicates that the two strings are being popped off
-of the stack. They are then concatenated and the resulting string is
-pushed onto the stack. The strings are displayed in hex.
+Logged at debug log level 40.
+A debug message issued when an option failed to unpack correctly, making it
+impossible to unpack the remaining options in the DHCPv6 query. The server
+will still attempt to service the packet. The sole argument provides a
+reason for unpacking error.
-EVAL_DEBUG_EQUAL
-================
+HA_BUFFER6_RECEIVE_UNPACK_FAILED
+================================
.. code-block:: text
- %1: Popping %2 and %3 pushing result %4
+ failed to parse query from %1 to %2, received over interface %3, reason: %4
-Logged at debug log level 55.
-This debug message indicates that the two strings are being popped off
-of the value stack and the result of comparing them is being pushed onto
-the value stack. The strings are displayed in hex.
+Logged at debug log level 40.
+This debug message is issued when received DHCPv6 query is malformed and
+can't be parsed by the buffer6_receive callout. The query will be
+dropped by the server. The first three arguments specify source IP address,
+destination IP address and the interface. The last argument provides a
+reason for failure.
-EVAL_DEBUG_HEXSTRING
-====================
+HA_COMMAND_PROCESSED_FAILED
+===========================
.. code-block:: text
- %1: Pushing hex string %2
+ command_processed callout failed: %1
-Logged at debug log level 55.
-This debug message indicates that the given binary string is being pushed
-onto the value stack. The string is displayed in hex.
+This error message is issued when the callout for the command_processed hook
+point failed. The argument contains a reason for the error.
-EVAL_DEBUG_IFELSE_FALSE
-=======================
+HA_COMMUNICATION_INTERRUPTED
+============================
.. code-block:: text
- %1: Popping %2 (false) and %3, leaving %4
+ %1: communication with %2 is interrupted
-Logged at debug log level 55.
-This debug message indicates that the condition is false so
-the iftrue branch value is removed and the ifelse branch value
-is left on the value stack.
+This warning message is issued by the server which discovered that the
+communication to the active partner has been interrupted for a time
+period longer than the configured heartbeat-delay time. At this stage
+the server starts the failover procedure by monitoring the DHCP traffic
+sent to the partner and checking whether the partner server responds to
+this traffic. If the max-unacked-clients value is set to 0 such
+verification is disabled in which case the server will transition to
+the partner-down state.
-EVAL_DEBUG_IFELSE_TRUE
-======================
+HA_COMMUNICATION_INTERRUPTED_CLIENT4
+====================================
.. code-block:: text
- %1: Popping %2 (true) and %3, leaving %4
+ %1: new client %2 attempting to get a lease from the partner
-Logged at debug log level 55.
-This debug message indicates that the condition is true so
-the ifelse branch value is removed and the iftrue branch value
-is left on the value stack.
+This informational message is issued when the surviving server observes
+a DHCP packet sent to the partner with which the communication is interrupted.
+The client whose packet is observed is not yet considered "unacked" because
+the secs field value does not exceed the configured threshold specified
+with max-ack-delay.
-EVAL_DEBUG_INT16TOTEXT
-======================
+HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED
+============================================
.. code-block:: text
- %1: Pushing Int16 %2
+ %1: partner server failed to respond to %2, %3 clients unacked so far, %4 clients left before transitioning to the partner-down state
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents a 16 bit integer.
+This informational message is issued when the surviving server determines
+that its partner failed to respond to the DHCP query and that this client
+is considered to not be served by the partner. The surviving server counts
+such clients and if the number of such clients exceeds the max-unacked-clients
+threshold, the server will transition to the partner-down state. The first
+argument specifies the relationship name. The second argument contains client
+identification information. The third argument specifies the number of
+clients to which the server has failed to respond. The forth argument specifies
+the number of additional clients which, if not provisioned, will cause the
+server to transition to the partner-down state.
-EVAL_DEBUG_INT32TOTEXT
-======================
+HA_COMMUNICATION_INTERRUPTED_CLIENT6
+====================================
.. code-block:: text
- %1: Pushing Int32 %2
+ %1: new client %2 attempting to get a lease from the partner
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents a 32 bit integer.
+This informational message is issued when the surviving server observes
+a DHCP packet sent to the partner with which the communication is interrupted.
+The client whose packet is observed is not yet considered "unacked" because
+the elapsed time option value does not exceed the configured threshold
+specified with max-ack-delay. The sole argument specifies client
+identification information.
-EVAL_DEBUG_INT8TOTEXT
-=====================
+HA_COMMUNICATION_INTERRUPTED_CLIENT6_UNACKED
+============================================
.. code-block:: text
- %1: Pushing Int8 %2
+ %1: partner server failed to respond to %2, %3 clients unacked so far, %4 clients left before transitioning to the partner-down state
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents an 8 bit integer.
+This informational message is issued when the surviving server determines
+that its partner failed to respond to the DHCP query and that this client
+is considered to not be served by the partner. The surviving server counts
+such clients and if the number of such clients exceeds the max-unacked-clients
+threshold, the server will transition to the partner-down state. The first
+argument specifies the relationship name. The second argument contains client
+identification information. The third argument specifies the number of clients
+to which the server has failed to respond. The forth argument specifies the
+number of additional clients which, if not provisioned, will cause the server
+to transition to the partner-down state.
-EVAL_DEBUG_IPADDRESS
-====================
+HA_CONFIGURATION_FAILED
+=======================
.. code-block:: text
- %1: Pushing IPAddress %2
+ failed to configure High Availability hooks library: %1
-Logged at debug log level 55.
-This debug message indicates that the given binary string is being pushed
-onto the value stack. This represents either an IPv4 or IPv6 address.
-The string is displayed in hex.
+This error message is issued when there is an error configuring the HA hooks
+library. The argument provides the detailed error message.
-EVAL_DEBUG_IPADDRESSTOTEXT
-==========================
+HA_CONFIGURATION_SUCCESSFUL
+===========================
.. code-block:: text
- %1: Pushing IPAddress %2
+ HA hook library has been successfully configured
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents either an IPv4 or IPv6
-address.
+This informational message is issued when the HA hook library configuration
+parser successfully parses and validates the new configuration.
-EVAL_DEBUG_LCASE
-================
+HA_CONFIG_AUTO_FAILOVER_DISABLED
+================================
.. code-block:: text
- %1: Popping string %2 and pushing converted value to lower case %3
+ %1: auto-failover disabled
-Logged at debug log level 55.
-This debug message indicates that the given string representation is being
-converted to lower case and pushed onto the value stack.
+This warning message is issued to indicate that the 'auto-failover' parameter
+was administratively disabled for the specified server. The server will not
+automatically start serving partner's scope when the partner failure is detected.
+The server administrator will need to enable this scope manually by
+sending appropriate ha-scopes command.
-EVAL_DEBUG_MATCH
-================
+HA_CONFIG_DHCP_MT_DISABLED
+==========================
.. code-block:: text
- Matching '%1' on %2, result %3
+ %1: HA multi-threading has been disabled, it cannot be enabled when Kea global multi-threading is disabled
-Logged at debug log level 55.
-This debug message indicates that the given regular expression was matched
-with the popped value. The result was pushed onto the value stack.
+This informational message is issued when HA configuration has enabled
+multi-threading while Kea global configuration has multi-threading disabled.
-EVAL_DEBUG_MATCH_ERROR
-======================
+HA_CONFIG_DHCP_MT_DISABLED_AND_KEA_MT_ENABLED
+=============================================
.. code-block:: text
- Matching '%1' on %2 raised an error: %3
+ %1: HA multi-threading is disabled while Kea global multi-threading is enabled which most likely cause performance degradation.
-This error message indicates that an error occurred while evaluating the given
-regular expression against the popped value.
+This warning message is issued when HA configuration has disabled
+multi-threading while Kea global configuration has multi-threading enabled.
+This will likely cause performance degradation.
-EVAL_DEBUG_MEMBER
-=================
+HA_CONFIG_LEASE_SYNCING_DISABLED
+================================
.. code-block:: text
- %1: Checking membership of '%2', pushing result %3
+ %1: lease database synchronization between HA servers is disabled
-Logged at debug log level 55.
-This debug message indicates that the membership of the packet for
-the client class was checked.
+This warning message is issued when the lease database synchronization is
+administratively disabled. This is valid configuration if the leases are
+replicated between lease databases via some other mechanism, e.g. SQL
+database replication.
-EVAL_DEBUG_NOT
-==============
+HA_CONFIG_LEASE_SYNCING_DISABLED_REMINDER
+=========================================
.. code-block:: text
- %1: Popping %2 pushing %3
+ %1: bypassing SYNCING state because lease database synchronization is administratively disabled
-Logged at debug log level 55.
-This debug message indicates that the first value is popped from
-the value stack, negated and then pushed onto the value stack.
-The string is displayed in text.
+This informational message is issued as a reminder that lease database
+synchronization is administratively disabled and therefore the server
+transitions directly from the "waiting" to "ready" state.
-EVAL_DEBUG_OPTION
-=================
+HA_CONFIG_LEASE_UPDATES_AND_SYNCING_DIFFER
+==========================================
.. code-block:: text
- %1: Pushing option %2 with value %3
+ %1: unusual configuration where "send-lease-updates": %2 and "sync-leases": %3
-Logged at debug log level 55.
-This debug message indicates that the given string representing the
-value of the requested option is being pushed onto the value stack.
-The string may be the text or binary value of the string based on the
-representation type requested (.text or .hex) or "true" or "false" if
-the requested type is .exists. The option code may be for either an
-option or a sub-option as requested in the classification statement.
+This warning message is issued when the configuration values of the
+send-lease-updates and sync-leases parameters differ. This may be a
+valid configuration but is unusual. Normally, if the lease database
+with replication is in use, both values are set to false. If a lease
+database without replication is in use (e.g. memfile), both values
+are set to true. Providing different values for those parameters means
+that an administrator either wants the server to not synchronize
+leases upon startup but later send lease updates to the partner, or
+the lease database should be synchronized upon startup, but no lease
+updates are later sent as a result of leases allocation.
-EVAL_DEBUG_OR
-=============
+HA_CONFIG_LEASE_UPDATES_DISABLED
+================================
.. code-block:: text
- %1: Popping %2 and %3 pushing %4
+ %1: lease updates will not be generated
-Logged at debug log level 55.
-This debug message indicates that two values are popped from
-the value stack. Then are then combined via logical or and
-the result is pushed onto the value stack. The string is displayed
-in text.
+This warning message is issued when the lease updates are administratively
+disabled. This is valid configuration if the leases are replicated to the
+partner's database via some other mechanism, e.g. SQL database replication.
-EVAL_DEBUG_PKT
-==============
+HA_CONFIG_LEASE_UPDATES_DISABLED_REMINDER
+=========================================
.. code-block:: text
- %1: Pushing PKT meta data %2 with value %3
+ %1: lease updates are administratively disabled and will not be generated while in %2 state
-Logged at debug log level 55.
-This debug message indicates that the given binary string representing
-the value of the requested meta data is being pushed onto the value stack.
-The string is displayed in hex at the exception of interface name.
+This informational message is issued as a reminder that the lease updates
+are administratively disabled and will not be issued in the HA state to
+which the server has transitioned. The sole argument specifies the state
+into which the server has transitioned.
-EVAL_DEBUG_PKT4
-===============
+HA_CONFIG_SYSTEM_MT_UNSUPPORTED
+===============================
.. code-block:: text
- %1: Pushing PKT4 field %2 with value %3
+ %1: HA multi-threading has been disabled, auto-detection of thread support reports 0
-Logged at debug log level 55.
-This debug message indicates that the given binary string representing
-the value of the requested field is being pushed onto the value stack.
-The string is displayed in hex.
+This informational message is issued when HA multi-threading configuration has
+specified auto-detection for the number of threads to use and the system
+reports the number of concurrent threads as 0. If you know your system can
+support multiple threads, then you may override this condition by specifying
+explicit values for http-listener-threads and http-client-threads.
-EVAL_DEBUG_PKT6
-===============
+HA_CONTINUE_HANDLER_FAILED
+==========================
.. code-block:: text
- %1: Pushing PKT6 field %2 with value %3
+ ha-continue command failed: %1
-Logged at debug log level 55.
-This debug message indicates that the given binary string representing
-the value of the requested field is being pushed onto the value stack.
-The string is displayed in hex.
+This error message is issued to indicate that the ha-continue command handler
+failed while processing the command. The argument provides the reason for
+failure.
-EVAL_DEBUG_POP_AND_BRANCH_FALSE
-===============================
+HA_DEINIT_OK
+============
.. code-block:: text
- Value is false: branching to %1
+ unloading High Availability hooks library successful
-Logged at debug log level 55.
-This debug message indicates that a branch on false condition is performed
-to the displayed target.
+This informational message indicates that the High Availability hooks library
+has been unloaded successfully.
-EVAL_DEBUG_POP_OR_BRANCH_FALSE
-==============================
+HA_DHCP4_START_SERVICE_FAILED
+=============================
.. code-block:: text
- Value is false: keeping it and branching to %1
+ failed to start DHCPv4 HA services in dhcp4_srv_configured callout: %1
-Logged at debug log level 55.
-This debug message indicates that a branch on false condition is performed
-to the displayed target.
+This error message is issued when an attempt to start High Availability services
+for the DHCPv4 server failed in the dhcp4_srv_configured callout. This
+is internal server error and a bug report should be created.
-EVAL_DEBUG_POP_OR_BRANCH_TRUE
+HA_DHCP6_START_SERVICE_FAILED
=============================
.. code-block:: text
- Value is true: keeping it and branching to %1
+ failed to start DHCPv6 HA services in dhcp6_srv_configured callout: %1
-Logged at debug log level 55.
-This debug message indicates that a branch on true condition is performed
-to the displayed target.
+This error message is issued when an attempt to start High Availability services
+for the DHCPv6 server failed in the dhcp6_srv_configured callout. This
+is internal server error and a bug report should be created.
-EVAL_DEBUG_RELAY6
-=================
+HA_DHCP_DISABLE_COMMUNICATIONS_FAILED
+=====================================
.. code-block:: text
- %1: Pushing PKT6 relay field %2 nest %3 with value %4
+ %1: failed to send request to disable DHCP service of %2: %3
-Logged at debug log level 55.
-This debug message indicates that the given binary string representing
-the value of the requested field is being pushed onto the value stack.
-The string is displayed in hex.
+This warning message indicates that there was a problem in communication with a
+HA peer while sending the dhcp-disable command. The first argument specifies
+the local server's name. The second argument provides the remote server's name.
+The third argument provides a reason for failure.
-EVAL_DEBUG_RELAY6_RANGE
-=======================
+HA_DHCP_DISABLE_FAILED
+======================
.. code-block:: text
- %1: Pushing PKT6 relay field %2 nest %3 with value %4
+ %1: failed to disable DHCP service of %2: %3
-Logged at debug log level 55.
-This debug message is generated if the nest field is out of range. The
-empty string will always be the value pushed onto the stack.
+This warning message indicates that a peer returned an error status code
+in response to a dhcp-disable command. The first argument provides the
+local server's name. The second argument provides the remote server's name.
+The third argument provides a reason for failure.
-EVAL_DEBUG_SPLIT
-================
+HA_DHCP_ENABLE_COMMUNICATIONS_FAILED
+====================================
.. code-block:: text
- %1: Popping field %2, delimiters %3, string %4, pushing result %5
+ %1: failed to send request to enable DHCP service of %2: %3
-Logged at debug log level 55.
-This debug message indicates that three values are being popped from the stack
-and a result is being pushed onto the stack. The values being popped are the
-field, delimiter and string. The result is the extracted field which is pushed
-onto the stack. The strings are displayed in hex.
+This warning message indicates that there was a problem in communication with a
+HA peer while sending the dhcp-enable command. The first argument provides the
+local server's name. The second argument provides the remote server's name. The
+third argument provides a reason for failure.
-EVAL_DEBUG_SPLIT_DELIM_EMPTY
-============================
+HA_DHCP_ENABLE_FAILED
+=====================
.. code-block:: text
- %1: Popping field %2, delimiters %3, string %4, pushing result %5
+ %1: failed to enable DHCP service of %2: %3
-Logged at debug log level 55.
-This debug message indicates that the delimiter popped from the stack was empty
-and so the result will be the entire string. The field, delimiter and string
-are still popped from the stack and the result is still pushed.
+This warning message indicates that a peer returned an error status code
+in response to a dhcp-enable command. The first argument provides the
+local server's name. The second argument provides the remote server's name.
+The third argument provides a reason for failure.
-EVAL_DEBUG_SPLIT_EMPTY
-======================
+HA_HEARTBEAT_COMMUNICATIONS_FAILED
+==================================
.. code-block:: text
- %1: Popping field %2, delimiters %3, string %4, pushing result %5
+ %1: failed to send heartbeat to %2: %3
-Logged at debug log level 55.
-This debug message indicates that the string popped from the stack was empty
-and so the result will also be empty. The field, delimiter and string are
-still popped from the stack and the result is still pushed.
+This warning message indicates that there was a problem in communication with a
+HA peer while sending a heartbeat. This is a first sign that the peer may be
+down. The server will keep trying to send heartbeats until it considers that
+communication is interrupted.
-EVAL_DEBUG_SPLIT_FIELD_OUT_OF_RANGE
-===================================
+HA_HEARTBEAT_FAILED
+===================
.. code-block:: text
- %1: Popping field %2, delimiters %3, string %4, pushing result %5
+ %1: heartbeat to %2 failed: %3
-Logged at debug log level 55.
-This debug message indicates that the field is either less than one or larger
-than the number of fields in the string popped from the stack. The result will
-be empty. The field, delimiter and string are still popped from the stack and
-the result is still pushed.
+This warning message indicates that a peer returned an error status code
+in response to a heartbeat. This is the sign that the peer may not function
+properly. The server will keep trying to send heartbeats until it considers
+that communication is interrupted.
-EVAL_DEBUG_STRING
-=================
+HA_HEARTBEAT_HANDLER_FAILED
+===========================
.. code-block:: text
- %1: Pushing text string %2
+ heartbeat command failed: %1
-Logged at debug log level 55.
-This debug message indicates that the given text string is being pushed
-onto the value stack. The string is displayed in text.
+This error message is issued to indicate that the heartbeat command handler
+failed while processing the command. The argument provides the reason for
+failure.
-EVAL_DEBUG_SUBSTRING
-====================
+HA_HIGH_CLOCK_SKEW
+==================
.. code-block:: text
- %1: Popping length %2, start %3, string %4 pushing result %5
+ %1: %2, please synchronize clocks!
-Logged at debug log level 55.
-This debug message indicates that three values are being popped from
-the value stack and a result is being pushed onto the value stack. The
-values being popped are the starting point and length of a substring to
-extract from the given string. The resulting string is pushed onto
-the stack. The strings are displayed in hex.
+This warning message is issued when the clock skew between the active servers
+exceeds 30 seconds. The HA service continues to operate but may not function
+properly, especially for low lease lifetimes. The administrator should
+should synchronize the clocks, e.g. using NTP. If the clock skew exceeds
+60 seconds, the HA service will terminate.
-EVAL_DEBUG_SUBSTRING_EMPTY
-==========================
+HA_HIGH_CLOCK_SKEW_CAUSED_TERMINATION
+=====================================
.. code-block:: text
- %1: Popping length %2, start %3, string %4 pushing result %5
+ %1: %2, causing HA service to terminate
-Logged at debug log level 55.
-This debug message indicates that the string popped from the stack was empty
-and so the result will also be empty. The start, length and string are
-still popped from the stack and the result is still pushed.
+This warning message is issued when the clock skew between the active servers
+exceeds 60 seconds. The HA service stops. The servers will continue to respond
+to the DHCP queries but won't exchange lease updates or send heartbeats.
+The administrator is required to synchronize the clocks and then restart the
+servers to resume the HA service.
-EVAL_DEBUG_SUBSTRING_RANGE
-==========================
+HA_INIT_OK
+==========
.. code-block:: text
- %1: Popping length %2, start %3, string %4 pushing result %5
+ loading High Availability hooks library successful
-Logged at debug log level 55.
-This debug message indicates that the value of start is outside of the
-string and an empty result will be pushed onto the stack. The start,
-length and string are still popped from the stack and the result is
-still pushed. The strings are displayed in hex.
+This informational message indicates that the High Availability hooks library
+has been loaded successfully. Enjoy!
-EVAL_DEBUG_SUB_OPTION
-=====================
+HA_INVALID_PARTNER_STATE_COMMUNICATION_RECOVERY
+===============================================
.. code-block:: text
- %1: Pushing option %2 sub-option %3 with value %4
+ %1: partner is in the communication-recovery state unexpectedly
-This debug message indicates that the given string representing the
-value of the requested sub-option of the requested parent option is
-being pushed onto the value stack. The string may be the text or
-binary value of the string based on the representation type requested
-(.text or .hex) or "true" or "false" if the requested type is .exists.
-The codes are the parent option and the sub-option codes as requested
-in the classification statement.
+This warning message is issued when a partner is in the communication-recovery
+state, and this server is not running in the load balancing mode. The server
+may only transition to the communication-recovery state when it runs in the
+load balancing mode. The HA mode of both servers must be the same.
-EVAL_DEBUG_SUB_OPTION_NO_OPTION
-===============================
+HA_INVALID_PARTNER_STATE_HOT_STANDBY
+====================================
.. code-block:: text
- %1: Requested option %2 sub-option %3, but the parent option is not present, pushing result %4
+ %1: partner is in the hot-standby state unexpectedly
-This debug message indicates that the parent option was not found.
-The codes are the parent option and the sub-option codes as requested
-in the classification statement.
+This warning message is issued when a partner is in the hot-standby state,
+and this server is not running in the hot standby mode. The server may only
+transition to the hot-standby state when it runs in the hot standby mode.
+The HA mode of both servers must be the same.
-EVAL_DEBUG_TOHEXSTRING
-======================
+HA_INVALID_PARTNER_STATE_LOAD_BALANCING
+=======================================
.. code-block:: text
- %1: Popping binary value %2 and separator %3, pushing result %4
+ %1: partner is in the load-balancing state unexpectedly
-Logged at debug log level 55.
-This debug message indicates that two values are being popped from
-the value stack and a result is being pushed onto the value stack.
-The values being popped are the binary value to convert and the separator.
-The binary value is converted to its hexadecimal string representation
-and pushed onto the stack. The binary value is displayed in hex.
+This warning message is issued when a partner is in the load-balancing state,
+and this server is not running in the load balancing mode. The server may only
+transition to the load-balancing state when it runs in the load balancing mode.
+The HA mode of both servers must be the same.
-EVAL_DEBUG_UCASE
-================
+HA_LEASE4_SERVER_DECLINE_FAILED
+===============================
.. code-block:: text
- %1: Popping string %2 and pushing converted value to upper case %3
+ lease4_server_decline callout failed: %1
-Logged at debug log level 55.
-This debug message indicates that the given string representation is being
-converted to upper case and pushed onto the value stack.
+This error message is issued when the callout for the lease4_server_decline hook
+point failed. This includes unexpected errors like wrong arguments provided to
+the callout by the DHCP server (unlikely internal server error).
+The argument contains a reason for the error.
-EVAL_DEBUG_UINT16TOTEXT
-=======================
+HA_LEASES4_COMMITTED_FAILED
+===========================
.. code-block:: text
- %1: Pushing UInt16 %2
+ leases4_committed callout failed: %1
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents a 16 bit unsigned integer.
+This error message is issued when the callout for the leases4_committed hook
+point failed. This includes unexpected errors like wrong arguments provided to
+the callout by the DHCP server (unlikely internal server error).
+The argument contains a reason for the error.
-EVAL_DEBUG_UINT32TOTEXT
-=======================
+HA_LEASES4_COMMITTED_NOTHING_TO_UPDATE
+======================================
.. code-block:: text
- %1: Pushing UInt32 %2
+ %1: leases4_committed callout was invoked without any leases
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents a 32 bit unsigned integer.
+Logged at debug log level 40.
+This debug message is issued when the "leases4_committed" callout returns
+because there are neither new leases nor deleted leases for which updates
+should be sent. The sole argument specifies the details of the client
+which sent the packet.
-EVAL_DEBUG_UINT8TOTEXT
-======================
+HA_LEASES4_COMMITTED_NO_RELATIONSHIP
+====================================
.. code-block:: text
- %1: Pushing UInt8 %2
+ %1: HA relationship not found: %2
-Logged at debug log level 55.
-This debug message indicates that the given address string representation is
-being pushed onto the value stack. This represents an 8 bit unsigned integer.
+This error message is issued when the relationship for the server name provided
+by the earlier callouts was not found in the HA configuration. This error is
+highly unlikely and rather indicates some programming error. The first argument
+is the client identification information. The second argument holds a more
+detailed error message.
-EVAL_DEBUG_VENDOR_CLASS_DATA
-============================
+HA_LEASES6_COMMITTED_FAILED
+===========================
.. code-block:: text
- %1: Data %2 (out of %3 received) in vendor class found, pushing result '%4'
+ leases6_committed callout failed: %1
-Logged at debug log level 55.
-This debug message indicates that vendor class option was found and passed
-enterprise-id checks and has sufficient number of data chunks. The total number
-of chunks and value pushed are reported as debugging aid.
+This error message is issued when the callout for the leases6_committed hook
+point failed. This includes unexpected errors like wrong arguments provided to
+the callout by the DHCP server (unlikely internal server error).
+The argument contains a reason for the error.
-EVAL_DEBUG_VENDOR_CLASS_DATA_NOT_FOUND
+HA_LEASES6_COMMITTED_NOTHING_TO_UPDATE
======================================
.. code-block:: text
- %1: Requested data index %2, but option with enterprise-id %3 has only %4 data tuple(s), pushing result '%5'
+ %1: leases6_committed callout was invoked without any leases
-Logged at debug log level 55.
-This debug message indicates that vendor class option was found and passed
-enterprise-id checks, but does not have sufficient number of data chunks.
-Note that the index starts at 0, so there has to be at least (index + 1)
-data chunks.
+Logged at debug log level 40.
+This debug message is issued when the "leases6_committed" callout returns
+because there are neither new leases nor deleted leases for which updates
+should be sent. The sole argument specifies the details of the client
+which sent the packet.
-EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID
-=====================================
+HA_LEASES6_COMMITTED_NO_RELATIONSHIP
+====================================
.. code-block:: text
- %1: Pushing enterprise-id %2 as result 0x%3
+ %1: HA relationship not found: %2
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated and vendor
-class option was found and its enterprise-id is being reported.
+This error message is issued when the relationship for the server name provided
+by the earlier callouts was not found in the HA configuration. This error is
+highly unlikely and rather indicates some programming error. The first argument
+is the client identification information. The second argument holds a more
+detailed error message.
-EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID_MISMATCH
-==============================================
+HA_LEASES_BACKLOG_COMMUNICATIONS_FAILED
+=======================================
.. code-block:: text
- %1: Was looking for %2, option had %3, pushing result '%4'
+ %1: failed to communicate with %2 while sending lease updates backlog: %3
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated
-and vendor class option was found, but has different enterprise-id than specified
-in the expression.
+This error message is issued to indicate that there was a communication error
+with a partner server while sending outstanding lease updates after resuming
+connection. The third argument contains a reason for the error.
-EVAL_DEBUG_VENDOR_CLASS_EXISTS
-==============================
+HA_LEASES_BACKLOG_FAILED
+========================
.. code-block:: text
- %1: Option with enterprise-id %2 found, pushing result '%3'
+ %1: failed to send lease updates backlog to %2: %3
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated and vendor
-class option was found.
+This error message is issued to indicate that sending lease updates backlog
+to a partner server failed. The lease updates backlog is sent to the partner
+after resuming temporarily broken communication with the partner. If this
+operation fails the server will transition to the waiting state to initiate
+full lease database synchronization.
-EVAL_DEBUG_VENDOR_CLASS_NO_OPTION
+HA_LEASES_BACKLOG_NOTHING_TO_SEND
=================================
.. code-block:: text
- %1: Option with code %2 missing, pushing result '%3'
-
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated
-and vendor class option was not found.
+ %1: no leases in backlog after communication recovery
-EVAL_DEBUG_VENDOR_ENTERPRISE_ID
-===============================
-
-.. code-block:: text
-
- %1: Pushing enterprise-id %2 as result 0x%3
-
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated and vendor
-option was found and its enterprise-id is being reported.
+This informational message is issued when there are no outstanding leases to
+be sent after communication recovery with a partner. This means that the
+communication interruption was short enough that no DHCP clients obtained
+any leases from the server while it was in the communication-recovery state.
+The server may now transition to the load-balancing state.
-EVAL_DEBUG_VENDOR_ENTERPRISE_ID_MISMATCH
-========================================
+HA_LEASES_BACKLOG_START
+=======================
.. code-block:: text
- %1: Was looking for %2, option had %3, pushing result '%4'
+ %1: starting to send %2 outstanding lease updates to %3
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated
-and vendor option was found, but has different enterprise-id than specified
-in the expression.
+This informational message is issued when the server starts to send outstanding
+lease updates to the partner after resuming communications. The first argument
+specifies the local server's name. The second argument specifies the number of
+lease updates to be sent. The name of the partner is specified with the third
+argument.
-EVAL_DEBUG_VENDOR_EXISTS
-========================
+HA_LEASES_BACKLOG_SUCCESS
+=========================
.. code-block:: text
- %1: Option with enterprise-id %2 found, pushing result '%3'
-
-Logged at debug log level 55.
-This debug message indicates that the expression has been evaluated and vendor
-option was found.
+ %1: sending lease updates backlog to %2 successful in %3
-****
-FLEX
-****
+This informational message is issued when server successfully completes
+sending lease updates backlog to the partner. The first argument specifies the
+local server's name. The second argument specifies the name of the remote server.
+The third argument specifies the duration of
+this operation.
-FLEX_ID_EXPRESSION_EMPTY
-========================
+HA_LEASES_SYNC_APPLIED_LEASES
+=============================
.. code-block:: text
- Specified identifier-expression is empty
+ %1: applied %2 leases received from the partner in the local lease database
-This warning message is printed when the flex-id library is being loaded,
-but the expression used to generate the identifier is empty. The library
-will load, but will not generate any identifiers. Please make sure that
-the identifier-expression parameter is specified.
+This informational message outputs the number of leases received from the
+partner during the database synchronization and applied in the local database.
+A typical case when only some leases are applied is when the server has
+multiple relationships and some of the received leases belong to another
+relationship. The first argument specifies this server name. The second
+argument specifies the number of applied leases.
-FLEX_ID_EXPRESSION_EVALUATED
-============================
+HA_LEASES_SYNC_COMMUNICATIONS_FAILED
+====================================
.. code-block:: text
- Expression evaluated for packet to "%1" (size: %2)
+ %1: failed to communicate with %2 while syncing leases: %3
-Logged at debug log level 40.
-This debug message is printed every time a packet evaluation is successful.
-This means that the identifier expression has been generated. Note that
-depending on the expression and content of the incoming packet, the
-expression may be evaluated to an empty string.
+This error message is issued to indicate that there was a communication error
+with a partner server while trying to fetch leases from its lease database.
+The argument contains a reason for the error.
-FLEX_ID_EXPRESSION_EVALUATED_NP
-===============================
+HA_LEASES_SYNC_FAILED
+=====================
.. code-block:: text
- Expression evaluated for packet to 0x%1 (size: %2)
+ %1: failed to synchronize leases with %2: %3
-This debug message is printed every time a packet evaluation is successful.
-This means that the identifier expression has been generated. As it is
-not printable it is converted to hexadecimal.
+This error message is issued to indicate that there was a problem while
+parsing a response from the server from which leases have been fetched for
+local database synchronization. The third argument contains a reason for
+the error.
-FLEX_ID_EXPRESSION_HEX
-======================
+HA_LEASES_SYNC_LEASE_PAGE_RECEIVED
+==================================
.. code-block:: text
- evaluated expression in hexadecimal form "%1"
+ %1: received %2 leases from %3
-Logged at debug log level 40.
-This debug message provides a hexadecimal representation of the evaluated
-expression. This is useful for debugging purposes because further logs use
-hexadecimal format for logging.
+This informational message is issued during lease database synchronization
+to indicate that a bulk of leases have been received. The first argument
+specifies the local server's name. The second argument holds the count of
+leases received. The third argument specifies the partner server name.
-FLEX_ID_EXPRESSION_INVALID_JSON_TYPE
-====================================
+HA_LEASE_SYNC_FAILED
+====================
.. code-block:: text
- The identifier-expression is %1, but expected JSON string
+ %1: synchronization failed for lease: %2, reason: %3
-This error message is printed when the flex-id library is being loaded,
-but the expression used to generate the identifier is malformed. It has
-a different JSON type (e.g. is a map) rather than expected string.
+This warning message is issued when creating or updating a lease in the
+local lease database fails. The lease information in the JSON format is
+provided as a first argument. The third argument provides a reason for
+the failure.
-FLEX_ID_EXPRESSION_NOT_DEFINED
-==============================
+HA_LEASE_SYNC_STALE_LEASE4_SKIP
+===============================
.. code-block:: text
- Expression (identifier-expression) is not defined.
+ %1: skipping stale lease %2 in subnet %3
-This warning message is printed when the flex-id library is loaded, but the
-expression used to generate the identifier is not specified. The library
-will load, but will not generate any identifiers. Please make sure that
-the identifier-expression parameter is specified for your library.
+Logged at debug log level 40.
+This debug message is issued during lease database synchronization, when
+fetched IPv4 lease instance appears to be older than the instance in the
+local database. The newer instance is left in the database and the fetched
+lease is dropped. The remote server will still hold the older lease instance
+until it synchronizes its database with this server. The first argument
+specifies the local server's name. The second argument specifies leased
+address. The third argument specifies a subnet to which the lease belongs.
-FLEX_ID_EXPRESSION_PARSE_FAILED
+HA_LEASE_SYNC_STALE_LEASE6_SKIP
===============================
.. code-block:: text
- The identifier-expression is [%1], but fails to parse with error: %2
+ %1: skipping stale lease %2 in subnet %3
-This error message is printed when the flex-id library is being loaded,
-but the expression used to generate the identifier is malformed. It failed
-to parse.
+Logged at debug log level 40.
+This debug message is issued during lease database synchronization, when
+fetched IPv6 lease instance appears to be older than the instance in the
+local database. The newer instance is left in the database and the fetched
+lease is dropped. The remote server will still hold the older lease instance
+until it synchronizes its database with this server. The first argument
+specifies the local server's name. The second argument specifies leased
+address. The second argument specifies a subnet to which the lease belongs.
-FLEX_ID_IGNORE_IAID_APPLIED_ON_NA
-=================================
+HA_LEASE_UPDATES_DISABLED
+=========================
.. code-block:: text
- the ignore-iaid has changed IAID (%1) to 0 for the IA_NA option.
+ %1: lease updates will not be sent to the partner while in %2 state
-Logged at debug log level 40.
-This DEBUG message is printed when the flex-id library did apply the ignore-iaid
-flag and changed IAID to 0 because the received packet contains exactly one
-IA_NA.
+This informational message is issued to indicate that lease updates will
+not be sent to the partner while the server is in the current state. The
+second argument specifies the server's current state name. The lease updates
+are still sent to the backup servers if they are configured but any
+possible errors in communication with the backup servers are ignored.
-FLEX_ID_IGNORE_IAID_APPLIED_ON_PD
-=================================
+HA_LEASE_UPDATES_ENABLED
+========================
.. code-block:: text
- the ignore-iaid has changed IAID (%1) to 0 for the IA_PD option.
+ %1: lease updates will be sent to the partner while in %2 state
-Logged at debug log level 40.
-This DEBUG message is printed when the flex-id library did apply the ignore-iaid
-flag and changed IAID to 0 because the received packet contains exactly one
-IA_PD.
+This informational message is issued to indicate that lease updates will
+be sent to the partner while the server is in the current state. The
+second specifies the server's current state name.
-FLEX_ID_IGNORE_IAID_ENABLED
-===========================
+HA_LEASE_UPDATE_COMMUNICATIONS_FAILED
+=====================================
.. code-block:: text
- the ignore-iaid is set. It only has an effect on clients with at most one IA_NA and one IA_PD.
+ %1: failed to send lease update %2 to %3: %4
-This WARNING message is printed when the flex-id library is being loaded,
-and the ignore-iaid parameter is set. This flag will enable the server to drop
-packets which contain more than one IA_NA and one IA_PD.
+This warning message indicates that there was a problem in communication with a
+HA peer while processing a DHCP client query and sending lease update. The
+client's DHCP message will be dropped.
-FLEX_ID_IGNORE_IAID_JSON_TYPE
-=============================
+HA_LEASE_UPDATE_CONFLICT
+========================
.. code-block:: text
- the ignore-iaid is %1 but expected boolean value
+ %1: lease update %2 sent to %3 returned conflict status code: %4
-This error message is printed when the flex-id library is being loaded,
-but the ignore-iaid parameter is malformed, i.e. it has a different
-type than expected. It is expected to be a boolean value.
+This warning message indicates that the partner returned a conflict status code
+in response to a lease update. The client's DHCP message will be dropped.
+If the server is configured to track conflicting lease updates, it may
+eventually transition to the terminated state when the configured threshold
+is exceeded.
-FLEX_ID_IGNORE_IAID_NOT_APPLIED_ON_NA
-=====================================
+HA_LEASE_UPDATE_CREATE_UPDATE_FAILED_ON_PEER
+============================================
.. code-block:: text
- the ignore-iaid was not applied on the packet because it contains more than one IA_NA.
+ %1: failed to create or update the lease having type %2 for address %3, reason: %4
-Logged at debug log level 40.
-This WARNING message is printed when the flex-id library did not apply the
-ignore-iaid flag because the received packet contains more than one IA_NA.
+This informational message is issued when one of the leases failed to be
+created or updated on the HA peer while processing the lease updates sent
+from this server. This may indicate an issue with communication between
+the peer and its lease database.
-FLEX_ID_IGNORE_IAID_NOT_APPLIED_ON_PD
+HA_LEASE_UPDATE_DELETE_FAILED_ON_PEER
=====================================
.. code-block:: text
- the ignore-iaid was not applied on the packet because it contains more than one IA_PD.
+ %1: failed to delete the lease having type %2 for address %3, reason: %4
-Logged at debug log level 40.
-This WARNING message is printed when the flex-id library did not apply the
-ignore-iaid flag because the received packet contains more than one IA_PD.
+This informational message is issued when one of the leases failed to delete
+on the HA peer while processing lease updates sent from this server. Typically,
+the lease fails to delete when it doesn't exist in the peer's database.
-FLEX_ID_LOAD_ERROR
-==================
+HA_LEASE_UPDATE_FAILED
+======================
.. code-block:: text
- An error occurred loading the library %1
+ %1: lease update %2 sent to %3 failed: %4
-This error message will be printed when an error is encountered during
-loading of the library. Details of the problem are printed as parameter
-to this message.
+This warning message indicates that a peer returned an error status code
+in response to a lease update. The client's DHCP message will be dropped.
-FLEX_ID_REPLACE_CLIENT_ID_JSON_TYPE
-===================================
+HA_LEASE_UPDATE_REJECTS_CAUSED_TERMINATION
+==========================================
.. code-block:: text
- the replace-client-id is %1 but expected boolean value
+ %1: too many rejected lease updates cause the HA service to terminate
-This error message is printed when the flex-id library is being loaded,
-but the replace-client-id parameter is malformed, i.e. it has a different
-type than expected. It is expected to be a boolean value.
+This error message is issued when the HA service terminates because the
+number of lease updates for which a conflict status code was returned
+by the partner exceeds the limit set with max-rejected-lease-updates
+configuration parameter.
-FLEX_ID_RESTORE_CLIENT_ID
-=========================
+HA_LOAD_BALANCING_DUID_MISSING
+==============================
.. code-block:: text
- restoring original client identifier '%1' in the response
+ %1: load balancing failed for the DHCPv6 message (transaction id: %2) because DUID is missing
Logged at debug log level 40.
-This debug message is issued when the original (client supplied) client identifier
-is restored into the server's response.
+This debug message is issued when the HA hook library was unable to load
+balance an incoming DHCPv6 query because neither client identifier nor
+HW address was included in the query. The query will be dropped. The
+sole argument contains transaction id.
-FLEX_ID_RESTORE_DUID
-====================
+HA_LOAD_BALANCING_IDENTIFIER_MISSING
+====================================
.. code-block:: text
- restoring original DUID "%1" in the response
+ %1: load balancing failed for the DHCPv4 message (transaction id: %2) because HW address and client identifier are missing
Logged at debug log level 40.
-This debug message is issued when the original (client supplied) client identifier
-is restored into the server"s response.
+This debug message is issued when the HA hook library was unable to load
+balance an incoming DHCPv4 query because neither client identifier nor
+HW address was included in the query. The query will be dropped. The
+sole argument contains transaction id.
-FLEX_ID_UNLOAD
-==============
+HA_LOCAL_DHCP_DISABLE
+=====================
.. code-block:: text
- Flex-id library has been unloaded.
+ local DHCP service is disabled while the %1 is in the %2 state
-This informational message signifies that the flexible-identifier library has been
-unloaded.
+This informational message is issued to indicate that the local DHCP service
+is disabled because the server remains in a state in which the server
+should not respond to DHCP clients, e.g. the server hasn't synchronized
+its lease database. The first argument specifies server name. The second
+argument specifies server's state.
-FLEX_ID_USED_AS_CLIENT_ID
-=========================
+HA_LOCAL_DHCP_ENABLE
+====================
.. code-block:: text
- using flexible identifier "%1" as client identifier
+ local DHCP service is enabled while the %1 is in the %2 state
-Logged at debug log level 40.
-This debug message is issued to indicate that the library is removing client
-supplied client identifier from the received message and is inserting flexible
-identifier based client identifier instead. The server will use this new client
-identifier for processing the packet. The original client identifier will be
-restored in the pkt4_send callout and sent back to the client.
+This informational message is issued to indicate that the local DHCP service
+is enabled because the server remains in a state in which it should
+respond to the DHCP clients. The first argument specifies server name.
+The second argument specifies server's state.
-FLEX_OPTION_LOAD_ERROR
-======================
+HA_MAINTENANCE_CANCEL_HANDLER_FAILED
+====================================
.. code-block:: text
- loading Flex Option hooks library failed: %1
+ ha-maintenance-cancel command failed: %1
-This error message indicates an error during loading the Flex Option
-hooks library. The details of the error are provided as argument of
-the log message.
+This error message is issued to indicate that the ha-maintenance-cancel command
+handler failed while processing the command. The argument provides the reason for
+failure.
-FLEX_OPTION_PROCESS_ADD
-=======================
+HA_MAINTENANCE_NOTIFY_CANCEL_COMMUNICATIONS_FAILED
+==================================================
.. code-block:: text
- Added the option code %1 with value %2
+ %1: failed to send ha-maintenance-notify to %2 in attempt to cancel its maintenance: %3
-Logged at debug log level 40.
-This debug message is printed when an option was added into the response
-packet. The option code and the value (between quotes if printable, in
-hexadecimal if not) are provided.
+This warning message indicates that there was a problem in communication with a
+HA peer while sending the ha-maintenance-notify command with the cancel flag
+set to true. The first argument provides the local server's name. The second
+argument provides the remote server's name. The third argument provides a reason
+for failure.
-FLEX_OPTION_PROCESS_CLIENT_CLASS
-================================
+HA_MAINTENANCE_NOTIFY_CANCEL_FAILED
+===================================
.. code-block:: text
- Skip processing of the option code %1 for class '%2'
+ %1: error returned while processing ha-maintenance-notify by %2 in attempt to cancel its maintenance: %3
-Logged at debug log level 40.
-This debug message is printed when the processing for an option is skipped
-because the query does not belongs to the client class. The option code and
-the client class name are provided.
+This warning message indicates that a peer returned an error status code
+in response to a ha-maintenance-notify command with the cancel flag set to
+true. The first argument provides the local server's name. The second argument
+provides the remote server's name. The third argument provides a reason for
+failure.
-FLEX_OPTION_PROCESS_ERROR
-=========================
+HA_MAINTENANCE_NOTIFY_COMMUNICATIONS_FAILED
+===========================================
.. code-block:: text
- An error occurred processing query %1: %2
+ %1: failed to send ha-maintenance-notify to %2: %3
-This error message indicates an error during processing of a query
-by the Flex Option hooks library. The client identification information
-from the query and the details of the error are provided as arguments
-of the log message.
+This warning message indicates that there was a problem in communication with a
+HA peer while sending the ha-maintenance-notify command. The first argument provides
+the local server's name. The second argument provides the remote server's name.
+The third argument provides a reason for failure.
-FLEX_OPTION_PROCESS_REMOVE
-==========================
+HA_MAINTENANCE_NOTIFY_FAILED
+============================
.. code-block:: text
- Removed option code %1
+ %1: error returned while processing ha-maintenance-notify by %2: %3
-Logged at debug log level 40.
-This debug message is printed when an option was removed from the response
-packet. The option code is provided.
+This warning message indicates that a peer returned an error status code
+in response to a ha-maintenance-notify command. The first argument provides the
+remote server's name. The second argument provides a reason for failure.
-FLEX_OPTION_PROCESS_SUB_ADD
-===========================
+HA_MAINTENANCE_NOTIFY_HANDLER_FAILED
+====================================
.. code-block:: text
- Added the sub-option code %1 in option code %2 with value %3
+ ha-maintenance-notify command failed: %1
-Logged at debug log level 40.
-This debug message is printed when an sub-option was added into the response
-packet. The sub-option and container option codes, and the value
-(between quotes if printable, in hexadecimal if not) are provided.
+This error message is issued to indicate that the ha-maintenance-notify command
+handler failed while processing the command. The argument provides the reason for
+failure.
-FLEX_OPTION_PROCESS_SUB_CLIENT_CLASS
-====================================
+HA_MAINTENANCE_SHUTDOWN_SAFE
+============================
.. code-block:: text
- Skip processing of the sub-option code %1 in option code %2 for class '%3'
+ %1: the server can now be shutdown for maintenance as the partner has taken over the DHCP traffic
-Logged at debug log level 40.
-This debug message is printed when the processing for a sub-option is skipped
-because the query does not belongs to the client class. The sub-option and
-container option codes, and the client class name are provided.
+This informational message is displayed after the server transitions to the
+in-maintenance state. This server no longer responds to any DHCP queries and its
+partner - in partner-in-maintenance state - has taken over the DHCP traffic.
+When the server in-maintenance state is shut down, the partner moves to
+the partner-down state immediately.
-FLEX_OPTION_PROCESS_SUB_REMOVE
-==============================
+HA_MAINTENANCE_STARTED
+======================
.. code-block:: text
- Removed sub-option code %1 in option code %2
+ %1: the server is now in the partner-in-maintenance state and the partner is in-maintenance state
-Logged at debug log level 40.
-This debug message is printed when a sub-option was removed from the response
-packet. The sub-option and container option codes are provided.
+This informational message is displayed when the server receiving the
+ha-maintenance-start command transitions to the partner-in-maintenance
+state. The server does it after sending the ha-maintenance-notify to
+its partner to put the partner in the in-maintenance state. From now on,
+the server in the partner-in-maintenance state will be responding to all
+queries and the partner will respond to no queries. The partner may be
+safely shut down for maintenance in which case this server will
+automatically transition from the partner-in-maintenance state to the
+partner-down state.
-FLEX_OPTION_PROCESS_SUB_SUPERSEDE
-=================================
+HA_MAINTENANCE_STARTED_IN_PARTNER_DOWN
+======================================
.. code-block:: text
- Supersedes the sub-option code %1 in option code %2 with value %3
+ %1: the server is now in the partner-down mode as a result of requested maintenance
-Logged at debug log level 40.
-This debug message is printed when a sub-option was superseded into the
-response packet. The sub-option and container option codes, and the value
-(between quotes if printable, in hexadecimal if not) are provided.
+This informational message is displayed when the server receiving the
+ha-maintenance-start command transitions to the partner-down state
+because it was unable to communicate with the partner while receiving
+the command. It is assumed that in such situation the partner is
+already offline for the maintenance. Note that in this case the
+normal failover procedure does not take place. The server does not wait
+for a heartbeat to fail several times, nor it monitors the DHCP traffic
+for not responded queries. In the maintenance case the server transitions
+to the partner-down state when it first encounters a communication
+problem with the partner.
-FLEX_OPTION_PROCESS_SUPERSEDE
-=============================
+HA_MAINTENANCE_START_HANDLER_FAILED
+===================================
.. code-block:: text
- Supersedes the option code %1 with value %2
+ ha-maintenance-start command failed: %1
-Logged at debug log level 40.
-This debug message is printed when an option was superseded into the response
-packet. The option code and the value (between quotes if printable, in
-hexadecimal if not) are provided.
+This error message is issued to indicate that the ha-maintenance-start command
+handler failed while processing the command. The argument provides the reason for
+failure.
-FLEX_OPTION_PROCESS_VENDOR_ID_MISMATCH
-======================================
+HA_MISSING_CONFIGURATION
+========================
.. code-block:: text
- Skip processing of vendor option code %1 with vendor id %2 not matching wanted %3
-
-Logged at debug log level 40.
-This debug message is printed when a sub-option of a vendor option is
-processed but vendor ids do not match. The code of the vendor option
-and the two vendor ids are provided.
+ high-availability parameter not specified for High Availability hooks library
-****
-FUZZ
-****
+This error message is issued to indicate that the configuration for the
+High Availability hooks library hasn't been specified. The 'high-availability'
+parameter must be specified for the hooks library to load properly.
-FUZZ_DATA_READ
-==============
+HA_PAUSE_CLIENT_LISTENER_FAILED
+===============================
.. code-block:: text
- read %1 byte(s) from AFL via stdin
+ %1: pausing multi-threaded HTTP processing failed: %2
-Logged at debug log level 50.
-A debug message output to indicate how much data has been received from
-the fuzzer via stdin
+This error message is emitted when attempting to pause HA's HTTP client and
+listener threads. This error is highly unlikely and indicates a programmatic
+issue that should be reported as a defect.
-FUZZ_INIT_COMPLETE
-==================
+HA_PAUSE_CLIENT_LISTENER_ILLEGAL
+================================
.. code-block:: text
- fuzz initialization complete: interface %1, address %2, port %3, max loops %4
+ %1: pausing multi-threaded HTTP processing failed: %2
-An informational message output when the fuzzing initialization function has
-completed successfully. The parameters listed are those which must be/can be
-set via environment variables.
+This error message is emitted when attempting to pause HA's HTTP client or
+listener thread pools from a worker thread. This error indicates that a command
+run on the listener threads is trying to use a critical section which would
+result in a dead-lock.
-FUZZ_INIT_FAIL
-==============
+HA_RESET_COMMUNICATIONS_FAILED
+==============================
.. code-block:: text
- fuzz initialization failure, reason: %1
+ %1: failed to send ha-reset command to %2: %3
-An error message reported if the fuzzing initialization failed. The reason
-for the failure is given in the message.
+This warning message indicates a problem with communication with a HA peer
+while sending the ha-reset command. The first argument specifies the local
+server name. The second argument specifies a remote server name. The third
+argument specifies a reason for failure.
-FUZZ_READ_FAIL
-==============
+HA_RESET_FAILED
+===============
.. code-block:: text
- error reading input from fuzzer: %1
+ %1: failed to reset HA state machine of %2: %3
-This error is reported if the read of data from the fuzzer (which is
-received over stdin) fails, or if a read returns zero bytes. If this
-occurs, the thread will sleep for a short period before retrying the read.
-The message includes the reason for the failure.
+This warning message indicates that a peer returned an error status code
+in response to the ha-reset command. The first argument specifies a local
+server name. The second argument specifies a remote server name. The third
+argument specifies a reason for failure.
-FUZZ_SEND
-=========
+HA_RESET_HANDLER_FAILED
+=======================
.. code-block:: text
- sent %1 byte(s) to the socket connected to the Kea interface
+ ha-reset command failed: %1
-Logged at debug log level 50.
-A debug message stating that the sendto() call in the main fuzzing function
-has successfully completed and reporting the number of bytes sent. This
-call sends data received from AFL to the port on which Kea is listening.
+This error message is issued to indicate that the ha-reset command handler
+failed while processing the command. The argument provides the reason for
+failure.
-FUZZ_SEND_ERROR
-===============
+HA_RESUME_CLIENT_LISTENER_FAILED
+================================
.. code-block:: text
- failed to send data to Kea input socket: %1
+ %1: resuming multi-threaded HTTP processing failed: %2
-This error will be reported if the sendto() call in the fuzzing thread (which
-sends data received from AFL to the socket on which Kea is listening) fails.
-The reason for the failure is given in the message. The fuzzing code will
-attempt to continue from this, but it may cause the fuzzing process to fail.
+This error message is emitted when attempting to resume HA's HTTP client and
+listener threads. This error is highly unlikely and indicates a programmatic
+issue that should be reported as a defect.
-FUZZ_SHORT_SEND
-===============
+HA_SCOPES_HANDLER_FAILED
+========================
.. code-block:: text
- expected to send %1 bytes to Kea input socket but only sent %2
-
-A warning message that is output if the sendto() call (used to send data
-from the fuzzing thread to the main Kea processing) did not send as much
-data as that read from AFL. This may indicate a problem in the underlying
-communications between the fuzzing thread and the main Kea processing.
+ ha-scopes command failed: %1
-***
-GSS
-***
+This error message is issued to indicate that the ha-scopes command handler
+failed while processing the command. The argument provides reason for
+the failure.
-GSS_TSIG_COMMAND_PROCESSED_FAILED
-=================================
+HA_SERVICE_STARTED
+==================
.. code-block:: text
- command_processed callout failed: %1.
+ %1: started high availability service in %2 mode as %3 server
-This error message is issued when the callout for the command_processed
-callout point failed. The argument contains a reason for the error.
+This informational message is issued when the HA service is started as a result
+of server startup or reconfiguration. The first argument specifies a local server
+name. The second argument provides the HA mode. The third argument specifies the
+role of this server instance in this configuration.
-GSS_TSIG_LOAD_FAILED
-====================
+HA_STATE_MACHINE_CONTINUED
+==========================
.. code-block:: text
- GSS-TSIG hooks library failed to load: %1.
+ %1: state machine is un-paused
-This error message indicates that an error occurred attempting to
-load the GSS-TSIG hooks library. The argument details the error.
+This informational message is issued when the HA state machine is un-paused.
+This unlocks the server from the current state. It may transition to any
+other state if it needs to do so, e.g. 'partner-down' if its partner appears
+to be offline. The server may also remain in the current state if the HA
+setup state warrants such behavior.
-GSS_TSIG_LOAD_OK
-================
+HA_STATE_MACHINE_PAUSED
+=======================
.. code-block:: text
- GSS-TSIG hooks library loaded successfully.
+ %1: state machine paused in state %2
-This info message indicates that the GSS-TSIG hooks library has
-been loaded successfully.
+This informational message is issued when the HA state machine is paused.
+HA state machine may be paused in certain states specified in the HA hooks library
+configuration. When the state machine is paused, the server remains in the given
+state until it is explicitly unpaused (via the ha-continue command). If the state
+machine is paused, the server operates normally but cannot transition to any
+other state.
-GSS_TSIG_MANAGER_STARTED
-========================
+HA_STATE_TRANSITION
+===================
.. code-block:: text
- hooks library GSS-TSIG key periodic manager started.
+ %1: server transitions from %2 to %3 state, partner state is %4
-Logged at debug log level 40.
-This debug message is issued when the GSS-TSIG key periodic manager has started.
+This informational message is issued when the server transitions to a new
+state as a result of some interaction (or lack of thereof) with its partner.
+The arguments specify local server name, initial server state, new server state
+and the partner's state.
-GSS_TSIG_MANAGER_STOPPED
-========================
+HA_STATE_TRANSITION_PASSIVE_BACKUP
+==================================
.. code-block:: text
- hooks library GSS-TSIG key periodic manager stopped.
+ %1: server transitions from %2 to %3 state
-Logged at debug log level 40.
-This debug message is issued when the GSS-TSIG key periodic manager has stopped.
+This informational message is issued when the server in passive-backup
+mode transitions to a new state. The arguments specify local server name, initial
+server state and a new server state.
-GSS_TSIG_MANAGER_STOP_ERROR
-===========================
+HA_SUBNET4_SELECT_FAILED
+========================
.. code-block:: text
- manager stop error: %1
+ subnet4_select callout failed: %1
-This error message is issued when the GSS-TSIG key periodic manager has stopped
-but an error is detected. The error message in the argument gives details about
-the problem.
+This error message is issued when the callout for the subnet4_select hook
+point failed. This may occur as a result of an internal server error.
+The argument contains a reason for the error.
-GSS_TSIG_MANAGER_STOP_GENERAL_ERROR
-===================================
+HA_SUBNET4_SELECT_INVALID_HA_SERVER_NAME
+========================================
.. code-block:: text
- manager stop general error
+ %1: invalid ha-server-name value for subnet %2
-This error message is issued when the GSS-TSIG key periodic manager has stopped
-but a general error is detected.
+This error message is issued when the received DHCPv4 query is dropped
+by this server because the specified ha-server-name value in the subnet's
+user-context has non-string type or is empty. It is a server's misconifguration.
+The first argument is the client identification information. The second argument
+is a subnet prefix.
-GSS_TSIG_NEW_KEY
-================
+HA_SUBNET4_SELECT_NOT_FOR_US
+============================
.. code-block:: text
- new GSS-TSIG key '%1' was created.
+ %1: dropping query in relationship %2 to be processed by another server
Logged at debug log level 40.
-This info message indicates that the GSS-TSIG hooks library has
-created a new GSS-TSIG key. The name of the new key is displayed.
+This debug message is issued when the received DHCPv4 query is dropped
+by this server because it should be served by another server. This
+is the case when a remote primary server is operational. The first argument
+is the client identification information. The second argument is the
+relationship name.
-GSS_TSIG_NEW_KEY_SETUP_FAILED
-=============================
+HA_SUBNET4_SELECT_NO_RELATIONSHIP_FOR_SUBNET
+============================================
.. code-block:: text
- new GSS-TSIG key '%1' setup failed: %2.
+ %1: HA relationship not found for %2
-This warning message is issued when the setup of a new GSS-TSIG key failed.
-The name of the new key and the error are displayed.
+This error message is issued when the received DHCPv4 query is dropped
+by this server because the server could not find a relationship matching
+the specified ha-server-name for a subnet. The server name matches no
+relationship specified in the HA configuration. A typical reason for it
+is a typo. The first argument is the client identification information.
+The second argument is the relationship name.
-GSS_TSIG_NEW_KEY_SETUP_SUCCEED
-==============================
+HA_SUBNET4_SELECT_NO_RELATIONSHIP_SELECTOR_FOR_SUBNET
+=====================================================
.. code-block:: text
- new GSS-TSIG key '%1' setup succeed.
+ %1: unable to determine HA relationship because selected subnet %2 lacks the ha-server-name
-Logged at debug log level 40.
-This debug message is issued when the setup of a new GSS-TSIG key
-successfully finished. The name of the new key is displayed.
+This error message is issued when the received DHCPv4 query is dropped
+by this server because it was unable to determine the HA relationship to
+which the received query belongs. If there are multiple relationships,
+it is required to specify ha-server-name value in the user-context at the subnet
+or shared network level for each subnet and/or shared network. The server
+uses them as a relationship selector. If these selectors are unspecified
+for any of the subnets it is a configuration error. The first argument is
+the client identification information. The second argument is a subnet
+prefix.
-GSS_TSIG_OLD_KEY_REMOVED
-========================
+HA_SUBNET4_SELECT_NO_SUBNET_SELECTED
+====================================
.. code-block:: text
- %1 old GSS-TSIG keys were removed
+ %1: unable to determine HA relationship because no subnet has been selected for the client
Logged at debug log level 40.
-This debug message is issued when some old keys (older than 2 times the maximum
-TKEY lifetime) were removed. The number of removed keys is displayed.
+This debug message is issued when the received DHCPv4 query is dropped
+by this server because it could not select a subnet for this client.
+Selecting the subnet is required to find a suitable HA relationship.
+This message is not emitted when the server has only one relationship.
+The argument is the client identification information.
-GSS_TSIG_UNLOAD_OK
-==================
+HA_SUBNET6_SELECT_FAILED
+========================
.. code-block:: text
- GSS-TSIG hooks library unloaded successfully.
+ subnet6_select callout failed: %1
-This info message indicates that the GSS-TSIG hooks library has
-been unloaded successfully.
+This error message is issued when the callout for the subnet6_select hook
+point failed. This may occur as a result of an internal server error.
+The argument contains a reason for the error.
-GSS_TSIG_VERIFIED
-=================
+HA_SUBNET6_SELECT_INVALID_HA_SERVER_NAME
+========================================
.. code-block:: text
- GSS-TSIG verify successed.
+ %1: invalid ha-server-name value for subnet %2
-Logged at debug log level 40.
-A debug message issued when GSS-TSIG verification succeeded.
+This error message is issued when the received DHCPv6 query is dropped
+by this server because the specified ha-server-name value in the subnet's
+user-context has non-string type or is empty. It is a server's misconifguration.
+The first argument is the client identification information. The second argument
+is a subnet prefix.
-GSS_TSIG_VERIFY_FAILED
-======================
+HA_SUBNET6_SELECT_NOT_FOR_US
+============================
.. code-block:: text
- GSS-TSIG verify failed: %1.
-
-This info message indicates that GSS-TSIG verification failed.
-The argument details the error.
+ %1: dropping query in relationship %2 to be processed by another server
-**
-HA
-**
+Logged at debug log level 40.
+This debug message is issued when the received DHCPv6 query is dropped
+by this server because it should be served by another server. This
+is the case when a remote primary server is operational. The first argument
+is the client identification information. The second argument is the
+relationship name.
-HA_BUFFER4_RECEIVE_FAILED
-=========================
+HA_SUBNET6_SELECT_NO_RELATIONSHIP_FOR_SUBNET
+============================================
.. code-block:: text
- buffer4_receive callout failed: %1
+ %1: HA relationship not found for %2
-This error message is issued when the callout for the buffer4_receive hook
-point failed. This may occur as a result of an internal server error.
-The argument contains a reason for the error.
+This error message is issued when the received DHCPv6 query is dropped
+by this server because the server could not find a relationship matching
+the specified ha-server-name for a subnet. The server name matches no
+relationship specified in the HA configuration. A typical reason for it
+is a typo. The first argument is the client identification information.
+The second argument is the relationship name.
-HA_BUFFER4_RECEIVE_NOT_FOR_US
-=============================
+HA_SUBNET6_SELECT_NO_RELATIONSHIP_SELECTOR_FOR_SUBNET
+=====================================================
.. code-block:: text
- %1: dropping query to be processed by another server
+ %1: unable to determine HA relationship because selected subnet %2 lacks the ha-server-name
-Logged at debug log level 40.
-This debug message is issued when the received DHCPv4 query is dropped
-by this server because it should be served by another server. This
-is the case when the remote server was designated to process the packet
-as a result of load balancing or because it is a primary server in the
-hot standby configuration. The argument provides client identification
-information retrieved from the query.
+This error message is issued when the received DHCPv6 query is dropped
+by this server because it was unable to determine the HA relationship to
+which the received query belongs. If there are multiple relationships,
+it is required to specify ha-server-name value in the user-context at the subnet
+or shared network level for each subnet and/or shared network. The server
+uses them as a relationship selector. If these selectors are unspecified
+for any of the subnets it is a configuration error. The first argument is
+the client identification information. The second argument is a subnet
+prefix.
-HA_BUFFER4_RECEIVE_PACKET_OPTIONS_SKIPPED
-=========================================
+HA_SUBNET6_SELECT_NO_SUBNET_SELECTED
+====================================
.. code-block:: text
- an error unpacking an option, caused subsequent options to be skipped: %1
+ %1: unable to determine HA relationship because no subnet has been selected for the client
Logged at debug log level 40.
-A debug message issued when an option failed to unpack correctly, making it
-impossible to unpack the remaining options in the DHCPv4 query. The server
-will still attempt to service the packet. The sole argument provides a
-reason for unpacking error.
+This debug message is issued when the received DHCPv6 query is dropped
+by this server because it could not select a subnet for this client.
+Selecting the subnet is required to find a suitable HA relationship.
+This message is not emitted when the server has only one relationship.
+The argument is the client identification information.
-HA_BUFFER4_RECEIVE_UNPACK_FAILED
-================================
+HA_SYNC_COMPLETE_NOTIFY_COMMUNICATIONS_FAILED
+=============================================
.. code-block:: text
- failed to parse query from %1 to %2, received over interface %3, reason: %4
+ %1: failed to send ha-sync-complete-notify to %2: %3
-Logged at debug log level 40.
-This debug message is issued when received DHCPv4 query is malformed and
-can't be parsed by the buffer4_receive callout. The query will be
-dropped by the server. The first three arguments specify source IP address,
-destination IP address and the interface. The last argument provides a
-reason for failure.
+This warning message indicates that there was a problem in communication with an
+HA peer while sending the ha-sync-complete-notify command. The first argument
+provides a local server's name. The second argument provides the remote server's
+name. The third argument provides a reason for failure.
-HA_BUFFER6_RECEIVE_FAILED
-=========================
+HA_SYNC_COMPLETE_NOTIFY_FAILED
+==============================
.. code-block:: text
- buffer6_receive callout failed: %1
+ %1: error processing ha-sync-complete-notify command on %2: %3
-This error message is issued when the callout for the buffer6_receive hook
-point failed. This may occur as a result of an internal server error.
-The argument contains a reason for the error.
+This warning message indicates that a peer returned an error status code
+in response to the ha-sync-complete-notify command. The first argument provides
+a local server's name. The second argument provides the remote server's name. The
+third argument provides a reason for failure.
-HA_BUFFER6_RECEIVE_NOT_FOR_US
-=============================
+HA_SYNC_COMPLETE_NOTIFY_HANDLER_FAILED
+======================================
.. code-block:: text
- %1: dropping query to be processed by another server
+ ha-sync-complete-notify command failed: %1
-Logged at debug log level 40.
-This debug message is issued when the received DHCPv6 query is dropped
-by this server because it should be served by another server. This
-is the case when the remote server was designated to process the packet
-as a result of load balancing or because it is a primary server in the
-hot standby configuration. The argument provides client identification
-information retrieved from the query.
+This error message is issued to indicate that the ha-sync-complete-notify command
+handler failed while processing the command. The argument provides the reason for
+failure.
-HA_BUFFER6_RECEIVE_PACKET_OPTIONS_SKIPPED
-=========================================
+HA_SYNC_FAILED
+==============
.. code-block:: text
- an error unpacking an option, caused subsequent options to be skipped: %1
+ %1: lease database synchronization with %2 failed: %3
-Logged at debug log level 40.
-A debug message issued when an option failed to unpack correctly, making it
-impossible to unpack the remaining options in the DHCPv6 query. The server
-will still attempt to service the packet. The sole argument provides a
-reason for unpacking error.
+This error message is issued to indicate that the lease database synchronization
+failed. The first argument provides the local server's name. The second argument
+provides the partner server's name. The third argument provides a reason for the
+failure.
-HA_BUFFER6_RECEIVE_UNPACK_FAILED
-================================
+HA_SYNC_HANDLER_FAILED
+======================
.. code-block:: text
- failed to parse query from %1 to %2, received over interface %3, reason: %4
+ ha-sync command failed: %1
-Logged at debug log level 40.
-This debug message is issued when received DHCPv6 query is malformed and
-can't be parsed by the buffer6_receive callout. The query will be
-dropped by the server. The first three arguments specify source IP address,
-destination IP address and the interface. The last argument provides a
-reason for failure.
+This error message is issued to indicate that the ha-sync command handler
+failed while processing the command. The argument provides the reason for
+failure.
-HA_COMMAND_PROCESSED_FAILED
-===========================
+HA_SYNC_START
+=============
.. code-block:: text
- command_processed callout failed: %1
+ %1: starting lease database synchronization with %2
-This error message is issued when the callout for the command_processed hook
-point failed. The argument contains a reason for the error.
+This informational message is issued when the server starts lease database
+synchronization with a partner. The arguments specify the local and remote
+server names.
-HA_COMMUNICATION_INTERRUPTED
-============================
+HA_SYNC_SUCCESSFUL
+==================
.. code-block:: text
- %1: communication with %2 is interrupted
+ %1: lease database synchronization with %2 completed successfully in %3
-This warning message is issued by the server which discovered that the
-communication to the active partner has been interrupted for a time
-period longer than the configured heartbeat-delay time. At this stage
-the server starts the failover procedure by monitoring the DHCP traffic
-sent to the partner and checking whether the partner server responds to
-this traffic. If the max-unacked-clients value is set to 0 such
-verification is disabled in which case the server will transition to
-the partner-down state.
+This informational message is issued when the server successfully completed
+lease database synchronization with the partner. The first argument specifies
+local server name. The second argument specifies the name of the partner server.
+The third argument specifies the duration of the synchronization.
-HA_COMMUNICATION_INTERRUPTED_CLIENT4
-====================================
+HA_TERMINATED
+=============
.. code-block:: text
- %1: new client %2 attempting to get a lease from the partner
+ HA %1: service terminated due to an unrecoverable condition. Check previous error message(s), address the problem and restart!
-This informational message is issued when the surviving server observes
-a DHCP packet sent to the partner with which the communication is interrupted.
-The client whose packet is observed is not yet considered "unacked" because
-the secs field value does not exceed the configured threshold specified
-with max-ack-delay.
+This error message is issued to indicate that the HA service has been stopped
+due to an unacceptable condition (e.g. too large of a clock skew). The exact
+cause should appear in a previous error message. Address the condition
+reported then restart the servers to resume service.
-HA_COMMUNICATION_INTERRUPTED_CLIENT4_UNACKED
-============================================
+HA_TERMINATED_PARTNER_DID_NOT_RESTART
+=====================================
.. code-block:: text
- %1: partner server failed to respond to %2, %3 clients unacked so far, %4 clients left before transitioning to the partner-down state
+ %1: service is terminating because the terminated partner was not restarted within %2 minutes
-This informational message is issued when the surviving server determines
-that its partner failed to respond to the DHCP query and that this client
-is considered to not be served by the partner. The surviving server counts
-such clients and if the number of such clients exceeds the max-unacked-clients
-threshold, the server will transition to the partner-down state. The first
-argument specifies the relationship name. The second argument contains client
-identification information. The third argument specifies the number of
-clients to which the server has failed to respond. The forth argument specifies
-the number of additional clients which, if not provisioned, will cause the
-server to transition to the partner-down state.
+This warning message is issued to indicate that the HA service is terminating
+because partner server is in the terminated state and was not restarted within
+an expected time frame. The terminated servers should be restarted after correcting
+the problem that caused the termination. They can be restarted sequentially but the
+duration between the restarts should not be too long. If it is long it may mean that
+the restart of one of the servers was unintentional (e.g., power outage). If the
+restarted server remains in the waiting state it cannot serve DHCP clients. Moving
+to the terminated state at least allows for responding to the DHCP traffic.
-HA_COMMUNICATION_INTERRUPTED_CLIENT6
-====================================
+*****
+HOOKS
+*****
+
+HOOKS_ALL_CALLOUTS_DEREGISTERED
+===============================
.. code-block:: text
- %1: new client %2 attempting to get a lease from the partner
+ hook library at index %1 removed all callouts on hook %2
-This informational message is issued when the surviving server observes
-a DHCP packet sent to the partner with which the communication is interrupted.
-The client whose packet is observed is not yet considered "unacked" because
-the elapsed time option value does not exceed the configured threshold
-specified with max-ack-delay. The sole argument specifies client
-identification information.
+Logged at debug log level 55.
+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.
-HA_COMMUNICATION_INTERRUPTED_CLIENT6_UNACKED
-============================================
+HOOKS_CALLOUTS_BEGIN
+====================
.. code-block:: text
- %1: partner server failed to respond to %2, %3 clients unacked so far, %4 clients left before transitioning to the partner-down state
+ begin all callouts for hook %1
-This informational message is issued when the surviving server determines
-that its partner failed to respond to the DHCP query and that this client
-is considered to not be served by the partner. The surviving server counts
-such clients and if the number of such clients exceeds the max-unacked-clients
-threshold, the server will transition to the partner-down state. The first
-argument specifies the relationship name. The second argument contains client
-identification information. The third argument specifies the number of clients
-to which the server has failed to respond. The forth argument specifies the
-number of additional clients which, if not provisioned, will cause the server
-to transition to the partner-down state.
+Logged at debug log level 45.
+This debug message is issued when callout manager begins to invoke callouts
+for the hook. The argument specifies the hook name.
-HA_CONFIGURATION_FAILED
+HOOKS_CALLOUTS_COMPLETE
=======================
.. code-block:: text
- failed to configure High Availability hooks library: %1
+ completed callouts for hook %1 (total callouts duration: %2)
-This error message is issued when there is an error configuring the HA hooks
-library. The argument provides the detailed error message.
+Logged at debug log level 45.
+This debug message is issued when callout manager has completed execution
+of all callouts for the particular hook. The arguments specify the hook
+name and total execution time for all callouts in milliseconds.
-HA_CONFIGURATION_SUCCESSFUL
-===========================
+HOOKS_CALLOUTS_REMOVED
+======================
.. code-block:: text
- HA hook library has been successfully configured
+ callouts removed from hook %1 for library %2
-This informational message is issued when the HA hook library configuration
-parser successfully parses and validates the new configuration.
+Logged at debug log level 45.
+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.
-HA_CONFIG_AUTO_FAILOVER_DISABLED
-================================
+HOOKS_CALLOUT_CALLED
+====================
.. code-block:: text
- %1: auto-failover disabled
+ hooks library with index %1 has called a callout on hook %2 that has address %3 (callout duration: %4)
-This warning message is issued to indicate that the 'auto-failover' parameter
-was administratively disabled for the specified server. The server will not
-automatically start serving partner's scope when the partner failure is detected.
-The server administrator will need to enable this scope manually by
-sending appropriate ha-scopes command.
+Logged at debug log level 55.
+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.
+The message includes the callout execution time in milliseconds.
-HA_CONFIG_DHCP_MT_DISABLED
+HOOKS_CALLOUT_DEREGISTERED
==========================
.. code-block:: text
- %1: HA multi-threading has been disabled, it cannot be enabled when Kea global multi-threading is disabled
-
-This informational message is issued when HA configuration has enabled
-multi-threading while Kea global configuration has multi-threading disabled.
-
-HA_CONFIG_DHCP_MT_DISABLED_AND_KEA_MT_ENABLED
-=============================================
-
-.. code-block:: text
-
- %1: HA multi-threading is disabled while Kea global multi-threading is enabled which most likely cause performance degradation.
+ hook library at index %1 deregistered a callout on hook %2
-This warning message is issued when HA configuration has disabled
-multi-threading while Kea global configuration has multi-threading enabled.
-This will likely cause performance degradation.
+Logged at debug log level 55.
+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.
-HA_CONFIG_LEASE_SYNCING_DISABLED
-================================
+HOOKS_CALLOUT_ERROR
+===================
.. code-block:: text
- %1: lease database synchronization between HA servers is disabled
+ error returned by callout on hook %1 registered by library with index %2 (callout address %3) (callout duration %4)
-This warning message is issued when the lease database synchronization is
-administratively disabled. This is valid configuration if the leases are
-replicated between lease databases via some other mechanism, e.g. SQL
-database replication.
+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.
+The error message includes the callout execution time in milliseconds.
-HA_CONFIG_LEASE_SYNCING_DISABLED_REMINDER
-=========================================
+HOOKS_CALLOUT_EXCEPTION
+=======================
.. code-block:: text
- %1: bypassing SYNCING state because lease database synchronization is administratively disabled
+ exception thrown by callout on hook %1 registered by library with index %2 (callout address %3): %4 (callout duration: %5)
-This informational message is issued as a reminder that lease database
-synchronization is administratively disabled and therefore the server
-transitions directly from the "waiting" to "ready" state.
+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.
+The error message includes the callout execution time in milliseconds.
-HA_CONFIG_LEASE_UPDATES_AND_SYNCING_DIFFER
-==========================================
+HOOKS_CALLOUT_REGISTRATION
+==========================
.. code-block:: text
- %1: unusual configuration where "send-lease-updates": %2 and "sync-leases": %3
+ hooks library with index %1 registering callout for hook '%2'
-This warning message is issued when the configuration values of the
-send-lease-updates and sync-leases parameters differ. This may be a
-valid configuration but is unusual. Normally, if the lease database
-with replication is in use, both values are set to false. If a lease
-database without replication is in use (e.g. memfile), both values
-are set to true. Providing different values for those parameters means
-that an administrator either wants the server to not synchronize
-leases upon startup but later send lease updates to the partner, or
-the lease database should be synchronized upon startup, but no lease
-updates are later sent as a result of leases allocation.
+Logged at debug log level 45.
+This is a debug message, output when a library (whose index in the list
+of libraries (being) loaded is given) registers a callout.
-HA_CONFIG_LEASE_UPDATES_DISABLED
-================================
+HOOKS_CLOSE_ERROR
+=================
.. code-block:: text
- %1: lease updates will not be generated
+ failed to close hook library %1: %2
-This warning message is issued when the lease updates are administratively
-disabled. This is valid configuration if the leases are replicated to the
-partner's database via some other mechanism, e.g. SQL database replication.
+Kea 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 Kea.
-HA_CONFIG_LEASE_UPDATES_DISABLED_REMINDER
-=========================================
+HOOKS_HOOK_LIST_RESET
+=====================
.. code-block:: text
- %1: lease updates are administratively disabled and will not be generated while in %2 state
+ the list of hooks has been reset
-This informational message is issued as a reminder that the lease updates
-are administratively disabled and will not be issued in the HA state to
-which the server has transitioned. The sole argument specifies the state
-into which the server has transitioned.
+This is a message indicating that the list of hooks has been reset.
+While this is usual when running the Kea test suite, it should not be
+seen when running Kea in a production environment. If this appears,
+please report a bug through the usual channels.
-HA_CONFIG_SYSTEM_MT_UNSUPPORTED
-===============================
+HOOKS_INCORRECT_VERSION
+=======================
.. code-block:: text
- %1: HA multi-threading has been disabled, auto-detection of thread support reports 0
-
-This informational message is issued when HA multi-threading configuration has
-specified auto-detection for the number of threads to use and the system
-reports the number of concurrent threads as 0. If you know your system can
-support multiple threads, then you may override this condition by specifying
-explicit values for http-listener-threads and http-client-threads.
-
-HA_CONTINUE_HANDLER_FAILED
-==========================
+ hook library %1 is at version %2, require version %3
+
+Kea has detected that the named hook library has been built against
+a version of Kea that is incompatible with the version of Kea
+running on your system. It has not loaded the library.
+This is most likely due to the installation of a new version of Kea
+without rebuilding the hook library. A rebuild and re-install of the
+library should fix the problem in most cases.
+
+HOOKS_LIBRARY_CLOSED
+====================
.. code-block:: text
- ha-continue command failed: %1
+ hooks library %1 successfully closed
-This error message is issued to indicate that the ha-continue command handler
-failed while processing the command. The argument provides the reason for
-failure.
+This information message is issued when a user-supplied hooks library
+has been successfully closed.
-HA_DEINIT_OK
-============
+HOOKS_LIBRARY_LOADED
+====================
.. code-block:: text
- unloading High Availability hooks library successful
+ hooks library %1 successfully loaded
-This informational message indicates that the High Availability hooks library
-has been unloaded successfully.
+This information message is issued when a user-supplied hooks library
+has been successfully loaded.
-HA_DHCP4_START_SERVICE_FAILED
-=============================
+HOOKS_LIBRARY_LOADING
+=====================
.. code-block:: text
- failed to start DHCPv4 HA services in dhcp4_srv_configured callout: %1
+ loading hooks library %1
-This error message is issued when an attempt to start High Availability services
-for the DHCPv4 server failed in the dhcp4_srv_configured callout. This
-is internal server error and a bug report should be created.
+Logged at debug log level 40.
+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.
-HA_DHCP6_START_SERVICE_FAILED
-=============================
+HOOKS_LIBRARY_MULTI_THREADING_COMPATIBLE
+========================================
.. code-block:: text
- failed to start DHCPv6 HA services in dhcp6_srv_configured callout: %1
+ hooks library %1 reports its multi-threading compatibility as %2
-This error message is issued when an attempt to start High Availability services
-for the DHCPv6 server failed in the dhcp6_srv_configured callout. This
-is internal server error and a bug report should be created.
+Logged at debug log level 45.
+A debug message issued when the "multi_threading_compatible" function was
+called. The returned value (0 means not compatible, others compatible)
+is displayed.
-HA_DHCP_DISABLE_COMMUNICATIONS_FAILED
-=====================================
+HOOKS_LIBRARY_MULTI_THREADING_NOT_COMPATIBLE
+============================================
.. code-block:: text
- %1: failed to send request to disable DHCP service of %2: %3
+ hooks library %1 is not compatible with multi-threading
-This warning message indicates that there was a problem in communication with a
-HA peer while sending the dhcp-disable command. The first argument specifies
-the local server's name. The second argument provides the remote server's name.
-The third argument provides a reason for failure.
+When multi-threading is enabled and the library is not compatible (either
+because the "multi_threading_compatible" function returned 0 or was not
+implemented) this error message is issued. The library must be removed
+from the configuration or the multi-threading disabled.
-HA_DHCP_DISABLE_FAILED
+HOOKS_LIBRARY_UNLOADED
======================
.. code-block:: text
- %1: failed to disable DHCP service of %2: %3
+ hooks library %1 successfully unloaded
-This warning message indicates that a peer returned an error status code
-in response to a dhcp-disable command. The first argument provides the
-local server's name. The second argument provides the remote server's name.
-The third argument provides a reason for failure.
+This information message is issued when a user-supplied hooks library
+has been successfully unloaded.
-HA_DHCP_ENABLE_COMMUNICATIONS_FAILED
-====================================
+HOOKS_LIBRARY_UNLOADING
+=======================
.. code-block:: text
- %1: failed to send request to enable DHCP service of %2: %3
+ unloading library %1
-This warning message indicates that there was a problem in communication with a
-HA peer while sending the dhcp-enable command. The first argument provides the
-local server's name. The second argument provides the remote server's name. The
-third argument provides a reason for failure.
+Logged at debug log level 40.
+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.
-HA_DHCP_ENABLE_FAILED
+HOOKS_LIBRARY_VERSION
=====================
.. code-block:: text
- %1: failed to enable DHCP service of %2: %3
+ hooks library %1 reports its version as %2
-This warning message indicates that a peer returned an error status code
-in response to a dhcp-enable command. The first argument provides the
-local server's name. The second argument provides the remote server's name.
-The third argument provides a reason for failure.
+Logged at debug log level 45.
+A debug message issued when the version check on the hooks library
+has succeeded.
-HA_HEARTBEAT_COMMUNICATIONS_FAILED
-==================================
+HOOKS_LOAD_ERROR
+================
.. code-block:: text
- %1: failed to send heartbeat to %2: %3
+ 'load' function in hook library %1 returned error %2
-This warning message indicates that there was a problem in communication with a
-HA peer while sending a heartbeat. This is a first sign that the peer may be
-down. The server will keep trying to send heartbeats until it considers that
-communication is interrupted.
+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.
-HA_HEARTBEAT_FAILED
-===================
+HOOKS_LOAD_EXCEPTION
+====================
.. code-block:: text
- %1: heartbeat to %2 failed: %3
+ 'load' function in hook library %1 threw an exception
-This warning message indicates that a peer returned an error status code
-in response to a heartbeat. This is the sign that the peer may not function
-properly. The server will keep trying to send heartbeats until it considers
-that communication is interrupted.
+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.
-HA_HEARTBEAT_HANDLER_FAILED
-===========================
+HOOKS_LOAD_FRAMEWORK_EXCEPTION
+==============================
.. code-block:: text
- heartbeat command failed: %1
+ 'load' function in hook library %1 threw an exception: reason %2
-This error message is issued to indicate that the heartbeat command handler
-failed while processing the command. The argument provides the reason for
-failure.
+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.
-HA_HIGH_CLOCK_SKEW
+HOOKS_LOAD_SUCCESS
==================
.. code-block:: text
- %1: %2, please synchronize clocks!
+ 'load' function in hook library %1 returned success
-This warning message is issued when the clock skew between the active servers
-exceeds 30 seconds. The HA service continues to operate but may not function
-properly, especially for low lease lifetimes. The administrator should
-should synchronize the clocks, e.g. using NTP. If the clock skew exceeds
-60 seconds, the HA service will terminate.
+Logged at debug log level 40.
+This is a debug message issued when the "load" function has been found
+in a hook library and has been successfully called.
-HA_HIGH_CLOCK_SKEW_CAUSED_TERMINATION
-=====================================
+HOOKS_MULTI_THREADING_COMPATIBLE_EXCEPTION
+==========================================
.. code-block:: text
- %1: %2, causing HA service to terminate
+ 'multi_threading_compatible' function in hook library %1 threw an exception
-This warning message is issued when the clock skew between the active servers
-exceeds 60 seconds. The HA service stops. The servers will continue to respond
-to the DHCP queries but won't exchange lease updates or send heartbeats.
-The administrator is required to synchronize the clocks and then restart the
-servers to resume the HA service.
+This error message is issued if the multi_threading_compatible()
+function in the specified hooks library was called and generated an
+exception. The library is considered unusable and will not be loaded.
-HA_INIT_OK
-==========
+HOOKS_NO_LOAD
+=============
.. code-block:: text
- loading High Availability hooks library successful
+ no 'load' function found in hook library %1
-This informational message indicates that the High Availability hooks library
-has been loaded successfully. Enjoy!
+Logged at debug log level 40.
+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.
-HA_INVALID_PARTNER_STATE_COMMUNICATION_RECOVERY
-===============================================
+HOOKS_NO_UNLOAD
+===============
.. code-block:: text
- %1: partner is in the communication-recovery state unexpectedly
+ no 'unload' function found in hook library %1
-This warning message is issued when a partner is in the communication-recovery
-state, and this server is not running in the load balancing mode. The server
-may only transition to the communication-recovery state when it runs in the
-load balancing mode. The HA mode of both servers must be the same.
+Logged at debug log level 40.
+This is a debug message issued when the library is being unloaded.
+It merely states that the library did not contain an "unload" function.
-HA_INVALID_PARTNER_STATE_HOT_STANDBY
-====================================
+HOOKS_NO_VERSION
+================
.. code-block:: text
- %1: partner is in the hot-standby state unexpectedly
+ no 'version' function found in hook library %1
-This warning message is issued when a partner is in the hot-standby state,
-and this server is not running in the hot standby mode. The server may only
-transition to the hot-standby state when it runs in the hot standby mode.
-The HA mode of both servers must be the same.
+The shared library named in the message was found and successfully loaded,
+but Kea did not find a function named "version" in it. This function
+is required and should return the version of Kea against which the
+library was built. The value is used to check that the library was built
+against a compatible version of Kea. The library has not been loaded.
-HA_INVALID_PARTNER_STATE_LOAD_BALANCING
-=======================================
+HOOKS_OPEN_ERROR
+================
.. code-block:: text
- %1: partner is in the load-balancing state unexpectedly
+ failed to open hook library %1: %2
-This warning message is issued when a partner is in the load-balancing state,
-and this server is not running in the load balancing mode. The server may only
-transition to the load-balancing state when it runs in the load balancing mode.
-The HA mode of both servers must be the same.
+Kea failed to open the specified hook library for the stated
+reason. The library has not been loaded. Kea will continue to
+function, but without the services offered by the library.
-HA_LEASE4_SERVER_DECLINE_FAILED
-===============================
+HOOKS_STD_CALLOUT_REGISTERED
+============================
.. code-block:: text
- lease4_server_decline callout failed: %1
+ hooks library %1 registered standard callout for hook %2 at address %3
-This error message is issued when the callout for the lease4_server_decline hook
-point failed. This includes unexpected errors like wrong arguments provided to
-the callout by the DHCP server (unlikely internal server error).
-The argument contains a reason for the error.
+Logged at debug log level 45.
+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.
-HA_LEASES4_COMMITTED_FAILED
-===========================
+HOOKS_UNLOAD_ERROR
+==================
.. code-block:: text
- leases4_committed callout failed: %1
+ 'unload' function in hook library %1 returned error %2
-This error message is issued when the callout for the leases4_committed hook
-point failed. This includes unexpected errors like wrong arguments provided to
-the callout by the DHCP server (unlikely internal server error).
-The argument contains a reason for the error.
+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.
-HA_LEASES4_COMMITTED_NOTHING_TO_UPDATE
-======================================
+HOOKS_UNLOAD_EXCEPTION
+======================
.. code-block:: text
- %1: leases4_committed callout was invoked without any leases
+ 'unload' function in hook library %1 threw an exception
-Logged at debug log level 40.
-This debug message is issued when the "leases4_committed" callout returns
-because there are neither new leases nor deleted leases for which updates
-should be sent. The sole argument specifies the details of the client
-which sent the packet.
+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.
-HA_LEASES4_COMMITTED_NO_RELATIONSHIP
-====================================
+HOOKS_UNLOAD_FRAMEWORK_EXCEPTION
+================================
.. code-block:: text
- %1: HA relationship not found: %2
+ 'unload' function in hook library %1 threw an exception, reason %2
-This error message is issued when the relationship for the server name provided
-by the earlier callouts was not found in the HA configuration. This error is
-highly unlikely and rather indicates some programming error. The first argument
-is the client identification information. The second argument holds a more
-detailed error message.
+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.
-HA_LEASES6_COMMITTED_FAILED
-===========================
+HOOKS_UNLOAD_SUCCESS
+====================
.. code-block:: text
- leases6_committed callout failed: %1
+ 'unload' function in hook library %1 returned success
-This error message is issued when the callout for the leases6_committed hook
-point failed. This includes unexpected errors like wrong arguments provided to
-the callout by the DHCP server (unlikely internal server error).
-The argument contains a reason for the error.
+Logged at debug log level 40.
+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.
-HA_LEASES6_COMMITTED_NOTHING_TO_UPDATE
-======================================
+*****
+HOSTS
+*****
+
+HOSTS_BACKENDS_REGISTERED
+=========================
.. code-block:: text
- %1: leases6_committed callout was invoked without any leases
+ the following host backend types are available: %1
-Logged at debug log level 40.
-This debug message is issued when the "leases6_committed" callout returns
-because there are neither new leases nor deleted leases for which updates
-should be sent. The sole argument specifies the details of the client
-which sent the packet.
+This informational message lists all possible host backends that could
+be used in hosts-database[s].
-HA_LEASES6_COMMITTED_NO_RELATIONSHIP
-====================================
+HOSTS_BACKEND_DEREGISTER
+========================
.. code-block:: text
- %1: HA relationship not found: %2
+ deregistered host backend type: %1
-This error message is issued when the relationship for the server name provided
-by the earlier callouts was not found in the HA configuration. This error is
-highly unlikely and rather indicates some programming error. The first argument
-is the client identification information. The second argument holds a more
-detailed error message.
+Logged at debug log level 40.
+This debug message is issued when a backend factory was deregistered.
+It is no longer possible to use host backend of this type.
-HA_LEASES_BACKLOG_COMMUNICATIONS_FAILED
-=======================================
+HOSTS_BACKEND_REGISTER
+======================
.. code-block:: text
- %1: failed to communicate with %2 while sending lease updates backlog: %3
+ registered host backend type: %1
-This error message is issued to indicate that there was a communication error
-with a partner server while sending outstanding lease updates after resuming
-connection. The third argument contains a reason for the error.
+Logged at debug log level 40.
+This debug message is issued when a backend factory was successfully
+registered. It is now possible to use host backend of this type.
-HA_LEASES_BACKLOG_FAILED
-========================
+HOSTS_CFG_ADD_HOST
+==================
.. code-block:: text
- %1: failed to send lease updates backlog to %2: %3
+ add the host for reservations: %1
-This error message is issued to indicate that sending lease updates backlog
-to a partner server failed. The lease updates backlog is sent to the partner
-after resuming temporarily broken communication with the partner. If this
-operation fails the server will transition to the waiting state to initiate
-full lease database synchronization.
+Logged at debug log level 40.
+This debug message is issued when new host (with reservations) is added to
+the server's configuration. The argument describes the host and its
+reservations in detail.
-HA_LEASES_BACKLOG_NOTHING_TO_SEND
-=================================
+HOSTS_CFG_CACHE_HOST_DATA_SOURCE
+================================
.. code-block:: text
- %1: no leases in backlog after communication recovery
+ get host cache data source: %1
-This informational message is issued when there are no outstanding leases to
-be sent after communication recovery with a partner. This means that the
-communication interruption was short enough that no DHCP clients obtained
-any leases from the server while it was in the communication-recovery state.
-The server may now transition to the load-balancing state.
+This informational message is issued when a host cache data source is
+detected by the host manager.
-HA_LEASES_BACKLOG_START
-=======================
+HOSTS_CFG_CLOSE_HOST_DATA_SOURCE
+================================
.. code-block:: text
- %1: starting to send %2 outstanding lease updates to %3
+ Closing host data source: %1
-This informational message is issued when the server starts to send outstanding
-lease updates to the partner after resuming communications. The first argument
-specifies the local server's name. The second argument specifies the number of
-lease updates to be sent. The name of the partner is specified with the third
-argument.
+Logged at debug log level 40.
+This is a normal message being printed when the server closes host data
+source connection.
-HA_LEASES_BACKLOG_SUCCESS
-=========================
+HOSTS_CFG_DEL
+=============
.. code-block:: text
- %1: sending lease updates backlog to %2 successful in %3
+ deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and address %4
-This informational message is issued when server successfully completes
-sending lease updates backlog to the partner. The first argument specifies the
-local server's name. The second argument specifies the name of the remote server.
-The third argument specifies the duration of
-this operation.
+Logged at debug log level 40.
+This debug message is issued when reservations are deleted for the specified
+subnet and address. The first argument specifies how many hosts have been
+deleted. The second argument specifies how many reservations have been deleted.
+The third argument is the subnet identifier. The fourth argument is the IP
+address.
-HA_LEASES_SYNC_APPLIED_LEASES
-=============================
+HOSTS_CFG_DEL4
+==============
.. code-block:: text
- %1: applied %2 leases received from the partner in the local lease database
+ deleted %1 host(s) for subnet id %2 and identifier %3
-This informational message outputs the number of leases received from the
-partner during the database synchronization and applied in the local database.
-A typical case when only some leases are applied is when the server has
-multiple relationships and some of the received leases belong to another
-relationship. The first argument specifies this server name. The second
-argument specifies the number of applied leases.
+Logged at debug log level 40.
+This debug message is issued when IPv4 reservations are deleted for the specified
+subnet and identifier. The first argument specifies how many hosts have been
+deleted. The second argument is the subnet identifier. The third argument is
+the identifier.
-HA_LEASES_SYNC_COMMUNICATIONS_FAILED
-====================================
+HOSTS_CFG_DEL6
+==============
.. code-block:: text
- %1: failed to communicate with %2 while syncing leases: %3
+ deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
-This error message is issued to indicate that there was a communication error
-with a partner server while trying to fetch leases from its lease database.
-The argument contains a reason for the error.
+Logged at debug log level 40.
+This debug message is issued when IPv6 reservations are deleted for the
+specified subnet and identifier. The first argument specifies how many hosts
+have been deleted. The second argument specifies how many reservations have
+been deleted. The third argument is the subnet identifier. The fourth argument
+is the identifier.
-HA_LEASES_SYNC_FAILED
-=====================
+HOSTS_CFG_DEL_ALL_SUBNET4
+=========================
.. code-block:: text
- %1: failed to synchronize leases with %2: %3
+ deleted all %1 host(s) for subnet id %2
-This error message is issued to indicate that there was a problem while
-parsing a response from the server from which leases have been fetched for
-local database synchronization. The third argument contains a reason for
-the error.
+Logged at debug log level 40.
+This debug message is issued when all IPv4 reservations are deleted for
+the specified subnet. The first argument specifies how many reservations
+have been deleted. The second argument is the subnet identifier.
-HA_LEASES_SYNC_LEASE_PAGE_RECEIVED
-==================================
+HOSTS_CFG_DEL_ALL_SUBNET6
+=========================
.. code-block:: text
- %1: received %2 leases from %3
+ deleted all %1 host(s) having %2 IPv6 reservation(s) for subnet id %3
-This informational message is issued during lease database synchronization
-to indicate that a bulk of leases have been received. The first argument
-specifies the local server's name. The second argument holds the count of
-leases received. The third argument specifies the partner server name.
+Logged at debug log level 40.
+This debug message is issued when all IPv6 reservations are deleted for
+the specified subnet. The first argument specifies how many hosts
+have been deleted. The second argument specifies how many IPv6
+(addresses and prefixes) reservations have been deleted. The third argument is
+the subnet identifier.
-HA_LEASE_SYNC_FAILED
-====================
+HOSTS_CFG_GET_ALL
+=================
.. code-block:: text
- %1: synchronization failed for lease: %2, reason: %3
+ get all hosts with reservations
-This warning message is issued when creating or updating a lease in the
-local lease database fails. The lease information in the JSON format is
-provided as a first argument. The third argument provides a reason for
-the failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts.
-HA_LEASE_SYNC_STALE_LEASE4_SKIP
-===============================
+HOSTS_CFG_GET_ALL_ADDRESS4
+==========================
.. code-block:: text
- %1: skipping stale lease %2 in subnet %3
+ get all hosts with reservations for IPv4 address %1
Logged at debug log level 40.
-This debug message is issued during lease database synchronization, when
-fetched IPv4 lease instance appears to be older than the instance in the
-local database. The newer instance is left in the database and the fetched
-lease is dropped. The remote server will still hold the older lease instance
-until it synchronizes its database with this server. The first argument
-specifies the local server's name. The second argument specifies leased
-address. The third argument specifies a subnet to which the lease belongs.
+This debug message is issued when starting to retrieve all hosts, holding the
+reservation for the specific IPv4 address, from the configuration. The
+argument specifies the IPv4 address used to search the hosts.
-HA_LEASE_SYNC_STALE_LEASE6_SKIP
-===============================
+HOSTS_CFG_GET_ALL_ADDRESS4_COUNT
+================================
.. code-block:: text
- %1: skipping stale lease %2 in subnet %3
+ using address %1, found %2 host(s)
-Logged at debug log level 40.
-This debug message is issued during lease database synchronization, when
-fetched IPv6 lease instance appears to be older than the instance in the
-local database. The newer instance is left in the database and the fetched
-lease is dropped. The remote server will still hold the older lease instance
-until it synchronizes its database with this server. The first argument
-specifies the local server's name. The second argument specifies leased
-address. The second argument specifies a subnet to which the lease belongs.
+Logged at debug log level 45.
+This debug message logs the number of hosts found using the specified
+IPv4 address. The arguments specify the IPv4 address used and the number
+of hosts found respectively.
-HA_LEASE_UPDATES_DISABLED
-=========================
+HOSTS_CFG_GET_ALL_ADDRESS4_HOST
+===============================
.. code-block:: text
- %1: lease updates will not be sent to the partner while in %2 state
+ using address %1 found host: %2
-This informational message is issued to indicate that lease updates will
-not be sent to the partner while the server is in the current state. The
-second argument specifies the server's current state name. The lease updates
-are still sent to the backup servers if they are configured but any
-possible errors in communication with the backup servers are ignored.
+Logged at debug log level 55.
+This debug message is issued when found host with the reservation
+for the specified IPv4 address. The arguments specify the IPv4 address
+and the detailed description of the host found.
-HA_LEASE_UPDATES_ENABLED
-========================
+HOSTS_CFG_GET_ALL_ADDRESS6
+==========================
.. code-block:: text
- %1: lease updates will be sent to the partner while in %2 state
+ get all hosts with reservations for IPv6 address %1
-This informational message is issued to indicate that lease updates will
-be sent to the partner while the server is in the current state. The
-second specifies the server's current state name.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts, holding the
+reservation for the specific IPv6 address, from the configuration.
+The argument specifies the IPv6 address used to search the hosts.
-HA_LEASE_UPDATE_COMMUNICATIONS_FAILED
-=====================================
+HOSTS_CFG_GET_ALL_ADDRESS6_COUNT
+================================
.. code-block:: text
- %1: failed to send lease update %2 to %3: %4
+ using address %1, found %2 host(s)
-This warning message indicates that there was a problem in communication with a
-HA peer while processing a DHCP client query and sending lease update. The
-client's DHCP message will be dropped.
+Logged at debug log level 45.
+This debug message logs the number of hosts found using the specified
+IPv6 address. The arguments specify the IPv6 address used and the number
+of hosts found respectively.
-HA_LEASE_UPDATE_CONFLICT
-========================
+HOSTS_CFG_GET_ALL_ADDRESS6_HOST
+===============================
.. code-block:: text
- %1: lease update %2 sent to %3 returned conflict status code: %4
+ using address %1 found host: %2
-This warning message indicates that the partner returned a conflict status code
-in response to a lease update. The client's DHCP message will be dropped.
-If the server is configured to track conflicting lease updates, it may
-eventually transition to the terminated state when the configured threshold
-is exceeded.
+Logged at debug log level 55.
+This debug message is issued when found host with the reservation
+for the specified IPv6 address. The arguments specify the IPv6 address
+and the detailed description of the host found.
-HA_LEASE_UPDATE_CREATE_UPDATE_FAILED_ON_PEER
-============================================
+HOSTS_CFG_GET_ALL_COUNT
+=======================
.. code-block:: text
- %1: failed to create or update the lease having type %2 for address %3, reason: %4
+ found %1 host(s)
-This informational message is issued when one of the leases failed to be
-created or updated on the HA peer while processing the lease updates sent
-from this server. This may indicate an issue with communication between
-the peer and its lease database.
+Logged at debug log level 45.
+This debug message include the details of the host found. The argument
+specifies the number of hosts found.
-HA_LEASE_UPDATE_DELETE_FAILED_ON_PEER
-=====================================
+HOSTS_CFG_GET_ALL_HOST
+======================
.. code-block:: text
- %1: failed to delete the lease having type %2 for address %3, reason: %4
+ found host: %1
-This informational message is issued when one of the leases failed to delete
-on the HA peer while processing lease updates sent from this server. Typically,
-the lease fails to delete when it doesn't exist in the peer's database.
+Logged at debug log level 55.
+This debug message includes the details of the host found. The argument
+specifies found host details.
-HA_LEASE_UPDATE_FAILED
-======================
+HOSTS_CFG_GET_ALL_HOSTNAME
+==========================
.. code-block:: text
- %1: lease update %2 sent to %3 failed: %4
+ get all hosts with reservations for hostname %1
-This warning message indicates that a peer returned an error status code
-in response to a lease update. The client's DHCP message will be dropped.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts with
+the specific hostname. The argument specifies hostname.
-HA_LEASE_UPDATE_REJECTS_CAUSED_TERMINATION
-==========================================
+HOSTS_CFG_GET_ALL_HOSTNAME_COUNT
+================================
.. code-block:: text
- %1: too many rejected lease updates cause the HA service to terminate
+ using hostname %1, found %2 host(s)
-This error message is issued when the HA service terminates because the
-number of lease updates for which a conflict status code was returned
-by the partner exceeds the limit set with max-rejected-lease-updates
-configuration parameter.
+Logged at debug log level 45.
+This debug message include the details of the host found using the
+hostname. The arguments specify hostname and the number of hosts found
+respectively.
-HA_LOAD_BALANCING_DUID_MISSING
-==============================
+HOSTS_CFG_GET_ALL_HOSTNAME_HOST
+===============================
.. code-block:: text
- %1: load balancing failed for the DHCPv6 message (transaction id: %2) because DUID is missing
+ using hostname %1, found host: %2
-Logged at debug log level 40.
-This debug message is issued when the HA hook library was unable to load
-balance an incoming DHCPv6 query because neither client identifier nor
-HW address was included in the query. The query will be dropped. The
-sole argument contains transaction id.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the hostname.
+The arguments specify hostname and found host details respectively.
-HA_LOAD_BALANCING_IDENTIFIER_MISSING
-====================================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4
+=====================================
.. code-block:: text
- %1: load balancing failed for the DHCPv4 message (transaction id: %2) because HW address and client identifier are missing
+ get all hosts with reservations for hostname %1 and IPv4 subnet %2
Logged at debug log level 40.
-This debug message is issued when the HA hook library was unable to load
-balance an incoming DHCPv4 query because neither client identifier nor
-HW address was included in the query. The query will be dropped. The
-sole argument contains transaction id.
+This debug message is issued when starting to retrieve all hosts with
+the specific hostname connected to the specific DHCPv4 subnet. The argument
+specifies hostname and subnet id.
-HA_LOCAL_DHCP_DISABLE
-=====================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_COUNT
+===========================================
.. code-block:: text
- local DHCP service is disabled while the %1 is in the %2 state
+ using hostname %1 and IPv4 subnet %2, found %3 host(s)
-This informational message is issued to indicate that the local DHCP service
-is disabled because the server remains in a state in which the server
-should not respond to DHCP clients, e.g. the server hasn't synchronized
-its lease database. The first argument specifies server name. The second
-argument specifies server's state.
+Logged at debug log level 45.
+This debug message include the details of the host found using the
+hostname and the DHCPv4 subnet id. The arguments specify hostname,
+subnet id and the number of hosts found respectively.
-HA_LOCAL_DHCP_ENABLE
-====================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_HOST
+==========================================
.. code-block:: text
- local DHCP service is enabled while the %1 is in the %2 state
+ using hostname %1 and IPv4 subnet %2, found host: %3
-This informational message is issued to indicate that the local DHCP service
-is enabled because the server remains in a state in which it should
-respond to the DHCP clients. The first argument specifies server name.
-The second argument specifies server's state.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the
+hostname and the DHCPv4 subnet id. The arguments specify hostname,
+subnet id and found host details respectively.
-HA_MAINTENANCE_CANCEL_HANDLER_FAILED
-====================================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6
+=====================================
.. code-block:: text
- ha-maintenance-cancel command failed: %1
+ get all hosts with reservations for hostname %1 and IPv6 subnet %2
-This error message is issued to indicate that the ha-maintenance-cancel command
-handler failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts with
+the specific hostname connected to the specific DHCPv6 subnet. The argument
+specifies hostname and subnet id.
-HA_MAINTENANCE_NOTIFY_CANCEL_COMMUNICATIONS_FAILED
-==================================================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_COUNT
+===========================================
.. code-block:: text
- %1: failed to send ha-maintenance-notify to %2 in attempt to cancel its maintenance: %3
+ using hostname %1 and IPv6 subnet %2, found %3 host(s)
-This warning message indicates that there was a problem in communication with a
-HA peer while sending the ha-maintenance-notify command with the cancel flag
-set to true. The first argument provides the local server's name. The second
-argument provides the remote server's name. The third argument provides a reason
-for failure.
+Logged at debug log level 45.
+This debug message include the details of the host found using the
+hostname and the DHCPv6 subnet id. The arguments specify hostname,
+subnet id and the number of hosts found respectively.
-HA_MAINTENANCE_NOTIFY_CANCEL_FAILED
-===================================
+HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_HOST
+==========================================
.. code-block:: text
- %1: error returned while processing ha-maintenance-notify by %2 in attempt to cancel its maintenance: %3
+ using hostname %1 and IPv6 subnet %2, found host: %3
-This warning message indicates that a peer returned an error status code
-in response to a ha-maintenance-notify command with the cancel flag set to
-true. The first argument provides the local server's name. The second argument
-provides the remote server's name. The third argument provides a reason for
-failure.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the
+hostname and the DHCPv6 subnet id. The arguments specify hostname,
+subnet id and found host details respectively.
-HA_MAINTENANCE_NOTIFY_COMMUNICATIONS_FAILED
-===========================================
+HOSTS_CFG_GET_ALL_IDENTIFIER
+============================
.. code-block:: text
- %1: failed to send ha-maintenance-notify to %2: %3
+ get all hosts with reservations using identifier: %1
-This warning message indicates that there was a problem in communication with a
-HA peer while sending the ha-maintenance-notify command. The first argument provides
-the local server's name. The second argument provides the remote server's name.
-The third argument provides a reason for failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve reservations for all hosts
+identified by HW address or DUID. The argument holds both the identifier
+type and the value.
-HA_MAINTENANCE_NOTIFY_FAILED
-============================
+HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT
+==================================
.. code-block:: text
- %1: error returned while processing ha-maintenance-notify by %2: %3
+ using identifier %1, found %2 host(s)
-This warning message indicates that a peer returned an error status code
-in response to a ha-maintenance-notify command. The first argument provides the
-remote server's name. The second argument provides a reason for failure.
+Logged at debug log level 45.
+This debug message logs the number of hosts found using the specified
+identifier. The arguments specify the identifier used and the number
+of hosts found respectively.
-HA_MAINTENANCE_NOTIFY_HANDLER_FAILED
-====================================
+HOSTS_CFG_GET_ALL_IDENTIFIER_HOST
+=================================
.. code-block:: text
- ha-maintenance-notify command failed: %1
+ using identifier: %1, found host: %2
-This error message is issued to indicate that the ha-maintenance-notify command
-handler failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 55.
+This debug message is issued when found host identified by the specific
+identifier. The arguments specify the identifier and the detailed
+description of the host found.
-HA_MAINTENANCE_SHUTDOWN_SAFE
+HOSTS_CFG_GET_ALL_SUBNET_ID4
============================
.. code-block:: text
- %1: the server can now be shutdown for maintenance as the partner has taken over the DHCP traffic
+ get all hosts with reservations for IPv4 subnet %1
+
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts connected to
+the specific DHCPv4 subnet. The argument specifies subnet id.
+
+HOSTS_CFG_GET_ALL_SUBNET_ID4_COUNT
+==================================
+
+.. code-block:: text
+
+ using IPv4 subnet %1, found %2 host(s)
-This informational message is displayed after the server transitions to the
-in-maintenance state. This server no longer responds to any DHCP queries and its
-partner - in partner-in-maintenance state - has taken over the DHCP traffic.
-When the server in-maintenance state is shut down, the partner moves to
-the partner-down state immediately.
+Logged at debug log level 45.
+This debug message include the details of the host found using the DHCPv4
+subnet id. The arguments specify subnet id and the number of hosts found
+respectively.
-HA_MAINTENANCE_STARTED
-======================
+HOSTS_CFG_GET_ALL_SUBNET_ID4_HOST
+=================================
.. code-block:: text
- %1: the server is now in the partner-in-maintenance state and the partner is in-maintenance state
+ using IPv4 subnet %1, found host: %2
-This informational message is displayed when the server receiving the
-ha-maintenance-start command transitions to the partner-in-maintenance
-state. The server does it after sending the ha-maintenance-notify to
-its partner to put the partner in the in-maintenance state. From now on,
-the server in the partner-in-maintenance state will be responding to all
-queries and the partner will respond to no queries. The partner may be
-safely shut down for maintenance in which case this server will
-automatically transition from the partner-in-maintenance state to the
-partner-down state.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the DHCPv4
+subnet id. The arguments specify subnet id and found host details respectively.
-HA_MAINTENANCE_STARTED_IN_PARTNER_DOWN
-======================================
+HOSTS_CFG_GET_ALL_SUBNET_ID6
+============================
.. code-block:: text
- %1: the server is now in the partner-down mode as a result of requested maintenance
+ get all hosts with reservations for IPv6 subnet %1
-This informational message is displayed when the server receiving the
-ha-maintenance-start command transitions to the partner-down state
-because it was unable to communicate with the partner while receiving
-the command. It is assumed that in such situation the partner is
-already offline for the maintenance. Note that in this case the
-normal failover procedure does not take place. The server does not wait
-for a heartbeat to fail several times, nor it monitors the DHCP traffic
-for not responded queries. In the maintenance case the server transitions
-to the partner-down state when it first encounters a communication
-problem with the partner.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts connected to
+the specific DHCPv6 subnet. The argument specifies subnet id.
-HA_MAINTENANCE_START_HANDLER_FAILED
-===================================
+HOSTS_CFG_GET_ALL_SUBNET_ID6_COUNT
+==================================
.. code-block:: text
- ha-maintenance-start command failed: %1
+ using IPv6 subnet %1, found %2 host(s)
-This error message is issued to indicate that the ha-maintenance-start command
-handler failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 45.
+This debug message include the details of the host found using the DHCPv6
+subnet id. The arguments specify subnet id and the number of hosts found
+respectively.
-HA_MISSING_CONFIGURATION
-========================
+HOSTS_CFG_GET_ALL_SUBNET_ID6_HOST
+=================================
.. code-block:: text
- high-availability parameter not specified for High Availability hooks library
+ using IPv6 subnet %1, found host: %2
-This error message is issued to indicate that the configuration for the
-High Availability hooks library hasn't been specified. The 'high-availability'
-parameter must be specified for the hooks library to load properly.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the DHCPv6
+subnet id. The arguments specify subnet id and found host details respectively.
-HA_PAUSE_CLIENT_LISTENER_FAILED
-===============================
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4
+====================================
.. code-block:: text
- %1: pausing multi-threaded HTTP processing failed: %2
+ get all hosts with reservations for subnet id %1 and IPv4 address %2
-This error message is emitted when attempting to pause HA's HTTP client and
-listener threads. This error is highly unlikely and indicates a programmatic
-issue that should be reported as a defect.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts having
+the reservation for the given IPv4 address within the given subnet. The
+first argument specifies subnet identifier. The second argument specifies
+the IPv4 address for which the reservation is to be returned.
-HA_PAUSE_CLIENT_LISTENER_ILLEGAL
-================================
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_COUNT
+==========================================
.. code-block:: text
- %1: pausing multi-threaded HTTP processing failed: %2
+ using IPv4 subnet %1 and IPv4 address %2, found %3 host(s)
-This error message is emitted when attempting to pause HA's HTTP client or
-listener thread pools from a worker thread. This error indicates that a command
-run on the listener threads is trying to use a critical section which would
-result in a dead-lock.
+Logged at debug log level 45.
+This debug message logs the number of hosts found having the reservation
+for the specified IPv4 address within the specified subnet. The first
+argument specifies the subnet identifier. The second argument specifies
+the reserved IPv4 address. The third argument specifies the number of
+hosts found.
-HA_RESET_COMMUNICATIONS_FAILED
-==============================
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_HOST
+=========================================
.. code-block:: text
- %1: failed to send ha-reset command to %2: %3
+ using IPv4 subnet %1 and IPv4 address %2, found host: %3
-This warning message indicates a problem with communication with a HA peer
-while sending the ha-reset command. The first argument specifies the local
-server name. The second argument specifies a remote server name. The third
-argument specifies a reason for failure.
+Logged at debug log level 55.
+This debug message is issued when found host having the reservation for
+the specified IPv4 address in the specified subnet. The first argument
+specifies the subnet identifier. The second argument specifies the reserved
+IPv4 address. The third argument specifies host details.
-HA_RESET_FAILED
-===============
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6
+====================================
.. code-block:: text
- %1: failed to reset HA state machine of %2: %3
+ get all hosts with reservations for subnet id %1 and IPv6 address %2
-This warning message indicates that a peer returned an error status code
-in response to the ha-reset command. The first argument specifies a local
-server name. The second argument specifies a remote server name. The third
-argument specifies a reason for failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve all hosts connected to
+the specific subnet and having the specific IPv6 address reserved.
+The arguments specify subnet id and IPv6 address respectively.
-HA_RESET_HANDLER_FAILED
-=======================
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_COUNT
+==========================================
.. code-block:: text
- ha-reset command failed: %1
+ using subnet id %1 and address %2, found %3 host(s)
-This error message is issued to indicate that the ha-reset command handler
-failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 45.
+This debug message include the details of the host found using the
+subnet id and address. The arguments specify subnet id, address and
+the number of hosts found respectively.
-HA_RESUME_CLIENT_LISTENER_FAILED
-================================
+HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_HOST
+=========================================
.. code-block:: text
- %1: resuming multi-threaded HTTP processing failed: %2
+ using subnet id %1 and address %2, found host: %3
-This error message is emitted when attempting to resume HA's HTTP client and
-listener threads. This error is highly unlikely and indicates a programmatic
-issue that should be reported as a defect.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the
+subnet id and address. The arguments specify subnet id, address and
+the number of hosts found respectively.
+found host details respectively.
-HA_SCOPES_HANDLER_FAILED
+HOSTS_CFG_GET_ONE_PREFIX
========================
.. code-block:: text
- ha-scopes command failed: %1
+ get one host with reservation for prefix %1/%2
-This error message is issued to indicate that the ha-scopes command handler
-failed while processing the command. The argument provides reason for
-the failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host having a
+reservation for a specified prefix. The arguments specify a prefix and
+prefix length.
-HA_SERVICE_STARTED
-==================
+HOSTS_CFG_GET_ONE_PREFIX_HOST
+=============================
.. code-block:: text
- %1: started high availability service in %2 mode as %3 server
+ using prefix %1/%2, found host: %3
-This informational message is issued when the HA service is started as a result
-of server startup or reconfiguration. The first argument specifies a local server
-name. The second argument provides the HA mode. The third argument specifies the
-role of this server instance in this configuration.
+Logged at debug log level 55.
+This debug message includes the details of the host found using the
+specific prefix/prefix length. The arguments specify prefix, prefix
+length and host details respectively.
-HA_STATE_MACHINE_CONTINUED
-==========================
+HOSTS_CFG_GET_ONE_PREFIX_NULL
+=============================
.. code-block:: text
- %1: state machine is un-paused
+ host not found using prefix %1/%2
-This informational message is issued when the HA state machine is un-paused.
-This unlocks the server from the current state. It may transition to any
-other state if it needs to do so, e.g. 'partner-down' if its partner appears
-to be offline. The server may also remain in the current state if the HA
-setup state warrants such behavior.
+Logged at debug log level 55.
+This debug message is issued when no host was found for a specified
+prefix and prefix length.
-HA_STATE_MACHINE_PAUSED
-=======================
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4
+====================================
.. code-block:: text
- %1: state machine paused in state %2
+ get one host with reservation for subnet id %1 and IPv4 address %2
-This informational message is issued when the HA state machine is paused.
-HA state machine may be paused in certain states specified in the HA hooks library
-configuration. When the state machine is paused, the server remains in the given
-state until it is explicitly unpaused (via the ha-continue command). If the state
-machine is paused, the server operates normally but cannot transition to any
-other state.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host connected to the
+specific subnet and having the specific IPv4 address reserved. The
+arguments specify subnet id and IPv4 address respectively.
-HA_STATE_TRANSITION
-===================
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST
+=========================================
.. code-block:: text
- %1: server transitions from %2 to %3 state, partner state is %4
+ using subnet id %1 and address %2, found host: %3
-This informational message is issued when the server transitions to a new
-state as a result of some interaction (or lack of thereof) with its partner.
-The arguments specify local server name, initial server state, new server state
-and the partner's state.
+Logged at debug log level 45.
+This debug message logs the details of the host found using the
+subnet id and IPv4 address.
-HA_STATE_TRANSITION_PASSIVE_BACKUP
-==================================
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL
+=========================================
.. code-block:: text
- %1: server transitions from %2 to %3 state
+ host not found using subnet id %1 and address %2
-This informational message is issued when the server in passive-backup
-mode transitions to a new state. The arguments specify local server name, initial
-server state and a new server state.
+Logged at debug log level 45.
+This debug message is issued when no host was found for the specified
+subnet id and IPv4 address.
-HA_SUBNET4_SELECT_FAILED
-========================
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6
+====================================
.. code-block:: text
- subnet4_select callout failed: %1
+ get one host with reservation for subnet id %1 and having IPv6 address %2
+
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host connected to the
+specific subnet and having the specific IPv6 address reserved. The
+arguments specify subnet id and IPv6 address respectively.
+
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_HOST
+=========================================
+
+.. code-block:: text
+
+ using subnet id %1 and address %2, found host: %3
-This error message is issued when the callout for the subnet4_select hook
-point failed. This may occur as a result of an internal server error.
-The argument contains a reason for the error.
+Logged at debug log level 45.
+This debug message logs the details of the host found using the
+subnet id and IPv6 address.
-HA_SUBNET4_SELECT_INVALID_HA_SERVER_NAME
-========================================
+HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_NULL
+=========================================
.. code-block:: text
- %1: invalid ha-server-name value for subnet %2
+ host not found using subnet id %1 and address %2
-This error message is issued when the received DHCPv4 query is dropped
-by this server because the specified ha-server-name value in the subnet's
-user-context has non-string type or is empty. It is a server's misconifguration.
-The first argument is the client identification information. The second argument
-is a subnet prefix.
+Logged at debug log level 45.
+This debug message is issued when no host was found using the specified
+subnet if and IPv6 address.
-HA_SUBNET4_SELECT_NOT_FOR_US
-============================
+HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER
+======================================
.. code-block:: text
- %1: dropping query in relationship %2 to be processed by another server
+ get one host with %1 reservation for subnet id %2, identified by %3
Logged at debug log level 40.
-This debug message is issued when the received DHCPv4 query is dropped
-by this server because it should be served by another server. This
-is the case when a remote primary server is operational. The first argument
-is the client identification information. The second argument is the
-relationship name.
+This debug message is issued when starting to retrieve a host holding
+IPv4 or IPv6 reservations, which is connected to a specific subnet and
+is identified by a specific unique identifier. The first argument
+identifies if the IPv4 or IPv6 reservation is desired.
-HA_SUBNET4_SELECT_NO_RELATIONSHIP_FOR_SUBNET
-============================================
+HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST
+===========================================
.. code-block:: text
- %1: HA relationship not found for %2
+ using subnet id %1 and identifier %2, found host: %3
-This error message is issued when the received DHCPv4 query is dropped
-by this server because the server could not find a relationship matching
-the specified ha-server-name for a subnet. The server name matches no
-relationship specified in the HA configuration. A typical reason for it
-is a typo. The first argument is the client identification information.
-The second argument is the relationship name.
+Logged at debug log level 45.
+This debug message includes the details of a host found using a
+subnet id and specific host identifier.
-HA_SUBNET4_SELECT_NO_RELATIONSHIP_SELECTOR_FOR_SUBNET
-=====================================================
+HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL
+===========================================
.. code-block:: text
- %1: unable to determine HA relationship because selected subnet %2 lacks the ha-server-name
+ host not found using subnet id %1 and identifier %2
-This error message is issued when the received DHCPv4 query is dropped
-by this server because it was unable to determine the HA relationship to
-which the received query belongs. If there are multiple relationships,
-it is required to specify ha-server-name value in the user-context at the subnet
-or shared network level for each subnet and/or shared network. The server
-uses them as a relationship selector. If these selectors are unspecified
-for any of the subnets it is a configuration error. The first argument is
-the client identification information. The second argument is a subnet
-prefix.
+Logged at debug log level 45.
+This debug message is issued when no host was found using the specified
+subnet id and host identifier.
-HA_SUBNET4_SELECT_NO_SUBNET_SELECTED
-====================================
+HOSTS_CFG_UPDATE_ADD
+====================
.. code-block:: text
- %1: unable to determine HA relationship because no subnet has been selected for the client
+ add the host for reservations: %1
Logged at debug log level 40.
-This debug message is issued when the received DHCPv4 query is dropped
-by this server because it could not select a subnet for this client.
-Selecting the subnet is required to find a suitable HA relationship.
-This message is not emitted when the server has only one relationship.
-The argument is the client identification information.
+This debug message is issued when a new host (with reservations) is
+added to the server's configuration during an update. The argument
+describes the host and its reservations in detail.
-HA_SUBNET6_SELECT_FAILED
-========================
+HOSTS_CFG_UPDATE_DEL4
+=====================
.. code-block:: text
- subnet6_select callout failed: %1
+ deleted %1 host(s) for subnet id %2 and identifier %3
-This error message is issued when the callout for the subnet6_select hook
-point failed. This may occur as a result of an internal server error.
-The argument contains a reason for the error.
+Logged at debug log level 40.
+This debug message is issued when IPv4 reservations are deleted for
+the specified subnet and identifier during an update. The first
+argument specifies how many hosts have been deleted. The second
+argument is the subnet identifier. The third argument is the
+identifier.
-HA_SUBNET6_SELECT_INVALID_HA_SERVER_NAME
-========================================
+HOSTS_CFG_UPDATE_DEL6
+=====================
.. code-block:: text
- %1: invalid ha-server-name value for subnet %2
+ deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
-This error message is issued when the received DHCPv6 query is dropped
-by this server because the specified ha-server-name value in the subnet's
-user-context has non-string type or is empty. It is a server's misconifguration.
-The first argument is the client identification information. The second argument
-is a subnet prefix.
+Logged at debug log level 40.
+This debug message is issued when IPv6 reservations are deleted for
+the specified subnet and identifier during an update. The first
+argument specifies how many hosts have been deleted. The second
+argument specifies how many reservations have been deleted. The third
+argument is the subnet identifier. The fourth argument is the
+identifier.
-HA_SUBNET6_SELECT_NOT_FOR_US
-============================
+HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_ADDRESS4
+===========================================
.. code-block:: text
- %1: dropping query in relationship %2 to be processed by another server
+ trying alternate sources for host using subnet id %1 and address %2
Logged at debug log level 40.
-This debug message is issued when the received DHCPv6 query is dropped
-by this server because it should be served by another server. This
-is the case when a remote primary server is operational. The first argument
-is the client identification information. The second argument is the
-relationship name.
+This debug message is issued when the Host Manager doesn't find the
+host connected to the specific subnet and having the reservation for
+the specific IPv4 address, and it is starting to search for this host
+in alternate host data sources.
-HA_SUBNET6_SELECT_NO_RELATIONSHIP_FOR_SUBNET
-============================================
+HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER
+=============================================
.. code-block:: text
- %1: HA relationship not found for %2
+ get one host with IPv4 reservation for subnet id %1, identified by %2
-This error message is issued when the received DHCPv6 query is dropped
-by this server because the server could not find a relationship matching
-the specified ha-server-name for a subnet. The server name matches no
-relationship specified in the HA configuration. A typical reason for it
-is a typo. The first argument is the client identification information.
-The second argument is the relationship name.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host holding
+IPv4 reservation, which is connected to a specific subnet and
+is identified by a specific unique identifier.
-HA_SUBNET6_SELECT_NO_RELATIONSHIP_SELECTOR_FOR_SUBNET
-=====================================================
+HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_HOST
+==================================================
.. code-block:: text
- %1: unable to determine HA relationship because selected subnet %2 lacks the ha-server-name
+ using subnet id %1 and identifier %2, found in %3 host: %4
-This error message is issued when the received DHCPv6 query is dropped
-by this server because it was unable to determine the HA relationship to
-which the received query belongs. If there are multiple relationships,
-it is required to specify ha-server-name value in the user-context at the subnet
-or shared network level for each subnet and/or shared network. The server
-uses them as a relationship selector. If these selectors are unspecified
-for any of the subnets it is a configuration error. The first argument is
-the client identification information. The second argument is a subnet
-prefix.
+Logged at debug log level 45.
+This debug message includes the details of a host returned by an
+alternate hosts data source using a subnet id and specific host
+identifier.
-HA_SUBNET6_SELECT_NO_SUBNET_SELECTED
-====================================
+HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_NULL
+==================================================
.. code-block:: text
- %1: unable to determine HA relationship because no subnet has been selected for the client
+ host not found using subnet id %1 and identifier %2
-Logged at debug log level 40.
-This debug message is issued when the received DHCPv6 query is dropped
-by this server because it could not select a subnet for this client.
-Selecting the subnet is required to find a suitable HA relationship.
-This message is not emitted when the server has only one relationship.
-The argument is the client identification information.
+Logged at debug log level 45.
+This debug message is issued when no host was found using the specified
+subnet id and host identifier.
-HA_SYNC_COMPLETE_NOTIFY_COMMUNICATIONS_FAILED
-=============================================
+HOSTS_MGR_ALTERNATE_GET6_PREFIX
+===============================
.. code-block:: text
- %1: failed to send ha-sync-complete-notify to %2: %3
+ trying alternate sources for host using prefix %1/%2
-This warning message indicates that there was a problem in communication with an
-HA peer while sending the ha-sync-complete-notify command. The first argument
-provides a local server's name. The second argument provides the remote server's
-name. The third argument provides a reason for failure.
+Logged at debug log level 40.
+This debug message is issued when the Host Manager doesn't find the
+host connected to the specific subnet and having the reservation for
+the specified prefix, and it is starting to search for this host in
+alternate host data sources.
-HA_SYNC_COMPLETE_NOTIFY_FAILED
-==============================
+HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_ADDRESS6
+===========================================
.. code-block:: text
- %1: error processing ha-sync-complete-notify command on %2: %3
+ trying alternate sources for host using subnet id %1 and IPv6 address %2
-This warning message indicates that a peer returned an error status code
-in response to the ha-sync-complete-notify command. The first argument provides
-a local server's name. The second argument provides the remote server's name. The
-third argument provides a reason for failure.
+Logged at debug log level 40.
+This debug message is issued when the Host Manager doesn't find the
+host connected to the specific subnet and having the reservation for
+the specified IPv6 address, and it is starting to search for this
+host in alternate host data sources.
-HA_SYNC_COMPLETE_NOTIFY_HANDLER_FAILED
-======================================
+HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER
+=============================================
.. code-block:: text
- ha-sync-complete-notify command failed: %1
+ get one host with IPv6 reservation for subnet id %1, identified by %2
-This error message is issued to indicate that the ha-sync-complete-notify command
-handler failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host holding
+IPv4 reservation, which is connected to a specific subnet and
+is identified by a specific unique identifier.
-HA_SYNC_FAILED
-==============
+HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_HOST
+==================================================
.. code-block:: text
- %1: lease database synchronization with %2 failed: %3
+ using subnet id %1 and identifier %2, found in %3 host: %4
-This error message is issued to indicate that the lease database synchronization
-failed. The first argument provides the local server's name. The second argument
-provides the partner server's name. The third argument provides a reason for the
-failure.
+Logged at debug log level 45.
+This debug message includes the details of a host returned by an
+alternate host data source using a subnet id and specific host
+identifier.
-HA_SYNC_HANDLER_FAILED
-======================
+HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_NULL
+==================================================
.. code-block:: text
- ha-sync command failed: %1
+ host not found using subnet id %1 and identifier %2
-This error message is issued to indicate that the ha-sync command handler
-failed while processing the command. The argument provides the reason for
-failure.
+Logged at debug log level 45.
+This debug message is issued when no host was found using the specified
+subnet id and host identifier.
-HA_SYNC_START
-=============
+HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS4
+==============================================
.. code-block:: text
- %1: starting lease database synchronization with %2
+ trying alternate sources for hosts using subnet id %1 and address %2
-This informational message is issued when the server starts lease database
-synchronization with a partner. The arguments specify the local and remote
-server names.
+Logged at debug log level 40.
+This debug message is issued when the Host Manager is starting to search
+for hosts in alternate host data sources by subnet ID and IPv4 address.
-HA_SYNC_SUCCESSFUL
-==================
+HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS6
+==============================================
.. code-block:: text
- %1: lease database synchronization with %2 completed successfully in %3
+ trying alternate sources for hosts using subnet id %1 and address %2
-This informational message is issued when the server successfully completed
-lease database synchronization with the partner. The first argument specifies
-local server name. The second argument specifies the name of the partner server.
-The third argument specifies the duration of the synchronization.
+Logged at debug log level 40.
+This debug message is issued when the Host Manager is starting to search
+for hosts in alternate host data sources by subnet ID and IPv6 address.
-HA_TERMINATED
-=============
+****
+HOST
+****
+
+HOST_CACHE_ADD
+==============
.. code-block:: text
- HA %1: service terminated due to an unrecoverable condition. Check previous error message(s), address the problem and restart!
+ add host: %1
-This error message is issued to indicate that the HA service has been stopped
-due to an unacceptable condition (e.g. too large of a clock skew). The exact
-cause should appear in a previous error message. Address the condition
-reported then restart the servers to resume service.
+Logged at debug log level 45.
+This debug message logs the details of the added host cache entry.
-HA_TERMINATED_PARTNER_DID_NOT_RESTART
-=====================================
+HOST_CACHE_ADD_DUPLICATE
+========================
.. code-block:: text
- %1: service is terminating because the terminated partner was not restarted within %2 minutes
-
-This warning message is issued to indicate that the HA service is terminating
-because partner server is in the terminated state and was not restarted within
-an expected time frame. The terminated servers should be restarted after correcting
-the problem that caused the termination. They can be restarted sequentially but the
-duration between the restarts should not be too long. If it is long it may mean that
-the restart of one of the servers was unintentional (e.g., power outage). If the
-restarted server remains in the waiting state it cannot serve DHCP clients. Moving
-to the terminated state at least allows for responding to the DHCP traffic.
+ duplicate host: %1
-*****
-HOOKS
-*****
+Logged at debug log level 45.
+The add operation failed because the entry conflicts with an already
+existing one. The details of the add operation argument are logged.
-HOOKS_ALL_CALLOUTS_DEREGISTERED
-===============================
+HOST_CACHE_COMMAND_CLEAR
+========================
.. code-block:: text
- hook library at index %1 removed all callouts on hook %2
+ cache-clear command successful
-Logged at debug log level 55.
-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.
+The cache-clear command has been successful.
-HOOKS_CALLOUTS_BEGIN
-====================
+HOST_CACHE_COMMAND_CLEAR_FAILED
+===============================
.. code-block:: text
- begin all callouts for hook %1
+ cache-clear command failed (reason: %1)
-Logged at debug log level 45.
-This debug message is issued when callout manager begins to invoke callouts
-for the hook. The argument specifies the hook name.
+The cache-clear command has failed. The reason is logged.
-HOOKS_CALLOUTS_COMPLETE
-=======================
+HOST_CACHE_COMMAND_FLUSH
+========================
.. code-block:: text
- completed callouts for hook %1 (total callouts duration: %2)
+ cache-flush command successful
-Logged at debug log level 45.
-This debug message is issued when callout manager has completed execution
-of all callouts for the particular hook. The arguments specify the hook
-name and total execution time for all callouts in milliseconds.
+The cache-flush command has been successful.
-HOOKS_CALLOUTS_REMOVED
-======================
+HOST_CACHE_COMMAND_FLUSH_FAILED
+===============================
.. code-block:: text
- callouts removed from hook %1 for library %2
+ cache-flush command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-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.
+The cache-flush command has failed. Both the reason as well as the
+parameters passed are logged.
-HOOKS_CALLOUT_CALLED
-====================
+HOST_CACHE_COMMAND_GET
+======================
.. code-block:: text
- hooks library with index %1 has called a callout on hook %2 that has address %3 (callout duration: %4)
+ cache-get command successful (returned: %1)
-Logged at debug log level 55.
-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.
-The message includes the callout execution time in milliseconds.
+The cache-get command has been successful. The number of returned entries
+is logged.
-HOOKS_CALLOUT_DEREGISTERED
-==========================
+HOST_CACHE_COMMAND_GET_BY_ID
+============================
.. code-block:: text
- hook library at index %1 deregistered a callout on hook %2
+ cache-get-by-id command successful (returned: %1)
-Logged at debug log level 55.
-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.
+The cache-get-by-id command has been successful. The number of returned entries
+is logged.
-HOOKS_CALLOUT_ERROR
-===================
+HOST_CACHE_COMMAND_GET_BY_ID_FAILED
+===================================
.. code-block:: text
- error returned by callout on hook %1 registered by library with index %2 (callout address %3) (callout duration %4)
+ cache-get-by-id command failed (reason: %1)
-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.
-The error message includes the callout execution time in milliseconds.
+The cache-get-by-id command has failed. The reason is logged.
-HOOKS_CALLOUT_EXCEPTION
-=======================
+HOST_CACHE_COMMAND_GET_FAILED
+=============================
.. code-block:: text
- exception thrown by callout on hook %1 registered by library with index %2 (callout address %3): %4 (callout duration: %5)
+ cache-get command failed (reason: %1)
-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.
-The error message includes the callout execution time in milliseconds.
+The cache-get command has failed. The reason is logged.
-HOOKS_CALLOUT_REGISTRATION
-==========================
+HOST_CACHE_COMMAND_INSERT
+=========================
.. code-block:: text
- hooks library with index %1 registering callout for hook '%2'
+ cache-insert command successful (inserted: %1, overwritten: %2)
-Logged at debug log level 45.
-This is a debug message, output when a library (whose index in the list
-of libraries (being) loaded is given) registers a callout.
+The cache-insert command has been successful. The number of inserted entries
+and the number of entries overwritten by more recent entries are logged.
-HOOKS_CLOSE_ERROR
-=================
+HOST_CACHE_COMMAND_INSERT_FAILED
+================================
.. code-block:: text
- failed to close hook library %1: %2
+ cache-insert command failed (parameters: %1, reason: %2)
-Kea 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 Kea.
+The cache-insert command has failed. Both the reason as well as the
+parameters passed are logged.
-HOOKS_HOOK_LIST_RESET
-=====================
+HOST_CACHE_COMMAND_LOAD
+=======================
.. code-block:: text
- the list of hooks has been reset
+ cache-load command successful (loaded: %1, overwritten: %2)
-This is a message indicating that the list of hooks has been reset.
-While this is usual when running the Kea test suite, it should not be
-seen when running Kea in a production environment. If this appears,
-please report a bug through the usual channels.
+The cache-load command has been successful. The number of loaded entries
+and the number of entries overwritten by more recent entries are logged.
-HOOKS_INCORRECT_VERSION
-=======================
+HOST_CACHE_COMMAND_LOAD_FAILED
+==============================
.. code-block:: text
- hook library %1 is at version %2, require version %3
+ cache-load command failed (parameters: %1, reason: %2)
-Kea has detected that the named hook library has been built against
-a version of Kea that is incompatible with the version of Kea
-running on your system. It has not loaded the library.
-This is most likely due to the installation of a new version of Kea
-without rebuilding the hook library. A rebuild and re-install of the
-library should fix the problem in most cases.
+The cache-load command has failed. Both the reason as well as the
+parameters passed are logged.
-HOOKS_LIBRARY_CLOSED
-====================
+HOST_CACHE_COMMAND_REMOVE
+=========================
.. code-block:: text
- hooks library %1 successfully closed
+ cache-remove command successful (parameters: %1)
-This information message is issued when a user-supplied hooks library
-has been successfully closed.
+The cache-remove command has been successful. Parameters of the host
+deleted are logged.
-HOOKS_LIBRARY_LOADED
-====================
+HOST_CACHE_COMMAND_REMOVE_FAILED
+================================
.. code-block:: text
- hooks library %1 successfully loaded
+ cache-remove command failed (parameters: %1, reason: %2)
-This information message is issued when a user-supplied hooks library
-has been successfully loaded.
+The cache-remove command has failed. Both the reason as well as the
+parameters passed are logged.
-HOOKS_LIBRARY_LOADING
-=====================
+HOST_CACHE_COMMAND_SIZE
+=======================
.. code-block:: text
- loading hooks library %1
+ cache-clear command successful: %1
-Logged at debug log level 40.
-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.
+The cache-size command has been successful and returned the number of
+entries in the host cache.
-HOOKS_LIBRARY_MULTI_THREADING_COMPATIBLE
-========================================
+HOST_CACHE_COMMAND_SIZE_FAILED
+==============================
.. code-block:: text
- hooks library %1 reports its multi-threading compatibility as %2
+ cache-size command failed (reason: %1)
-Logged at debug log level 45.
-A debug message issued when the "multi_threading_compatible" function was
-called. The returned value (0 means not compatible, others compatible)
-is displayed.
+The cache-size command has failed. The reason is logged.
-HOOKS_LIBRARY_MULTI_THREADING_NOT_COMPATIBLE
-============================================
+HOST_CACHE_COMMAND_WRITE
+========================
.. code-block:: text
- hooks library %1 is not compatible with multi-threading
+ cache-write command successful (dumped: %1)
-When multi-threading is enabled and the library is not compatible (either
-because the "multi_threading_compatible" function returned 0 or was not
-implemented) this error message is issued. The library must be removed
-from the configuration or the multi-threading disabled.
+The cache-write command has been successful. The number of dumped entries
+is logged.
-HOOKS_LIBRARY_UNLOADED
-======================
+HOST_CACHE_COMMAND_WRITE_FAILED
+===============================
.. code-block:: text
- hooks library %1 successfully unloaded
+ cache-write command failed (parameters: %1, reason: %2)
-This information message is issued when a user-supplied hooks library
-has been successfully unloaded.
+The cache-write command has failed. Both the reason as well as the
+parameters passed are logged.
-HOOKS_LIBRARY_UNLOADING
-=======================
+HOST_CACHE_CONFIGURATION_FAILED
+===============================
.. code-block:: text
- unloading library %1
+ failed to configure Host Cache hooks library: %1
-Logged at debug log level 40.
-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.
+This error message is issued when there is an error configuring the Host
+Cache hooks library. The argument provides the detailed error message.
-HOOKS_LIBRARY_VERSION
-=====================
+HOST_CACHE_DEINIT_OK
+====================
.. code-block:: text
- hooks library %1 reports its version as %2
+ unloading Host Cache hooks library successful
-Logged at debug log level 45.
-A debug message issued when the version check on the hooks library
-has succeeded.
+This informational message indicates that the Host Cache hooks library
+has been unloaded successfully.
-HOOKS_LOAD_ERROR
-================
+HOST_CACHE_DEL_SUBNET_ID_ADDRESS4
+=================================
.. code-block:: text
- 'load' function in hook library %1 returned error %2
+ using subnet id %1 and address %2, delete host: %3
-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.
+Logged at debug log level 45.
+This debug message logs the details of the host cache entry deleted using
+the subnet id and IPv4 address.
-HOOKS_LOAD_EXCEPTION
-====================
+HOST_CACHE_DEL_SUBNET_ID_ADDRESS6
+=================================
.. code-block:: text
- 'load' function in hook library %1 threw an exception
+ using subnet id %1 and address %2, delete host: %3
-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.
+Logged at debug log level 45.
+This debug message logs the details of the host cache entry deleted using
+the subnet id and IPv6 address.
-HOOKS_LOAD_FRAMEWORK_EXCEPTION
-==============================
+HOST_CACHE_DEL_SUBNET_ID_IDENTIFIER4
+====================================
.. code-block:: text
- 'load' function in hook library %1 threw an exception: reason %2
+ using subnet id %1 and identifier %2, delete host: %3
-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.
+Logged at debug log level 45.
+This debug message logs the details of the host cache entry deleted using a
+subnet id and specific host identifier.
-HOOKS_LOAD_SUCCESS
-==================
+HOST_CACHE_DEL_SUBNET_ID_IDENTIFIER6
+====================================
.. code-block:: text
- 'load' function in hook library %1 returned success
+ using subnet id %1 and identifier %2, delete host: %3
-Logged at debug log level 40.
-This is a debug message issued when the "load" function has been found
-in a hook library and has been successfully called.
+Logged at debug log level 45.
+This debug message logs the details of the host cache entry deleted using a
+subnet id and specific host identifier.
-HOOKS_MULTI_THREADING_COMPATIBLE_EXCEPTION
-==========================================
+HOST_CACHE_GET_ONE_PREFIX
+=========================
.. code-block:: text
- 'multi_threading_compatible' function in hook library %1 threw an exception
+ get one host with reservation for prefix %1/%2
-This error message is issued if the multi_threading_compatible()
-function in the specified hooks library was called and generated an
-exception. The library is considered unusable and will not be loaded.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host cache entry
+having a reservation for a specified prefix. The arguments specify a prefix
+and prefix length.
-HOOKS_NO_LOAD
-=============
+HOST_CACHE_GET_ONE_PREFIX_HOST
+==============================
.. code-block:: text
- no 'load' function found in hook library %1
+ using prefix %1/%2, found host: %3
-Logged at debug log level 40.
-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.
+Logged at debug log level 45.
+This debug message includes the details of the host cache entry found
+using the specific prefix/prefix length. The arguments specify prefix,
+prefix length and host details respectively.
-HOOKS_NO_UNLOAD
-===============
+HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS4
+=====================================
.. code-block:: text
- no 'unload' function found in hook library %1
+ get one host with reservation for subnet id %1 and IPv4 address %2
Logged at debug log level 40.
-This is a debug message issued when the library is being unloaded.
-It merely states that the library did not contain an "unload" function.
+This debug message is issued when starting to retrieve a host cache entry
+connected to the specific subnet and having the specific IPv4 address reserved.
+The arguments specify subnet id and IPv4 address respectively.
-HOOKS_NO_VERSION
-================
+HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS4_HOST
+==========================================
.. code-block:: text
- no 'version' function found in hook library %1
+ using subnet id %1 and address %2, found host: %3
-The shared library named in the message was found and successfully loaded,
-but Kea did not find a function named "version" in it. This function
-is required and should return the version of Kea against which the
-library was built. The value is used to check that the library was built
-against a compatible version of Kea. The library has not been loaded.
+Logged at debug log level 45.
+This debug message logs the details of the host cache entry found using the
+subnet id and IPv4 address.
-HOOKS_OPEN_ERROR
-================
+HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS6
+=====================================
.. code-block:: text
- failed to open hook library %1: %2
+ get one host with reservation for subnet id %1 and including IPv6 address %2
-Kea failed to open the specified hook library for the stated
-reason. The library has not been loaded. Kea will continue to
-function, but without the services offered by the library.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host cache entry
+connected to the specific subnet and having the specific IPv6 address
+reserved. The arguments specify subnet id and IPv6 address respectively.
-HOOKS_STD_CALLOUT_REGISTERED
-============================
+HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS6_HOST
+==========================================
.. code-block:: text
- hooks library %1 registered standard callout for hook %2 at address %3
+ using subnet id %1 and address %2, found host: %3
Logged at debug log level 45.
-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.
+This debug message logs the details of the host cache entry found using
+the subnet id and IPv6 address.
-HOOKS_UNLOAD_ERROR
-==================
+HOST_CACHE_GET_ONE_SUBNET_ID_IDENTIFIER
+=======================================
.. code-block:: text
- 'unload' function in hook library %1 returned error %2
+ get one host with %1 reservation for subnet id %2, identified by %3
-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.
+Logged at debug log level 40.
+This debug message is issued when starting to retrieve a host cache entry
+holding IPv4 or IPv6 reservations, which is connected to a specific subnet
+and is identified by a specific unique identifier. The first argument
+identifies if the IPv4 or IPv6 reservation is desired.
-HOOKS_UNLOAD_EXCEPTION
-======================
+HOST_CACHE_GET_ONE_SUBNET_ID_IDENTIFIER_HOST
+============================================
.. code-block:: text
- 'unload' function in hook library %1 threw an exception
+ using subnet id %1 and identifier %2, found host: %3
-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.
+Logged at debug log level 45.
+This debug message includes the details of a host cache entry found using a
+subnet id and specific host identifier.
-HOOKS_UNLOAD_FRAMEWORK_EXCEPTION
-================================
+HOST_CMDS_DEINIT_OK
+===================
.. code-block:: text
- 'unload' function in hook library %1 threw an exception, reason %2
+ unloading Host Commands hooks library successful
-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.
+This info message indicates that the Host Commands hooks library has been
+removed successfully.
-HOOKS_UNLOAD_SUCCESS
-====================
+HOST_CMDS_INIT_FAILED
+=====================
.. code-block:: text
- 'unload' function in hook library %1 returned success
-
-Logged at debug log level 40.
-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.
+ loading Host Commands hooks library failed: %1
-*****
-HOSTS
-*****
+This error message indicates an error during loading the Host Commands
+hooks library. The details of the error are provided as argument of
+the log message.
-HOSTS_BACKENDS_REGISTERED
-=========================
+HOST_CMDS_INIT_OK
+=================
.. code-block:: text
- the following host backend types are available: %1
+ loading Host Commands hooks library successful
-This informational message lists all possible host backends that could
-be used in hosts-database[s].
+This info message indicates that the Host Commands hooks library has been
+loaded successfully. Enjoy!
-HOSTS_BACKEND_DEREGISTER
-========================
+HOST_CMDS_RESERV_ADD
+====================
.. code-block:: text
- deregistered host backend type: %1
+ reservation-add command called (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when a backend factory was deregistered.
-It is no longer possible to use host backend of this type.
+The reservation-add command has been called. Parameters passed are logged.
-HOSTS_BACKEND_REGISTER
-======================
+HOST_CMDS_RESERV_ADD_FAILED
+===========================
.. code-block:: text
- registered host backend type: %1
+ reservation-add command failed (parameters: %1, reason: %2)
-Logged at debug log level 40.
-This debug message is issued when a backend factory was successfully
-registered. It is now possible to use host backend of this type.
+The reservation-add command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_ADD_HOST
-==================
+HOST_CMDS_RESERV_ADD_SUCCESS
+============================
.. code-block:: text
- add the host for reservations: %1
+ reservation-add command success (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when new host (with reservations) is added to
-the server's configuration. The argument describes the host and its
-reservations in detail.
+The reservation-add command has been successful. Parameters passed are logged.
-HOSTS_CFG_CACHE_HOST_DATA_SOURCE
-================================
+HOST_CMDS_RESERV_DEL
+====================
.. code-block:: text
- get host cache data source: %1
+ reservation-del command called (parameters: %1)
-This informational message is issued when a host cache data source is
-detected by the host manager.
+The reservation-del command has been called. Parameters passed are logged.
-HOSTS_CFG_CLOSE_HOST_DATA_SOURCE
-================================
+HOST_CMDS_RESERV_DEL_FAILED
+===========================
.. code-block:: text
- Closing host data source: %1
+ reservation-del command failed (parameters: %1, reason: %2)
-Logged at debug log level 40.
-This is a normal message being printed when the server closes host data
-source connection.
+The reservation-del command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_DEL
-=============
+HOST_CMDS_RESERV_DEL_SUCCESS
+============================
.. code-block:: text
- deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and address %4
+ reservation-del command success (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when reservations are deleted for the specified
-subnet and address. The first argument specifies how many hosts have been
-deleted. The second argument specifies how many reservations have been deleted.
-The third argument is the subnet identifier. The fourth argument is the IP
-address.
+The reservation-del command has been successful. Parameters passed are logged.
-HOSTS_CFG_DEL4
-==============
+HOST_CMDS_RESERV_GET
+====================
.. code-block:: text
- deleted %1 host(s) for subnet id %2 and identifier %3
+ reservation-get command called (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when IPv4 reservations are deleted for the specified
-subnet and identifier. The first argument specifies how many hosts have been
-deleted. The second argument is the subnet identifier. The third argument is
-the identifier.
+The reservation-get command has been called. Parameters passed are logged.
-HOSTS_CFG_DEL6
-==============
+HOST_CMDS_RESERV_GET_ALL
+========================
.. code-block:: text
- deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
+ reservation-get-all command called (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when IPv6 reservations are deleted for the
-specified subnet and identifier. The first argument specifies how many hosts
-have been deleted. The second argument specifies how many reservations have
-been deleted. The third argument is the subnet identifier. The fourth argument
-is the identifier.
+The reservation-get-all command has been called. Parameters passed are logged.
-HOSTS_CFG_DEL_ALL_SUBNET4
-=========================
+HOST_CMDS_RESERV_GET_ALL_FAILED
+===============================
.. code-block:: text
- deleted all %1 host(s) for subnet id %2
+ reservation-get-all command failed (parameters: %1, reason: %2)
-Logged at debug log level 40.
-This debug message is issued when all IPv4 reservations are deleted for
-the specified subnet. The first argument specifies how many reservations
-have been deleted. The second argument is the subnet identifier.
+The reservation-get-all command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_DEL_ALL_SUBNET6
-=========================
+HOST_CMDS_RESERV_GET_ALL_SUCCESS
+================================
.. code-block:: text
- deleted all %1 host(s) having %2 IPv6 reservation(s) for subnet id %3
+ reservation-get-all command success (parameters: %1)
-Logged at debug log level 40.
-This debug message is issued when all IPv6 reservations are deleted for
-the specified subnet. The first argument specifies how many hosts
-have been deleted. The second argument specifies how many IPv6
-(addresses and prefixes) reservations have been deleted. The third argument is
-the subnet identifier.
+The reservation-get-all command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL
-=================
+HOST_CMDS_RESERV_GET_BY_ADDRESS
+===============================
.. code-block:: text
- get all hosts with reservations
+ reservation-get-by-address command called (parameters: %1)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts.
+The reservation-get-by-address command has been called. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS4
-==========================
+HOST_CMDS_RESERV_GET_BY_ADDRESS_FAILED
+======================================
.. code-block:: text
- get all hosts with reservations for IPv4 address %1
+ reservation-get-by-address command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts, holding the
-reservation for the specific IPv4 address, from the configuration. The
-argument specifies the IPv4 address used to search the hosts.
+The reservation-get-by-address command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS4_COUNT
-================================
+HOST_CMDS_RESERV_GET_BY_ADDRESS_SUCCESS
+=======================================
.. code-block:: text
- using address %1, found %2 host(s)
+ reservation-get-by-address command success (parameters: %1)
-Logged at debug log level 45.
-This debug message logs the number of hosts found using the specified
-IPv4 address. The arguments specify the IPv4 address used and the number
-of hosts found respectively.
+The reservation-get-by-address command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS4_HOST
-===============================
+HOST_CMDS_RESERV_GET_BY_HOSTNAME
+================================
.. code-block:: text
- using address %1 found host: %2
+ reservation-get-by-hostname command called (parameters: %1)
-Logged at debug log level 55.
-This debug message is issued when found host with the reservation
-for the specified IPv4 address. The arguments specify the IPv4 address
-and the detailed description of the host found.
+The reservation-get-by-hostname command has been called. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS6
-==========================
+HOST_CMDS_RESERV_GET_BY_HOSTNAME_FAILED
+=======================================
.. code-block:: text
- get all hosts with reservations for IPv6 address %1
+ reservation-get-by-hostname command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts, holding the
-reservation for the specific IPv6 address, from the configuration.
-The argument specifies the IPv6 address used to search the hosts.
+The reservation-get-by-hostname command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS6_COUNT
-================================
+HOST_CMDS_RESERV_GET_BY_HOSTNAME_SUCCESS
+========================================
.. code-block:: text
- using address %1, found %2 host(s)
+ reservation-get-by-hostname command success (parameters: %1)
-Logged at debug log level 45.
-This debug message logs the number of hosts found using the specified
-IPv6 address. The arguments specify the IPv6 address used and the number
-of hosts found respectively.
+The reservation-get-by-hostname command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_ADDRESS6_HOST
-===============================
+HOST_CMDS_RESERV_GET_BY_ID
+==========================
.. code-block:: text
- using address %1 found host: %2
+ reservation-get-by-id command called (parameters: %1)
-Logged at debug log level 55.
-This debug message is issued when found host with the reservation
-for the specified IPv6 address. The arguments specify the IPv6 address
-and the detailed description of the host found.
+The reservation-get-by-id command has been called. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_COUNT
-=======================
+HOST_CMDS_RESERV_GET_BY_ID_FAILED
+=================================
.. code-block:: text
- found %1 host(s)
+ reservation-get-by-id command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message include the details of the host found. The argument
-specifies the number of hosts found.
+The reservation-get-by-id command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOST
-======================
+HOST_CMDS_RESERV_GET_BY_ID_SUCCESS
+==================================
.. code-block:: text
- found host: %1
+ reservation-get-by-id command success (parameters: %1)
-Logged at debug log level 45.
-This debug message includes the details of the host found. The argument
-specifies found host details.
+The reservation-get-by-id command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME
-==========================
+HOST_CMDS_RESERV_GET_FAILED
+===========================
.. code-block:: text
- get all hosts with reservations for hostname %1
+ reservation-get command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts with
-the specific hostname. The argument specifies hostname.
+The reservation-add command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_COUNT
-================================
+HOST_CMDS_RESERV_GET_PAGE
+=========================
.. code-block:: text
- using hostname %1, found %2 host(s)
+ reservation-get-page command called (parameters: %1)
-Logged at debug log level 45.
-This debug message include the details of the host found using the
-hostname. The arguments specify hostname and the number of hosts found
-respectively.
+The reservation-get-page command has been called. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_HOST
-===============================
+HOST_CMDS_RESERV_GET_PAGE_FAILED
+================================
.. code-block:: text
- using hostname %1, found host: %2
+ reservation-get-page command failed (parameters: %1, reason: %2)
-Logged at debug log level 55.
-This debug message includes the details of the host found using the hostname.
-The arguments specify hostname and found host details respectively.
+The reservation-get-page command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4
-=====================================
+HOST_CMDS_RESERV_GET_PAGE_SUCCESS
+=================================
.. code-block:: text
- get all hosts with reservations for hostname %1 and IPv4 subnet %2
+ reservation-get-page command success (parameters: %1)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts with
-the specific hostname connected to the specific DHCPv4 subnet. The argument
-specifies hostname and subnet id.
+The reservation-get-page command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_COUNT
-===========================================
+HOST_CMDS_RESERV_GET_SUCCESS
+============================
.. code-block:: text
- using hostname %1 and IPv4 subnet %2, found %3 host(s)
+ reservation-get command success (parameters: %1)
-Logged at debug log level 45.
-This debug message include the details of the host found using the
-hostname and the DHCPv4 subnet id. The arguments specify hostname,
-subnet id and the number of hosts found respectively.
+The reservation-get command has been successful. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_HOST
-==========================================
+HOST_CMDS_RESERV_UPDATE
+=======================
.. code-block:: text
- using hostname %1 and IPv4 subnet %2, found host: %3
+ reservation-update command called (parameters: %1)
-Logged at debug log level 55.
-This debug message includes the details of the host found using the
-hostname and the DHCPv4 subnet id. The arguments specify hostname,
-subnet id and found host details respectively.
+The reservation-update command has been called. Parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6
-=====================================
+HOST_CMDS_RESERV_UPDATE_FAILED
+==============================
.. code-block:: text
- get all hosts with reservations for hostname %1 and IPv6 subnet %2
+ reservation-update command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts with
-the specific hostname connected to the specific DHCPv6 subnet. The argument
-specifies hostname and subnet id.
+The reservation-update command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_COUNT
-===========================================
+*****
+HTTPS
+*****
+
+HTTPS_REQUEST_RECEIVE_START
+===========================
.. code-block:: text
- using hostname %1 and IPv6 subnet %2, found %3 host(s)
+ start receiving request from %1
-Logged at debug log level 45.
-This debug message include the details of the host found using the
-hostname and the DHCPv6 subnet id. The arguments specify hostname,
-subnet id and the number of hosts found respectively.
+Logged at debug log level 50.
+This debug message is issued when the server starts receiving new request
+over the established connection. The argument specifies the address
+of the remote endpoint.
-HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_HOST
-==========================================
+****
+HTTP
+****
+
+HTTP_BAD_CLIENT_REQUEST_RECEIVED
+================================
.. code-block:: text
- using hostname %1 and IPv6 subnet %2, found host: %3
+ bad request received from %1: %2
-Logged at debug log level 55.
-This debug message includes the details of the host found using the
-hostname and the DHCPv6 subnet id. The arguments specify hostname,
-subnet id and found host details respectively.
+Logged at debug log level 40.
+This debug message is issued when an HTTP client sends malformed request to
+the server. This includes HTTP requests using unexpected content types,
+including malformed JSON etc. The first argument specifies an address of
+the remote endpoint which sent the request. The second argument provides
+a detailed error message.
-HOSTS_CFG_GET_ALL_IDENTIFIER
-============================
+HTTP_BAD_CLIENT_REQUEST_RECEIVED_DETAILS
+========================================
.. code-block:: text
- get all hosts with reservations using identifier: %1
+ detailed information about bad request received from %1:\n%2
Logged at debug log level 45.
-This debug message is issued when starting to retrieve reservations for all hosts
-identified by HW address or DUID. The argument holds both the identifier
-type and the value.
+This debug message is issued when an HTTP client sends malformed request to
+the server. It includes detailed information about the received request
+rejected by the server. The first argument specifies an address of
+the remote endpoint which sent the request. The second argument provides
+a request in the textual format. The request is truncated by the logger
+if it is too large to be printed.
-HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT
-==================================
+HTTP_BAD_SERVER_RESPONSE_RECEIVED
+=================================
.. code-block:: text
- using identifier %1, found %2 host(s)
+ bad response received when communicating with %1: %2
-Logged at debug log level 45.
-This debug message logs the number of hosts found using the specified
-identifier. The arguments specify the identifier used and the number
-of hosts found respectively.
+Logged at debug log level 40.
+This debug message is issued when an HTTP client fails to receive a response
+from the server or when this response is malformed. The first argument
+specifies the server URL. The second argument provides a detailed error
+message.
-HOSTS_CFG_GET_ALL_IDENTIFIER_HOST
-=================================
+HTTP_BAD_SERVER_RESPONSE_RECEIVED_DETAILS
+=========================================
.. code-block:: text
- using identifier: %1, found host: %2
+ detailed information about bad response received from %1:\n%2
-Logged at debug log level 55.
-This debug message is issued when found host identified by the specific
-identifier. The arguments specify the identifier and the detailed
-description of the host found.
+Logged at debug log level 45.
+This debug message is issued when an HTTP client receives malformed response
+from the server. The first argument specifies an URL of the server. The
+second argument provides a response in the textual format. The request is
+truncated by the logger if it is too large to be printed.
-HOSTS_CFG_GET_ALL_SUBNET_ID4
-============================
+HTTP_CLIENT_MT_STARTED
+======================
.. code-block:: text
- get all hosts with reservations for IPv4 subnet %1
+ HttpClient has been started in multi-threaded mode running %1 threads
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts connected to
-the specific DHCPv4 subnet. The argument specifies subnet id.
+Logged at debug log level 40.
+This debug message is issued when a multi-threaded HTTP client instance has
+been created. The argument specifies the maximum number of threads.
-HOSTS_CFG_GET_ALL_SUBNET_ID4_COUNT
-==================================
+HTTP_CLIENT_QUEUE_SIZE_GROWING
+==============================
.. code-block:: text
- using IPv4 subnet %1, found %2 host(s)
+ queue for URL: %1, now has %2 entries and may be growing too quickly
-Logged at debug log level 45.
-This debug message include the details of the host found using the DHCPv4
-subnet id. The arguments specify subnet id and the number of hosts found
-respectively.
+This warning message is issued when the queue of pending requests for the
+given URL appears to be growing more quickly than the requests can be handled.
+It will be emitted periodically as long as the queue size continues to grow.
+This may occur with a surge of client traffic creating a momentary backlog
+which then subsides as the surge subsides. If it happens continually then
+it most likely indicates a deployment configuration that cannot sustain the
+client load.
-HOSTS_CFG_GET_ALL_SUBNET_ID4_HOST
-=================================
+HTTP_CLIENT_REQUEST_AUTHORIZED
+==============================
.. code-block:: text
- using IPv4 subnet %1, found host: %2
+ received HTTP request authorized for '%1'
-Logged at debug log level 55.
-This debug message includes the details of the host found using the DHCPv4
-subnet id. The arguments specify subnet id and found host details respectively.
+This information message is issued when the server receives with a matching
+authentication header. The argument provides the user id.
-HOSTS_CFG_GET_ALL_SUBNET_ID6
-============================
+HTTP_CLIENT_REQUEST_BAD_AUTH_HEADER
+===================================
.. code-block:: text
- get all hosts with reservations for IPv6 subnet %1
+ received HTTP request with malformed authentication header: %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts connected to
-the specific DHCPv6 subnet. The argument specifies subnet id.
+This information message is issued when the server receives a request with
+a malformed authentication header. The argument explains the problem.
-HOSTS_CFG_GET_ALL_SUBNET_ID6_COUNT
+HTTP_CLIENT_REQUEST_NOT_AUTHORIZED
==================================
.. code-block:: text
- using IPv6 subnet %1, found %2 host(s)
+ received HTTP request with not matching authentication header
-Logged at debug log level 45.
-This debug message include the details of the host found using the DHCPv6
-subnet id. The arguments specify subnet id and the number of hosts found
-respectively.
+This information message is issued when the server receives a request with
+authentication header carrying not recognized credential: the user
+provided incorrect user id and/or password.
-HOSTS_CFG_GET_ALL_SUBNET_ID6_HOST
-=================================
+HTTP_CLIENT_REQUEST_RECEIVED
+============================
.. code-block:: text
- using IPv6 subnet %1, found host: %2
+ received HTTP request from %1
-Logged at debug log level 55.
-This debug message includes the details of the host found using the DHCPv6
-subnet id. The arguments specify subnet id and found host details respectively.
+Logged at debug log level 40.
+This debug message is issued when the server finished receiving a HTTP
+request from the remote endpoint. The address of the remote endpoint is
+specified as an argument.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4
+HTTP_CLIENT_REQUEST_RECEIVED_DETAILS
====================================
.. code-block:: text
- get all hosts with reservations for subnet id %1 and IPv4 address %2
+ detailed information about well-formed request received from %1:\n%2
Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts having
-the reservation for the given IPv4 address within the given subnet. The
-first argument specifies subnet identifier. The second argument specifies
-the IPv4 address for which the reservation is to be returned.
+This debug message is issued when the HTTP server receives a well-formed
+request. It includes detailed information about the received request. The
+first argument specifies an address of the remote endpoint which sent the
+request. The second argument provides the request in the textual format.
+The request is truncated by the logger if it is too large to be printed.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_COUNT
-==========================================
+HTTP_CLIENT_REQUEST_SEND
+========================
.. code-block:: text
- using IPv4 subnet %1 and IPv4 address %2, found %3 host(s)
+ sending HTTP request %1 to %2
-Logged at debug log level 45.
-This debug message logs the number of hosts found having the reservation
-for the specified IPv4 address within the specified subnet. The first
-argument specifies the subnet identifier. The second argument specifies
-the reserved IPv4 address. The third argument specifies the number of
-hosts found.
+Logged at debug log level 50.
+This debug message is issued when the client is starting to send a HTTP
+request to a server. The first argument holds basic information
+about the request (HTTP version number and status code). The second
+argument specifies a URL of the server.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_HOST
-=========================================
+HTTP_CLIENT_REQUEST_SEND_DETAILS
+================================
.. code-block:: text
- using IPv4 subnet %1 and IPv4 address %2, found host: %3
+ detailed information about request sent to %1:\n%2
Logged at debug log level 55.
-This debug message is issued when found host having the reservation for
-the specified IPv4 address in the specified subnet. The first argument
-specifies the subnet identifier. The second argument specifies the reserved
-IPv4 address. The third argument specifies host details.
+This debug message is issued right before the client sends an HTTP request
+to the server. It includes detailed information about the request. The
+first argument specifies an URL of the server to which the request is
+being sent. The second argument provides the request in the textual form.
+The request is truncated by the logger if it is too large to be printed.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6
+HTTP_CLIENT_REQUEST_TIMEOUT_OCCURRED
====================================
.. code-block:: text
- get all hosts with reservations for subnet id %1 and IPv6 address %2
+ HTTP request timeout occurred when communicating with %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve all hosts connected to
-the specific subnet and having the specific IPv6 address reserved.
-The arguments specify subnet id and IPv6 address respectively.
+Logged at debug log level 50.
+This debug message is issued when the HTTP request timeout has occurred and
+the server is going to send a response with Http Request timeout status
+code.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_COUNT
+HTTP_COMMAND_MGR_IGNORED_TLS_SETUP_CHANGES
==========================================
.. code-block:: text
- using subnet id %1 and address %2, found %3 host(s)
+ ignore a change in TLS setup of the http control socket
-Logged at debug log level 45.
-This debug message include the details of the host found using the
-subnet id and address. The arguments specify subnet id, address and
-the number of hosts found respectively.
+The warning message is issued when the HTTP/HTTPS control socket was
+reconfigured with a different TLS setup but keeping the address and port.
+These changes are ignored because they can't be applied without opening a new
+socket which will conflict with the existing one.
-HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_HOST
-=========================================
+HTTP_COMMAND_MGR_SERVICE_STARTED
+================================
.. code-block:: text
- using subnet id %1 and address %2, found host: %3
+ started %1 service bound to address %2 port %3
-Logged at debug log level 55.
-This debug message includes the details of the host found using the
-subnet id and address. The arguments specify subnet id, address and
-the number of hosts found respectively.
-found host details respectively.
+This informational message indicates that the server has started
+HTTP/HTTPS service on the specified address and port for receiving
+control commands.
+
+HTTP_CONNECTION_CLOSE_CALLBACK_FAILED
+=====================================
+
+.. code-block:: text
-HOSTS_CFG_GET_ONE_PREFIX
-========================
+ Connection close callback threw an exception
+
+This is an error message emitted when the close connection callback
+registered on the connection failed unexpectedly. This is a programmatic
+error that should be submitted as a bug.
+
+HTTP_CONNECTION_HANDSHAKE_FAILED
+================================
.. code-block:: text
- get one host with reservation for prefix %1/%2
+ TLS handshake with %1 failed with %2
-Logged at debug log level 40.
-This debug message is issued when starting to retrieve a host having a
-reservation for a specified prefix. The arguments specify a prefix and
-prefix length.
+This information message is issued when the TLS handshake failed at the
+server side. The client address and the error message are displayed.
-HOSTS_CFG_GET_ONE_PREFIX_HOST
-=============================
+HTTP_CONNECTION_HANDSHAKE_START
+===============================
.. code-block:: text
- using prefix %1/%2, found host: %3
+ start TLS handshake with %1 with timeout %2
-Logged at debug log level 55.
-This debug message includes the details of the host found using the
-specific prefix/prefix length. The arguments specify prefix, prefix
-length and host details respectively.
+Logged at debug log level 50.
+This debug message is issued when the server starts the TLS handshake
+with the remote endpoint. The first argument specifies the address
+of the remote endpoint. The second argument specifies request timeout in
+seconds.
-HOSTS_CFG_GET_ONE_PREFIX_NULL
-=============================
+HTTP_CONNECTION_SHUTDOWN
+========================
.. code-block:: text
- host not found using prefix %1/%2
+ shutting down HTTP connection from %1
-Logged at debug log level 55.
-This debug message is issued when no host was found for a specified
-prefix and prefix length.
+Logged at debug log level 40.
+This debug message is issued when one of the HTTP connections is shut down.
+The connection can be stopped as a result of an error or after the
+successful message exchange with a client.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4
-====================================
+HTTP_CONNECTION_SHUTDOWN_FAILED
+===============================
.. code-block:: text
- get one host with reservation for subnet id %1 and IPv4 address %2
+ shutting down HTTP connection failed
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host connected to the
-specific subnet and having the specific IPv4 address reserved. The
-arguments specify subnet id and IPv4 address respectively.
+This error message is issued when an error occurred during shutting down
+a HTTP connection with a client.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST
-=========================================
+HTTP_CONNECTION_STOP
+====================
.. code-block:: text
- using subnet id %1 and address %2, found host: %3
+ stopping HTTP connection from %1
-Logged at debug log level 45.
-This debug message logs the details of the host found using the
-subnet id and IPv4 address.
+Logged at debug log level 40.
+This debug message is issued when one of the HTTP connections is stopped.
+The connection can be stopped as a result of an error or after the
+successful message exchange with a client.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL
-=========================================
+HTTP_CONNECTION_STOP_FAILED
+===========================
.. code-block:: text
- host not found using subnet id %1 and address %2
+ stopping HTTP connection failed
-Logged at debug log level 45.
-This debug message is issued when no host was found for the specified
-subnet id and IPv4 address.
+This error message is issued when an error occurred during closing a
+HTTP connection with a client.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6
-====================================
+HTTP_CONNECTION_WATCH_SOCKET_CLEAR_ERROR
+========================================
.. code-block:: text
- get one host with reservation for subnet id %1 and having IPv6 address %2
+ clearing connection watch socket failed: %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host connected to the
-specific subnet and having the specific IPv6 address reserved. The
-arguments specify subnet id and IPv6 address respectively.
+This error message is issued when an error occurred during clearing the
+watch socket associated with a HTTP connection with a client. The error
+is displayed.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_HOST
-=========================================
+HTTP_CONNECTION_WATCH_SOCKET_CLOSE_ERROR
+========================================
.. code-block:: text
- using subnet id %1 and address %2, found host: %3
+ closing connection watch socket failed: %1
-Logged at debug log level 45.
-This debug message logs the details of the host found using the
-subnet id and IPv6 address.
+This error message is issued when an error occurred during closing the
+watch socket associated with a HTTP connection with a client. The error
+is displayed.
-HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_NULL
-=========================================
+HTTP_CONNECTION_WATCH_SOCKET_MARK_READY_ERROR
+=============================================
.. code-block:: text
- host not found using subnet id %1 and address %2
+ marking ready connection watch socket failed: %1
-Logged at debug log level 45.
-This debug message is issued when no host was found using the specified
-subnet if and IPv6 address.
+This error message is issued when an error occurred during marking as ready
+the watch socket associated with a HTTP connection with a client. The error
+is displayed.
-HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER
-======================================
+HTTP_DATA_RECEIVED
+==================
.. code-block:: text
- get one host with %1 reservation for subnet id %2, identified by %3
+ received %1 bytes from %2
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host holding
-IPv4 or IPv6 reservations, which is connected to a specific subnet and
-is identified by a specific unique identifier. The first argument
-identifies if the IPv4 or IPv6 reservation is desired.
+Logged at debug log level 55.
+This debug message is issued when the server receives a chunk of data from
+the remote endpoint. This may include the whole request or only a part
+of the request. The first argument specifies the amount of received data.
+The second argument specifies an address of the remote endpoint which
+produced the data.
-HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST
-===========================================
+HTTP_IDLE_CONNECTION_TIMEOUT_OCCURRED
+=====================================
.. code-block:: text
- using subnet id %1 and identifier %2, found host: %3
+ closing persistent connection with %1 as a result of a timeout
-Logged at debug log level 45.
-This debug message includes the details of a host found using a
-subnet id and specific host identifier.
+Logged at debug log level 50.
+This debug message is issued when the persistent HTTP connection is being
+closed as a result of being idle.
-HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL
-===========================================
+HTTP_PREMATURE_CONNECTION_TIMEOUT_OCCURRED
+==========================================
.. code-block:: text
- host not found using subnet id %1 and identifier %2
+ premature connection timeout occurred: in transaction ? %1, transid: %2, current_transid: %3
-Logged at debug log level 45.
-This debug message is issued when no host was found using the specified
-subnet id and host identifier.
+This warning message is issued when unexpected timeout occurred during the
+transaction. This is proven to occur when the system clock is moved manually
+or as a result of synchronization with a time server. Any ongoing transactions
+will be interrupted. New transactions should be conducted normally.
-HOSTS_CFG_UPDATE_ADD
-====================
+HTTP_REQUEST_RECEIVE_START
+==========================
.. code-block:: text
- add the host for reservations: %1
+ start receiving request from %1 with timeout %2
-Logged at debug log level 40.
-This debug message is issued when a new host (with reservations) is
-added to the server's configuration during an update. The argument
-describes the host and its reservations in detail.
+Logged at debug log level 50.
+This debug message is issued when the server starts receiving new request
+over the established connection. The first argument specifies the address
+of the remote endpoint. The second argument specifies request timeout in
+seconds.
-HOSTS_CFG_UPDATE_DEL4
-=====================
+HTTP_SERVER_RESPONSE_RECEIVED
+=============================
.. code-block:: text
- deleted %1 host(s) for subnet id %2 and identifier %3
+ received HTTP response from %1
Logged at debug log level 40.
-This debug message is issued when IPv4 reservations are deleted for
-the specified subnet and identifier during an update. The first
-argument specifies how many hosts have been deleted. The second
-argument is the subnet identifier. The third argument is the
-identifier.
+This debug message is issued when the client finished receiving an HTTP
+response from the server. The URL of the server is specified as an argument.
-HOSTS_CFG_UPDATE_DEL6
-=====================
+HTTP_SERVER_RESPONSE_RECEIVED_DETAILS
+=====================================
.. code-block:: text
- deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
+ detailed information about well-formed response received from %1:\n%2
-Logged at debug log level 40.
-This debug message is issued when IPv6 reservations are deleted for
-the specified subnet and identifier during an update. The first
-argument specifies how many hosts have been deleted. The second
-argument specifies how many reservations have been deleted. The third
-argument is the subnet identifier. The fourth argument is the
-identifier.
+Logged at debug log level 45.
+This debug message is issued when the HTTP client receives a well-formed
+response from the server. It includes detailed information about the
+received response. The first argument specifies a URL of the server which
+sent the response. The second argument provides the response in the textual
+format. The response is truncated by the logger if it is too large to
+be printed.
-HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_ADDRESS4
-===========================================
+HTTP_SERVER_RESPONSE_SEND
+=========================
.. code-block:: text
- trying alternate sources for host using subnet id %1 and address %2
+ sending HTTP response %1 to %2
Logged at debug log level 40.
-This debug message is issued when the Host Manager doesn't find the
-host connected to the specific subnet and having the reservation for
-the specific IPv4 address, and it is starting to search for this host
-in alternate host data sources.
+This debug message is issued when the server is starting to send a HTTP
+response to a remote endpoint. The first argument holds basic information
+about the response (HTTP version number and status code). The second
+argument specifies an address of the remote endpoint.
-HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER
-=============================================
+***
+KEY
+***
+
+KEY_LOOKUP_DISABLED
+===================
.. code-block:: text
- get one host with IPv4 reservation for subnet id %1, identified by %2
+ hooks library lookup for a key: GSS-TSIG is not enabled for the current DNS server.
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host holding
-IPv4 reservation, which is connected to a specific subnet and
-is identified by a specific unique identifier.
+Logged at debug log level 40.
+This debug message is issued when the lookup for a GSS-TSIG key was performed
+for a DNS server where GSS-TSIG is not enabled.
-HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_HOST
-==================================================
+KEY_LOOKUP_FOUND
+================
.. code-block:: text
- using subnet id %1 and identifier %2, found in %3 host: %4
+ hooks library lookup for a key: return GSS-TSIG key '%1'.
-Logged at debug log level 45.
-This debug message includes the details of a host returned by an
-alternate hosts data source using a subnet id and specific host
-identifier.
+Logged at debug log level 40.
+This debug message is issued when the lookup for a GSS-TSIG key returned
+an usable key for protecting the DNS update. The key name is displayed.
-HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_NULL
-==================================================
+KEY_LOOKUP_NONE
+===============
.. code-block:: text
- host not found using subnet id %1 and identifier %2
+ hooks library lookup for a key: found no usable key.
-Logged at debug log level 45.
-This debug message is issued when no host was found using the specified
-subnet id and host identifier.
+Logged at debug log level 40.
+This debug message is issued when the lookup for a GSS-TSIG key failed
+to find an usable key.
-HOSTS_MGR_ALTERNATE_GET6_PREFIX
-===============================
+KEY_PROCESSING_FAILED
+=====================
.. code-block:: text
- trying alternate sources for host using prefix %1/%2
+ The GSS-TKEY processing for server %1 failed because of an error: %2
-Logged at debug log level 40.
-This debug message is issued when the Host Manager doesn't find the
-host connected to the specific subnet and having the reservation for
-the specified prefix, and it is starting to search for this host in
-alternate host data sources.
+This error message is issued when the key processing for a specific server has
+failed. The first argument specifies the server identifier and the second
+argument gives more information about the error.
-HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_ADDRESS6
-===========================================
+KEY_PROCESSING_FAILED_UNSPECIFIED_ERROR
+=======================================
.. code-block:: text
- trying alternate sources for host using subnet id %1 and IPv6 address %2
+ The GSS-TKEY processing for server %1 failed because of an unspecified error
-Logged at debug log level 40.
-This debug message is issued when the Host Manager doesn't find the
-host connected to the specific subnet and having the reservation for
-the specified IPv6 address, and it is starting to search for this
-host in alternate host data sources.
+This error message is issued when the key processing for a specific server has
+failed. The first argument specifies the server identifier.
-HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER
-=============================================
+*****
+LEASE
+*****
+
+LEASE_CMDS_ADD4
+===============
.. code-block:: text
- get one host with IPv6 reservation for subnet id %1, identified by %2
+ lease4-add command successful (address: %1)
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host holding
-IPv4 reservation, which is connected to a specific subnet and
-is identified by a specific unique identifier.
+Logged at debug log level 20.
+The lease4-add command has been successful. Lease IPv4 address
+is logged.
-HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_HOST
-==================================================
+LEASE_CMDS_ADD4_CONFLICT
+========================
.. code-block:: text
- using subnet id %1 and identifier %2, found in %3 host: %4
+ lease4-add command failed due to conflict (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message includes the details of a host returned by an
-alternate host data source using a subnet id and specific host
-identifier.
+The received lease4-add is well-formed and contains valid parameters but the
+lease could not be created because it is in conflict with the server state
+or configuration. The reason for a conflict is logged in the message.
-HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_NULL
-==================================================
+LEASE_CMDS_ADD4_FAILED
+======================
.. code-block:: text
- host not found using subnet id %1 and identifier %2
+ lease4-add command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message is issued when no host was found using the specified
-subnet id and host identifier.
+The lease4-add command has failed. Both the reason as well as the
+parameters passed are logged.
-HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS4
-==============================================
+LEASE_CMDS_ADD6
+===============
.. code-block:: text
- trying alternate sources for hosts using subnet id %1 and address %2
+ lease6-add command successful (address: %1)
-Logged at debug log level 40.
-This debug message is issued when the Host Manager is starting to search
-for hosts in alternate host data sources by subnet ID and IPv4 address.
+Logged at debug log level 20.
+The lease6-add command has been successful. Lease IPv6 address
+is logged.
-HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS6
-==============================================
+LEASE_CMDS_ADD6_CONFLICT
+========================
.. code-block:: text
- trying alternate sources for hosts using subnet id %1 and address %2
+ lease6-add command failed due to conflict (parameters: %1, reason: %2)
-Logged at debug log level 40.
-This debug message is issued when the Host Manager is starting to search
-for hosts in alternate host data sources by subnet ID and IPv6 address.
+The received lease6-add is well-formed and contains valid parameters but the
+lease could not be created because it is in conflict with the server state
+or configuration. The reason for a conflict is logged in the message.
-****
-HOST
-****
+LEASE_CMDS_ADD6_FAILED
+======================
-HOST_CACHE_ADD
-==============
+.. code-block:: text
+
+ lease6-add command failed (parameters: %1, reason: %2)
+
+The lease6-add command has failed. Both the reason as well as the
+parameters passed are logged.
+
+LEASE_CMDS_BULK_APPLY6
+======================
.. code-block:: text
- add host: %1
+ lease6-bulk-apply command successful (applied addresses count: %1)
-Logged at debug log level 45.
-This debug message logs the details of the added host cache entry.
+Logged at debug log level 20.
+The lease6-bulk-apply command has been successful. The number of applied
+addresses is logged.
-HOST_CACHE_ADD_DUPLICATE
-========================
+LEASE_CMDS_BULK_APPLY6_FAILED
+=============================
.. code-block:: text
- duplicate host: %1
+ lease6-bulk-apply command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-The add operation failed because the entry conflicts with an already
-existing one. The details of the add operation argument are logged.
+The lease6-bulk-apply command has failed. Both the reason as well
+as the parameters passed are logged.
-HOST_CACHE_COMMAND_CLEAR
-========================
+LEASE_CMDS_DEINIT_OK
+====================
.. code-block:: text
- cache-clear command successful
+ unloading Lease Commands hooks library successful
-The cache-clear command has been successful.
+This info message indicates that the Lease Commands hooks library has been
+removed successfully.
-HOST_CACHE_COMMAND_CLEAR_FAILED
-===============================
+LEASE_CMDS_DEL4
+===============
.. code-block:: text
- cache-clear command failed (reason: %1)
+ lease4-del command successful (address: %1)
-The cache-clear command has failed. The reason is logged.
+Logged at debug log level 20.
+The attempt to delete an IPv4 lease (lease4-del command) has been successful.
+Lease IPv4 address is logged.
-HOST_CACHE_COMMAND_FLUSH
-========================
+LEASE_CMDS_DEL4_FAILED
+======================
.. code-block:: text
- cache-flush command successful
+ lease4-del command failed (parameters: %1, reason: %2)
-The cache-flush command has been successful.
+The attempt to delete an IPv4 lease (lease4-del command) has failed. Both the
+reason as well as the parameters passed are logged.
-HOST_CACHE_COMMAND_FLUSH_FAILED
-===============================
+LEASE_CMDS_DEL6
+===============
.. code-block:: text
- cache-flush command failed (parameters: %1, reason: %2)
+ lease4-del command successful (address: %1)
-The cache-flush command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 20.
+The attempt to delete an IPv4 lease (lease4-del command) has been successful.
+Lease IPv6 address is logged.
-HOST_CACHE_COMMAND_GET
+LEASE_CMDS_DEL6_FAILED
======================
.. code-block:: text
- cache-get command successful (returned: %1)
+ lease6-del command failed (parameters: %1, reason: %2)
-The cache-get command has been successful. The number of returned entries
-is logged.
+The attempt to delete an IPv6 lease (lease4-del command) has failed. Both the
+reason as well as the parameters passed are logged.
-HOST_CACHE_COMMAND_GET_BY_ID
-============================
+LEASE_CMDS_GET4_FAILED
+======================
.. code-block:: text
- cache-get-by-id command successful (returned: %1)
+ lease4-get command failed (parameters: %1, reason: %2)
-The cache-get-by-id command has been successful. The number of returned entries
-is logged.
+The lease4-get command has failed. Both the reason as well as the
+parameters passed are logged.
-HOST_CACHE_COMMAND_GET_BY_ID_FAILED
-===================================
+LEASE_CMDS_GET6_FAILED
+======================
.. code-block:: text
- cache-get-by-id command failed (reason: %1)
+ lease6-get command failed (parameters: %1, reason: %2)
-The cache-get-by-id command has failed. The reason is logged.
+The lease4-get command has failed. Both the reason as well as the
+parameters passed are logged.
-HOST_CACHE_COMMAND_GET_FAILED
-=============================
+LEASE_CMDS_INIT_OK
+==================
.. code-block:: text
- cache-get command failed (reason: %1)
+ loading Lease Commands hooks library successful
-The cache-get command has failed. The reason is logged.
+This info message indicates that the Lease Commands hooks library has been
+loaded successfully. Enjoy!
-HOST_CACHE_COMMAND_INSERT
-=========================
+LEASE_CMDS_RESEND_DDNS4
+=======================
.. code-block:: text
- cache-insert command successful (inserted: %1, overwritten: %2)
+ lease4-resend-ddns command successful: %1
-The cache-insert command has been successful. The number of inserted entries
-and the number of entries overwritten by more recent entries are logged.
+A request to update DNS for the requested IPv4 lease has been
+successfully queued for transmission to kea-dhcp-ddns.
-HOST_CACHE_COMMAND_INSERT_FAILED
-================================
+LEASE_CMDS_RESEND_DDNS4_FAILED
+==============================
.. code-block:: text
- cache-insert command failed (parameters: %1, reason: %2)
+ lease4-resend-ddns command failed: %1
-The cache-insert command has failed. Both the reason as well as the
-parameters passed are logged.
+A request to update DNS for the requested IPv4 lease has failed. The
+reason for the failure is logged.
-HOST_CACHE_COMMAND_LOAD
+LEASE_CMDS_RESEND_DDNS6
=======================
.. code-block:: text
- cache-load command successful (loaded: %1, overwritten: %2)
+ lease6-resend-ddns command successful: %1
-The cache-load command has been successful. The number of loaded entries
-and the number of entries overwritten by more recent entries are logged.
+A request to update DNS for the requested IPv6 lease has been
+successfully queued for transmission to kea-dhcp-ddns.
-HOST_CACHE_COMMAND_LOAD_FAILED
+LEASE_CMDS_RESEND_DDNS6_FAILED
==============================
.. code-block:: text
- cache-load command failed (parameters: %1, reason: %2)
+ lease6-resend-ddns command failed: %1
-The cache-load command has failed. Both the reason as well as the
-parameters passed are logged.
+A request to update DNS for the requested IPv6 lease has failed. The
+reason for the failure is logged.
-HOST_CACHE_COMMAND_REMOVE
-=========================
+LEASE_CMDS_UPDATE4
+==================
.. code-block:: text
- cache-remove command successful (parameters: %1)
+ lease4-update command successful (address: %1)
-The cache-remove command has been successful. Parameters of the host
-deleted are logged.
+Logged at debug log level 20.
+The lease4-update command has been successful. Lease IPv4 address
+is logged.
-HOST_CACHE_COMMAND_REMOVE_FAILED
-================================
+LEASE_CMDS_UPDATE4_CONFLICT
+===========================
.. code-block:: text
- cache-remove command failed (parameters: %1, reason: %2)
+ lease4-update command failed due to conflict (parameters: %1, reason: %2)
-The cache-remove command has failed. Both the reason as well as the
-parameters passed are logged.
+The received lease4-update is well-formed and contains valid parameters
+but the lease could not be created because it is in conflict with the
+server state or configuration. The reason for a conflict is logged in
+the message.
-HOST_CACHE_COMMAND_SIZE
-=======================
+LEASE_CMDS_UPDATE4_FAILED
+=========================
.. code-block:: text
- cache-clear command successful: %1
+ lease4-update command failed (parameters: %1, reason: %2)
-The cache-size command has been successful and returned the number of
-entries in the host cache.
+The lease4-update command has failed. Both the reason as well as the
+parameters passed are logged.
-HOST_CACHE_COMMAND_SIZE_FAILED
-==============================
+LEASE_CMDS_UPDATE6
+==================
.. code-block:: text
- cache-size command failed (reason: %1)
+ lease6-update command successful (address: %1)
-The cache-size command has failed. The reason is logged.
+Logged at debug log level 20.
+The lease6-update command has been successful. Lease IPv6 address
+is logged.
-HOST_CACHE_COMMAND_WRITE
-========================
+LEASE_CMDS_UPDATE6_CONFLICT
+===========================
.. code-block:: text
- cache-write command successful (dumped: %1)
+ lease6-update command failed due to conflict (parameters: %1, reason: %2)
-The cache-write command has been successful. The number of dumped entries
-is logged.
+The received lease6-update is well-formed and contains valid parameters
+but the lease could not be created because it is in conflict with the
+server state or configuration. The reason for a conflict is logged in
+the message.
-HOST_CACHE_COMMAND_WRITE_FAILED
-===============================
+LEASE_CMDS_UPDATE6_FAILED
+=========================
.. code-block:: text
- cache-write command failed (parameters: %1, reason: %2)
+ lease6-add command failed (parameters: %1, reason: %2)
-The cache-write command has failed. Both the reason as well as the
+The lease6-update command has failed. Both the reason as well as the
parameters passed are logged.
-HOST_CACHE_CONFIGURATION_FAILED
-===============================
+LEASE_CMDS_WIPE4
+================
.. code-block:: text
- failed to configure Host Cache hooks library: %1
+ lease4-wipe command successful (parameters: %1)
-This error message is issued when there is an error configuring the Host
-Cache hooks library. The argument provides the detailed error message.
+The lease4-wipe command has been successful. Parameters of the command
+are logged.
-HOST_CACHE_DEINIT_OK
-====================
+LEASE_CMDS_WIPE4_DEPRECATED
+===========================
.. code-block:: text
- unloading Host Cache hooks library successful
+ lease4-wipe command is deprecated and it will be removed in the future.
-This informational message indicates that the Host Cache hooks library
-has been unloaded successfully.
+The lease4-wipe command is deprecated and it will be removed in the future.
-HOST_CACHE_DEL_SUBNET_ID_ADDRESS4
-=================================
+LEASE_CMDS_WIPE4_FAILED
+=======================
.. code-block:: text
- using subnet id %1 and address %2, delete host: %3
+ lease4-wipe command failed (parameters: %1, reason: %2)
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry deleted using
-the subnet id and IPv4 address.
+The lease4-wipe command has failed. Both the reason as well as the
+parameters passed are logged.
-HOST_CACHE_DEL_SUBNET_ID_ADDRESS6
-=================================
+LEASE_CMDS_WIPE6
+================
.. code-block:: text
- using subnet id %1 and address %2, delete host: %3
+ lease6-wipe command successful (parameters: %1)
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry deleted using
-the subnet id and IPv6 address.
+The lease6-wipe command has been successful. Parameters of the command
+are logged.
-HOST_CACHE_DEL_SUBNET_ID_IDENTIFIER4
-====================================
+LEASE_CMDS_WIPE6_DEPRECATED
+===========================
.. code-block:: text
- using subnet id %1 and identifier %2, delete host: %3
+ lease6-wipe command is deprecated and it will be removed in the future.
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry deleted using a
-subnet id and specific host identifier.
+The lease6-wipe command is deprecated and it will be removed in the future.
-HOST_CACHE_DEL_SUBNET_ID_IDENTIFIER6
-====================================
+LEASE_QUERY_LOAD_FAILED
+=======================
.. code-block:: text
- using subnet id %1 and identifier %2, delete host: %3
+ Lease Query hooks library failed to load: %1
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry deleted using a
-subnet id and specific host identifier.
+This error message indicates that an error occurred attempting to
+load the Lease Query hooks library. The argument details the error.
-HOST_CACHE_GET_ONE_PREFIX
-=========================
+LEASE_QUERY_LOAD_OK
+===================
.. code-block:: text
- get one host with reservation for prefix %1/%2
+ Lease Query hooks library loaded successfully.
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host cache entry
-having a reservation for a specified prefix. The arguments specify a prefix
-and prefix length.
+This info message indicates that the Lease Query hooks library has
+been loaded successfully.
-HOST_CACHE_GET_ONE_PREFIX_HOST
-==============================
+*****
+LEGAL
+*****
+
+LEGAL_LOG_COMMAND_NO_LEGAL_STORE
+================================
.. code-block:: text
- using prefix %1/%2, found host: %3
+ LegalStore instance is null
-Logged at debug log level 45.
-This debug message includes the details of the host cache entry found
-using the specific prefix/prefix length. The arguments specify prefix,
-prefix length and host details respectively.
+This is an error message issued when the Legal Log library attempted to
+write a control command entry to the legal store and the store instance
+has not been created. This is a programmatic error and should not occur.
-HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS4
-=====================================
+LEGAL_LOG_COMMAND_WRITE_ERROR
+=============================
.. code-block:: text
- get one host with reservation for subnet id %1 and IPv4 address %2
+ Could not write command entry to the legal store: %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host cache entry
-connected to the specific subnet and having the specific IPv4 address reserved.
-The arguments specify subnet id and IPv4 address respectively.
+This is an error message issued when the Legal Log library attempted to
+write a control command entry to the legal store and the write failed.
+The message content should provide an detailed explanation.
+error.
-HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS4_HOST
-==========================================
+LEGAL_LOG_DB_OPEN_CONNECTION_WITH_RETRY_FAILED
+==============================================
.. code-block:: text
- using subnet id %1 and address %2, found host: %3
+ Failed to connect to database: %1 with error: %2
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry found using the
-subnet id and IPv4 address.
+This is an informational message issued when the the server failed to connect to
+the store database. The operation started a retry to connect procedure.
+The database access string with password redacted is logged, along with the
+error and details for the reconnect procedure.
-HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS6
-=====================================
+LEGAL_LOG_INVALID_ACCESS
+========================
.. code-block:: text
- get one host with reservation for subnet id %1 and including IPv6 address %2
+ invalid database access string: %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host cache entry
-connected to the specific subnet and having the specific IPv6 address
-reserved. The arguments specify subnet id and IPv6 address respectively.
+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.
-HOST_CACHE_GET_ONE_SUBNET_ID_ADDRESS6_HOST
-==========================================
+LEGAL_LOG_LEASE4_NO_LEGAL_STORE
+===============================
.. code-block:: text
- using subnet id %1 and address %2, found host: %3
+ LegalStore instance is null
-Logged at debug log level 45.
-This debug message logs the details of the host cache entry found using
-the subnet id and IPv6 address.
+This is an error message issued when the Legal Log library attempted to
+write a IPv4 lease entry to the legal store and the store instance
+has not been created. This is a programmatic error and should not occur.
-HOST_CACHE_GET_ONE_SUBNET_ID_IDENTIFIER
-=======================================
+LEGAL_LOG_LEASE4_WRITE_ERROR
+============================
.. code-block:: text
- get one host with %1 reservation for subnet id %2, identified by %3
+ Could not write to the legal store: %1
-Logged at debug log level 45.
-This debug message is issued when starting to retrieve a host cache entry
-holding IPv4 or IPv6 reservations, which is connected to a specific subnet
-and is identified by a specific unique identifier. The first argument
-identifies if the IPv4 or IPv6 reservation is desired.
+This is an error message issued when the Legal Log library attempted to
+write a IPv4 lease entry to the legal store and the write failed.
+The message content should include the physical store name and the nature of the
+error.
-HOST_CACHE_GET_ONE_SUBNET_ID_IDENTIFIER_HOST
-============================================
+LEGAL_LOG_LEASE6_NO_LEGAL_STORE
+===============================
.. code-block:: text
- using subnet id %1 and identifier %2, found host: %3
+ LegalStore instance is null
-Logged at debug log level 45.
-This debug message includes the details of a host cache entry found using a
-subnet id and specific host identifier.
+This is an error message issued when the Legal Log library attempted to
+write a IPv6 lease entry to the legal store and the store instance has not been
+created. This is a programmatic error and should not occur.
-HOST_CMDS_DEINIT_OK
-===================
+LEGAL_LOG_LEASE6_WRITE_ERROR
+============================
.. code-block:: text
- unloading Host Commands hooks library successful
+ Could not write to the legal store: %1
-This info message indicates that the Host Commands hooks library has been
-removed successfully.
+This is an error message issued when the Legal Log library attempted to
+write a IPv6 lease entry to the legal store and the write failed.
+The message content should include the physical store name and the nature of the
+error.
-HOST_CMDS_INIT_FAILED
-=====================
+LEGAL_LOG_LOAD_ERROR
+====================
.. code-block:: text
- loading Host Commands hooks library failed: %1
+ LEGAL LOGGING DISABLED! An error occurred loading the library: %1
-This error message indicates an error during loading the Host Commands
-hooks library. The details of the error are provided as argument of
-the log message.
+This is an error message issued when the DHCP Legal Log library could not
+be loaded. The exact cause should be explained in the log message. No existing
+stores will be altered, nor any legal logging entries emitted.
-HOST_CMDS_INIT_OK
-=================
+LEGAL_LOG_MYSQL_COMMIT
+======================
.. code-block:: text
- loading Host Commands hooks library successful
+ committing to MySQL database
-This info message indicates that the Host Commands hooks library has been
-loaded successfully. Enjoy!
+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.
-HOST_CMDS_RESERV_ADD
-====================
+LEGAL_LOG_MYSQL_DB
+==================
.. code-block:: text
- reservation-add command called (parameters: %1)
+ opening MySQL log database: %1
-The reservation-add command has been called. Parameters passed are logged.
+This informational message is logged when a legal log hook library is
+about to open a MySQL log database. The parameters of the
+connection including database name and username needed to access it
+(but not the password if any) are logged.
-HOST_CMDS_RESERV_ADD_FAILED
-===========================
+LEGAL_LOG_MYSQL_DB_RECONNECT_ATTEMPT_FAILED
+===========================================
.. code-block:: text
- reservation-add command failed (parameters: %1, reason: %2)
+ database reconnect failed: %1
-The reservation-add command has failed. Both the reason as well as the
-parameters passed are logged.
+An error message issued when an attempt to reconnect has failed.
-HOST_CMDS_RESERV_ADD_SUCCESS
-============================
+LEGAL_LOG_MYSQL_DB_RECONNECT_ATTEMPT_SCHEDULE
+=============================================
.. code-block:: text
- reservation-add command success (parameters: %1)
+ scheduling attempt %1 of %2 in %3 milliseconds
-The reservation-add command has been successful. Parameters passed are logged.
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-HOST_CMDS_RESERV_DEL
-====================
+LEGAL_LOG_MYSQL_DB_RECONNECT_FAILED
+===================================
.. code-block:: text
- reservation-del command called (parameters: %1)
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-The reservation-del command has been called. Parameters passed are logged.
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-HOST_CMDS_RESERV_DEL_FAILED
+LEGAL_LOG_MYSQL_FATAL_ERROR
===========================
.. code-block:: text
- reservation-del command failed (parameters: %1, reason: %2)
+ Unrecoverable MySQL error occurred: %1 for <%2>, reason: %3 (error code: %4).
-The reservation-del command has failed. Both the reason as well as the
-parameters passed are logged.
+An error message indicating that communication with the MySQL database server
+has been lost. When this occurs the server exits immediately with a non-zero
+exit code. This is most likely due to a network issue.
-HOST_CMDS_RESERV_DEL_SUCCESS
-============================
+LEGAL_LOG_MYSQL_GET_VERSION
+===========================
.. code-block:: text
- reservation-del command success (parameters: %1)
+ obtaining schema version information
-The reservation-del command has been successful. Parameters passed are logged.
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the MySQL database.
-HOST_CMDS_RESERV_GET
-====================
+LEGAL_LOG_MYSQL_INSERT_LOG
+==========================
.. code-block:: text
- reservation-get command called (parameters: %1)
+ Adding a log entry to the database: %1
-The reservation-get command has been called. Parameters passed are logged.
+Logged at debug log level 50.
+An informational message logged when a log entry is inserted.
-HOST_CMDS_RESERV_GET_ALL
-========================
+LEGAL_LOG_MYSQL_NO_TLS
+======================
.. code-block:: text
- reservation-get-all command called (parameters: %1)
+ TLS was required but is not used
-The reservation-get-all command has been called. Parameters passed are logged.
+This error message is issued when TLS for the connection was required but
+TLS is not used.
-HOST_CMDS_RESERV_GET_ALL_FAILED
-===============================
+LEGAL_LOG_MYSQL_ROLLBACK
+========================
.. code-block:: text
- reservation-get-all command failed (parameters: %1, reason: %2)
+ rolling back MySQL database
-The reservation-get-all command has failed. Both the reason as well as the
-parameters passed are logged.
+The code has issued a rollback call. All outstanding transaction will
+be rolled back and not committed to the database.
-HOST_CMDS_RESERV_GET_ALL_SUCCESS
-================================
+LEGAL_LOG_MYSQL_START_TRANSACTION
+=================================
.. code-block:: text
- reservation-get-all command success (parameters: %1)
+ starting new MySQL transaction
-The reservation-get-all command has been successful. Parameters passed are logged.
+A debug message issued when a new MySQL transaction is being started.
+This message is typically not issued when inserting data into a
+single table because the server doesn't explicitly start
+transactions in this case. This message is issued when data is
+inserted into multiple tables with multiple INSERT statements
+and there may be a need to rollback the whole transaction if
+any of these INSERT statements fail.
-HOST_CMDS_RESERV_GET_BY_ADDRESS
-===============================
+LEGAL_LOG_MYSQL_TLS_CIPHER
+==========================
.. code-block:: text
- reservation-get-by-address command called (parameters: %1)
+ TLS cipher: %1
-The reservation-get-by-address command has been called. Parameters passed are logged.
+Logged at debug log level 50.
+A debug message issued when a new MySQL connected is created with TLS.
+The TLS cipher name is logged.
-HOST_CMDS_RESERV_GET_BY_ADDRESS_FAILED
-======================================
+LEGAL_LOG_PGSQL_COMMIT
+======================
.. code-block:: text
- reservation-get-by-address command failed (parameters: %1, reason: %2)
+ committing to PostgreSQL database
-The reservation-get-by-address command has failed. Both the reason as well as the
-parameters passed are logged.
+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.
-HOST_CMDS_RESERV_GET_BY_ADDRESS_SUCCESS
-=======================================
+LEGAL_LOG_PGSQL_DB
+==================
.. code-block:: text
- reservation-get-by-address command success (parameters: %1)
+ opening PostgreSQL log database: %1
-The reservation-get-by-address command has been successful. Parameters passed are logged.
+This informational message is logged when a legal log hook library is
+about to open a PostgreSQL log database. The parameters of the
+connection including database name and username needed to access it
+(but not the password if any) are logged.
-HOST_CMDS_RESERV_GET_BY_HOSTNAME
-================================
+LEGAL_LOG_PGSQL_DB_RECONNECT_ATTEMPT_FAILED
+===========================================
.. code-block:: text
- reservation-get-by-hostname command called (parameters: %1)
+ database reconnect failed: %1
-The reservation-get-by-hostname command has been called. Parameters passed are logged.
+An error message issued when an attempt to reconnect has failed.
-HOST_CMDS_RESERV_GET_BY_HOSTNAME_FAILED
-=======================================
+LEGAL_LOG_PGSQL_DB_RECONNECT_ATTEMPT_SCHEDULE
+=============================================
.. code-block:: text
- reservation-get-by-hostname command failed (parameters: %1, reason: %2)
+ scheduling attempt %1 of %2 in %3 milliseconds
-The reservation-get-by-hostname command has failed. Both the reason as well as the
-parameters passed are logged.
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-HOST_CMDS_RESERV_GET_BY_HOSTNAME_SUCCESS
-========================================
+LEGAL_LOG_PGSQL_DB_RECONNECT_FAILED
+===================================
.. code-block:: text
- reservation-get-by-hostname command success (parameters: %1)
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-The reservation-get-by-hostname command has been successful. Parameters passed are logged.
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-HOST_CMDS_RESERV_GET_BY_ID
-==========================
+LEGAL_LOG_PGSQL_DEALLOC_ERROR
+=============================
.. code-block:: text
- reservation-get-by-id command called (parameters: %1)
+ An error occurred deallocating SQL statements while closing the PostgreSQL log database: %1
-The reservation-get-by-id command has been called. Parameters passed are logged.
+This is an error message issued when a legal log hook library 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.
-HOST_CMDS_RESERV_GET_BY_ID_FAILED
-=================================
+LEGAL_LOG_PGSQL_FATAL_ERROR
+===========================
.. code-block:: text
- reservation-get-by-id command failed (parameters: %1, reason: %2)
+ Unrecoverable PostgreSQL error occurred: Statement: <%1>, reason: %2 (error code: %3).
-The reservation-get-by-id command has failed. Both the reason as well as the
-parameters passed are logged.
+An error message indicating that communication with the MySQL database server
+has been lost. When this occurs the server exits immediately with a non-zero
+exit code. This is most likely due to a network issue.
-HOST_CMDS_RESERV_GET_BY_ID_SUCCESS
-==================================
+LEGAL_LOG_PGSQL_GET_VERSION
+===========================
.. code-block:: text
- reservation-get-by-id command success (parameters: %1)
+ obtaining schema version information
-The reservation-get-by-id command has been successful. Parameters passed are logged.
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the PostgreSQL database.
-HOST_CMDS_RESERV_GET_FAILED
-===========================
+LEGAL_LOG_PGSQL_INSERT_LOG
+==========================
.. code-block:: text
- reservation-get command failed (parameters: %1, reason: %2)
+ Adding a log entry to the database: %1
-The reservation-add command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 50.
+An informational message logged when a log entry is inserted.
-HOST_CMDS_RESERV_GET_PAGE
-=========================
+LEGAL_LOG_PGSQL_NO_TLS_SUPPORT
+==============================
.. code-block:: text
- reservation-get-page command called (parameters: %1)
+ Attempt to configure TLS (unsupported for PostgreSQL): %1
-The reservation-get-page command has been called. Parameters passed are logged.
+This error message is printed when TLS support was required in the Kea
+configuration: Kea was built with this feature disabled for PostgreSQL.
+The parameters of the connection are logged.
-HOST_CMDS_RESERV_GET_PAGE_FAILED
-================================
+LEGAL_LOG_PGSQL_ROLLBACK
+========================
.. code-block:: text
- reservation-get-page command failed (parameters: %1, reason: %2)
+ rolling back PostgreSQL database
-The reservation-get-page command has failed. Both the reason as well as the
-parameters passed are logged.
+The code has issued a rollback call. All outstanding transaction will
+be rolled back and not committed to the database.
-HOST_CMDS_RESERV_GET_PAGE_SUCCESS
+LEGAL_LOG_PGSQL_START_TRANSACTION
=================================
.. code-block:: text
- reservation-get-page command success (parameters: %1)
+ starting a new PostgreSQL transaction
-The reservation-get-page command has been successful. Parameters passed are logged.
+A debug message issued when a new PostgreSQL transaction is being started.
+This message is typically not issued when inserting data into a
+single table because the server doesn't explicitly start
+transactions in this case. This message is issued when data is
+inserted into multiple tables with multiple INSERT statements
+and there may be a need to rollback the whole transaction if
+any of these INSERT statements fail.
-HOST_CMDS_RESERV_GET_SUCCESS
-============================
+LEGAL_LOG_PGSQL_TLS_SUPPORT
+===========================
.. code-block:: text
- reservation-get command success (parameters: %1)
+ Attempt to configure TLS: %1
-The reservation-get command has been successful. Parameters passed are logged.
+This informational message is printed when TLS support was required in
+the Kea configuration: The TLS support in PostgreSQL will be initialized but
+its configuration is fully managed outside the C API.
+The parameters of the connection are logged.
-HOST_CMDS_RESERV_UPDATE
-=======================
+LEGAL_LOG_STORE_CLOSED
+======================
.. code-block:: text
- reservation-update command called (parameters: %1)
+ Legal store closed: %1
-The reservation-update command has been called. Parameters passed are logged.
+This is an informational message issued when the Legal Log library
+has successfully closed the legal store.
-HOST_CMDS_RESERV_UPDATE_FAILED
-==============================
+LEGAL_LOG_STORE_CLOSE_ERROR
+===========================
.. code-block:: text
- reservation-update command failed (parameters: %1, reason: %2)
-
-The reservation-update command has failed. Both the reason as well as the
-parameters passed are logged.
+ An error occurred closing the store: %1, error: %2
-*****
-HTTPS
-*****
+This is an error message issued when the legal log library experienced an
+error attempting to close a legal store. This is highly unlikely to occur and
+should not affect the store content or subsequent legal store operations.
-HTTPS_REQUEST_RECEIVE_START
-===========================
+LEGAL_LOG_STORE_OPENED
+======================
.. code-block:: text
- start receiving request from %1
+ Legal store opened: %1
-Logged at debug log level 50.
-This debug message is issued when the server starts receiving new request
-over the established connection. The argument specifies the address
-of the remote endpoint.
+This is an informational message issued when the Legal Log library
+has successfully opened the legal store.
-****
-HTTP
-****
+***
+LFC
+***
-HTTP_BAD_CLIENT_REQUEST_RECEIVED
-================================
+LFC_FAIL_PID_CREATE
+===================
.. code-block:: text
- bad request received from %1: %2
+ : %1
-Logged at debug log level 40.
-This debug message is issued when an HTTP client sends malformed request to
-the server. This includes HTTP requests using unexpected content types,
-including malformed JSON etc. The first argument specifies an address of
-the remote endpoint which sent the request. The second argument provides
-a detailed error message.
+This message is issued if LFC detected a failure when trying
+to create the PID file. It includes a more specific error string.
-HTTP_BAD_CLIENT_REQUEST_RECEIVED_DETAILS
-========================================
+LFC_FAIL_PID_DEL
+================
.. code-block:: text
- detailed information about bad request received from %1:\n%2
+ : %1
-Logged at debug log level 45.
-This debug message is issued when an HTTP client sends malformed request to
-the server. It includes detailed information about the received request
-rejected by the server. The first argument specifies an address of
-the remote endpoint which sent the request. The second argument provides
-a request in the textual format. The request is truncated by the logger
-if it is too large to be printed.
+This message is issued if LFC detected a failure when trying
+to delete the PID file. It includes a more specific error string.
-HTTP_BAD_SERVER_RESPONSE_RECEIVED
-=================================
+LFC_FAIL_PROCESS
+================
.. code-block:: text
- bad response received when communicating with %1: %2
+ : %1
-Logged at debug log level 40.
-This debug message is issued when an HTTP client fails to receive a response
-from the server or when this response is malformed. The first argument
-specifies the server URL. The second argument provides a detailed error
-message.
+This message is issued if LFC detected a failure when trying
+to process the files. It includes a more specific error string.
-HTTP_BAD_SERVER_RESPONSE_RECEIVED_DETAILS
-=========================================
+LFC_FAIL_ROTATE
+===============
.. code-block:: text
- detailed information about bad response received from %1:\n%2
+ : %1
-Logged at debug log level 45.
-This debug message is issued when an HTTP client receives malformed response
-from the server. The first argument specifies an URL of the server. The
-second argument provides a response in the textual format. The request is
-truncated by the logger if it is too large to be printed.
+This message is issued if LFC detected a failure when trying
+to rotate the files. It includes a more specific error string.
-HTTP_CLIENT_MT_STARTED
-======================
+LFC_PROCESSING
+==============
.. code-block:: text
- HttpClient has been started in multi-threaded mode running %1 threads
+ Previous file: %1, copy file: %2
-Logged at debug log level 40.
-This debug message is issued when a multi-threaded HTTP client instance has
-been created. The argument specifies the maximum number of threads.
+This message is issued just before LFC starts processing the
+lease files.
-HTTP_CLIENT_QUEUE_SIZE_GROWING
-==============================
+LFC_READ_STATS
+==============
.. code-block:: text
- queue for URL: %1, now has %2 entries and may be growing too quickly
+ Leases: %1, attempts: %2, errors: %3.
-This warning message is issued when the queue of pending requests for the
-given URL appears to be growing more quickly than the requests can be handled.
-It will be emitted periodically as long as the queue size continues to grow.
-This may occur with a surge of client traffic creating a momentary backlog
-which then subsides as the surge subsides. If it happens continually then
-it most likely indicates a deployment configuration that cannot sustain the
-client load.
+This message prints out the number of leases that were read, the
+number of attempts to read leases and the number of errors
+encountered while reading.
-HTTP_CLIENT_REQUEST_AUTHORIZED
-==============================
+LFC_ROTATING
+============
.. code-block:: text
- received HTTP request authorized for '%1'
+ LFC rotating files
-This information message is issued when the server receives with a matching
-authentication header. The argument provides the user id.
+This message is issued just before LFC starts rotating the
+lease files - removing the old and replacing them with the new.
-HTTP_CLIENT_REQUEST_BAD_AUTH_HEADER
-===================================
+LFC_RUNNING
+===========
.. code-block:: text
- received HTTP request with malformed authentication header: %1
+ LFC instance already running
-This information message is issued when the server receives a request with
-a malformed authentication header. The argument explains the problem.
+This message is issued if LFC detects that a previous copy of LFC
+may still be running via the PID check.
-HTTP_CLIENT_REQUEST_NOT_AUTHORIZED
-==================================
+LFC_START
+=========
.. code-block:: text
- received HTTP request with not matching authentication header
+ Starting lease file cleanup
-This information message is issued when the server receives a request with
-authentication header carrying not recognized credential: the user
-provided incorrect user id and/or password.
+This message is issued as the LFC process starts.
-HTTP_CLIENT_REQUEST_RECEIVED
-============================
+LFC_TERMINATE
+=============
.. code-block:: text
- received HTTP request from %1
+ LFC finished processing
-Logged at debug log level 40.
-This debug message is issued when the server finished receiving a HTTP
-request from the remote endpoint. The address of the remote endpoint is
-specified as an argument.
+This message is issued when the LFC process completes. It does not
+indicate that the process was successful only that it has finished.
-HTTP_CLIENT_REQUEST_RECEIVED_DETAILS
-====================================
+******
+LIMITS
+******
+
+LIMITS_CONFIGURATION_LEASE_BACKEND_NOT_AVAILABLE
+================================================
.. code-block:: text
- detailed information about well-formed request received from %1:\n%2
+ Lease backend not available. Could not check JSON support in the database. Continuing without checking...
-Logged at debug log level 45.
-This debug message is issued when the HTTP server receives a well-formed
-request. It includes detailed information about the received request. The
-first argument specifies an address of the remote endpoint which sent the
-request. The second argument provides the request in the textual format.
-The request is truncated by the logger if it is too large to be printed.
+Warning message logged to notify that limits might not work if the recovering database does not have JSON support.
-HTTP_CLIENT_REQUEST_SEND
-========================
+LIMITS_CONFIGURATION_LEASE_BACKEND_SHOULD_HAVE_BEEN_AVAILABLE
+=============================================================
.. code-block:: text
- sending HTTP request %1 to %2
+ Lease backend not available when configuration shows it should have been. This is likely a programmatic error. Continuing...
-Logged at debug log level 50.
-This debug message is issued when the client is starting to send a HTTP
-request to a server. The first argument holds basic information
-about the request (HTTP version number and status code). The second
-argument specifies a URL of the server.
+Error message logged to notify about an unexpected situation where the lease backend was expected to be available, but it was not. Runtime errors might occur.
-HTTP_CLIENT_REQUEST_SEND_DETAILS
-================================
+LIMITS_CONFIGURED_ADDRESS_LIMIT_BY_CLIENT_CLASS
+===============================================
.. code-block:: text
- detailed information about request sent to %1:\n%2
+ New lease limit of %1 addresses for client class %2 has been configured.
-Logged at debug log level 55.
-This debug message is issued right before the client sends an HTTP request
-to the server. It includes detailed information about the request. The
-first argument specifies an URL of the server to which the request is
-being sent. The second argument provides the request in the textual form.
-The request is truncated by the logger if it is too large to be printed.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of an address limit per client class
-HTTP_CLIENT_REQUEST_TIMEOUT_OCCURRED
-====================================
+LIMITS_CONFIGURED_ADDRESS_LIMIT_BY_SUBNET
+=========================================
.. code-block:: text
- HTTP request timeout occurred when communicating with %1
+ New lease limit of %1 addresses for subnet with ID %2 has been configured.
-Logged at debug log level 50.
-This debug message is issued when the HTTP request timeout has occurred and
-the server is going to send a response with Http Request timeout status
-code.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of an address limit per subnet
-HTTP_COMMAND_MGR_IGNORED_TLS_SETUP_CHANGES
-==========================================
+LIMITS_CONFIGURED_PREFIX_LIMIT_BY_CLIENT_CLASS
+==============================================
.. code-block:: text
- ignore a change in TLS setup of the http control socket
+ New lease limit of %1 prefixes for client class %2 has been configured.
-The warning message is issued when the HTTP/HTTPS control socket was
-reconfigured with a different TLS setup but keeping the address and port.
-These changes are ignored because they can't be applied without opening a new
-socket which will conflict with the existing one.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of a prefix limit per client class
-HTTP_COMMAND_MGR_SERVICE_STARTED
-================================
+LIMITS_CONFIGURED_PREFIX_LIMIT_BY_SUBNET
+========================================
.. code-block:: text
- started %1 service bound to address %2 port %3
+ New lease limit of %1 prefixes for subnet with ID %2 has been configured.
-This informational message indicates that the server has started
-HTTP/HTTPS service on the specified address and port for receiving
-control commands.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of a prefix limit per subnet
-HTTP_CONNECTION_CLOSE_CALLBACK_FAILED
-=====================================
+LIMITS_CONFIGURED_RATE_LIMIT_BY_CLIENT_CLASS
+============================================
.. code-block:: text
- Connection close callback threw an exception
+ New rate limit of %1 for client class %2 has been configured.
-This is an error message emitted when the close connection callback
-registered on the connection failed unexpectedly. This is a programmatic
-error that should be submitted as a bug.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of a rate limit per client class
-HTTP_CONNECTION_HANDSHAKE_FAILED
-================================
+LIMITS_CONFIGURED_RATE_LIMIT_BY_SUBNET
+======================================
.. code-block:: text
- TLS handshake with %1 failed with %2
+ New rate limit of %1 for subnet with ID %2 has been configured.
-This information message is issued when the TLS handshake failed at the
-server side. The client address and the error message are displayed.
+Logged at debug log level 40.
+Debug message logged to notify about the successful configuration of a rate limit per subnet
-HTTP_CONNECTION_HANDSHAKE_START
-===============================
+LIMITS_LEASE_LIMIT_EXCEEDED
+===========================
.. code-block:: text
- start TLS handshake with %1 with timeout %2
+ Lease was not allocated due to exceeding %1.
-Logged at debug log level 50.
-This debug message is issued when the server starts the TLS handshake
-with the remote endpoint. The first argument specifies the address
-of the remote endpoint. The second argument specifies request timeout in
-seconds.
+Logged at debug log level 40.
+Debug message logged to indicate that the current number of leased addresses or
+prefixes for a client class or a subnet is exceeding the limit.
-HTTP_CONNECTION_SHUTDOWN
-========================
+LIMITS_LEASE_WITHIN_LIMITS
+==========================
.. code-block:: text
- shutting down HTTP connection from %1
+ Lease with address %1 is within limits.
Logged at debug log level 40.
-This debug message is issued when one of the HTTP connections is shut down.
-The connection can be stopped as a result of an error or after the
-successful message exchange with a client.
+Debug message logged to indicate that the current number of leased addresses or
+prefixes for a client class or a subnet is exceeding the limit.
-HTTP_CONNECTION_SHUTDOWN_FAILED
-===============================
+LIMITS_PACKET_WIIH_SUBNET_ID_RATE_NO_SUBNET
+===========================================
.. code-block:: text
- shutting down HTTP connection failed
+ Packet is not being rate limited due to no subnet specified.
-This error message is issued when an error occurred during shutting down
-a HTTP connection with a client.
+Logged at debug log level 55.
+Debug message logged to indicate that the current packet's subnet rate limit, if any, is not being
+checked due to the subnet not being set in the callout handle. This can happen e.g. if the subnet
+had been deleted after it was selected for the currently processed packet.
-HTTP_CONNECTION_STOP
-====================
+LIMITS_PACKET_WITH_CLIENT_CLASSES_RATE_LIMIT_DROPPED
+====================================================
.. code-block:: text
- stopping HTTP connection from %1
+ Packet assigned to client classes %1 is being dropped for exceeding the rate limit of %2 for client class %3.
Logged at debug log level 40.
-This debug message is issued when one of the HTTP connections is stopped.
-The connection can be stopped as a result of an error or after the
-successful message exchange with a client.
+Debug message logged to indicate that the current packet has exceeded one of the rate limits
+configured under at least one client class
-HTTP_CONNECTION_STOP_FAILED
-===========================
+LIMITS_PACKET_WITH_CLIENT_CLASSES_RATE_LIMIT_HONORED
+====================================================
.. code-block:: text
- stopping HTTP connection failed
+ Packet assigned to client classes %1 is being honored.
-This error message is issued when an error occurred during closing a
-HTTP connection with a client.
+Logged at debug log level 55.
+Debug message logged to indicate that the current packet has not exceeded any of the rate limits
+configured under any client class
-HTTP_CONNECTION_WATCH_SOCKET_CLEAR_ERROR
-========================================
+LIMITS_PACKET_WITH_SUBNET_ID_RATE_LIMIT_DROPPED
+===============================================
.. code-block:: text
- clearing connection watch socket failed: %1
+ Packet assigned to subnet with ID %1 is being dropped for exceeding the rate limit of %2.
-This error message is issued when an error occurred during clearing the
-watch socket associated with a HTTP connection with a client. The error
-is displayed.
+Logged at debug log level 40.
+Debug message logged to indicate that the current packet has exceeded the limit configured under
+the assigned subnet ID, if any is configured
-HTTP_CONNECTION_WATCH_SOCKET_CLOSE_ERROR
-========================================
+*******
+LOGIMPL
+*******
+
+LOGIMPL_ABOVE_MAX_DEBUG
+=======================
.. code-block:: text
- closing connection watch socket failed: %1
+ debug level of %1 is too high and will be set to the maximum of %2
-This error message is issued when an error occurred during closing the
-watch socket associated with a HTTP connection with a client. The error
-is displayed.
+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.
-HTTP_CONNECTION_WATCH_SOCKET_MARK_READY_ERROR
-=============================================
+LOGIMPL_BAD_DEBUG_STRING
+========================
.. code-block:: text
- marking ready connection watch socket failed: %1
+ debug string '%1' has invalid format
-This error message is issued when an error occurred during marking as ready
-the watch socket associated with a HTTP connection with a client. The error
-is displayed.
+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.
-HTTP_DATA_RECEIVED
-==================
+***
+LOG
+***
+
+LOG_BAD_DESTINATION
+===================
.. code-block:: text
- received %1 bytes from %2
+ unrecognized log destination: %1
-Logged at debug log level 55.
-This debug message is issued when the server receives a chunk of data from
-the remote endpoint. This may include the whole request or only a part
-of the request. The first argument specifies the amount of received data.
-The second argument specifies an address of the remote endpoint which
-produced the data.
+This error message is printed when a logger destination value was given that was not recognized. The
+destination should be one of "console", "file", or "syslog".
-HTTP_IDLE_CONNECTION_TIMEOUT_OCCURRED
-=====================================
+LOG_BAD_SEVERITY
+================
.. code-block:: text
- closing persistent connection with %1 as a result of a timeout
+ unrecognized log severity: %1
-Logged at debug log level 50.
-This debug message is issued when the persistent HTTP connection is being
-closed as a result of being idle.
+This error message is printed when a logger severity value was given that was not recognized. The severity
+should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE".
-HTTP_PREMATURE_CONNECTION_TIMEOUT_OCCURRED
-==========================================
+LOG_BAD_STREAM
+==============
.. code-block:: text
- premature connection timeout occurred: in transaction ? %1, transid: %2, current_transid: %3
+ bad log console output stream: %1
-This warning message is issued when unexpected timeout occurred during the
-transaction. This is proven to occur when the system clock is moved manually
-or as a result of synchronization with a time server. Any ongoing transactions
-will be interrupted. New transactions should be conducted normally.
+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 recognized.
+Allowed values are "stdout" and "stderr".
-HTTP_REQUEST_RECEIVE_START
-==========================
+LOG_DUPLICATE_MESSAGE_ID
+========================
.. code-block:: text
- start receiving request from %1 with timeout %2
+ duplicate message ID (%1) in compiled code
-Logged at debug log level 50.
-This debug message is issued when the server starts receiving new request
-over the established connection. The first argument specifies the address
-of the remote endpoint. The second argument specifies request timeout in
-seconds.
+During start-up, Kea detected that the given message identification
+had been defined multiple times in the Kea code. This indicates a
+programming error; please submit a bug report.
-HTTP_SERVER_RESPONSE_RECEIVED
-=============================
+LOG_DUPLICATE_NAMESPACE
+=======================
.. code-block:: text
- received HTTP response from %1
+ line %1: duplicate $NAMESPACE directive found
-Logged at debug log level 40.
-This debug message is issued when the client finished receiving an HTTP
-response from the server. The URL of the server is specified as an argument.
+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.
-HTTP_SERVER_RESPONSE_RECEIVED_DETAILS
-=====================================
+LOG_INPUT_OPEN_FAIL
+===================
.. code-block:: text
- detailed information about well-formed response received from %1:\n%2
+ unable to open message file %1 for input: %2
-Logged at debug log level 45.
-This debug message is issued when the HTTP client receives a well-formed
-response from the server. It includes detailed information about the
-received response. The first argument specifies a URL of the server which
-sent the response. The second argument provides the response in the textual
-format. The response is truncated by the logger if it is too large to
-be printed.
+The program was not able to open the specified input message file for
+the reason given.
-HTTP_SERVER_RESPONSE_SEND
-=========================
+LOG_INVALID_MESSAGE_ID
+======================
.. code-block:: text
- sending HTTP response %1 to %2
-
-Logged at debug log level 40.
-This debug message is issued when the server is starting to send a HTTP
-response to a remote endpoint. The first argument holds basic information
-about the response (HTTP version number and status code). The second
-argument specifies an address of the remote endpoint.
+ line %1: invalid message identification '%2'
-***
-KEY
-***
+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.
-KEY_LOOKUP_DISABLED
-===================
+LOG_NAMESPACE_EXTRA_ARGS
+========================
.. code-block:: text
- hooks library lookup for a key: GSS-TSIG is not enabled for the current DNS server.
+ line %1: $NAMESPACE directive has too many arguments
-Logged at debug log level 40.
-This debug message is issued when the lookup for a GSS-TSIG key was performed
-for a DNS server where GSS-TSIG is not enabled.
+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.
-KEY_LOOKUP_FOUND
-================
+LOG_NAMESPACE_INVALID_ARG
+=========================
.. code-block:: text
- hooks library lookup for a key: return GSS-TSIG key '%1'.
+ line %1: $NAMESPACE directive has an invalid argument ('%2')
-Logged at debug log level 40.
-This debug message is issued when the lookup for a GSS-TSIG key returned
-an usable key for protecting the DNS update. The key name is displayed.
+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.
-KEY_LOOKUP_NONE
-===============
+LOG_NAMESPACE_NO_ARGS
+=====================
.. code-block:: text
- hooks library lookup for a key: found no usable key.
+ line %1: no arguments were given to the $NAMESPACE directive
-Logged at debug log level 40.
-This debug message is issued when the lookup for a GSS-TSIG key failed
-to find an usable key.
+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.
-KEY_PROCESSING_FAILED
-=====================
+LOG_NO_MESSAGE_ID
+=================
.. code-block:: text
- The GSS-TKEY processing for server %1 failed because of an error: %2
+ line %1: message definition line found without a message ID
-This error message is issued when the key processing for a specific server has
-failed. The first argument specifies the server identifier and the second
-argument gives more information about the error.
+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.
-KEY_PROCESSING_FAILED_UNSPECIFIED_ERROR
-=======================================
+LOG_NO_MESSAGE_TEXT
+===================
.. code-block:: text
- The GSS-TKEY processing for server %1 failed because of an unspecified error
-
-This error message is issued when the key processing for a specific server has
-failed. The first argument specifies the server identifier.
+ line %1: line found containing a message ID ('%2') and no text
-*****
-LEASE
-*****
+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.
-LEASE_CMDS_ADD4
-===============
+LOG_NO_SUCH_MESSAGE
+===================
.. code-block:: text
- lease4-add command successful (address: %1)
+ could not replace message text for '%1': no such message
-Logged at debug log level 20.
-The lease4-add command has been successful. Lease IPv4 address
-is logged.
+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 are several reasons why this message may appear:
+- The message ID has been misspelled 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 Kea software
+and the later version no longer generates that message.
+Whatever the reason, there is no impact on the operation of Kea.
-LEASE_CMDS_ADD4_CONFLICT
-========================
+LOG_OPEN_OUTPUT_FAIL
+====================
.. code-block:: text
- lease4-add command failed due to conflict (parameters: %1, reason: %2)
+ unable to open %1 for output: %2
-The received lease4-add is well-formed and contains valid parameters but the
-lease could not be created because it is in conflict with the server state
-or configuration. The reason for a conflict is logged in the message.
+Originating within the logging code, the program was not able to open
+the specified output file for the reason given.
-LEASE_CMDS_ADD4_FAILED
-======================
+LOG_PREFIX_EXTRA_ARGS
+=====================
.. code-block:: text
- lease4-add command failed (parameters: %1, reason: %2)
+ line %1: $PREFIX directive has too many arguments
-The lease4-add command has failed. Both the reason as well as the
-parameters passed are logged.
+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 Kea.
-LEASE_CMDS_ADD6
-===============
+LOG_PREFIX_INVALID_ARG
+======================
.. code-block:: text
- lease6-add command successful (address: %1)
+ line %1: $PREFIX directive has an invalid argument ('%2')
-Logged at debug log level 20.
-The lease6-add command has been successful. Lease IPv6 address
-is logged.
+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 Kea.
-LEASE_CMDS_ADD6_CONFLICT
-========================
+LOG_READING_LOCAL_FILE
+======================
.. code-block:: text
- lease6-add command failed due to conflict (parameters: %1, reason: %2)
+ reading local message file %1
-The received lease6-add is well-formed and contains valid parameters but the
-lease could not be created because it is in conflict with the server state
-or configuration. The reason for a conflict is logged in the message.
+This is an informational message output by Kea 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.)
-LEASE_CMDS_ADD6_FAILED
-======================
+LOG_READ_ERROR
+==============
.. code-block:: text
- lease6-add command failed (parameters: %1, reason: %2)
+ error reading from message file %1: %2
-The lease6-add command has failed. Both the reason as well as the
-parameters passed are logged.
+The specified error was encountered reading from the named message file.
-LEASE_CMDS_BULK_APPLY6
-======================
+LOG_UNRECOGNIZED_DIRECTIVE
+==========================
.. code-block:: text
- lease6-bulk-apply command successful (applied addresses count: %1)
+ line %1: unrecognized directive '%2'
-Logged at debug log level 20.
-The lease6-bulk-apply command has been successful. The number of applied
-addresses is logged.
+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 recognized.
-LEASE_CMDS_BULK_APPLY6_FAILED
-=============================
+**
+MT
+**
+
+MT_TCP_LISTENER_MGR_STARTED
+===========================
.. code-block:: text
- lease6-bulk-apply command failed (parameters: %1, reason: %2)
+ MtTcpListenerMgr started with %1 threads, listening on %2:%3, use TLS: %4
-The lease6-bulk-apply command has failed. Both the reason as well
-as the parameters passed are logged.
+Logged at debug log level 40.
+This debug messages is issued when an MtTcpListenerMgr has been started to
+accept connections. Arguments detail the number of threads that the listener
+is using, the address and port at which it is listening, and if TLS is used
+or not.
-LEASE_CMDS_DEINIT_OK
-====================
+MT_TCP_LISTENER_MGR_STOPPED
+===========================
.. code-block:: text
- unloading Lease Commands hooks library successful
+ MtTcpListenerMgr for %1:%2 stopped.
-This info message indicates that the Lease Commands hooks library has been
-removed successfully.
+Logged at debug log level 40.
+This debug messages is issued when the MtTcpListenerMgr, listening
+at the given address and port, has completed shutdown.
-LEASE_CMDS_DEL4
-===============
+MT_TCP_LISTENER_MGR_STOPPING
+============================
.. code-block:: text
- lease4-del command successful (address: %1)
+ Stopping MtTcpListenerMgr for %1:%2
-Logged at debug log level 20.
-The attempt to delete an IPv4 lease (lease4-del command) has been successful.
-Lease IPv4 address is logged.
+Logged at debug log level 40.
+This debug messages is issued when the MtTcpListenerMgr, listening
+at the given address and port, has begun to shutdown.
-LEASE_CMDS_DEL4_FAILED
-======================
+*****
+MYSQL
+*****
+
+MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4
+======================================
.. code-block:: text
- lease4-del command failed (parameters: %1, reason: %2)
+ create or update option pool start: %1 pool end: %2
-The attempt to delete an IPv4 lease (lease4-del command) has failed. Both the
-reason as well as the parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by pool
-LEASE_CMDS_DEL6
-===============
+MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6
+======================================
.. code-block:: text
- lease4-del command successful (address: %1)
+ create or update option pool start: %1 pool end: %2
-Logged at debug log level 20.
-The attempt to delete an IPv4 lease (lease4-del command) has been successful.
-Lease IPv6 address is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by pool
-LEASE_CMDS_DEL6_FAILED
-======================
+MYSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6
+========================================
.. code-block:: text
- lease6-del command failed (parameters: %1, reason: %2)
+ create or update option prefix: %1 prefix len: %2
-The attempt to delete an IPv6 lease (lease4-del command) has failed. Both the
-reason as well as the parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by prefix
-LEASE_CMDS_GET4_FAILED
-======================
+MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4
+===========================================
.. code-block:: text
- lease4-get command failed (parameters: %1, reason: %2)
+ create or update option by subnet id: %1
-The lease4-get command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by subnet id
-LEASE_CMDS_GET6_FAILED
-======================
+MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6
+===========================================
.. code-block:: text
- lease6-get command failed (parameters: %1, reason: %2)
+ create or update option by subnet id: %1
-The lease4-get command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by subnet id
-LEASE_CMDS_INIT_OK
-==================
+MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS4
+====================================
.. code-block:: text
- loading Lease Commands hooks library successful
+ create or update client class: %1
-This info message indicates that the Lease Commands hooks library has been
-loaded successfully. Enjoy!
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update client class
-LEASE_CMDS_RESEND_DDNS4
-=======================
+MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS6
+====================================
.. code-block:: text
- lease4-resend-ddns command successful: %1
+ create or update client class: %1
-A request to update DNS for the requested IPv4 lease has been
-successfully queued for transmission to kea-dhcp-ddns.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update client class
-LEASE_CMDS_RESEND_DDNS4_FAILED
-==============================
+MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4
+========================================
.. code-block:: text
- lease4-resend-ddns command failed: %1
+ create or update global parameter: %1
-A request to update DNS for the requested IPv4 lease has failed. The
-reason for the failure is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update global parameter
-LEASE_CMDS_RESEND_DDNS6
-=======================
+MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6
+========================================
.. code-block:: text
- lease6-resend-ddns command successful: %1
+ create or update global parameter: %1
-A request to update DNS for the requested IPv6 lease has been
-successfully queued for transmission to kea-dhcp-ddns.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update global parameter
-LEASE_CMDS_RESEND_DDNS6_FAILED
+MYSQL_CB_CREATE_UPDATE_OPTION4
==============================
.. code-block:: text
- lease6-resend-ddns command failed: %1
+ create or update option
-A request to update DNS for the requested IPv6 lease has failed. The
-reason for the failure is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option
-LEASE_CMDS_UPDATE4
-==================
+MYSQL_CB_CREATE_UPDATE_OPTION6
+==============================
.. code-block:: text
- lease4-update command successful (address: %1)
+ create or update option
-Logged at debug log level 20.
-The lease4-update command has been successful. Lease IPv4 address
-is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option
-LEASE_CMDS_UPDATE4_CONFLICT
-===========================
+MYSQL_CB_CREATE_UPDATE_OPTION_DEF4
+==================================
.. code-block:: text
- lease4-update command failed due to conflict (parameters: %1, reason: %2)
+ create or update option definition: %1 code: %2
-The received lease4-update is well-formed and contains valid parameters
-but the lease could not be created because it is in conflict with the
-server state or configuration. The reason for a conflict is logged in
-the message.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option definition
-LEASE_CMDS_UPDATE4_FAILED
-=========================
+MYSQL_CB_CREATE_UPDATE_OPTION_DEF6
+==================================
.. code-block:: text
- lease4-update command failed (parameters: %1, reason: %2)
+ create or update option definition: %1 code: %2
-The lease4-update command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option definition
-LEASE_CMDS_UPDATE6
-==================
+MYSQL_CB_CREATE_UPDATE_SERVER4
+==============================
.. code-block:: text
- lease6-update command successful (address: %1)
+ create or update server: %1
-Logged at debug log level 20.
-The lease6-update command has been successful. Lease IPv6 address
-is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update a DHCPv4
+server information.
-LEASE_CMDS_UPDATE6_CONFLICT
-===========================
+MYSQL_CB_CREATE_UPDATE_SERVER6
+==============================
.. code-block:: text
- lease6-update command failed due to conflict (parameters: %1, reason: %2)
+ create or update server: %1
-The received lease6-update is well-formed and contains valid parameters
-but the lease could not be created because it is in conflict with the
-server state or configuration. The reason for a conflict is logged in
-the message.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update a DHCPv6
+server information.
-LEASE_CMDS_UPDATE6_FAILED
-=========================
+MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK4
+======================================
.. code-block:: text
- lease6-add command failed (parameters: %1, reason: %2)
+ create or update shared network: %1
-The lease6-update command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network
-LEASE_CMDS_WIPE4
-================
+MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK6
+======================================
.. code-block:: text
- lease4-wipe command successful (parameters: %1)
+ create or update shared network: %1
-The lease4-wipe command has been successful. Parameters of the command
-are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network
-LEASE_CMDS_WIPE4_DEPRECATED
-===========================
+MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4
+=============================================
.. code-block:: text
- lease4-wipe command is deprecated and it will be removed in the future.
+ create or update shared network: %1 option
-The lease4-wipe command is deprecated and it will be removed in the future.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network option
-LEASE_CMDS_WIPE4_FAILED
-=======================
+MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6
+=============================================
.. code-block:: text
- lease4-wipe command failed (parameters: %1, reason: %2)
+ create or update shared network: %1 option
-The lease4-wipe command has failed. Both the reason as well as the
-parameters passed are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network option
-LEASE_CMDS_WIPE6
-================
+MYSQL_CB_CREATE_UPDATE_SUBNET4
+==============================
.. code-block:: text
- lease6-wipe command successful (parameters: %1)
+ create or update subnet: %1
-The lease6-wipe command has been successful. Parameters of the command
-are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update subnet
-LEASE_CMDS_WIPE6_DEPRECATED
-===========================
+MYSQL_CB_CREATE_UPDATE_SUBNET6
+==============================
.. code-block:: text
- lease6-wipe command is deprecated and it will be removed in the future.
+ create or update subnet: %1
-The lease6-wipe command is deprecated and it will be removed in the future.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update subnet
-LEASE_QUERY_LOAD_FAILED
-=======================
+MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4
+===================================
.. code-block:: text
- Lease Query hooks library failed to load: %1
+ delete all client classes
-This error message indicates that an error occurred attempting to
-load the Lease Query hooks library. The argument details the error.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all client classes
-LEASE_QUERY_LOAD_OK
-===================
+MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT
+==========================================
.. code-block:: text
- Lease Query hooks library loaded successfully.
-
-This info message indicates that the Lease Query hooks library has
-been loaded successfully.
+ deleted: %1 entries
-*****
-LEGAL
-*****
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all client classes
-LEGAL_LOG_COMMAND_NO_LEGAL_STORE
-================================
+MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6
+===================================
.. code-block:: text
- LegalStore instance is null
+ delete all client classes
-This is an error message issued when the Legal Log library attempted to
-write a control command entry to the legal store and the store instance
-has not been created. This is a programmatic error and should not occur.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all client classes
-LEGAL_LOG_COMMAND_WRITE_ERROR
-=============================
+MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT
+==========================================
.. code-block:: text
- Could not write command entry to the legal store: %1
+ deleted: %1 entries
-This is an error message issued when the Legal Log library attempted to
-write a control command entry to the legal store and the write failed.
-The message content should provide an detailed explanation.
-error.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all client classes
-LEGAL_LOG_DB_OPEN_CONNECTION_WITH_RETRY_FAILED
-==============================================
+MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4
+======================================
.. code-block:: text
- Failed to connect to database: %1 with error: %2
+ delete all global parameters
-This is an informational message issued when the the server failed to connect to
-the store database. The operation started a retry to connect procedure.
-The database access string with password redacted is logged, along with the
-error and details for the reconnect procedure.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all global parameters
-LEGAL_LOG_INVALID_ACCESS
-========================
+MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT
+=============================================
.. code-block:: text
- invalid database access string: %1
+ deleted: %1 entries
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all global parameters
-LEGAL_LOG_LEASE4_NO_LEGAL_STORE
-===============================
+MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6
+======================================
.. code-block:: text
- LegalStore instance is null
+ delete all global parameters
-This is an error message issued when the Legal Log library attempted to
-write a IPv4 lease entry to the legal store and the store instance
-has not been created. This is a programmatic error and should not occur.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all global parameters
-LEGAL_LOG_LEASE4_WRITE_ERROR
-============================
+MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT
+=============================================
.. code-block:: text
- Could not write to the legal store: %1
+ deleted: %1 entries
-This is an error message issued when the Legal Log library attempted to
-write a IPv4 lease entry to the legal store and the write failed.
-The message content should include the physical store name and the nature of the
-error.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all global parameters
-LEGAL_LOG_LEASE6_NO_LEGAL_STORE
-===============================
+MYSQL_CB_DELETE_ALL_OPTION_DEFS4
+================================
.. code-block:: text
- LegalStore instance is null
+ delete all option definitions
-This is an error message issued when the Legal Log library attempted to
-write a IPv6 lease entry to the legal store and the store instance has not been
-created. This is a programmatic error and should not occur.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all option definitions
-LEGAL_LOG_LEASE6_WRITE_ERROR
-============================
+MYSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT
+=======================================
.. code-block:: text
- Could not write to the legal store: %1
+ deleted: %1 entries
-This is an error message issued when the Legal Log library attempted to
-write a IPv6 lease entry to the legal store and the write failed.
-The message content should include the physical store name and the nature of the
-error.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all option definitions
-LEGAL_LOG_LOAD_ERROR
-====================
+MYSQL_CB_DELETE_ALL_OPTION_DEFS6
+================================
.. code-block:: text
- LEGAL LOGGING DISABLED! An error occurred loading the library: %1
+ delete all option definitions
-This is an error message issued when the DHCP Legal Log library could not
-be loaded. The exact cause should be explained in the log message. No existing
-stores will be altered, nor any legal logging entries emitted.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all option definitions
-LEGAL_LOG_MYSQL_COMMIT
-======================
+MYSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT
+=======================================
.. code-block:: text
- committing to MySQL database
+ deleted: %1 entries
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all option definitions
-LEGAL_LOG_MYSQL_DB
-==================
+MYSQL_CB_DELETE_ALL_SERVERS4
+============================
.. code-block:: text
- opening MySQL log database: %1
+ delete all DHCPv4 servers
-This informational message is logged when a legal log hook library is
-about to open a MySQL log database. The parameters of the
-connection including database name and username needed to access it
-(but not the password if any) are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all servers.
-LEGAL_LOG_MYSQL_DB_RECONNECT_ATTEMPT_FAILED
-===========================================
+MYSQL_CB_DELETE_ALL_SERVERS4_RESULT
+===================================
.. code-block:: text
- database reconnect failed: %1
+ deleted: %1 entries
-An error message issued when an attempt to reconnect has failed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all servers.
-LEGAL_LOG_MYSQL_DB_RECONNECT_ATTEMPT_SCHEDULE
-=============================================
+MYSQL_CB_DELETE_ALL_SERVERS6
+============================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ delete all DHCPv6 servers
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all servers.
-LEGAL_LOG_MYSQL_DB_RECONNECT_FAILED
+MYSQL_CB_DELETE_ALL_SERVERS6_RESULT
===================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ deleted: %1 entries
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all servers.
-LEGAL_LOG_MYSQL_FATAL_ERROR
-===========================
+MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4
+====================================
.. code-block:: text
- Unrecoverable MySQL error occurred: %1 for <%2>, reason: %3 (error code: %4).
+ delete all shared networks
-An error message indicating that communication with the MySQL database server
-has been lost. When this occurs the server exits immediately with a non-zero
-exit code. This is most likely due to a network issue.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all shared networks
-LEGAL_LOG_MYSQL_GET_VERSION
-===========================
+MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT
+===========================================
.. code-block:: text
- obtaining schema version information
+ deleted: %1 entries
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the MySQL database.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all shared networks
-LEGAL_LOG_MYSQL_INSERT_LOG
-==========================
+MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6
+====================================
.. code-block:: text
- Adding a log entry to the database: %1
+ delete all shared networks
-Logged at debug log level 50.
-An informational message logged when a log entry is inserted.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all shared networks
-LEGAL_LOG_MYSQL_NO_TLS
-======================
+MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT
+===========================================
.. code-block:: text
- TLS was required but is not used
+ deleted: %1 entries
-This error message is issued when TLS for the connection was required but
-TLS is not used.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all shared networks
-LEGAL_LOG_MYSQL_ROLLBACK
-========================
+MYSQL_CB_DELETE_ALL_SUBNETS4
+============================
.. code-block:: text
- rolling back MySQL database
+ delete all subnets
-The code has issued a rollback call. All outstanding transaction will
-be rolled back and not committed to the database.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all subnets
-LEGAL_LOG_MYSQL_START_TRANSACTION
-=================================
+MYSQL_CB_DELETE_ALL_SUBNETS4_RESULT
+===================================
.. code-block:: text
- starting new MySQL transaction
+ deleted: %1 entries
-A debug message issued when a new MySQL transaction is being started.
-This message is typically not issued when inserting data into a
-single table because the server doesn't explicitly start
-transactions in this case. This message is issued when data is
-inserted into multiple tables with multiple INSERT statements
-and there may be a need to rollback the whole transaction if
-any of these INSERT statements fail.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all subnets
-LEGAL_LOG_MYSQL_TLS_CIPHER
-==========================
+MYSQL_CB_DELETE_ALL_SUBNETS6
+============================
.. code-block:: text
- TLS cipher: %1
+ delete all subnets
-Logged at debug log level 50.
-A debug message issued when a new MySQL connected is created with TLS.
-The TLS cipher name is logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all subnets
-LEGAL_LOG_PGSQL_COMMIT
-======================
+MYSQL_CB_DELETE_ALL_SUBNETS6_RESULT
+===================================
.. code-block:: text
- committing to PostgreSQL database
+ deleted: %1 entries
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all subnets
-LEGAL_LOG_PGSQL_DB
-==================
+MYSQL_CB_DELETE_BY_POOL_OPTION4
+===============================
.. code-block:: text
- opening PostgreSQL log database: %1
+ delete pool start: %1 pool end: %2 option code: %3 space: %4
-This informational message is logged when a legal log hook library is
-about to open a PostgreSQL log database. The parameters of the
-connection including database name and username needed to access it
-(but not the password if any) are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by pool
-LEGAL_LOG_PGSQL_DB_RECONNECT_ATTEMPT_FAILED
-===========================================
+MYSQL_CB_DELETE_BY_POOL_OPTION4_RESULT
+======================================
.. code-block:: text
- database reconnect failed: %1
+ deleted: %1 entries
-An error message issued when an attempt to reconnect has failed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by pool
-LEGAL_LOG_PGSQL_DB_RECONNECT_ATTEMPT_SCHEDULE
-=============================================
+MYSQL_CB_DELETE_BY_POOL_OPTION6
+===============================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ delete pool start: %1 pool end: %2 option code: %3 space: %4
-An info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by pool
-LEGAL_LOG_PGSQL_DB_RECONNECT_FAILED
-===================================
+MYSQL_CB_DELETE_BY_POOL_OPTION6_RESULT
+======================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ deleted: %1 entries
-An error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by pool
-LEGAL_LOG_PGSQL_DEALLOC_ERROR
-=============================
+MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6
+======================================
.. code-block:: text
- An error occurred deallocating SQL statements while closing the PostgreSQL log database: %1
+ delete prefix: %1 prefix len: %2 option code: %3 space: %4
-This is an error message issued when a legal log hook library 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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by prefix
-LEGAL_LOG_PGSQL_FATAL_ERROR
-===========================
+MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT
+=============================================
.. code-block:: text
- Unrecoverable PostgreSQL error occurred: Statement: <%1>, reason: %2 (error code: %3).
+ deleted: %1 entries
-An error message indicating that communication with the MySQL database server
-has been lost. When this occurs the server exits immediately with a non-zero
-exit code. This is most likely due to a network issue.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by prefix
-LEGAL_LOG_PGSQL_GET_VERSION
-===========================
+MYSQL_CB_DELETE_BY_PREFIX_SUBNET4
+=================================
.. code-block:: text
- obtaining schema version information
+ delete subnet by prefix: %1
-Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
-information from the PostgreSQL database.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete subnet by prefix
-LEGAL_LOG_PGSQL_INSERT_LOG
-==========================
+MYSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT
+========================================
.. code-block:: text
- Adding a log entry to the database: %1
+ deleted: %1 entries
-Logged at debug log level 50.
-An informational message logged when a log entry is inserted.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by prefix
-LEGAL_LOG_PGSQL_NO_TLS_SUPPORT
-==============================
+MYSQL_CB_DELETE_BY_PREFIX_SUBNET6
+=================================
.. code-block:: text
- Attempt to configure TLS (unsupported for PostgreSQL): %1
+ delete subnet by prefix: %1
-This error message is printed when TLS support was required in the Kea
-configuration: Kea was built with this feature disabled for PostgreSQL.
-The parameters of the connection are logged.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete subnet by prefix
-LEGAL_LOG_PGSQL_ROLLBACK
-========================
+MYSQL_CB_DELETE_BY_PREFIX_SUBNET6_RESULT
+========================================
.. code-block:: text
- rolling back PostgreSQL database
+ deleted: %1 entries
-The code has issued a rollback call. All outstanding transaction will
-be rolled back and not committed to the database.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by prefix
-LEGAL_LOG_PGSQL_START_TRANSACTION
-=================================
+MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4
+====================================
.. code-block:: text
- starting a new PostgreSQL transaction
+ delete by subnet id: %1 option code: %2 space: %3
-A debug message issued when a new PostgreSQL transaction is being started.
-This message is typically not issued when inserting data into a
-single table because the server doesn't explicitly start
-transactions in this case. This message is issued when data is
-inserted into multiple tables with multiple INSERT statements
-and there may be a need to rollback the whole transaction if
-any of these INSERT statements fail.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by subnet id
-LEGAL_LOG_PGSQL_TLS_SUPPORT
-===========================
+MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT
+===========================================
.. code-block:: text
- Attempt to configure TLS: %1
+ deleted: %1 entries
-This informational message is printed when TLS support was required in
-the Kea configuration: The TLS support in PostgreSQL will be initialized but
-its configuration is fully managed outside the C API.
-The parameters of the connection are logged.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by subnet id
-LEGAL_LOG_STORE_CLOSED
-======================
+MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6
+====================================
.. code-block:: text
- Legal store closed: %1
+ delete by subnet id: %1 option code: %2 space: %3
-This is an informational message issued when the Legal Log library
-has successfully closed the legal store.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by subnet id
-LEGAL_LOG_STORE_CLOSE_ERROR
-===========================
+MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT
+===========================================
.. code-block:: text
- An error occurred closing the store: %1, error: %2
+ deleted: %1 entries
-This is an error message issued when the legal log library experienced an
-error attempting to close a legal store. This is highly unlikely to occur and
-should not affect the store content or subsequent legal store operations.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by subnet id
-LEGAL_LOG_STORE_OPENED
-======================
+MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4
+====================================
.. code-block:: text
- Legal store opened: %1
-
-This is an informational message issued when the Legal Log library
-has successfully opened the legal store.
+ delete subnet by subnet id: %1
-***
-LFC
-***
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete subnet by subnet id
-LFC_FAIL_PID_CREATE
-===================
+MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT
+===========================================
.. code-block:: text
- : %1
+ deleted: %1 entries
-This message is issued if LFC detected a failure when trying
-to create the PID file. It includes a more specific error string.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by subnet id
-LFC_FAIL_PID_DEL
-================
+MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6
+====================================
.. code-block:: text
- : %1
+ delete subnet by subnet id: %1
-This message is issued if LFC detected a failure when trying
-to delete the PID file. It includes a more specific error string.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete subnet by subnet id
-LFC_FAIL_PROCESS
-================
+MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT
+===========================================
.. code-block:: text
- : %1
+ deleted: %1 entries
-This message is issued if LFC detected a failure when trying
-to process the files. It includes a more specific error string.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by subnet id
-LFC_FAIL_ROTATE
-===============
+MYSQL_CB_DELETE_CLIENT_CLASS4
+=============================
.. code-block:: text
- : %1
+ delete client class: %1
-This message is issued if LFC detected a failure when trying
-to rotate the files. It includes a more specific error string.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete client class
-LFC_PROCESSING
-==============
+MYSQL_CB_DELETE_CLIENT_CLASS4_RESULT
+====================================
.. code-block:: text
- Previous file: %1, copy file: %2
+ deleted: %1 entries
-This message is issued just before LFC starts processing the
-lease files.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete client class
-LFC_READ_STATS
-==============
+MYSQL_CB_DELETE_CLIENT_CLASS6
+=============================
.. code-block:: text
- Leases: %1, attempts: %2, errors: %3.
+ delete client class: %1
-This message prints out the number of leases that were read, the
-number of attempts to read leases and the number of errors
-encountered while reading.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete client class
-LFC_ROTATING
-============
+MYSQL_CB_DELETE_CLIENT_CLASS6_RESULT
+====================================
.. code-block:: text
- LFC rotating files
+ deleted: %1 entries
-This message is issued just before LFC starts rotating the
-lease files - removing the old and replacing them with the new.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete client class
-LFC_RUNNING
-===========
+MYSQL_CB_DELETE_GLOBAL_PARAMETER4
+=================================
.. code-block:: text
- LFC instance already running
+ delete global parameter: %1
-This message is issued if LFC detects that a previous copy of LFC
-may still be running via the PID check.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete global parameter
-LFC_START
-=========
+MYSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT
+========================================
.. code-block:: text
- Starting lease file cleanup
+ deleted: %1 entries
-This message is issued as the LFC process starts.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete global parameter
-LFC_TERMINATE
-=============
+MYSQL_CB_DELETE_GLOBAL_PARAMETER6
+=================================
.. code-block:: text
- LFC finished processing
+ delete global parameter: %1
-This message is issued when the LFC process completes. It does not
-indicate that the process was successful only that it has finished.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete global parameter
-******
-LIMITS
-******
+MYSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT
+========================================
-LIMITS_CONFIGURATION_LEASE_BACKEND_NOT_AVAILABLE
-================================================
+.. code-block:: text
+
+ deleted: %1 entries
+
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete global parameter
+
+MYSQL_CB_DELETE_OPTION4
+=======================
.. code-block:: text
- Lease backend not available. Could not check JSON support in the database. Continuing without checking...
+ delete option code: %1 space: %2
-Warning message logged to notify that limits might not work if the recovering database does not have JSON support.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option
-LIMITS_CONFIGURATION_LEASE_BACKEND_SHOULD_HAVE_BEEN_AVAILABLE
-=============================================================
+MYSQL_CB_DELETE_OPTION4_RESULT
+==============================
.. code-block:: text
- Lease backend not available when configuration shows it should have been. This is likely a programmatic error. Continuing...
+ deleted: %1 entries
-Error message logged to notify about an unexpected situation where the lease backend was expected to be available, but it was not. Runtime errors might occur.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option
-LIMITS_CONFIGURED_ADDRESS_LIMIT_BY_CLIENT_CLASS
-===============================================
+MYSQL_CB_DELETE_OPTION6
+=======================
.. code-block:: text
- New lease limit of %1 addresses for client class %2 has been configured.
+ delete option code: %1 space: %2
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of an address limit per client class
+Debug message issued when triggered an action to delete option
-LIMITS_CONFIGURED_ADDRESS_LIMIT_BY_SUBNET
-=========================================
+MYSQL_CB_DELETE_OPTION6_RESULT
+==============================
.. code-block:: text
- New lease limit of %1 addresses for subnet with ID %2 has been configured.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of an address limit per subnet
+Debug message indicating the result of an action to delete option
-LIMITS_CONFIGURED_PREFIX_LIMIT_BY_CLIENT_CLASS
-==============================================
+MYSQL_CB_DELETE_OPTION_DEF4
+===========================
.. code-block:: text
- New lease limit of %1 prefixes for client class %2 has been configured.
+ delete option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of a prefix limit per client class
+Debug message issued when triggered an action to delete option definition
-LIMITS_CONFIGURED_PREFIX_LIMIT_BY_SUBNET
-========================================
+MYSQL_CB_DELETE_OPTION_DEF4_RESULT
+==================================
.. code-block:: text
- New lease limit of %1 prefixes for subnet with ID %2 has been configured.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of a prefix limit per subnet
+Debug message indicating the result of an action to delete option definition
-LIMITS_CONFIGURED_RATE_LIMIT_BY_CLIENT_CLASS
-============================================
+MYSQL_CB_DELETE_OPTION_DEF6
+===========================
.. code-block:: text
- New rate limit of %1 for client class %2 has been configured.
+ delete option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of a rate limit per client class
+Debug message issued when triggered an action to delete option definition
-LIMITS_CONFIGURED_RATE_LIMIT_BY_SUBNET
-======================================
+MYSQL_CB_DELETE_OPTION_DEF6_RESULT
+==================================
.. code-block:: text
- New rate limit of %1 for subnet with ID %2 has been configured.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to notify about the successful configuration of a rate limit per subnet
+Debug message indicating the result of an action to delete option definition
-LIMITS_LEASE_LIMIT_EXCEEDED
-===========================
+MYSQL_CB_DELETE_SERVER4
+=======================
.. code-block:: text
- Lease was not allocated due to exceeding %1.
+ delete DHCPv4 server: %1
Logged at debug log level 40.
-Debug message logged to indicate that the current number of leased addresses or
-prefixes for a client class or a subnet is exceeding the limit.
+Debug message issued when triggered an action to delete a server.
-LIMITS_LEASE_WITHIN_LIMITS
-==========================
+MYSQL_CB_DELETE_SERVER4_RESULT
+==============================
.. code-block:: text
- Lease with address %1 is within limits.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to indicate that the current number of leased addresses or
-prefixes for a client class or a subnet is exceeding the limit.
+Debug message indicating the result of an action to delete a server.
-LIMITS_PACKET_WIIH_SUBNET_ID_RATE_NO_SUBNET
-===========================================
+MYSQL_CB_DELETE_SERVER6
+=======================
.. code-block:: text
- Packet is not being rate limited due to no subnet specified.
+ delete DHCPv6 server: %1
-Logged at debug log level 55.
-Debug message logged to indicate that the current packet's subnet rate limit, if any, is not being
-checked due to the subnet not being set in the callout handle. This can happen e.g. if the subnet
-had been deleted after it was selected for the currently processed packet.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete a server.
-LIMITS_PACKET_WITH_CLIENT_CLASSES_RATE_LIMIT_DROPPED
-====================================================
+MYSQL_CB_DELETE_SERVER6_RESULT
+==============================
.. code-block:: text
- Packet assigned to client classes %1 is being dropped for exceeding the rate limit of %2 for client class %3.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to indicate that the current packet has exceeded one of the rate limits
-configured under at least one client class
+Debug message indicating the result of an action to delete a server.
-LIMITS_PACKET_WITH_CLIENT_CLASSES_RATE_LIMIT_HONORED
-====================================================
+MYSQL_CB_DELETE_SHARED_NETWORK4
+===============================
.. code-block:: text
- Packet assigned to client classes %1 is being honored.
+ delete shared network: %1
-Logged at debug log level 55.
-Debug message logged to indicate that the current packet has not exceeded any of the rate limits
-configured under any client class
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network
-LIMITS_PACKET_WITH_SUBNET_ID_RATE_LIMIT_DROPPED
-===============================================
+MYSQL_CB_DELETE_SHARED_NETWORK4_RESULT
+======================================
.. code-block:: text
- Packet assigned to subnet with ID %1 is being dropped for exceeding the rate limit of %2.
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message logged to indicate that the current packet has exceeded the limit configured under
-the assigned subnet ID, if any is configured
-
-*******
-LOGIMPL
-*******
+Debug message indicating the result of an action to delete shared network
-LOGIMPL_ABOVE_MAX_DEBUG
-=======================
+MYSQL_CB_DELETE_SHARED_NETWORK6
+===============================
.. code-block:: text
- debug level of %1 is too high and will be set to the maximum of %2
+ delete shared network: %1
-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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network
-LOGIMPL_BAD_DEBUG_STRING
-========================
+MYSQL_CB_DELETE_SHARED_NETWORK6_RESULT
+======================================
.. code-block:: text
- 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.
+ deleted: %1 entries
-***
-LOG
-***
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete shared network
-LOG_BAD_DESTINATION
-===================
+MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4
+======================================
.. code-block:: text
- unrecognized log destination: %1
+ delete shared network: %1 option code: %2 space: %3
-This error message is printed when a logger destination value was given that was not recognized. The
-destination should be one of "console", "file", or "syslog".
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network option
-LOG_BAD_SEVERITY
-================
+MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT
+=============================================
.. code-block:: text
- unrecognized log severity: %1
+ deleted: %1 entries
-This error message is printed when a logger severity value was given that was not recognized. The severity
-should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE".
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete shared network option
-LOG_BAD_STREAM
-==============
+MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6
+======================================
.. code-block:: text
- bad log console output stream: %1
+ delete shared network: %1 option code: %2 space: %3
-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 recognized.
-Allowed values are "stdout" and "stderr".
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network option
-LOG_DUPLICATE_MESSAGE_ID
-========================
+MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT
+=============================================
.. code-block:: text
- duplicate message ID (%1) in compiled code
+ deleted: %1 entries
-During start-up, Kea detected that the given message identification
-had been defined multiple times in the Kea code. This indicates a
-programming error; please submit a bug report.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete shared network option
-LOG_DUPLICATE_NAMESPACE
-=======================
+MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4
+=======================================
.. code-block:: text
- line %1: duplicate $NAMESPACE directive found
+ delete shared network: %1 subnets
-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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network subnets
-LOG_INPUT_OPEN_FAIL
-===================
+MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT
+==============================================
.. code-block:: text
- unable to open message file %1 for input: %2
+ deleted: %1 entries
-The program was not able to open the specified input message file for
-the reason given.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete shared network subnets
-LOG_INVALID_MESSAGE_ID
-======================
+MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6
+=======================================
.. code-block:: text
- line %1: invalid message identification '%2'
+ delete shared network: %1 subnets
-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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete shared network subnets
-LOG_NAMESPACE_EXTRA_ARGS
-========================
+MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT
+==============================================
.. code-block:: text
- line %1: $NAMESPACE directive has too many arguments
+ deleted: %1 entries
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete shared network subnets
-LOG_NAMESPACE_INVALID_ARG
-=========================
+MYSQL_CB_GET_ALL_CLIENT_CLASSES4
+================================
.. code-block:: text
- line %1: $NAMESPACE directive has an invalid argument ('%2')
+ retrieving all client classes
-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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all client classes
-LOG_NAMESPACE_NO_ARGS
-=====================
+MYSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT
+=======================================
.. code-block:: text
- line %1: no arguments were given to the $NAMESPACE directive
+ retrieving: %1 elements
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve all client classes
-LOG_NO_MESSAGE_ID
-=================
+MYSQL_CB_GET_ALL_CLIENT_CLASSES6
+================================
.. code-block:: text
- line %1: message definition line found without a message ID
+ retrieving all client classes
-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.
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all client classes
-LOG_NO_MESSAGE_TEXT
-===================
+MYSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT
+=======================================
.. code-block:: text
- line %1: line found containing a message ID ('%2') and no text
+ retrieving: %1 elements
-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.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve all client classes
-LOG_NO_SUCH_MESSAGE
-===================
+MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4
+===================================
.. code-block:: text
- could not replace message text for '%1': no such message
+ retrieving all global parameters
-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 are several reasons why this message may appear:
-- The message ID has been misspelled 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 Kea software
-and the later version no longer generates that message.
-Whatever the reason, there is no impact on the operation of Kea.
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all global parameters
-LOG_OPEN_OUTPUT_FAIL
-====================
+MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT
+==========================================
.. code-block:: text
- unable to open %1 for output: %2
+ retrieving: %1 elements
-Originating within the logging code, the program was not able to open
-the specified output file for the reason given.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve all global parameters
-LOG_PREFIX_EXTRA_ARGS
-=====================
+MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6
+===================================
.. code-block:: text
- line %1: $PREFIX directive has too many arguments
+ retrieving all global parameters
-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 Kea.
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all global parameters
-LOG_PREFIX_INVALID_ARG
-======================
+MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT
+==========================================
.. code-block:: text
- line %1: $PREFIX directive has an invalid argument ('%2')
+ retrieving: %1 elements
-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 Kea.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve all global parameters
-LOG_READING_LOCAL_FILE
-======================
+MYSQL_CB_GET_ALL_OPTIONS4
+=========================
.. code-block:: text
- reading local message file %1
+ retrieving all options
-This is an informational message output by Kea 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.)
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all options
-LOG_READ_ERROR
-==============
+MYSQL_CB_GET_ALL_OPTIONS4_RESULT
+================================
.. code-block:: text
- error reading from message file %1: %2
+ retrieving: %1 elements
-The specified error was encountered reading from the named message file.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve all options
-LOG_UNRECOGNIZED_DIRECTIVE
-==========================
+MYSQL_CB_GET_ALL_OPTIONS6
+=========================
.. code-block:: text
- line %1: unrecognized 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 recognized.
+ retrieving all options
-**
-MT
-**
+Logged at debug log level 40.
+Debug message issued when triggered an action to retrieve all options
-MT_TCP_LISTENER_MGR_STARTED
-===========================
+MYSQL_CB_GET_ALL_OPTIONS6_RESULT
+================================
.. code-block:: text
- MtTcpListenerMgr started with %1 threads, listening on %2:%3, use TLS: %4
+ retrieving: %1 elements
Logged at debug log level 40.
-This debug messages is issued when an MtTcpListenerMgr has been started to
-accept connections. Arguments detail the number of threads that the listener
-is using, the address and port at which it is listening, and if TLS is used
-or not.
+Debug message indicating the result of an action to retrieve all options
-MT_TCP_LISTENER_MGR_STOPPED
-===========================
+MYSQL_CB_GET_ALL_OPTION_DEFS4
+=============================
.. code-block:: text
- MtTcpListenerMgr for %1:%2 stopped.
+ retrieving all option definitions
Logged at debug log level 40.
-This debug messages is issued when the MtTcpListenerMgr, listening
-at the given address and port, has completed shutdown.
+Debug message issued when triggered an action to retrieve all option definitions
-MT_TCP_LISTENER_MGR_STOPPING
-============================
+MYSQL_CB_GET_ALL_OPTION_DEFS4_RESULT
+====================================
.. code-block:: text
- Stopping MtTcpListenerMgr for %1:%2
+ retrieving: %1 elements
Logged at debug log level 40.
-This debug messages is issued when the MtTcpListenerMgr, listening
-at the given address and port, has begun to shutdown.
-
-*****
-MYSQL
-*****
+Debug message indicating the result of an action to retrieve all option definitions
-MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4
-======================================
+MYSQL_CB_GET_ALL_OPTION_DEFS6
+=============================
.. code-block:: text
- create or update option pool start: %1 pool end: %2
+ retrieving all option definitions
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by pool
+Debug message issued when triggered an action to retrieve all option definitions
-MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6
-======================================
+MYSQL_CB_GET_ALL_OPTION_DEFS6_RESULT
+====================================
.. code-block:: text
- create or update option pool start: %1 pool end: %2
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by pool
+Debug message indicating the result of an action to retrieve all option definitions
-MYSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6
-========================================
+MYSQL_CB_GET_ALL_SERVERS4
+=========================
.. code-block:: text
- create or update option prefix: %1 prefix len: %2
+ retrieving all servers
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by prefix
+Debug message issued when triggered an action to retrieve all DHCPv4
+servers
-MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4
-===========================================
+MYSQL_CB_GET_ALL_SERVERS4_RESULT
+================================
.. code-block:: text
- create or update option by subnet id: %1
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by subnet id
+Debug message indicating the result of an action to retrieve all DHCPv4
+servers
-MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6
-===========================================
+MYSQL_CB_GET_ALL_SERVERS6
+=========================
.. code-block:: text
- create or update option by subnet id: %1
+ retrieving all DHCPv6 servers
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by subnet id
+Debug message issued when triggered an action to retrieve all DHCPv6
+servers
-MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS4
-====================================
+MYSQL_CB_GET_ALL_SERVERS6_RESULT
+================================
.. code-block:: text
- create or update client class: %1
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update client class
+Debug message indicating the result of an action to retrieve all DHCPv6
+servers
-MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS6
-====================================
+MYSQL_CB_GET_ALL_SHARED_NETWORKS4
+=================================
.. code-block:: text
- create or update client class: %1
+ retrieving all shared networks
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update client class
+Debug message issued when triggered an action to retrieve all shared networks
-MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4
+MYSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT
========================================
.. code-block:: text
- create or update global parameter: %1
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update global parameter
+Debug message indicating the result of an action to retrieve all shared networks
-MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6
-========================================
+MYSQL_CB_GET_ALL_SHARED_NETWORKS6
+=================================
.. code-block:: text
- create or update global parameter: %1
+ retrieving all shared networks
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update global parameter
+Debug message issued when triggered an action to retrieve all shared networks
-MYSQL_CB_CREATE_UPDATE_OPTION4
-==============================
+MYSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT
+========================================
.. code-block:: text
- create or update option
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option
+Debug message indicating the result of an action to retrieve all shared networks
-MYSQL_CB_CREATE_UPDATE_OPTION6
-==============================
+MYSQL_CB_GET_ALL_SUBNETS4
+=========================
.. code-block:: text
- create or update option
+ retrieving all subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option
+Debug message issued when triggered an action to retrieve all subnets
-MYSQL_CB_CREATE_UPDATE_OPTION_DEF4
-==================================
+MYSQL_CB_GET_ALL_SUBNETS4_RESULT
+================================
.. code-block:: text
- create or update option definition: %1 code: %2
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option definition
+Debug message indicating the result of an action to retrieve all subnets
-MYSQL_CB_CREATE_UPDATE_OPTION_DEF6
-==================================
+MYSQL_CB_GET_ALL_SUBNETS6
+=========================
.. code-block:: text
- create or update option definition: %1 code: %2
+ retrieving all subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option definition
+Debug message issued when triggered an action to retrieve all subnets
-MYSQL_CB_CREATE_UPDATE_SERVER4
-==============================
+MYSQL_CB_GET_ALL_SUBNETS6_RESULT
+================================
.. code-block:: text
- create or update server: %1
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update a DHCPv4
-server information.
+Debug message indicating the result of an action to retrieve all subnets
-MYSQL_CB_CREATE_UPDATE_SERVER6
-==============================
+MYSQL_CB_GET_CLIENT_CLASS4
+==========================
.. code-block:: text
- create or update server: %1
+ retrieving client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update a DHCPv6
-server information.
+Debug message issued when triggered an action to retrieve a client class
-MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK4
-======================================
+MYSQL_CB_GET_CLIENT_CLASS6
+==========================
.. code-block:: text
- create or update shared network: %1
+ retrieving client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network
+Debug message issued when triggered an action to retrieve a client class
-MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK6
-======================================
+MYSQL_CB_GET_GLOBAL_PARAMETER4
+==============================
.. code-block:: text
- create or update shared network: %1
+ retrieving global parameter: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network
+Debug message issued when triggered an action to retrieve global parameter
-MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4
-=============================================
+MYSQL_CB_GET_GLOBAL_PARAMETER6
+==============================
.. code-block:: text
- create or update shared network: %1 option
+ retrieving global parameter: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network option
+Debug message issued when triggered an action to retrieve global parameter
-MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6
-=============================================
+MYSQL_CB_GET_HOST4
+==================
.. code-block:: text
- create or update shared network: %1 option
+ get host
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network option
+Debug message issued when triggered an action to retrieve host
-MYSQL_CB_CREATE_UPDATE_SUBNET4
-==============================
+MYSQL_CB_GET_HOST6
+==================
.. code-block:: text
- create or update subnet: %1
+ get host
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update subnet
+Debug message issued when triggered an action to retrieve host
-MYSQL_CB_CREATE_UPDATE_SUBNET6
-==============================
+MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4
+=====================================
.. code-block:: text
- create or update subnet: %1
+ retrieving modified client classes from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update subnet
+Debug message issued when triggered an action to retrieve modified client classes from specified time
-MYSQL_CB_DEINIT_OK
-==================
+MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT
+============================================
.. code-block:: text
- unloading MYSQL CB hooks library successful
+ retrieving: %1 elements
-This informational message indicates that the MySQL Configuration Backend hooks
-library has been unloaded successfully.
+Logged at debug log level 40.
+Debug message indicating the result of an action to retrieve modified client classes from specified time
-MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4
-===================================
+MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6
+=====================================
.. code-block:: text
- delete all client classes
+ retrieving modified client classes from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all client classes
+Debug message issued when triggered an action to retrieve modified client classes from specified time
-MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT
-==========================================
+MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT
+============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all client classes
+Debug message indicating the result of an action to retrieve modified client classes from specified time
-MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6
-===================================
+MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4
+========================================
.. code-block:: text
- delete all client classes
+ retrieving modified global parameters from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all client classes
+Debug message issued when triggered an action to retrieve modified global parameters from specified time
-MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT
-==========================================
+MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT
+===============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all client classes
+Debug message indicating the result of an action to retrieve modified global parameters from specified time
-MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4
-======================================
+MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6
+========================================
.. code-block:: text
- delete all global parameters
+ retrieving modified global parameters from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all global parameters
+Debug message issued when triggered an action to retrieve modified global parameters from specified time
-MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT
-=============================================
+MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT
+===============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all global parameters
+Debug message indicating the result of an action to retrieve modified global parameters from specified time
-MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6
-======================================
+MYSQL_CB_GET_MODIFIED_OPTIONS4
+==============================
.. code-block:: text
- delete all global parameters
+ retrieving modified options from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all global parameters
+Debug message issued when triggered an action to retrieve modified options from specified time
-MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT
-=============================================
+MYSQL_CB_GET_MODIFIED_OPTIONS4_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all global parameters
+Debug message indicating the result of an action to retrieve modified options from specified time
-MYSQL_CB_DELETE_ALL_OPTION_DEFS4
-================================
+MYSQL_CB_GET_MODIFIED_OPTIONS6
+==============================
.. code-block:: text
- delete all option definitions
+ retrieving modified options from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all option definitions
+Debug message issued when triggered an action to retrieve modified options from specified time
-MYSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT
-=======================================
+MYSQL_CB_GET_MODIFIED_OPTIONS6_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all option definitions
+Debug message indicating the result of an action to retrieve modified options from specified time
-MYSQL_CB_DELETE_ALL_OPTION_DEFS6
-================================
+MYSQL_CB_GET_MODIFIED_OPTION_DEFS4
+==================================
.. code-block:: text
- delete all option definitions
+ retrieving modified option definitions from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all option definitions
+Debug message issued when triggered an action to retrieve modified option definitions from specified time
-MYSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT
-=======================================
+MYSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all option definitions
+Debug message indicating the result of an action to retrieve modified option definitions from specified time
-MYSQL_CB_DELETE_ALL_SERVERS4
-============================
+MYSQL_CB_GET_MODIFIED_OPTION_DEFS6
+==================================
.. code-block:: text
- delete all DHCPv4 servers
+ retrieving modified option definitions from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all servers.
+Debug message issued when triggered an action to retrieve modified option definitions from specified time
-MYSQL_CB_DELETE_ALL_SERVERS4_RESULT
-===================================
+MYSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all servers.
+Debug message indicating the result of an action to retrieve modified option definitions from specified time
-MYSQL_CB_DELETE_ALL_SERVERS6
-============================
+MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4
+======================================
.. code-block:: text
- delete all DHCPv6 servers
+ retrieving modified shared networks from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all servers.
+Debug message issued when triggered an action to retrieve modified shared networks from specified time
-MYSQL_CB_DELETE_ALL_SERVERS6_RESULT
-===================================
+MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT
+=============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all servers.
+Debug message indicating the result of an action to retrieve modified shared networks from specified time
-MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4
-====================================
+MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6
+======================================
.. code-block:: text
- delete all shared networks
+ retrieving modified shared networks from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all shared networks
+Debug message issued when triggered an action to retrieve modified shared networks from specified time
-MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT
-===========================================
+MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT
+=============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all shared networks
+Debug message indicating the result of an action to retrieve modified shared networks from specified time
-MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6
-====================================
+MYSQL_CB_GET_MODIFIED_SUBNETS4
+==============================
.. code-block:: text
- delete all shared networks
+ retrieving modified subnets from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all shared networks
+Debug message issued when triggered an action to retrieve modified subnets from specified time
-MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT
-===========================================
+MYSQL_CB_GET_MODIFIED_SUBNETS4_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all shared networks
+Debug message indicating the result of an action to retrieve modified subnets from specified time
-MYSQL_CB_DELETE_ALL_SUBNETS4
-============================
+MYSQL_CB_GET_MODIFIED_SUBNETS6
+==============================
.. code-block:: text
- delete all subnets
+ retrieving modified subnets from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all subnets
+Debug message issued when triggered an action to retrieve modified subnets from specified time
-MYSQL_CB_DELETE_ALL_SUBNETS4_RESULT
-===================================
+MYSQL_CB_GET_MODIFIED_SUBNETS6_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all subnets
+Debug message indicating the result of an action to retrieve modified subnets from specified time
-MYSQL_CB_DELETE_ALL_SUBNETS6
-============================
+MYSQL_CB_GET_OPTION4
+====================
.. code-block:: text
- delete all subnets
+ retrieving option code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all subnets
+Debug message issued when triggered an action to retrieve option
-MYSQL_CB_DELETE_ALL_SUBNETS6_RESULT
-===================================
+MYSQL_CB_GET_OPTION6
+====================
.. code-block:: text
- deleted: %1 entries
+ retrieving option code: %1 space: %2
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all subnets
+Debug message issued when triggered an action to retrieve option
-MYSQL_CB_DELETE_BY_POOL_OPTION4
-===============================
+MYSQL_CB_GET_OPTION_DEF4
+========================
.. code-block:: text
- delete pool start: %1 pool end: %2 option code: %3 space: %4
+ retrieving option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by pool
+Debug message issued when triggered an action to retrieve option definition
-MYSQL_CB_DELETE_BY_POOL_OPTION4_RESULT
-======================================
+MYSQL_CB_GET_OPTION_DEF6
+========================
.. code-block:: text
- deleted: %1 entries
+ retrieving option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by pool
+Debug message issued when triggered an action to retrieve option definition
-MYSQL_CB_DELETE_BY_POOL_OPTION6
-===============================
+MYSQL_CB_GET_PORT4
+==================
.. code-block:: text
- delete pool start: %1 pool end: %2 option code: %3 space: %4
+ get port
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by pool
+Debug message issued when triggered an action to retrieve port
-MYSQL_CB_DELETE_BY_POOL_OPTION6_RESULT
-======================================
+MYSQL_CB_GET_PORT6
+==================
.. code-block:: text
- deleted: %1 entries
+ get port
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by pool
+Debug message issued when triggered an action to retrieve port
-MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6
-======================================
+MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4
+==================================
.. code-block:: text
- delete prefix: %1 prefix len: %2 option code: %3 space: %4
+ retrieving audit entries from: %1 %2
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by prefix
+Debug message issued when triggered an action to retrieve audit entries from specified time and id.
-MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT
-=============================================
+MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by prefix
+Debug message indicating the result of an action to retrieve audit entries from specified time
-MYSQL_CB_DELETE_BY_PREFIX_SUBNET4
-=================================
+MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6
+==================================
.. code-block:: text
- delete subnet by prefix: %1
+ retrieving audit entries from: %1 %2
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by prefix
+Debug message issued when triggered an action to retrieve audit entries from specified time and id
-MYSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT
-========================================
+MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by prefix
+Debug message indicating the result of an action to retrieve audit entries from specified time
-MYSQL_CB_DELETE_BY_PREFIX_SUBNET6
-=================================
+MYSQL_CB_GET_SERVER4
+====================
.. code-block:: text
- delete subnet by prefix: %1
+ retrieving DHCPv4 server: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by prefix
-
-MYSQL_CB_DELETE_BY_PREFIX_SUBNET6_RESULT
-========================================
+Debug message issued when triggered an action to retrieve a DHCPv4 server information.
+
+MYSQL_CB_GET_SERVER6
+====================
.. code-block:: text
- deleted: %1 entries
+ retrieving DHCPv6 server: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by prefix
+Debug message issued when triggered an action to retrieve a DHCPv6 server information.
-MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4
-====================================
+MYSQL_CB_GET_SHARED_NETWORK4
+============================
.. code-block:: text
- delete by subnet id: %1 option code: %2 space: %3
+ retrieving shared network: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by subnet id
+Debug message issued when triggered an action to retrieve shared network
-MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT
-===========================================
+MYSQL_CB_GET_SHARED_NETWORK6
+============================
.. code-block:: text
- deleted: %1 entries
+ retrieving shared network: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by subnet id
+Debug message issued when triggered an action to retrieve shared network
-MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6
+MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4
====================================
.. code-block:: text
- delete by subnet id: %1 option code: %2 space: %3
+ retrieving shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by subnet id
+Debug message issued when triggered an action to retrieve shared network subnets
-MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT
+MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT
===========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by subnet id
+Debug message indicating the result of an action to retrieve shared network subnets
-MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4
+MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6
====================================
.. code-block:: text
- delete subnet by subnet id: %1
+ retrieving shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by subnet id
+Debug message issued when triggered an action to retrieve shared network subnets
-MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT
+MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT
===========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by subnet id
+Debug message indicating the result of an action to retrieve shared network subnets
-MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6
-====================================
+MYSQL_CB_GET_SUBNET4_BY_PREFIX
+==============================
.. code-block:: text
- delete subnet by subnet id: %1
+ retrieving subnet by prefix: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by subnet id
+Debug message issued when triggered an action to retrieve subnet by prefix
-MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT
-===========================================
+MYSQL_CB_GET_SUBNET4_BY_SUBNET_ID
+=================================
.. code-block:: text
- deleted: %1 entries
+ retrieving subnet by subnet id: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by subnet id
+Debug message issued when triggered an action to retrieve subnet by subnet id
-MYSQL_CB_DELETE_CLIENT_CLASS4
-=============================
+MYSQL_CB_GET_SUBNET6_BY_PREFIX
+==============================
.. code-block:: text
- delete client class: %1
+ retrieving subnet by prefix: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete client class
+Debug message issued when triggered an action to retrieve subnet by prefix
-MYSQL_CB_DELETE_CLIENT_CLASS4_RESULT
-====================================
+MYSQL_CB_GET_SUBNET6_BY_SUBNET_ID
+=================================
.. code-block:: text
- deleted: %1 entries
+ retrieving subnet by subnet id: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete client class
+Debug message issued when triggered an action to retrieve subnet by subnet id
-MYSQL_CB_DELETE_CLIENT_CLASS6
-=============================
+MYSQL_CB_GET_TYPE4
+==================
.. code-block:: text
- delete client class: %1
+ get type
Logged at debug log level 40.
-Debug message issued when triggered an action to delete client class
+Debug message issued when triggered an action to retrieve type
-MYSQL_CB_DELETE_CLIENT_CLASS6_RESULT
-====================================
+MYSQL_CB_GET_TYPE6
+==================
.. code-block:: text
- deleted: %1 entries
+ get type
Logged at debug log level 40.
-Debug message indicating the result of an action to delete client class
+Debug message issued when triggered an action to retrieve type
-MYSQL_CB_DELETE_GLOBAL_PARAMETER4
-=================================
+MYSQL_CB_NO_TLS
+===============
.. code-block:: text
- delete global parameter: %1
+ TLS was required but is not used
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete global parameter
+This error message is issued when TLS for the connection was required but
+TLS is not used.
-MYSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT
-========================================
+MYSQL_CB_RECONNECT_ATTEMPT_FAILED4
+==================================
.. code-block:: text
- deleted: %1 entries
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete global parameter
+Error message issued when an attempt to reconnect has failed.
-MYSQL_CB_DELETE_GLOBAL_PARAMETER6
-=================================
+MYSQL_CB_RECONNECT_ATTEMPT_FAILED6
+==================================
.. code-block:: text
- delete global parameter: %1
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete global parameter
+Error message issued when an attempt to reconnect has failed.
-MYSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT
-========================================
+MYSQL_CB_RECONNECT_ATTEMPT_SCHEDULE4
+====================================
.. code-block:: text
- deleted: %1 entries
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete global parameter
+Info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-MYSQL_CB_DELETE_OPTION4
-=======================
+MYSQL_CB_RECONNECT_ATTEMPT_SCHEDULE6
+====================================
.. code-block:: text
- delete option code: %1 space: %2
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete option
+Info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-MYSQL_CB_DELETE_OPTION4_RESULT
-==============================
+MYSQL_CB_RECONNECT_FAILED4
+==========================
.. code-block:: text
- deleted: %1 entries
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete option
+Error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-MYSQL_CB_DELETE_OPTION6
-=======================
+MYSQL_CB_RECONNECT_FAILED6
+==========================
.. code-block:: text
- delete option code: %1 space: %2
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete option
+Error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-MYSQL_CB_DELETE_OPTION6_RESULT
-==============================
+MYSQL_CB_REGISTER_BACKEND_TYPE4
+===============================
.. code-block:: text
- deleted: %1 entries
+ register backend
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option
+Debug message issued when triggered an action to register backend
-MYSQL_CB_DELETE_OPTION_DEF4
-===========================
+MYSQL_CB_REGISTER_BACKEND_TYPE6
+===============================
.. code-block:: text
- delete option definition code: %1 space: %2
+ register backend
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option definition
+Debug message issued when triggered an action to register backend
-MYSQL_CB_DELETE_OPTION_DEF4_RESULT
-==================================
+MYSQL_CB_TLS_CIPHER
+===================
.. code-block:: text
- deleted: %1 entries
+ TLS cipher: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option definition
+A debug message issued when a new MySQL connected is created with TLS.
+The TLS cipher name is logged.
-MYSQL_CB_DELETE_OPTION_DEF6
-===========================
+MYSQL_CB_UNREGISTER_BACKEND_TYPE4
+=================================
.. code-block:: text
- delete option definition code: %1 space: %2
+ unregister backend
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option definition
+Debug message issued when triggered an action to unregister backend
-MYSQL_CB_DELETE_OPTION_DEF6_RESULT
-==================================
+MYSQL_DEINIT_OK
+===============
.. code-block:: text
- deleted: %1 entries
+ unloading MySQL hooks library successful
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete option definition
+This informational message indicates that the MySQL Backend hooks
+library has been unloaded successfully.
-MYSQL_CB_DELETE_SERVER4
-=======================
+MYSQL_HB_DB
+===========
.. code-block:: text
- delete DHCPv4 server: %1
+ opening MySQL hosts database: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete a server.
+This informational message is logged when a DHCP server (either V4 or
+V6) is about to open a MySQL hosts database. The parameters of the
+connection including database name and username needed to access it
+(but not the password if any) are logged.
-MYSQL_CB_DELETE_SERVER4_RESULT
-==============================
+MYSQL_HB_DB_GET_VERSION
+=======================
.. code-block:: text
- deleted: %1 entries
+ obtaining schema version information for the MySQL hosts database
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete a server.
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the MySQL hosts database.
-MYSQL_CB_DELETE_SERVER6
-=======================
+MYSQL_HB_DB_READONLY
+====================
.. code-block:: text
- delete DHCPv6 server: %1
+ MySQL host database opened for read access only
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete a server.
+This informational message is issued when the user has configured the MySQL
+database in read-only mode. Kea will not be able to insert or modify
+host reservations but will be able to retrieve existing ones and
+assign them to the clients communicating with the server.
-MYSQL_CB_DELETE_SERVER6_RESULT
-==============================
+MYSQL_HB_DB_RECONNECT_ATTEMPT_FAILED
+====================================
.. code-block:: text
- deleted: %1 entries
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete a server.
+An error message issued when an attempt to reconnect has failed.
-MYSQL_CB_DELETE_SHARED_NETWORK4
-===============================
+MYSQL_HB_DB_RECONNECT_ATTEMPT_SCHEDULE
+======================================
+
+.. code-block:: text
+
+ scheduling attempt %1 of %2 in %3 milliseconds
+
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
+
+MYSQL_HB_DB_RECONNECT_FAILED
+============================
.. code-block:: text
- delete shared network: %1
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-MYSQL_CB_DELETE_SHARED_NETWORK4_RESULT
-======================================
+MYSQL_HB_NO_TLS
+===============
.. code-block:: text
- deleted: %1 entries
+ TLS was required but is not used
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network
+This error message is issued when TLS for the connection was required but
+TLS is not used.
-MYSQL_CB_DELETE_SHARED_NETWORK6
-===============================
+MYSQL_INIT_OK
+=============
.. code-block:: text
- delete shared network: %1
+ loading MySQL hooks library successful
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network
+This informational message indicates that the MySQL Backend hooks
+library has been loaded successfully. Enjoy!
-MYSQL_CB_DELETE_SHARED_NETWORK6_RESULT
-======================================
+MYSQL_LB_ADD_ADDR4
+==================
.. code-block:: text
- deleted: %1 entries
+ adding IPv4 lease with address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network
+Logged at debug log level 50.
+A debug message issued when the server is about to add an IPv4 lease
+with the specified address to the MySQL backend database.
-MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4
-======================================
+MYSQL_LB_ADD_ADDR6
+==================
.. code-block:: text
- delete shared network: %1 option code: %2 space: %3
+ adding IPv6 lease with address %1, lease type %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network option
+Logged at debug log level 50.
+A debug message issued when the server is about to add an IPv6 lease
+with the specified address to the MySQL backend database.
-MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT
-=============================================
+MYSQL_LB_COMMIT
+===============
.. code-block:: text
- deleted: %1 entries
+ committing to MySQL database
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network option
+Logged at debug log level 50.
+The code has issued a commit call. All outstanding transactions will be
+committed to the database. Note that depending on the MySQL settings,
+the commit may not include a write to disk.
-MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6
-======================================
+MYSQL_LB_DB
+===========
.. code-block:: text
- delete shared network: %1 option code: %2 space: %3
+ opening MySQL lease database: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network option
+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.
-MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT
-=============================================
+MYSQL_LB_DB_RECONNECT_ATTEMPT_FAILED
+====================================
.. code-block:: text
- deleted: %1 entries
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network option
+An error message issued when an attempt to reconnect has failed.
-MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4
-=======================================
+MYSQL_LB_DB_RECONNECT_ATTEMPT_SCHEDULE
+======================================
.. code-block:: text
- delete shared network: %1 subnets
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network subnets
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT
-==============================================
+MYSQL_LB_DB_RECONNECT_FAILED
+============================
.. code-block:: text
- deleted: %1 entries
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network subnets
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6
-=======================================
+MYSQL_LB_DELETED_EXPIRED_RECLAIMED
+==================================
.. code-block:: text
- delete shared network: %1 subnets
+ deleted %1 reclaimed leases from the database
-Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network subnets
+Logged at debug log level 50.
+A debug message issued when the server has removed a number of reclaimed
+leases from the database. The number of removed leases is included in the
+message.
-MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT
-==============================================
+MYSQL_LB_DELETE_ADDR4
+=====================
.. code-block:: text
- deleted: %1 entries
+ deleting lease for address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network subnets
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_CLIENT_CLASSES4
-================================
+MYSQL_LB_DELETE_ADDR6
+=====================
.. code-block:: text
- retrieving all client classes
+ deleting lease for address %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all client classes
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT
-=======================================
+MYSQL_LB_DELETE_EXPIRED_RECLAIMED4
+==================================
.. code-block:: text
- retrieving: %1 elements
+ deleting reclaimed IPv4 leases that expired more than %1 seconds ago
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all client classes
+Logged at debug log level 50.
+A debug message issued when the server is removing reclaimed DHCPv4
+leases which have expired longer than a specified period of time.
+The argument is the amount of time Kea waits after a reclaimed
+lease expires before considering its removal.
-MYSQL_CB_GET_ALL_CLIENT_CLASSES6
-================================
+MYSQL_LB_DELETE_EXPIRED_RECLAIMED6
+==================================
.. code-block:: text
- retrieving all client classes
+ deleting reclaimed IPv6 leases that expired more than %1 seconds ago
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all client classes
+Logged at debug log level 50.
+A debug message issued when the server is removing reclaimed DHCPv6
+leases which have expired longer than a specified period of time.
+The argument is the amount of time Kea waits after a reclaimed
+lease expires before considering its removal.
-MYSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT
-=======================================
+MYSQL_LB_GET4
+=============
.. code-block:: text
- retrieving: %1 elements
+ obtaining all IPv4 leases
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all client classes
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv4
+leases from the MySQL database.
-MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4
-===================================
+MYSQL_LB_GET6
+=============
.. code-block:: text
- retrieving all global parameters
+ obtaining all IPv6 leases
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all global parameters
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv6
+leases from the MySQL database.
-MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT
-==========================================
+MYSQL_LB_GET_ADDR4
+==================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 lease for address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all global parameters
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain an IPv4
+lease from the MySQL database for the specified address.
-MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6
-===================================
+MYSQL_LB_GET_ADDR6
+==================
.. code-block:: text
- retrieving all global parameters
+ obtaining IPv6 lease for address %1, lease type %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all global parameters
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain an IPv6
+lease from the MySQL database for the specified address.
-MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT
-==========================================
+MYSQL_LB_GET_CLIENTID
+=====================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 leases for client ID %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all global parameters
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_OPTIONS4
-=========================
+MYSQL_LB_GET_DUID
+=================
.. code-block:: text
- retrieving all options
+ obtaining IPv6 lease for duid %1,
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all options
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain an IPv6
+lease from the MySQL database for the specified duid.
-MYSQL_CB_GET_ALL_OPTIONS4_RESULT
-================================
+MYSQL_LB_GET_EXPIRED4
+=====================
.. code-block:: text
- retrieving: %1 elements
+ obtaining maximum %1 of expired IPv4 leases
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all options
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain expired
+IPv4 leases to reclaim them. The maximum number of leases to be retrieved
+is logged in the message.
-MYSQL_CB_GET_ALL_OPTIONS6
-=========================
+MYSQL_LB_GET_EXPIRED6
+=====================
.. code-block:: text
- retrieving all options
+ obtaining maximum %1 of expired IPv6 leases
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all options
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain expired
+IPv6 leases to reclaim them. The maximum number of leases to be retrieved
+is logged in the message.
-MYSQL_CB_GET_ALL_OPTIONS6_RESULT
-================================
+MYSQL_LB_GET_HOSTNAME4
+======================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 leases for hostname %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all options
+Logged at debug log level 50.
+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
+hostname.
-MYSQL_CB_GET_ALL_OPTION_DEFS4
-=============================
+MYSQL_LB_GET_HOSTNAME6
+======================
.. code-block:: text
- retrieving all option definitions
-
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all option definitions
+ obtaining IPv6 leases for hostname %1
-MYSQL_CB_GET_ALL_OPTION_DEFS4_RESULT
-====================================
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a set
+of IPv6 leases from the MySQL database for a client with the specified
+hostname.
+
+MYSQL_LB_GET_HWADDR
+===================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 leases for hardware address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all option definitions
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_OPTION_DEFS6
-=============================
+MYSQL_LB_GET_IAID_DUID
+======================
.. code-block:: text
- retrieving all option definitions
+ obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all option definitions
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a set of IPv6
+leases from the MySQL database for a client with the specified IAID (Identity
+Association ID) and DUID (DHCP Unique Identifier).
-MYSQL_CB_GET_ALL_OPTION_DEFS6_RESULT
-====================================
+MYSQL_LB_GET_IAID_SUBID_DUID
+============================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all option definitions
+Logged at debug log level 50.
+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).
-MYSQL_CB_GET_ALL_SERVERS4
-=========================
+MYSQL_LB_GET_PAGE4
+==================
.. code-block:: text
- retrieving all servers
+ obtaining at most %1 IPv4 leases starting from address %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all DHCPv4
-servers
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page
+of leases beginning with the specified address.
-MYSQL_CB_GET_ALL_SERVERS4_RESULT
-================================
+MYSQL_LB_GET_PAGE6
+==================
.. code-block:: text
- retrieving: %1 elements
+ obtaining at most %1 IPv6 leases starting from address %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all DHCPv4
-servers
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page
+of leases beginning with the specified address.
-MYSQL_CB_GET_ALL_SERVERS6
-=========================
+MYSQL_LB_GET_RELAYID4
+=====================
.. code-block:: text
- retrieving all DHCPv6 servers
+ obtaining at most %1 IPv4 leases starting from address %2 with relay id %3 and cltt between %4 and %5
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all DHCPv6
-servers
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv4 leases beginning with the specified address with a relay id and client
+transaction time between start and end dates.
-MYSQL_CB_GET_ALL_SERVERS6_RESULT
-================================
+MYSQL_LB_GET_RELAYID6
+=====================
.. code-block:: text
- retrieving: %1 elements
+ obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all DHCPv6
-servers
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases beginning with the specified address with a relay id.
-MYSQL_CB_GET_ALL_SHARED_NETWORKS4
-=================================
+MYSQL_LB_GET_REMOTEID4
+======================
.. code-block:: text
- retrieving all shared networks
+ obtaining at most %1 IPv4 leases starting from address %2 with remote id %3 and cltt between %4 and %5
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all shared networks
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv4 leases beginning with the specified address with a remote id and client
+transaction time between start and end dates.
-MYSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT
-========================================
+MYSQL_LB_GET_REMOTEID6
+======================
.. code-block:: text
- retrieving: %1 elements
+ obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all shared networks
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases beginning with the specified address with a remote id.
-MYSQL_CB_GET_ALL_SHARED_NETWORKS6
-=================================
+MYSQL_LB_GET_SUBID4
+===================
.. code-block:: text
- retrieving all shared networks
+ obtaining IPv4 leases for subnet ID %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all shared networks
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv4
+leases for a given subnet identifier from the MySQL database.
-MYSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT
-========================================
+MYSQL_LB_GET_SUBID6
+===================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv6 leases for subnet ID %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all shared networks
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv6
+leases for a given subnet identifier from the MySQL database.
-MYSQL_CB_GET_ALL_SUBNETS4
-=========================
+MYSQL_LB_GET_SUBID_CLIENTID
+===========================
.. code-block:: text
- retrieving all subnets
+ obtaining IPv4 lease for subnet ID %1 and client ID %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all subnets
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_SUBNETS4_RESULT
-================================
+MYSQL_LB_GET_SUBID_HWADDR
+=========================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 lease for subnet ID %1 and hardware address %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all subnets
+Logged at debug log level 50.
+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.
-MYSQL_CB_GET_ALL_SUBNETS6
-=========================
+MYSQL_LB_GET_SUBID_PAGE6
+========================
.. code-block:: text
- retrieving all subnets
+ obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all subnets
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases from the MySQL database beginning with the specified address
+for the specified subnet identifier.
-MYSQL_CB_GET_ALL_SUBNETS6_RESULT
-================================
+MYSQL_LB_GET_VERSION
+====================
.. code-block:: text
- retrieving: %1 elements
+ obtaining schema version information
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all subnets
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the MySQL database.
-MYSQL_CB_GET_CLIENT_CLASS4
-==========================
+MYSQL_LB_NEGATIVE_LEASES_STAT
+=============================
.. code-block:: text
- retrieving client class: %1
+ recount of leases returned a negative value
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a client class
+This warning message is issued when the recount of leases using counters
+in the MySQL database returned a negative value. This shows a problem
+which can be fixed only by an offline direct recount on the database.
+This message is issued only once.
-MYSQL_CB_GET_CLIENT_CLASS6
-==========================
+MYSQL_LB_NO_TLS
+===============
.. code-block:: text
- retrieving client class: %1
+ TLS was required but is not used
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a client class
+This error message is issued when TLS for the connection was required but
+TLS is not used.
-MYSQL_CB_GET_GLOBAL_PARAMETER4
-==============================
+MYSQL_LB_ROLLBACK
+=================
.. code-block:: text
- retrieving global parameter: %1
+ rolling back MySQL database
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve global parameter
+Logged at debug log level 50.
+The code has issued a rollback call. All outstanding transaction will
+be rolled back and not committed to the database.
-MYSQL_CB_GET_GLOBAL_PARAMETER6
-==============================
+MYSQL_LB_TLS_CIPHER
+===================
.. code-block:: text
- retrieving global parameter: %1
+ TLS cipher: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve global parameter
+A debug message issued when a new MySQL connected is created with TLS.
+The TLS cipher name is logged.
-MYSQL_CB_GET_HOST4
-==================
+MYSQL_LB_UPDATE_ADDR4
+=====================
.. code-block:: text
- get host
+ updating IPv4 lease for address %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve host
+Logged at debug log level 50.
+A debug message issued when the server is attempting to update IPv4
+lease from the MySQL database for the specified address.
-MYSQL_CB_GET_HOST6
-==================
+MYSQL_LB_UPDATE_ADDR6
+=====================
.. code-block:: text
- get host
+ updating IPv6 lease for address %1, lease type %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve host
+Logged at debug log level 50.
+A debug message issued when the server is attempting to update IPv6
+lease from the MySQL database for the specified address.
-MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4
-=====================================
+MYSQL_LB_UPGRADE_EXTENDED_INFO4
+===============================
.. code-block:: text
- retrieving modified client classes from: %1
+ upgrading IPv4 leases done in %1 pages with %2 updated leases
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified client classes from specified time
+The server upgraded extended info. The number of pages and the final count of
+updated leases are displayed.
-MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT
-============================================
+MYSQL_LB_UPGRADE_EXTENDED_INFO4_ERROR
+=====================================
.. code-block:: text
- retrieving: %1 elements
+ upgrading extending info for IPv4 lease at %1 failed with %2
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified client classes from specified time
+A debug message issued when the server failed to upgrade an extended info.
+The address of the lease and the error message are displayed.
-MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6
-=====================================
+MYSQL_LB_UPGRADE_EXTENDED_INFO4_PAGE
+====================================
.. code-block:: text
- retrieving modified client classes from: %1
+ upgrading IPv4 lease extended info at page %1 starting at %2 (updated %3)
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified client classes from specified time
+Logged at debug log level 50.
+A debug message issued when the server upgrades IPv4 lease extended info.
+The page number and started address, and the count of already updated leases
+are displayed.
-MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT
-============================================
+MYSQL_LB_UPGRADE_EXTENDED_INFO6
+===============================
.. code-block:: text
- retrieving: %1 elements
+ upgrading IPv6 leases done in %1 pages with %2 updated leases
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified client classes from specified time
+The server upgraded extended info. The number of pages and the final count of
+updated leases are displayed.
-MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4
-========================================
+MYSQL_LB_UPGRADE_EXTENDED_INFO6_ERROR
+=====================================
.. code-block:: text
- retrieving modified global parameters from: %1
+ upgrading extending info for IPv6 lease at %1 failed with %2
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified global parameters from specified time
+A debug message issued when the server failed to upgrade the extended info
+for a lease. The address of the lease and the error message are displayed.
-MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT
-===============================================
+*******
+NETCONF
+*******
+
+NETCONF_BOOT_UPDATE_COMPLETED
+=============================
.. code-block:: text
- retrieving: %1 elements
+ Boot-update configuration completed for server %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified global parameters from specified time
+This informational message is issued when the initial configuration
+was retrieved using NETCONF and successfully applied to Kea server.
-MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6
-========================================
+NETCONF_CONFIG_CHANGED_DETAIL
+=============================
.. code-block:: text
- retrieving modified global parameters from: %1
+ YANG configuration changed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified global parameters from specified time
+Logged at debug log level 55.
+This debug message indicates a YANG configuration change. The format
+is the change operation (created, modified, deleted or moved) followed
+by xpaths and values of old and new nodes.
-MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT
-===============================================
+NETCONF_CONFIG_CHANGE_EVENT
+===========================
.. code-block:: text
- retrieving: %1 elements
+ Received YANG configuration change %1 event
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified global parameters from specified time
+This informational message is issued when kea-netconf receives a YANG
+configuration change event. The type of event is printed.
-MYSQL_CB_GET_MODIFIED_OPTIONS4
-==============================
+NETCONF_CONFIG_CHECK_FAIL
+=========================
.. code-block:: text
- retrieving modified options from: %1
+ NETCONF configuration check failed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified options from specified time
+This error message indicates that kea-netconf had failed configuration
+check. Details are provided. Additional details may be available
+in earlier log entries, possibly on lower levels.
-MYSQL_CB_GET_MODIFIED_OPTIONS4_RESULT
-=====================================
+NETCONF_CONFIG_FAIL
+===================
.. code-block:: text
- retrieving: %1 elements
+ NETCONF configuration failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified options from specified time
+This error message indicates that kea-netconf had failed configuration
+attempt. Details are provided. Additional details may be available
+in earlier log entries, possibly on lower levels.
-MYSQL_CB_GET_MODIFIED_OPTIONS6
-==============================
+NETCONF_CONFIG_SYNTAX_WARNING
+=============================
.. code-block:: text
- retrieving modified options from: %1
+ NETCONF configuration syntax warning: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified options from specified time
+This warning message indicates that the NETCONF configuration had a minor
+syntax error. The error was displayed and the configuration parsing resumed.
-MYSQL_CB_GET_MODIFIED_OPTIONS6_RESULT
-=====================================
+NETCONF_FAILED
+==============
.. code-block:: text
- retrieving: %1 elements
+ application experienced a fatal error: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified options from specified time
+This is a fatal error message issued when kea-netconf
+got an unrecoverable error from within the event loop.
-MYSQL_CB_GET_MODIFIED_OPTION_DEFS4
-==================================
+NETCONF_GET_CONFIG
+==================
.. code-block:: text
- retrieving modified option definitions from: %1
+ got configuration from %1 server: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified option definitions from specified time
+Logged at debug log level 55.
+This debug message indicates that kea-netconf got the configuration from a
+Kea server. The server name and the retrieved configuration are printed.
-MYSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT
-=========================================
+NETCONF_GET_CONFIG_FAILED
+=========================
.. code-block:: text
- retrieving: %1 elements
+ getting configuration from %1 server failed: %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified option definitions from specified time
+The error message indicates that kea-netconf got an error getting the
+configuration from a Kea server. Make sure that the server is up and
+running, has appropriate control socket defined and that the controls
+socket configuration on the server matches that of kea-netconf. The
+name of the server and the error are printed.
-MYSQL_CB_GET_MODIFIED_OPTION_DEFS6
-==================================
+NETCONF_GET_CONFIG_STARTED
+==========================
.. code-block:: text
- retrieving modified option definitions from: %1
+ getting configuration from %1 server
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified option definitions from specified time
+This informational message indicates that kea-netconf is trying to get the
+configuration from a Kea server.
-MYSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT
-=========================================
+NETCONF_MODULE_CHANGE_INTERNAL_ERROR
+====================================
.. code-block:: text
- retrieving: %1 elements
+ an internal error occurred while processing changes for module %1: %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified option definitions from specified time
+The error message indicates that kea-netconf got an error while sysrepo was processing modules changes.
+This usually follows a config validation failure, and can be recovered from.
+The name of the module and the internal error message are printed.
-MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4
-======================================
+NETCONF_MODULE_MISSING_ERR
+==========================
.. code-block:: text
- retrieving modified shared networks from: %1
+ Missing essential module %1 in sysrepo
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified shared networks from specified time
+This fatal error message indicates that a module required by Netconf
+configuration is not available in the sysrepo repository. The name of
+the module is printed.
-MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT
-=============================================
+NETCONF_MODULE_MISSING_WARN
+===========================
.. code-block:: text
- retrieving: %1 elements
+ Missing module %1 in sysrepo
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified shared networks from specified time
+This warning message indicates that a module used by Kea is not
+available in the sysrepo repository. The name of the module is printed.
-MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6
-======================================
+NETCONF_MODULE_REVISION_ERR
+===========================
.. code-block:: text
- retrieving modified shared networks from: %1
+ Essential module %1 does NOT have the right revision: expected %2, got %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified shared networks from specified time
+This fatal error message indicates that a module required by Netconf
+configuration is not at the right revision in the sysrepo repository.
+The name, expected and available revisions of the module are printed.
-MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT
-=============================================
+NETCONF_MODULE_REVISION_WARN
+============================
.. code-block:: text
- retrieving: %1 elements
+ Module %1 does NOT have the right revision: expected %2, got %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified shared networks from specified time
+This warning message indicates that a module used by Kea is not at the
+right revision in the sysrepo repository. The name, expected and
+available revisions of the module are printed.
-MYSQL_CB_GET_MODIFIED_SUBNETS4
-==============================
+NETCONF_NOTIFICATION_INTERNAL_ERROR
+===================================
.. code-block:: text
- retrieving modified subnets from: %1
+ an internal error occurred while sending an event notification for module %1: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified subnets from specified time
+The error message indicates that kea-netconf got an error while sysrepo was sending an event notification.
+This error is not fatal and can be recovered from.
+The name of the module and the internal error message are printed.
-MYSQL_CB_GET_MODIFIED_SUBNETS4_RESULT
-=====================================
+NETCONF_NOTIFICATION_RECEIVED
+=============================
.. code-block:: text
- retrieving: %1 elements
+ Received notification of type %1 for module %2: '%3'
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified subnets from specified time
+This informational message logs any YANG notification that has been signaled
+by the server, sent to kea-netconf which then was forwarded to subscribed
+clients. To achieve this, kea-netconf subscribes itself as a client to all
+notifications for the configured module.
-MYSQL_CB_GET_MODIFIED_SUBNETS6
-==============================
+NETCONF_NOT_SUBSCRIBED_TO_NOTIFICATIONS
+=======================================
.. code-block:: text
- retrieving modified subnets from: %1
+ subscribing to notifications for %1 server with %2 module failed: %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified subnets from specified time
+The warning message indicates that kea-netconf got an error subscribing to
+notifications for a Kea server. The most probable cause is probably that the
+model that kea-netconf subscribed to does not have any notification nodes, but
+there may be other more unexpected causes as well.
+The server name, module name and the error are printed.
-MYSQL_CB_GET_MODIFIED_SUBNETS6_RESULT
-=====================================
+NETCONF_RUN_EXIT
+================
.. code-block:: text
- retrieving: %1 elements
+ application is exiting the event loop
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified subnets from specified time
+Logged at debug log level 0.
+This is a debug message issued when kea-netconf exits its
+event loop. This is a normal step during kea-netconf shutdown.
-MYSQL_CB_GET_OPTION4
-====================
+NETCONF_SET_CONFIG
+==================
.. code-block:: text
- retrieving option code: %1 space: %2
+ set configuration to %1 server: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option
+Logged at debug log level 55.
+This debug message indicates that kea-netconf set the configuration to a
+Kea server. The server name and the applied configuration are printed.
-MYSQL_CB_GET_OPTION6
-====================
+NETCONF_SET_CONFIG_FAILED
+=========================
.. code-block:: text
- retrieving option code: %1 space: %2
+ setting configuration to %1 server failed: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option
+The error message indicates that kea-netconf got an error setting the
+configuration to a Kea server. Make sure that the server is up and
+running, has appropriate control socket defined and that the controls
+socket configuration on the server matches that of kea-netconf. The
+name of the server and the error are printed.
-MYSQL_CB_GET_OPTION_DEF4
-========================
+NETCONF_SET_CONFIG_STARTED
+==========================
.. code-block:: text
- retrieving option definition code: %1 space: %2
-
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option definition
+ setting configuration to %1 server
-MYSQL_CB_GET_OPTION_DEF6
-========================
+This informational message indicates that kea-netconf is trying to set the
+configuration to a Kea server.
+
+NETCONF_STARTED
+===============
.. code-block:: text
- retrieving option definition code: %1 space: %2
+ kea-netconf (version %1) started
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option definition
+This informational message indicates that kea-netconf has processed
+all configuration information and is ready to begin processing.
+The version is also printed.
-MYSQL_CB_GET_PORT4
-==================
+NETCONF_SUBSCRIBE_CONFIG
+========================
.. code-block:: text
- get port
+ subscribing configuration changes for %1 server with %2 module
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve port
+This information message indicates that kea-netconf is trying to subscribe
+configuration changes for a Kea server. The names of the server and
+the module are printed.
-MYSQL_CB_GET_PORT6
-==================
+NETCONF_SUBSCRIBE_CONFIG_FAILED
+===============================
.. code-block:: text
- get port
+ subscribe configuration changes for %1 server with %2 module failed: %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve port
+The error message indicates that kea-netconf got an error subscribing
+configuration changes for a Kea server. The names of the server and
+the module, and the error are printed.
-MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4
-==================================
+NETCONF_SUBSCRIBE_NOTIFICATIONS
+===============================
.. code-block:: text
- retrieving audit entries from: %1 %2
+ subscribing to notifications for %1 server with %2 module
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve audit entries from specified time and id.
+This information message indicates that kea-netconf is trying to subscribe to
+notifications for a Kea server. The server name and module name are printed.
-MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT
-=========================================
+NETCONF_UPDATE_CONFIG
+=====================
.. code-block:: text
- retrieving: %1 elements
+ updating configuration with %1 server: %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve audit entries from specified time
+Logged at debug log level 55.
+This debug message indicates that kea-netconf update the configuration
+of a Kea server. The server name and the updated configuration are
+printed.
-MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6
-==================================
+NETCONF_UPDATE_CONFIG_COMPLETED
+===============================
.. code-block:: text
- retrieving audit entries from: %1 %2
+ completed updating configuration for %1 server
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve audit entries from specified time and id
+This informational message indicates that kea-netconf updated with success the
+configuration of a Kea server.
-MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT
-=========================================
+NETCONF_UPDATE_CONFIG_FAILED
+============================
.. code-block:: text
- retrieving: %1 elements
+ updating configuration with %1 server: %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve audit entries from specified time
+The error message indicates that kea-netconf got an error updating the
+configuration of a Kea server. This includes a configuration rejected
+by a Kea server when it tried to apply it. The name of the server and
+the error are printed.
-MYSQL_CB_GET_SERVER4
-====================
+NETCONF_UPDATE_CONFIG_STARTED
+=============================
.. code-block:: text
- retrieving DHCPv4 server: %1
+ started updating configuration for %1 server
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a DHCPv4 server information.
+This informational message indicates that kea-netconf is trying to update the
+configuration of a Kea server.
-MYSQL_CB_GET_SERVER6
-====================
+NETCONF_VALIDATE_CONFIG
+=======================
.. code-block:: text
- retrieving DHCPv6 server: %1
+ validating configuration with %1 server: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a DHCPv6 server information.
+Logged at debug log level 55.
+This debug message indicates that kea-netconf is validating the configuration
+with a Kea server. The server name and the validated configuration are
+printed.
-MYSQL_CB_GET_SHARED_NETWORK4
-============================
+NETCONF_VALIDATE_CONFIG_COMPLETED
+=================================
.. code-block:: text
- retrieving shared network: %1
+ completed validating configuration for %1 server
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network
+This informational message indicates that kea-netconf validated with success the
+configuration with a Kea server.
-MYSQL_CB_GET_SHARED_NETWORK6
-============================
+NETCONF_VALIDATE_CONFIG_FAILED
+==============================
.. code-block:: text
- retrieving shared network: %1
+ validating configuration with %1 server got an error: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network
+The error message indicates that kea-netconf got an error validating the
+configuration with a Kea server. This message is produced when
+exception is thrown during an attempt to validate received
+configuration. Additional explanation may be provided as a
+parameter. You may also take a look at earlier log messages. The name
+of the server and the error are printed.
-MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4
-====================================
+NETCONF_VALIDATE_CONFIG_REJECTED
+================================
.. code-block:: text
- retrieving shared network: %1 subnets
+ validating configuration with %1 server was rejected: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network subnets
+The warning message indicates that kea-netconf got an error validating the
+configuration with a Kea server. This message is printed when the
+configuration was rejected during normal processing. Additional
+explanation may be provided as a parameter. You may also take a look
+at earlier log messages. The name of the server and the error are
+printed.
-MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT
-===========================================
+*******
+PERFMON
+*******
+
+PERFMON_ALARM_CLEARED
+=====================
.. code-block:: text
- retrieving: %1 elements
+ Alarm for %1 has been cleared, reported mean duration %2 is now below low-water-ms: %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve shared network subnets
+This info message is emitted when the reported mean duration for
+an alarm that has been triggered has fallen below the value of its
+low-water-ms parameter. The arguments detail the alarm's key and
+the most recently reported mean.
-MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6
-====================================
+PERFMON_ALARM_TRIGGERED
+=======================
.. code-block:: text
- retrieving shared network: %1 subnets
+ Alarm for %1 has been triggered since %2, reported mean duration %3 exceeds high-water-ms: %4
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network subnets
+This warning message is emitted when the reported mean duration for
+an alarm exceeds its high-water-ms value. As long as the reported
+averges remain above the low-water-ms value, the alarm will remain
+triggered and this message will be repeated every alarm-report-secs.
+Arguments detail the alarm's key, the time the alarm was first
+triggered, the most recent reported mean, and the high-water-ms
+value.
-MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT
-===========================================
+PERFMON_CMDS_CONTROL_ERROR
+==========================
.. code-block:: text
- retrieving: %1 elements
+ perfmon-control command processing failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve shared network subnets
+This error message is issued when the PerfMon hook library encounters an
+error processing a perfmon-control command. The argument explains the
+command error.
-MYSQL_CB_GET_SUBNET4_BY_PREFIX
-==============================
+PERFMON_CMDS_CONTROL_OK
+=======================
.. code-block:: text
- retrieving subnet by prefix: %1
+ perfmon-control command success: active monitoring: %1, stats-mgr-reporting: %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by prefix
+This info log is issued when perfmon-control command has successfully
+enabled/disabled active monitoring and/or statistics mgr reporting.
+Arguments reflect the current state of both.
-MYSQL_CB_GET_SUBNET4_BY_SUBNET_ID
-=================================
+PERFMON_CMDS_GET_ALL_DURATIONS_ERROR
+====================================
.. code-block:: text
- retrieving subnet by subnet id: %1
+ perfmon-get-all-durations command processing failed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by subnet id
+This error message is issued when the PerfMon hook library encounters an
+error processing a perfmon-get-all-durations command. The argument explains the
+command error.
-MYSQL_CB_GET_SUBNET6_BY_PREFIX
-==============================
+PERFMON_CMDS_GET_ALL_DURATIONS_OK
+=================================
.. code-block:: text
- retrieving subnet by prefix: %1
+ perfmon-get-all-durations returning %1 durations
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by prefix
+This info log is issued when perfmon-get-all-durations command has
+completed successfully. The argument contains the number of
+durations returned.
-MYSQL_CB_GET_SUBNET6_BY_SUBNET_ID
-=================================
+PERFMON_DEINIT_OK
+=================
.. code-block:: text
- retrieving subnet by subnet id: %1
+ unloading PerfMon hooks library successful
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by subnet id
+This info message indicates that the PerfMon hooks library has been
+removed successfully.
-MYSQL_CB_GET_TYPE4
-==================
+PERFMON_DHCP4_PKT_EVENTS
+========================
.. code-block:: text
- get type
+ query: %1 events=[%2]
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve type
+Logged at debug log level 50.
+This debug message is emitted after an inbound DHCPv4 query has been
+processed, the arguments are the query label and the dump of the
+query's packet event stack.
-MYSQL_CB_GET_TYPE6
-==================
+PERFMON_DHCP4_PKT_PROCESS_ERROR
+===============================
.. code-block:: text
- get type
+ Packet event stack was not processed for query %1, reason %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve type
+Logged at debug log level 50.
+This debug message is emitted when the query's event stack could not
+be processed. This is most likely a programmatic error and should be
+reported. The arguments identify the query and the reason it could
+not be processed. These errors should not affect server's normal
+operations.
-MYSQL_CB_INIT_OK
-================
+PERFMON_DHCP4_SOCKET_RECEIVED_TIME_SUPPORT
+==========================================
.. code-block:: text
- loading MYSQL CB hooks library successful
+ Kernel supports socket received time? %1
-This informational message indicates that the MySQL Configuration Backend hooks
-library has been loaded successfully. Enjoy!
+Logged at debug log level 40.
+This debug message is emitted after a (re)configuration and indicates
+whether or not the packet filter being used by kea-dhcp4 can supply
+the timestamp a packet was received by the kernel for recording
+SOCKET_RECEIVED events. If it does not, perfmon will still function but
+will not have data available to determine kernel buffer wait times.
-MYSQL_CB_NO_TLS
-===============
+PERFMON_DHCP6_PKT_EVENTS
+========================
.. code-block:: text
- TLS was required but is not used
+ query: %1 events=[%2]
-This error message is issued when TLS for the connection was required but
-TLS is not used.
+Logged at debug log level 50.
+The debug message is emitted after an inbound DHCPv6 query has been
+processed, the arguments are the query label and the dump of the
+query's packet event stack.
-MYSQL_CB_RECONNECT_ATTEMPT_FAILED4
-==================================
+PERFMON_DHCP6_PKT_PROCESS_ERROR
+===============================
.. code-block:: text
- database reconnect failed: %1
+ Packet event stack was not processed for query %1, reason %2
-Error message issued when an attempt to reconnect has failed.
+Logged at debug log level 50.
+This debug message is emitted when the query's event stack could not
+be processed. This is most likely a programmatic error and should be
+reported. The arguments identify the query and the reason it could
+not be processed. These errors should not affect server's normal
+operations.
-MYSQL_CB_RECONNECT_ATTEMPT_FAILED6
-==================================
+PERFMON_DHCP6_SOCKET_RECEIVED_TIME_SUPPORT
+==========================================
.. code-block:: text
- database reconnect failed: %1
+ Kernel supports socket received time? %1
-Error message issued when an attempt to reconnect has failed.
+Logged at debug log level 40.
+This debug message is emitted after a (re)configuration and indicates
+whether or not the packet filter being used by kea-dhcp6 can supply
+the timestamp a packet was received by the kernel for recording
+SOCKET_RECEIVED events. If it does not, perfmon will still function but
+will not have data available to determine kernel buffer wait times.
-MYSQL_CB_RECONNECT_ATTEMPT_SCHEDULE4
-====================================
+PERFMON_INIT_FAILED
+===================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ loading PerfMon hooks library failed: %1
-Info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+This error message indicates an error during loading the PerfMon
+hooks library. The details of the error are provided as argument of
+the log message.
-MYSQL_CB_RECONNECT_ATTEMPT_SCHEDULE6
-====================================
+*****
+PGSQL
+*****
+
+PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4
+======================================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ create or update option pool start: %1 pool end: %2
-Info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by pool
-MYSQL_CB_RECONNECT_FAILED4
-==========================
+PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6
+======================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ create or update option pool start: %1 pool end: %2
-Error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by pool
-MYSQL_CB_RECONNECT_FAILED6
-==========================
+PGSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6
+========================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ create or update option prefix: %1 prefix len: %2
-Error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option by prefix
-MYSQL_CB_REGISTER_BACKEND_TYPE4
-===============================
+PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4
+===========================================
.. code-block:: text
- register backend
+ create or update option by subnet id: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to register backend
+Debug message issued when triggered an action to create or update option by subnet id
-MYSQL_CB_REGISTER_BACKEND_TYPE6
-===============================
+PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6
+===========================================
.. code-block:: text
- register backend
+ create or update option by subnet id: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to register backend
+Debug message issued when triggered an action to create or update option by subnet id
-MYSQL_CB_TLS_CIPHER
-===================
+PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS4
+====================================
.. code-block:: text
- TLS cipher: %1
+ create or update client class: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
-The TLS cipher name is logged.
+Debug message issued when triggered an action to create or update client class
-MYSQL_CB_UNREGISTER_BACKEND_TYPE4
-=================================
+PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS6
+====================================
.. code-block:: text
- unregister backend
+ create or update client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to unregister backend
-
-*******
-NETCONF
-*******
+Debug message issued when triggered an action to create or update client class
-NETCONF_BOOT_UPDATE_COMPLETED
-=============================
+PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4
+========================================
.. code-block:: text
- Boot-update configuration completed for server %1
+ create or update global parameter: %1
-This informational message is issued when the initial configuration
-was retrieved using NETCONF and successfully applied to Kea server.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update global parameter
-NETCONF_CONFIG_CHANGED_DETAIL
-=============================
+PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6
+========================================
.. code-block:: text
- YANG configuration changed: %1
+ create or update global parameter: %1
-Logged at debug log level 55.
-This debug message indicates a YANG configuration change. The format
-is the change operation (created, modified, deleted or moved) followed
-by xpaths and values of old and new nodes.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update global parameter
-NETCONF_CONFIG_CHANGE_EVENT
-===========================
+PGSQL_CB_CREATE_UPDATE_OPTION4
+==============================
.. code-block:: text
- Received YANG configuration change %1 event
+ create or update option
-This informational message is issued when kea-netconf receives a YANG
-configuration change event. The type of event is printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option
-NETCONF_CONFIG_CHECK_FAIL
-=========================
+PGSQL_CB_CREATE_UPDATE_OPTION6
+==============================
.. code-block:: text
- NETCONF configuration check failed: %1
+ create or update option
-This error message indicates that kea-netconf had failed configuration
-check. Details are provided. Additional details may be available
-in earlier log entries, possibly on lower levels.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option
-NETCONF_CONFIG_FAIL
-===================
+PGSQL_CB_CREATE_UPDATE_OPTION_DEF4
+==================================
.. code-block:: text
- NETCONF configuration failed: %1
+ create or update option definition: %1 code: %2
-This error message indicates that kea-netconf had failed configuration
-attempt. Details are provided. Additional details may be available
-in earlier log entries, possibly on lower levels.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option definition
-NETCONF_CONFIG_SYNTAX_WARNING
-=============================
+PGSQL_CB_CREATE_UPDATE_OPTION_DEF6
+==================================
.. code-block:: text
- NETCONF configuration syntax warning: %1
+ create or update option definition: %1 code: %2
-This warning message indicates that the NETCONF configuration had a minor
-syntax error. The error was displayed and the configuration parsing resumed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update option definition
-NETCONF_FAILED
-==============
+PGSQL_CB_CREATE_UPDATE_SERVER4
+==============================
.. code-block:: text
- application experienced a fatal error: %1
+ create or update server: %1
-This is a fatal error message issued when kea-netconf
-got an unrecoverable error from within the event loop.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update a DHCPv4
+server information.
-NETCONF_GET_CONFIG
-==================
+PGSQL_CB_CREATE_UPDATE_SERVER6
+==============================
.. code-block:: text
- got configuration from %1 server: %2
+ create or update server: %1
-Logged at debug log level 55.
-This debug message indicates that kea-netconf got the configuration from a
-Kea server. The server name and the retrieved configuration are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update a DHCPv6
+server information.
-NETCONF_GET_CONFIG_FAILED
-=========================
+PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK4
+======================================
.. code-block:: text
- getting configuration from %1 server failed: %2
+ create or update shared network: %1
-The error message indicates that kea-netconf got an error getting the
-configuration from a Kea server. Make sure that the server is up and
-running, has appropriate control socket defined and that the controls
-socket configuration on the server matches that of kea-netconf. The
-name of the server and the error are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network
-NETCONF_GET_CONFIG_STARTED
-==========================
+PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK6
+======================================
.. code-block:: text
- getting configuration from %1 server
+ create or update shared network: %1
-This informational message indicates that kea-netconf is trying to get the
-configuration from a Kea server.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network
-NETCONF_MODULE_CHANGE_INTERNAL_ERROR
-====================================
+PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4
+=============================================
.. code-block:: text
- an internal error occurred while processing changes for module %1: %2
+ create or update shared network: %1 option
-The error message indicates that kea-netconf got an error while sysrepo was processing modules changes.
-This usually follows a config validation failure, and can be recovered from.
-The name of the module and the internal error message are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network option
-NETCONF_MODULE_MISSING_ERR
-==========================
+PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6
+=============================================
.. code-block:: text
- Missing essential module %1 in sysrepo
+ create or update shared network: %1 option
-This fatal error message indicates that a module required by Netconf
-configuration is not available in the sysrepo repository. The name of
-the module is printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update shared network option
-NETCONF_MODULE_MISSING_WARN
-===========================
+PGSQL_CB_CREATE_UPDATE_SUBNET4
+==============================
.. code-block:: text
- Missing module %1 in sysrepo
+ create or update subnet: %1
-This warning message indicates that a module used by Kea is not
-available in the sysrepo repository. The name of the module is printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update subnet
-NETCONF_MODULE_REVISION_ERR
-===========================
+PGSQL_CB_CREATE_UPDATE_SUBNET6
+==============================
.. code-block:: text
- Essential module %1 does NOT have the right revision: expected %2, got %3
+ create or update subnet: %1
-This fatal error message indicates that a module required by Netconf
-configuration is not at the right revision in the sysrepo repository.
-The name, expected and available revisions of the module are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to create or update subnet
-NETCONF_MODULE_REVISION_WARN
-============================
+PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4
+===================================
.. code-block:: text
- Module %1 does NOT have the right revision: expected %2, got %3
+ delete all client classes
-This warning message indicates that a module used by Kea is not at the
-right revision in the sysrepo repository. The name, expected and
-available revisions of the module are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all client classes
-NETCONF_NOTIFICATION_INTERNAL_ERROR
-===================================
+PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT
+==========================================
.. code-block:: text
- an internal error occurred while sending an event notification for module %1: %2
+ deleted: %1 entries
-The error message indicates that kea-netconf got an error while sysrepo was sending an event notification.
-This error is not fatal and can be recovered from.
-The name of the module and the internal error message are printed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all client classes
-NETCONF_NOTIFICATION_RECEIVED
-=============================
+PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6
+===================================
.. code-block:: text
- Received notification of type %1 for module %2: '%3'
+ delete all client classes
-This informational message logs any YANG notification that has been signaled
-by the server, sent to kea-netconf which then was forwarded to subscribed
-clients. To achieve this, kea-netconf subscribes itself as a client to all
-notifications for the configured module.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all client classes
-NETCONF_NOT_SUBSCRIBED_TO_NOTIFICATIONS
-=======================================
+PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT
+==========================================
.. code-block:: text
- subscribing to notifications for %1 server with %2 module failed: %3
+ deleted: %1 entries
-The warning message indicates that kea-netconf got an error subscribing to
-notifications for a Kea server. The most probable cause is probably that the
-model that kea-netconf subscribed to does not have any notification nodes, but
-there may be other more unexpected causes as well.
-The server name, module name and the error are printed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all client classes
-NETCONF_RUN_EXIT
-================
+PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4
+======================================
.. code-block:: text
- application is exiting the event loop
+ delete all global parameters
-Logged at debug log level 0.
-This is a debug message issued when kea-netconf exits its
-event loop. This is a normal step during kea-netconf shutdown.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all global parameters
-NETCONF_SET_CONFIG
-==================
+PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT
+=============================================
.. code-block:: text
- set configuration to %1 server: %2
+ deleted: %1 entries
-Logged at debug log level 55.
-This debug message indicates that kea-netconf set the configuration to a
-Kea server. The server name and the applied configuration are printed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all global parameters
-NETCONF_SET_CONFIG_FAILED
-=========================
+PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6
+======================================
.. code-block:: text
- setting configuration to %1 server failed: %2
+ delete all global parameters
-The error message indicates that kea-netconf got an error setting the
-configuration to a Kea server. Make sure that the server is up and
-running, has appropriate control socket defined and that the controls
-socket configuration on the server matches that of kea-netconf. The
-name of the server and the error are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all global parameters
-NETCONF_SET_CONFIG_STARTED
-==========================
+PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT
+=============================================
.. code-block:: text
- setting configuration to %1 server
+ deleted: %1 entries
-This informational message indicates that kea-netconf is trying to set the
-configuration to a Kea server.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all global parameters
-NETCONF_STARTED
-===============
+PGSQL_CB_DELETE_ALL_OPTION_DEFS4
+================================
.. code-block:: text
- kea-netconf (version %1) started
+ delete all option definitions
-This informational message indicates that kea-netconf has processed
-all configuration information and is ready to begin processing.
-The version is also printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all option definitions
-NETCONF_SUBSCRIBE_CONFIG
-========================
+PGSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT
+=======================================
.. code-block:: text
- subscribing configuration changes for %1 server with %2 module
+ deleted: %1 entries
-This information message indicates that kea-netconf is trying to subscribe
-configuration changes for a Kea server. The names of the server and
-the module are printed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all option definitions
-NETCONF_SUBSCRIBE_CONFIG_FAILED
-===============================
+PGSQL_CB_DELETE_ALL_OPTION_DEFS6
+================================
.. code-block:: text
- subscribe configuration changes for %1 server with %2 module failed: %3
+ delete all option definitions
-The error message indicates that kea-netconf got an error subscribing
-configuration changes for a Kea server. The names of the server and
-the module, and the error are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all option definitions
-NETCONF_SUBSCRIBE_NOTIFICATIONS
-===============================
+PGSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT
+=======================================
.. code-block:: text
- subscribing to notifications for %1 server with %2 module
+ deleted: %1 entries
-This information message indicates that kea-netconf is trying to subscribe to
-notifications for a Kea server. The server name and module name are printed.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all option definitions
-NETCONF_UPDATE_CONFIG
-=====================
+PGSQL_CB_DELETE_ALL_SERVERS4
+============================
.. code-block:: text
- updating configuration with %1 server: %2
+ delete all DHCPv4 servers
-Logged at debug log level 55.
-This debug message indicates that kea-netconf update the configuration
-of a Kea server. The server name and the updated configuration are
-printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all servers.
-NETCONF_UPDATE_CONFIG_COMPLETED
-===============================
+PGSQL_CB_DELETE_ALL_SERVERS4_RESULT
+===================================
.. code-block:: text
- completed updating configuration for %1 server
+ deleted: %1 entries
-This informational message indicates that kea-netconf updated with success the
-configuration of a Kea server.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all servers.
-NETCONF_UPDATE_CONFIG_FAILED
+PGSQL_CB_DELETE_ALL_SERVERS6
============================
.. code-block:: text
- updating configuration with %1 server: %2
+ delete all DHCPv6 servers
-The error message indicates that kea-netconf got an error updating the
-configuration of a Kea server. This includes a configuration rejected
-by a Kea server when it tried to apply it. The name of the server and
-the error are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all servers.
-NETCONF_UPDATE_CONFIG_STARTED
-=============================
+PGSQL_CB_DELETE_ALL_SERVERS6_RESULT
+===================================
.. code-block:: text
- started updating configuration for %1 server
+ deleted: %1 entries
-This informational message indicates that kea-netconf is trying to update the
-configuration of a Kea server.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all servers.
-NETCONF_VALIDATE_CONFIG
-=======================
+PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4
+====================================
.. code-block:: text
- validating configuration with %1 server: %2
+ delete all shared networks
-Logged at debug log level 55.
-This debug message indicates that kea-netconf is validating the configuration
-with a Kea server. The server name and the validated configuration are
-printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all shared networks
-NETCONF_VALIDATE_CONFIG_COMPLETED
-=================================
+PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT
+===========================================
.. code-block:: text
- completed validating configuration for %1 server
+ deleted: %1 entries
-This informational message indicates that kea-netconf validated with success the
-configuration with a Kea server.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all shared networks
-NETCONF_VALIDATE_CONFIG_FAILED
-==============================
+PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6
+====================================
.. code-block:: text
- validating configuration with %1 server got an error: %2
+ delete all shared networks
-The error message indicates that kea-netconf got an error validating the
-configuration with a Kea server. This message is produced when
-exception is thrown during an attempt to validate received
-configuration. Additional explanation may be provided as a
-parameter. You may also take a look at earlier log messages. The name
-of the server and the error are printed.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all shared networks
-NETCONF_VALIDATE_CONFIG_REJECTED
-================================
+PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT
+===========================================
.. code-block:: text
- validating configuration with %1 server was rejected: %2
-
-The warning message indicates that kea-netconf got an error validating the
-configuration with a Kea server. This message is printed when the
-configuration was rejected during normal processing. Additional
-explanation may be provided as a parameter. You may also take a look
-at earlier log messages. The name of the server and the error are
-printed.
+ deleted: %1 entries
-*******
-PERFMON
-*******
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all shared networks
-PERFMON_ALARM_CLEARED
-=====================
+PGSQL_CB_DELETE_ALL_SUBNETS4
+============================
.. code-block:: text
- Alarm for %1 has been cleared, reported mean duration %2 is now below low-water-ms: %3
+ delete all subnets
-This info message is emitted when the reported mean duration for
-an alarm that has been triggered has fallen below the value of its
-low-water-ms parameter. The arguments detail the alarm's key and
-the most recently reported mean.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all subnets
-PERFMON_ALARM_TRIGGERED
-=======================
+PGSQL_CB_DELETE_ALL_SUBNETS4_RESULT
+===================================
.. code-block:: text
- Alarm for %1 has been triggered since %2, reported mean duration %3 exceeds high-water-ms: %4
+ deleted: %1 entries
-This warning message is emitted when the reported mean duration for
-an alarm exceeds its high-water-ms value. As long as the reported
-averges remain above the low-water-ms value, the alarm will remain
-triggered and this message will be repeated every alarm-report-secs.
-Arguments detail the alarm's key, the time the alarm was first
-triggered, the most recent reported mean, and the high-water-ms
-value.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all subnets
-PERFMON_CMDS_CONTROL_ERROR
-==========================
+PGSQL_CB_DELETE_ALL_SUBNETS6
+============================
.. code-block:: text
- perfmon-control command processing failed: %1
+ delete all subnets
-This error message is issued when the PerfMon hook library encounters an
-error processing a perfmon-control command. The argument explains the
-command error.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete all subnets
-PERFMON_CMDS_CONTROL_OK
-=======================
+PGSQL_CB_DELETE_ALL_SUBNETS6_RESULT
+===================================
.. code-block:: text
- perfmon-control command success: active monitoring: %1, stats-mgr-reporting: %2
+ deleted: %1 entries
-This info log is issued when perfmon-control command has successfully
-enabled/disabled active monitoring and/or statistics mgr reporting.
-Arguments reflect the current state of both.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete all subnets
-PERFMON_CMDS_GET_ALL_DURATIONS_ERROR
-====================================
+PGSQL_CB_DELETE_BY_POOL_OPTION4
+===============================
.. code-block:: text
- perfmon-get-all-durations command processing failed: %1
+ delete pool start: %1 pool end: %2 option code: %3 space: %4
-This error message is issued when the PerfMon hook library encounters an
-error processing a perfmon-get-all-durations command. The argument explains the
-command error.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by pool
-PERFMON_CMDS_GET_ALL_DURATIONS_OK
-=================================
+PGSQL_CB_DELETE_BY_POOL_OPTION4_RESULT
+======================================
.. code-block:: text
- perfmon-get-all-durations returning %1 durations
+ deleted: %1 entries
-This info log is issued when perfmon-get-all-durations command has
-completed successfully. The argument contains the number of
-durations returned.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by pool
-PERFMON_DEINIT_OK
-=================
+PGSQL_CB_DELETE_BY_POOL_OPTION6
+===============================
.. code-block:: text
- unloading PerfMon hooks library successful
+ delete pool start: %1 pool end: %2 option code: %3 space: %4
-This info message indicates that the PerfMon hooks library has been
-removed successfully.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by pool
-PERFMON_DHCP4_PKT_EVENTS
-========================
+PGSQL_CB_DELETE_BY_POOL_OPTION6_RESULT
+======================================
.. code-block:: text
- query: %1 events=[%2]
+ deleted: %1 entries
-Logged at debug log level 50.
-This debug message is emitted after an inbound DHCPv4 query has been
-processed, the arguments are the query label and the dump of the
-query's packet event stack.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option by pool
-PERFMON_DHCP4_PKT_PROCESS_ERROR
-===============================
+PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6
+======================================
.. code-block:: text
- Packet event stack was not processed for query %1, reason %2
+ delete prefix: %1 prefix len: %2 option code: %3 space: %4
-Logged at debug log level 50.
-This debug message is emitted when the query's event stack could not
-be processed. This is most likely a programmatic error and should be
-reported. The arguments identify the query and the reason it could
-not be processed. These errors should not affect server's normal
-operations.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete option by prefix
-PERFMON_DHCP4_SOCKET_RECEIVED_TIME_SUPPORT
-==========================================
+PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT
+=============================================
.. code-block:: text
- Kernel supports socket received time? %1
+ deleted: %1 entries
Logged at debug log level 40.
-This debug message is emitted after a (re)configuration and indicates
-whether or not the packet filter being used by kea-dhcp4 can supply
-the timestamp a packet was received by the kernel for recording
-SOCKET_RECEIVED events. If it does not, perfmon will still function but
-will not have data available to determine kernel buffer wait times.
+Debug message indicating the result of an action to delete option by prefix
-PERFMON_DHCP6_PKT_EVENTS
-========================
+PGSQL_CB_DELETE_BY_PREFIX_SUBNET4
+=================================
.. code-block:: text
- query: %1 events=[%2]
+ delete subnet by prefix: %1
-Logged at debug log level 50.
-The debug message is emitted after an inbound DHCPv6 query has been
-processed, the arguments are the query label and the dump of the
-query's packet event stack.
+Logged at debug log level 40.
+Debug message issued when triggered an action to delete subnet by prefix
-PERFMON_DHCP6_PKT_PROCESS_ERROR
-===============================
+PGSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT
+========================================
.. code-block:: text
- Packet event stack was not processed for query %1, reason %2
+ deleted: %1 entries
-Logged at debug log level 50.
-This debug message is emitted when the query's event stack could not
-be processed. This is most likely a programmatic error and should be
-reported. The arguments identify the query and the reason it could
-not be processed. These errors should not affect server's normal
-operations.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by prefix
-PERFMON_DHCP6_SOCKET_RECEIVED_TIME_SUPPORT
-==========================================
+PGSQL_CB_DELETE_BY_PREFIX_SUBNET6
+=================================
.. code-block:: text
- Kernel supports socket received time? %1
+ delete subnet by prefix: %1
Logged at debug log level 40.
-This debug message is emitted after a (re)configuration and indicates
-whether or not the packet filter being used by kea-dhcp6 can supply
-the timestamp a packet was received by the kernel for recording
-SOCKET_RECEIVED events. If it does not, perfmon will still function but
-will not have data available to determine kernel buffer wait times.
+Debug message issued when triggered an action to delete subnet by prefix
-PERFMON_INIT_FAILED
-===================
+PGSQL_CB_DELETE_BY_PREFIX_SUBNET6_RESULT
+========================================
.. code-block:: text
- loading PerfMon hooks library failed: %1
-
-This error message indicates an error during loading the PerfMon
-hooks library. The details of the error are provided as argument of
-the log message.
+ deleted: %1 entries
-*****
-PGSQL
-*****
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete subnet by prefix
-PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4
-======================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4
+====================================
.. code-block:: text
- create or update option pool start: %1 pool end: %2
+ delete by subnet id: %1 option code: %2 space: %3
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by pool
+Debug message issued when triggered an action to delete option by subnet id
-PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6
-======================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT
+===========================================
.. code-block:: text
- create or update option pool start: %1 pool end: %2
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by pool
+Debug message indicating the result of an action to delete option by subnet id
-PGSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6
-========================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6
+====================================
.. code-block:: text
- create or update option prefix: %1 prefix len: %2
+ delete by subnet id: %1 option code: %2 space: %3
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by prefix
+Debug message issued when triggered an action to delete option by subnet id
-PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4
+PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT
===========================================
.. code-block:: text
- create or update option by subnet id: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by subnet id
+Debug message indicating the result of an action to delete option by subnet id
-PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6
-===========================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4
+====================================
.. code-block:: text
- create or update option by subnet id: %1
+ delete subnet by subnet id: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option by subnet id
+Debug message issued when triggered an action to delete subnet by subnet id
-PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS4
-====================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT
+===========================================
.. code-block:: text
- create or update client class: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update client class
+Debug message indicating the result of an action to delete subnet by subnet id
-PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS6
+PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6
====================================
.. code-block:: text
- create or update client class: %1
+ delete subnet by subnet id: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update client class
+Debug message issued when triggered an action to delete subnet by subnet id
-PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4
-========================================
+PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT
+===========================================
.. code-block:: text
- create or update global parameter: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update global parameter
+Debug message indicating the result of an action to delete subnet by subnet id
-PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6
-========================================
+PGSQL_CB_DELETE_CLIENT_CLASS4
+=============================
.. code-block:: text
- create or update global parameter: %1
+ delete client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update global parameter
+Debug message issued when triggered an action to delete client class
-PGSQL_CB_CREATE_UPDATE_OPTION4
-==============================
+PGSQL_CB_DELETE_CLIENT_CLASS4_RESULT
+====================================
.. code-block:: text
- create or update option
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option
+Debug message indicating the result of an action to delete client class
-PGSQL_CB_CREATE_UPDATE_OPTION6
-==============================
+PGSQL_CB_DELETE_CLIENT_CLASS6
+=============================
.. code-block:: text
- create or update option
+ delete client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option
+Debug message issued when triggered an action to delete client class
-PGSQL_CB_CREATE_UPDATE_OPTION_DEF4
-==================================
+PGSQL_CB_DELETE_CLIENT_CLASS6_RESULT
+====================================
.. code-block:: text
- create or update option definition: %1 code: %2
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option definition
+Debug message indicating the result of an action to delete client class
-PGSQL_CB_CREATE_UPDATE_OPTION_DEF6
-==================================
+PGSQL_CB_DELETE_GLOBAL_PARAMETER4
+=================================
.. code-block:: text
- create or update option definition: %1 code: %2
+ delete global parameter: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update option definition
+Debug message issued when triggered an action to delete global parameter
-PGSQL_CB_CREATE_UPDATE_SERVER4
-==============================
+PGSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT
+========================================
.. code-block:: text
- create or update server: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update a DHCPv4
-server information.
+Debug message indicating the result of an action to delete global parameter
-PGSQL_CB_CREATE_UPDATE_SERVER6
-==============================
+PGSQL_CB_DELETE_GLOBAL_PARAMETER6
+=================================
.. code-block:: text
- create or update server: %1
+ delete global parameter: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update a DHCPv6
-server information.
+Debug message issued when triggered an action to delete global parameter
-PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK4
-======================================
+PGSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT
+========================================
.. code-block:: text
- create or update shared network: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network
+Debug message indicating the result of an action to delete global parameter
-PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK6
-======================================
+PGSQL_CB_DELETE_OPTION4
+=======================
.. code-block:: text
- create or update shared network: %1
+ delete option code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network
+Debug message issued when triggered an action to delete option
-PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4
-=============================================
+PGSQL_CB_DELETE_OPTION4_RESULT
+==============================
.. code-block:: text
- create or update shared network: %1 option
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network option
+Debug message indicating the result of an action to delete option
-PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6
-=============================================
+PGSQL_CB_DELETE_OPTION6
+=======================
.. code-block:: text
- create or update shared network: %1 option
+ delete option code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update shared network option
+Debug message issued when triggered an action to delete option
-PGSQL_CB_CREATE_UPDATE_SUBNET4
+PGSQL_CB_DELETE_OPTION6_RESULT
==============================
.. code-block:: text
- create or update subnet: %1
+ deleted: %1 entries
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update subnet
+Debug message indicating the result of an action to delete option
-PGSQL_CB_CREATE_UPDATE_SUBNET6
-==============================
+PGSQL_CB_DELETE_OPTION_DEF4
+===========================
.. code-block:: text
- create or update subnet: %1
+ delete option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to create or update subnet
+Debug message issued when triggered an action to delete option definition
-PGSQL_CB_DEINIT_OK
-==================
+PGSQL_CB_DELETE_OPTION_DEF4_RESULT
+==================================
.. code-block:: text
- unloading Postgres CB hooks library successful
+ deleted: %1 entries
-This informational message indicates that the Postgres Configuration Backend hooks
-library has been unloaded successfully.
+Logged at debug log level 40.
+Debug message indicating the result of an action to delete option definition
-PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4
-===================================
+PGSQL_CB_DELETE_OPTION_DEF6
+===========================
.. code-block:: text
- delete all client classes
+ delete option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all client classes
+Debug message issued when triggered an action to delete option definition
-PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT
-==========================================
+PGSQL_CB_DELETE_OPTION_DEF6_RESULT
+==================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all client classes
+Debug message indicating the result of an action to delete option definition
-PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6
-===================================
+PGSQL_CB_DELETE_SERVER4
+=======================
.. code-block:: text
- delete all client classes
+ delete DHCPv4 server: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all client classes
+Debug message issued when triggered an action to delete a server.
-PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT
-==========================================
+PGSQL_CB_DELETE_SERVER4_RESULT
+==============================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all client classes
+Debug message indicating the result of an action to delete a server.
-PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4
-======================================
+PGSQL_CB_DELETE_SERVER6
+=======================
.. code-block:: text
- delete all global parameters
+ delete DHCPv6 server: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all global parameters
+Debug message issued when triggered an action to delete a server.
-PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT
-=============================================
+PGSQL_CB_DELETE_SERVER6_RESULT
+==============================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all global parameters
+Debug message indicating the result of an action to delete a server.
-PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6
-======================================
+PGSQL_CB_DELETE_SHARED_NETWORK4
+===============================
.. code-block:: text
- delete all global parameters
+ delete shared network: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all global parameters
+Debug message issued when triggered an action to delete shared network
-PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT
-=============================================
+PGSQL_CB_DELETE_SHARED_NETWORK4_RESULT
+======================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all global parameters
+Debug message indicating the result of an action to delete shared network
-PGSQL_CB_DELETE_ALL_OPTION_DEFS4
-================================
+PGSQL_CB_DELETE_SHARED_NETWORK6
+===============================
.. code-block:: text
- delete all option definitions
+ delete shared network: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all option definitions
+Debug message issued when triggered an action to delete shared network
-PGSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT
-=======================================
+PGSQL_CB_DELETE_SHARED_NETWORK6_RESULT
+======================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all option definitions
+Debug message indicating the result of an action to delete shared network
-PGSQL_CB_DELETE_ALL_OPTION_DEFS6
-================================
+PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4
+======================================
.. code-block:: text
- delete all option definitions
+ delete shared network: %1 option code: %2 space: %3
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all option definitions
+Debug message issued when triggered an action to delete shared network option
-PGSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT
-=======================================
+PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT
+=============================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all option definitions
+Debug message indicating the result of an action to delete shared network option
-PGSQL_CB_DELETE_ALL_SERVERS4
-============================
+PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6
+======================================
.. code-block:: text
- delete all DHCPv4 servers
+ delete shared network: %1 option code: %2 space: %3
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all servers.
+Debug message issued when triggered an action to delete shared network option
-PGSQL_CB_DELETE_ALL_SERVERS4_RESULT
-===================================
+PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT
+=============================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all servers.
+Debug message indicating the result of an action to delete shared network option
-PGSQL_CB_DELETE_ALL_SERVERS6
-============================
+PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4
+=======================================
.. code-block:: text
- delete all DHCPv6 servers
+ delete shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all servers.
+Debug message issued when triggered an action to delete shared network subnets
-PGSQL_CB_DELETE_ALL_SERVERS6_RESULT
-===================================
+PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT
+==============================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all servers.
+Debug message indicating the result of an action to delete shared network subnets
-PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4
-====================================
+PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6
+=======================================
.. code-block:: text
- delete all shared networks
+ delete shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all shared networks
+Debug message issued when triggered an action to delete shared network subnets
-PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT
-===========================================
+PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT
+==============================================
.. code-block:: text
deleted: %1 entries
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all shared networks
+Debug message indicating the result of an action to delete shared network subnets
-PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6
-====================================
+PGSQL_CB_GET_ALL_CLIENT_CLASSES4
+================================
.. code-block:: text
- delete all shared networks
+ retrieving all client classes
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all shared networks
+Debug message issued when triggered an action to retrieve all client classes
-PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT
-===========================================
+PGSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT
+=======================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all shared networks
+Debug message indicating the result of an action to retrieve all client classes
-PGSQL_CB_DELETE_ALL_SUBNETS4
-============================
+PGSQL_CB_GET_ALL_CLIENT_CLASSES6
+================================
.. code-block:: text
- delete all subnets
+ retrieving all client classes
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all subnets
+Debug message issued when triggered an action to retrieve all client classes
-PGSQL_CB_DELETE_ALL_SUBNETS4_RESULT
-===================================
+PGSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT
+=======================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all subnets
+Debug message indicating the result of an action to retrieve all client classes
-PGSQL_CB_DELETE_ALL_SUBNETS6
-============================
+PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4
+===================================
.. code-block:: text
- delete all subnets
+ retrieving all global parameters
Logged at debug log level 40.
-Debug message issued when triggered an action to delete all subnets
+Debug message issued when triggered an action to retrieve all global parameters
-PGSQL_CB_DELETE_ALL_SUBNETS6_RESULT
-===================================
+PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT
+==========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete all subnets
+Debug message indicating the result of an action to retrieve all global parameters
-PGSQL_CB_DELETE_BY_POOL_OPTION4
-===============================
+PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6
+===================================
.. code-block:: text
- delete pool start: %1 pool end: %2 option code: %3 space: %4
+ retrieving all global parameters
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by pool
+Debug message issued when triggered an action to retrieve all global parameters
-PGSQL_CB_DELETE_BY_POOL_OPTION4_RESULT
-======================================
+PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT
+==========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by pool
+Debug message indicating the result of an action to retrieve all global parameters
-PGSQL_CB_DELETE_BY_POOL_OPTION6
-===============================
+PGSQL_CB_GET_ALL_OPTIONS4
+=========================
.. code-block:: text
- delete pool start: %1 pool end: %2 option code: %3 space: %4
+ retrieving all options
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by pool
+Debug message issued when triggered an action to retrieve all options
-PGSQL_CB_DELETE_BY_POOL_OPTION6_RESULT
-======================================
+PGSQL_CB_GET_ALL_OPTIONS4_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by pool
+Debug message indicating the result of an action to retrieve all options
-PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6
-======================================
+PGSQL_CB_GET_ALL_OPTIONS6
+=========================
.. code-block:: text
- delete prefix: %1 prefix len: %2 option code: %3 space: %4
+ retrieving all options
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by prefix
+Debug message issued when triggered an action to retrieve all options
-PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT
-=============================================
+PGSQL_CB_GET_ALL_OPTIONS6_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by prefix
+Debug message indicating the result of an action to retrieve all options
-PGSQL_CB_DELETE_BY_PREFIX_SUBNET4
-=================================
+PGSQL_CB_GET_ALL_OPTION_DEFS4
+=============================
.. code-block:: text
- delete subnet by prefix: %1
+ retrieving all option definitions
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by prefix
+Debug message issued when triggered an action to retrieve all option definitions
-PGSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT
-========================================
+PGSQL_CB_GET_ALL_OPTION_DEFS4_RESULT
+====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by prefix
+Debug message indicating the result of an action to retrieve all option definitions
-PGSQL_CB_DELETE_BY_PREFIX_SUBNET6
-=================================
+PGSQL_CB_GET_ALL_OPTION_DEFS6
+=============================
.. code-block:: text
- delete subnet by prefix: %1
+ retrieving all option definitions
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by prefix
+Debug message issued when triggered an action to retrieve all option definitions
-PGSQL_CB_DELETE_BY_PREFIX_SUBNET6_RESULT
-========================================
+PGSQL_CB_GET_ALL_OPTION_DEFS6_RESULT
+====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by prefix
+Debug message indicating the result of an action to retrieve all option definitions
-PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4
-====================================
+PGSQL_CB_GET_ALL_SERVERS4
+=========================
.. code-block:: text
- delete by subnet id: %1 option code: %2 space: %3
+ retrieving all servers
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by subnet id
+Debug message issued when triggered an action to retrieve all DHCPv4
+servers
-PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT
-===========================================
+PGSQL_CB_GET_ALL_SERVERS4_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by subnet id
+Debug message indicating the result of an action to retrieve all DHCPv4
+servers
-PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6
-====================================
+PGSQL_CB_GET_ALL_SERVERS6
+=========================
.. code-block:: text
- delete by subnet id: %1 option code: %2 space: %3
+ retrieving all DHCPv6 servers
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option by subnet id
+Debug message issued when triggered an action to retrieve all DHCPv6
+servers
-PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT
-===========================================
+PGSQL_CB_GET_ALL_SERVERS6_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option by subnet id
+Debug message indicating the result of an action to retrieve all DHCPv6
+servers
-PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4
-====================================
+PGSQL_CB_GET_ALL_SHARED_NETWORKS4
+=================================
.. code-block:: text
- delete subnet by subnet id: %1
+ retrieving all shared networks
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by subnet id
+Debug message issued when triggered an action to retrieve all shared networks
-PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT
-===========================================
+PGSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT
+========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by subnet id
+Debug message indicating the result of an action to retrieve all shared networks
-PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6
-====================================
+PGSQL_CB_GET_ALL_SHARED_NETWORKS6
+=================================
.. code-block:: text
- delete subnet by subnet id: %1
+ retrieving all shared networks
Logged at debug log level 40.
-Debug message issued when triggered an action to delete subnet by subnet id
+Debug message issued when triggered an action to retrieve all shared networks
-PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT
-===========================================
+PGSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT
+========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete subnet by subnet id
+Debug message indicating the result of an action to retrieve all shared networks
-PGSQL_CB_DELETE_CLIENT_CLASS4
-=============================
+PGSQL_CB_GET_ALL_SUBNETS4
+=========================
.. code-block:: text
- delete client class: %1
+ retrieving all subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete client class
+Debug message issued when triggered an action to retrieve all subnets
-PGSQL_CB_DELETE_CLIENT_CLASS4_RESULT
-====================================
+PGSQL_CB_GET_ALL_SUBNETS4_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete client class
+Debug message indicating the result of an action to retrieve all subnets
-PGSQL_CB_DELETE_CLIENT_CLASS6
-=============================
+PGSQL_CB_GET_ALL_SUBNETS6
+=========================
.. code-block:: text
- delete client class: %1
+ retrieving all subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to delete client class
+Debug message issued when triggered an action to retrieve all subnets
-PGSQL_CB_DELETE_CLIENT_CLASS6_RESULT
-====================================
+PGSQL_CB_GET_ALL_SUBNETS6_RESULT
+================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete client class
+Debug message indicating the result of an action to retrieve all subnets
-PGSQL_CB_DELETE_GLOBAL_PARAMETER4
-=================================
+PGSQL_CB_GET_CLIENT_CLASS4
+==========================
.. code-block:: text
- delete global parameter: %1
+ retrieving client class: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete global parameter
+Debug message issued when triggered an action to retrieve a client class
-PGSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT
-========================================
+PGSQL_CB_GET_CLIENT_CLASS6
+==========================
.. code-block:: text
- deleted: %1 entries
+ retrieving client class: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete global parameter
+Debug message issued when triggered an action to retrieve a client class
-PGSQL_CB_DELETE_GLOBAL_PARAMETER6
-=================================
+PGSQL_CB_GET_GLOBAL_PARAMETER4
+==============================
.. code-block:: text
- delete global parameter: %1
+ retrieving global parameter: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete global parameter
+Debug message issued when triggered an action to retrieve global parameter
-PGSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT
-========================================
+PGSQL_CB_GET_GLOBAL_PARAMETER6
+==============================
.. code-block:: text
- deleted: %1 entries
+ retrieving global parameter: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to delete global parameter
+Debug message issued when triggered an action to retrieve global parameter
-PGSQL_CB_DELETE_OPTION4
-=======================
+PGSQL_CB_GET_HOST4
+==================
.. code-block:: text
- delete option code: %1 space: %2
+ get host
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option
+Debug message issued when triggered an action to retrieve host
-PGSQL_CB_DELETE_OPTION4_RESULT
-==============================
+PGSQL_CB_GET_HOST6
+==================
.. code-block:: text
- deleted: %1 entries
+ get host
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option
+Debug message issued when triggered an action to retrieve host
-PGSQL_CB_DELETE_OPTION6
-=======================
+PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4
+=====================================
.. code-block:: text
- delete option code: %1 space: %2
+ retrieving modified client classes from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option
+Debug message issued when triggered an action to retrieve modified client classes from specified time
-PGSQL_CB_DELETE_OPTION6_RESULT
-==============================
+PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT
+============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option
+Debug message indicating the result of an action to retrieve modified client classes from specified time
-PGSQL_CB_DELETE_OPTION_DEF4
-===========================
+PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6
+=====================================
.. code-block:: text
- delete option definition code: %1 space: %2
+ retrieving modified client classes from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option definition
-
-PGSQL_CB_DELETE_OPTION_DEF4_RESULT
-==================================
+Debug message issued when triggered an action to retrieve modified client classes from specified time
+
+PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT
+============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option definition
+Debug message indicating the result of an action to retrieve modified client classes from specified time
-PGSQL_CB_DELETE_OPTION_DEF6
-===========================
+PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4
+========================================
.. code-block:: text
- delete option definition code: %1 space: %2
+ retrieving modified global parameters from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete option definition
+Debug message issued when triggered an action to retrieve modified global parameters from specified time
-PGSQL_CB_DELETE_OPTION_DEF6_RESULT
-==================================
+PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT
+===============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete option definition
+Debug message indicating the result of an action to retrieve modified global parameters from specified time
-PGSQL_CB_DELETE_SERVER4
-=======================
+PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6
+========================================
.. code-block:: text
- delete DHCPv4 server: %1
+ retrieving modified global parameters from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete a server.
+Debug message issued when triggered an action to retrieve modified global parameters from specified time
-PGSQL_CB_DELETE_SERVER4_RESULT
-==============================
+PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT
+===============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete a server.
+Debug message indicating the result of an action to retrieve modified global parameters from specified time
-PGSQL_CB_DELETE_SERVER6
-=======================
+PGSQL_CB_GET_MODIFIED_OPTIONS4
+==============================
.. code-block:: text
- delete DHCPv6 server: %1
+ retrieving modified options from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete a server.
+Debug message issued when triggered an action to retrieve modified options from specified time
-PGSQL_CB_DELETE_SERVER6_RESULT
-==============================
+PGSQL_CB_GET_MODIFIED_OPTIONS4_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete a server.
+Debug message indicating the result of an action to retrieve modified options from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK4
-===============================
+PGSQL_CB_GET_MODIFIED_OPTIONS6
+==============================
.. code-block:: text
- delete shared network: %1
+ retrieving modified options from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network
+Debug message issued when triggered an action to retrieve modified options from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK4_RESULT
-======================================
+PGSQL_CB_GET_MODIFIED_OPTIONS6_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network
+Debug message indicating the result of an action to retrieve modified options from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK6
-===============================
+PGSQL_CB_GET_MODIFIED_OPTION_DEFS4
+==================================
.. code-block:: text
- delete shared network: %1
+ retrieving modified option definitions from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network
+Debug message issued when triggered an action to retrieve modified option definitions from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK6_RESULT
-======================================
+PGSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network
+Debug message indicating the result of an action to retrieve modified option definitions from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4
-======================================
+PGSQL_CB_GET_MODIFIED_OPTION_DEFS6
+==================================
.. code-block:: text
- delete shared network: %1 option code: %2 space: %3
+ retrieving modified option definitions from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network option
+Debug message issued when triggered an action to retrieve modified option definitions from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT
-=============================================
+PGSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT
+=========================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network option
+Debug message indicating the result of an action to retrieve modified option definitions from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6
+PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4
======================================
.. code-block:: text
- delete shared network: %1 option code: %2 space: %3
+ retrieving modified shared networks from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network option
+Debug message issued when triggered an action to retrieve modified shared networks from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT
+PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT
=============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network option
+Debug message indicating the result of an action to retrieve modified shared networks from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4
-=======================================
+PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6
+======================================
.. code-block:: text
- delete shared network: %1 subnets
+ retrieving modified shared networks from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network subnets
+Debug message issued when triggered an action to retrieve modified shared networks from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT
-==============================================
+PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT
+=============================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network subnets
+Debug message indicating the result of an action to retrieve modified shared networks from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6
-=======================================
+PGSQL_CB_GET_MODIFIED_SUBNETS4
+==============================
.. code-block:: text
- delete shared network: %1 subnets
+ retrieving modified subnets from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to delete shared network subnets
+Debug message issued when triggered an action to retrieve modified subnets from specified time
-PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT
-==============================================
+PGSQL_CB_GET_MODIFIED_SUBNETS4_RESULT
+=====================================
.. code-block:: text
- deleted: %1 entries
+ retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to delete shared network subnets
+Debug message indicating the result of an action to retrieve modified subnets from specified time
-PGSQL_CB_GET_ALL_CLIENT_CLASSES4
-================================
+PGSQL_CB_GET_MODIFIED_SUBNETS6
+==============================
.. code-block:: text
- retrieving all client classes
+ retrieving modified subnets from: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all client classes
+Debug message issued when triggered an action to retrieve modified subnets from specified time
-PGSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT
-=======================================
+PGSQL_CB_GET_MODIFIED_SUBNETS6_RESULT
+=====================================
.. code-block:: text
retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all client classes
+Debug message indicating the result of an action to retrieve modified subnets from specified time
-PGSQL_CB_GET_ALL_CLIENT_CLASSES6
-================================
+PGSQL_CB_GET_OPTION4
+====================
.. code-block:: text
- retrieving all client classes
+ retrieving option code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all client classes
+Debug message issued when triggered an action to retrieve option
-PGSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT
-=======================================
+PGSQL_CB_GET_OPTION6
+====================
.. code-block:: text
- retrieving: %1 elements
+ retrieving option code: %1 space: %2
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all client classes
+Debug message issued when triggered an action to retrieve option
-PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4
-===================================
+PGSQL_CB_GET_OPTION_DEF4
+========================
.. code-block:: text
- retrieving all global parameters
+ retrieving option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all global parameters
+Debug message issued when triggered an action to retrieve option definition
-PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT
-==========================================
+PGSQL_CB_GET_OPTION_DEF6
+========================
.. code-block:: text
- retrieving: %1 elements
+ retrieving option definition code: %1 space: %2
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all global parameters
+Debug message issued when triggered an action to retrieve option definition
-PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6
-===================================
+PGSQL_CB_GET_PORT4
+==================
.. code-block:: text
- retrieving all global parameters
+ get port
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all global parameters
+Debug message issued when triggered an action to retrieve port
-PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT
-==========================================
+PGSQL_CB_GET_PORT6
+==================
.. code-block:: text
- retrieving: %1 elements
+ get port
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all global parameters
+Debug message issued when triggered an action to retrieve port
-PGSQL_CB_GET_ALL_OPTIONS4
-=========================
+PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4
+==================================
.. code-block:: text
- retrieving all options
+ retrieving audit entries from: %1 %2
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all options
+Debug message issued when triggered an action to retrieve audit entries from specified time and id.
-PGSQL_CB_GET_ALL_OPTIONS4_RESULT
-================================
+PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT
+=========================================
.. code-block:: text
retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all options
+Debug message indicating the result of an action to retrieve audit entries from specified time
-PGSQL_CB_GET_ALL_OPTIONS6
-=========================
+PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6
+==================================
.. code-block:: text
- retrieving all options
+ retrieving audit entries from: %1 %2
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all options
+Debug message issued when triggered an action to retrieve audit entries from specified time and id
-PGSQL_CB_GET_ALL_OPTIONS6_RESULT
-================================
+PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT
+=========================================
.. code-block:: text
retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all options
+Debug message indicating the result of an action to retrieve audit entries from specified time
-PGSQL_CB_GET_ALL_OPTION_DEFS4
-=============================
+PGSQL_CB_GET_SERVER4
+====================
.. code-block:: text
- retrieving all option definitions
+ retrieving DHCPv4 server: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all option definitions
+Debug message issued when triggered an action to retrieve a DHCPv4 server information.
-PGSQL_CB_GET_ALL_OPTION_DEFS4_RESULT
-====================================
+PGSQL_CB_GET_SERVER6
+====================
.. code-block:: text
- retrieving: %1 elements
+ retrieving DHCPv6 server: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all option definitions
-
-PGSQL_CB_GET_ALL_OPTION_DEFS6
-=============================
+Debug message issued when triggered an action to retrieve a DHCPv6 server information.
+
+PGSQL_CB_GET_SHARED_NETWORK4
+============================
.. code-block:: text
- retrieving all option definitions
+ retrieving shared network: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all option definitions
+Debug message issued when triggered an action to retrieve shared network
-PGSQL_CB_GET_ALL_OPTION_DEFS6_RESULT
-====================================
+PGSQL_CB_GET_SHARED_NETWORK6
+============================
.. code-block:: text
- retrieving: %1 elements
+ retrieving shared network: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all option definitions
+Debug message issued when triggered an action to retrieve shared network
-PGSQL_CB_GET_ALL_SERVERS4
-=========================
+PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4
+====================================
.. code-block:: text
- retrieving all servers
+ retrieving shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all DHCPv4
-servers
+Debug message issued when triggered an action to retrieve shared network subnets
-PGSQL_CB_GET_ALL_SERVERS4_RESULT
-================================
+PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT
+===========================================
.. code-block:: text
retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all DHCPv4
-servers
+Debug message indicating the result of an action to retrieve shared network subnets
-PGSQL_CB_GET_ALL_SERVERS6
-=========================
+PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6
+====================================
.. code-block:: text
- retrieving all DHCPv6 servers
+ retrieving shared network: %1 subnets
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all DHCPv6
-servers
+Debug message issued when triggered an action to retrieve shared network subnets
-PGSQL_CB_GET_ALL_SERVERS6_RESULT
-================================
+PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT
+===========================================
.. code-block:: text
retrieving: %1 elements
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all DHCPv6
-servers
+Debug message indicating the result of an action to retrieve shared network subnets
-PGSQL_CB_GET_ALL_SHARED_NETWORKS4
-=================================
+PGSQL_CB_GET_SUBNET4_BY_PREFIX
+==============================
.. code-block:: text
- retrieving all shared networks
+ retrieving subnet by prefix: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all shared networks
+Debug message issued when triggered an action to retrieve subnet by prefix
-PGSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT
-========================================
+PGSQL_CB_GET_SUBNET4_BY_SUBNET_ID
+=================================
.. code-block:: text
- retrieving: %1 elements
+ retrieving subnet by subnet id: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all shared networks
+Debug message issued when triggered an action to retrieve subnet by subnet id
-PGSQL_CB_GET_ALL_SHARED_NETWORKS6
-=================================
+PGSQL_CB_GET_SUBNET6_BY_PREFIX
+==============================
.. code-block:: text
- retrieving all shared networks
+ retrieving subnet by prefix: %1
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all shared networks
+Debug message issued when triggered an action to retrieve subnet by prefix
-PGSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT
-========================================
+PGSQL_CB_GET_SUBNET6_BY_SUBNET_ID
+=================================
.. code-block:: text
- retrieving: %1 elements
+ retrieving subnet by subnet id: %1
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all shared networks
+Debug message issued when triggered an action to retrieve subnet by subnet id
-PGSQL_CB_GET_ALL_SUBNETS4
-=========================
+PGSQL_CB_GET_TYPE4
+==================
.. code-block:: text
- retrieving all subnets
+ get type
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all subnets
+Debug message issued when triggered an action to retrieve type
-PGSQL_CB_GET_ALL_SUBNETS4_RESULT
-================================
+PGSQL_CB_GET_TYPE6
+==================
.. code-block:: text
- retrieving: %1 elements
+ get type
Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all subnets
+Debug message issued when triggered an action to retrieve type
-PGSQL_CB_GET_ALL_SUBNETS6
-=========================
+PGSQL_CB_NO_TLS_SUPPORT
+=======================
.. code-block:: text
- retrieving all subnets
+ Attempt to configure TLS (unsupported for PostgreSQL): %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve all subnets
+This error message is printed when TLS support was required in the Kea
+configuration: Kea was built with this feature disabled for PostgreSQL.
+The parameters of the connection are logged.
-PGSQL_CB_GET_ALL_SUBNETS6_RESULT
-================================
+PGSQL_CB_RECONNECT_ATTEMPT_FAILED4
+==================================
.. code-block:: text
- retrieving: %1 elements
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve all subnets
+Error message issued when an attempt to reconnect has failed.
-PGSQL_CB_GET_CLIENT_CLASS4
-==========================
+PGSQL_CB_RECONNECT_ATTEMPT_FAILED6
+==================================
.. code-block:: text
- retrieving client class: %1
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a client class
+Error message issued when an attempt to reconnect has failed.
-PGSQL_CB_GET_CLIENT_CLASS6
-==========================
+PGSQL_CB_RECONNECT_ATTEMPT_SCHEDULE4
+====================================
.. code-block:: text
- retrieving client class: %1
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a client class
+Info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-PGSQL_CB_GET_GLOBAL_PARAMETER4
-==============================
+PGSQL_CB_RECONNECT_ATTEMPT_SCHEDULE6
+====================================
.. code-block:: text
- retrieving global parameter: %1
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve global parameter
+Info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-PGSQL_CB_GET_GLOBAL_PARAMETER6
-==============================
+PGSQL_CB_RECONNECT_FAILED4
+==========================
.. code-block:: text
- retrieving global parameter: %1
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve global parameter
+Error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-PGSQL_CB_GET_HOST4
-==================
+PGSQL_CB_RECONNECT_FAILED6
+==========================
.. code-block:: text
- get host
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve host
+Error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-PGSQL_CB_GET_HOST6
-==================
+PGSQL_CB_REGISTER_BACKEND_TYPE4
+===============================
.. code-block:: text
- get host
+ register backend
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve host
+Debug message issued when triggered an action to register backend
-PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4
-=====================================
+PGSQL_CB_REGISTER_BACKEND_TYPE6
+===============================
.. code-block:: text
- retrieving modified client classes from: %1
+ register backend
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified client classes from specified time
+Debug message issued when triggered an action to register backend
-PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT
-============================================
+PGSQL_CB_TLS_SUPPORT
+====================
.. code-block:: text
- retrieving: %1 elements
+ Attempt to configure TLS: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified client classes from specified time
+This informational message is printed when TLS support was required in
+the Kea configuration: The TLS support in PostgreSQL will be initialized but
+its configuration is fully managed outside the C API.
+The parameters of the connection are logged.
-PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6
-=====================================
+PGSQL_CB_UNREGISTER_BACKEND_TYPE4
+=================================
.. code-block:: text
- retrieving modified client classes from: %1
+ unregister backend
Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified client classes from specified time
+Debug message issued when triggered an action to unregister backend
-PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT
-============================================
+PGSQL_DEINIT_OK
+===============
.. code-block:: text
- retrieving: %1 elements
+ unloading PostgreSQL hooks library successful
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified client classes from specified time
+This informational message indicates that the PostgreSQL Backend hooks
+library has been unloaded successfully.
-PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4
-========================================
+PGSQL_HB_DB
+===========
.. code-block:: text
- retrieving modified global parameters from: %1
+ opening PostgreSQL hosts database: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified global parameters from specified time
+This informational message is logged when a DHCP server (either V4 or
+V6) is about to open a PostgreSQL hosts database. The parameters of the
+connection including database name and username needed to access it
+(but not the password if any) are logged.
-PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT
-===============================================
+PGSQL_HB_DB_GET_VERSION
+=======================
.. code-block:: text
- retrieving: %1 elements
+ obtaining schema version information for the PostgreSQL hosts database
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified global parameters from specified time
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the PostgreSQL hosts database.
-PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6
-========================================
+PGSQL_HB_DB_READONLY
+====================
.. code-block:: text
- retrieving modified global parameters from: %1
+ PostgreSQL host database opened for read access only
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified global parameters from specified time
+This informational message is issued when the user has configured the PostgreSQL
+database in read-only mode. Kea will not be able to insert or modify
+host reservations but will be able to retrieve existing ones and
+assign them to the clients communicating with the server.
-PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT
-===============================================
+PGSQL_HB_DB_RECONNECT_ATTEMPT_FAILED
+====================================
.. code-block:: text
- retrieving: %1 elements
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified global parameters from specified time
+An error message issued when an attempt to reconnect has failed.
-PGSQL_CB_GET_MODIFIED_OPTIONS4
-==============================
+PGSQL_HB_DB_RECONNECT_ATTEMPT_SCHEDULE
+======================================
.. code-block:: text
- retrieving modified options from: %1
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified options from specified time
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-PGSQL_CB_GET_MODIFIED_OPTIONS4_RESULT
-=====================================
+PGSQL_HB_DB_RECONNECT_FAILED
+============================
.. code-block:: text
- retrieving: %1 elements
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified options from specified time
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-PGSQL_CB_GET_MODIFIED_OPTIONS6
-==============================
+PGSQL_HB_NO_TLS_SUPPORT
+=======================
.. code-block:: text
- retrieving modified options from: %1
+ Attempt to configure TLS (unsupported for PostgreSQL): %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified options from specified time
+This error message is printed when TLS support was required in the Kea
+configuration: Kea was built with this feature disabled for PostgreSQL.
+The parameters of the connection are logged.
-PGSQL_CB_GET_MODIFIED_OPTIONS6_RESULT
-=====================================
+PGSQL_INIT_OK
+=============
.. code-block:: text
- retrieving: %1 elements
+ loading PostgreSQL hooks library successful
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified options from specified time
+This informational message indicates that the PostgreSQL Backend hooks
+library has been loaded successfully. Enjoy!
-PGSQL_CB_GET_MODIFIED_OPTION_DEFS4
-==================================
+PGSQL_LB_ADD_ADDR4
+==================
.. code-block:: text
- retrieving modified option definitions from: %1
+ adding IPv4 lease with address %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified option definitions from specified time
+Logged at debug log level 50.
+A debug message issued when the server is about to add an IPv4 lease
+with the specified address to the PostgreSQL backend database.
-PGSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT
-=========================================
+PGSQL_LB_ADD_ADDR6
+==================
.. code-block:: text
- retrieving: %1 elements
+ adding IPv6 lease with address %1, lease type %2
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified option definitions from specified time
+Logged at debug log level 50.
+A debug message issued when the server is about to add an IPv6 lease
+with the specified address to the PostgreSQL backend database.
-PGSQL_CB_GET_MODIFIED_OPTION_DEFS6
-==================================
+PGSQL_LB_COMMIT
+===============
.. code-block:: text
- retrieving modified option definitions from: %1
+ committing to PostgreSQL database
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified option definitions from specified time
+Logged at debug log level 50.
+The code has issued a commit call. All outstanding transactions will be
+committed to the database. Note that depending on the PostgreSQL settings,
+the commit may not include a write to disk.
-PGSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT
-=========================================
+PGSQL_LB_DB
+===========
.. code-block:: text
- retrieving: %1 elements
+ opening PostgreSQL lease database: %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified option definitions from specified time
+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.
-PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4
-======================================
+PGSQL_LB_DB_RECONNECT_ATTEMPT_FAILED
+====================================
.. code-block:: text
- retrieving modified shared networks from: %1
+ database reconnect failed: %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified shared networks from specified time
+An error message issued when an attempt to reconnect has failed.
-PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT
-=============================================
+PGSQL_LB_DB_RECONNECT_ATTEMPT_SCHEDULE
+======================================
.. code-block:: text
- retrieving: %1 elements
+ scheduling attempt %1 of %2 in %3 milliseconds
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified shared networks from specified time
+An info message issued when the server is scheduling the next attempt to reconnect
+to the database. This occurs when the server has lost database connectivity and
+is attempting to reconnect automatically.
-PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6
-======================================
+PGSQL_LB_DB_RECONNECT_FAILED
+============================
.. code-block:: text
- retrieving modified shared networks from: %1
+ maximum number of database reconnect attempts: %1, has been exhausted without success
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified shared networks from specified time
+An error message issued when the server failed to reconnect. Loss of connectivity
+is typically a network or database server issue.
-PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT
-=============================================
+PGSQL_LB_DELETE_ADDR4
+=====================
.. code-block:: text
- retrieving: %1 elements
+ deleting lease for address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified shared networks from specified time
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_MODIFIED_SUBNETS4
-==============================
+PGSQL_LB_DELETE_ADDR6
+=====================
.. code-block:: text
- retrieving modified subnets from: %1
+ deleting lease for address %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified subnets from specified time
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_MODIFIED_SUBNETS4_RESULT
-=====================================
+PGSQL_LB_DELETE_EXPIRED_RECLAIMED4
+==================================
.. code-block:: text
- retrieving: %1 elements
+ deleting reclaimed IPv4 leases that expired more than %1 seconds ago
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified subnets from specified time
+Logged at debug log level 50.
+A debug message issued when the server is removing reclaimed DHCPv4
+leases which have expired longer than a specified period of time.
+The argument is the amount of time Kea waits after a reclaimed
+lease expires before considering its removal.
-PGSQL_CB_GET_MODIFIED_SUBNETS6
-==============================
+PGSQL_LB_DELETE_EXPIRED_RECLAIMED6
+==================================
.. code-block:: text
- retrieving modified subnets from: %1
+ deleting reclaimed IPv6 leases that expired more than %1 seconds ago
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve modified subnets from specified time
+Logged at debug log level 50.
+A debug message issued when the server is removing reclaimed DHCPv6
+leases which have expired longer than a specified period of time.
+The argument is the amount of time Kea waits after a reclaimed
+lease expires before considering its removal.
-PGSQL_CB_GET_MODIFIED_SUBNETS6_RESULT
-=====================================
+PGSQL_LB_GET4
+=============
.. code-block:: text
- retrieving: %1 elements
+ obtaining all IPv4 leases
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve modified subnets from specified time
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv4
+leases from the PostgreSQL database.
-PGSQL_CB_GET_OPTION4
-====================
+PGSQL_LB_GET6
+=============
.. code-block:: text
- retrieving option code: %1 space: %2
+ obtaining all IPv6 leases
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv6
+leases from the PostgreSQL database.
-PGSQL_CB_GET_OPTION6
-====================
+PGSQL_LB_GET_ADDR4
+==================
.. code-block:: text
- retrieving option code: %1 space: %2
+ obtaining IPv4 lease for address %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain an IPv4
+lease from the PostgreSQL database for the specified address.
-PGSQL_CB_GET_OPTION_DEF4
-========================
+PGSQL_LB_GET_ADDR6
+==================
.. code-block:: text
- retrieving option definition code: %1 space: %2
+ obtaining IPv6 lease for address %1 (lease type %2)
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option definition
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain an IPv6
+lease from the PostgreSQL database for the specified address.
-PGSQL_CB_GET_OPTION_DEF6
-========================
+PGSQL_LB_GET_CLIENTID
+=====================
.. code-block:: text
- retrieving option definition code: %1 space: %2
+ obtaining IPv4 leases for client ID %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve option definition
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_PORT4
-==================
+PGSQL_LB_GET_DUID
+=================
.. code-block:: text
- get port
+ obtaining IPv6 leases for DUID %1,
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve port
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a set of IPv6
+leases from the PostgreSQL database for a client with the specified DUID (DHCP Unique Identifier).
-PGSQL_CB_GET_PORT6
-==================
+PGSQL_LB_GET_EXPIRED4
+=====================
.. code-block:: text
- get port
+ obtaining maximum %1 of expired IPv4 leases
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve port
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain expired
+IPv4 leases to reclaim them. The maximum number of leases to be retrieved
+is logged in the message.
-PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4
-==================================
+PGSQL_LB_GET_EXPIRED6
+=====================
.. code-block:: text
- retrieving audit entries from: %1 %2
+ obtaining maximum %1 of expired IPv6 leases
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve audit entries from specified time and id.
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain expired
+IPv6 leases to reclaim them. The maximum number of leases to be retrieved
+is logged in the message.
-PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT
-=========================================
+PGSQL_LB_GET_HOSTNAME4
+======================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 leases for hostname %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve audit entries from specified time
+Logged at debug log level 50.
+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
+hostname.
-PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6
-==================================
+PGSQL_LB_GET_HOSTNAME6
+======================
.. code-block:: text
- retrieving audit entries from: %1 %2
+ obtaining IPv6 leases for hostname %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve audit entries from specified time and id
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a set
+of IPv6 leases from the PostgreSQL database for a client with the specified
+hostname.
-PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT
-=========================================
+PGSQL_LB_GET_HWADDR
+===================
.. code-block:: text
- retrieving: %1 elements
+ obtaining IPv4 leases for hardware address %1
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve audit entries from specified time
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_SERVER4
-====================
+PGSQL_LB_GET_IAID_DUID
+======================
.. code-block:: text
- retrieving DHCPv4 server: %1
+ obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a DHCPv4 server information.
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a set of IPv6
+leases from the PostgreSQL database for a client with the specified IAID
+(Identity Association ID) and DUID (DHCP Unique Identifier).
-PGSQL_CB_GET_SERVER6
-====================
+PGSQL_LB_GET_IAID_SUBID_DUID
+============================
.. code-block:: text
- retrieving DHCPv6 server: %1
+ obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve a DHCPv6 server information.
+Logged at debug log level 50.
+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).
-PGSQL_CB_GET_SHARED_NETWORK4
-============================
+PGSQL_LB_GET_PAGE4
+==================
.. code-block:: text
- retrieving shared network: %1
+ obtaining at most %1 IPv4 leases starting from address %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page
+of leases beginning with the specified address.
-PGSQL_CB_GET_SHARED_NETWORK6
-============================
+PGSQL_LB_GET_PAGE6
+==================
.. code-block:: text
- retrieving shared network: %1
+ obtaining at most %1 IPv6 leases starting from address %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page
+of leases beginning with the specified address.
-PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4
-====================================
+PGSQL_LB_GET_RELAYID4
+=====================
.. code-block:: text
- retrieving shared network: %1 subnets
+ obtaining at most %1 IPv4 leases starting from address %2 with relay id %3 and cltt between %4 and %5
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network subnets
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv4 leases beginning with the specified address with a relay id and client
+transaction time between start and end dates.
-PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT
-===========================================
+PGSQL_LB_GET_RELAYID6
+=====================
.. code-block:: text
- retrieving: %1 elements
+ obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve shared network subnets
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases beginning with the specified address with a relay id.
-PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6
-====================================
+PGSQL_LB_GET_REMOTEID4
+======================
.. code-block:: text
- retrieving shared network: %1 subnets
+ obtaining at most %1 IPv4 leases starting from address %2 with remote id %3 and cltt between %4 and %5
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve shared network subnets
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv4 leases beginning with the specified address with a remote id and client
+transaction time between start and end dates.
-PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT
-===========================================
+PGSQL_LB_GET_REMOTEID6
+======================
.. code-block:: text
- retrieving: %1 elements
+ obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
-Logged at debug log level 40.
-Debug message indicating the result of an action to retrieve shared network subnets
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases beginning with the specified address with a remote id.
-PGSQL_CB_GET_SUBNET4_BY_PREFIX
-==============================
+PGSQL_LB_GET_SUBID4
+===================
.. code-block:: text
- retrieving subnet by prefix: %1
+ obtaining IPv4 leases for subnet ID %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by prefix
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv4
+leases for a given subnet identifier from the PostgreSQL database.
-PGSQL_CB_GET_SUBNET4_BY_SUBNET_ID
-=================================
+PGSQL_LB_GET_SUBID6
+===================
.. code-block:: text
- retrieving subnet by subnet id: %1
+ obtaining IPv6 leases for subnet ID %1
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by subnet id
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain all IPv6
+leases for a given subnet identifier from the PostgreSQL database.
-PGSQL_CB_GET_SUBNET6_BY_PREFIX
-==============================
+PGSQL_LB_GET_SUBID_CLIENTID
+===========================
.. code-block:: text
- retrieving subnet by prefix: %1
+ obtaining IPv4 lease for subnet ID %1 and client ID %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by prefix
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_SUBNET6_BY_SUBNET_ID
-=================================
+PGSQL_LB_GET_SUBID_HWADDR
+=========================
.. code-block:: text
- retrieving subnet by subnet id: %1
+ obtaining IPv4 lease for subnet ID %1 and hardware address %2
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve subnet by subnet id
+Logged at debug log level 50.
+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.
-PGSQL_CB_GET_TYPE4
-==================
+PGSQL_LB_GET_SUBID_PAGE6
+========================
.. code-block:: text
- get type
+ obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve type
+Logged at debug log level 50.
+A debug message issued when the server is attempting to obtain a page of
+IPv6 leases from the PostgreSQL database beginning with the specified address
+for the specified subnet identifier.
-PGSQL_CB_GET_TYPE6
-==================
+PGSQL_LB_GET_VERSION
+====================
.. code-block:: text
- get type
+ obtaining schema version information
-Logged at debug log level 40.
-Debug message issued when triggered an action to retrieve type
+Logged at debug log level 50.
+A debug message issued when the server is about to obtain schema version
+information from the PostgreSQL database.
-PGSQL_CB_INIT_OK
-================
+PGSQL_LB_NEGATIVE_LEASES_STAT
+=============================
.. code-block:: text
- loading Postgres CB hooks library successful
+ recount of leases returned a negative value
-This informational message indicates that the Postgres Configuration Backend hooks
-library has been loaded successfully. Enjoy!
+This warning message is issued when the recount of leases using counters
+in the PostgreSQL database returned a negative value. This shows a problem
+which can be fixed only by an offline direct recount on the database.
+This message is issued only once.
-PGSQL_CB_NO_TLS_SUPPORT
+PGSQL_LB_NO_TLS_SUPPORT
=======================
.. code-block:: text
configuration: Kea was built with this feature disabled for PostgreSQL.
The parameters of the connection are logged.
-PGSQL_CB_RECONNECT_ATTEMPT_FAILED4
-==================================
+PGSQL_LB_ROLLBACK
+=================
.. code-block:: text
- database reconnect failed: %1
+ rolling back PostgreSQL database
-Error message issued when an attempt to reconnect has failed.
+Logged at debug log level 50.
+The code has issued a rollback call. All outstanding transaction will
+be rolled back and not committed to the database.
-PGSQL_CB_RECONNECT_ATTEMPT_FAILED6
-==================================
+PGSQL_LB_TLS_SUPPORT
+====================
.. code-block:: text
- database reconnect failed: %1
+ Attempt to configure TLS: %1
-Error message issued when an attempt to reconnect has failed.
+This informational message is printed when TLS support was required in
+the Kea configuration: The TLS support in PostgreSQL will be initialized but
+its configuration is fully managed outside the C API.
+The parameters of the connection are logged.
-PGSQL_CB_RECONNECT_ATTEMPT_SCHEDULE4
-====================================
+PGSQL_LB_UPDATE_ADDR4
+=====================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ updating IPv4 lease for address %1
-Info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+Logged at debug log level 50.
+A debug message issued when the server is attempting to update IPv4
+lease from the PostgreSQL database for the specified address.
-PGSQL_CB_RECONNECT_ATTEMPT_SCHEDULE6
-====================================
+PGSQL_LB_UPDATE_ADDR6
+=====================
.. code-block:: text
- scheduling attempt %1 of %2 in %3 milliseconds
+ updating IPv6 lease for address %1, lease type %2
-Info message issued when the server is scheduling the next attempt to reconnect
-to the database. This occurs when the server has lost database connectivity and
-is attempting to reconnect automatically.
+Logged at debug log level 50.
+A debug message issued when the server is attempting to update IPv6
+lease from the PostgreSQL database for the specified address.
-PGSQL_CB_RECONNECT_FAILED4
-==========================
+PGSQL_LB_UPGRADE_EXTENDED_INFO4
+===============================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ upgrading IPv4 leases done in %1 pages with %2 updated leases
-Error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+The server upgraded extended info. The number of pages and the final count of
+updated leases are displayed.
-PGSQL_CB_RECONNECT_FAILED6
-==========================
+PGSQL_LB_UPGRADE_EXTENDED_INFO4_ERROR
+=====================================
.. code-block:: text
- maximum number of database reconnect attempts: %1, has been exhausted without success
+ upgrading extending info for IPv4 lease at %1 failed with %2
-Error message issued when the server failed to reconnect. Loss of connectivity
-is typically a network or database server issue.
+Logged at debug log level 40.
+A debug message issued when the server failed to upgrade an extended info.
+The address of the lease and the error message are displayed.
-PGSQL_CB_REGISTER_BACKEND_TYPE4
-===============================
+PGSQL_LB_UPGRADE_EXTENDED_INFO4_PAGE
+====================================
.. code-block:: text
- register backend
+ upgrading IPv4 lease extended info at page %1 starting at %2 (updated %3)
-Logged at debug log level 40.
-Debug message issued when triggered an action to register backend
+Logged at debug log level 50.
+A debug message issued when the server upgrades IPv4 lease extended info.
+The page number and started address, and the count of already updated leases
+are displayed.
-PGSQL_CB_REGISTER_BACKEND_TYPE6
+PGSQL_LB_UPGRADE_EXTENDED_INFO6
===============================
.. code-block:: text
- register backend
+ upgrading IPv6 leases done in %1 pages with %2 updated leases
Logged at debug log level 40.
-Debug message issued when triggered an action to register backend
-
-PGSQL_CB_TLS_SUPPORT
-====================
-
-.. code-block:: text
-
- Attempt to configure TLS: %1
-
-This informational message is printed when TLS support was required in
-the Kea configuration: The TLS support in PostgreSQL will be initialized but
-its configuration is fully managed outside the C API.
-The parameters of the connection are logged.
+The server upgraded extended info. The number of pages and the final count of
+updated leases are displayed.
-PGSQL_CB_UNREGISTER_BACKEND_TYPE4
-=================================
+PGSQL_LB_UPGRADE_EXTENDED_INFO6_ERROR
+=====================================
.. code-block:: text
- unregister backend
+ upgrading extending info for IPv6 lease at %1 failed with %2
Logged at debug log level 40.
-Debug message issued when triggered an action to unregister backend
+A debug message issued when the server failed to upgrade the extended info
+for a lease. The address of the lease and the error message are displayed.
****
PING
projects / thirdparty / kea.git / commitdiff
