-# Copyright (C) 2016-2022 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2016-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
the control message to the specified Kea service and receives a response.
% CTRL_AGENT_COMMAND_FORWARD_BEGIN begin forwarding command %1 to service %2
+Logged at debug log level 10.
This debug message is issued when the Control Agent starts forwarding a
received command to one of the Kea servers.
% CTRL_AGENT_COMMAND_FORWARD_FAILED failed forwarding command %1: %2
+Logged at debug log level 10.
This debug message is issued when the Control Agent failed forwarding a
received command to one of the Kea servers. The second argument provides
the details of the error.
address and port.
% CTRL_AGENT_RUN_EXIT application is exiting the event loop
+Logged at debug log level 0.
This is a debug message issued when the Control Agent exits its
event loop.
second contains the PID and PID file.
% DHCP4_BUFFER_RECEIVED received buffer from %1:%2 to %3:%4 over interface %5
+Logged at debug log level 40.
This debug message is logged when the server has received a packet
over the socket. When the message is logged the contents of the received
packet hasn't been parsed yet. The only available information is the
the message.
% DHCP4_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
+Logged at debug log level 50.
This debug message is issued when the server starts parsing the received
buffer holding the DHCPv4 message. The arguments specify the source and
destination IPv4 addresses as well as the interface over which the buffer has
been received.
% DHCP4_BUFFER_WAIT_SIGNAL signal received while waiting for next packet
+Logged at debug log level 50.
This debug message is issued when the server was waiting for the
packet, but the wait has been interrupted by the signal received
by the process. The signal will be handled before the server starts
in the database and reload (or restart) the server.
% DHCP4_CLASSES_ASSIGNED %1: client packet has been assigned on %2 message to the following classes: %3
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
argument includes all classes to which the packet has been assigned.
% DHCP4_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION %1: client packet has been assigned to the following classes: %2
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
been assigned.
% DHCP4_CLASS_ASSIGNED %1: client packet has been assigned to the following class: %2
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
class. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
packet has been assigned.
% DHCP4_CLASS_UNCONFIGURED %1: client packet belongs to an unconfigured class: %2
+Logged at debug log level 40.
This debug message informs that incoming packet belongs to a class
which cannot be found in the configuration. Either a hook written
before the classification was added to Kea is used, or class naming is
inconsistent.
% DHCP4_CLASS_UNDEFINED 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 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 %1: not using client identifier for lease allocation for subnet %2
+Logged at debug log level 50.
This debug message is issued when the server is processing the DHCPv4 message
for which client identifier will not be used when allocating new lease or
renewing existing lease. The server is explicitly configured to not use
operation is configured on the server.
% DHCP4_CLIENT_FQDN_DATA %1: Client sent FQDN option: %2
+Logged at debug log level 55.
This debug message includes the detailed information extracted from the
Client FQDN option sent in the query. The first argument includes the
client and transaction identification information. The second argument
by the server.
% DHCP4_CLIENT_FQDN_PROCESS %1: processing Client FQDN option
+Logged at debug log level 50.
This debug message is issued when the server starts processing the Client
FQDN option sent in the client's query. The argument includes the
client and transaction identification information.
% DHCP4_CLIENT_HOSTNAME_DATA %1: client sent Hostname option: %2
+Logged at debug log level 55.
This debug message includes the detailed information extracted from the
Hostname option sent in the query. The first argument includes the
client and transaction identification information. The second argument
client.
% DHCP4_CLIENT_HOSTNAME_MALFORMED %1: client hostname option malformed: %2
+Logged at debug log level 50.
This debug message is issued when the DHCP server was unable to process the
the hostname option sent by the client because the content is malformed.
The first argument includes the client and transaction identification
information. The second argument contains a description of the data error.
% DHCP4_CLIENT_HOSTNAME_PROCESS %1: processing client's Hostname option
+Logged at debug log level 50.
This debug message is issued when the server starts processing the Hostname
option sent in the client's query. The argument includes the client and
transaction identification information.
% DHCP4_CLIENT_NAME_PROC_FAIL %1: failed to process the fqdn or hostname sent by a client: %2
+Logged at debug log level 55.
This debug message is issued when the DHCP server was unable to process the
FQDN or Hostname option sent by a client. This is likely because the client's
name was malformed or due to internal server error. The first argument
shown depends upon the packet queue type selected.
% DHCP4_CONFIG_RECEIVED received configuration %1
+Logged at debug log level 10.
A debug message listing the configuration received by the DHCPv4 server.
The source of that configuration depends on used configuration backend.
% DHCP4_CONFIG_START DHCPv4 server is processing the following configuration: %1
+Logged at debug log level 10.
This is a debug message that is issued every time the server receives a
configuration. That happens at start up and also when a server configuration
change is committed by the administrator.
a client's error or a server's purged database.
% DHCP4_DEFERRED_OPTION_MISSING %1: cannot find deferred option code %2 in the query
+Logged at debug log level 50.
This debug message is printed when a deferred option cannot be found in
the query.
% DHCP4_DEFERRED_OPTION_UNPACK_FAIL %1: An error unpacking the deferred option %2: %3
+Logged at debug log level 50.
A debug message issued when deferred unpacking of an option failed, making it
to be left unpacked in the packet. The first argument is the option code,
the second the error.
(vs stable) one: the second number of the version is odd.
% DHCP4_DHCP4O6_BAD_PACKET %1: received malformed DHCPv4o6 packet: %2
+Logged at debug log level 50.
A malformed DHCPv4o6 packet was received.
% DHCP4_DHCP4O6_HOOK_SUBNET4_SELECT_DROP %1: packet was dropped, because a callout set the next step to 'drop'
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet4_select hook point sets the next step to 'drop' value. For this particular hook
point, the setting to that value instructs the server to drop the received
information.
% DHCP4_DHCP4O6_HOOK_SUBNET4_SELECT_SKIP %1: no subnet was selected, because a callout set the next skip flag
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet4_select hook point sets the next step to SKIP value. For this particular hook
point, the setting of the flag instructs the server not to choose a
information.
% DHCP4_DHCP4O6_PACKET_RECEIVED received DHCPv4o6 packet from DHCPv4 server (type %1) for %2 on interface %3
+Logged at debug log level 40.
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv4 server over inter-process communication.
% DHCP4_DHCP4O6_PACKET_SEND %1: trying to send packet %2 (type %3) to %4 port %5 on interface %6 encapsulating %7: %8 (type %9)
+Logged at debug log level 40.
The arguments specify the client identification information (HW address
and client identifier), DHCPv6 message name and type, source IPv6
address and port, and interface name, DHCPv4 client identification,
error is included in the message.
% DHCP4_DHCP4O6_RECEIVE_FAIL failed to receive DHCPv4o6: %1
+Logged at debug log level 50.
This debug message indicates the inter-process communication with the
DHCPv6 server failed. The reason for the error is included in
the message.
% DHCP4_DHCP4O6_RECEIVING receiving DHCPv4o6 packet from DHCPv6 server
+Logged at debug log level 50.
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv6 server over inter-process communication socket.
% DHCP4_DHCP4O6_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
+Logged at debug log level 55.
A debug message including the detailed data about the packet being
sent to the DHCPv6 server to be forwarded to the client. The first
argument contains the client and the transaction identification
information.
% DHCP4_DHCP4O6_SUBNET_DATA %1: the selected subnet details: %2
+Logged at debug log level 55.
This debug message includes the details of the subnet selected for
the client. The first argument includes the client and the
transaction identification information. The second arguments
includes the subnet details.
% DHCP4_DHCP4O6_SUBNET_SELECTED %1: the subnet with ID %2 was selected for client assignments
+Logged at debug log level 45.
This is a debug message noting the selection of a subnet to be used for
address and option assignment. Subnet selection is one of the early
steps in the processing of incoming client message. The first
information. The second argument holds the selected subnet id.
% DHCP4_DHCP4O6_SUBNET_SELECTION_FAILED %1: failed to select subnet for the client
+Logged at debug log level 50.
This debug message indicates that the server failed to select the
subnet for the client which has sent a message to the server.
The server will not be able to offer any lease to the client and
information.
% DHCP4_DISCOVER %1: server is processing DHCPDISCOVER with hint=%2
+Logged at debug log level 50.
This is a debug message that indicates the processing of a received DHCPDISCOVER
message. The first argument contains the client and the transaction
identification information. The second argument may hold the hint for the server
succeeded.
% DHCP4_EMPTY_HOSTNAME %1: received empty hostname from the client, skipping processing of this option
+Logged at debug log level 50.
This debug message is issued when the server received an empty Hostname option
from a client. Server does not process empty Hostname options and therefore
option is skipped. The argument holds the client and transaction identification
information.
% DHCP4_FLEX_ID %1: flexible identifier generated for incoming packet: %2
+Logged at debug log level 40.
This debug message is printed when host reservation type is set to flexible identifier
and the expression specified in its configuration generated (was evaluated to)
an identifier for incoming packet. This debug message is mainly intended as a
debugging assistance for flexible identifier.
% DHCP4_GENERATE_FQDN %1: client did not send a FQDN or hostname; FQDN will be generated for the client
+Logged at debug log level 55.
This debug message is issued when the server did not receive a Hostname option
from the client and hostname generation is enabled. This provides a means to
create DNS entries for unsophisticated clients.
processing. This likely indicates a coding error and should be reported to ISC.
% DHCP4_HOOK_BUFFER_RCVD_DROP received buffer from %1 to %2 over interface %3 was dropped because a callout set the drop flag
+Logged at debug log level 15.
This debug message is printed when a callout installed on buffer4_receive
hook point set the drop flag. For this particular hook point, the
setting of the flag by a callout instructs the server to drop the packet.
the name of the interface over which the buffer has been received.
% DHCP4_HOOK_BUFFER_RCVD_SKIP received buffer from %1 to %2 over interface %3 is not parsed because a callout set the next step to SKIP.
+Logged at debug log level 50.
This debug message is printed when a callout installed on
buffer4_receive hook point set the next step to SKIP. For this particular hook
point, this value set by a callout instructs the server to
the name of the interface over which the buffer has been received.
% DHCP4_HOOK_BUFFER_SEND_SKIP %1: prepared response is dropped because a callout set the next step to SKIP.
+Logged at debug log level 40.
This debug message is printed when a callout installed on buffer4_send
hook point set the next step to SKIP. For this particular hook point, the
SKIP value set by a callout instructs the server to drop the packet.
or released leases), but the response will not be send to the client.
% DHCP4_HOOK_DDNS_UPDATE A hook has updated the DDNS parameters: hostname %1=>%2, forward update %3=>%4, reverse update %5=>%6
+Logged at debug log level 15.
This message indicates that there was a hook called on ddns4_update hook point
and that hook updated the DDNS update parameters: hostname, or whether to
conduct forward (A record) or reverse (PTR record) DDNS updates.
% DHCP4_HOOK_DECLINE_SKIP Decline4 hook callouts set status to DROP, ignoring packet.
+Logged at debug log level 15.
This message indicates that the server received DHCPDECLINE message, it was verified
to be correct and matching server's lease information. The server called hooks
for decline4 hook point and one of the callouts set next step status to DROP.
those callouts can fulfill them.
% DHCP4_HOOK_LEASE4_RELEASE_SKIP %1: lease was not released because a callout set the next step to SKIP
+Logged at debug log level 15.
This debug message is printed when a callout installed on lease4_release
hook point set the next step status to SKIP. For this particular hook point, the
value set by a callout instructs the server to not release a lease.
those callouts can fulfill them.
% DHCP4_HOOK_PACKET_RCVD_SKIP %1: packet is dropped, because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the pkt4_receive
hook point sets the next step to SKIP. For this particular hook point, the
value setting of the flag instructs the server to drop the packet.
% DHCP4_HOOK_PACKET_SEND_DROP %1: prepared DHCPv4 response was not sent because a callout set the next ste to DROP
+Logged at debug log level 15.
This debug message is printed when a callout installed on the pkt4_send
hook point set the next step to DROP. For this particular hook point, the setting
of the value by a callout instructs the server to drop the packet. This
identification information.
% DHCP4_HOOK_PACKET_SEND_SKIP %1: prepared response is not sent, because a callout set the next stp to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the pkt4_send
hook point sets the next step to SKIP. For this particular hook point, this
setting instructs the server to drop the packet. This means that
client's request and acted on it (e.g. possibly allocated a lease).
% DHCP4_HOOK_SUBNET4_SELECT_4O6_PARKING_LOT_FULL The parked-packet-limit %1, has been reached, dropping query: %2
+Logged at debug log level 15.
This debug message occurs when the parking lot used to hold client queries
while the hook library work for them completes has reached or exceeded the
limit set by the parked-packet-limit global parameter. This can occur when
those callouts can fulfill them.
% DHCP4_HOOK_SUBNET4_SELECT_DROP %1: packet was dropped, because a callout set the next step to 'drop'
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet4_select hook point sets the next step to 'drop' value. For this particular hook
point, the setting to that value instructs the server to drop the received
information.
% DHCP4_HOOK_SUBNET4_SELECT_PARK %1: packet was parked
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet4_select hook point set the park flag. The argument holds the
client and transaction identification information.
% DHCP4_HOOK_SUBNET4_SELECT_PARKING_LOT_FULL The parked-packet-limit %1, has been reached, dropping query: %2
+Logged at debug log level 15.
This debug message occurs when the parking lot used to hold client queries
while the hook library work for them completes has reached or exceeded the
limit set by the parked-packet-limit global parameter. This can occur when
those callouts can fulfill them.
% DHCP4_HOOK_SUBNET4_SELECT_SKIP %1: no subnet was selected, because a callout set the next skip flag
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet4_select hook point sets the next step to SKIP value. For this particular hook
point, the setting of the flag instructs the server not to choose a
information.
% DHCP4_INFORM_DIRECT_REPLY %1: DHCPACK in reply to the DHCPINFORM will be sent directly to %2 over %3
+Logged at debug log level 50.
This debug message is issued when the DHCPACK will be sent directly to the
client, rather than via a relay. The first argument contains the client
and transaction identification information. The second argument contains
DHCPv4 server but it is not running.
% DHCP4_NO_LEASE_INIT_REBOOT %1: no lease for address %2 requested by INIT-REBOOT client
+Logged at debug log level 50.
This debug message is issued when the client being in the INIT-REBOOT state
requested an IPv4 address but this client is unknown. The server will not
respond. The first argument includes the client and the transaction id
is logged.
% DHCP4_OPEN_SOCKET opening service sockets on port %1
+Logged at debug log level 0.
A debug message issued during startup, this indicates that the DHCPv4
server is about to open sockets on the specified port.
for the failure is appended as an argument of the log message.
% DHCP4_PACKET_DROP_0001 %1: failed to parse packet from %2 to %3, received over interface %4, reason: %5, %6
+Logged at debug log level 15.
The DHCPv4 server has received a packet that it is unable to
interpret. The reason why the packet is invalid is included in the message.
% DHCP4_PACKET_DROP_0002 %1, from interface %2: no suitable subnet configured for a direct client
+Logged at debug log level 15.
This info message is logged when received a message from a directly connected
client but there is no suitable subnet configured for the interface on
which this message has been received. The IPv4 address assigned on this
received message is dropped.
% DHCP4_PACKET_DROP_0003 %1, from interface %2: it contains a foreign server identifier
+Logged at debug log level 15.
This debug message is issued when received DHCPv4 message is dropped because
it is addressed to a different server, i.e. a server identifier held by
this message doesn't match the identifier used by our server. The arguments
the message has been received.
% DHCP4_PACKET_DROP_0004 %1, from interface %2: missing msg-type option
+Logged at debug log level 15.
This is a debug message informing that incoming DHCPv4 packet did not
have mandatory DHCP message type option and thus was dropped. The
arguments specify the client and transaction identification information,
as well as the interface on which the message has been received.
% DHCP4_PACKET_DROP_0005 %1: unrecognized type %2 in option 53
+Logged at debug log level 15.
This debug message indicates that the message type carried in DHCPv4 option
53 is unrecognized by the server. The valid message types are listed
on the IANA website: http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml#message-type-53.
received message type.
% DHCP4_PACKET_DROP_0006 %1: unsupported DHCPv4 message type %2
+Logged at debug log level 15.
This debug message indicates that the message type carried in DHCPv4 option
53 is valid but the message will not be processed by the server. This includes
messages being normally sent by the server to the client, such as DHCPOFFER,
identification information. The second argument specifies the message type.
% DHCP4_PACKET_DROP_0007 %1: failed to process packet: %2
+Logged at debug log level 15.
This is a general catch-all message indicating that the processing of a
received packet failed. The reason is given in the message. The server
will not send a response but will instead ignore the packet. The first
The second argument includes the details of the error.
% DHCP4_PACKET_DROP_0008 %1: DHCP service is globally disabled
+Logged at debug log level 15.
This debug message is issued when a packet is dropped because the DHCP service
has been temporarily disabled. This affects all received DHCP packets. The
service may be enabled by the "dhcp-enable" control command or automatically
after a specified amount of time since receiving "dhcp-disable" command.
% DHCP4_PACKET_DROP_0009 %1: Option 53 missing (no DHCP message type), is this a BOOTP packet?
+Logged at debug log level 15.
This debug message is issued when a packet is dropped because it did contain
option 53 and thus has no DHCP message type. The most likely explanation is
that it was BOOTP packet.
% DHCP4_PACKET_DROP_0010 dropped as member of the special class 'DROP': %1, %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
into the special class 'DROP' and dropped. The packet details are displayed.
% DHCP4_PACKET_DROP_0011 dropped as sent by the same client than a packet being processed by another thread: dropped %1, %2 by thread %3 as duplicate of %4, %5 processed by %6
+Logged at debug log level 15.
Currently multi-threading processing avoids races between packets sent by
a client using the same client id option by dropping new packets until
processing is finished.
this warning message.
% DHCP4_PACKET_DROP_0012 dropped as sent by the same client than a packet being processed by another thread: dropped %1, %2 by thread %3 as duplicate of %4, %5 processed by %6
+Logged at debug log level 15.
Currently multi-threading processing avoids races between packets sent by
a client using the same hardware address by dropping new packets until
processing is finished.
this warning message.
% DHCP4_PACKET_DROP_0013 dropped as member of the special class 'DROP' after host reservation lookup: %1, %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
after host reservation lookup into the special class 'DROP' and dropped.
The packet details are displayed.
% DHCP4_PACKET_DROP_0014 dropped as member of the special class 'DROP' after early global host reservations lookup: %1, %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
after early global host reservations lookup into the special class 'DROP'
and dropped. The packet details are displayed.
the name of the received packet.
% DHCP4_PACKET_NAK_0002 %1: invalid address %2 requested by INIT-REBOOT
+Logged at debug log level 50.
This debug message is issued when the client being in the INIT-REBOOT state
requested an IPv4 address which is not assigned to him. The server will respond
to this client with DHCPNAK. The first argument contains the client and
IPv4 address requested by the client.
% DHCP4_PACKET_NAK_0003 %1: failed to advertise a lease, client sent ciaddr %2, requested-ip-address %3
+Logged at debug log level 50.
This message indicates that the server has failed to offer a lease to
the specified client after receiving a DISCOVER message from it. There are
many possible reasons for such a failure. The first argument contains
(if present).
% DHCP4_PACKET_NAK_0004 %1: failed to grant a lease, client sent ciaddr %2, requested-ip-address %3
+Logged at debug log level 50.
This message indicates that the server failed to grant a lease to the
specified client after receiving a REQUEST message from it. There are many
possible reasons for such a failure. Additional messages will indicate the
requested-ip-address option (if present).
% DHCP4_PACKET_OPTIONS_SKIPPED %1: An error unpacking an option, caused subsequent options to be skipped: %2
+Logged at debug log level 50.
A debug message issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
server will still attempt to service the packet.
the second the error.
% DHCP4_PACKET_PACK %1: preparing on-wire format of the packet to be sent
+Logged at debug log level 50.
This debug message is issued when the server starts preparing the on-wire
format of the packet to be sent back to the client. The argument specifies
the client and the transaction identification information.
loop.
% DHCP4_PACKET_QUEUE_FULL multi-threading packet queue is full
+Logged at debug log level 40.
A debug message noting that the multi-threading packet queue is full so
the oldest packet of the queue was dropped to make room for the received one.
initially selected for allocation) from the same shared network.
% DHCP4_QUERY_DATA %1, packet details: %2
+Logged at debug log level 55.
A debug message printing the details of the received packet. The first
argument includes the client and the transaction identification
information.
and provides the cause of failure.
% DHCP4_RECOVERED_STASHED_RELAY_AGENT_INFO recovered for query %1 relay agent option from lease %2: %3
+Logged at debug log level 55.
This debug message indicates that agent options were stashed in the lease for
the client address of the request and were recovered. The first argument
includes the request information, the second the client address and the last
argument the content of the dhcp-agent-options option.
% DHCP4_RELEASE %1: address %2 was released properly.
+Logged at debug log level 50.
This informational message indicates that an address was released properly. It
is a normal operation during client shutdown. The first argument includes
the client and transaction identification information. The second argument
the released IPv4 address.
% DHCP4_RELEASE_FAIL %1: failed to remove lease for address %2
+Logged at debug log level 50.
This error message indicates that the software failed to remove a
lease from the lease database. It is probably due to an error during a
database operation: resolution will most likely require administrator
was attempted.
% DHCP4_RELEASE_FAIL_NO_LEASE %1: client is trying to release non-existing lease %2
+Logged at debug log level 50.
This debug message is printed when client attempts to release a lease,
but no such lease is known to the server. The first argument contains
the client and transaction identification information. The second
release.
% DHCP4_RELEASE_FAIL_WRONG_CLIENT %1: client is trying to release the lease %2 which belongs to a different client
+Logged at debug log level 50.
This debug message is issued when a client is trying to release the
lease for the address which is currently used by another client, i.e.
the 'client identifier' or 'chaddr' doesn't match between the client
the leased address.
% DHCP4_REQUEST %1: server is processing DHCPREQUEST with hint=%2
+Logged at debug log level 50.
This is a debug message that indicates the processing of a received DHCPREQUEST
message. The first argument contains the client and the transaction
identification information. The second argument may hold the hint for the server
lease lookup when multi-threading is enabled overwriting configured value.
% DHCP4_RESERVED_HOSTNAME_ASSIGNED %1: server assigned reserved hostname %2
+Logged at debug log level 55.
This debug message is issued when the server found a hostname reservation
for a client and uses this reservation in a hostname option sent back
to this client. The reserved hostname is qualified with a value
of 'ddns-qualifying-suffix' parameter, if this parameter is specified.
% DHCP4_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
+Logged at debug log level 55.
A debug message including the detailed data about the packet being sent
to the client. The first argument contains the client and the transaction
identification information. The second and third argument contains the
packet information.
% DHCP4_RESPONSE_FQDN_DATA %1: including FQDN option in the server's response: %2
+Logged at debug log level 55.
This debug message is issued when the server is adding the Client FQDN
option in its response to the client. The first argument includes the
client and transaction identification information. The second argument
the lease is acquired for the client.
% DHCP4_RESPONSE_HOSTNAME_DATA %1: including Hostname option in the server's response: %2
+Logged at debug log level 55.
This debug message is issued when the server is adding the Hostname
option in its response to the client. The first argument includes the
client and transaction identification information. The second argument
the lease is acquired for the client.
% DHCP4_RESPONSE_HOSTNAME_GENERATE %1: server has generated hostname %2 for the client
+Logged at debug log level 50.
This debug message includes the auto-generated hostname which will be used
for the client which message is processed. Hostnames may need to be generated
when required by the server's configuration or when the client hasn't
address for which the decline was attempted.
% DHCP4_SHUTDOWN server shutdown
+Logged at debug log level 40.
The DHCPv4 server has terminated normally.
% DHCP4_SHUTDOWN_REQUEST shutdown of server requested
+Logged at debug log level 40.
This debug message indicates that a shutdown of the DHCPv4 server has
been requested via a call to the 'shutdown' method of the core Dhcpv4Srv
object.
is also printed.
% DHCP4_START_INFO pid: %1, server port: %2, client port: %3, verbose: %4
+Logged at debug log level 0.
This is a debug message issued during the DHCPv4 server startup.
It lists some information about the parameters with which the server
is running.
% DHCP4_SUBNET_DATA %1: the selected subnet details: %2
+Logged at debug log level 55.
This debug message includes the details of the subnet selected for
the client. The first argument includes the client and the
transaction identification information. The second arguments
includes the subnet details.
% DHCP4_SUBNET_DYNAMICALLY_CHANGED %1: changed selected subnet %2 to subnet %3 from shared network %4 for client assignments
+Logged at debug log level 45.
This debug message indicates that the server is using another subnet
than initially selected for client assignments. This newly selected
subnet belongs to the same shared network as the original subnet.
includes some static reservations for this client.
% DHCP4_SUBNET_SELECTED %1: the subnet with ID %2 was selected for client assignments
+Logged at debug log level 45.
This is a debug message noting the selection of a subnet to be used for
address and option assignment. Subnet selection is one of the early
steps in the processing of incoming client message. The first
information. The second argument holds the selected subnet id.
% DHCP4_SUBNET_SELECTION_FAILED %1: failed to select subnet for the client
+Logged at debug log level 50.
This debug message indicates that the server failed to select the
subnet for the client which has sent a message to the server.
The server will not be able to offer any lease to the client and
to simulate multiple subnet traffic from single source.
% DHCP4_UNKNOWN_ADDRESS_REQUESTED %1: client requested an unknown address, client sent ciaddr %2, requested-ip-address %3
+Logged at debug log level 50.
This message indicates that the client requested an address that does
not belong to any dynamic pools managed by this server. The first argument
contains the client and the transaction identification information.
$NAMESPACE isc::dhcp
% DHCP4_HOOK_SUBNET6_SELECT_PARKING_LOT_FULL The parked-packet-limit %1, has been reached, dropping query: %2
+Logged at debug log level 15.
This debug message occurs when the parking lot used to hold client queries
while the hook library work for them completes has reached or exceeded the
limit set by the parked-packet-limit global parameter. This can occur when
Interface Manager starts up procedure of opening sockets.
% DHCP6_ADD_GLOBAL_STATUS_CODE %1: adding Status Code to DHCPv6 packet: %2
+Logged at debug log level 50.
This message is logged when the server is adding the top-level
Status Code option. The first argument includes the client and the
transaction identification information. The second argument includes
the details of the status code.
% DHCP6_ADD_STATUS_CODE_FOR_IA %1: adding Status Code to IA with iaid=%2: %3
+Logged at debug log level 50.
This message is logged when the server is adding the Status Code
option to an IA. The first argument includes the client and the
transaction identification information. The second argument specifies
contains the PID and PID file.
% DHCP6_BUFFER_RECEIVED received buffer from %1:%2 to %3:%4 over interface %5
+Logged at debug log level 40.
This debug message is logged when the server has received a packet
over the socket. When the message is logged the contents of the received
packet hasn't been parsed yet. The only available information is the
interface and the source and destination addresses/ports.
% DHCP6_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
+Logged at debug log level 50.
This debug message is issued when the server starts parsing the received
buffer holding the DHCPv6 message. The arguments specify the source and
destination addresses as well as the interface over which the buffer has
been received.
% DHCP6_BUFFER_WAIT_SIGNAL signal received while waiting for next packet
+Logged at debug log level 50.
This debug message is issued when the server was waiting for the
packet, but the wait has been interrupted by the signal received
by the process. The signal will be handled before the server starts
in the database and reload (or restart) the server.
% DHCP6_CLASSES_ASSIGNED %1: client packet has been assigned on %2 message to the following classes: %3
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
argument includes all classes to which the packet has been assigned.
% DHCP6_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION %1: client packet has been assigned to the following classes: %2
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
classes. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
been assigned.
% DHCP6_CLASS_ASSIGNED %1: client packet has been assigned to the following class: %2
+Logged at debug log level 40.
This debug message informs that incoming packet has been assigned to specified
class. This is a normal behavior and indicates successful operation.
The first argument specifies the client and transaction identification
packet has been assigned.
% DHCP6_CLASS_UNCONFIGURED %1: client packet belongs to an unconfigured class: %2
+Logged at debug log level 40.
This debug message informs that incoming packet belongs to a class
which cannot be found in the configuration. Either a hook written
before the classification was added to Kea is used, or class naming is
inconsistent.
% DHCP6_CLASS_UNDEFINED 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 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.
shown depends upon the packet queue type selected.
% DHCP6_CONFIG_RECEIVED received configuration: %1
+Logged at debug log level 10.
A debug message listing the configuration received by the DHCPv6 server.
The source of that configuration depends on used configuration backend.
% DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1
+Logged at debug log level 10.
This is a debug message that is issued every time the server receives a
configuration. That happens start up and also when a server configuration
change is committed by the administrator.
service has been restored.
% DHCP6_DDNS_CREATE_ADD_NAME_CHANGE_REQUEST %1: created name change request: %2
+Logged at debug log level 50.
This debug message is logged when the new NameChangeRequest has been created
to perform the DNS Update, which adds new RRs.
% DHCP6_DDNS_FQDN_GENERATED %1: generated FQDN for the client: %2
+Logged at debug log level 55.
This debug message is logged when the server generated FQDN (name)
for the client which message is processed. The names may be
generated by the server when required by the server's policy or
address. The third argument includes the reason for the failure.
% DHCP6_DDNS_GENERATE_FQDN %1: client did not send a FQDN option; FQDN will be
+Logged at debug log level 50.
generated for the client.
This debug message is issued when the server did not receive a FQDN option
from the client and client name replacement is enabled. This provides a means
to create DNS entries for unsophisticated clients.
% DHCP6_DDNS_RECEIVE_FQDN %1: received DHCPv6 Client FQDN option: %2
+Logged at debug log level 50.
This debug message is logged when server has found the DHCPv6 Client FQDN Option
sent by a client and started processing it. The first argument includes the
client and transaction identification information. The second argument
includes the received FQDN.
% DHCP6_DDNS_REMOVE_OLD_LEASE_FQDN %1: FQDN for a lease: %2 has changed. New values: hostname = %3, reverse mapping = %4, forward mapping = %5
+Logged at debug log level 50.
This debug message is logged during lease renewal when an old lease that is
no longer being offered has a different FQDN than the renewing lease. Thus
the old DNS entries need to be removed. The first argument includes the client
networking error.
% DHCP6_DDNS_RESPONSE_FQDN_DATA %1: including FQDN option in the server's response: %2
+Logged at debug log level 50.
This debug message is issued when the server is adding the Client FQDN
option in its response to the client. The first argument includes the
client and transaction identification information. The second argument
to this message may reappear.
% DHCP6_DECLINE_PROCESS_IA Processing of IA (IAID: %1) from client %2 started.
+Logged at debug log level 50.
This debug message is printed when the server starts processing an IA_NA option
received in Decline message. It's expected that the option will contain an
address that is being declined. Specific information will be printed in a
(vs stable) one: the second number of the version is odd.
% DHCP6_DHCP4O6_PACKET_RECEIVED received DHCPv4o6 packet from DHCPv4 server (type %1) for %2 port %3 on interface %4
+Logged at debug log level 40.
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv4 server over inter-process communication.
% DHCP6_DHCP4O6_RECEIVE_FAIL failed to receive DHCPv4o6: %1
+Logged at debug log level 50.
This debug message indicates the inter-process communication with the
DHCPv4 server failed. The reason for the error is included in
the message.
% DHCP6_DHCP4O6_RECEIVING receiving DHCPv4o6 packet from DHCPv4 server
+Logged at debug log level 50.
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv4 server over inter-process communication socket.
% DHCP6_DHCP4O6_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
+Logged at debug log level 55.
A debug message including the detailed data about the packet being sent
to the client. The first argument contains the client and the transaction
identification information. The second and third argument contains the
succeeded.
% DHCP6_FLEX_ID %1: flexible identifier generated for incoming packet: %2
+Logged at debug log level 40.
This debug message is printed when host reservation type is set to flexible identifier
and the expression specified in its configuration generated (was evaluated to)
an identifier for incoming packet. This debug message is mainly intended as a
processing. This likely indicates a coding error and should be reported to ISC.
% DHCP6_HOOK_BUFFER_RCVD_DROP received buffer from %1 to %2 over interface %3 was dropped because a callout set the drop flag
+Logged at debug log level 15.
This debug message is printed when a callout installed on buffer6_receive
hook point set the drop flag. For this particular hook point, the
setting of the flag by a callout instructs the server to drop the packet.
the name of the interface over which the buffer has been received.
% DHCP6_HOOK_BUFFER_RCVD_SKIP received buffer from %1 to %2 over interface %3 is not parsed because a callout set the next step to SKIP
+Logged at debug log level 50.
This debug message is printed when a callout installed on
buffer6_receive hook point set the next step status to skip. For this particular
hook point, this value set by a callout instructs the server to
name of the interface over which the buffer has been received.
% DHCP6_HOOK_BUFFER_SEND_SKIP %1: prepared DHCPv6 response was dropped because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on buffer6_send
hook point set the next step to SKIP value. For this particular hook point, the
SKIP setting a callout instructs the server to drop the packet.
information.
% DHCP6_HOOK_DDNS_UPDATE A hook has updated the DDNS parameters: hostname %1=>%2, forward update %3=>%4, reverse update %5=>%6
+Logged at debug log level 15.
This message indicates that there was a hook called on ddns6_update hook point
and that hook updated the DDNS update parameters: hostname, or whether to
conduct forward (A record) or reverse (PTR record) DDNS updates.
% DHCP6_HOOK_DECLINE_DROP During Decline processing (client=%1, interface=%2, addr=%3) hook callout set next step to DROP, dropping packet.
+Logged at debug log level 15.
This message indicates that the server received DECLINE message, it was verified
to be correct and matching server's lease information. The server called hooks
for the lease6_decline hook point and one of the callouts set next step status to DROP.
received. The lease will continue to be assigned to this client.
% DHCP6_HOOK_DECLINE_SKIP During Decline processing (client=%1, interface=%2, addr=%3) hook callout set status to SKIP, skipping decline.
+Logged at debug log level 50.
This message indicates that the server received DECLINE message, it was verified
to be correct and matching server's lease information. The server called hooks
for the lease6_decline hook point and one of the callouts set next step status to SKIP.
as if the decline actually took place.
% DHCP6_HOOK_LEASE6_RELEASE_NA_SKIP %1: DHCPv6 address lease was not released because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
lease6_release hook point set the next step to SKIP. For this particular hook
point, this setting by a callout instructs the server to not
client and transaction identification information.
% DHCP6_HOOK_LEASE6_RELEASE_PD_SKIP %1: prefix lease was not released because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease6_release
hook point set the next step to SKIP value. For this particular hook point, that
setting by a callout instructs the server to not release
client and transaction identification information.
% DHCP6_HOOK_LEASES6_COMMITTED_DROP %1: packet is dropped, because a callout set the next step to DROP
+Logged at debug log level 15.
This debug message is printed when a callout installed on the leases6_committed
hook point sets the next step to DROP.
% DHCP6_HOOK_LEASES6_COMMITTED_PARK %1: packet is parked, because a callout set the next step to PARK
+Logged at debug log level 40.
This debug message is printed when a callout installed on the leases6_committed
hook point sets the next step to PARK.
% DHCP6_HOOK_LEASES6_PARKING_LOT_FULL The parked-packet-limit %1, has been reached, dropping query: %2
+Logged at debug log level 15.
This debug message occurs when the parking lot used to hold client queries
while the hook library work for them completes has reached or exceeded the
limit set by the parked-packet-limit global parameter. This can occur when
those callouts can fulfill them.
% DHCP6_HOOK_PACKET_RCVD_SKIP %1: packet is dropped, because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the pkt6_receive
hook point sets the next step to SKIP. For this particular hook point, the
value setting instructs the server to drop the packet.
% DHCP6_HOOK_PACKET_SEND_DROP %1: prepared DHCPv6 response was not sent because a callout set the next ste to DROP
+Logged at debug log level 15.
This debug message is printed when a callout installed on the pkt6_send
hook point set the next step to DROP. For this particular hook point, the setting
of the value by a callout instructs the server to drop the packet. This
identification information.
% DHCP6_HOOK_PACKET_SEND_SKIP %1: prepared DHCPv6 response is not built because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
pkt6_send hook point set the next step to SKIP. For this particular hook
point, the setting of the value by a callout instructs the server to
information.
% DHCP6_HOOK_SUBNET6_SELECT_DROP %1: packet was dropped because a callout set the drop flag
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet6_select hook point set the drop flag. For this particular hook
point, the setting of the flag instructs the server to drop the
identification information.
% DHCP6_HOOK_SUBNET6_SELECT_PARK %1: packet was parked
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet6_select hook point set the park flag. The argument holds the
client and transaction identification information.
% DHCP6_HOOK_SUBNET6_SELECT_SKIP %1: no subnet was selected because a callout set the next step to SKIP
+Logged at debug log level 40.
This debug message is printed when a callout installed on the
subnet6_select hook point set the next step to SKIP value. For this particular hook
point, the setting of this value instructs the server not to choose a
provides more details about the issue.
% DHCP6_LEASE_ADVERT %1: lease for address %2 and iaid=%3 will be advertised
+Logged at debug log level 50.
This informational message indicates that the server will advertise an
address to the client in the ADVERTISE message. The client will
request allocation of this address with the REQUEST message sent
hold the allocated address and IAID.
% DHCP6_LEASE_ADVERT_FAIL %1: failed to advertise an address lease for iaid=%2
+Logged at debug log level 50.
This message indicates that in response to a received SOLICIT, the server
failed to advertise a non-temporary lease for a given client. There may
be many reasons for such failure. Each failure is logged in a separate
information. The second argument holds the IAID.
% DHCP6_LEASE_ALLOC %1: lease for address %2 and iaid=%3 has been allocated for %4 seconds
+Logged at debug log level 50.
This informational message indicates that in response to a client's REQUEST
message, the server successfully granted a non-temporary address
lease. This is a normal behavior and indicates successful operation.
IAID and validity lifetime.
% DHCP6_LEASE_ALLOC_FAIL %1: failed to grant an address lease for iaid=%2
+Logged at debug log level 50.
This message indicates that in response to a received REQUEST, the server
failed to grant a non-temporary address lease for the client. There may
be many reasons for such failure. Each failure is logged in a separate
information. The second argument holds the IAID.
% DHCP6_LEASE_DATA %1: detailed lease information for iaid=%2: %3
+Logged at debug log level 55.
This debug message is used to print the detailed information about the
allocated lease or a lease which will be advertised to the client.
The first argument holds the client and the transaction identification
configured to receive the traffic.
% DHCP6_OPEN_SOCKET opening service sockets on port %1
+Logged at debug log level 0.
A debug message issued during startup, this indicates that the IPv6 DHCP
server is about to open sockets on the specified port.
for the failure is appended as an argument of the log message.
% DHCP6_PACKET_DROP_DHCP_DISABLED %1: DHCP service is globally disabled
+Logged at debug log level 15.
This debug message is issued when a packet is dropped because the DHCP service
has been temporarily disabled. This affects all received DHCP packets. The
service may be enabled by the "dhcp-enable" control command or automatically
after a specified amount of time since receiving "dhcp-disable" command.
% DHCP6_PACKET_DROP_DROP_CLASS dropped as member of the special class 'DROP': %1 %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
into the special class 'DROP' and dropped. The packet details are displayed.
% DHCP6_PACKET_DROP_DROP_CLASS2 dropped as member of the special class 'DROP' after host reservation lookup: %1 %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
after host reservation lookup into the special class 'DROP' and dropped.
The packet details are displayed.
% DHCP6_PACKET_DROP_DROP_CLASS_EARLY dropped as member of the special class 'DROP' after early global host reservations lookup: %1 %2
+Logged at debug log level 15.
This debug message is emitted when an incoming packet was classified
after early global host reservations lookup into the special class 'DROP'
and dropped. The packet details are displayed.
% DHCP6_PACKET_DROP_DUPLICATE dropped as sent by the same client than a packet being processed by another thread: dropped %1 %2 by thread %3 as duplicate of %4 %5 processed by %6
+Logged at debug log level 15.
Currently multi-threading processing avoids races between packets sent by
the same client by dropping new packets until processing is finished.
Packet details and thread identifiers are included for both packets in
this warning message.
% DHCP6_PACKET_DROP_PARSE_FAIL %1: failed to parse packet from %2 to %3, received over interface %4, reason: %5, %6
+Logged at debug log level 15.
The DHCPv6 server has received a packet that it is unable to
interpret. The reason why the packet is invalid is included in the message.
% DHCP6_PACKET_DROP_SERVERID_MISMATCH %1: dropping packet with server identifier: %2, server is using: %3
+Logged at debug log level 15.
A debug message noting that server has received message with server identifier
option that not matching server identifier that server is using.
% DHCP6_PACKET_DROP_UNICAST %1: dropping unicast %2 packet as this packet should be sent to multicast
+Logged at debug log level 15.
This debug message is issued when the server drops the unicast packet,
because packets of this type must be sent to multicast. The first argument
specifies the client and transaction identification information, the
second argument specifies packet type.
% DHCP6_PACKET_OPTIONS_SKIPPED %1: An error unpacking an option, caused subsequent options to be skipped: %2
+Logged at debug log level 50.
A debug message issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
server will still attempt to service the packet.
loop.
% DHCP6_PACKET_PROCESS_FAIL %1: processing of %2 message received from %3 failed: %4
+Logged at debug log level 40.
This is a general catch-all message indicating that the processing of the
specified packet type from the indicated address failed. The reason is given in the
message. The server will not send a response but will instead ignore the packet.
loop.
% DHCP6_PACKET_QUEUE_FULL multi-threading packet queue is full
+Logged at debug log level 40.
A debug message noting that the multi-threading packet queue is full so
the oldest packet of the queue was dropped to make room for the received one.
failure is given in the message.
% DHCP6_PD_LEASE_ADVERT %1: lease for prefix %2/%3 and iaid=%4 will be advertised
+Logged at debug log level 50.
This informational message indicates that the server will advertise a
prefix to the client in the ADVERTISE message. The client will
request allocation of this prefix with the REQUEST message sent
hold the allocated prefix, prefix length and IAID.
% DHCP6_PD_LEASE_ADVERT_FAIL %1: failed to advertise a prefix lease for iaid=%2
+Logged at debug log level 50.
This message indicates that in response to a received SOLICIT, the
server failed to advertise a prefix lease for a given client. There may
be many reasons for such failure. Each failure is logged in a separate
information. The second argument holds the IAID.
% DHCP6_PD_LEASE_ALLOC %1: lease for prefix %2/%3 and iaid=%4 has been allocated for %5 seconds
+Logged at debug log level 50.
This informational message indicates that in response to a client's REQUEST
message, the server successfully granted a prefix lease.
This is a normal behavior and indicates successful operation.
prefix length, IAID and validity lifetime.
% DHCP6_PD_LEASE_ALLOC_FAIL %1: failed to grant a prefix lease for iaid=%2
+Logged at debug log level 50.
This message indicates that in response to a received REQUEST, the server
failed to grant a prefix lease for the client. There may be many reasons
for such failure. Each failure is logged in a separate log entry. The first
prefix length, IAID and validity lifetime.
% DHCP6_PROCESS_IA_NA_EXTEND %1: extending lease lifetime for IA_NA option with iaid=%2
+Logged at debug log level 50.
This message is logged when the server is starting to extend the lifetime
of the address lease associated with the particular IAID. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.
% DHCP6_PROCESS_IA_NA_RELEASE %1: releasing lease for IA_NA option with iaid=%2
+Logged at debug log level 50.
This message is logged when the server is trying to release the client's
as a result of receiving the RELEASE message. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.
% DHCP6_PROCESS_IA_NA_REQUEST %1: server is processing IA_NA option with iaid=%2 and hint=%3
+Logged at debug log level 50.
This is a debug message that indicates the processing of a received
IA_NA option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
that the hint hasn't been sent.
% DHCP6_PROCESS_IA_NA_SOLICIT %1: server is processing IA_NA option with iaid=%2 and hint=%3
+Logged at debug log level 50.
This is a debug message that indicates the processing of a received
IA_NA option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
that the hint hasn't been sent.
% DHCP6_PROCESS_IA_PD_EXTEND %1: extending lease lifetime for IA_PD option with iaid=%2
+Logged at debug log level 50.
This message is logged when the server is starting to extend the lifetime
of the prefix lease associated with the particular IAID. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.
% DHCP6_PROCESS_IA_PD_REQUEST %1: server is processing IA_PD option with iaid=%2 and hint=%3
+Logged at debug log level 50.
This is a debug message that indicates a processing of received IA_PD
option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
that the hint hasn't been sent.
% DHCP6_PROCESS_IA_PD_SOLICIT %1: server is processing IA_PD option with iaid=%2 and hint=%3
+Logged at debug log level 50.
This is a debug message that indicates a processing of received IA_PD
option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
that the hint hasn't been sent.
% DHCP6_QUERY_DATA %1, packet details: %2
+Logged at debug log level 55.
A debug message printing the details of the received packet. The first
argument includes the client and the transaction identification
information.
the client and the transaction identification information.
% DHCP6_RAPID_COMMIT %1: Rapid Commit option received, following 2-way exchange
+Logged at debug log level 50.
This debug message is issued when the server found a Rapid Commit option
in the client's message and 2-way exchanges are supported by the
server for the subnet on which the client is connected. The argument
expected IAID and IAID found respectively.
% DHCP6_REQUIRED_OPTIONS_CHECK_FAIL %1: %2 message received from %3 failed the following check: %4
+Logged at debug log level 40.
This message indicates that received DHCPv6 packet is invalid. This may be due
to a number of reasons, e.g. the mandatory client-id option is missing,
the server-id forbidden in that particular type of message is present,
lease lookup when multi-threading is enabled overwriting configured value.
% DHCP6_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
+Logged at debug log level 55.
A debug message including the detailed data about the packet being sent
to the client. The first argument contains the client and the transaction
identification information. The second and third argument contains the
The reason for the failure is included in the message.
% DHCP6_SHUTDOWN server shutdown
+Logged at debug log level 40.
The IPv6 DHCP server has terminated normally.
% DHCP6_SHUTDOWN_REQUEST shutdown of server requested
+Logged at debug log level 40.
This debug message indicates that a shutdown of the IPv6 server has
been requested via a call to the 'shutdown' method of the core Dhcpv6Srv
object.
is also printed.
% DHCP6_START_INFO pid: %1, server port: %2, client port: %3, verbose: %4
+Logged at debug log level 0.
This is a debug message issued during the IPv6 DHCP server startup.
It lists some information about the parameters with which the server
is running.
% DHCP6_SUBNET_DATA %1: the selected subnet details: %2
+Logged at debug log level 55.
This debug message includes the details of the subnet selected for
the client. The first argument includes the client and the
transaction identification information. The second argument
includes the subnet details.
% DHCP6_SUBNET_DYNAMICALLY_CHANGED %1: changed selected subnet %2 to subnet %3 from shared network %4 for client assignments
+Logged at debug log level 45.
This debug message indicates that the server is using another subnet
than initially selected for client assignments. This newly selected
subnet belongs to the same shared network as the original subnet.
includes some static reservations for this client.
% DHCP6_SUBNET_SELECTED %1: the subnet with ID %2 was selected for client assignments
+Logged at debug log level 45.
This is a debug message noting the selection of a subnet to be used for
address and option assignment. Subnet selection is one of the early
steps in the processing of incoming client message. The first
information. The second argument holds the selected subnet id.
% DHCP6_SUBNET_SELECTION_FAILED %1: failed to select subnet for the client
+Logged at debug log level 50.
This debug message indicates that the server failed to select the
subnet for the client which has sent a message to the server.
The cause is likely due to a misconfiguration of the server. The packet
the client and the transaction identification information.
% DHCP6_UNKNOWN_MSG_RECEIVED %1: received unknown message (type %2) on interface %3
+Logged at debug log level 40.
This debug message is printed when server receives a message of unknown type.
That could either mean missing functionality or invalid or broken relay or client.
The list of formally defined message types is available here:
was retrieved using NETCONF and successfully applied to Kea server.
% NETCONF_CONFIG_CHANGED_DETAIL YANG configuration changed: %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.
got an unrecoverable error from within the event loop.
% NETCONF_GET_CONFIG got configuration from %1 server: %2
+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.
The server name, module name and the error are printed.
% NETCONF_RUN_EXIT application is exiting the event loop
+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.
% NETCONF_SET_CONFIG set configuration to %1 server: %2
+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.
notifications for a Kea server. The server name and module name are printed.
% NETCONF_UPDATE_CONFIG updating configuration with %1 server: %2
+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.
configuration of a Kea server.
% NETCONF_VALIDATE_CONFIG validating configuration with %1 server: %2
+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.
-# Copyright (C) 2019-2020 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2019-2024 Internet Systems Consortium, Inc. ("ISC")
% BOOTP_BOOTP_QUERY recognized a BOOTP query: %1
+Logged at debug log level 40.
This debug message is printed when the BOOTP query was recognized. The
BOOTP client class was added and the message type set to DHCPREQUEST.
The query client and transaction identification are displayed.
This info message indicates that the Bootp hooks library has been loaded.
% BOOTP_PACKET_OPTIONS_SKIPPED an error unpacking an option, caused subsequent options to be skipped: %1
+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.
% BOOTP_PACKET_PACK %1: preparing on-wire format of the packet to be sent
+Logged at debug log level 40.
This debug message is issued when the server starts preparing the on-wire
format of the packet to be sent back to the client. The argument specifies
the client and the transaction identification information.
BOOTP transaction. The second argument includes the error string.
% BOOTP_PACKET_UNPACK_FAILED failed to parse query from %1 to %2, received over interface %3, reason: %4
+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,
-# Copyright (C) 2019-2022 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2019-2024 Internet Systems Consortium, Inc. ("ISC")
% FLEX_OPTION_LOAD_ERROR loading Flex Option hooks library failed: %1
This error message indicates an error during loading the Flex Option
the log message.
% FLEX_OPTION_PROCESS_ADD Added the option code %1 with value %2
+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.
% FLEX_OPTION_PROCESS_CLIENT_CLASS Skip processing of the option code %1 for class '%2'
+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.
of the log message.
% FLEX_OPTION_PROCESS_REMOVE Removed option code %1
+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.
% FLEX_OPTION_PROCESS_SUB_ADD Added the sub-option code %1 in option code %2 with value %3
+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.
% FLEX_OPTION_PROCESS_SUB_CLIENT_CLASS Skip processing of the sub-option code %1 in option code %2 for class '%3'
+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.
% FLEX_OPTION_PROCESS_SUB_REMOVE Removed sub-option code %1 in option code %2
+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.
% FLEX_OPTION_PROCESS_SUB_SUPERSEDE Supersedes the sub-option code %1 in option code %2 with value %3
+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.
% FLEX_OPTION_PROCESS_SUPERSEDE Supersedes the option code %1 with value %2
+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.
% FLEX_OPTION_PROCESS_VENDOR_ID_MISMATCH 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.
The argument contains a reason for the error.
% HA_BUFFER4_RECEIVE_NOT_FOR_US %1: dropping query to be processed by another server
+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
information retrieved from the query.
% HA_BUFFER4_RECEIVE_PACKET_OPTIONS_SKIPPED an error unpacking an option, caused subsequent options to be skipped: %1
+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.
% HA_BUFFER4_RECEIVE_UNPACK_FAILED failed to parse query from %1 to %2, received over interface %3, reason: %4
+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,
The argument contains a reason for the error.
% HA_BUFFER6_RECEIVE_NOT_FOR_US %1: dropping query to be processed by another server
+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
information retrieved from the query.
% HA_BUFFER6_RECEIVE_PACKET_OPTIONS_SKIPPED an error unpacking an option, caused subsequent options to be skipped: %1
+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.
% HA_BUFFER6_RECEIVE_UNPACK_FAILED failed to parse query from %1 to %2, received over interface %3, reason: %4
+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,
The argument contains a reason for the error.
% HA_LEASES4_COMMITTED_NOTHING_TO_UPDATE %1: leases4_committed callout was invoked without any leases
+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
The argument contains a reason for the error.
% HA_LEASES6_COMMITTED_NOTHING_TO_UPDATE %1: leases6_committed callout was invoked without any leases
+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
the failure.
% HA_LEASE_SYNC_STALE_LEASE4_SKIP %1: skipping stale lease %2 in subnet %3
+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
address. The third argument specifies a subnet to which the lease belongs.
% HA_LEASE_SYNC_STALE_LEASE6_SKIP %1: skipping stale lease %2 in subnet %3
+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
configuration parameter.
% HA_LOAD_BALANCING_DUID_MISSING %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 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.
% HA_LOAD_BALANCING_IDENTIFIER_MISSING %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 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
is a subnet prefix.
% HA_SUBNET4_SELECT_NOT_FOR_US %1: dropping query in relationship %2 to be processed by another server
+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
prefix.
% HA_SUBNET4_SELECT_NO_SUBNET_SELECTED %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 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.
is a subnet prefix.
% HA_SUBNET6_SELECT_NOT_FOR_US %1: dropping query in relationship %2 to be processed by another server
+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
prefix.
% HA_SUBNET6_SELECT_NO_SUBNET_SELECTED %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 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.
# Copyright (C) 2017-2024 Internet Systems Consortium, Inc. ("ISC")
% LEASE_CMDS_ADD4 lease4-add command successful (address: %1)
+Logged at debug log level 20.
The lease4-add command has been successful. Lease IPv4 address
is logged.
parameters passed are logged.
% LEASE_CMDS_ADD6 lease6-add command successful (address: %1)
+Logged at debug log level 20.
The lease6-add command has been successful. Lease IPv6 address
is logged.
parameters passed are logged.
% LEASE_CMDS_BULK_APPLY6 lease6-bulk-apply command successful (applied addresses count: %1)
+Logged at debug log level 20.
The lease6-bulk-apply command has been successful. The number of applied
addresses is logged.
removed successfully.
% LEASE_CMDS_DEL4 lease4-del command successful (address: %1)
+Logged at debug log level 20.
The attempt to delete an IPv4 lease (lease4-del command) has been successful.
Lease IPv4 address is logged.
reason as well as the parameters passed are logged.
% LEASE_CMDS_DEL6 lease4-del command successful (address: %1)
+Logged at debug log level 20.
The attempt to delete an IPv4 lease (lease4-del command) has been successful.
Lease IPv6 address is logged.
reason for the failure is logged.
% LEASE_CMDS_UPDATE4 lease4-update command successful (address: %1)
+Logged at debug log level 20.
The lease4-update command has been successful. Lease IPv4 address
is logged.
parameters passed are logged.
% LEASE_CMDS_UPDATE6 lease6-update command successful (address: %1)
+Logged at debug log level 20.
The lease6-update command has been successful. Lease IPv6 address
is logged.
-# Copyright (C) 2018-2023 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2018-2024 Internet Systems Consortium, Inc. ("ISC")
$NAMESPACE isc::cb
% MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4 create or update option pool start: %1 pool end: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by pool
% MYSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6 create or update option pool start: %1 pool end: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by pool
% MYSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6 create or update option prefix: %1 prefix len: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by prefix
% MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4 create or update option 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
% MYSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6 create or update option 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
% MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS4 create or update client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update client class
% MYSQL_CB_CREATE_UPDATE_CLIENT_CLASS6 create or update client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update client class
% MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4 create or update global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update global parameter
% MYSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6 create or update global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update global parameter
% MYSQL_CB_CREATE_UPDATE_OPTION4 create or update option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option
% MYSQL_CB_CREATE_UPDATE_OPTION6 create or update option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option
% MYSQL_CB_CREATE_UPDATE_OPTION_DEF4 create or update option definition: %1 code: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option definition
% MYSQL_CB_CREATE_UPDATE_OPTION_DEF6 create or update option definition: %1 code: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option definition
% MYSQL_CB_CREATE_UPDATE_SERVER4 create or update server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update a DHCPv4
server information.
% MYSQL_CB_CREATE_UPDATE_SERVER6 create or update server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update a DHCPv6
server information.
% MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK4 create or update shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network
% MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK6 create or update shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network
% MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4 create or update shared network: %1 option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network option
% MYSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6 create or update shared network: %1 option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network option
% MYSQL_CB_CREATE_UPDATE_SUBNET4 create or update subnet: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update subnet
% MYSQL_CB_CREATE_UPDATE_SUBNET6 create or update subnet: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update subnet
% MYSQL_CB_DEINIT_OK unloading MYSQL CB hooks library successful
library has been unloaded successfully.
% MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4 delete all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all client classes
% MYSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all client classes
% MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6 delete all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all client classes
% MYSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all client classes
% MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4 delete all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all global parameters
% MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all global parameters
% MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6 delete all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all global parameters
% MYSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all global parameters
% MYSQL_CB_DELETE_ALL_OPTION_DEFS4 delete all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all option definitions
% MYSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all option definitions
% MYSQL_CB_DELETE_ALL_OPTION_DEFS6 delete all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all option definitions
% MYSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all option definitions
% MYSQL_CB_DELETE_ALL_SERVERS4 delete all DHCPv4 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all servers.
% MYSQL_CB_DELETE_ALL_SERVERS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all servers.
% MYSQL_CB_DELETE_ALL_SERVERS6 delete all DHCPv6 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all servers.
% MYSQL_CB_DELETE_ALL_SERVERS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all servers.
% MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4 delete all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all shared networks
% MYSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all shared networks
% MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6 delete all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all shared networks
% MYSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all shared networks
% MYSQL_CB_DELETE_ALL_SUBNETS4 delete all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all subnets
% MYSQL_CB_DELETE_ALL_SUBNETS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all subnets
% MYSQL_CB_DELETE_ALL_SUBNETS6 delete all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all subnets
% MYSQL_CB_DELETE_ALL_SUBNETS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all subnets
% MYSQL_CB_DELETE_BY_POOL_OPTION4 delete pool start: %1 pool end: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by pool
% MYSQL_CB_DELETE_BY_POOL_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by pool
% MYSQL_CB_DELETE_BY_POOL_OPTION6 delete pool start: %1 pool end: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by pool
% MYSQL_CB_DELETE_BY_POOL_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by pool
% MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6 delete prefix: %1 prefix len: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by prefix
% MYSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by prefix
% MYSQL_CB_DELETE_BY_PREFIX_SUBNET4 delete subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by prefix
% MYSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by prefix
% MYSQL_CB_DELETE_BY_PREFIX_SUBNET6 delete subnet by prefix: %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 deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by prefix
% MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4 delete by subnet id: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6 delete by subnet id: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4 delete subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6 delete subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by subnet id
% MYSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by subnet id
% MYSQL_CB_DELETE_CLIENT_CLASS4 delete client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete client class
% MYSQL_CB_DELETE_CLIENT_CLASS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete client class
% MYSQL_CB_DELETE_CLIENT_CLASS6 delete client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete client class
% MYSQL_CB_DELETE_CLIENT_CLASS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete client class
% MYSQL_CB_DELETE_GLOBAL_PARAMETER4 delete global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete global parameter
% MYSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete global parameter
% MYSQL_CB_DELETE_GLOBAL_PARAMETER6 delete global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete global parameter
% MYSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT 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 delete option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option
% MYSQL_CB_DELETE_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option
% MYSQL_CB_DELETE_OPTION6 delete option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option
% MYSQL_CB_DELETE_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option
% MYSQL_CB_DELETE_OPTION_DEF4 delete option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option definition
% MYSQL_CB_DELETE_OPTION_DEF4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option definition
% MYSQL_CB_DELETE_OPTION_DEF6 delete option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option definition
% MYSQL_CB_DELETE_OPTION_DEF6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option definition
% MYSQL_CB_DELETE_SERVER4 delete DHCPv4 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete a server.
% MYSQL_CB_DELETE_SERVER4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete a server.
% MYSQL_CB_DELETE_SERVER6 delete DHCPv6 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete a server.
% MYSQL_CB_DELETE_SERVER6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete a server.
% MYSQL_CB_DELETE_SHARED_NETWORK4 delete shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network
% MYSQL_CB_DELETE_SHARED_NETWORK4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network
% MYSQL_CB_DELETE_SHARED_NETWORK6 delete shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network
% MYSQL_CB_DELETE_SHARED_NETWORK6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network
% MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4 delete shared network: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network option
% MYSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network option
% MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6 delete shared network: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network option
% MYSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network option
% MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4 delete shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network subnets
% MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network subnets
% MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6 delete shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network subnets
% MYSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network subnets
% MYSQL_CB_GET_ALL_CLIENT_CLASSES4 retrieving all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all client classes
% MYSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all client classes
% MYSQL_CB_GET_ALL_CLIENT_CLASSES6 retrieving all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all client classes
% MYSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all client classes
% MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4 retrieving all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all global parameters
% MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all global parameters
% MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6 retrieving all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all global parameters
% MYSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all global parameters
% MYSQL_CB_GET_ALL_OPTIONS4 retrieving all options
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all options
% MYSQL_CB_GET_ALL_OPTIONS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all options
% MYSQL_CB_GET_ALL_OPTIONS6 retrieving all options
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all options
% MYSQL_CB_GET_ALL_OPTIONS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all options
% MYSQL_CB_GET_ALL_OPTION_DEFS4 retrieving all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all option definitions
% MYSQL_CB_GET_ALL_OPTION_DEFS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all option definitions
% MYSQL_CB_GET_ALL_OPTION_DEFS6 retrieving all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all option definitions
% MYSQL_CB_GET_ALL_OPTION_DEFS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all option definitions
% MYSQL_CB_GET_ALL_SERVERS4 retrieving all servers
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all DHCPv4
servers
% MYSQL_CB_GET_ALL_SERVERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all DHCPv4
servers
% MYSQL_CB_GET_ALL_SERVERS6 retrieving all DHCPv6 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all DHCPv6
servers
% MYSQL_CB_GET_ALL_SERVERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all DHCPv6
servers
% MYSQL_CB_GET_ALL_SHARED_NETWORKS4 retrieving all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all shared networks
% MYSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all shared networks
% MYSQL_CB_GET_ALL_SHARED_NETWORKS6 retrieving all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all shared networks
% MYSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all shared networks
% MYSQL_CB_GET_ALL_SUBNETS4 retrieving all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all subnets
% MYSQL_CB_GET_ALL_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all subnets
% MYSQL_CB_GET_ALL_SUBNETS6 retrieving all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all subnets
% MYSQL_CB_GET_ALL_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all subnets
% MYSQL_CB_GET_CLIENT_CLASS4 retrieving client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a client class
% MYSQL_CB_GET_CLIENT_CLASS6 retrieving client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a client class
% MYSQL_CB_GET_GLOBAL_PARAMETER4 retrieving global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve global parameter
% MYSQL_CB_GET_GLOBAL_PARAMETER6 retrieving global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve global parameter
% MYSQL_CB_GET_HOST4 get host
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve host
% MYSQL_CB_GET_HOST6 get host
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve host
% MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4 retrieving modified client classes from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified client classes from specified time
% MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified client classes from specified time
% MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6 retrieving modified client classes from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified client classes from specified time
% MYSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified client classes from specified time
% MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4 retrieving modified global parameters from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified global parameters from specified time
% MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified global parameters from specified time
% MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6 retrieving modified global parameters from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified global parameters from specified time
% MYSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified global parameters from specified time
% MYSQL_CB_GET_MODIFIED_OPTIONS4 retrieving modified options from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified options from specified time
% MYSQL_CB_GET_MODIFIED_OPTIONS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified options from specified time
% MYSQL_CB_GET_MODIFIED_OPTIONS6 retrieving modified options from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified options from specified time
% MYSQL_CB_GET_MODIFIED_OPTIONS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified options from specified time
% MYSQL_CB_GET_MODIFIED_OPTION_DEFS4 retrieving modified option definitions from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified option definitions from specified time
% MYSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified option definitions from specified time
% MYSQL_CB_GET_MODIFIED_OPTION_DEFS6 retrieving modified option definitions from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified option definitions from specified time
% MYSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified option definitions from specified time
% MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4 retrieving modified shared networks from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified shared networks from specified time
% MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified shared networks from specified time
% MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6 retrieving modified shared networks from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified shared networks from specified time
% MYSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified shared networks from specified time
% MYSQL_CB_GET_MODIFIED_SUBNETS4 retrieving modified subnets from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified subnets from specified time
% MYSQL_CB_GET_MODIFIED_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified subnets from specified time
% MYSQL_CB_GET_MODIFIED_SUBNETS6 retrieving modified subnets from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified subnets from specified time
% MYSQL_CB_GET_MODIFIED_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified subnets from specified time
% MYSQL_CB_GET_OPTION4 retrieving option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option
% MYSQL_CB_GET_OPTION6 retrieving option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option
% MYSQL_CB_GET_OPTION_DEF4 retrieving option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option definition
% MYSQL_CB_GET_OPTION_DEF6 retrieving option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option definition
% MYSQL_CB_GET_PORT4 get port
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve port
% MYSQL_CB_GET_PORT6 get port
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve port
% MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4 retrieving audit entries from: %1 %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve audit entries from specified time and id.
% MYSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve audit entries from specified time
% MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6 retrieving audit entries from: %1 %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve audit entries from specified time and id
% MYSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve audit entries from specified time
% MYSQL_CB_GET_SERVER4 retrieving DHCPv4 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a DHCPv4 server information.
% MYSQL_CB_GET_SERVER6 retrieving DHCPv6 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a DHCPv6 server information.
% MYSQL_CB_GET_SHARED_NETWORK4 retrieving shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network
% MYSQL_CB_GET_SHARED_NETWORK6 retrieving shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network
% MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4 retrieving shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network subnets
% MYSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve shared network subnets
% MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6 retrieving shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network subnets
% MYSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve shared network subnets
% MYSQL_CB_GET_SUBNET4_BY_PREFIX retrieving subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by prefix
% MYSQL_CB_GET_SUBNET4_BY_SUBNET_ID retrieving subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by subnet id
% MYSQL_CB_GET_SUBNET6_BY_PREFIX retrieving subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by prefix
% MYSQL_CB_GET_SUBNET6_BY_SUBNET_ID retrieving subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by subnet id
% MYSQL_CB_GET_TYPE4 get type
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve type
% MYSQL_CB_GET_TYPE6 get type
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve type
% MYSQL_CB_INIT_OK loading MYSQL CB hooks library successful
is typically a network or database server issue.
% MYSQL_CB_REGISTER_BACKEND_TYPE4 register backend
+Logged at debug log level 40.
Debug message issued when triggered an action to register backend
% MYSQL_CB_REGISTER_BACKEND_TYPE6 register backend
+Logged at debug log level 40.
Debug message issued when triggered an action to register backend
% MYSQL_CB_TLS_CIPHER TLS cipher: %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.
% MYSQL_CB_UNREGISTER_BACKEND_TYPE4 unregister backend
+Logged at debug log level 40.
Debug message issued when triggered an action to unregister backend
% MYSQL_CB_UNREGISTER_BACKEND_TYPE6 unregister backend
+Logged at debug log level 40.
Debug message issued when triggered an action to unregister backend
removed successfully.
% PERFMON_DHCP4_PKT_EVENTS query: %1 events=[%2]
+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.
% PERFMON_DHCP4_PKT_PROCESS_ERROR Packet event stack was not processed for query %1, reason %2
+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
operations.
% PERFMON_DHCP4_SOCKET_RECEIVED_TIME_SUPPORT Kernel supports socket received time? %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-dhcp4 can supply
the timestamp a packet was received by the kernel for recording
will not have data available to determine kernel buffer wait times.
% PERFMON_DHCP6_PKT_EVENTS query: %1 events=[%2]
+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.
% PERFMON_DHCP6_PKT_PROCESS_ERROR Packet event stack was not processed for query %1, reason %2
+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
operations.
% PERFMON_DHCP6_SOCKET_RECEIVED_TIME_SUPPORT Kernel supports socket received time? %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
-# Copyright (C) 2021-2023 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2021-2024 Internet Systems Consortium, Inc. ("ISC")
$NAMESPACE isc::cb
% PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION4 create or update option pool start: %1 pool end: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by pool
% PGSQL_CB_CREATE_UPDATE_BY_POOL_OPTION6 create or update option pool start: %1 pool end: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by pool
% PGSQL_CB_CREATE_UPDATE_BY_PREFIX_OPTION6 create or update option prefix: %1 prefix len: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option by prefix
% PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION4 create or update option 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
% PGSQL_CB_CREATE_UPDATE_BY_SUBNET_ID_OPTION6 create or update option 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
% PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS4 create or update client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update client class
% PGSQL_CB_CREATE_UPDATE_CLIENT_CLASS6 create or update client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update client class
% PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER4 create or update global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update global parameter
% PGSQL_CB_CREATE_UPDATE_GLOBAL_PARAMETER6 create or update global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update global parameter
% PGSQL_CB_CREATE_UPDATE_OPTION4 create or update option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option
% PGSQL_CB_CREATE_UPDATE_OPTION6 create or update option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option
% PGSQL_CB_CREATE_UPDATE_OPTION_DEF4 create or update option definition: %1 code: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option definition
% PGSQL_CB_CREATE_UPDATE_OPTION_DEF6 create or update option definition: %1 code: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update option definition
% PGSQL_CB_CREATE_UPDATE_SERVER4 create or update server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update a DHCPv4
server information.
% PGSQL_CB_CREATE_UPDATE_SERVER6 create or update server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update a DHCPv6
server information.
% PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK4 create or update shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network
% PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK6 create or update shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network
% PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION4 create or update shared network: %1 option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network option
% PGSQL_CB_CREATE_UPDATE_SHARED_NETWORK_OPTION6 create or update shared network: %1 option
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update shared network option
% PGSQL_CB_CREATE_UPDATE_SUBNET4 create or update subnet: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update subnet
% PGSQL_CB_CREATE_UPDATE_SUBNET6 create or update subnet: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to create or update subnet
% PGSQL_CB_DEINIT_OK unloading Postgres CB hooks library successful
library has been unloaded successfully.
% PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4 delete all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all client classes
% PGSQL_CB_DELETE_ALL_CLIENT_CLASSES4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all client classes
% PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6 delete all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all client classes
% PGSQL_CB_DELETE_ALL_CLIENT_CLASSES6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all client classes
% PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4 delete all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all global parameters
% PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all global parameters
% PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6 delete all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all global parameters
% PGSQL_CB_DELETE_ALL_GLOBAL_PARAMETERS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all global parameters
% PGSQL_CB_DELETE_ALL_OPTION_DEFS4 delete all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all option definitions
% PGSQL_CB_DELETE_ALL_OPTION_DEFS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all option definitions
% PGSQL_CB_DELETE_ALL_OPTION_DEFS6 delete all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all option definitions
% PGSQL_CB_DELETE_ALL_OPTION_DEFS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all option definitions
% PGSQL_CB_DELETE_ALL_SERVERS4 delete all DHCPv4 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all servers.
% PGSQL_CB_DELETE_ALL_SERVERS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all servers.
% PGSQL_CB_DELETE_ALL_SERVERS6 delete all DHCPv6 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all servers.
% PGSQL_CB_DELETE_ALL_SERVERS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all servers.
% PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4 delete all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all shared networks
% PGSQL_CB_DELETE_ALL_SHARED_NETWORKS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all shared networks
% PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6 delete all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all shared networks
% PGSQL_CB_DELETE_ALL_SHARED_NETWORKS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all shared networks
% PGSQL_CB_DELETE_ALL_SUBNETS4 delete all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all subnets
% PGSQL_CB_DELETE_ALL_SUBNETS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all subnets
% PGSQL_CB_DELETE_ALL_SUBNETS6 delete all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete all subnets
% PGSQL_CB_DELETE_ALL_SUBNETS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete all subnets
% PGSQL_CB_DELETE_BY_POOL_OPTION4 delete pool start: %1 pool end: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by pool
% PGSQL_CB_DELETE_BY_POOL_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by pool
% PGSQL_CB_DELETE_BY_POOL_OPTION6 delete pool start: %1 pool end: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by pool
% PGSQL_CB_DELETE_BY_POOL_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by pool
% PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6 delete prefix: %1 prefix len: %2 option code: %3 space: %4
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by prefix
% PGSQL_CB_DELETE_BY_POOL_PREFIX_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by prefix
% PGSQL_CB_DELETE_BY_PREFIX_SUBNET4 delete subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by prefix
% PGSQL_CB_DELETE_BY_PREFIX_SUBNET4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by prefix
% PGSQL_CB_DELETE_BY_PREFIX_SUBNET6 delete subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by prefix
% PGSQL_CB_DELETE_BY_PREFIX_SUBNET6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by prefix
% PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4 delete by subnet id: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6 delete by subnet id: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4 delete subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6 delete subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete subnet by subnet id
% PGSQL_CB_DELETE_BY_SUBNET_ID_SUBNET6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete subnet by subnet id
% PGSQL_CB_DELETE_CLIENT_CLASS4 delete client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete client class
% PGSQL_CB_DELETE_CLIENT_CLASS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete client class
% PGSQL_CB_DELETE_CLIENT_CLASS6 delete client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete client class
% PGSQL_CB_DELETE_CLIENT_CLASS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete client class
% PGSQL_CB_DELETE_GLOBAL_PARAMETER4 delete global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete global parameter
% PGSQL_CB_DELETE_GLOBAL_PARAMETER4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete global parameter
% PGSQL_CB_DELETE_GLOBAL_PARAMETER6 delete global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete global parameter
% PGSQL_CB_DELETE_GLOBAL_PARAMETER6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete global parameter
% PGSQL_CB_DELETE_OPTION4 delete option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option
% PGSQL_CB_DELETE_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option
% PGSQL_CB_DELETE_OPTION6 delete option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option
% PGSQL_CB_DELETE_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option
% PGSQL_CB_DELETE_OPTION_DEF4 delete option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option definition
% PGSQL_CB_DELETE_OPTION_DEF4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option definition
% PGSQL_CB_DELETE_OPTION_DEF6 delete option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to delete option definition
% PGSQL_CB_DELETE_OPTION_DEF6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete option definition
% PGSQL_CB_DELETE_SERVER4 delete DHCPv4 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete a server.
% PGSQL_CB_DELETE_SERVER4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete a server.
% PGSQL_CB_DELETE_SERVER6 delete DHCPv6 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete a server.
% PGSQL_CB_DELETE_SERVER6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete a server.
% PGSQL_CB_DELETE_SHARED_NETWORK4 delete shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network
% PGSQL_CB_DELETE_SHARED_NETWORK4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network
% PGSQL_CB_DELETE_SHARED_NETWORK6 delete shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network
% PGSQL_CB_DELETE_SHARED_NETWORK6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network
% PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4 delete shared network: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network option
% PGSQL_CB_DELETE_SHARED_NETWORK_OPTION4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network option
% PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6 delete shared network: %1 option code: %2 space: %3
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network option
% PGSQL_CB_DELETE_SHARED_NETWORK_OPTION6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network option
% PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4 delete shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network subnets
% PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS4_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network subnets
% PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6 delete shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to delete shared network subnets
% PGSQL_CB_DELETE_SHARED_NETWORK_SUBNETS6_RESULT deleted: %1 entries
+Logged at debug log level 40.
Debug message indicating the result of an action to delete shared network subnets
% PGSQL_CB_GET_ALL_CLIENT_CLASSES4 retrieving all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all client classes
% PGSQL_CB_GET_ALL_CLIENT_CLASSES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all client classes
% PGSQL_CB_GET_ALL_CLIENT_CLASSES6 retrieving all client classes
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all client classes
% PGSQL_CB_GET_ALL_CLIENT_CLASSES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all client classes
% PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4 retrieving all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all global parameters
% PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all global parameters
% PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6 retrieving all global parameters
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all global parameters
% PGSQL_CB_GET_ALL_GLOBAL_PARAMETERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all global parameters
% PGSQL_CB_GET_ALL_OPTIONS4 retrieving all options
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all options
% PGSQL_CB_GET_ALL_OPTIONS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all options
% PGSQL_CB_GET_ALL_OPTIONS6 retrieving all options
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all options
% PGSQL_CB_GET_ALL_OPTIONS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all options
% PGSQL_CB_GET_ALL_OPTION_DEFS4 retrieving all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all option definitions
% PGSQL_CB_GET_ALL_OPTION_DEFS4_RESULT retrieving: %1 elements
+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 retrieving all option definitions
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all option definitions
% PGSQL_CB_GET_ALL_OPTION_DEFS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all option definitions
% PGSQL_CB_GET_ALL_SERVERS4 retrieving all servers
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all DHCPv4
servers
% PGSQL_CB_GET_ALL_SERVERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all DHCPv4
servers
% PGSQL_CB_GET_ALL_SERVERS6 retrieving all DHCPv6 servers
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all DHCPv6
servers
% PGSQL_CB_GET_ALL_SERVERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all DHCPv6
servers
% PGSQL_CB_GET_ALL_SHARED_NETWORKS4 retrieving all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all shared networks
% PGSQL_CB_GET_ALL_SHARED_NETWORKS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all shared networks
% PGSQL_CB_GET_ALL_SHARED_NETWORKS6 retrieving all shared networks
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all shared networks
% PGSQL_CB_GET_ALL_SHARED_NETWORKS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all shared networks
% PGSQL_CB_GET_ALL_SUBNETS4 retrieving all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all subnets
% PGSQL_CB_GET_ALL_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all subnets
% PGSQL_CB_GET_ALL_SUBNETS6 retrieving all subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve all subnets
% PGSQL_CB_GET_ALL_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve all subnets
% PGSQL_CB_GET_CLIENT_CLASS4 retrieving client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a client class
% PGSQL_CB_GET_CLIENT_CLASS6 retrieving client class: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a client class
% PGSQL_CB_GET_GLOBAL_PARAMETER4 retrieving global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve global parameter
% PGSQL_CB_GET_GLOBAL_PARAMETER6 retrieving global parameter: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve global parameter
% PGSQL_CB_GET_HOST4 get host
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve host
% PGSQL_CB_GET_HOST6 get host
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve host
% PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4 retrieving modified client classes from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified client classes from specified time
% PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified client classes from specified time
% PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6 retrieving modified client classes from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified client classes from specified time
% PGSQL_CB_GET_MODIFIED_CLIENT_CLASSES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified client classes from specified time
% PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4 retrieving modified global parameters from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified global parameters from specified time
% PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified global parameters from specified time
% PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6 retrieving modified global parameters from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified global parameters from specified time
% PGSQL_CB_GET_MODIFIED_GLOBAL_PARAMETERS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified global parameters from specified time
% PGSQL_CB_GET_MODIFIED_OPTIONS4 retrieving modified options from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified options from specified time
% PGSQL_CB_GET_MODIFIED_OPTIONS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified options from specified time
% PGSQL_CB_GET_MODIFIED_OPTIONS6 retrieving modified options from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified options from specified time
% PGSQL_CB_GET_MODIFIED_OPTIONS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified options from specified time
% PGSQL_CB_GET_MODIFIED_OPTION_DEFS4 retrieving modified option definitions from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified option definitions from specified time
% PGSQL_CB_GET_MODIFIED_OPTION_DEFS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified option definitions from specified time
% PGSQL_CB_GET_MODIFIED_OPTION_DEFS6 retrieving modified option definitions from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified option definitions from specified time
% PGSQL_CB_GET_MODIFIED_OPTION_DEFS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified option definitions from specified time
% PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4 retrieving modified shared networks from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified shared networks from specified time
% PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified shared networks from specified time
% PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6 retrieving modified shared networks from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified shared networks from specified time
% PGSQL_CB_GET_MODIFIED_SHARED_NETWORKS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified shared networks from specified time
% PGSQL_CB_GET_MODIFIED_SUBNETS4 retrieving modified subnets from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified subnets from specified time
% PGSQL_CB_GET_MODIFIED_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified subnets from specified time
% PGSQL_CB_GET_MODIFIED_SUBNETS6 retrieving modified subnets from: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve modified subnets from specified time
% PGSQL_CB_GET_MODIFIED_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve modified subnets from specified time
% PGSQL_CB_GET_OPTION4 retrieving option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option
% PGSQL_CB_GET_OPTION6 retrieving option code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option
% PGSQL_CB_GET_OPTION_DEF4 retrieving option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option definition
% PGSQL_CB_GET_OPTION_DEF6 retrieving option definition code: %1 space: %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve option definition
% PGSQL_CB_GET_PORT4 get port
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve port
% PGSQL_CB_GET_PORT6 get port
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve port
% PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4 retrieving audit entries from: %1 %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve audit entries from specified time and id.
% PGSQL_CB_GET_RECENT_AUDIT_ENTRIES4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve audit entries from specified time
% PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6 retrieving audit entries from: %1 %2
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve audit entries from specified time and id
% PGSQL_CB_GET_RECENT_AUDIT_ENTRIES6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve audit entries from specified time
% PGSQL_CB_GET_SERVER4 retrieving DHCPv4 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a DHCPv4 server information.
% PGSQL_CB_GET_SERVER6 retrieving DHCPv6 server: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve a DHCPv6 server information.
% PGSQL_CB_GET_SHARED_NETWORK4 retrieving shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network
% PGSQL_CB_GET_SHARED_NETWORK6 retrieving shared network: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network
% PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4 retrieving shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network subnets
% PGSQL_CB_GET_SHARED_NETWORK_SUBNETS4_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve shared network subnets
% PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6 retrieving shared network: %1 subnets
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve shared network subnets
% PGSQL_CB_GET_SHARED_NETWORK_SUBNETS6_RESULT retrieving: %1 elements
+Logged at debug log level 40.
Debug message indicating the result of an action to retrieve shared network subnets
% PGSQL_CB_GET_SUBNET4_BY_PREFIX retrieving subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by prefix
% PGSQL_CB_GET_SUBNET4_BY_SUBNET_ID retrieving subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by subnet id
% PGSQL_CB_GET_SUBNET6_BY_PREFIX retrieving subnet by prefix: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by prefix
% PGSQL_CB_GET_SUBNET6_BY_SUBNET_ID retrieving subnet by subnet id: %1
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve subnet by subnet id
% PGSQL_CB_GET_TYPE4 get type
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve type
% PGSQL_CB_GET_TYPE6 get type
+Logged at debug log level 40.
Debug message issued when triggered an action to retrieve type
% PGSQL_CB_INIT_OK loading Postgres CB hooks library successful
is typically a network or database server issue.
% PGSQL_CB_REGISTER_BACKEND_TYPE4 register backend
+Logged at debug log level 40.
Debug message issued when triggered an action to register backend
% PGSQL_CB_REGISTER_BACKEND_TYPE6 register backend
+Logged at debug log level 40.
Debug message issued when triggered an action to register backend
% PGSQL_CB_TLS_SUPPORT Attempt to configure TLS: %1
The parameters of the connection are logged.
% PGSQL_CB_UNREGISTER_BACKEND_TYPE4 unregister backend
+Logged at debug log level 40.
Debug message issued when triggered an action to unregister backend
% PGSQL_CB_UNREGISTER_BACKEND_TYPE6 unregister backend
+Logged at debug log level 40.
Debug message issued when triggered an action to unregister backend
-# Copyright (C) 2018-2021 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2018-2024 Internet Systems Consortium, Inc. ("ISC")
% STAT_CMDS_DEINIT_FAILED unloading Stat Commands hooks library failed: %1
This error message indicates an error during unloading the Lease Commands
be logged.
% STAT_CMDS_LEASE4_ORPHANED_STATS stat-lease4-get command omitted statistics for one or more non-existent subnets
+Logged at debug log level 40.
During processing the stat-lease4-get found statistics for subnet IDs for
non-existent subnets. These values were omitted from the command response
returned to the user. This may occur when subnets have been removed from
be logged.
% STAT_CMDS_LEASE6_ORPHANED_STATS stat-lease6-get command omitted statistics for one or more non-existent subnets
+Logged at debug log level 40.
During processing the stat-lease4-get found statistics for subnet IDs for
non-existent subnets. These values were omitted from the command response
returned to the user. This may occur when subnets have been removed from
The file descriptor number is noted.
% ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed
+Logged at debug log level 70.
A debug message, this records that the upstream fetch (a query made by the
resolver on behalf of its client) to the specified address has completed.
% ASIODNS_FETCH_STOPPED upstream fetch to %1(%2) has been stopped
+Logged at debug log level 40.
An external component has requested the halting of an upstream fetch. This
is an allowed operation, and the message should only appear if debug is
enabled.
error that caused the problem is given in the message.
% ASIODNS_READ_TIMEOUT receive timeout while waiting for data from %1(%2)
+Logged at debug log level 50.
An upstream fetch from the specified address timed out. This may happen for
any number of reasons and is most probably a problem at the remote server
or a problem on the network. The message will only appear if debug is
-# Copyright (C) 2011-2023 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2011-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
reason for failure.
% COMMAND_DEREGISTERED Command %1 deregistered
+Logged at debug log level 10.
This debug message indicates that the daemon stopped supporting specified
command. This command can no longer be issued. If the command socket is
open and this command is issued, the daemon will not be able to process it.
% COMMAND_EXTENDED_REGISTERED Command %1 registered
+Logged at debug log level 10.
This debug message indicates that the daemon started supporting specified
command. The handler for the registered command includes a parameter holding
entire command to be processed.
% COMMAND_HTTP_LISTENER_COMMAND_REJECTED Command HTTP listener rejected command '%1' from '%2'
+Logged at debug log level 10.
This debug messages is issued when a command is rejected. Arguments detail
the command and the address the request was received from.
% COMMAND_HTTP_LISTENER_STARTED Command HTTP listener started with %1 threads, listening on %2:%3, use TLS: %4
+Logged at debug log level 10.
This debug messages is issued when an HTTP listener has been started to
accept connections from Command API clients through which commands can be
received and responses sent. Arguments detail the number of threads
and if HTTPS/TLS is used or not.
% COMMAND_HTTP_LISTENER_STOPPED Command HTTP listener for %1:%2 stopped.
+Logged at debug log level 10.
This debug messages is issued when the Command HTTP listener, listening
at the given address and port, has completed shutdown.
% COMMAND_HTTP_LISTENER_STOPPING Stopping Command HTTP listener for %1:%2
+Logged at debug log level 10.
This debug messages is issued when the Command HTTP listener, listening
at the given address and port, has begun to shutdown.
with separate messages.
% COMMAND_REGISTERED Command %1 registered
+Logged at debug log level 10.
This debug message indicates that the daemon started supporting specified
command. If the command socket is open, this command can now be issued.
includes details about the reason for failure.
% COMMAND_SOCKET_CONNECTION_CLOSED Closed socket %1 for existing command connection
+Logged at debug log level 10.
This is a debug message indicating that the socket created for handling
client's connection is closed. This usually means that the client disconnected,
but may also mean a timeout.
detailed error is provided as an argument.
% COMMAND_SOCKET_CONNECTION_OPENED Opened socket %1 for incoming command connection
+Logged at debug log level 10.
This is a debug message indicating that a new incoming command connection was
detected and a dedicated socket was opened for that connection.
sent by the server indicates a timeout and is then closed.
% COMMAND_SOCKET_READ Received %1 bytes over command socket %2
+Logged at debug log level 10.
This debug message indicates that specified number of bytes was received
over command socket identified by specified file descriptor.
reading from command socket.
% COMMAND_SOCKET_WRITE Sent response of %1 bytes (%2 bytes left to send) over command socket %3
+Logged at debug log level 10.
This debug message indicates that the specified number of bytes was sent
over command socket identifier by the specified file descriptor.
-# Copyright (C) 2013-2023 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2013-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
the DHCP_DDNS process name, the second contains the PID and PID file.
% DHCP_DDNS_AT_MAX_TRANSACTIONS application has %1 queued requests but has reached maximum number of %2 concurrent transactions
+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.
% DHCP_DDNS_CLEARED_FOR_SHUTDOWN application has met shutdown criteria for shutdown type: %1
+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.
has been invoked.
% DHCP_DDNS_CONFIGURE configuration %1 received: %2
+Logged at debug log level 40.
This is a debug message issued when the DHCP-DDNS application configure method
has been invoked.
server or others as appropriate.
% DHCP_DDNS_FWD_REQUEST_IGNORED Request ID %1: Forward updates are disabled, the forward portion of request will be ignored: %2
+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.
% DHCP_DDNS_INVALID_RESPONSE received response to DNS Update message is malformed: %1
+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.
version of Kea will implement authentication to guard against such attacks.
% DHCP_DDNS_NO_ELIGIBLE_JOBS although there are queued requests, there are pending transactions for each, Queue count: %1 Transaction count: %2
+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.
load issues.
% DHCP_DDNS_QUEUE_MGR_QUEUE_RECEIVE Request ID %1: received and queued a request.
+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.
% DHCP_DDNS_QUEUE_MGR_RECONFIGURING application is reconfiguring the queue manager
+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.
% DHCP_DDNS_QUEUE_MGR_RECOVERING application is attempting to recover from a queue manager IO error
resume accepting requests.
% DHCP_DDNS_QUEUE_MGR_STARTED application's queue manager has begun listening for requests.
+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.
restart the queue manager if given a new configuration.
% DHCP_DDNS_QUEUE_MGR_STOPPED application's queue manager has stopped listening for requests.
+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.
% DHCP_DDNS_QUEUE_MGR_STOPPING application is stopping the queue manager for %1
+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.
mapping removals which were received and accepted by an appropriate DNS server.
% DHCP_DDNS_REQUEST_DROPPED Request ID %1: Request contains no enabled update requests and will be dropped: %2
+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
server or others as appropriate.
% DHCP_DDNS_REV_REQUEST_IGNORED Request ID %1: Reverse updates are disabled, the reverse portion of request will be ignored: %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.
% DHCP_DDNS_RUN_EXIT application is exiting the event loop
+Logged at debug log level 0.
This is a debug message issued when the DHCP-DDNS server exits its
event lo
% DHCP_DDNS_SHUTDOWN_COMMAND application received shutdown command with args: %1
+Logged at debug log level 0.
This is a debug message issued when the application has been instructed
to shut down by the controller.
The version is also printed.
% DHCP_DDNS_STARTING_TRANSACTION Request ID %1:
+Logged at debug log level 50.
This is a debug message issued when DHCP-DDNS has begun a transaction for
a given request.
of the DNS updates requested as part of this request did not succeed.
% DHCP_DDNS_UPDATE_REQUEST_SENT 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.
% DHCP_DDNS_UPDATE_RESPONSE_RECEIVED Request ID %1: to server: %2 status: %3
+Logged at debug log level 50.
This is a debug message issued when DHCP_DDNS receives sends a DNS update
response from a DNS server.
-# Copyright (C) 2013-2020 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2013-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
correctly.
% DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests
+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.
$NAMESPACE isc::dhcp
% ALLOC_ENGINE_IGNORING_UNSUITABLE_GLOBAL_ADDRESS %1: ignoring globally reserved address %2, it falls outside %3
+Logged at debug log level 40.
This debug message is issued when the allocation engine determines that
the globally reserved address falls outside the selected subnet or
shared-network. The server should ignore the reserved address and
attempt a dynamic allocation.
% ALLOC_ENGINE_IGNORING_UNSUITABLE_GLOBAL_ADDRESS6 %1: ignoring globally reserved address %2, it falls outside %3
+Logged at debug log level 40.
This debug message is issued when the allocation engine determines that
the globally reserved address falls outside the selected subnet or
shared-network. The server should ignore the reserved address and
attempt a dynamic allocation.
% ALLOC_ENGINE_LEASE_RECLAIMED successfully reclaimed lease %1
+Logged at debug log level 40.
This debug message is logged when the allocation engine successfully
reclaims a lease. The lease is now available for assignment.
The first argument includes the client identification information.
% ALLOC_ENGINE_V4_DISCOVER_HR client %1 sending DHCPDISCOVER has reservation for the address %2
+Logged at debug log level 40.
This message is issued when the allocation engine determines that the
client sending the DHCPDISCOVER has a reservation for the specified
address. The allocation engine will try to offer this address to
the client.
% ALLOC_ENGINE_V4_LEASES_RECLAMATION_COMPLETE reclaimed %1 leases in %2
+Logged at debug log level 40.
This debug message is logged when the allocation engine completes
reclamation of a set of expired leases. The maximum number of leases
to be reclaimed in a single pass of the lease reclamation routine
DHCP packets, while it processes the expired leases.
% ALLOC_ENGINE_V4_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = %1 leases or %2 milliseconds)
+Logged at debug log level 40.
This debug message is issued when the allocation engine starts the
reclamation of the expired leases. The maximum number of leases to
be reclaimed and the timeout is included in the message. If any of
these values is 0, it means "unlimited".
% ALLOC_ENGINE_V4_LEASES_RECLAMATION_TIMEOUT timeout of %1 ms reached while reclaiming IPv4 leases
+Logged at debug log level 40.
This debug message is issued when the allocation engine hits the
timeout for performing reclamation of the expired leases. The
reclamation will now be interrupted and all leases which haven't
value expressed in milliseconds.
% ALLOC_ENGINE_V4_LEASE_RECLAIM %1: reclaiming expired lease for address %2
+Logged at debug log level 40.
This debug message is issued when the server begins reclamation of the
expired DHCPv4 lease. The first argument specifies the client identification
information. The second argument holds the leased IPv4 address.
while performing the operation on the lease database.
% ALLOC_ENGINE_V4_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
+Logged at debug log level 40.
This debug message is issued when the server reclaims all expired
DHCPv4 leases in the database.
% ALLOC_ENGINE_V4_OFFER_EXISTING_LEASE allocation engine will try to offer existing lease to the client %1
+Logged at debug log level 40.
This message is issued when the allocation engine determines that
the client has a lease in the lease database, it doesn't have
reservation for any other lease, and the leased address is not
to offer the same lease to the client.
% ALLOC_ENGINE_V4_OFFER_NEW_LEASE allocation engine will try to offer new lease to the client %1
+Logged at debug log level 40.
This message is issued when the allocation engine will try to
offer a new lease to the client. This is the case when the
client doesn't have any existing lease, it has no reservation
the hint is in use.
% ALLOC_ENGINE_V4_OFFER_REQUESTED_LEASE allocation engine will try to offer requested lease %1 to the client %2
+Logged at debug log level 40.
This message is issued when the allocation engine will try to
offer the lease specified in the hint. This situation may occur
when: (a) client doesn't have any reservations, (b) client has
reservation but the reserved address is leased to another client.
% ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases expired more than %1 seconds ago
+Logged at debug log level 40.
This debug message is issued when the allocation engine begins
deletion of the reclaimed leases which have expired more than
a specified number of seconds ago. This operation is triggered
removed.
% ALLOC_ENGINE_V4_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted %1 expired-reclaimed leases
+Logged at debug log level 40.
This debug message is issued when the server successfully deletes
"expired-reclaimed" leases from the lease database. The number of
deleted leases is included in the log message.
the log message.
% ALLOC_ENGINE_V4_REQUEST_ADDRESS_RESERVED %1: requested address %2 is reserved
+Logged at debug log level 40.
This message is issued when the allocation engine refused to
allocate address requested by the client because this
address is reserved for another client. The first argument
includes the client identification information.
% ALLOC_ENGINE_V4_REQUEST_ALLOC_REQUESTED %1: trying to allocate requested address %2
+Logged at debug log level 40.
This message is issued when the allocation engine is trying
to allocate (or reuse an expired) address which has been
requested by the client. The first argument includes the
client identification information.
% ALLOC_ENGINE_V4_REQUEST_EXTEND_LEASE %1: extending lifetime of the lease for address %2
+Logged at debug log level 40.
This message is issued when the allocation engine determines
that the client already has a lease whose lifetime can be
extended, and which can be returned to the client.
The first argument includes the client identification information.
% ALLOC_ENGINE_V4_REQUEST_INVALID client %1 having a reservation for address %2 is requesting invalid address %3
+Logged at debug log level 40.
This message is logged when the client, having a reservation for
one address, is requesting a different address. The client is
only allowed to do this when the reserved address is in use by
client should request the reserved address.
% ALLOC_ENGINE_V4_REQUEST_IN_USE %1: requested address %2 is in use
+Logged at debug log level 40.
This message is issued when the client is requesting or has a
reservation for an address which is in use. The first argument
includes the client identification information.
% ALLOC_ENGINE_V4_REQUEST_OUT_OF_POOL client %1, which doesn't have a reservation, requested address %2 out of the dynamic pool
+Logged at debug log level 40.
This message is issued when the client has requested allocation
of the address which doesn't belong to any address pool from
which addresses are dynamically allocated. The client also
could only be allocated if the client had reservation for it.
% ALLOC_ENGINE_V4_REQUEST_PICK_ADDRESS client %1 hasn't specified an address - picking available address from the pool
+Logged at debug log level 40.
This message is logged when the client hasn't specified any
preferred address (the client should always do it, but Kea
tries to be forgiving). The allocation engine will try to pick an available
address from the dynamic pool and allocate it to the client.
% ALLOC_ENGINE_V4_REQUEST_REMOVE_LEASE %1: removing previous client's lease %2
+Logged at debug log level 40.
This message is logged when the allocation engine removes previous
lease for the client because the client has been allocated new one.
% ALLOC_ENGINE_V4_REQUEST_USE_HR client %1 hasn't requested specific address, using reserved address %2
+Logged at debug log level 40.
This message is issued when the client is not requesting any specific
address but the allocation engine has determined that there is a
reservation for this client. The allocation engine will try to
allocate the reserved address.
% ALLOC_ENGINE_V4_REUSE_EXPIRED_LEASE_DATA %1: reusing expired lease, updated lease information: %2
+Logged at debug log level 55.
This message is logged when the allocation engine is reusing
an existing lease. The details of the updated lease are
printed. The first argument includes the client identification
information to distinguish between these different cases.
% ALLOC_ENGINE_V6_ALLOC_HR_LEASE_EXISTS %1: lease type %2 for reserved address/prefix %3 already exists
+Logged at debug log level 40.
This debug message is issued when the allocation engine determines that
the lease for the IPv6 address or prefix has already been allocated
for the client and the client can continue using it. The first argument
includes the client identification information.
% ALLOC_ENGINE_V6_ALLOC_LEASES_HR leases and static reservations found for client %1
+Logged at debug log level 40.
This message is logged when the allocation engine is in the process of
allocating leases for the client, it found existing leases and static
reservations for the client. The allocation engine will verify if
and returned.
% ALLOC_ENGINE_V6_ALLOC_LEASES_NO_HR no reservations found but leases exist for client %1
+Logged at debug log level 40.
This message is logged when the allocation engine is in the process if
allocating leases for the client, there are no static reservations,
but lease(s) exist for the client. The allocation engine will remove
remaining leases to the client.
% ALLOC_ENGINE_V6_ALLOC_NO_LEASES_HR no leases found but reservations exist for client %1
+Logged at debug log level 40.
This message is logged when the allocation engine is in the process of
allocating leases for the client. It hasn't found any existing leases
for this client, but the client appears to have static reservations.
the client.
% ALLOC_ENGINE_V6_ALLOC_NO_V6_HR %1: unable to allocate reserved leases - no IPv6 reservations
+Logged at debug log level 40.
This message is logged when the allocation engine determines that the
client has no IPv6 reservations and thus the allocation engine will have
to try to allocate allocating leases from the dynamic pool or stop
includes the client identification information.
% ALLOC_ENGINE_V6_ALLOC_UNRESERVED no static reservations available - trying to dynamically allocate leases for client %1
+Logged at debug log level 40.
This debug message is issued when the allocation engine will attempt
to allocate leases from the dynamic pools. This may be due to one of
(a) there are no reservations for this client, (b) there are
has now been allocated to another client.
% ALLOC_ENGINE_V6_CALCULATED_PREFERRED_LIFETIME %1: using a calculated preferred-lifetime of %2
+Logged at debug log level 40.
This debug message indicates that the preferred-lifetime being returned
to the client is defaulting to 62.5% of the valid-lifetime. This may
occur if either the preferred-lifetime has not been explicitly configured,
process.
% ALLOC_ENGINE_V6_EXPIRED_HINT_RESERVED %1: expired lease for the client's hint %2 is reserved for another client
+Logged at debug log level 40.
This message is logged when the allocation engine finds that the
expired lease for the client's hint can't be reused because it
is reserved for another client. The first argument includes the
client identification information.
% ALLOC_ENGINE_V6_EXTEND_ALLOC_UNRESERVED allocate new (unreserved) leases for the renewing client %1
+Logged at debug log level 40.
This debug message is issued when the allocation engine is trying to
allocate new leases for the renewing client because it was unable to
renew any of the existing client's leases, e.g. because leases are
information.
% ALLOC_ENGINE_V6_EXTEND_LEASE %1: extending lifetime of the lease type %2, address %3
+Logged at debug log level 50.
This debug message is issued when the allocation engine is trying
to extend lifetime of the lease. The first argument includes the
client identification information.
% ALLOC_ENGINE_V6_EXTEND_LEASE_DATA %1: detailed information about the lease being extended: %2
+Logged at debug log level 55.
This debug message prints detailed information about the lease which
lifetime is being extended (renew or rebind). The first argument
includes the client identification information.
% ALLOC_ENGINE_V6_EXTEND_NEW_LEASE_DATA %1: new lease information for the lease being extended: %2
+Logged at debug log level 55.
This debug message prints updated information about the lease to be
extended. If the lease update is successful, the information printed
by this message will be stored in the database. The first argument
includes the client identification information.
% ALLOC_ENGINE_V6_HINT_RESERVED %1: lease for the client's hint %2 is reserved for another client
+Logged at debug log level 40.
This message is logged when the allocation engine cannot allocate
the lease using the client's hint because the lease for this hint
is reserved for another client. The first argument includes the
reserved for it.
% ALLOC_ENGINE_V6_LEASES_RECLAMATION_COMPLETE reclaimed %1 leases in %2
+Logged at debug log level 40.
This debug message is logged when the allocation engine completes
reclamation of a set of expired leases. The maximum number of leases
to be reclaimed in a single pass of the lease reclamation routine
DHCP packets, while it processes the expired leases.
% ALLOC_ENGINE_V6_LEASES_RECLAMATION_START starting reclamation of expired leases (limit = %1 leases or %2 milliseconds)
+Logged at debug log level 40.
This debug message is issued when the allocation engine starts the
reclamation of the expired leases. The maximum number of leases to
be reclaimed and the timeout is included in the message. If any of
these values is 0, it means "unlimited".
% ALLOC_ENGINE_V6_LEASES_RECLAMATION_TIMEOUT timeout of %1 ms reached while reclaiming IPv6 leases
+Logged at debug log level 40.
This debug message is issued when the allocation engine hits the
timeout for performing reclamation of the expired leases. The
reclamation will now be interrupted and all leases which haven't
value expressed in milliseconds.
% ALLOC_ENGINE_V6_LEASE_RECLAIM %1: reclaiming expired lease for prefix %2/%3
+Logged at debug log level 40.
This debug message is issued when the server begins reclamation of the
expired DHCPv6 lease. The reclaimed lease may either be an address lease
or delegated prefix. The first argument provides the client identification
while performing the operation on the lease database.
% ALLOC_ENGINE_V6_NO_MORE_EXPIRED_LEASES all expired leases have been reclaimed
+Logged at debug log level 40.
This debug message is issued when the server reclaims all expired
DHCPv6 leases in the database.
% ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE begin deletion of reclaimed leases expired more than %1 seconds ago
+Logged at debug log level 40.
This debug message is issued when the allocation engine begins
deletion of the reclaimed leases which have expired more than
a specified number of seconds ago. This operation is triggered
removed.
% ALLOC_ENGINE_V6_RECLAIMED_LEASES_DELETE_COMPLETE successfully deleted %1 expired-reclaimed leases
+Logged at debug log level 40.
This debug message is issued when the server successfully deletes
"expired-reclaimed" leases from the lease database. The number of
deleted leases is included in the log message.
the log message.
% ALLOC_ENGINE_V6_RENEW_HR allocating leases reserved for the client %1 as a result of Renew
+Logged at debug log level 40.
This debug message is issued when the allocation engine tries to
allocate reserved leases for the client sending a Renew message.
The server will also remove any leases that the client is trying
to renew that are not reserved for the client.
% ALLOC_ENGINE_V6_RENEW_REMOVE_RESERVED %1: checking if existing client's leases are reserved for another client
+Logged at debug log level 40.
This message is logged when the allocation engine finds leases for
the client and will check if these leases are reserved for another
client. If they are, they will not be renewed for the client
another client.
% ALLOC_ENGINE_V6_REUSE_EXPIRED_LEASE_DATA %1: reusing expired lease, updated lease information: %2
+Logged at debug log level 55.
This message is logged when the allocation engine is reusing
an existing lease. The details of the updated lease are
printed. The first argument includes the client identification
interfaces on which the server listens to DHCP messages.
% DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet %1
+Logged at debug log level 40.
A debug message reported when the DHCP configuration manager is adding the
specified IPv4 subnet to its database.
% DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet %1
+Logged at debug log level 40.
A debug message reported when the DHCP configuration manager is adding the
specified IPv6 subnet to its database.
% DHCPSRV_CFGMGR_ALL_IFACES_ACTIVE enabling listening on all interfaces
+Logged at debug log level 40.
A debug message issued when the server is being configured to listen on all
interfaces.
% DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to: %1
+Logged at debug log level 40.
A debug message issued when the server's DHCP-DDNS settings are changed.
% DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces
the supported parameters.
% DHCPSRV_CFGMGR_DEL_SUBNET4 IPv4 subnet %1 removed
+Logged at debug log level 40.
This debug message is issued when a subnet is successfully removed from the
server configuration. The argument identifies the removed subnet.
% DHCPSRV_CFGMGR_DEL_SUBNET6 IPv6 subnet %1 removed
+Logged at debug log level 40.
This debug message is issued when a subnet is successfully removed from the
server configuration. The argument identifies the removed subnet.
OS, it will use an UDP socket instead.
% DHCPSRV_CFGMGR_SUBNET4 retrieved subnet %1 for address hint %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv4 subnet when given the address hint specified
as the address is within the subnet.
% DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet %1 for packet received by matching address %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager
has returned the specified IPv4 subnet for a received packet. This particular
subnet was selected, because an IPv4 address was matched which belonged to that
subnet.
% DHCPSRV_CFGMGR_SUBNET4_IFACE selected subnet %1 for packet received over interface %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager
has returned the specified IPv4 subnet for a packet received over
the given interface. This particular subnet was selected, because it
'interface' parameter in the subnet4 definition).
% DHCPSRV_CFGMGR_SUBNET4_RELAY selected subnet %1, because of matching relay addr %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv4 subnet, because detected relay agent address
matches value specified for this subnet.
% DHCPSRV_CFGMGR_SUBNET6 retrieved subnet %1 for address hint %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv6 subnet when given the address hint specified
as the address is within the subnet.
% DHCPSRV_CFGMGR_SUBNET6_IFACE selected subnet %1 for packet received over interface %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager
has returned the specified IPv6 subnet for a packet received over
given interface. This particular subnet was selected, because it
'interface' parameter in the subnet6 definition).
% DHCPSRV_CFGMGR_SUBNET6_IFACE_ID selected subnet %1 (interface-id match) for incoming packet
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager
has returned the specified IPv6 subnet for a received packet. This particular
subnet was selected, because value of interface-id option matched what was
(see 'interface-id' parameter in the subnet6 definition).
% DHCPSRV_CFGMGR_SUBNET6_RELAY selected subnet %1, because of matching relay addr %2
+Logged at debug log level 40.
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv6 subnet, because detected relay agent address
matches value specified for this subnet.
uncommon use.
% DHCPSRV_CFGMGR_UPDATE_SUBNET4 updating subnet %1 (result %2)
+Logged at debug log level 40.
A debug message reported when the DHCP configuration manager is updating the
specified IPv4 subnet in its current configuration. Subnet ID and result
(expected to be true) are displayed.
% DHCPSRV_CFGMGR_UPDATE_SUBNET6 updating subnet %1 (result %2)
+Logged at debug log level 40.
A debug message reported when the DHCP configuration manager is replacing the
specified IPv6 subnet in its current configuration. Subnet ID and result
(expected to be true) are displayed.
address on the specific interface.
% DHCPSRV_CLOSE_DB closing currently open %1 database
+Logged at debug log level 40.
This is a debug message, issued when the DHCP server closes the currently
open lease database. It is issued at program shutdown and whenever
the database access parameters are changed: in the latter case, the
the new parameters.
% DHCPSRV_DDNS_TTL_PERCENT_TOO_SMALL ddns-ttl-percent %1 of lease lifetime %2 is too small, ignoring it
+Logged at debug log level 55.
A debug message issued when the DDNS TTL value calculated using the
ddns-ttl-percent is zero. Kea will ignore the value and calculate
the DDNS TTL as though ddsn-ttl-percent were not specified. The
requests are being generated faster than they can be delivered.
% DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: %1
+Logged at debug log level 50.
A debug message issued when a NameChangeRequest has been successfully sent to
kea-dhcp-ddns.
be made without intervention.
% DHCPSRV_HOOK_LEASE4_RECOVER_SKIP DHCPv4 lease %1 was not recovered from the declined state because a callout set the skip status.
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease4_recover
hook point set the next step status to SKIP. For this particular hook point, this
indicates that the server should not recover the lease from declined state.
takes place.
% DHCPSRV_HOOK_LEASE4_RENEW_SKIP DHCPv4 lease was not renewed because a callout set the skip flag.
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease4_renew
hook point set the skip flag. For this particular hook point, the setting
of the flag by a callout instructs the server to not renew a lease. The
server will use existing lease as it is, without extending its lifetime.
% DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease4_select
hook point sets the skip flag. It means that the server was told that
no lease4 should be assigned. The server will not put that lease in its
database and the client will get a NAK packet.
% DHCPSRV_HOOK_LEASE6_EXTEND_SKIP DHCPv6 lease lifetime was not extended because a callout set the skip flag for message %1
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease6_renew
or the lease6_rebind hook point set the skip flag. For this particular hook
point, the setting of the flag by a callout instructs the server to not
of the one in question and will proceed with other renewals as usual.
% DHCPSRV_HOOK_LEASE6_RECOVER_SKIP DHCPv6 lease %1 was not recovered from declined state because a callout set the skip status.
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease6_recover
hook point set the next step status to SKIP. For this particular hook point, this
indicates that the server should not recover the lease from declined state.
takes place.
% DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.
+Logged at debug log level 40.
This debug message is printed when a callout installed on lease6_select
hook point sets the skip flag. It means that the server was told that
no lease6 should be assigned. The server will not put that lease in its
the extended info deleted from the lease user context.
% DHCPSRV_LEASE4_EXTENDED_INFO_UPGRADED extended info for lease %1 was upgraded
+Logged at debug log level 40.
This debug message is printed when a lease extended info was upgraded.
% DHCPSRV_LEASE6_EXTENDED_INFO_SANITY_FAIL extended info for lease %1 failed checks (%2)
the extended info deleted from the lease user context.
% DHCPSRV_LEASE6_EXTENDED_INFO_UPGRADED extended info for lease %1 was upgraded
+Logged at debug log level 40.
This debug message is printed when a lease extended info was upgraded.
% DHCPSRV_LEASE_MGR_CALLBACK_EXCEPTION exception occurred in a lease manager callback for callback type %1, subnet id %2, and lease %3: %4
so Kea updated subnet-id and loaded the lease successfully.
% DHCPSRV_MEMFILE_ADD_ADDR4 adding IPv4 lease with address %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 memory file backend database.
% DHCPSRV_MEMFILE_ADD_ADDR6 adding IPv6 lease with address %1
+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 memory file backend database.
% DHCPSRV_MEMFILE_BEGIN_BUILD_EXTENDED_INFO_TABLES6 building extended info tables with %1 sanity check level, tables %2
+Logged at debug log level 40.
A debug message issued when the server is building extended info tables.
The extended info sanity check level and the fact tables are enabled
or disabled are displayed.
% DHCPSRV_MEMFILE_BEGIN_EXTRACT_EXTENDED_INFO4 extract extended info with %1 sanity check level%2
+Logged at debug log level 40.
A debug message issued when the server is extracting extended info.
The extended info sanity check level and update in file when requested
are displayed.
receives an exception processing a lease.
% DHCPSRV_MEMFILE_COMMIT committing to memory file database
+Logged at debug log level 50.
The code has issued a commit call. For the memory file database this is
a no-op.
(but not the password if any) are logged.
% DHCPSRV_MEMFILE_DELETE_ADDR 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_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
+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.
% DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
+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.
% DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED_START starting deletion of %1 expired-reclaimed leases
+Logged at debug log level 50.
A debug message issued when the server has found expired-reclaimed
leases to be removed. The number of leases to be removed is logged
in the message.
% DHCPSRV_MEMFILE_EXTRACT_EXTENDED_INFO4 extracting extended info saw %1 leases, extended info sanity checks modified %2 / updated %3 leases and %4 leases have relay or remote id
+Logged at debug log level 40.
Extended info extraction was finished. Some statistics are displayed, the
updated in database is returned to the command interface.
% DHCPSRV_MEMFILE_EXTRACT_EXTENDED_INFO4_ERROR extracting extended info got an exception on the lease for %1: %2
+Logged at debug log level 40.
A debug message issued when the server is extracting extended info and
receives an exception processing a lease.
% DHCPSRV_MEMFILE_GET4 obtaining all IPv4 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv4
leases from the memory file database.
% DHCPSRV_MEMFILE_GET6 obtaining all IPv6 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv6
leases from the memory file database.
% DHCPSRV_MEMFILE_GET6_DUID obtaining IPv6 leases for DUID %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain IPv6
leases from the memory file database for the DUID.
% DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain an IPv4
lease from the memory file database for the specified address.
% DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain an IPv6
lease from the memory file database for the specified address.
% DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain a set of
IPv4 leases from the memory file database for a client with the specified
client identification.
% DHCPSRV_MEMFILE_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
+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.
% DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
+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.
% DHCPSRV_MEMFILE_GET_HOSTNAME4 obtaining IPv4 leases for hostname %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 memory file database for a client with the specified
hostname.
% DHCPSRV_MEMFILE_GET_HOSTNAME6 obtaining IPv6 leases for hostname %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain a set of
IPv6 leases from the memory file database for a client with the specified
hostname.
% DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %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 memory file database for a client with the specified
hardware address.
% DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %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 memory file database for a client with the specified IAID
(Identity Association ID) and DUID (DHCP Unique Identifier).
% DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain an IPv6
lease from the memory file database for a client with the specified IAID
(Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
% DHCPSRV_MEMFILE_GET_PAGE4 obtaining at most %1 IPv4 leases starting from address %2
+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.
% DHCPSRV_MEMFILE_GET_PAGE6 obtaining at most %1 IPv6 leases starting from address %2
+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.
% DHCPSRV_MEMFILE_GET_RELAYID4 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 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.
% DHCPSRV_MEMFILE_GET_RELAYID6 obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
+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.
% DHCPSRV_MEMFILE_GET_REMOTEID4 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 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.
% DHCPSRV_MEMFILE_GET_REMOTEID6 obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
+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.
% DHCPSRV_MEMFILE_GET_SUBID4 obtaining IPv4 leases for subnet ID %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 memory file database.
% DHCPSRV_MEMFILE_GET_SUBID6 obtaining IPv6 leases for subnet ID %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 memory file database.
% DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain an IPv4
lease from the memory file database for a client with the specified
subnet ID and client ID.
% DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain an IPv4
lease from the memory file database for a client with the specified
subnet ID and hardware address.
% DHCPSRV_MEMFILE_GET_SUBID_PAGE6 obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain a page of
IPv6 leases from the memory file database beginning with the specified
address for a given subnet identifier.
replaced by those read from the file.
% DHCPSRV_MEMFILE_LEASE_LOAD loading lease %1
+Logged at debug log level 55.
A debug message issued when DHCP lease is being loaded from the file to memory.
% DHCPSRV_MEMFILE_LEASE_LOAD_ROW_ERROR discarding row %1, error: %2
starts the periodic Lease File Cleanup.
% DHCPSRV_MEMFILE_LFC_UNREGISTER_TIMER_FAILED failed to unregister timer 'memfile-lfc': %1
+Logged at debug log level 40.
This debug message is logged when Memfile backend fails to unregister
timer used for lease file cleanup scheduling. There are several reasons
why this could occur, although the most likely cause is that the system
have hardware address associated with it.
% DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database
+Logged at debug log level 50.
The code has issued a rollback call. For the memory file database this is
a no-op.
% DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to update IPv4
lease from the memory file database for the specified address.
% DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1
+Logged at debug log level 50.
A debug message issued when the server is attempting to update IPv6
lease from the memory file database for the specified address.
individually.
% DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %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.
% DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
+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.
The code has issued a begin transaction call.
% DHCPSRV_MYSQL_COMMIT committing to MySQL database
+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.
(but not the password if any) are logged.
% DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted %1 reclaimed leases from the database
+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.
% DHCPSRV_MYSQL_DELETE_ADDR 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 MySQL database for the specified address.
% DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
+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.
% DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
+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
or the MySQL server has gone down.
% DHCPSRV_MYSQL_GET4 obtaining all IPv4 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv4
leases from the MySQL database.
% DHCPSRV_MYSQL_GET6 obtaining all IPv6 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv6
leases from the MySQL database.
% DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %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 the specified address.
% DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2
+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.
% DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %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 MySQL database for a client with the specified
client identification.
% DHCPSRV_MYSQL_GET_DUID obtaining IPv6 lease for duid %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.
% DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
+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.
% DHCPSRV_MYSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
+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.
% DHCPSRV_MYSQL_GET_HOSTNAME4 obtaining IPv4 leases for hostname %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 MySQL database for a client with the specified
hostname.
% DHCPSRV_MYSQL_GET_HOSTNAME6 obtaining IPv6 leases for hostname %1
+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.
% DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %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 MySQL database for a client with the specified
hardware address.
% DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
+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).
% DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
+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).
% DHCPSRV_MYSQL_GET_PAGE4 obtaining at most %1 IPv4 leases starting from address %2
+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.
% DHCPSRV_MYSQL_GET_PAGE6 obtaining at most %1 IPv6 leases starting from address %2
+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.
% DHCPSRV_MYSQL_GET_RELAYID4 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 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.
% DHCPSRV_MYSQL_GET_RELAYID6 obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
+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.
% DHCPSRV_MYSQL_GET_REMOTEID4 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 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.
% DHCPSRV_MYSQL_GET_REMOTEID6 obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
+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.
% DHCPSRV_MYSQL_GET_SUBID4 obtaining IPv4 leases for subnet ID %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 MySQL database.
% DHCPSRV_MYSQL_GET_SUBID6 obtaining IPv6 leases for subnet ID %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.
% DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %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.
% DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %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 hardware address.
% DHCPSRV_MYSQL_GET_SUBID_PAGE6 obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
+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.
% DHCPSRV_MYSQL_GET_VERSION obtaining schema version information
+Logged at debug log level 50.
A debug message issued when the server is about to obtain schema version
information from the MySQL database.
% DHCPSRV_MYSQL_HOST_DB opening MySQL hosts database: %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.
% DHCPSRV_MYSQL_HOST_DB_GET_VERSION obtaining schema version information for the MySQL hosts database
+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.
TLS is not used.
% DHCPSRV_MYSQL_ROLLBACK rolling back MySQL 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.
any of these INSERT statements fail.
% DHCPSRV_MYSQL_TLS_CIPHER TLS cipher: %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.
% DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
+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.
% DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
+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.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4 upgrading IPv4 leases done in %1 pages with %2 updated leases
+Logged at debug log level 40.
The server upgraded extended info. The number of pages and the final count of
updated leases are displayed.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4_ERROR upgrading extending info for IPv4 lease at %1 failed with %2
+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.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO4_PAGE upgrading IPv4 lease extended info at page %1 starting at %2 (updated %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.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6 upgrading IPv6 leases done in %1 pages with %2 updated leases
+Logged at debug log level 40.
The server upgraded extended info. The number of pages and the final count of
updated leases are displayed.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6_ERROR upgrading extending info for IPv6 lease at %1 failed with %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.
% DHCPSRV_MYSQL_UPGRADE_EXTENDED_INFO6_PAGE upgrading IPv6 lease extended info at page %1 starting at %2 (updated %3)
+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.
The reason for the failure is appended as an argument of the log message.
% DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %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 PostgreSQL backend database.
% DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
+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.
The code has issued a begin transaction call.
% DHCPSRV_PGSQL_COMMIT committing to PostgreSQL database
+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.
unlikely to occur or negatively impact server operation.
% DHCPSRV_PGSQL_DELETE_ADDR 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 PostgreSQL database for the specified address.
% DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
+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.
% DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
+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
or the PostgreSQL server has gone down.
% DHCPSRV_PGSQL_GET4 obtaining all IPv4 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv4
leases from the PostgreSQL database.
% DHCPSRV_PGSQL_GET6 obtaining all IPv6 leases
+Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv6
leases from the PostgreSQL database.
% DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %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.
% DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)
+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.
% DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %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.
% DHCPSRV_PGSQL_GET_DUID obtaining IPv6 leases for DUID %1,
+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).
% DHCPSRV_PGSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
+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.
% DHCPSRV_PGSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
+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.
% DHCPSRV_PGSQL_GET_HOSTNAME4 obtaining IPv4 leases for hostname %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.
% DHCPSRV_PGSQL_GET_HOSTNAME6 obtaining IPv6 leases for hostname %1
+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.
% DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %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
hardware address.
% DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %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 PostgreSQL database for a client with the specified IAID
(Identity Association ID) and DUID (DHCP Unique Identifier).
% DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
+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).
% DHCPSRV_PGSQL_GET_PAGE4 obtaining at most %1 IPv4 leases starting from address %2
+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.
% DHCPSRV_PGSQL_GET_PAGE6 obtaining at most %1 IPv6 leases starting from address %2
+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.
% DHCPSRV_PGSQL_GET_RELAYID4 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 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.
% DHCPSRV_PGSQL_GET_RELAYID6 obtaining at most %1 IPv6 leases starting from address %2 with relay id %3
+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.
% DHCPSRV_PGSQL_GET_REMOTEID4 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 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.
% DHCPSRV_PGSQL_GET_REMOTEID6 obtaining at most %1 IPv6 leases starting from address %2 with remote id %3
+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.
% DHCPSRV_PGSQL_GET_SUBID4 obtaining IPv4 leases for subnet ID %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.
% DHCPSRV_PGSQL_GET_SUBID6 obtaining IPv6 leases for subnet ID %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 PostgreSQL database.
% DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
+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.
% DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
+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.
% DHCPSRV_PGSQL_GET_SUBID_PAGE6 obtaining at most %1 IPv6 leases starting from address %2 for subnet ID %3
+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.
% DHCPSRV_PGSQL_GET_VERSION obtaining schema version information
+Logged at debug log level 50.
A debug message issued when the server is about to obtain schema version
information from the PostgreSQL database.
% DHCPSRV_PGSQL_HOST_DB opening PostgreSQL hosts database: %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.
% DHCPSRV_PGSQL_HOST_DB_GET_VERSION obtaining schema version information for the PostgreSQL hosts database
+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.
The parameters of the connection are logged.
% DHCPSRV_PGSQL_ROLLBACK 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.
The parameters of the connection are logged.
% DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
+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.
% DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
+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.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4 upgrading IPv4 leases done in %1 pages with %2 updated leases
+Logged at debug log level 40.
The server upgraded extended info. The number of pages and the final count of
updated leases are displayed.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4_ERROR upgrading extending info for IPv4 lease at %1 failed with %2
+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.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO4_PAGE upgrading IPv4 lease extended info at page %1 starting at %2 (updated %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.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6 upgrading IPv6 leases done in %1 pages with %2 updated leases
+Logged at debug log level 40.
The server upgraded extended info. The number of pages and the final count of
updated leases are displayed.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6_ERROR upgrading extending info for IPv6 lease at %1 failed with %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.
% DHCPSRV_PGSQL_UPGRADE_EXTENDED_INFO6_PAGE upgrading IPv6 lease extended info at page %1 starting at %2 (updated %3)
+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.
% DHCPSRV_QUEUE_NCR %1: Name change request to %2 DNS entry queued: %3
+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
last argument provides the reason for failure.
% DHCPSRV_QUEUE_NCR_SKIP %1: skip queuing name change request for lease: %2
+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
information. The second argument includes the leased address.
% DHCPSRV_SUBNET4O6_SELECT_FAILED Failed to select any subnet for the DHCPv4o6 packet
+Logged at debug log level 40.
A debug message issued when the server was unable to select any subnet for the
DHCPv4o6 packet.
% DHCPSRV_SUBNET4_SELECT_BY_ADDRESS_NO_MATCH No subnet matches address: %1
+Logged at debug log level 40.
A debug message issued when the server was unable to select a subnet using
the specified address.
% DHCPSRV_SUBNET4_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: %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.
% DHCPSRV_SUBNET4_SELECT_BY_RELAY_ADDRESS_NO_MATCH No subnet matches relay address: %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.
% DHCPSRV_SUBNET4_SELECT_NO_RAI_OPTIONS No RAI options found to use for subnet selection.
+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_SUBNET4_SELECT_NO_RELAY_ADDRESS Relay address (giaddr) in client packet is empty.
+Logged at debug log level 40.
A debug message issued when no relay address was specified to use for subnet
selection.
% DHCPSRV_SUBNET4_SELECT_NO_USABLE_ADDRESS No subnet selected because no suitable address to use for subnet selection was found.
+Logged at debug log level 40.
A debug message issued when the server was find a suitable address to use for
subnet selection.
% DHCPSRV_SUBNET6_SELECT_BY_ADDRESS_NO_MATCH No subnet matches address: %1
+Logged at debug log level 40.
A debug message issued when the server was unable to select a subnet using
the specified address.
% DHCPSRV_SUBNET6_SELECT_BY_INTERFACE_ID_NO_MATCH No subnet matches interface id: %1
+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_SUBNET6_SELECT_BY_INTERFACE_NO_MATCH No subnet matches interface: %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.
The timer name and the reason for exception is logged.
% DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: %1, using interval: %2 ms
+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
included in the message.
% DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: %1
+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
message.
% DHCPSRV_TIMERMGR_START_TIMER starting timer: %1
+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_TIMERMGR_STOP_TIMER stopping timer: %1
+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_TIMERMGR_UNREGISTER_ALL_TIMERS unregistering all timers
+Logged at debug log level 40.
A debug message issued when all registered interval timers are
being unregistered from the Timer Manager.
% DHCPSRV_TIMERMGR_UNREGISTER_TIMER 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.
$NAMESPACE isc::dhcp
% FUZZ_DATA_READ read %1 byte(s) from AFL via stdin
+Logged at debug log level 50.
A debug message output to indicate how much data has been received from
the fuzzer via stdin
The message includes the reason for the failure.
% FUZZ_SEND sent %1 byte(s) to the socket connected to the Kea interface
+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.
be used in hosts-database[s].
% HOSTS_BACKEND_DEREGISTER deregistered host backend type: %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.
% HOSTS_BACKEND_REGISTER registered host backend type: %1
+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.
% HOSTS_CFG_ADD_HOST add the host for reservations: %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.
detected by the host manager.
% HOSTS_CFG_CLOSE_HOST_DATA_SOURCE Closing host data source: %1
+Logged at debug log level 40.
This is a normal message being printed when the server closes host data
source connection.
% HOSTS_CFG_DEL deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and address %4
+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.
address.
% HOSTS_CFG_DEL4 deleted %1 host(s) for subnet id %2 and identifier %3
+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.
% HOSTS_CFG_DEL6 deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
+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
is the identifier.
% HOSTS_CFG_DEL_ALL_SUBNET4 deleted all %1 host(s) for subnet id %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.
% HOSTS_CFG_DEL_ALL_SUBNET6 deleted all %1 host(s) having %2 IPv6 reservation(s) for subnet id %3
+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
the subnet identifier.
% HOSTS_CFG_GET_ALL get all hosts with reservations
+Logged at debug log level 45.
This debug message is issued when starting to retrieve all hosts.
% HOSTS_CFG_GET_ALL_ADDRESS4 get all hosts with reservations for IPv4 address %1
+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.
% HOSTS_CFG_GET_ALL_ADDRESS4_COUNT using address %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_ADDRESS4_HOST using address %1 found host: %2
+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.
% HOSTS_CFG_GET_ALL_ADDRESS6 get all hosts with reservations for IPv6 address %1
+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.
% HOSTS_CFG_GET_ALL_ADDRESS6_COUNT using address %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_ADDRESS6_HOST using address %1 found host: %2
+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.
% HOSTS_CFG_GET_ALL_COUNT found %1 host(s)
+Logged at debug log level 45.
This debug message include the details of the host found. The argument
specifies the number of hosts found.
% HOSTS_CFG_GET_ALL_HOST found host: %1
+Logged at debug log level 45.
This debug message includes the details of the host found. The argument
specifies found host details.
% HOSTS_CFG_GET_ALL_HOSTNAME get all hosts with reservations for hostname %1
+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.
% HOSTS_CFG_GET_ALL_HOSTNAME_COUNT using hostname %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_HOSTNAME_HOST using hostname %1, found host: %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.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4 get all hosts with reservations for hostname %1 and IPv4 subnet %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 DHCPv4 subnet. The argument
specifies hostname and subnet id.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_COUNT using hostname %1 and IPv4 subnet %2, found %3 host(s)
+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.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID4_HOST using hostname %1 and IPv4 subnet %2, found host: %3
+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.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6 get all hosts with reservations for hostname %1 and IPv6 subnet %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.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_COUNT using hostname %1 and IPv6 subnet %2, found %3 host(s)
+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.
% HOSTS_CFG_GET_ALL_HOSTNAME_SUBNET_ID6_HOST using hostname %1 and IPv6 subnet %2, found host: %3
+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.
% HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using identifier: %1
+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.
% HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_IDENTIFIER_HOST using identifier: %1, found host: %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.
% HOSTS_CFG_GET_ALL_SUBNET_ID4 get all hosts with reservations for IPv4 subnet %1
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID4_COUNT using IPv4 subnet %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID4_HOST using IPv4 subnet %1, found host: %2
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID6 get all hosts with reservations for IPv6 subnet %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.
% HOSTS_CFG_GET_ALL_SUBNET_ID6_COUNT using IPv6 subnet %1, found %2 host(s)
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID6_HOST using IPv6 subnet %1, found host: %2
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4 get all hosts with reservations for subnet id %1 and IPv4 address %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.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_COUNT using IPv4 subnet %1 and IPv4 address %2, found %3 host(s)
+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
hosts found.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS4_HOST using IPv4 subnet %1 and IPv4 address %2, found host: %3
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6 get all hosts with reservations for subnet id %1 and IPv6 address %2
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_COUNT using subnet id %1 and address %2, found %3 host(s)
+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.
% HOSTS_CFG_GET_ALL_SUBNET_ID_ADDRESS6_HOST using subnet id %1 and address %2, found host: %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.
% HOSTS_CFG_GET_ONE_PREFIX get one host with reservation for prefix %1/%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.
% HOSTS_CFG_GET_ONE_PREFIX_HOST using prefix %1/%2, found host: %3
+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.
% HOSTS_CFG_GET_ONE_PREFIX_NULL host not found using prefix %1/%2
+Logged at debug log level 55.
This debug message is issued when no host was found for a specified
prefix and prefix length.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4 get one host with reservation for subnet id %1 and IPv4 address %2
+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.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_HOST using subnet id %1 and address %2, found host: %3
+Logged at debug log level 45.
This debug message logs the details of the host found using the
subnet id and IPv4 address.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS4_NULL host not found using subnet id %1 and address %2
+Logged at debug log level 45.
This debug message is issued when no host was found for the specified
subnet id and IPv4 address.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6 get one host with reservation for subnet id %1 and having IPv6 address %2
+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.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_HOST using subnet id %1 and address %2, found host: %3
+Logged at debug log level 45.
This debug message logs the details of the host found using the
subnet id and IPv6 address.
% HOSTS_CFG_GET_ONE_SUBNET_ID_ADDRESS6_NULL host not found using subnet id %1 and address %2
+Logged at debug log level 45.
This debug message is issued when no host was found using the specified
subnet if and IPv6 address.
% HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER get one host with %1 reservation for subnet id %2, identified by %3
+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.
% HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_HOST using subnet id %1 and identifier %2, found host: %3
+Logged at debug log level 45.
This debug message includes the details of a host found using a
subnet id and specific host identifier.
% HOSTS_CFG_GET_ONE_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id %1 and identifier %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.
% HOSTS_CFG_UPDATE_ADD add the host for reservations: %1
+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.
% HOSTS_CFG_UPDATE_DEL4 deleted %1 host(s) for subnet id %2 and identifier %3
+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
identifier.
% HOSTS_CFG_UPDATE_DEL6 deleted %1 host(s) having %2 IPv6 reservation(s) for subnet id %3 and identifier %4
+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
identifier.
% HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_ADDRESS4 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 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.
% HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER get one host with IPv4 reservation for subnet id %1, identified by %2
+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.
% HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_HOST using subnet id %1 and identifier %2, found in %3 host: %4
+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.
% HOSTS_MGR_ALTERNATE_GET4_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id %1 and identifier %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.
% HOSTS_MGR_ALTERNATE_GET6_PREFIX trying alternate sources for host using prefix %1/%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.
% HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_ADDRESS6 trying alternate sources for host using subnet id %1 and IPv6 address %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 IPv6 address, and it is starting to search for this
host in alternate host data sources.
% HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER get one host with IPv6 reservation for subnet id %1, identified by %2
+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.
% HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_HOST using subnet id %1 and identifier %2, found in %3 host: %4
+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.
% HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_IDENTIFIER_NULL host not found using subnet id %1 and identifier %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.
% HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS4 trying alternate sources for hosts using subnet id %1 and address %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 IPv4 address.
% HOSTS_MGR_ALTERNATE_GET_ALL_SUBNET_ID_ADDRESS6 trying alternate sources for hosts using subnet id %1 and address %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.
# For use with TokenAnd
% EVAL_DEBUG_AND %1: Popping %2 and %3 pushing %4
+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.
# For use with TokenConcat
% EVAL_DEBUG_CONCAT %1: Popping %2 and %3 pushing %4
+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.
# Start with binary for the inputs for now, we may add text in the future.
% EVAL_DEBUG_EQUAL %1: Popping %2 and %3 pushing result %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.
# For use with TokenHexString
% EVAL_DEBUG_HEXSTRING %1: Pushing hex string %2
+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.
# For use with TokenLowerCase
% EVAL_DEBUG_IFELSE_FALSE %1: Popping %2 (false) and %3, leaving %4
+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.
% EVAL_DEBUG_IFELSE_TRUE %1: Popping %2 (true) and %3, leaving %4
+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.
# For use with TokenIpAddress
% EVAL_DEBUG_INT16TOTEXT %1: Pushing Int16 %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 a 16 bit integer.
# For use with TokenInt32ToText
% EVAL_DEBUG_INT32TOTEXT %1: Pushing Int32 %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 a 32 bit integer.
# For use with TokenUInt8ToText
% EVAL_DEBUG_INT8TOTEXT %1: Pushing Int8 %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 integer.
# For use with TokenInt16ToText
% EVAL_DEBUG_IPADDRESS %1: Pushing IPAddress %2
+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.
# For use with TokenIpAddressToText
% EVAL_DEBUG_IPADDRESSTOTEXT %1: Pushing IPAddress %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 either an IPv4 or IPv6
address.
# For use with TokenInt8ToText
% EVAL_DEBUG_LCASE %1: Popping string %2 and pushing converted value to lower case %3
+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.
# For use with TokenMatch
% EVAL_DEBUG_MATCH Matching '%1' on %2, result %3
+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.
# For use with TokenMember
% EVAL_DEBUG_MEMBER %1: Checking membership of '%2', pushing result %3
+Logged at debug log level 55.
This debug message indicates that the membership of the packet for
the client class was checked.
# For use with TokenNot
% EVAL_DEBUG_NOT %1: Popping %2 pushing %3
+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.
# TokenRelay4Option and TokenRelay6Option.
% EVAL_DEBUG_OPTION %1: Pushing option %2 with value %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
# For use with TokenOr
% EVAL_DEBUG_OR %1: Popping %2 and %3 pushing %4
+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
# For use with TokenPkt
% EVAL_DEBUG_PKT %1: Pushing PKT meta data %2 with value %3
+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.
# For use with TokenPkt4
% EVAL_DEBUG_PKT4 %1: Pushing PKT4 field %2 with value %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.
# For use with TokenPkt6
% EVAL_DEBUG_PKT6 %1: Pushing PKT6 field %2 with value %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.
# For use with TokenRelay6Field
% EVAL_DEBUG_RELAY6 %1: Pushing PKT6 relay field %2 nest %3 with value %4
+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.
% EVAL_DEBUG_RELAY6_RANGE %1: Pushing PKT6 relay field %2 nest %3 with value %4
+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.
# For use with TokenString
% EVAL_DEBUG_SPLIT %1: Popping field %2, delimiters %3, string %4, pushing result %5
+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.
% EVAL_DEBUG_SPLIT_DELIM_EMPTY %1: Popping field %2, delimiters %3, string %4, pushing result %5
+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.
% EVAL_DEBUG_SPLIT_EMPTY %1: Popping field %2, delimiters %3, string %4, pushing result %5
+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.
% EVAL_DEBUG_SPLIT_FIELD_OUT_OF_RANGE %1: Popping field %2, delimiters %3, string %4, pushing result %5
+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.
% EVAL_DEBUG_STRING %1: Pushing text string %2
+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.
# Start with binary for the strings for now, we may add text in the future.
% EVAL_DEBUG_SUBSTRING %1: Popping length %2, start %3, string %4 pushing result %5
+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
the stack. The strings are displayed in hex.
% EVAL_DEBUG_SUBSTRING_EMPTY %1: Popping length %2, start %3, string %4 pushing result %5
+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.
% EVAL_DEBUG_SUBSTRING_RANGE %1: Popping length %2, start %3, string %4 pushing result %5
+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
# For use with TokenToHexString
% EVAL_DEBUG_TOHEXSTRING %1: Popping binary value %2 and separator %3, pushing result %4
+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.
and pushed onto the stack. The binary value is displayed in hex.
% EVAL_DEBUG_UCASE %1: Popping string %2 and pushing converted value to upper case %3
+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.
# For use with TokenIfElse
% EVAL_DEBUG_UINT16TOTEXT %1: Pushing UInt16 %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 a 16 bit unsigned integer.
# For use with TokenUInt32ToText
% EVAL_DEBUG_UINT32TOTEXT %1: Pushing UInt32 %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 a 32 bit unsigned integer.
# For use with TokenMember
% EVAL_DEBUG_UINT8TOTEXT %1: Pushing UInt8 %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.
# For use with TokenUInt16ToText
% EVAL_DEBUG_VENDOR_CLASS_DATA %1: Data %2 (out of %3 received) in vendor class found, pushing result '%4'
+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.
% EVAL_DEBUG_VENDOR_CLASS_DATA_NOT_FOUND %1: Requested data index %2, but option with enterprise-id %3 has only %4 data tuple(s), pushing result '%5'
+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.
% EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID %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
class option was found and its enterprise-id is being reported.
% EVAL_DEBUG_VENDOR_CLASS_ENTERPRISE_ID_MISMATCH %1: Was looking for %2, option had %3, pushing result '%4'
+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.
% EVAL_DEBUG_VENDOR_CLASS_EXISTS %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
class option was found.
% EVAL_DEBUG_VENDOR_CLASS_NO_OPTION %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.
% EVAL_DEBUG_VENDOR_ENTERPRISE_ID %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.
% EVAL_DEBUG_VENDOR_ENTERPRISE_ID_MISMATCH %1: Was looking for %2, option had %3, pushing result '%4'
+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.
% EVAL_DEBUG_VENDOR_EXISTS %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.
% EVAL_DEBUG_VENDOR_NO_OPTION %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 option was not found.
% EVAL_RESULT %1: Expression %2 evaluated to %3
+Logged at debug log level 50.
This debug message indicates that the expression has been evaluated
to said value. This message is mostly useful during debugging of the
client classification expressions.
-# Copyright (C) 2013-2020 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2013-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
$NAMESPACE isc::hooks
% HOOKS_ALL_CALLOUTS_DEREGISTERED hook library at index %1 removed all callouts on hook %2
+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.
% HOOKS_CALLOUTS_BEGIN begin all callouts for hook %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.
% HOOKS_CALLOUTS_COMPLETE completed callouts for hook %1 (total callouts duration: %2)
+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.
% HOOKS_CALLOUTS_REMOVED callouts removed from hook %1 for library %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
higher-level in the hook framework.
% HOOKS_CALLOUT_CALLED hooks library with index %1 has called a callout on hook %2 that has address %3 (callout duration: %4)
+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
The message includes the callout execution time in milliseconds.
% HOOKS_CALLOUT_DEREGISTERED hook library at index %1 deregistered a callout on hook %2
+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 error message includes the callout execution time in milliseconds.
% HOOKS_CALLOUT_REGISTRATION hooks library with index %1 registering callout for hook '%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.
has been successfully loaded.
% HOOKS_LIBRARY_LOADING loading hooks library %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.
% HOOKS_LIBRARY_MULTI_THREADING_COMPATIBLE hooks library %1 reports its multi-threading compatibility as %2
+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.
has been successfully unloaded.
% HOOKS_LIBRARY_UNLOADING unloading 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.
% HOOKS_LIBRARY_VERSION hooks library %1 reports its version as %2
+Logged at debug log level 45.
A debug message issued when the version check on the hooks library
has succeeded.
installed.
% HOOKS_LOAD_SUCCESS 'load' function in hook library %1 returned success
+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.
exception. The library is considered unusable and will not be loaded.
% HOOKS_NO_LOAD no 'load' function found in hook library %1
+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.
% HOOKS_NO_UNLOAD no 'unload' function found in hook library %1
+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.
function, but without the services offered by the library.
% HOOKS_STD_CALLOUT_REGISTERED hooks library %1 registered standard callout for hook %2 at address %3
+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 message and the library has been unloaded.
% HOOKS_UNLOAD_SUCCESS '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.
-# Copyright (C) 2016-2021 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2016-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
$NAMESPACE isc::http
% HTTPS_REQUEST_RECEIVE_START start receiving request from %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.
% HTTP_BAD_CLIENT_REQUEST_RECEIVED bad request received from %1: %2
+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
a detailed error message.
% HTTP_BAD_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about bad request received from %1:\n%2
+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
if it is too large to be printed.
% HTTP_BAD_SERVER_RESPONSE_RECEIVED bad response received when communicating with %1: %2
+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.
% HTTP_BAD_SERVER_RESPONSE_RECEIVED_DETAILS detailed information about bad response received from %1:\n%2
+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.
% HTTP_CLIENT_MT_STARTED HttpClient has been started in multi-threaded mode running %1 threads
+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.
client load.
% HTTP_CLIENT_REQUEST_RECEIVED received HTTP request from %1
+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.
% HTTP_CLIENT_REQUEST_RECEIVED_DETAILS detailed information about well-formed request received from %1:\n%2
+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
The request is truncated by the logger if it is too large to be printed.
% HTTP_CLIENT_REQUEST_SEND sending HTTP request %1 to %2
+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.
% HTTP_CLIENT_REQUEST_SEND_DETAILS detailed information about request sent to %1:\n%2
+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
The request is truncated by the logger if it is too large to be printed.
% HTTP_CLIENT_REQUEST_TIMEOUT_OCCURRED HTTP request timeout occurred when communicating with %1
+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.
server side. The client address and the error message are displayed.
% HTTP_CONNECTION_HANDSHAKE_START start TLS handshake with %1 with timeout %2
+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.
% HTTP_CONNECTION_SHUTDOWN shutting down HTTP connection from %1
+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.
a HTTP connection with a client.
% HTTP_CONNECTION_STOP stopping HTTP connection from %1
+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.
HTTP connection with a client.
% HTTP_DATA_RECEIVED received %1 bytes from %2
+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.
produced the data.
% HTTP_IDLE_CONNECTION_TIMEOUT_OCCURRED closing persistent connection with %1 as a result of a timeout
+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.
will be interrupted. New transactions should be conducted normally.
% HTTP_REQUEST_RECEIVE_START start receiving request from %1 with timeout %2
+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.
% HTTP_SERVER_RESPONSE_RECEIVED received HTTP response from %1
+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.
% HTTP_SERVER_RESPONSE_RECEIVED_DETAILS detailed information about well-formed response received from %1:\n%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
be printed.
% HTTP_SERVER_RESPONSE_SEND 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.
% HTTP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to %1:\n%2
+Logged at debug log level 45.
This debug message is issued right before the server sends a HTTP response
to the client. It includes detailed information about the response. The
first argument specifies an address of the remote endpoint to which the
-# Copyright (C) 2011-2020 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2011-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
$NAMESPACE isc::log
% LOG_BAD_DESTINATION unrecognized log destination: %1
+Logged at debug log level 0.
A logger destination value was given that was not recognized. The
destination should be one of "console", "file", or "syslog".
% LOG_BAD_SEVERITY unrecognized log severity: %1
+Logged at debug log level 25.
A logger severity value was given that was not recognized. The severity
should be one of "DEBUG", "INFO", "WARN", "ERROR", "FATAL" or "NONE".
version of Kea.
% LOG_READING_LOCAL_FILE reading local message file %1
+Logged at debug log level 0.
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.)
process requests until the configuration has been corrected.
% DCTL_CONFIG_START parsing new configuration: %1
+Logged at debug log level 10.
A debug message indicating that the application process has received an
updated configuration and has passed it to its configuration manager
for parsing.
(vs stable) one: the second number of the version is odd.
% DCTL_INIT_PROCESS %1 initializing the application
+Logged at debug log level 0.
This debug message is issued just before the controller attempts
to create and initialize its application instance.
included in the message.
% DCTL_RUN_PROCESS %1 starting application event loop
+Logged at debug log level 0.
This debug message is issued just before the controller invokes
the application run method.
Kea and will exit.
% DCTL_SHUTDOWN %1 has shut down, pid: %2, version: %3
+Logged at debug log level 0.
This is an informational message indicating that the service has shut
down. The argument specifies a name of the service.
% DCTL_SHUTDOWN_SIGNAL_RECVD OS signal %1 received, starting shutdown
+Logged at debug log level 0.
This is a debug message indicating the application has received a signal
instructing it to shutdown.
% DCTL_STANDALONE %1 skipping message queue, running standalone
+Logged at debug log level 0.
This is a debug message indicating that the controller is running in the
application in standalone mode. This means it will not connected to the Kea
message queue. Standalone mode is only useful during program development,
-# Copyright (C) 2022-2023 Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2022-2024 Internet Systems Consortium, Inc. ("ISC")
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
$NAMESPACE isc::tcp
% MT_TCP_LISTENER_MGR_STARTED MtTcpListenerMgr started with %1 threads, listening on %2:%3, use TLS: %4
+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.
% MT_TCP_LISTENER_MGR_STOPPED MtTcpListenerMgr for %1:%2 stopped.
+Logged at debug log level 40.
This debug messages is issued when the MtTcpListenerMgr, listening
at the given address and port, has completed shutdown.
% MT_TCP_LISTENER_MGR_STOPPING Stopping MtTcpListenerMgr for %1:%2
+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.
% TCP_CLIENT_REQUEST_RECEIVED received TCP request from %1
+Logged at debug log level 40.
This debug message is issued when the server finished receiving a TCP
request from the remote endpoint. The address of the remote endpoint is
specified as an argument.
error that should be submitted as a bug.
% TCP_CONNECTION_REJECTED_BY_FILTER connection from %1 has been denied by the connection filter.
+Logged at debug log level 50.
This debug message is issued when the server's connection filter rejects
a new connection based on the client's ip address.
% TCP_CONNECTION_SHUTDOWN shutting down TCP connection from %1
+Logged at debug log level 40.
This debug message is issued when one of the TCP connections is shut down.
The connection can be stopped as a result of an error or after the
successful message exchange with a client.
a TCP connection with a client.
% TCP_CONNECTION_STOP stopping TCP connection from %1
+Logged at debug log level 40.
This debug message is issued when one of the TCP connections is stopped.
The connection can be stopped as a result of an error or after the
successful message exchange with a client.
TCP connection with a client.
% TCP_DATA_RECEIVED received %1 bytes from %2
+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.
produced the data.
% TCP_DATA_SENT send %1 bytes to %2
+Logged at debug log level 55.
This debug message is issued when the server sends a chunk of data to
the remote endpoint. This may include the whole response or only a part
of the response. The first argument specifies the amount of sent data.
The second argument specifies an address of the remote endpoint.
% TCP_IDLE_CONNECTION_TIMEOUT_OCCURRED closing connection with %1 as a result of a timeout
+Logged at debug log level 50.
This debug message is issued when the TCP connection is being closed as a
result of being idle.
error.
% TCP_REQUEST_RECEIVE_START start receiving request from %1 with timeout %2
+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.
% TCP_SERVER_RESPONSE_SEND sending TCP response to %1
+Logged at debug log level 40.
This debug message is issued when the server is starting to send a TCP
response to a remote endpoint. The argument specifies an address of
the remote endpoint.
server side. The client address and the error message are displayed.
% TLS_CONNECTION_HANDSHAKE_START start TLS handshake with %1 with timeout %2
+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.
% TLS_REQUEST_RECEIVE_START start receiving request from %1 with timeout %2
+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.
% TLS_SERVER_RESPONSE_SEND sending TLS response to %1
+Logged at debug log level 40.
This debug message is issued when the server is starting to send a TLS
response to a remote endpoint. The argument specifies an address of
the remote endpoint.
projects / thirdparty / kea.git / commitdiff
