while DHCP_DDNS was adding a forward address mapping. The request will be
aborted. This is most likely a programmatic issue and should be reported.
-% DHCP_DDNS_FORWARD_ADD_BUILD_FAILURE DNS Request ID %1: udpate message to add a forward DNS entry could not be constructed for this request: %2, reason: %3
+% DHCP_DDNS_FORWARD_ADD_BUILD_FAILURE DNS Request ID %1: update message to add a forward DNS entry could not be constructed for this request: %2, reason: %3
This is an error message issued when an error occurs attempting to construct
the server bound packet requesting a forward address addition. This is due
to invalid data contained in the NameChangeRequest. The request will be aborted.
while DHCP_DDNS was removing a forward address mapping. The request will be
aborted. This is most likely a programmatic issue and should be reported.
-% DHCP_DDNS_FORWARD_REMOVE_ADDRS_BUILD_FAILURE DNS Request ID %1: udpate message to remove a forward DNS Address entry could not be constructed for this request: %2, reason: %3
+% DHCP_DDNS_FORWARD_REMOVE_ADDRS_BUILD_FAILURE DNS Request ID %1: update message to remove a forward DNS Address entry could not be constructed for this request: %2, reason: %3
This is an error message issued when an error occurs attempting to construct
the server bound packet requesting a forward address (A or AAAA) removal. This
is due to invalid data contained in the NameChangeRequest. The request will be
while DHCP_DDNS was removing forward RRs. The request will be aborted. This is
most likely a programmatic issue and should be reported.
-% DHCP_DDNS_FORWARD_REMOVE_RRS_BUILD_FAILURE DNS Request ID %1: udpate message to remove forward DNS RR entries could not be constructed for this request: %2, reason: %3
+% DHCP_DDNS_FORWARD_REMOVE_RRS_BUILD_FAILURE DNS Request ID %1: update message to remove forward DNS RR entries could not be constructed for this request: %2, reason: %3
This is an error message issued when an error occurs attempting to construct
the server bound packet requesting forward RR (DHCID RR) removal. This is due
-to invalid data contained in the NameChangeRequest. The request will be aborted.This is most likely a configuration issue.
+to invalid data contained in the NameChangeRequest. The request will be aborted.
+This is most likely a configuration issue.
% DHCP_DDNS_FORWARD_REMOVE_RRS_IO_ERROR DHCP_DDNS Request ID %1: encountered an IO error sending a forward RR removal for FQDN %2 to DNS server %3
This is an error message issued when a communication error occurs while
% DHCP_DDNS_REQUEST_DROPPED Request ID %1: Request contains no enabled update requests and will be dropped: %2
This is a debug message issued when DHCP_DDNS receives a request which does not
contain updates in a direction that is enabled. In other words, if only forward
-updates are enabled and request is recevied that asks only for reverse updates
+updates are enabled and request is received that asks only for reverse updates
then the request is dropped.
% DHCP_DDNS_REVERSE_REMOVE_BAD_DNSCLIENT_STATUS DHCP_DDNS Request ID %1: received an unknown DNSClient status: %2, while removing reverse address mapping for FQDN %3 to DNS server %4
% 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 beging processing.
+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
and timers. After that, it will enter the wait state again.
% DHCP4_BUFFER_WAIT_INTERRUPTED interrupted wait for the next packet due to timeout, signal or external socket callback (timeout value is %1)
-This debug message is issued when the server intrrupts waiting
+This debug message is issued when the server interrupts waiting
for reception of the next DHCPv6 message due to timeout, signal
or reception of the data over socket other than used for DHCPv4
message transmission. The server will now handle signals
the client and transaction identification information. The second argument
includes the released IPv4 address.
-% DHCP4_RELEASE_EXCEPTION %1: while trying to release address %2 an exception occured: %3
+% DHCP4_RELEASE_EXCEPTION %1: while trying to release address %2 an exception occurred: %3
This message is output when an error was encountered during an attempt
to process a DHCPRELEASE message. The error will not affect the client,
which does not expect any response from the server for DHCPRELEASE
failure is given within the message.
% DHCP4_SRV_D2STOP_ERROR error stopping IO with DHCP_DDNS during shutdown: %1
-This error message indicates that during shutdown, an erro occurred while
+This error message indicates that during shutdown, an error occurred while
stopping IO between the DHCPv4 server and the DHCP_DDNS server. This is
probably due to a programmatic error is not likely to impact either server
upon restart. The reason for the failure is given within the message.
% DHCP6_DECLINE_LEASE Client %1 sent DECLINE for address %2 and the server marked it as declined. The lease will be recovered in %3 seconds.
This informational message indicates that the client leased an address, but
-discovered that it is being used by some other devicea and reported this to the
+discovered that it is being used by some other device and reported this to the
server by sending a Decline message. The server marked the lease as
declined. This likely indicates a misconfiguration in the network. Either
the server is configured with an incorrect pool or there are devices that have
failure is given within the message.
% DHCP6_SRV_D2STOP_ERROR error stopping IO with DHCP_DDNS during shutdown: %1
-This error message indicates that during shutdown, an erro occurred while
+This error message indicates that during shutdown, an error occurred while
stopping IO between the DHCPv6 server and the DHCP_DDNS server. This is
probably due to a programmatic error is not likely to impact either server
upon restart. The reason for the failure is given within the message.
$NAMESPACE isc::lfc
% LFC_FAIL_PID_CREATE : %1
This message is issued if LFC detected a failure when trying
-to create the PID file. It includes a more specifc error string.
+to create the PID file. It includes a more specific error string.
% LFC_FAIL_PID_DEL : %1
This message is issued if LFC detected a failure when trying
-to delete the PID file. It includes a more specifc error string.
+to delete the PID file. It includes a more specific error string.
% LFC_FAIL_PROCESS : %1
This message is issued if LFC detected a failure when trying
-to process the files. It includes a more specifc error string.
+to process the files. It includes a more specific error string.
% LFC_FAIL_ROTATE : %1
This message is issued if LFC detected a failure when trying
-to rotate the files. It includes a more specifc error string.
+to rotate the files. It includes a more specific error string.
% LFC_PROCESSING Previous file: %1, copy file: %2
This message is issued just before LFC starts processing the
% ALLOC_ENGINE_V4_REQUEST_REMOVE_LEASE %1: removing previous client's lease %2
This message is logged when the allocation engine removes previous
-lease for the client because the cliet has been allocated new one.
+lease for the client because the client has been allocated new one.
% ALLOC_ENGINE_V4_REQUEST_USE_HR client %1 hasn't requested specific address, using reserved address %2
This message is issued when the client is not requesting any specific
allocating leases for the client, 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
-remaning leases to the client.
+remaining leases to the client.
% ALLOC_ENGINE_V6_ALLOC_NO_LEASES_HR no leases found but reservations exist for client %1
This message is logged when the allocation engine is in the process of
The server will also remove any leases that the client is trying
to renew that are not reserved for the client.
-% ALLOC_ENGINE_V6_RENEW_REMOVE_RESERVED %1: checking if existing client's leases are reseved for another client
+% ALLOC_ENGINE_V6_RENEW_REMOVE_RESERVED %1: checking if existing client's leases are reserved for another client
This message is logged when the allocation engine finds leases for
the client and will check if these leases are reserved for another
client. If they are, they will not be renewed for the client
log with details. No further attempts to communicate with kea-dhcp-ddns will
be made without intervention.
-% DHCPSRV_HOOK_LEASE4_RECOVER_SKIP DHCPv4 lease %1 was not recoverd from the declined state because a callout set the skip status.
+% DHCPSRV_HOOK_LEASE4_RECOVER_SKIP DHCPv4 lease %1 was not recovered from the declined state because a callout set the skip status.
This debug message is printed when a callout installed on lease4_recover
hook point set the next step status to SKIP. For this particular hook point, this
indicates that the server should not recover the lease from declined state.
lease expires before considering its removal.
% DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED_START starting deletion of %1 expired-reclaimed leases
-A debug message issued wheb the server has found expired-reclaimed
+A debug message issued when the server has found expired-reclaimed
leases to be removed. The number of leases to be removed is logged
in the message.
A debug message issued when the server is attempting to update IPv6
lease from the memory file database for the specified address.
-% DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple brodcast capable sockets on some interfaces and some DHCP messages may be duplicated
+% DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple broadcast capable sockets on some interfaces and some DHCP messages may be duplicated
A warning message issued when the current configuration indicates that multiple
-sockets, capable of receiving brodcast traffic, will be opened on some of the
+sockets, capable of receiving broadcast traffic, will be opened on some of the
interfaces. It must be noted that this may lead to receiving and processing
the same DHCP message multiple times, as it will be received by each socket
individually.
should be executed for this timer. The callback will not
be executed this time and most likely the subsequent attempts
will not be successful too. This error is highly unlikely.
-The name of the timer and thre reason for failure is included
+The name of the timer and the reason for failure is included
in the message.
% DHCPSRV_TIMERMGR_START_THREAD starting thread for timers
% HOSTS_CFG_GET_ALL_ADDRESS4_HOST using address %1 found host: %2
This debug message is issued when found host with the reservation
-for the specified IPv4 addres. The arguments specify the IPv4 address
+for the specified IPv4 address. The arguments specify the IPv4 address
and the detailed description of the host found.
% HOSTS_CFG_GET_ALL_ADDRESS6 get all hosts with reservations for IPv6 address %1
% HOSTS_MGR_ALTERNATE_GET6_SUBNET_ID_ADDRESS6 trying alternate source for host using subnet id %1 and IPv6 address %2
This debug message is issued when the Host Manager doesn't find the
-host connected to teh specific subnet and having the reservation for
+host connected to the specific subnet and having the reservation for
the specified IPv6 address, and it is starting to search for this
host in the alternate host data source.
projects / thirdparty / kea.git / commitdiff
