|
@@ -1,4 +1,4 @@
|
|
|
-# Copyright (C) 2013-2015 Internet Systems Consortium, Inc. ("ISC")
|
|
|
+# Copyright (C) 2013-2016 Internet Systems Consortium, Inc. ("ISC")
|
|
|
#
|
|
|
# This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
@@ -6,83 +6,6 @@
|
|
|
|
|
|
$NAMESPACE isc::d2
|
|
|
|
|
|
-% 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_CCSESSION_STARTING %1 starting control channel session, specfile: %2
|
|
|
-This debug message is issued just before the controller attempts
|
|
|
-to establish a session with the Kea control channel.
|
|
|
-
|
|
|
-% 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_COMPLETE server has completed configuration: %1
|
|
|
-This is an informational message announcing the successful processing of a
|
|
|
-new configuration. It is output during server startup, and when an updated
|
|
|
-configuration is committed by the administrator. Additional information
|
|
|
-may be provided.
|
|
|
-
|
|
|
-% DCTL_CONFIG_FILE_LOAD_FAIL %1 reason: %2
|
|
|
-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
|
|
|
-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_INIT_PROCESS %1 initializing the application
|
|
|
-This debug message is issued just before the controller attempts
|
|
|
-to create and initialize its application instance.
|
|
|
-
|
|
|
-% DCTL_INIT_PROCESS_FAIL %1 application initialization failed: %2
|
|
|
-This error message is issued if the controller could not initialize the
|
|
|
-application and will exit.
|
|
|
-
|
|
|
-% DCTL_NOT_RUNNING %1 application instance is not running
|
|
|
-A warning message is issued when an attempt is made to shut down the
|
|
|
-application when it is not running.
|
|
|
-
|
|
|
-% DCTL_PARSER_FAIL : %1
|
|
|
-On receipt of a new configuration, the server failed to create a parser to
|
|
|
-decode the contents of the named configuration element, or the creation
|
|
|
-succeeded but the parsing actions and committal of changes failed.
|
|
|
-The reason for the failure is given in the message.
|
|
|
-
|
|
|
-% DCTL_PROCESS_FAILED %1 application execution failed: %2
|
|
|
-The controller has encountered a fatal error while running the
|
|
|
-application and is terminating. The reason for the failure is
|
|
|
-included in the message.
|
|
|
-
|
|
|
-% DCTL_RUN_PROCESS %1 starting application event loop
|
|
|
-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_STANDALONE %1 skipping message queue, running standalone
|
|
|
-This is a debug message indicating that the controller is running in the
|
|
|
-application in standalone mode. This means it will not connected to the Kea
|
|
|
-message queue. Standalone mode is only useful during program development,
|
|
|
-and should not be used in a production environment.
|
|
|
-
|
|
|
% DHCP_DDNS_ADD_FAILED DHCP_DDNS Request ID %1: Transaction outcome %2
|
|
|
This is an error message issued after DHCP_DDNS attempts to submit DNS mapping
|
|
|
entry additions have failed. The precise reason for the failure should be
|
|
@@ -106,16 +29,6 @@ the DHCP_DDNS process name, the second contains the PID and PID file.
|
|
|
This is a debug message that indicates that the application has DHCP_DDNS
|
|
|
requests in the queue but is working as many concurrent requests as allowed.
|
|
|
|
|
|
-% DHCP_DDNS_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
|
|
|
-invalid content in the configuration file. The application should continue
|
|
|
-to operate under its current configuration.
|
|
|
-
|
|
|
-% DHCP_DDNS_CFG_FILE_RELOAD_SIGNAL_RECVD OS signal %1 received, reloading configuration from file: %2
|
|
|
-This is an informational message indicating the application has received a signal
|
|
|
-instructing it to reload its configuration from file.
|
|
|
-
|
|
|
% DHCP_DDNS_CLEARED_FOR_SHUTDOWN application has met shutdown criteria for shutdown type: %1
|
|
|
This is a debug message issued when the application has been instructed
|
|
|
to shutdown and has met the required criteria to exit.
|
|
@@ -280,15 +193,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_PID_FILE_ERROR %1 could not create a PID file: %2
|
|
|
-This is an error message that occurs when DHCP_DDNS is unable to create
|
|
|
-its PID file. The log message should contain details sufficient to
|
|
|
-determine the underlying cause. The most likely culprits are that
|
|
|
-some portion of the pathname does not exist or a permissions issue. The
|
|
|
-default path is determined by --localstatedir configure parameter but
|
|
|
-may be overridden by setting environment variable, KEA_PIDFILE_DIR. The
|
|
|
-first argument is the DHCP_DDNS process name.
|
|
|
-
|
|
|
% DHCP_DDNS_PROCESS_INIT application init invoked
|
|
|
This is a debug message issued when the DHCP-DDNS application enters
|
|
|
its initialization method.
|
|
@@ -448,33 +352,15 @@ reverse update will not performed.
|
|
|
This is a debug message issued when the DHCP-DDNS server exits its
|
|
|
event lo
|
|
|
|
|
|
-% DHCP_DDNS_SHUTDOWN DHCP-DDNS has shut down
|
|
|
-This is an informational message indicating that the DHCP-DDNS service
|
|
|
-has shut down.
|
|
|
-
|
|
|
% DHCP_DDNS_SHUTDOWN_COMMAND application received shutdown command with args: %1
|
|
|
This is a debug message issued when the application has been instructed
|
|
|
to shut down by the controller.
|
|
|
|
|
|
-% DHCP_DDNS_SHUTDOWN_SIGNAL_RECVD OS signal %1 received, starting shutdown
|
|
|
-This is a debug message indicating the application has received a signal
|
|
|
-instructing it to shutdown.
|
|
|
-
|
|
|
-% DHCP_DDNS_SIGNAL_ERROR signal handler for signal %1, threw an unexpected exception: %2
|
|
|
-This is an error message indicating that the application encountered an unexpected
|
|
|
-error after receiving a signal. This is a programmatic error and should be
|
|
|
-reported. While The application will likely continue to operating, it may be
|
|
|
-unable to respond correctly to signals.
|
|
|
-
|
|
|
% DHCP_DDNS_STARTED Kea DHCP-DDNS server version %1 started
|
|
|
This informational message indicates that the DHCP-DDNS server has
|
|
|
processed all configuration information and is ready to begin processing.
|
|
|
The version is also printed.
|
|
|
|
|
|
-% DHCP_DDNS_STARTING DHCP-DDNS starting, pid: %1, version: %2
|
|
|
-This is an informational message issued when controller for the
|
|
|
-service first starts. Version is also reported.
|
|
|
-
|
|
|
% DHCP_DDNS_STARTING_TRANSACTION Request ID %1:
|
|
|
This is a debug message issued when DHCP-DDNS has begun a transaction for
|
|
|
a given request.
|
|
@@ -491,12 +377,6 @@ message but the attempt to send it suffered an unexpected error. This is most
|
|
|
likely a programmatic error, rather than a communications issue. Some or all
|
|
|
of the DNS updates requested as part of this request did not succeed.
|
|
|
|
|
|
-% DHCP_DDNS_UNSUPPORTED_SIGNAL ignoring reception of unsupported signal: %1
|
|
|
-This is a debug message indicating that the application received an
|
|
|
-unsupported signal. This is a programming error indicating that the
|
|
|
-application has registered to receive the signal but no associated
|
|
|
-processing logic has been added.
|
|
|
-
|
|
|
% DHCP_DDNS_UPDATE_REQUEST_SENT Request ID %1: %2 to server: %3
|
|
|
This is a debug message issued when DHCP_DDNS sends a DNS request to a DNS
|
|
|
server.
|