mir/kea
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/kea synced 2025-08-31 05:55:28 +00:00
Code Issues Releases Wiki Activity

[#1723] remove unlogged message definitions

Browse Source
This commit is contained in:
Andrei Pavel
2024-06-26 15:59:48 +03:00
parent 909676bdcd
commit cd41c2e2cb
12 changed files with 0 additions and 439 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
src/bin/dhcp4/dhcp4_messages.mes
View File

@@ -6,11 +6,6 @@
$NAMESPACE isc::dhcp
% DHCP4_ACTIVATE_INTERFACE activating interface %1
This message is printed when DHCPv4 server enabled an interface to be used
to receive DHCPv4 traffic. IPv4 socket on this interface will be opened once
Interface Manager starts up procedure of opening sockets.
% DHCP4_ALREADY_RUNNING %1 already running? %2
This is an error message that occurs when the DHCPv4 server encounters
a pre-existing PID file which contains the PID of a running process.
@@ -171,25 +166,12 @@ new configuration. It is output during server startup, and when an updated
configuration is committed by the administrator. Additional information
may be provided.
% DHCP4_CONFIG_FETCH Fetching configuration data from config backends.
This is an informational message emitted when the DHCPv4 server about to begin
retrieving configuration data from one or more configuration backends.
% DHCP4_CONFIG_LOAD_FAIL configuration error using file: %1, reason: %2
This error message indicates that the DHCPv4 configuration has failed.
If this is an initial configuration (during server's startup) the server
will fail to start. If this is a dynamic reconfiguration attempt the
server will continue to use an old configuration.
% DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1
This is an informational message reporting that the configuration has
been extended to include the specified IPv4 subnet.
% DHCP4_CONFIG_OPTION_DUPLICATE multiple options with the code %1 added to the subnet %2
This warning message is issued on an attempt to configure multiple options
with the same option code for a particular subnet. Adding multiple options
is uncommon for DHCPv4, but is not prohibited.
% DHCP4_CONFIG_PACKET_QUEUE DHCPv4 packet queue info after configuration: %1
This informational message is emitted during DHCPv4 server configuration,
immediately after configuring the DHCPv4 packet queue. The information
@@ -224,10 +206,6 @@ issued). Finally, the server could be restarted completely.
This error message is issued when the configuration includes an unsupported
object (i.e. a top level element).
% DHCP4_CONFIG_UPDATE updated configuration received: %1
A debug message indicating that the DHCPv4 server has received an
updated configuration from the Kea configuration system.
% DHCP4_DB_RECONNECT_DISABLED database reconnect is disabled: max-reconnect-tries %1, reconnect-wait-time %2
This is an informational message indicating that connectivity to either the
lease or host database or both and that automatic reconnect is not enabled.
@@ -259,11 +237,6 @@ This error message indicates that DHCP4 server attempted to send a DDNS
update request to the DHCP-DDNS server. This is most likely a configuration or
networking error.
% DHCP4_DEACTIVATE_INTERFACE deactivate interface %1
This message is printed when DHCPv4 server disables an interface from being
used to receive DHCPv4 traffic. Sockets on this interface will not be opened
by the Interface Manager until interface is enabled.
% DHCP4_DECLINE_FAIL %1: error on decline lease for address %2: %3
This error message indicates that the software failed to decline a
lease from the lease database due to an error during a database
@@ -435,10 +408,6 @@ This debug message is issued when the server did not receive a Hostname option
from the client and hostname generation is enabled. This provides a means to
create DNS entries for unsophisticated clients.
% DHCP4_HANDLE_SIGNAL_EXCEPTION An exception was thrown while handing signal: %1
This error message is printed when an ISC or standard exception was raised during signal
processing. This likely indicates a coding error and should be reported to ISC.
% DHCP4_HOOK_BUFFER_RCVD_DROP received buffer from %1 to %2 over interface %3 was dropped because a callout set the drop flag
Logged at debug log level 15.
This debug message is printed when a callout installed on buffer4_receive
@@ -654,16 +623,6 @@ respond. The first argument includes the client and the transaction id
identification information. The second argument includes the IPv4 address
requested by the client.
% DHCP4_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
This warning message is issued when current server configuration specifies
no interfaces that server should listen on, or specified interfaces are not
configured to receive the traffic.
% DHCP4_OPEN_CONFIG_DB Opening configuration database: %1
This message is printed when the DHCPv4 server is attempting to open a
configuration database. The database access string with password redacted
is logged.
% DHCP4_OPEN_SOCKET opening service sockets on port %1
Logged at debug log level 0.
A debug message issued during startup, this indicates that the DHCPv4
@@ -679,10 +638,6 @@ This is an error message indicating a programmatic error that should not occur.
It prohibits the server from attempting to bind to its service sockets if they
are unavailable, and the server exits. This error should be reported.
% DHCP4_OPEN_SOCKET_FAIL failed to open socket: %1
A warning message issued when IfaceMgr fails to open and bind a socket. The reason
for the failure is appended as an argument of the log message.
% DHCP4_PACKET_DROP_0001 %1: failed to parse packet from %2 to %3, received over interface %4, reason: %5, %6
Logged at debug log level 15.
The DHCPv4 server has received a packet that it is unable to
@@ -824,11 +779,6 @@ A debug message issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
server will still attempt to service the packet.
% DHCP4_PACKET_OPTION_UNPACK_FAIL An error unpacking the option %1: %2
A debug message issued when an option failed to unpack correctly, making it
to be left unpacked in the packet. The first argument is the option code,
the second the error.
% DHCP4_PACKET_PACK %1: preparing on-wire format of the packet to be sent
Logged at debug log level 50.
This debug message is issued when the server starts preparing the on-wire
@@ -1093,14 +1043,6 @@ the lease store. The first argument includes the client and the transaction
identification information. The second argument holds the IPv4 address for which
the decline was attempted.
% DHCP4_SERVER_INITIATED_DECLINE_FAILED %1: error on server-initiated decline lease for address %2: %3
This error message indicates that the software failed to decline a
lease from the lease database due to an error during a database
operation. The first argument includes the client and the transaction
identification information. The second argument holds the IPv4 address
for which the decline was attempted. The last one contains the reason of
failure.
% DHCP4_SERVER_INITIATED_DECLINE_RESOURCE_BUSY %1: error declining a lease for address %2
This error message indicates that while one server thread was attempting to mark
a lease as DECLINED, it was already locked by another thread. The first argument

45
src/bin/dhcp6/dhcp6_messages.mes
View File

@@ -15,11 +15,6 @@ kea-dhcp4 is using hook libraries (e.g. radius) that implement the
"subnet6_select" callout and client queries are arriving faster than
those callouts can fulfill them.
% DHCP6_ACTIVATE_INTERFACE activating interface %1
This message is printed when DHCPv6 server enabled an interface to be used
to receive DHCPv6 traffic. IPv6 socket on this interface will be opened once
Interface Manager starts up procedure of opening sockets.
% DHCP6_ADD_GLOBAL_STATUS_CODE %1: adding Status Code to DHCPv6 packet: %2
Logged at debug log level 50.
This message is logged when the server is adding the top-level
@@ -173,15 +168,6 @@ issued). Finally, the server could be restarted completely.
This error message is issued when the configuration includes an unsupported
object (i.e. a top level element).
% DHCP6_CONFIG_UPDATE updated configuration received: %1
A debug message indicating that the IPv6 DHCP server has received an
updated configuration from the Kea configuration system.
% DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2)
This informational message is printed every time the IPv6 DHCP server
is started. It indicates what database backend type is being to store
lease and other information.
% DHCP6_DB_RECONNECT_DISABLED database reconnect is disabled: max-reconnect-tries %1, reconnect-wait-time %2
This is an informational message indicating that connectivity to either the
lease or host database or both and that automatic reconnect is not enabled.
@@ -268,15 +254,6 @@ includes the details of the FQDN option being included. Note that the
name carried in the FQDN option may be modified by the server when
the lease is acquired for the client.
% DHCP6_DDNS_SEND_FQDN sending DHCPv6 Client FQDN Option to the client: %1
This debug message is logged when server includes an DHCPv6 Client FQDN Option
in its response to the client.
% DHCP6_DEACTIVATE_INTERFACE deactivate interface %1
This message is printed when DHCPv6 server disables an interface from being
used to receive DHCPv6 traffic. Sockets on this interface will not be opened
by the Interface Manager until interface is enabled.
% DHCP6_DECLINE_FAIL %1: error on decline lease for address %2: %3
This error message indicates that the software failed to decline a
lease from the lease database due to an error during a database
@@ -381,10 +358,6 @@ and the expression specified in its configuration generated (was evaluated to)
an identifier for incoming packet. This debug message is mainly intended as a
debugging assistance for flexible identifier.
% DHCP6_HANDLE_SIGNAL_EXCEPTION An exception was thrown while handing signal: %1
This error message is printed when an exception was raised during signal
processing. This likely indicates a coding error and should be reported to ISC.
% DHCP6_HOOK_BUFFER_RCVD_DROP received buffer from %1 to %2 over interface %3 was dropped because a callout set the drop flag
Logged at debug log level 15.
This debug message is printed when a callout installed on buffer6_receive
@@ -618,11 +591,6 @@ IPv6 DHCP server but it is not running.
During startup the IPv6 DHCP server failed to detect any network
interfaces and is therefore shutting down.
% DHCP6_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
This warning message is issued when current server configuration specifies
no interfaces that server should listen on, or specified interfaces are not
configured to receive the traffic.
% DHCP6_OPEN_SOCKET opening service sockets on port %1
Logged at debug log level 0.
A debug message issued during startup, this indicates that the IPv6 DHCP
@@ -638,10 +606,6 @@ This is an error message indicating a programmatic error that should not occur.
It prohibits the server from attempting to bind to its service sockets if they
are unavailable, and the server exits. This error should be reported.
% DHCP6_OPEN_SOCKET_FAIL failed to open socket: %1
A warning message issued when IfaceMgr fails to open and bind a socket. The reason
for the failure is appended as an argument of the log message.
% DHCP6_PACKET_DROP_DHCP_DISABLED %1: DHCP service is globally disabled
Logged at debug log level 15.
This debug message is issued when a packet is dropped because the DHCP service
@@ -1053,9 +1017,6 @@ This debug message indicates that a shutdown of the IPv6 server has
been requested via a call to the 'shutdown' method of the core Dhcpv6Srv
object.
% DHCP6_SOCKET_UNICAST server is about to open socket on address %1 on interface %2
This is a debug message that inform that a unicast socket will be opened.
% DHCP6_SRV_CONSTRUCT_ERROR error creating Dhcpv6Srv object, reason: %1
This error message indicates that during startup, the construction of a
core component within the IPv6 DHCP server (the Dhcpv6 server object)
@@ -1075,12 +1036,6 @@ a programmatic error in the server code. If it is not empty it could be
a programmatic error in one of the hooks libraries which could lead to
a crash during finalization.
% DHCP6_STANDALONE skipping message queue, running standalone
This is a debug message indicating that the IPv6 server is running in
standalone mode, not connected to the message queue. Standalone mode
is only useful during program development, and should not be used in a
production environment.
% DHCP6_STARTED Kea DHCPv6 server version %1 started
This informational message indicates that the IPv6 DHCP server has
processed all configuration information and is ready to process

4
src/bin/netconf/netconf_messages.mes
View File

@@ -54,10 +54,6 @@ name of the server and the error are printed.
This informational message indicates that kea-netconf is trying to get the
configuration from a Kea server.
% NETCONF_LOG_CHANGE_FAIL NETCONF configuration change logging failed: %1
The warning message indicates that the configuration change logging
encountered an unexpected condition. Details of it will be logged.
% NETCONF_MODULE_CHANGE_INTERNAL_ERROR an internal error occurred while processing changes for module %1: %2
The error message indicates that kea-netconf got an error while sysrepo was processing modules changes.
This usually follows a config validation failure, and can be recovered from.

10
src/hooks/dhcp/lease_cmds/lease_cmds_messages.mes
View File

@@ -37,11 +37,6 @@ addresses is logged.
The lease6-bulk-apply command has failed. Both the reason as well
as the parameters passed are logged.
% LEASE_CMDS_DEINIT_FAILED unloading Lease Commands hooks library failed: %1
This error message indicates an error during unloading the Lease Commands
hooks library. The details of the error are provided as argument of
the log message.
% LEASE_CMDS_DEINIT_OK unloading Lease Commands hooks library successful
This info message indicates that the Lease Commands hooks library has been
removed successfully.
@@ -72,11 +67,6 @@ parameters passed are logged.
The lease4-get command has failed. Both the reason as well as the
parameters passed are logged.
% LEASE_CMDS_INIT_FAILED loading Lease Commands hooks library failed: %1
This error message indicates an error during loading the Lease Commands
hooks library. The details of the error are provided as argument of
the log message.
% LEASE_CMDS_INIT_OK loading Lease Commands hooks library successful
This info message indicates that the Lease Commands hooks library has been
loaded successfully. Enjoy!

5
src/hooks/dhcp/perfmon/perfmon_messages.mes
View File

@@ -35,11 +35,6 @@ This info log is issued when perfmon-get-all-durations command has
completed successfully. The argument contains the number of
durations returned.
% PERFMON_DEINIT_FAILED unloading PerfMon hooks library failed: %1
This error message indicates an error unloading the PerfMon hooks
library. The details of the error are provided as argument of
the log message.
% PERFMON_DEINIT_OK unloading PerfMon hooks library successful
This info message indicates that the PerfMon hooks library has been
removed successfully.

10
src/hooks/dhcp/stat_cmds/stat_cmds_messages.mes
View File

@@ -1,19 +1,9 @@
# Copyright (C) 2018-2024 Internet Systems Consortium, Inc. ("ISC")
% STAT_CMDS_DEINIT_FAILED unloading Stat Commands hooks library failed: %1
This error message indicates an error during unloading the Lease Commands
hooks library. The details of the error are provided as argument of
the log message.
% STAT_CMDS_DEINIT_OK unloading Stat Commands hooks library successful
This info message indicates that the Stat Commands hooks library has been
removed successfully.
% STAT_CMDS_INIT_FAILED loading Stat Commands hooks library failed: %1
This error message indicates an error during loading the Lease Commands
hooks library. The details of the error are provided as argument of
the log message.
% STAT_CMDS_INIT_OK loading Stat Commands hooks library successful
This info message indicates that the Stat Commands hooks library has been
loaded successfully. Enjoy!

119
src/lib/asiodns/asiodns_messages.mes
View File

@@ -6,14 +6,6 @@
$NAMESPACE isc::asiodns
% ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1
A debug message informing about installing a file descriptor as a server.
The file descriptor number is noted.
% ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1
A debug message informing about installing a file descriptor as a server.
The file descriptor number is noted.
% ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed
Logged at debug log level 70.
A debug message, this records that the upstream fetch (a query made by the
@@ -48,117 +40,6 @@ The asynchronous I/O code encountered an error when trying to send data to
the specified address on the given protocol. The number of the system
error that caused the problem is given in the message.
% ASIODNS_SYNC_UDP_CLOSE_FAIL failed to close a DNS/UDP socket: %1
This is the same to ASIODNS_UDP_CLOSE_FAIL but happens on the
"synchronous UDP server", mainly used for the authoritative DNS server
daemon.
% ASIODNS_TCP_ACCEPT_FAIL failed to accept TCP DNS connection: %1
Accepting a TCP connection from a DNS client failed due to an error
that could happen but should be rare. The reason for the error is
included in the log message. The server still keeps accepting new
connections, so unless it happens often it's probably okay to ignore
this error. If the shown error indicates something like "too many
open files", it's probably because the run time environment is too
restrictive on this limitation, so consider adjusting the limit using
a tool such as ulimit. If you see other types of errors too often,
there may be something overlooked; please file a bug report in that case.
% ASIODNS_TCP_CLEANUP_CLOSE_FAIL failed to close a DNS/TCP socket on port cleanup: %1
A TCP DNS server tried to close a TCP socket (one created on accepting
a new connection or is already unused) as a step of cleaning up the
corresponding listening port, but it failed to do that. This is
generally an unexpected event and so is logged as an error.
See also the description of ASIODNS_TCP_CLOSE_ACCEPTOR_FAIL.
% ASIODNS_TCP_CLOSE_ACCEPTOR_FAIL failed to close listening TCP socket: %1
A TCP DNS server tried to close a listening TCP socket (for accepting
new connections) as a step of cleaning up the corresponding listening
port (e.g., on server shutdown or updating port configuration), but it
failed to do that. This is generally an unexpected event and so is
logged as an error. See ASIODNS_TCP_CLOSE_FAIL on the implication of
related system resources.
% ASIODNS_TCP_CLOSE_FAIL failed to close DNS/TCP socket with a client: %1
A TCP DNS server tried to close a TCP socket used to communicate with
a client, but it failed to do that. While closing a socket should
normally be an error-free operation, there have been known cases where
this happened with a "connection reset by peer" error. This might be
because of some odd client behavior, such as sending a TCP RST after
establishing the connection and before the server closes the socket,
but how exactly this could happen seems to be system dependent (i.e,
it's not part of the standard socket API), so it's difficult to
provide a general explanation. In any case, it is believed that an
error on closing a socket doesn't mean leaking system resources (the
kernel should clean up any internal resource related to the socket,
just reporting an error detected in the close call), but, again, it
seems to be system dependent. This message is logged at a debug level
as it's known to happen and could be triggered by a remote node and it
would be better to not be too verbose, but you might want to increase
the log level and make sure there's no resource leak or other system
level troubles when it's logged.
% ASIODNS_TCP_CLOSE_NORESP_FAIL failed to close DNS/TCP socket with a client: %1
A TCP DNS server tried to close a TCP socket used to communicate with
a client without returning an answer (which normally happens for zone
transfer requests), but it failed to do that. See ASIODNS_TCP_CLOSE_FAIL
for more details.
% ASIODNS_TCP_GETREMOTE_FAIL failed to get remote address of a DNS TCP connection: %1
A TCP DNS server tried to get the address and port of a remote client
on a connected socket but failed. It's expected to be rare but can
still happen. See also ASIODNS_TCP_READLEN_FAIL.
% ASIODNS_TCP_READDATA_FAIL failed to get DNS data on a TCP socket: %1
A TCP DNS server tried to read a DNS message (that follows a 2-byte
length field) but failed. It's expected to be rare but can still happen.
See also ASIODNS_TCP_READLEN_FAIL.
% ASIODNS_TCP_READLEN_FAIL failed to get DNS data length on a TCP socket: %1
A TCP DNS server tried to get the length field of a DNS message (the first
2 bytes of a new chunk of data) but failed. This is generally expected to
be rare but can still happen, e.g, due to an unexpected reset of the
connection. A specific reason for the failure is included in the log
message.
% ASIODNS_TCP_WRITE_FAIL failed to send DNS message over a TCP socket: %1
A TCP DNS server tried to send a DNS message to a remote client but
failed. It's expected to be rare but can still happen. See also
ASIODNS_TCP_READLEN_FAIL.
% ASIODNS_UDP_ASYNC_SEND_FAIL Error sending UDP packet to %1: %2
The low-level ASIO library reported an error when trying to send a UDP
packet in asynchronous UDP mode. This can be any error reported by
send_to(), and can indicate problems such as too high a load on the network,
or a problem in the underlying library or system.
This packet is dropped and will not be sent, but service should resume
normally.
If you see a single occurrence of this message, it probably does not
indicate any significant problem, but if it is logged often, it is probably
a good idea to inspect your network traffic.
% ASIODNS_UDP_CLOSE_FAIL failed to close a DNS/UDP socket: %1
A UDP DNS server tried to close its UDP socket, but failed to do that.
This is generally an unexpected event and so is logged as an error.
% ASIODNS_UDP_RECEIVE_FAIL failed to receive UDP DNS packet: %1
Receiving a UDP packet from a DNS client failed due to an error that
could happen but should be very rare. The server still keeps
receiving UDP packets on this socket. The reason for the error is
included in the log message. This log message is basically not
expected to appear at all in practice; if it does, there may be some
system level failure and other system logs may have to be checked.
% ASIODNS_UDP_SYNC_RECEIVE_FAIL failed to receive UDP DNS packet: %1
This is the same to ASIODNS_UDP_RECEIVE_FAIL but happens on the
"synchronous UDP server", mainly used for the authoritative DNS server
daemon.
% ASIODNS_UDP_SYNC_SEND_FAIL Error sending UDP packet to %1: %2
The low-level ASIO library reported an error when trying to send a UDP
packet in synchronous UDP mode. See ASIODNS_UDP_ASYNC_SEND_FAIL for
more information.
% ASIODNS_UNKNOWN_ORIGIN unknown origin for ASIO error code %1 (protocol: %2, address %3)
An internal consistency check on the origin of a message from the
asynchronous I/O module failed. This may indicate an internal error;

18
src/lib/d2srv/d2_messages.mes
View File

@@ -15,16 +15,6 @@ documented in preceding log entries.
This is an informational message issued after DHCP_DDNS has submitted DNS
mapping additions which were received and accepted by an appropriate DNS server.
% DHCP_DDNS_ALREADY_RUNNING %1 already running? %2
This is an error message that occurs when DHCP_DDNS encounters a pre-existing
PID file which contains the PID of a running process. This most likely
indicates an attempt to start a second instance of DHCP_DDNS using the
same configuration file. It is possible, though unlikely, that the PID file
is a remnant left behind by a server crash or power failure and the PID
it contains refers to a process other than DHCP_DDNS. In such an event,
it would be necessary to manually remove the PID file. The first argument is
the DHCP_DDNS process name, the second contains the PID and PID file.
% DHCP_DDNS_AT_MAX_TRANSACTIONS application has %1 queued requests but has reached maximum number of %2 concurrent transactions
Logged at debug log level 55.
This is a debug message that indicates that the application has DHCP_DDNS
@@ -35,10 +25,6 @@ Logged at debug log level 0.
This is a debug message issued when the application has been instructed
to shutdown and has met the required criteria to exit.
% DHCP_DDNS_COMMAND command directive received, command: %1 - args: %2
This is a debug message issued when the DHCP-DDNS application command method
has been invoked.
% DHCP_DDNS_CONFIGURE configuration %1 received: %2
Logged at debug log level 40.
This is a debug message issued when the DHCP-DDNS application configure method
@@ -250,10 +236,6 @@ no configured DDNS domains in the DHCP_DDNS configuration. Either the DHCP_DDNS
configuration needs to be updated or the source of the FQDN itself should be
investigated.
% DHCP_DDNS_PROCESS_INIT application init invoked
This is a debug message issued when the DHCP-DDNS application enters
its initialization method.
% DHCP_DDNS_QUEUE_MGR_QUEUE_FULL application request queue has reached maximum number of entries %1
This an error message indicating that DHCP-DDNS is receiving DNS update
requests faster than they can be processed. This may mean the maximum queue

15
src/lib/dhcpsrv/alloc_engine_messages.mes
View File

@@ -25,14 +25,6 @@ Logged at debug log level 40.
This debug message is logged when the allocation engine successfully
reclaims a lease. The lease is now available for assignment.
% ALLOC_ENGINE_REMOVAL_NCR_FAILED sending removal name change request failed for lease %1: %2
This error message is logged when sending a removal NameChangeRequest
to DHCP DDNS failed. This NameChangeRequest is usually generated when
the lease reclamation routine acts upon expired leases. If a lease being
reclaimed has a corresponding DNS entry it needs to be removed.
This message indicates that removal of the DNS entry has failed.
Nevertheless the lease will be reclaimed.
% ALLOC_ENGINE_V4_ALLOC_ERROR %1: error during attempt to allocate an IPv4 address: %2
An error occurred during an attempt to allocate an IPv4 address, the
reason for the failure being contained in the message. The server will
@@ -621,13 +613,6 @@ client. If they are, they will not be renewed for the client
requesting their renewal. The first argument includes the client
identification information.
% ALLOC_ENGINE_V6_RENEW_REMOVE_UNRESERVED dynamically allocating leases for the renewing client %1
This debug message is issued as the allocation engine is trying
to dynamically allocate new leases for the renewing client. This
is the case when the server couldn't renew any of the existing
client's leases, e.g. because leased resources are reserved for
another client.
% ALLOC_ENGINE_V6_REUSE_EXPIRED_LEASE_DATA %1: reusing expired lease, updated lease information: %2
Logged at debug log level 55.
This message is logged when the allocation engine is reusing

111
src/lib/dhcpsrv/dhcpsrv_messages.mes
View File

@@ -29,12 +29,6 @@ interfaces.
Logged at debug log level 40.
A debug message issued when the server's DHCP-DDNS settings are changed.
% DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces
A debug message issued when configuration manager clears the internal list
of active interfaces. This doesn't prevent the server from listening to
the DHCP traffic through open sockets, but will rather be used by Interface
Manager to select active interfaces when sockets are re-opened.
% DHCPSRV_CFGMGR_CONFIG4_MERGED Configuration backend data has been merged.
This is an informational message emitted when the DHCPv4 server has
successfully merged configuration data retrieved from its configuration
@@ -58,25 +52,6 @@ there is a good reason for it, to avoid increased number of renewals and
a need for rebinding (increase of multicast traffic, which may be received
by multiple servers).
% DHCPSRV_CFGMGR_DDNS_PARAMETER_IGNORED dhcp-ddns:%1 is deprecated, using existing global:%2
This is an informational message issued during configuration parsing when
the server detects that a deprecated parameter has been specified in the
"dhcp-ddns" element which conflicts with its corresponding global parameter.
When this occurs the server simply ignores the value from dhcp-ddns.
The log message shows be the deprecated and the supported parameter names.
Note the configuration change only affects the in-memory configuration.
Modify the configuration to comply with the supported parameters.
% DHCPSRV_CFGMGR_DDNS_PARAMETER_MOVED dhcp-ddns:%1 is deprecated, moving it to global:%2
This is an informational message issued during configuration parsing when
the server detects that a deprecated parameter has been specified in the
"dhcp-ddns" element for which no corresponding global value exists. When
this occurs, the server removes the parameter from dhcp-ddns and inserts the
parameter into the global scope. The log message shows the deprecated
and the supported parameter names. Note the configuration change only affects
the in-memory configuration. Modify the configuration to comply with
the supported parameters.
% DHCPSRV_CFGMGR_DEL_SUBNET4 IPv4 subnet %1 removed
Logged at debug log level 40.
This debug message is issued when a subnet is successfully removed from the
@@ -149,26 +124,6 @@ been extended to include the specified IPv4 subnet.
This is an informational message reporting that the configuration has
been extended to include the specified subnet.
% DHCPSRV_CFGMGR_NO_SUBNET4 no suitable subnet is defined for address hint %1
This debug message is output when the DHCP configuration manager has received
a request for an IPv4 subnet for the specified address, but no such
subnet exists.
% DHCPSRV_CFGMGR_NO_SUBNET6 no suitable subnet is defined for address hint %1
This debug message is output when the DHCP configuration manager has received
a request for an IPv6 subnet for the specified address, but no such
subnet exists.
% DHCPSRV_CFGMGR_ONLY_SUBNET4 retrieved subnet %1 for address hint %2
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv4 subnet when given the address hint specified
because it is the only subnet defined.
% DHCPSRV_CFGMGR_ONLY_SUBNET6 retrieved subnet %1 for address hint %2
This is a debug message reporting that the DHCP configuration manager has
returned the specified IPv6 subnet when given the address hint specified
because it is the only subnet defined.
% DHCPSRV_CFGMGR_OPTION_DUPLICATE multiple options with the code: %1 added to the subnet: %2
This warning message is issued on an attempt to configure multiple options with the
same option code for the particular subnet. Adding multiple options is uncommon
@@ -401,12 +356,6 @@ the host database. The operation started a retry to connect procedure.
The database access string with password redacted is logged, along with the
error and details for the reconnect procedure.
% DHCPSRV_INVALID_ACCESS invalid database access string: %1
This is logged when an attempt has been made to parse a database access string
and the attempt ended in error. The access string in question - which
should be of the form 'keyword=value keyword=value...' is included in
the message.
% DHCPSRV_LEASE4_EXTENDED_INFO_SANITY_FAIL extended info for lease %1 failed checks (%2)
This error message is printed when a lease extended info failed to
pass sanity checks. The detail of the found problem was displayed and
@@ -491,10 +440,6 @@ A debug message issued when the server is extracting extended info.
The extended info sanity check level and update in file when requested
are displayed.
% DHCPSRV_MEMFILE_BEGIN_TRANSACTION committing to memory file database
The code has issued a begin transaction call. For the memory file database
this is a no-op.
% DHCPSRV_MEMFILE_BUILD_EXTENDED_INFO_TABLES6 building extended info tables saw %1 leases, extended info sanity checks modified %2 leases and %3 leases were entered into tables
Extended info tables build was finished. Some statistics are displayed, the
updated in database is returned to the command interface.
@@ -690,10 +635,6 @@ A debug message issued when the server is attempting to obtain a page of
IPv6 leases from the memory file database beginning with the specified
address for a given subnet identifier.
% DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information
A debug message issued when the server is about to obtain schema version
information from the memory file database.
% DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file %1
An info message issued when the server is about to start reading DHCP leases
from the lease file. All leases currently held in the memory will be
@@ -835,9 +776,6 @@ Logged at debug log level 50.
A debug message issued when the server is about to add an IPv6 lease
with the specified address to the MySQL backend database.
% DHCPSRV_MYSQL_BEGIN_TRANSACTION committing to MySQL database
The code has issued a begin transaction call.
% DHCPSRV_MYSQL_COMMIT committing to MySQL database
Logged at debug log level 50.
The code has issued a commit call. All outstanding transactions will be
@@ -875,13 +813,6 @@ leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% DHCPSRV_MYSQL_FATAL_ERROR Unrecoverable MySQL error occurred: %1 for <%2>, reason: %3 (error code: %4).
An error message indicating that communication with the MySQL database server
has been lost. If automatic recovery has been enabled, then the server will
attempt to recover the connectivity. If not the server will exit with a
non-zero exit code. The cause of such an error is most likely a network issue
or the MySQL server has gone down.
% DHCPSRV_MYSQL_GET4 obtaining all IPv4 leases
Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv4
@@ -1077,15 +1008,6 @@ Logged at debug log level 50.
The code has issued a rollback call. All outstanding transaction will
be rolled back and not committed to the database.
% DHCPSRV_MYSQL_START_TRANSACTION starting new MySQL transaction
A debug message issued when a new MySQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
inserted into multiple tables with multiple INSERT statements
and there may be a need to rollback the whole transaction if
any of these INSERT statements fail.
% DHCPSRV_MYSQL_TLS_CIPHER TLS cipher: %1
Logged at debug log level 40.
A debug message issued when a new MySQL connected is created with TLS.
@@ -1158,9 +1080,6 @@ Logged at debug log level 50.
A debug message issued when the server is about to add an IPv6 lease
with the specified address to the PostgreSQL backend database.
% DHCPSRV_PGSQL_BEGIN_TRANSACTION committing to PostgreSQL database
The code has issued a begin transaction call.
% DHCPSRV_PGSQL_COMMIT committing to PostgreSQL database
Logged at debug log level 50.
The code has issued a commit call. All outstanding transactions will be
@@ -1173,13 +1092,6 @@ V6) is about to open a PostgreSQL lease database. The parameters of the
connection including database name and username needed to access it
(but not the password if any) are logged.
% DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
This is an error message issued when a DHCP server (either V4 or V6) experienced
and error freeing database SQL resources as part of closing its connection to
the PostgreSQL database. The connection is closed as part of normal server
shutdown. This error is most likely a programmatic issue that is highly
unlikely to occur or negatively impact server operation.
% DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1
Logged at debug log level 50.
A debug message issued when the server is attempting to delete a lease for
@@ -1199,13 +1111,6 @@ leases which have expired longer than a specified period of time.
The argument is the amount of time Kea waits after a reclaimed
lease expires before considering its removal.
% DHCPSRV_PGSQL_FATAL_ERROR Unrecoverable PostgreSQL error occurred: Statement: <%1>, reason: %2 (error code: %3).
An error message indicating that communication with the PostgreSQL database server
has been lost. If automatic recovery has been enabled, then the server will
attempt to recover the connectivity. If not the server will exit with a
non-zero exit code. The cause of such an error is most likely a network issue
or the PostgreSQL server has gone down.
% DHCPSRV_PGSQL_GET4 obtaining all IPv4 leases
Logged at debug log level 50.
A debug message issued when the server is attempting to obtain all IPv4
@@ -1402,15 +1307,6 @@ Logged at debug log level 50.
The code has issued a rollback call. All outstanding transaction will
be rolled back and not committed to the database.
% DHCPSRV_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction
A debug message issued when a new PostgreSQL transaction is being started.
This message is typically not issued when inserting data into a
single table because the server doesn't explicitly start
transactions in this case. This message is issued when data is
inserted into multiple tables with multiple INSERT statements
and there may be a need to rollback the whole transaction if
any of these INSERT statements fail.
% DHCPSRV_PGSQL_TLS_SUPPORT Attempt to configure TLS: %1
This informational message is printed when TLS support was required in
the Kea configuration: The TLS support in PostgreSQL will be initialized but
@@ -1578,13 +1474,6 @@ A debug message issued when one of the registered interval timers
is unregistered from the Timer Manager. The name of the timer is
included in the message.
% DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'
The parameters for access the lease database were passed to the server through
the named configuration parameter, but the code was expecting them to be
passed via the parameter named "lease-database". If the database opens
successfully, there is no impact on server operation. However, as this does
indicate an error in the source code, please submit a bug report.
% DHCPSRV_UNKNOWN_DB unknown database type: %1
The database access string specified a database type (given in the
message) that is unknown to the software. This is a configuration error.

25
src/lib/process/process_messages.mes
View File

@@ -16,10 +16,6 @@ it contains refers to a process other than Kea process. In such an event,
it would be necessary to manually remove the PID file. The first argument is
the process name, the second contains the PID and PID file.
% DCTL_CCSESSION_ENDING %1 ending control channel session
This debug message is issued just before the controller attempts
to disconnect from its session with the Kea control channel.
% DCTL_CFG_FILE_RELOAD_ERROR configuration reload failed: %1, reverting to current configuration.
This is an error message indicating that the application attempted to reload
its configuration from file and encountered an error. This is likely due to
@@ -30,10 +26,6 @@ to operate under its current configuration.
This is an informational message indicating the application has received a signal
instructing it to reload its configuration from file.
% DCTL_COMMAND_RECEIVED %1 received command: %2, arguments: %3
A debug message listing the command (and possible arguments) received
from the Kea control system by the controller.
% DCTL_CONFIG_CHECK_COMPLETE server has completed configuration check: %1, result: %2
This is an informational message announcing the successful processing of a
new configuration check is complete. The result of that check is printed.
@@ -57,25 +49,12 @@ retrieving configuration data from one or more configuration backends.
This fatal error message indicates that the application attempted to load its
initial configuration from file and has failed. The service will exit.
% DCTL_CONFIG_LOAD_FAIL %1 configuration failed to load: %2
This critical error message indicates that the initial application
configuration has failed. The service will start, but will not
process requests until the configuration has been corrected.
% DCTL_CONFIG_START parsing new configuration: %1
Logged at debug log level 10.
A debug message indicating that the application process has received an
updated configuration and has passed it to its configuration manager
for parsing.
% DCTL_CONFIG_STUB %1 configuration stub handler called
This debug message is issued when the dummy handler for configuration
events is called. This only happens during initial startup.
% DCTL_CONFIG_UPDATE %1 updated configuration received: %2
A debug message indicating that the controller has received an
updated configuration from the Kea configuration system.
% DCTL_DB_OPEN_CONNECTION_WITH_RETRY_FAILED Failed to connect to database: %1 with error: %2
This is an informational message issued when the server failed to connect to
the configuration database. The operation started a retry to connect procedure.
@@ -129,10 +108,6 @@ Logged at debug log level 0.
This debug message is issued just before the controller invokes
the application run method.
% DCTL_SESSION_FAIL %1 controller failed to establish Kea session: %1
The controller has failed to establish communication with the rest of
Kea and will exit.
% DCTL_SHUTDOWN %1 has shut down, pid: %2, version: %3
Logged at debug log level 0.
This is an informational message indicating that the service has shut

19
src/lib/tcp/tcp_messages.mes
View File

@@ -29,11 +29,6 @@ This debug message is issued when the server finished receiving a TCP
request from the remote endpoint. The address of the remote endpoint is
specified as an argument.
% TCP_CONNECTION_CLOSE_CALLBACK_FAILED Connection close callback threw an exception
This is an error message emitted when the close connection callback
registered on the connection failed unexpectedly. This is a programmatic
error that should be submitted as a bug.
% TCP_CONNECTION_REJECTED_BY_FILTER connection from %1 has been denied by the connection filter.
Logged at debug log level 50.
This debug message is issued when the server's connection filter rejects
@@ -79,12 +74,6 @@ Logged at debug log level 50.
This debug message is issued when the TCP connection is being closed as a
result of being idle.
% TCP_PREMATURE_CONNECTION_TIMEOUT_OCCURRED premature connection timeout occurred: in transaction ? %1, transid: %2, current_transid: %3
This warning message is issued when unexpected timeout occurred during the
transaction. This is proven to occur when the system clock is moved manually
or as a result of synchronization with a time server. Any ongoing transactions
will be interrupted. New transactions should be conducted normally.
% TCP_REQUEST_RECEIVED_FAILED An unexpected error occurred processing a request from %1, error: %2
This error message is issued when an unexpected error occurred while the
server attempted to process a received request. The first argument specifies
@@ -104,14 +93,6 @@ This debug message is issued when the server is starting to send a TCP
response to a remote endpoint. The argument specifies an address of
the remote endpoint.
% TCP_SERVER_RESPONSE_SEND_DETAILS detailed information about response sent to %1:\n%2
This debug message is issued right before the server sends a TCP response
to the client. It includes detailed information about the response. The
first argument specifies an address of the remote endpoint to which the
response is being sent. The second argument provides a response in the
textual form. The response is truncated by the logger if it is too large
to be printed.
% TLS_CONNECTION_HANDSHAKE_FAILED TLS handshake with %1 failed with %2
This information message is issued when the TLS handshake failed at the
server side. The client address and the error message are displayed.