pools require packet to belong to certain classes and the incoming packet
didn't belong to any of them. Another case where this information may be
useful is to point out that the pool reserved to a given class has run
-out of addresses. When you see this message, you may consider checking your
-pool size and your classification definitions.
+out of addresses. If this message is displayed, consider checking the
+pool size and the classification definitions.
ALLOC_ENGINE_V4_ALLOC_FAIL_NO_POOLS
===================================
pools require packet to belong to certain classes and the incoming packet
didn't belong to any of them. Another case where this information may be
useful is to point out that the pool reserved to a given class has run
-out of addresses. When you see this message, you may consider checking your
-pool size and your classification definitions.
+out of addresses. If this message is displayed, you may consider checking the
+pool size and the classification definitions.
ALLOC_ENGINE_V6_ALLOC_FAIL_NO_POOLS
===================================
Logged at debug log level 40.
This message is logged when the allocation engine is in the process of
-allocating leases for the client, there are no static reservations,
+allocating leases for the client and there are no static reservations,
but lease(s) exist for the client. The allocation engine will remove
leases which are reserved for other clients, and return all
remaining leases to the client.
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
+This debug message is 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.
failed to reuse HTTPS service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTPS service on the specified address and port. The server can not switch from
+This error message indicates that the server has failed to reuse existing
+HTTPS service on the specified address and port. The server cannot switch from
HTTPS to HTTP sockets using the same address and port.
CTRL_AGENT_HTTPS_SERVICE_STARTED
failed to reuse HTTP service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTP service on the specified address and port. The server can not switch from
+This error message indicates that the server has failed to reuse existing
+HTTP service on the specified address and port. The server cannot switch from
HTTP to HTTPS sockets using the same address and port.
CTRL_AGENT_HTTP_SERVICE_STARTED
starting new MySQL transaction
-A debug message issued when a new MySQL transaction is being started.
+This debug message is issued when a new MySQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
starting a new PostgreSQL transaction
-A debug message issued when a new PostgreSQL transaction is being started.
+This debug message is issued when a new PostgreSQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
%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
+This debug message is 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.
opening service sockets on port %1
Logged at debug log level 0.
-A debug message issued during startup, this indicates that the DHCPv4
+This debug message is issued during startup, this indicates that the DHCPv4
server is about to open sockets on the specified port.
DHCP4_OPEN_SOCKETS_FAILED
%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
+This debug message is issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
still attempt to service the packet.
.. code-block:: text
- All packets will be sent to source address of an incoming packet - use only for testing
+ All packets will be sent to the source address of an incoming packet - use only for testing
-This message is printed then KEA_TEST_SEND_RESPONSES_TO_SOURCE
-environment variable is set. It's causing Kea to send packets to
-source address of incoming packet. Usable just in testing environment
+This message is printed, then the KEA_TEST_SEND_RESPONSES_TO_SOURCE
+environment variable is set. It's causes Kea to send packets to the
+source address of the incoming packet. It is only usable in a testing environment
to simulate multiple subnet traffic from single source.
DHCP4_UNKNOWN_ADDRESS_REQUESTED
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
-release a lease. If a client requested the release of multiples leases
+release a lease. If a client requested the release of multiple leases
(by sending multiple IA options), the server will retain this particular
lease and proceed with other releases as usual. The argument holds the
client and transaction identification information.
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
-a lease. If client requested release of multiples leases (by sending
+a lease. If client requested release of multiple leases (by sending
multiple IA options), the server will retain this particular lease and
will proceed with other renewals as usual. The argument holds the
client and transaction identification information.
opening service sockets on port %1
Logged at debug log level 0.
-A debug message issued during startup, this indicates that the IPv6 DHCP
+This debug message is issued during startup, this indicates that the IPv6 DHCP
server is about to open sockets on the specified port.
DHCP6_OPEN_SOCKETS_FAILED
%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
+This debug message is 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.
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
+This debug message is 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.
+This debug message is issued when the server's DHCP-DDNS settings are changed.
DHCPSRV_CFGMGR_CONFIG4_MERGED
=============================
%1 of lease life time %2 is %3, using maximum of %4 instead.
Logged at debug log level 55.
-A debug message issued when the DDNS TTL value calculated using the
+This debug message is issued when the DDNS TTL value calculated using the
ddns-ttl-percent if specified or (0.33 if not) is larger than the
the specified value of ddns-ttl-max. Kea will ignore the value and
use the specified maximum instead. The message details include
%1 of lease life time %2 is %3, using minimum of %4 instead.
Logged at debug log level 55.
-A debug message issued when the DDNS TTL value calculated using the
+This debug message is issued when the DDNS TTL value calculated using the
ddns-ttl-percent if specified or (0.33 if not) is too small. Kea will
ignore the value and use the minimum (ddns-ttl-min if specified or 600
seconds if not). The message details include the percentage, the lease
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
+This debug message is issued when a NameChangeRequest has been successfully sent to
kea-dhcp-ddns.
DHCPSRV_DHCP_DDNS_SENDER_STARTED
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
+This debug message is 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
+This debug message is 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.
+This debug message is 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.
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.
+This debug message is issued when the server is extracting extended info.
The extended info sanity check level and update in file when requested
are displayed.
deleting lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to delete a lease
+This debug message is issued when the server is attempting to delete a lease
for the specified address from the memory file database for the specified
address.
deleting lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to delete a lease
+This debug message is issued when the server is attempting to delete a lease
for the specified address from the memory file database for the specified
address.
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
+This debug message is 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.
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
+This debug message is 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.
starting deletion of %1 expired-reclaimed leases
Logged at debug log level 50.
-A debug message issued when the server has found expired-reclaimed
+This debug message is issued when the server has found expired-reclaimed
leases to be removed. The number of leases to be removed is logged
in the message.
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
+This debug message is issued when the server is extracting extended info and
receives an exception processing a lease.
DHCPSRV_MEMFILE_FAILED_TO_OPEN
obtaining all IPv4 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
obtaining IPv6 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
+This debug message is issued when the server is attempting to obtain a set of
IPv6 leases from the memory file database for a client with the specified
hardware address.
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
+This debug message is 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).
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
+This debug message is 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).
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
+This debug message is 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
+This debug message is 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
+This debug message is 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.
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
+This debug message is 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
+This debug message is 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.
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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
loading lease %1
Logged at debug log level 55.
-A debug message issued when DHCP lease is being loaded from the file to memory.
+This debug message is issued when DHCP lease is being loaded from the file to memory.
DHCPSRV_MEMFILE_LEASE_LOAD_ROW_ERROR
====================================
updating IPv4 lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv4
+This debug message is 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
+This debug message is issued when the server is attempting to update IPv6
lease from the memory file database for the specified address.
DHCPSRV_MEMFILE_WIPE_LEASES4
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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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 could not find a suitable address to use for
+This debug message is issued when the server could not 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
+This debug message is 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
+This debug message is 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
+This debug message is issued when the server was unable to select a subnet using
the specified interface name.
DHCPSRV_TEMPLATE_EVAL_ERROR
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
+This debug message is issued when the new interval timer is registered in
the Timer Manager. This timer will have a callback function
associated with it, and this function will be executed according
to the interval specified. The unique name of the timer and the
running operation for timer: %1
Logged at debug log level 50.
-A debug message issued when the Timer Manager is about to
+This debug message is issued when the Timer Manager is about to
run a periodic operation associated with the given timer.
An example of such operation is a periodic cleanup of
expired leases. The name of the timer is included in the
starting timer: %1
Logged at debug log level 40.
-A debug message issued when the registered interval timer is
+This debug message is 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.
stopping timer: %1
Logged at debug log level 40.
-A debug message issued when the registered interval timer is
+This debug message is 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.
unregistering all timers
Logged at debug log level 40.
-A debug message issued when all registered interval timers are
+This debug message is 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
+This debug message is issued when one of the registered interval timers
is unregistered from the Timer Manager. The name of the timer is
included in the message.
Logged at debug log level 0.
This is a debug message issued when the DHCP-DDNS server exits its
-event loop
+event loop.
DHCP_DDNS_SECURITY_CHECKS_DISABLED
==================================
Logged at debug log level 55.
This debug message indicates that two values are popped from
-the value stack. They are then combined via logical and and
+the value stack. They are then combined via logical "and" and
the result is pushed onto the value stack.
EVAL_DEBUG_BRANCH
Logged at debug log level 55.
This debug message indicates that two values are popped from
-the value stack. They are then combined via logical or and
+the value stack. They are then combined via logical "or" and
the result is pushed onto the value stack. The string is displayed
in text.
GSS-TSIG verify succeeded.
Logged at debug log level 40.
-A debug message issued when GSS-TSIG verification succeeded.
+This debug message is issued when GSS-TSIG verification succeeded.
GSS_TSIG_VERIFY_FAILED
======================
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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is issued when all instances of a particular callouts on
the hook identified in the message that were registered by the library
with the given index have been removed.
hooks 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
+This debug message is issued when the "multi_threading_compatible" function was
called. The returned value (0 means not compatible, others compatible)
is displayed.
failed to reused HTTPS service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTPS service on the specified address and port. The server can not swith from
+This error message indicates that the server has failed to reuse existing
+HTTPS service on the specified address and port. The server cannot swith from
HTTPS to HTTP sockets using the same address and port.
HTTP_COMMAND_MGR_HTTPS_SERVICE_UPDATED
failed to reused HTTP service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTP service on the specified address and port. The server can not swith from
+This error message indicates that the server has failed to reuse existing
+HTTP service on the specified address and port. The server cannot swith from
HTTP to HTTPS sockets using the same address and port.
HTTP_COMMAND_MGR_HTTP_SERVICE_UPDATED
obtaining schema version information
Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
+This debug message is issued when the server is about to obtain schema version
information from the MySQL database.
LEGAL_LOG_MYSQL_INSERT_LOG
starting new MySQL transaction
-A debug message issued when a new MySQL transaction is being started.
+This debug message is issued when a new MySQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
TLS cipher: %1
Logged at debug log level 50.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
LEGAL_LOG_PATH_SECURITY_WARNING
An error occurred deallocating SQL statements while closing the PostgreSQL log database: %1
-This is an error message issued when a legal log hook library experienced
+This is an error message issued when the legal log hook library experienced
an error freeing database SQL resources as part of closing its connection to
the PostgreSQL database. The connection is closed as part of normal server
shutdown. This error is most likely a programmatic issue that is highly
obtaining schema version information
Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL database.
LEGAL_LOG_PGSQL_INSERT_LOG
starting a new PostgreSQL transaction
-A debug message issued when a new PostgreSQL transaction is being started.
+This debug message is issued when a new PostgreSQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
TLS cipher: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
MYSQL_CB_UNREGISTER_BACKEND_TYPE4
opening MySQL log database: %1
-This informational message is logged when a legal log hook library is
+This informational message is logged when the legal log hook library is
about to open a MySQL log database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
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
+This debug message is issued when the server is about to obtain schema version
information from the MySQL hosts database.
MYSQL_HB_DB_READONLY
TLS cipher: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
MYSQL_INIT_OK
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
+This debug message is issued when the server is about to add an IPv4 lease
with the specified address to the MySQL backend database.
MYSQL_LB_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
+This debug message is issued when the server is about to add an IPv6 lease
with the specified address to the MySQL backend database.
MYSQL_LB_COMMIT
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
+This debug message is issued when the server has removed a number of reclaimed
leases from the database. The number of removed leases is included in the
message.
deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
MYSQL_LB_DELETED_SUBNET6_ID
deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
MYSQL_LB_DELETE_ADDR4
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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the MySQL database for the specified address.
MYSQL_LB_DELETE_ADDR6
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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the MySQL database for the specified address.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
obtaining all IPv4 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
+This debug message is issued when the server is attempting to obtain all IPv4
leases from the MySQL database.
MYSQL_LB_GET6
obtaining all IPv6 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
+This debug message is issued when the server is attempting to obtain all IPv6
leases from the MySQL database.
MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the MySQL database for the specified address.
MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the MySQL database for the specified address.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the MySQL database for the specified duid.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database for a client with the specified
hostname.
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
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database for a client with the specified
hostname.
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
+This debug message is 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.
obtaining IPv6 leases for hardware address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database for a client with the specified
hardware address.
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
+This debug message is 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).
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
+This debug message is 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).
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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a relay id.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a remote id.
MYSQL_LB_GET_STATE4
obtaining IPv4 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database with the specified state.
MYSQL_LB_GET_STATE6
obtaining IPv6 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database with the specified state.
MYSQL_LB_GET_STATE_SUBID4
obtaining IPv4 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database with the specified state in
the specified subnet.
obtaining IPv6 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database with the specified state in
the specified subnet.
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
+This debug message is issued when the server is attempting to obtain all IPv4
leases for a given subnet identifier from the MySQL database.
MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv6
leases for a given subnet identifier from the MySQL database.
MYSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
obtaining schema version information
Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
+This debug message is issued when the server is about to obtain schema version
information from the MySQL database.
MYSQL_LB_NEGATIVE_LEASES_STAT
TLS cipher: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
MYSQL_LB_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
+This debug message is issued when the server is attempting to update IPv4
lease from the MySQL database for the specified address.
MYSQL_LB_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
+This debug message is issued when the server is attempting to update IPv6
lease from the MySQL database for the specified address.
MYSQL_LB_UPGRADE_EXTENDED_INFO4
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.
+This debug message is issued when the server failed to upgrade an extended info.
The address of the lease and the error message are displayed.
MYSQL_LB_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.
+This debug message is issued when the server upgrades IPv4 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
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
+This debug message is issued when the server failed to upgrade the extended info
for a lease. The address of the lease and the error message are displayed.
MYSQL_LB_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.
+This debug message is issued when the server upgrades IPv6 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
opening PostgreSQL log database: %1
-This informational message is logged when a legal log hook library is
+This informational message is logged when the legal log hook library is
about to open a PostgreSQL log database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
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
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL hosts database.
PGSQL_HB_DB_READONLY
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
+This debug message is issued when the server is about to add an IPv4 lease
with the specified address to the PostgreSQL backend database.
PGSQL_LB_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
+This debug message is issued when the server is about to add an IPv6 lease
with the specified address to the PostgreSQL backend database.
PGSQL_LB_COMMIT
deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
PGSQL_LB_DELETED_SUBNET6_ID
deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
PGSQL_LB_DELETE_ADDR4
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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the PostgreSQL database for the specified address.
PGSQL_LB_DELETE_ADDR6
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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the PostgreSQL database for the specified address.
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
obtaining all IPv4 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
+This debug message is issued when the server is attempting to obtain all IPv4
leases from the PostgreSQL database.
PGSQL_LB_GET6
obtaining all IPv6 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
+This debug message is issued when the server is attempting to obtain all IPv6
leases from the PostgreSQL database.
PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the PostgreSQL database for the specified address.
PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the PostgreSQL database for the specified address.
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a set of IPv6
leases from the PostgreSQL database for a client with the specified DUID (DHCP Unique Identifier).
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database for a client with the specified
hostname.
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
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database for a client with the specified
hostname.
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
+This debug message is 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.
obtaining IPv6 leases for hardware address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database for a client with the specified
hardware address.
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
+This debug message is 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).
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
+This debug message is 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).
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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a relay id.
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a remote id.
PGSQL_LB_GET_STATE4
obtaining IPv4 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database with the specified state.
PGSQL_LB_GET_STATE6
obtaining IPv6 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database with the specified state.
PGSQL_LB_GET_STATE_SUBID4
obtaining IPv4 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database with the specified state in
the specified subnet.
obtaining IPv6 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database with the specified state in
the specified subnet.
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
+This debug message is issued when the server is attempting to obtain all IPv4
leases for a given subnet identifier from the PostgreSQL database.
PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv6
leases for a given subnet identifier from the PostgreSQL database.
PGSQL_LB_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
+This debug message is 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.
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
+This debug message is 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.
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
+This debug message is 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.
obtaining schema version information
Logged at debug log level 50.
-A debug message issued when the server is about to obtain schema version
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL database.
PGSQL_LB_NEGATIVE_LEASES_STAT
updating IPv4 lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to update IPv4
+This debug message is issued when the server is attempting to update IPv4
lease from the PostgreSQL database for the specified address.
PGSQL_LB_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
+This debug message is issued when the server is attempting to update IPv6
lease from the PostgreSQL database for the specified address.
PGSQL_LB_UPGRADE_EXTENDED_INFO4
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.
+This debug message is issued when the server failed to upgrade an extended info.
The address of the lease and the error message are displayed.
PGSQL_LB_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.
+This debug message is issued when the server upgrades IPv4 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
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
+This debug message is issued when the server failed to upgrade the extended info
for a lease. The address of the lease and the error message are displayed.
PGSQL_LB_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.
+This debug message is issued when the server upgrades IPv6 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
This error message is emitted when an unexpected error occurred while
attempting to resume operation of the ping channel's thread pool. This
error is highly unlikely and indicates a programmatic issue that should
-be reported as defect.
+be reported as a defect.
PING_CHECK_UNEXPECTED_READ_ERROR
================================
This error message is emitted when an unexpected error occurred while attempting
to resume the thread pool. This error is highly unlikely and indicates a
-programmatic issue that should be reported as defect.
+programmatic issue that should be reported as a defect.
RADIUS_SERVER_CONFIGURED
========================
GSS-TKEY exchange received a response with answer class: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified answer class.
TKEY_EXCHANGE_FAILED_TO_VERIFY
GSS-TKEY exchange failed because the response failed to verify.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
failed to verify.
TKEY_EXCHANGE_FAIL_EMPTY_IN_TOKEN
GSS-TKEY exchange failed because input token is empty.
-This error message indicated that GSS-TKEY exchange failed because input token
+This error message indicates that the GSS-TKEY exchange failed because input token
is empty.
TKEY_EXCHANGE_FAIL_EMPTY_OUT_TOKEN
GSS-TKEY exchange failed because output token is empty.
-This error message indicated that GSS-TKEY exchange failed because output token
+This error message indicates that the GSS-TKEY exchange failed because output token
is empty.
TKEY_EXCHANGE_FAIL_EMPTY_RESPONSE
GSS-TKEY exchange failed because the response is empty.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is empty.
TKEY_EXCHANGE_FAIL_IO_ERROR
GSS-TKEY exchange failed because of the IO error: %1.
-This error message indicated that GSS-TKEY exchange failed because of an IO error.
+This error message indicates that the GSS-TKEY exchange failed because of an IO error.
The argument details the IO error.
TKEY_EXCHANGE_FAIL_IO_STOPPED
GSS-TKEY exchange failed because the IO service was stopped.
-This error message indicated that GSS-TKEY exchange failed because the IO
+This error message indicates that the GSS-TKEY exchange failed because the IO
service was stopped.
TKEY_EXCHANGE_FAIL_IO_TIMEOUT
GSS-TKEY exchange failed because of IO timeout.
-This error message indicated that GSS-TKEY exchange failed because of IO
+This error message indicates that the GSS-TKEY exchange failed because of IO
timeout.
TKEY_EXCHANGE_FAIL_NOT_SIGNED
GSS-TKEY exchange failed because the response is not signed.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is not signed.
TKEY_EXCHANGE_FAIL_NO_RDATA
GSS-TKEY exchange failed because the response contains no rdata.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains no rdata.
TKEY_EXCHANGE_FAIL_NO_RESPONSE_ANSWER
GSS-TKEY exchange failed because the response contains no answer.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains no answer.
TKEY_EXCHANGE_FAIL_NULL_RESPONSE
GSS-TKEY exchange failed because the response is null.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is null.
TKEY_EXCHANGE_FAIL_RESPONSE_ERROR
GSS-TKEY exchange failed because the response contains an error: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains an error. The argument details the response error.
TKEY_EXCHANGE_FAIL_TKEY_ERROR
GSS-TKEY exchange failed because the response contains TKEY error: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains TKEY error. The argument details the TKEY error.
TKEY_EXCHANGE_FAIL_TO_INIT
GSS-TKEY exchange failed to initialize because of the error: %1.
-This error message indicated that GSS-TKEY exchange failed in the
+This error message indicates that the GSS-TKEY exchange failed in the
initialization phase, for instance because the server principal does not
exist. The argument details the error.
GSS-TKEY exchange failed because the response contains invalid number of RRs: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains invalid number of RRs. The argument contains the wrong number of RRs.
TKEY_EXCHANGE_FAIL_WRONG_RESPONSE_ANSWER_TYPE
GSS-TKEY exchange failed because the response contains wrong answer type: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains wrong answer type. The argument contains the wrong answer type.
TKEY_EXCHANGE_FAIL_WRONG_RESPONSE_OPCODE
GSS-TKEY exchange failed because the response contains invalid opcode: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains invalid opcode. The argument contains the wrong opcode.
TKEY_EXCHANGE_NOT_A_RESPONSE
GSS-TKEY exchange received a non response type.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a non response
+This debug message indicates that the GSS-TKEY exchange received a non response
type.
TKEY_EXCHANGE_OUT_TOKEN_NOT_EMPTY
GSS-TKEY exchange output token is not empty.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange output token is not empty.
+This debug message indicates that the GSS-TKEY exchange output token is not empty.
TKEY_EXCHANGE_RDATA_COUNT
=========================
GSS-TKEY exchange received a response with rdata count: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified rdata count.
TKEY_EXCHANGE_RECEIVE_MESSAGE
GSS-TKEY exchange receives a message of size: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange receives a message of
+This debug message indicates that the GSS-TKEY exchange receives a message of
specified size.
TKEY_EXCHANGE_RESPONSE_TTL
GSS-TKEY exchange received a response with TTL of: %1 seconds.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified TTL.
TKEY_EXCHANGE_SEND_MESSAGE
GSS-TKEY exchange sends a message of size: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange sends a message of specified
+This debug message indicates that the GSS-TKEY exchange sends a message of specified
size.
TKEY_EXCHANGE_VALID
GSS-TKEY exchange retrieved a TKEY valid for: %1 seconds.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange retrieved a TKEY valid for
+This debug message indicates that the GSS-TKEY exchange retrieved a TKEY valid for
the specified time period expressed in seconds.
TKEY_EXCHANGE_VERIFIED
GSS-TKEY exchange verified.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange is verified.
+This debug message indicates that the GSS-TKEY exchange is verified.
***
TLS
"CTRL_AGENT_HTTPS_SERVICE_REUSE_FAILED", "failed to reuse HTTPS service bound to address: %1 port: %2",
"CTRL_AGENT_HTTPS_SERVICE_STARTED", "HTTPS service bound to address: %1 port: %2",
"CTRL_AGENT_HTTPS_SERVICE_UPDATED", "reused HTTPS service bound to address: %1 port: %2 and updated TLS settings",
- "CTRL_AGENT_HTTP_SERVICE_REUSE_FAILED", "failed to reused HTTP service bound to address: %1 port: %2",
+ "CTRL_AGENT_HTTP_SERVICE_REUSE_FAILED", "failed to reuse HTTP service bound to address: %1 port: %2",
"CTRL_AGENT_HTTP_SERVICE_STARTED", "HTTP service bound to address: %1 port: %2",
"CTRL_AGENT_HTTP_SERVICE_UPDATED", "reused HTTP service bound to address: %1 port: %2",
"CTRL_AGENT_IS_DEPRECATED", "Kea Control Agent is deprecated. Its function has been moved to Kea servers.",
encounters an unrecoverable error from within the event loop.
% CTRL_AGENT_HTTPS_SERVICE_REUSE_FAILED failed to reuse HTTPS service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTPS service on the specified address and port. The server can not switch from
+This error message indicates that the server has failed to reuse existing
+HTTPS service on the specified address and port. The server cannot switch from
HTTPS to HTTP sockets using the same address and port.
% CTRL_AGENT_HTTPS_SERVICE_STARTED HTTPS service bound to address: %1 port: %2
the TLS setup has been applied.
% CTRL_AGENT_HTTP_SERVICE_REUSE_FAILED failed to reuse HTTP service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTP service on the specified address and port. The server can not switch from
+This error message indicates that the server has failed to reuse existing
+HTTP service on the specified address and port. The server cannot switch from
HTTP to HTTPS sockets using the same address and port.
% CTRL_AGENT_HTTP_SERVICE_STARTED HTTP service bound to address: %1 port: %2
"DHCP4_HOOK_LEASES4_COMMITTED_PARK", "%1: packet is parked, because a callout set the next step to PARK",
"DHCP4_HOOK_LEASES4_COMMITTED_PARKING_LOT_FULL", "The parked-packet-limit %1, has been reached, dropping query: %2",
"DHCP4_HOOK_PACKET_RCVD_SKIP", "%1: packet is dropped, because a callout set the next step to SKIP",
- "DHCP4_HOOK_PACKET_SEND_DROP", "%1: prepared DHCPv4 response was not sent because a callout set the next ste to DROP",
- "DHCP4_HOOK_PACKET_SEND_SKIP", "%1: prepared response is not sent, because a callout set the next stp to SKIP",
+ "DHCP4_HOOK_PACKET_SEND_DROP", "%1: prepared DHCPv4 response was not sent because a callout set the next step to DROP",
+ "DHCP4_HOOK_PACKET_SEND_SKIP", "%1: prepared response is not sent, because a callout set the next step to SKIP",
"DHCP4_HOOK_SUBNET4_SELECT_4O6_PARKING_LOT_FULL", "The parked-packet-limit %1, has been reached, dropping query: %2",
"DHCP4_HOOK_SUBNET4_SELECT_DROP", "%1: packet was dropped, because a callout set the next step to 'drop'",
"DHCP4_HOOK_SUBNET4_SELECT_PARK", "%1: packet was parked",
"DHCP4_SUBNET_DYNAMICALLY_CHANGED", "%1: changed selected subnet %2 to subnet %3 from shared network %4 for client assignments",
"DHCP4_SUBNET_SELECTED", "%1: the subnet with ID %2 was selected for client assignments",
"DHCP4_SUBNET_SELECTION_FAILED", "%1: failed to select subnet for the client",
- "DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED", "All packets will be send to source address of an incoming packet - use only for testing",
+ "DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED", "All packets will be sent to the source address of an incoming packet - use only for testing",
"DHCP4_UNKNOWN_ADDRESS_REQUESTED", "%1: client requested an unknown address, client sent ciaddr %2, requested-ip-address %3",
"DHCP4_V6_ONLY_PREFERRED_MISSING_IN_ACK", "v6-only-preferred option missing in 0.0.0.0 reply to query: %1",
"DHCP4_V6_ONLY_PREFERRED_MISSING_IN_OFFER", "v6-only-preferred option missing in 0.0.0.0 offer to query: %1",
% 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
+This debug message is 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.
% 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
+This debug message is issued during startup, this indicates that the DHCPv4
server is about to open sockets on the specified port.
% DHCP4_OPEN_SOCKETS_FAILED maximum number of open service sockets attempts: %1, has been exhausted without success
% 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
+This debug message is issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
still attempt to service the packet.
The argument includes the client and the transaction identification
information.
-% DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED All packets will be sent to source address of an incoming packet - use only for testing
-This message is printed then KEA_TEST_SEND_RESPONSES_TO_SOURCE
-environment variable is set. It's causing Kea to send packets to
-source address of incoming packet. Usable just in testing environment
+% DHCP4_TESTING_MODE_SEND_TO_SOURCE_ENABLED All packets will be sent to the source address of an incoming packet - use only for testing
+This message is printed, then the KEA_TEST_SEND_RESPONSES_TO_SOURCE
+environment variable is set. It's causes Kea to send packets to the
+source address of the incoming packet. It is only usable in a testing environment
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
"DHCP6_HOOK_LEASES6_COMMITTED_PARK", "%1: packet is parked, because a callout set the next step to PARK",
"DHCP6_HOOK_LEASES6_PARKING_LOT_FULL", "The parked-packet-limit %1, has been reached, dropping query: %2",
"DHCP6_HOOK_PACKET_RCVD_SKIP", "%1: packet is dropped, because a callout set the next step to SKIP",
- "DHCP6_HOOK_PACKET_SEND_DROP", "%1: prepared DHCPv6 response was not sent because a callout set the next ste to DROP",
+ "DHCP6_HOOK_PACKET_SEND_DROP", "%1: prepared DHCPv6 response was not sent because a callout set the next step to DROP",
"DHCP6_HOOK_PACKET_SEND_SKIP", "%1: prepared DHCPv6 response is not built because a callout set the next step to SKIP",
"DHCP6_HOOK_SUBNET6_SELECT_DROP", "%1: packet was dropped because a callout set the drop flag",
"DHCP6_HOOK_SUBNET6_SELECT_PARK", "%1: packet was parked",
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
-release a lease. If a client requested the release of multiples leases
+release a lease. If a client requested the release of multiple leases
(by sending multiple IA options), the server will retain this particular
lease and proceed with other releases as usual. The argument holds the
client and transaction identification information.
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
-a lease. If client requested release of multiples leases (by sending
+a lease. If client requested release of multiple leases (by sending
multiple IA options), the server will retain this particular lease and
will proceed with other renewals as usual. The argument holds the
client and transaction identification information.
% 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
+This debug message is issued during startup, this indicates that the IPv6 DHCP
server is about to open sockets on the specified port.
% DHCP6_OPEN_SOCKETS_FAILED maximum number of open service sockets attempts: %1, has been exhausted without success
% 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
+This debug message is 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.
"GSS_TSIG_MANAGER_STOP_GENERAL_ERROR", "manager stop general error",
"GSS_TSIG_NEW_KEY", "new GSS-TSIG key '%1' was created.",
"GSS_TSIG_NEW_KEY_SETUP_FAILED", "new GSS-TSIG key '%1' setup failed: %2.",
- "GSS_TSIG_NEW_KEY_SETUP_SUCCEED", "new GSS-TSIG key '%1' setup succeed.",
+ "GSS_TSIG_NEW_KEY_SETUP_SUCCEED", "new GSS-TSIG key '%1' setup succeeded.",
"GSS_TSIG_OLD_KEY_REMOVED", "%1 old GSS-TSIG keys were removed",
"GSS_TSIG_UNLOAD_OK", "GSS-TSIG hooks library unloaded successfully.",
- "GSS_TSIG_VERIFIED", "GSS-TSIG verify successed.",
+ "GSS_TSIG_VERIFIED", "GSS-TSIG verify succeeded.",
"GSS_TSIG_VERIFY_FAILED", "GSS-TSIG verify failed: %1.",
"KEY_LOOKUP_DISABLED", "hooks library lookup for a key: GSS-TSIG is not enabled for the current DNS server.",
"KEY_LOOKUP_FOUND", "hooks library lookup for a key: return GSS-TSIG key '%1'.",
% GSS_TSIG_VERIFIED GSS-TSIG verify succeeded.
Logged at debug log level 40.
-A debug message issued when GSS-TSIG verification succeeded.
+This debug message is issued when GSS-TSIG verification succeeded.
% GSS_TSIG_VERIFY_FAILED GSS-TSIG verify failed: %1.
This info message indicates that GSS-TSIG verification failed.
% TKEY_EXCHANGE_ANSWER_CLASS GSS-TKEY exchange received a response with answer class: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified answer class.
% TKEY_EXCHANGE_FAILED_TO_VERIFY GSS-TKEY exchange failed because the response failed to verify.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
failed to verify.
% TKEY_EXCHANGE_FAIL_EMPTY_IN_TOKEN GSS-TKEY exchange failed because input token is empty.
-This error message indicated that GSS-TKEY exchange failed because input token
+This error message indicates that the GSS-TKEY exchange failed because input token
is empty.
% TKEY_EXCHANGE_FAIL_EMPTY_OUT_TOKEN GSS-TKEY exchange failed because output token is empty.
-This error message indicated that GSS-TKEY exchange failed because output token
+This error message indicates that the GSS-TKEY exchange failed because output token
is empty.
% TKEY_EXCHANGE_FAIL_EMPTY_RESPONSE GSS-TKEY exchange failed because the response is empty.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is empty.
% TKEY_EXCHANGE_FAIL_IO_ERROR GSS-TKEY exchange failed because of the IO error: %1.
-This error message indicated that GSS-TKEY exchange failed because of an IO error.
+This error message indicates that the GSS-TKEY exchange failed because of an IO error.
The argument details the IO error.
% TKEY_EXCHANGE_FAIL_IO_STOPPED GSS-TKEY exchange failed because the IO service was stopped.
-This error message indicated that GSS-TKEY exchange failed because the IO
+This error message indicates that the GSS-TKEY exchange failed because the IO
service was stopped.
% TKEY_EXCHANGE_FAIL_IO_TIMEOUT GSS-TKEY exchange failed because of IO timeout.
-This error message indicated that GSS-TKEY exchange failed because of IO
+This error message indicates that the GSS-TKEY exchange failed because of IO
timeout.
% TKEY_EXCHANGE_FAIL_NOT_SIGNED GSS-TKEY exchange failed because the response is not signed.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is not signed.
% TKEY_EXCHANGE_FAIL_NO_RDATA GSS-TKEY exchange failed because the response contains no rdata.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains no rdata.
% TKEY_EXCHANGE_FAIL_NO_RESPONSE_ANSWER GSS-TKEY exchange failed because the response contains no answer.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains no answer.
% TKEY_EXCHANGE_FAIL_NULL_RESPONSE GSS-TKEY exchange failed because the response is null.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
is null.
% TKEY_EXCHANGE_FAIL_RESPONSE_ERROR GSS-TKEY exchange failed because the response contains an error: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains an error. The argument details the response error.
% TKEY_EXCHANGE_FAIL_TKEY_ERROR GSS-TKEY exchange failed because the response contains TKEY error: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains TKEY error. The argument details the TKEY error.
% TKEY_EXCHANGE_FAIL_TO_INIT GSS-TKEY exchange failed to initialize because of the error: %1.
-This error message indicated that GSS-TKEY exchange failed in the
+This error message indicates that the GSS-TKEY exchange failed in the
initialization phase, for instance because the server principal does not
exist. The argument details the error.
% TKEY_EXCHANGE_FAIL_WRONG_RESPONSE_ANSWER_COUNT GSS-TKEY exchange failed because the response contains invalid number of RRs: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains invalid number of RRs. The argument contains the wrong number of RRs.
% TKEY_EXCHANGE_FAIL_WRONG_RESPONSE_ANSWER_TYPE GSS-TKEY exchange failed because the response contains wrong answer type: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains wrong answer type. The argument contains the wrong answer type.
% TKEY_EXCHANGE_FAIL_WRONG_RESPONSE_OPCODE GSS-TKEY exchange failed because the response contains invalid opcode: %1.
-This error message indicated that GSS-TKEY exchange failed because the response
+This error message indicates that the GSS-TKEY exchange failed because the response
contains invalid opcode. The argument contains the wrong opcode.
% TKEY_EXCHANGE_NOT_A_RESPONSE GSS-TKEY exchange received a non response type.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a non response
+This debug message indicates that the GSS-TKEY exchange received a non response
type.
% TKEY_EXCHANGE_OUT_TOKEN_NOT_EMPTY GSS-TKEY exchange output token is not empty.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange output token is not empty.
+This debug message indicates that the GSS-TKEY exchange output token is not empty.
% TKEY_EXCHANGE_RDATA_COUNT GSS-TKEY exchange received a response with rdata count: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified rdata count.
% TKEY_EXCHANGE_RECEIVE_MESSAGE GSS-TKEY exchange receives a message of size: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange receives a message of
+This debug message indicates that the GSS-TKEY exchange receives a message of
specified size.
% TKEY_EXCHANGE_RESPONSE_TTL GSS-TKEY exchange received a response with TTL of: %1 seconds.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange received a response with
+This debug message indicates that the GSS-TKEY exchange received a response with
specified TTL.
% TKEY_EXCHANGE_SEND_MESSAGE GSS-TKEY exchange sends a message of size: %1.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange sends a message of specified
+This debug message indicates that the GSS-TKEY exchange sends a message of specified
size.
% TKEY_EXCHANGE_VALID GSS-TKEY exchange retrieved a TKEY valid for: %1 seconds.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange retrieved a TKEY valid for
+This debug message indicates that the GSS-TKEY exchange retrieved a TKEY valid for
the specified time period expressed in seconds.
% TKEY_EXCHANGE_VERIFIED GSS-TKEY exchange verified.
Logged at debug log level 40.
-This debug message indicates that GSS-TKEY exchange is verified.
+This debug message indicates that the GSS-TKEY exchange is verified.
% 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
+This debug message is 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_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
+This debug message is 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_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
+This debug message is 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.
% 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.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
% MYSQL_CB_UNREGISTER_BACKEND_TYPE4 unregister backend
% LEGAL_LOG_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
+This debug message is issued when the server is about to obtain schema version
information from the MySQL database.
% LEGAL_LOG_MYSQL_INSERT_LOG Adding a log entry to the database: %1
be rolled back and not committed to the database.
% LEGAL_LOG_MYSQL_START_TRANSACTION starting new MySQL transaction
-A debug message issued when a new MySQL transaction is being started.
+This debug message is issued when a new MySQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
% LEGAL_LOG_MYSQL_TLS_CIPHER TLS cipher: %1
Logged at debug log level 50.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
% MYSQL_FB_DB opening MySQL log database: %1
-This informational message is logged when a legal log hook library is
+This informational message is logged when the legal log hook library is
about to open a MySQL log database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
% MYSQL_HB_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
+This debug message is issued when the server is about to obtain schema version
information from the MySQL hosts database.
% MYSQL_HB_DB_READONLY MySQL host database opened for read access only
% MYSQL_HB_TLS_CIPHER TLS cipher: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
% MYSQL_LB_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
+This debug message is issued when the server is about to add an IPv4 lease
with the specified address to the MySQL backend database.
% MYSQL_LB_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
+This debug message is issued when the server is about to add an IPv6 lease
with the specified address to the MySQL backend database.
% MYSQL_LB_COMMIT committing to MySQL database
% MYSQL_LB_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
+This debug message is issued when the server has removed a number of reclaimed
leases from the database. The number of removed leases is included in the
message.
% MYSQL_LB_DELETED_SUBNET4_ID deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
% MYSQL_LB_DELETED_SUBNET6_ID deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
% MYSQL_LB_DELETE_ADDR4 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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the MySQL database for the specified address.
% MYSQL_LB_DELETE_ADDR6 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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the MySQL database for the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is removing reclaimed DHCPv4
leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% MYSQL_LB_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
+This debug message is issued when the server is removing reclaimed DHCPv6
leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% MYSQL_LB_GET4 obtaining all IPv4 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
+This debug message is issued when the server is attempting to obtain all IPv4
leases from the MySQL database.
% MYSQL_LB_GET6 obtaining all IPv6 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
+This debug message is issued when the server is attempting to obtain all IPv6
leases from the MySQL database.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the MySQL database for the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the MySQL database for the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database for a client with the specified
client identification.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the MySQL database for the specified duid.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain expired
IPv4 leases to reclaim them. The maximum number of leases to be retrieved
is logged in the message.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain expired
IPv6 leases to reclaim them. The maximum number of leases to be retrieved
is logged in the message.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database for a client with the specified
hostname.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database for a client with the specified
hostname.
% MYSQL_LB_GET_HWADDR4 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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database for a client with the specified
hardware address.
% MYSQL_LB_GET_HWADDR6 obtaining IPv6 leases for hardware address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database for a client with the specified
hardware address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set of IPv6
leases from the MySQL database for a client with the specified IAID (Identity
Association ID) and DUID (DHCP Unique Identifier).
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the MySQL database for a client with the specified IAID
(Identity Association ID), subnet ID and DUID (DHCP Unique Identifier).
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv4 leases beginning with the specified address with a relay id and client
transaction time between start and end dates.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a relay id.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv4 leases beginning with the specified address with a remote id and client
transaction time between start and end dates.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a remote id.
% MYSQL_LB_GET_STATE4 obtaining IPv4 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database with the specified state.
% MYSQL_LB_GET_STATE6 obtaining IPv6 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database with the specified state.
% MYSQL_LB_GET_STATE_SUBID4 obtaining IPv4 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the MySQL database with the specified state in
the specified subnet.
% MYSQL_LB_GET_STATE_SUBID6 obtaining IPv6 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the MySQL database with the specified state in
the specified subnet.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv4
leases for a given subnet identifier from the MySQL database.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv6
leases for a given subnet identifier from the MySQL database.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the MySQL database for a client with the specified subnet ID
and client ID.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the MySQL database for a client with the specified subnet ID
and hardware address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases from the MySQL database beginning with the specified address
for the specified subnet identifier.
% MYSQL_LB_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
+This debug message is issued when the server is about to obtain schema version
information from the MySQL database.
% MYSQL_LB_NEGATIVE_LEASES_STAT recount of leases returned a negative value
% MYSQL_LB_TLS_CIPHER TLS cipher: %1
Logged at debug log level 40.
-A debug message issued when a new MySQL connected is created with TLS.
+This debug message is issued when a new MySQL connected is created with TLS.
The TLS cipher name is logged.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to update IPv4
lease from the MySQL database for the specified address.
% MYSQL_LB_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
+This debug message is issued when the server is attempting to update IPv6
lease from the MySQL database for the specified address.
% MYSQL_LB_UPGRADE_EXTENDED_INFO4 upgrading IPv4 leases done in %1 pages with %2 updated leases
% MYSQL_LB_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.
+This debug message is issued when the server failed to upgrade an extended info.
The address of the lease and the error message are displayed.
% MYSQL_LB_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.
+This debug message is issued when the server upgrades IPv4 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
% MYSQL_LB_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
+This debug message is issued when the server failed to upgrade the extended info
for a lease. The address of the lease and the error message are displayed.
% MYSQL_LB_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.
+This debug message is issued when the server upgrades IPv6 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
is typically a network or database server issue.
% LEGAL_LOG_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL log database: %1
-This is an error message issued when a legal log hook library experienced
+This is an error message issued when the legal log hook library experienced
an error freeing database SQL resources as part of closing its connection to
the PostgreSQL database. The connection is closed as part of normal server
shutdown. This error is most likely a programmatic issue that is highly
% LEGAL_LOG_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
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL database.
% LEGAL_LOG_PGSQL_INSERT_LOG Adding a log entry to the database: %1
be rolled back and not committed to the database.
% LEGAL_LOG_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction
-A debug message issued when a new PostgreSQL transaction is being started.
+This debug message is issued when a new PostgreSQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
any of these INSERT statements fail.
% PGSQL_FB_DB opening PostgreSQL log database: %1
-This informational message is logged when a legal log hook library is
+This informational message is logged when the legal log hook library is
about to open a PostgreSQL log database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
% PGSQL_HB_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
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL hosts database.
% PGSQL_HB_DB_READONLY PostgreSQL host database opened for read access only
% PGSQL_LB_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
+This debug message is issued when the server is about to add an IPv4 lease
with the specified address to the PostgreSQL backend database.
% PGSQL_LB_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
+This debug message is issued when the server is about to add an IPv6 lease
with the specified address to the PostgreSQL backend database.
% PGSQL_LB_COMMIT committing to PostgreSQL database
% PGSQL_LB_DELETED_SUBNET4_ID deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
% PGSQL_LB_DELETED_SUBNET6_ID deleted %1 leases that match subnet ID %2.
Logged at debug log level 50.
-A debug message issued when the server is removing leases which match
+This debug message is issued when the server is removing leases which match
respective subnet ID.
% PGSQL_LB_DELETE_ADDR4 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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the PostgreSQL database for the specified address.
% PGSQL_LB_DELETE_ADDR6 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
+This debug message is issued when the server is attempting to delete a lease for
the specified address from the PostgreSQL database for the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is removing reclaimed DHCPv4
leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% PGSQL_LB_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
+This debug message is issued when the server is removing reclaimed DHCPv6
leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% PGSQL_LB_GET4 obtaining all IPv4 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv4
+This debug message is issued when the server is attempting to obtain all IPv4
leases from the PostgreSQL database.
% PGSQL_LB_GET6 obtaining all IPv6 leases
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain all IPv6
+This debug message is issued when the server is attempting to obtain all IPv6
leases from the PostgreSQL database.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the PostgreSQL database for the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the PostgreSQL database for the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database for a client with the specified
client identification.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set of IPv6
leases from the PostgreSQL database for a client with the specified DUID (DHCP Unique Identifier).
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain expired
IPv4 leases to reclaim them. The maximum number of leases to be retrieved
is logged in the message.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain expired
IPv6 leases to reclaim them. The maximum number of leases to be retrieved
is logged in the message.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database for a client with the specified
hostname.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database for a client with the specified
hostname.
% PGSQL_LB_GET_HWADDR4 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
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database for a client with the specified
hardware address.
% PGSQL_LB_GET_HWADDR6 obtaining IPv6 leases for hardware address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database for a client with the specified
hardware address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a set of IPv6
leases from the PostgreSQL database for a client with the specified IAID
(Identity Association ID) and DUID (DHCP Unique Identifier).
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv6
lease from the PostgreSQL database for a client with the specified IAID
(Identity Association ID), subnet ID and DUID (DHCP Unique Identifier).
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page
of leases beginning with the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv4 leases beginning with the specified address with a relay id and client
transaction time between start and end dates.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a relay id.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv4 leases beginning with the specified address with a remote id and client
transaction time between start and end dates.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases beginning with the specified address with a remote id.
% PGSQL_LB_GET_STATE4 obtaining IPv4 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database with the specified state.
% PGSQL_LB_GET_STATE6 obtaining IPv6 leases with state %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database with the specified state.
% PGSQL_LB_GET_STATE_SUBID4 obtaining IPv4 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv4 leases from the PostgreSQL database with the specified state in
the specified subnet.
% PGSQL_LB_GET_STATE_SUBID6 obtaining IPv6 leases with state %1 in subnet %2
Logged at debug log level 50.
-A debug message issued when the server is attempting to obtain a set
+This debug message is issued when the server is attempting to obtain a set
of IPv6 leases from the PostgreSQL database with the specified state in
the specified subnet.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv4
leases for a given subnet identifier from the PostgreSQL database.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain all IPv6
leases for a given subnet identifier from the PostgreSQL database.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the PostgreSQL database for a client with the specified subnet ID
and client ID.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain an IPv4
lease from the PostgreSQL database for a client with the specified subnet ID
and hardware address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to obtain a page of
IPv6 leases from the PostgreSQL database beginning with the specified address
for the specified subnet identifier.
% PGSQL_LB_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
+This debug message is issued when the server is about to obtain schema version
information from the PostgreSQL database.
% PGSQL_LB_NEGATIVE_LEASES_STAT recount of leases returned a negative value
% PGSQL_LB_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
+This debug message is issued when the server is attempting to update IPv4
lease from the PostgreSQL database for the specified address.
% PGSQL_LB_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
+This debug message is issued when the server is attempting to update IPv6
lease from the PostgreSQL database for the specified address.
% PGSQL_LB_UPGRADE_EXTENDED_INFO4 upgrading IPv4 leases done in %1 pages with %2 updated leases
% PGSQL_LB_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.
+This debug message is issued when the server failed to upgrade an extended info.
The address of the lease and the error message are displayed.
% PGSQL_LB_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.
+This debug message is issued when the server upgrades IPv4 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
% PGSQL_LB_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
+This debug message is issued when the server failed to upgrade the extended info
for a lease. The address of the lease and the error message are displayed.
% PGSQL_LB_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.
+This debug message is issued when the server upgrades IPv6 lease extended info.
The page number and started address, and the count of already updated leases
are displayed.
This error message is emitted when an unexpected error occurred while
attempting to resume operation of the ping channel's thread pool. This
error is highly unlikely and indicates a programmatic issue that should
-be reported as defect.
+be reported as a defect.
% PING_CHECK_UNEXPECTED_READ_ERROR could not start next socket read %1
This error message occurs when initiating an asynchronous read on the ICMP
"RADIUS_PAUSE_ILLEGAL", "Pausing the RADIUS thread pool not allowed: %1",
"RADIUS_PAUSE_PERMISSIONS_FAILED", "Checking for permissions to pause the RADIUS thread pool failed: %1",
"RADIUS_REPLY_MESSAGE_ATTRIBUTE", "Message %1 on exchange %2 has a Reply-Message attribute with value '%3'.",
- "RADIUS_RESUME_FAILED", "Resuming ithe RADIUS thread pool failed: %1",
+ "RADIUS_RESUME_FAILED", "Resuming the RADIUS thread pool failed: %1",
"RADIUS_SERVER_CONFIGURED", "configured an %1 server: %2",
"RADIUS_SESSION_HISTORY_APPEND_FAILED", "appending of a new record for %1 to the session history file failed: %2",
"RADIUS_SESSION_HISTORY_LOADED", "loading of the session history file succeeded: read %1 records including %2 active records",
% RADIUS_RESUME_FAILED Resuming the RADIUS thread pool failed: %1
This error message is emitted when an unexpected error occurred while attempting
to resume the thread pool. This error is highly unlikely and indicates a
-programmatic issue that should be reported as defect.
+programmatic issue that should be reported as a defect.
% RADIUS_SERVER_CONFIGURED configured an %1 server: %2
This informational message is issued when a RADIUS server is
to operate correctly.
% HTTP_COMMAND_MGR_HTTPS_SERVICE_REUSE_FAILED failed to reused HTTPS service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTPS service on the specified address and port. The server can not swith from
+This error message indicates that the server has failed to reuse existing
+HTTPS service on the specified address and port. The server cannot swith from
HTTPS to HTTP sockets using the same address and port.
% HTTP_COMMAND_MGR_HTTPS_SERVICE_UPDATED reused HTTPS service bound to address: %1 port: %2 and updated TLS settings
the TLS setup has been applied.
% HTTP_COMMAND_MGR_HTTP_SERVICE_REUSE_FAILED failed to reused HTTP service bound to address: %1 port: %2
-This error message indicates that the server has failed reusing existing
-HTTP service on the specified address and port. The server can not swith from
+This error message indicates that the server has failed to reuse existing
+HTTP service on the specified address and port. The server cannot swith from
HTTP to HTTPS sockets using the same address and port.
% HTTP_COMMAND_MGR_HTTP_SERVICE_UPDATED reused HTTP service bound to address: %1 port: %2
% 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 loop
+event loop.
% DHCP_DDNS_SECURITY_CHECKS_DISABLED Invoked with command line option -X, Security checks are disabled!!
This warning is emitted when internal security checks normally
be rolled back and not committed to the database.
% DATABASE_MYSQL_START_TRANSACTION starting new MySQL transaction
-A debug message issued when a new MySQL transaction is being started.
+This debug message is issued when a new MySQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
and not committed to the database.
% DATABASE_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction
-A debug message issued when a new PostgreSQL transaction is being started.
+This debug message is issued when a new PostgreSQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
pools require packet to belong to certain classes and the incoming packet
didn't belong to any of them. Another case where this information may be
useful is to point out that the pool reserved to a given class has run
-out of addresses. When you see this message, you may consider checking your
-pool size and your classification definitions.
+out of addresses. If this message is displayed, consider checking the
+pool size and the classification definitions.
% ALLOC_ENGINE_V4_ALLOC_FAIL_NO_POOLS %1: no pools were available for the address allocation
This warning message is issued when the allocation engine fails to
pools require packet to belong to certain classes and the incoming packet
didn't belong to any of them. Another case where this information may be
useful is to point out that the pool reserved to a given class has run
-out of addresses. When you see this message, you may consider checking your
-pool size and your classification definitions.
+out of addresses. If this message is displayed, you may consider checking the
+pool size and the classification definitions.
% ALLOC_ENGINE_V6_ALLOC_FAIL_NO_POOLS %1: no pools were available for the lease allocation
This warning message is issued when the allocation engine fails to
% 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 of
-allocating leases for the client, there are no static reservations,
+allocating leases for the client and there are no static reservations,
but lease(s) exist for the client. The allocation engine will remove
leases which are reserved for other clients, and return all
remaining leases to the client.
% 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
+This debug message is 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.
+This debug message is issued when the server's DHCP-DDNS settings are changed.
% DHCPSRV_CFGMGR_CONFIG4_MERGED Configuration backend data has been merged.
This is an informational message emitted when the DHCPv4 server has
% DHCPSRV_DDNS_TTL_TOO_LARGE %1 of lease life time %2 is %3, using maximum of %4 instead.
Logged at debug log level 55.
-A debug message issued when the DDNS TTL value calculated using the
+This debug message is issued when the DDNS TTL value calculated using the
ddns-ttl-percent if specified or (0.33 if not) is larger than the
the specified value of ddns-ttl-max. Kea will ignore the value and
use the specified maximum instead. The message details include
% DHCPSRV_DDNS_TTL_TOO_SMALL %1 of lease life time %2 is %3, using minimum of %4 instead.
Logged at debug log level 55.
-A debug message issued when the DDNS TTL value calculated using the
+This debug message is issued when the DDNS TTL value calculated using the
ddns-ttl-percent if specified or (0.33 if not) is too small. Kea will
ignore the value and use the minimum (ddns-ttl-min if specified or 600
seconds if not). The message details include the percentage, the lease
% 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
+This debug message is issued when a NameChangeRequest has been successfully sent to
kea-dhcp-ddns.
% DHCPSRV_DHCP_DDNS_SENDER_STARTED NameChangeRequest sender has been started: %1
% 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
+This debug message is 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
+This debug message is 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.
+This debug message is 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.
+This debug message is issued when the server is extracting extended info.
The extended info sanity check level and update in file when requested
are displayed.
% DHCPSRV_MEMFILE_DELETE_ADDR4 deleting lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to delete a lease
+This debug message is issued when the server is attempting to delete a lease
for the specified address from the memory file database for the specified
address.
% DHCPSRV_MEMFILE_DELETE_ADDR6 deleting lease for address %1
Logged at debug log level 50.
-A debug message issued when the server is attempting to delete a lease
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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_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
+This debug message is issued when the server is extracting extended info and
receives an exception processing a lease.
% DHCPSRV_MEMFILE_FAILED_TO_OPEN Could not open lease file: %1
% 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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_HWADDR4 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
+This debug message is 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_HWADDR6 obtaining IPv6 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
+This debug message is issued when the server is attempting to obtain a set of
IPv6 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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.
% 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.
+This debug message is issued when DHCP lease is being loaded from the file to memory.
% DHCPSRV_MEMFILE_LEASE_LOAD_ROW_ERROR discarding row %1, error: %2
An error message issued if the DHCP lease being loaded from the given row of
% 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
+This debug message is 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
+This debug message is issued when the server is attempting to update IPv6
lease from the memory file database for the specified address.
% DHCPSRV_MEMFILE_WIPE_LEASES4 removing all IPv4 leases from subnet %1
% 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is 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 could not find a suitable address to use for
+This debug message is issued when the server could not 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
+This debug message is 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
+This debug message is 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
+This debug message is issued when the server was unable to select a subnet using
the specified interface name.
% DHCPSRV_TEMPLATE_EVAL_ERROR %1: Expression '%2' evaluated to %3
% 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
+This debug message is issued when the new interval timer is registered in
the Timer Manager. This timer will have a callback function
associated with it, and this function will be executed according
to the interval specified. The unique name of the timer and the
% 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
+This debug message is issued when the Timer Manager is about to
run a periodic operation associated with the given timer.
An example of such operation is a periodic cleanup of
expired leases. The name of the timer is included in the
% DHCPSRV_TIMERMGR_START_TIMER starting timer: %1
Logged at debug log level 40.
-A debug message issued when the registered interval timer is
+This debug message is 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
+This debug message is 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
+This debug message is 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
+This debug message is issued when one of the registered interval timers
is unregistered from the Timer Manager. The name of the timer is
included in the message.
auto tmpname = tmp.str();
::remove(tmpname.c_str());
- // Dump in memory leases to temp file.
+ // Dump in-memory leases to temp file.
try {
CSVLeaseFile4 tmpfile(tmpname);
tmpfile.open();
auto tmpname = tmp.str();
::remove(tmpname.c_str());
- // Dump in memory leases to temp file.
+ // Dump in-memory leases to temp file.
try {
CSVLeaseFile6 tmpfile(tmpname);
tmpfile.open();
}
// This test is sort of BS. How does an updated lease move to
-// a new subnet without changing lease address, other than
-// if the lease is being manually fixed after config change
-// altered subnets and pool.
+// a new subnet without changing the lease address, other than
+// by the lease being manually fixed after a config change
+// altered subnets and pool?
void
GenericLeaseMgrTest::testUpdateStatsOn4DifferentSubnet() {
// Create two subnets.
% 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. They are then combined via logical and and
+the value stack. They are then combined via logical "and" and
the result is pushed onto the value stack.
# For use with TokenBranch
% 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. They are then combined via logical or and
+the value stack. They are then combined via logical "or" and
the result is pushed onto the value stack. The string is displayed
in text.
% 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
+This debug message is 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_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
+This debug message is issued when all instances of a particular callouts on
the hook identified in the message that were registered by the library
with the given index have been removed.
% HOOKS_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
+This debug message is issued when the "multi_threading_compatible" function was
called. The returned value (0 means not compatible, others compatible)
is displayed.
projects / thirdparty / kea.git / commitdiff
