dhcp4_messages.mes 39.7 KB
Newer Older
1
# Copyright (C) 2012-2018 Internet Systems Consortium, Inc. ("ISC")
2
#
3 4 5
# 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
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
6 7 8

$NAMESPACE isc::dhcp

9 10 11 12 13
% 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.

14 15 16 17 18 19 20 21
% 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.
This most likely indicates an attempt to start a second instance of
the server 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
the server.  In such an event, it would be necessary to manually remove
22
the PID file.  The first argument is the DHCPv4 process name, the
23
second contains the PID and PID file.
24

25
% DHCP4_BUFFER_RECEIVED received buffer from %1:%2 to %3:%4 over interface %5
26
This debug message is logged when the server has received a packet
27 28
over the socket. When the message is logged the contents of the received
packet hasn't been parsed yet. The only available information is the
29
interface and the source and destination IPv4 addresses/ports.
30

31 32 33 34 35
% DHCP4_BUFFER_RECEIVE_FAIL error on attempt to receive packet: %1
The DHCPv4 server tried to receive a packet but an error
occurred during this attempt. The reason for the error is included in
the message.

36
% DHCP4_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
37
This debug message is issued when the server starts parsing the received
38
buffer holding the DHCPv4 message. The arguments specify the source and
39
destination IPv4 addresses as well as the interface over which the buffer has
40
been received.
41 42

% DHCP4_BUFFER_WAIT_SIGNAL signal received while waiting for next packet, next waiting signal is %1
43 44 45 46 47
This debug message is issued when the server was waiting for the
packet, but the wait has been interrupted by the signal received
by the process. The signal will be handled before the server starts
waiting for next packets. The argument specifies the next signal to
be handled by the server.
48

49
% DHCP4_CLASS_ASSIGNED %1: client packet has been assigned to the following class(es): %2
50
This debug message informs that incoming packet has been assigned to specified
Francis Dupont's avatar
Francis Dupont committed
51
class or classes. This is a normal behavior and indicates successful operation.
52 53 54
The first argument specifies the client and transaction identification
information. The second argument includes all classes to which the
packet has been assigned.
55

Shawn Routhier's avatar
Shawn Routhier committed
56
% DHCP4_CLASS_UNCONFIGURED %1: client packet belongs to an unconfigured class: %2
57 58 59 60
This debug message informs that incoming packet belongs to a class
which cannot be found in the configuration. Either a hook written
before the classification was added to Kea is used, or class naming is
inconsistent.
61

62 63 64 65 66 67 68
% DHCP4_CLIENTID_IGNORED_FOR_LEASES %1: not using client identifier for lease allocation for subnet %2
This debug message is issued when the server is processing the DHCPv4 message
for which client identifier will not be used when allocating new lease or
renewing existing lease. The server is explicitly configured to not use
client identifier to lookup existing leases for the client and will not
record client identifier in the lease database. This mode of operation
is useful when clients don't use stable client identifiers, e.g. multi
69 70 71 72
stage booting. The first argument includes the client and transaction
identification information. The second argument specifies the identifier
of the subnet where the client is connected and for which this mode of
operation is configured on the server.
73

74
% DHCP4_CLIENT_FQDN_DATA %1: Client sent FQDN option: %2
75 76
This debug message includes the detailed information extracted from the
Client FQDN option sent in the query. The first argument includes the
77 78 79
client and transaction identification information. The second argument
specifies the detailed information about the FQDN option received
by the server.
80

81 82 83 84
% DHCP4_CLIENT_FQDN_PROCESS %1: processing Client FQDN option
This debug message is issued when the server starts processing the Client
FQDN option sent in the client's query. The argument includes the
client and transaction identification information.
85

86
% DHCP4_CLIENT_HOSTNAME_DATA %1: client sent Hostname option: %2
87 88
This debug message includes the detailed information extracted from the
Hostname option sent in the query. The first argument includes the
89 90 91
client and transaction identification information. The second argument
specifies the hostname carried in the Hostname option sent by the
client.
92

93 94 95 96 97
% DHCP4_CLIENT_HOSTNAME_PROCESS %1: processing client's Hostname option
This debug message is issued when the server starts processing the Hostname
option sent in the client's query. The argument includes the client and
transaction identification information.

98
% DHCP4_CLIENT_NAME_PROC_FAIL %1: failed to process the fqdn or hostname sent by a client: %2
99 100
This debug message is issued when the DHCP server was unable to process the
FQDN or Hostname option sent by a client. This is likely because the client's
101 102 103
name was malformed or due to internal server error. The first argument
contains the client and transaction identification information. The
second argument holds the detailed description of the error.
104

105
% DHCP4_COMMAND_RECEIVED received command %1, arguments: %2
106
A debug message listing the command (and possible arguments) received
107
from the Kea control system by the DHCPv4 server.
108

109 110 111 112 113 114
% DHCP4_CONFIG_COMPLETE DHCPv4 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.

115 116 117 118 119
% 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.
120

121
% DHCP4_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1
Jeremy C. Reed's avatar
Jeremy C. Reed committed
122 123
This is an informational message reporting that the configuration has
been extended to include the specified IPv4 subnet.
124

125 126 127 128
% 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.
129

130 131 132 133
% DHCP4_CONFIG_RECEIVED received configuration %1
A debug message listing the configuration received by the DHCPv4 server.
The source of that configuration depends on used configuration backend.

134 135
% DHCP4_CONFIG_START DHCPv4 server is processing the following configuration: %1
This is a debug message that is issued every time the server receives a
136
configuration. That happens at start up and also when a server configuration
137 138
change is committed by the administrator.

139
% DHCP4_CONFIG_UPDATE updated configuration received: %1
140
A debug message indicating that the DHCPv4 server has received an
141
updated configuration from the Kea configuration system.
142

143
% DHCP4_DDNS_REQUEST_SEND_FAILED failed sending a request to kea-dhcp-ddns, error: %1,  ncr: %2
144
This error message indicates that DHCP4 server attempted to send a DDNS
Francis Dupont's avatar
Francis Dupont committed
145
update request to the DHCP-DDNS server.  This is most likely a configuration or
146 147
networking error.

148 149 150 151 152
% 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.

Tomek Mrugalski's avatar
Tomek Mrugalski committed
153
% DHCP4_DECLINE_LEASE Received DHCPDECLINE for addr %1 from client %2. The lease will be unavailable for %3 seconds.
154
This informational message is printed when a client received an address, but
155 156 157
discovered that it is being used by some other device and notified the server by
sending a DHCPDECLINE message. The server checked that this address really was
leased to the client and marked this address as unusable for a certain
158 159 160
amount of time. This message may indicate a misconfiguration in a network,
as there is either a buggy client or more likely a device that is using an
address that it is not supposed to. The server will fully recover from this
161
situation, but if the underlying problem of a misconfigured or rogue device
162 163
is not solved, this address may be declined again in the future.

164
% DHCP4_DECLINE_LEASE_MISMATCH Received DHCPDECLINE for addr %1 from client %2, but the data doesn't match: received hwaddr: %3, lease hwaddr: %4, received client-id: %5, lease client-id: %6
165
This informational message means that a client attempted to report his address
166 167
as declined (i.e. used by unknown entity). The server has information about
a lease for that address, but the client's hardware address or client identifier
168
does not match the server's stored information. The client's request will be ignored.
169

170 171 172 173 174 175
% DHCP4_DECLINE_LEASE_NOT_FOUND Received DHCPDECLINE for addr %1 from client %2, but no such lease found.
This warning message indicates that a client reported that his address was
detected as a duplicate (i.e. another device in the network is using this address).
However, the server does not have a record for this address. This may indicate
a client's error or a server's purged database.

176 177 178
% DHCP4_DHCP4O6_BAD_PACKET received malformed DHCPv4o6 packet: %1
A malformed DHCPv4o6 packet was received.

Francis Dupont's avatar
Francis Dupont committed
179
% DHCP4_DHCP4O6_PACKET_SEND %1: trying to send packet %2 (type %3) to %4 on interface %5 encapsulating %6: %7 (type %8)
180
The arguments specify the client identification information (HW address
Francis Dupont's avatar
Francis Dupont committed
181 182 183
and client identifier), DHCPv6 message name and type, source IPv6
address and interface name, DHCPv4 client identification, message
name and type.
184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206

% DHCP4_DHCP4O6_PACKET_SEND_FAIL %1: failed to send DHCPv4o6 packet: %2
This error is output if the IPv4 DHCP server fails to send an
DHCPv4o6 message to the IPv6 DHCP server. The reason for the
error is included in the message.

% DHCP4_DHCP4O6_RECEIVE_FAIL failed to receive DHCPv4o6: %1
This debug message indicates the inter-process communication with the
DHCPv6 server failed. The reason for the error is included in
the message.

% DHCP4_DHCP4O6_RECEIVING receiving DHCPv4o6 packet from DHCPv6 server
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv6 server over inter-process communication socket.

% DHCP4_DHCP4O6_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
A debug message including the detailed data about the packet being
sent to the DHCPv6 server to be forwarded to the client. The first
argument contains the client and the transaction identification
information. The second and third argument contains the packet name
and type respectively. The fourth argument contains detailed packet
information.

Francis Dupont's avatar
Francis Dupont committed
207
% DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: %1, after receiving SIGHUP signal
208 209 210 211 212 213 214
This is the info message logged when the DHCPv4 server starts reconfiguration
as a result of receiving SIGHUP signal.

% DHCP4_DYNAMIC_RECONFIGURATION_FAIL dynamic server reconfiguration failed with file: %1
This is an error message logged when the dynamic reconfiguration of the
DHCP server failed.

215
% DHCP4_EMPTY_HOSTNAME %1: received empty hostname from the client, skipping processing of this option
216 217
This debug message is issued when the server received an empty Hostname option
from a client. Server does not process empty Hostname options and therefore
218 219
option is skipped. The argument holds the client and transaction identification
information.
220

221 222 223
% DHCP4_FLEX_ID flexible identifier generated for incoming packet: %1
This debug message is printed when host reservation type is set to flexible identifier
and the expression specified in its configuration generated (was evaluated to)
Francis Dupont's avatar
Francis Dupont committed
224
an identifier for incoming packet. This debug message is mainly intended as a
225 226
debugging assistance for flexible identifier.

227 228 229 230 231
% DHCP4_GENERATE_FQDN %1: client did not send a FQDN or hostname; FQDN will be be generated for the client
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.

Tomek Mrugalski's avatar
Tomek Mrugalski committed
232 233
% 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
234 235
processing. This likely indicates a coding error and should be reported to ISC.

236 237 238 239 240
% DHCP4_HOOKS_LIBS_RELOAD_FAIL reload of hooks libraries failed
A "libreload" command was issued to reload the hooks libraries but for
some reason the reload failed.  Other error messages issued from the
hooks framework will indicate the nature of the problem.

241
% DHCP4_HOOK_BUFFER_RCVD_DROP received buffer from %1 to %2 over interface %3 was dropped because a callout set the drop flag
242
This debug message is printed when a callout installed on buffer4_receive
243
hook point set the drop flag. For this particular hook point, the
244
setting of the flag by a callout instructs the server to drop the packet.
245
The arguments specify the source and destination IPv4 address as well as
246
the name of the interface over which the buffer has been received.
247

248
% DHCP4_HOOK_BUFFER_RCVD_SKIP received buffer from %1 to %2 over interface %3 is not parsed because a callout set the next step to SKIP.
249
This debug message is printed when a callout installed on
250 251
buffer4_receive hook point set the next step to SKIP. For this particular hook
point, this value set by a callout instructs the server to
252 253 254 255
not parse the buffer because it was already parsed by the hook. The
arguments specify the source and destination IPv4 address as well as
the name of the interface over which the buffer has been received.

256
% DHCP4_HOOK_BUFFER_SEND_SKIP %1: prepared response is dropped because a callout set the next step to SKIP.
257
This debug message is printed when a callout installed on buffer4_send
258 259
hook point set the next step to SKIP. For this particular hook point, the
SKIP value set by a callout instructs the server to drop the packet.
260 261 262
Server completed all the processing (e.g. may have assigned, updated
or released leases), but the response will not be send to the client.

263 264 265 266 267 268 269
% DHCP4_HOOK_DECLINE_SKIP Decline4 hook callouts set status to DROP, ignoring packet.
This message indicates that the server received DHCPDECLINE message, it was verified
to be correct and matching server's lease information. The server called hooks
for decline4 hook point and one of the callouts set next step status to DROP.
The server will now abort processing of the packet as if it was never
received. The lease will continue to be assigned to this client.

270
% DHCP4_HOOK_LEASE4_RELEASE_SKIP %1: lease was not released because a callout set the next step to SKIP
271
This debug message is printed when a callout installed on lease4_release
272 273
hook point set the next step status to SKIP. For this particular hook point, the
value set by a callout instructs the server to not release a lease.
274

275 276 277 278
% DHCP4_HOOK_LEASES4_COMMITTED_DROP %1: packet is dropped, because a callout set the next step tp DROP
This debug message is printed when a callout installed on the leases4_committed
hook point sets the next step to DROP.

279
% DHCP4_HOOK_PACKET_RCVD_SKIP %1: packet is dropped, because a callout set the next step to SKIP
280
This debug message is printed when a callout installed on the pkt4_receive
281 282
hook point sets the next step to SKIP. For this particular hook point, the
value setting of the flag instructs the server to drop the packet.
283

284
% DHCP4_HOOK_PACKET_SEND_SKIP %1: prepared response is not sent, because a callout set the next stp to SKIP
285
This debug message is printed when a callout installed on the pkt4_send
286 287
hook point sets the next step to SKIP. For this particular hook point, this
setting instructs the server to drop the packet. This means that
288 289 290
the client will not get any response, even though the server processed
client's request and acted on it (e.g. possibly allocated a lease).

291
% DHCP4_HOOK_SUBNET4_SELECT_DROP %1: packet was dropped, because a callout set the next step to 'drop'
292
This debug message is printed when a callout installed on the
293 294
subnet4_select hook point sets the next step to 'drop' value. For this particular hook
point, the setting to that value instructs the server to drop the received
295 296 297
packet. The argument specifies the client and transaction identification
information.

298
% DHCP4_HOOK_SUBNET4_SELECT_SKIP %1: no subnet was selected, because a callout set the next skip flag
299
This debug message is printed when a callout installed on the
300
subnet4_select hook point sets the next step to SKIP value. For this particular hook
301 302 303
point, the setting of the flag instructs the server not to choose a
subnet, an action that severely limits further processing; the server
will be only able to offer global options - no addresses will be assigned.
304 305
The argument specifies the client and transaction identification
information.
306

307
% DHCP4_INFORM_DIRECT_REPLY %1: DHCPACK in reply to the DHCPINFORM will be sent directly to %2 over %3
308 309 310
This debug message is issued when the DHCPACK will be sent directly to the
client, rather than via a relay. The first argument contains the client
and transaction identification information. The second argument contains
311 312
the client's IPv4 address to which the response will be sent. The third
argument contains the local interface name.
313

314 315 316 317 318
% DHCP4_INIT_FAIL failed to initialize Kea server: %1
The server has failed to initialize. This may be because the configuration
was not successful, or it encountered any other critical error on startup.
Attached error message provides more details about the issue.

319
% DHCP4_INIT_REBOOT %1: client is in INIT-REBOOT state and requests address %2
320 321 322 323
This informational message is issued when the client is in the INIT-REBOOT
state and is requesting an IPv4 address it is using to be allocated for it.
The first argument includes the client and transaction identification
information. The second argument specifies the requested IPv4 address.
324

325
% DHCP4_LEASE_ADVERT %1: lease %2 will be advertised
326
This informational message indicates that the server has found the lease to be
327
offered to the client. It is up to the client to choose one server out of
328 329
those which offered leases and continue allocation with that server.
The first argument specifies the client and the transaction identification
330
information. The second argument specifies the IPv4 address to be offered.
331 332

% DHCP4_LEASE_ALLOC %1: lease %2 has been allocated
333 334 335 336 337
This informational message indicates that the server successfully granted a
lease in response to client's DHCPREQUEST message. The lease information will
be sent to the client in the DHCPACK message. The first argument contains the
client and the transaction identification information. The second argument
contains the allocated IPv4 address.
338

339
% DHCP4_NCR_CREATE %1: DDNS updates enabled, therefore sending name change requests
340
This debug message is issued when the server is starting to send
341 342
name change requests to the D2 module to update records for the client
in the DNS. This includes removal of old records and addition of the
343 344 345
new records as required. Details of the name change requests will be
logged in additional log entries. The argument includes the client
and the transaction identification information.
346 347

% DHCP4_NCR_CREATION_FAILED %1: failed to generate name change requests for DNS: %2
348
This message indicates that server was unable to generate NameChangeRequests
349
which should be sent to the kea-dhcp_ddns module to create
350
new DNS records for the lease being acquired or to update existing records
351 352
for the renewed lease. The first argument contains the client and transaction
identification information. The second argument includes the reason for the
353
failure.
354

355 356 357 358
% DHCP4_NOT_RUNNING DHCPv4 server is not running
A warning message is issued when an attempt is made to shut down the
DHCPv4 server but it is not running.

359
% DHCP4_NO_LEASE_INIT_REBOOT %1: no lease for address %2 requested by INIT-REBOOT client
360
This debug message is issued when the client being in the INIT-REBOOT state
361 362 363 364
requested an IPv4 address but this client is unknown. The server will not
respond. The first argument includes the client and the transaction id
identification information. The second argument includes the IPv4 address
requested by the client.
365

366 367 368 369 370
% 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.

371
% DHCP4_OPEN_SOCKET opening sockets on port %1
372
A debug message issued during startup, this indicates that the DHCPv4
373
server is about to open sockets on the specified port.
374

375
% DHCP4_OPEN_SOCKET_FAIL failed to open socket: %1
376 377 378
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.

Vincent Legout's avatar
Vincent Legout committed
379
% DHCP4_PACKET_DROP_0001 failed to parse packet from %1 to %2, received over interface %3, reason: %4
380 381 382
The DHCPv4 server has received a packet that it is unable to
interpret. The reason why the packet is invalid is included in the message.

383
% DHCP4_PACKET_DROP_0002 %1, from interface %2: no suitable subnet configured for a direct client
384 385 386 387 388
This info message is logged when received a message from a directly connected
client but there is no suitable subnet configured for the interface on
which this message has been received. The IPv4 address assigned on this
interface must belong to one of the configured subnets. Otherwise
received message is dropped.
389

390
% DHCP4_PACKET_DROP_0003 %1, from interface %2: it contains a foreign server identifier
391 392
This debug message is issued when received DHCPv4 message is dropped because
it is addressed to a different server, i.e. a server identifier held by
393 394 395
this message doesn't match the identifier used by our server. The arguments
of this message hold the name of the transaction id and interface on which
the message has been received.
396

397
% DHCP4_PACKET_DROP_0004 %1, from interface %2: missing msg-type option
398
This is a debug message informing that incoming DHCPv4 packet did not
399 400 401
have mandatory DHCP message type option and thus was dropped. The
arguments specify the client and transaction identification information,
as well as the interface on which the message has been received.
402

403
% DHCP4_PACKET_DROP_0005 %1: unrecognized type %2 in option 53
404 405 406
This debug message indicates that the message type carried in DHCPv4 option
53 is unrecognized by the server. The valid message types are listed
on the IANA website: http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml#message-type-53.
407 408 409
The message will not be processed by the server. The arguments specify
the client and transaction identification information, as well as the
received message type.
410

411
% DHCP4_PACKET_DROP_0006 %1: unsupported DHCPv4 message type %2
412 413
This debug message indicates that the message type carried in DHCPv4 option
53 is valid but the message will not be processed by the server. This includes
414 415 416
messages being normally sent by the server to the client, such as DHCPOFFER,
DHCPACK, DHCPNAK etc. The first argument specifies the client and transaction
identification information. The second argument specifies the message type.
417

418
% DHCP4_PACKET_DROP_0007 %1: failed to process packet: %2
419 420
This is a general catch-all message indicating that the processing of a
received packet failed.  The reason is given in the message.  The server
421 422 423
will not send a response but will instead ignore the packet. The first
argument contains the client and transaction identification information.
The second argument includes the details of the error.
424

425 426 427 428 429 430
% DHCP4_PACKET_DROP_0008 %1: DHCP service is globally disabled
This debug message is issued when a packet is dropped because the DHCP service
has been temporarily disabled. This affects all received DHCP packets. The
service may be enabled by the "dhcp-enable" control command or automatically
after a specified amount of time since receiving "dhcp-disable" command.

431
% DHCP4_PACKET_NAK_0001 %1: failed to select a subnet for incoming packet, src %2, type %3
432
This error message is output when a packet was received from a subnet
433
for which the DHCPv4 server has not been configured. The most probable
434 435
cause is a misconfiguration of the server. The first argument contains
the client and transaction identification information. The second argument
436
contains the source IPv4 address of the packet. The third argument contains
437
the name of the received packet.
438

439
% DHCP4_PACKET_NAK_0002 %1: invalid address %2 requested by INIT-REBOOT
440
This debug message is issued when the client being in the INIT-REBOOT state
441
requested an IPv4 address which is not assigned to him. The server will respond
442 443
to this client with DHCPNAK. The first argument contains the client and
the transaction identification information. The second arguments holds the
444
IPv4 address requested by the client.
445

446
% DHCP4_PACKET_NAK_0003 %1: failed to advertise a lease, client sent ciaddr %2, requested-ip-address %3
447 448
This message indicates that the server has failed to offer a lease to
the specified client after receiving a DISCOVER message from it. There are
449 450
many possible reasons for such a failure. The first argument contains
the client and the transaction identification information. The second
451 452
argument contains the IPv4 address in the ciaddr field. The third
argument contains the IPv4 address in the requested-ip-address option
453
(if present).
454

455
% DHCP4_PACKET_NAK_0004 %1: failed to grant a lease, client sent ciaddr %2, requested-ip-address %3
456 457 458
This message indicates that the server failed to grant a lease to the
specified client after receiving a REQUEST message from it.  There are many
possible reasons for such a failure. Additional messages will indicate the
459
reason. The first argument contains the client and the transaction
460 461
identification information. The second argument contains the IPv4 address
in the ciaddr field. The third argument contains the IPv4 address in the
462
requested-ip-address option (if present).
463

464 465 466
% DHCP4_PACKET_PACK %1: preparing on-wire format of the packet to be sent
This debug message is issued when the server starts preparing the on-wire
format of the packet to be sent back to the client. The argument specifies
467
the client and the transaction identification information.
468 469 470 471 472 473

% DHCP4_PACKET_PACK_FAIL %1: preparing on-wire-format of the packet to be sent failed %2
This error message is issued when preparing an on-wire format of the packet
has failed. The first argument identifies the client and the DHCP transaction.
The second argument includes the error string.

474 475 476 477 478 479 480 481 482 483 484
% DHCP4_PACKET_PROCESS_EXCEPTION exception occurred during packet processing
This error message indicates that a non-standard exception was raised
during packet processing that was not caught by other, more specific
exception handlers. This packet will be dropped and the server will
continue operation.

% DHCP4_PACKET_PROCESS_STD_EXCEPTION exception occurred during packet processing: %1
This error message indicates that a standard exception was raised
during packet processing that was not caught by other, more specific
exception handlers. This packet will be dropped and the server will
continue operation.
485

486
% DHCP4_PACKET_RECEIVED %1: %2 (type %3) received from %4 to %5 on interface %6
487
A debug message noting that the server has received the specified type of
488 489 490
packet on the specified interface. The first argument specifies the
client and transaction identification information. The second and third
argument specify the name of the DHCPv4 message and its numeric type
491 492
respectively. The remaining arguments specify the source IPv4 address,
destination IPv4 address and the name of the interface on which the
493
message has been received.
494

495
% DHCP4_PACKET_SEND %1: trying to send packet %2 (type %3) from %4:%5 to %6:%7 on interface %8
496 497 498 499 500
The arguments specify the client identification information (HW address
and client identifier), DHCP message name and type, source IPv4
address and port, destination IPv4 address and port and the
interface name.

501
This debug message is issued when the server is trying to send the
Shawn Routhier's avatar
Shawn Routhier committed
502
response to the client. When the server is using an UDP socket
503
to send the packet there are cases when this operation may be
Shawn Routhier's avatar
Shawn Routhier committed
504 505 506
unsuccessful and no error message will be displayed. One such situation
occurs when the server is unicasting the response to the 'ciaddr' of
a DHCPINFORM message. This often requires broadcasting an ARP
507 508
message to obtain the link layer address of the unicast destination.
If broadcast ARP messages are blocked in the network, according to
Shawn Routhier's avatar
Shawn Routhier committed
509 510
the firewall policy, the ARP message will not cause a response.
Consequently, the response to the DHCPINFORM will not be sent.
511 512
Since the ARP communication is under the OS control, Kea is not
notified about the drop of the packet which it is trying to send
Shawn Routhier's avatar
Shawn Routhier committed
513
and it has no means to display an error message.
514

515
% DHCP4_PACKET_SEND_FAIL %1: failed to send DHCPv4 packet: %2
516
This error is output if the DHCPv4 server fails to send an assembled
517 518 519
DHCP message to a client. The first argument includes the client and
the transaction identification information. The second argument includes
the reason for failure.
520

521
% DHCP4_PARSER_COMMIT_EXCEPTION parser failed to commit changes
522
On receipt of message containing details to a change of the DHCPv4
523 524 525 526 527
server configuration, a set of parsers were successfully created, but one
of them failed to commit its changes due to a low-level system exception
being raised.  Additional messages may be output indicating the reason.

% DHCP4_PARSER_COMMIT_FAIL parser failed to commit changes: %1
528
On receipt of message containing details to a change of the DHCPv4
529 530 531 532
server configuration, a set of parsers were successfully created, but
one of them failed to commit its changes.  The reason for the failure
is given in the message.

533
% DHCP4_PARSER_EXCEPTION failed to create or run parser for configuration element %1
534
On receipt of message containing details to a change of its configuration,
535
the DHCPv4 server failed to create a parser to decode the contents of
536 537
the named configuration element, or the creation succeeded but the parsing
actions and committal of changes failed.  The message has been output in
538
response to a non-Kea exception being raised.  Additional messages
539 540
may give further information.

541 542
% DHCP4_PARSER_FAIL failed to create or run parser for configuration element %1: %2
On receipt of message containing details to a change of its configuration,
543
the DHCPv4 server failed to create a parser to decode the contents
544 545 546 547
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.

548 549 550 551 552 553 554
% DHCP4_POST_ALLOCATION_NAME_UPDATE_FAIL %1: failed to update hostname %2 in a lease after address allocation: %3
This message indicates the failure when trying to update the lease and/or
options in the server's response with the hostname generated by the server
or reserved for the client belonging to a shared network. The latter is
the case when the server dynamically switches to another subnet (than
initially selected for allocation) from the same shared network.

555 556 557 558
% DHCP4_QUERY_DATA %1, packet details: %2
A debug message printing the details of the received packet. The first
argument includes the client and the transaction identification
information.
559

560
% DHCP4_RELEASE %1: address %2 was released properly.
561
This informational message indicates that an address was released properly. It
562 563
is a normal operation during client shutdown. The first argument includes
the client and transaction identification information. The second argument
564
includes the released IPv4 address.
565

Jeremy C. Reed's avatar
Jeremy C. Reed committed
566
% DHCP4_RELEASE_EXCEPTION %1: while trying to release address %2 an exception occurred: %3
567
This message is output when an error was encountered during an attempt
568 569
to process a DHCPRELEASE message. The error will not affect the client,
which does not expect any response from the server for DHCPRELEASE
570
messages. Depending on the nature of problem, it may affect future
571 572
server operation. The first argument includes the client and the
transaction identification information. The second argument
573
includes the IPv4 address which release was attempted. The last
574
argument includes the detailed error description.
575

576
% DHCP4_RELEASE_FAIL %1: failed to remove lease for address %2
577 578 579 580 581
This error message indicates that the software failed to remove a
lease from the lease database. It is probably due to an error during a
database operation: resolution will most likely require administrator
intervention (e.g. check if DHCP process has sufficient privileges to
update the database). It may also be triggered if a lease was manually
582 583
removed from the database during RELEASE message processing. The
first argument includes the client and the transaction identification
584
information. The second argument holds the IPv4 address which release
585
was attempted.
586

587 588 589 590
% DHCP4_RELEASE_FAIL_NO_LEASE %1: client is trying to release non-existing lease %2
This debug message is printed when client attempts to release a lease,
but no such lease is known to the server. The first argument contains
the client and transaction identification information. The second
591 592
argument contains the IPv4 address which the client is trying to
release.
593

594 595 596 597 598 599 600
% DHCP4_RELEASE_FAIL_WRONG_CLIENT %1: client is trying to release the lease %2 which belongs to a different client
This debug message is issued when a client is trying to release the
lease for the address which is currently used by another client, i.e.
the 'client identifier' or 'chaddr' doesn't match between the client
and the lease. The first argument includes the client and the
transaction identification information. The second argument specifies
the leased address.
601

602
% DHCP4_RESERVED_HOSTNAME_ASSIGNED %1: server assigned reserved hostname %2
603
This debug message is issued when the server found a hostname reservation
604 605 606 607
for a client and uses this reservation in a hostname option sent back
to this client. The reserved hostname is qualified with a value
of 'qualifying-suffix' parameter, if this parameter is specified.

608 609 610 611 612 613 614
% DHCP4_RESPONSE_DATA %1: responding with packet %2 (type %3), packet details: %4
A debug message including the detailed data about the packet being sent
to the client. The first argument contains the client and the transaction
identification information. The second and third argument contains the
packet name and type respectively. The fourth argument contains detailed
packet information.

615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638
% DHCP4_RESPONSE_FQDN_DATA %1: including FQDN option in the server's response: %2
This debug message is issued when the server is adding the Client FQDN
option in its response to the client. The first argument includes the
client and transaction identification information. The second argument
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.

% DHCP4_RESPONSE_HOSTNAME_DATA %1: including Hostname option in the server's response: %2
This debug message is issued when the server is adding the Hostname
option in its response to the client. The first argument includes the
client and transaction identification information. The second argument
includes the details of the FQDN option being included. Note that the
name carried in the Hostname option may be modified by the server when
the lease is acquired for the client.

% DHCP4_RESPONSE_HOSTNAME_GENERATE %1: server has generated hostname %2 for the client
This debug message includes the auto-generated hostname which will be used
for the client which message is processed. Hostnames may need to be generated
when required by the server's configuration or when the client hasn't
supplied its hostname. The first argument includes the client and the
transaction identification information. The second argument holds the
generated hostname.

639
% DHCP4_SERVER_FAILED server failed: %1
640
The DHCPv4 server has encountered a fatal error and is terminating.
641 642
The reason for the failure is included in the message.

643
% DHCP4_SHUTDOWN server shutdown
644
The DHCPv4 server has terminated normally.
645 646

% DHCP4_SHUTDOWN_REQUEST shutdown of server requested
647
This debug message indicates that a shutdown of the DHCPv4 server has
648 649
been requested via a call to the 'shutdown' method of the core Dhcpv4Srv
object.
650 651

% DHCP4_SRV_CONSTRUCT_ERROR error creating Dhcpv4Srv object, reason: %1
652
This error message indicates that during startup, the construction of a
653
core component within the DHCPv4 server (the Dhcpv4 server object)
654 655
has failed.  As a result, the server will exit.  The reason for the
failure is given within the message.
656

657
% DHCP4_SRV_D2STOP_ERROR error stopping IO with DHCP_DDNS during shutdown: %1
Jeremy C. Reed's avatar
Jeremy C. Reed committed
658
This error message indicates that during shutdown, an error occurred while
659 660 661 662
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.

663 664 665 666 667 668
% DHCP4_SRV_DHCP4O6_ERROR error stopping IO with DHCPv4o6 during shutdown: %1
This error message indicates that during shutdown, an error occurred while
stopping IO between the DHCPv4 server and the DHCPv6o6 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.

669 670 671 672 673
% DHCP4_STARTED Kea DHCPv4 server version %1 started
This informational message indicates that the DHCPv4 server has
processed all configuration information and is ready to process
DHCPv4 packets.  The version is also printed.

674
% DHCP4_STARTING Kea DHCPv4 server version %1 starting
675
This informational message indicates that the DHCPv4 server has
676 677
processed any command-line switches and is starting. The version
is also printed.
678

Tomek Mrugalski's avatar
Tomek Mrugalski committed
679
% DHCP4_START_INFO pid: %1, port: %2, verbose: %3
680
This is a debug message issued during the DHCPv4 server startup.
681 682
It lists some information about the parameters with which the server
is running.
683

684
% DHCP4_SUBNET_DATA %1: the selected subnet details: %2
685
This debug message includes the details of the subnet selected for
686 687 688 689
the client. The first argument includes the client and the
transaction identification information. The second arguments
includes the subnet details.

690 691 692 693 694 695 696 697
% DHCP4_SUBNET_DYNAMICALLY_CHANGED %1: changed selected subnet %2 to subnet %3 from shared network %4 for client assignments
This debug message indicates that the server is using another subnet
than initially selected for client assignments. This newly selected
subnet belongs to the same shared network as the original subnet.
Some reasons why the new subnet was selected include: address pool
exhaustion in the original subnet or the fact that the new subnet
includes some static reservations for this client.

698
% DHCP4_SUBNET_SELECTED %1: the subnet with ID %2 was selected for client assignments
699
This is a debug message noting the selection of a subnet to be used for
700 701 702 703 704 705 706 707 708 709 710 711 712
address and option assignment. Subnet selection is one of the early
steps in the processing of incoming client message. The first
argument includes the client and the transaction identification
information. The second argument holds the selected subnet id.

% DHCP4_SUBNET_SELECTION_FAILED %1: failed to select subnet for the client
This debug message indicates that the server failed to select the
subnet for the client which has sent a message to the server.
The server will not be able to offer any lease to the client and
will drop its message if the received message was DHCPDISCOVER,
and will send DHCPNAK if the received message was DHCPREQUEST.
The argument includes the client and the transaction identification
information.
713 714 715 716

% DHCP6_DHCP4O6_PACKET_RECEIVED received DHCPv4o6 packet from DHCPv6 server (type %1) for %2 on interface %3
This debug message is printed when the server is receiving a DHCPv4o6
from the DHCPv6 server over inter-process communication.