[#1723] remove unlogged message definitions

Author: andrei-pavel

src/bin/dhcp4/dhcp4_messages.mes

@@ -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

src/bin/dhcp6/dhcp6_messages.mes

@@ -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

src/bin/netconf/netconf_messages.mes

@@ -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.

src/hooks/dhcp/lease_cmds/lease_cmds_messages.mes

@@ -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!

src/hooks/dhcp/perfmon/perfmon_messages.mes

@@ -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.

src/hooks/dhcp/stat_cmds/stat_cmds_messages.mes

@@ -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!