dhcp6_messages.mes 39.7 KB
Newer Older
1
# Copyright (C) 2012-2015  Internet Systems Consortium, Inc. ("ISC")
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
#
# Permission to use, copy, modify, and/or distribute this software for any
# purpose with or without fee is hereby granted, provided that the above
# copyright notice and this permission notice appear in all copies.
#
# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
# AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.

$NAMESPACE isc::dhcp

17 18 19 20 21
% 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.

22 23 24 25 26 27 28 29 30 31
% DHCP6_ALREADY_RUNNING %1 already running? %2
This is an error message that occurs when the DHCPv6 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
the PID file.

32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62
% DHCP6_ADD_GLOBAL_STATUS_CODE %1: adding Status Code to DHCPv6 packet: %2
This message is logged when the server is adding the top-level
Status Code option. The first argument includes the client and the
transaction identification information. The second argument includes
the details of the status code.

% DHCP6_ADD_STATUS_CODE_FOR_IA %1: adding Status Code to IA with iaid=%2: %3
This message is logged when the server is adding the Status Code
option to an IA. The first argument includes the client and the
transaction identification information. The second argument specifies
the IAID. The third argument includes the details of the status code.

% DHCP6_BUFFER_RECEIVED received buffer from %1:%2 to %3:%4 over interface %5
This debug message is logged when the server has received a packet
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
interface and the source and destination addresses/ports.

% DHCP6_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
This debug message is issued when the server starts parsing the received
buffer holding the DHCPv6 message. The arguments specify the source and
destination addresses as well as the interface over which the buffer has
been received.

% DHCP6_BUFFER_WAIT waiting for next DHCPv6 packet with timeout %1 ms
This debug message is issued when the server enters the state when it
waits for new packets. The argument specifies the timeout for the server
to wait for the packet. When this time elapses the server will pass
through its main loop to perform handling of any pending signals
and timers. After that, it will enter the wait state again.

63
% DHCP6_BUFFER_WAIT_INTERRUPTED interrupted wait for the next packet due to timeout, signal or external socket callback (timeout value is %1)
Francis Dupont's avatar
Francis Dupont committed
64
This debug message is issued when the server interrupts waiting
65 66 67 68 69 70
for reception of the next DHCPv6 message due to timeout, signal
or reception of the data over socket other than used for DHCPv6
message transmission. The server will now handle signals
received and ready timers before waiting for next packets again.
The argument specifies the timeout value in milliseconds.

71 72 73 74 75 76 77
% DHCP6_BUFFER_WAIT_SIGNAL signal received while waiting for next packet, next waiting signal is %1
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.

78 79
% DHCP6_CCSESSION_STARTED control channel session started on socket %1
A debug message issued during startup after the IPv6 DHCP server has
80
successfully established a session with the Kea control channel.
81 82 83

% DHCP6_CCSESSION_STARTING starting control channel session, specfile: %1
This debug message is issued just before the IPv6 DHCP server attempts
84
to establish a session with the Kea control channel.
85

86 87
% DHCP6_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1
This debug message informs that incoming packet has been assigned to specified
Francis Dupont's avatar
Francis Dupont committed
88
class or classes.
89

90 91
% DHCP6_COMMAND_RECEIVED received command %1, arguments: %2
A debug message listing the command (and possible arguments) received
92
from the Kea control system by the IPv6 DHCP server.
93

94 95 96 97 98 99
% DHCP6_CONFIG_COMPLETE DHCPv6 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.

100 101 102 103 104
% DHCP6_CONFIG_LOAD_FAIL configuration error using file: %1, reason: %2
This error message indicates that the DHCPv6 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.
105 106 107 108 109 110

% DHCP6_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 subnet.

% DHCP6_CONFIG_OPTION_DUPLICATE multiple options with the code: %1 added to the subnet: %2
111
This warning message is issued on an attempt to configure multiple options with the
112
same option code for the particular subnet. Adding multiple options is uncommon
113
for DHCPv6, but it is not prohibited.
114

115 116 117 118
% DHCP6_CONFIG_RECEIVED received configuration: %1
A debug message listing the configuration received by the DHCPv6 server.
The source of that configuration depends on used configuration backend.

119 120 121 122 123
% DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1
This is a debug message that is issued every time the server receives a
configuration. That happens start up and also when a server configuration
change is committed by the administrator.

124 125
% DHCP6_CONFIG_UPDATE updated configuration received: %1
A debug message indicating that the IPv6 DHCP server has received an
126
updated configuration from the Kea configuration system.
127

128
% DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2)
129 130 131
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.
132

133 134 135 136
% DHCP6_DDNS_CREATE_ADD_NAME_CHANGE_REQUEST created name change request: %1
This debug message is logged when the new Name Change Request has been created
to perform the DNS Update, which adds new RRs.

137
% DHCP6_DDNS_CREATE_REMOVE_NAME_CHANGE_REQUEST %1: created name change request: %2
138
This debug message is logged when the new Name Change Request has been created
139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157
to perform the DNS Update, which removes RRs from the DNS. The first argument
includes the client and transaction identification information. The second
argument specifies the details of the generated name change request.

% DHCP6_DDNS_FQDN_GENERATED %1: generated FQDN for the client: %2
This debug message is logged when the server generated FQDN (name)
for the client which message is processed. The names may be
generated by the server when required by the server's policy or
when the client doesn't provide any specific FQDN in its message
to the server. The first argument includes the client and
transaction identification information. The second argument includes
the generated FQDN.

% DHCP6_DDNS_GENERATED_FQDN_UPDATE_FAIL %1: failed to update the lease using address %2, after generating FQDN for a client, reason: %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
from the acquired address. The first argument includes the client and the
transaction identification information. The second argument is a leased
address. The third argument includes the reason for the failure.
158

159
% DHCP6_DDNS_LEASE_ASSIGN_FQDN_CHANGE FQDN %1: FQDN for the allocated lease: %2 has changed. New values: hostname = %3, reverse mapping = %4, forward mapping = %5
160 161
This debug message is logged when FQDN mapping for a particular lease has
been changed by the recent Request message. This mapping will be changed in DNS.
162 163 164 165
The first argument includes the client and the transaction identification
information. The second argument holds the details about the lease for which
the FQDN information and/or mappings have changed. The remaining arguments
hold the new FQDN information and flags for mappings.
166

167
% DHCP6_DDNS_LEASE_RENEW_FQDN_CHANGE FQDN %1: FQDN for the renewed lease: %2 has changed. New values: hostname = %3, reverse mapping = %4, forward mapping = %5
168 169
This debug message is logged when FQDN mapping for a particular lease has been
changed by the recent Renew message. This mapping will be changed in DNS.
170 171 172 173
The first argument includes the client and the transaction identification
information. The second argument holds the details about the lease for which
the FQDN information and/or mappings have changed. The remaining arguments
hold the new FQDN information and flags for mappings.
174

175
% DHCP6_DDNS_RECEIVE_FQDN %1: received DHCPv6 Client FQDN option: %2
176
This debug message is logged when server has found the DHCPv6 Client FQDN Option
177 178 179
sent by a client and started processing it. The first argument includes the
client and transaction identification information. The second argument
includes the received FQDN.
180

181
% DHCP6_DDNS_REMOVE_INVALID_HOSTNAME %1: invalid FQDN %2 for the lease: %3 when removing DNS bindings
182 183 184
This error message is issued when a lease being deleted contains an indication
that the DNS Update has been performed for it, but the FQDN held in the lease
database has invalid format and can't be transformed to the canonical on-wire
185 186
format. The first argument includes the client and transaction identification
information.
187

188
% DHCP6_DDNS_REQUEST_SEND_FAILED failed sending a request to kea-dhcp-ddns, error: %1,  ncr: %2
189
This error message indicates that IPv6 DHCP server failed to send a DDNS
Francis Dupont's avatar
Francis Dupont committed
190
update request to the DHCP-DDNS server. This is most likely a configuration or
191 192
networking error.

193 194 195 196 197 198 199 200
% DHCP6_DDNS_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.

201 202 203 204
% 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.

205
% DHCP6_DDNS_SKIP_REMOVE_NAME_CHANGE_REQUEST %1: name change request creation skipped for lease: %2
206 207 208 209 210 211 212
This debug message is logged when the server determines that removal
name change request should not be sent to the DNS, because the DNS
updates are disabled on the DHCP server, or no DNS update has been
performed for the processed lease. The first argument includes the
client and the transaction identification information. The second
argument provides the details of the lease.

213 214 215 216
% 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.
217

Francis Dupont's avatar
Francis Dupont committed
218
% DHCP6_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: %1, after receiving SIGHUP signal
219 220 221
This is the info message logged when the DHCPv6 server starts reconfiguration
as a result of receiving SIGHUP signal.

222
% DHCP6_DYNAMIC_RECONFIGURATION_FAIL dynamic server reconfiguration failed with file: %1
223 224 225
This is an error message logged when the dynamic reconfiguration of the
DHCP server failed.

226
% DHCP6_EXTEND_NA_UNKNOWN %1: received unknown IA_NA with iaid=%2 in subnet %3
227 228 229 230 231 232 233
This warning message is printed when client attempts to extend the lease
for the address (in the IA_NA option) but no such lease is known by the server.
It typically means that client has attempted to use its lease past its
lifetime: causes of this include a adjustment of the client's date/time
setting or poor support on the client for sleep/recovery. A properly
implemented client will recover from such a situation by restarting the
lease allocation process after receiving a negative reply from the server.
234 235 236
The first argument includes the client and the transaction identification
information. The second argument holds IAID. The third argument holds the
subnet information.
237 238 239 240 241 242 243

An alternative cause could be that the server has lost its database
recently and does not recognize its well-behaving clients. This is more
probable if you see many such messages. Clients will recover from this,
but they will most likely get a different IP addresses and experience
a brief service interruption.

244 245 246 247 248
% DHCP6_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.

249
% DHCP6_HOOK_BUFFER_RCVD_SKIP received buffer from %1 to %2 over interface %3 was dropped because a callout set the skip flag
250 251 252
This debug message is printed when a callout installed on buffer6_receive
hook point set the skip flag. For this particular hook point, the
setting of the flag by a callout instructs the server to drop the packet.
253 254
The arguments specify the source and destination address as well as
the name of the interface over which the buffer has been received.
255

256
% DHCP6_HOOK_BUFFER_SEND_SKIP %1: prepared DHCPv6 response was dropped because a callout set the skip flag
257
This debug message is printed when a callout installed on buffer6_send
258 259 260 261
hook point set the skip flag. For this particular hook point, the
setting of the flag by a callout instructs the server to drop the packet.
Server completed all the processing (e.g. may have assigned, updated
or released leases), but the response will not be send to the client.
262 263
The argument includes the client and transaction identification
information.
264

265
% DHCP6_HOOK_LEASE6_RELEASE_NA_SKIP %1: DHCPv6 address lease was not released because a callout set the skip flag
266 267 268 269 270
This debug message is printed when a callout installed on the
lease6_release hook point set the skip flag. For this particular hook
point, the setting of the flag by a callout instructs the server to not
release a lease. If a client requested the release of multiples leases
(by sending multiple IA options), the server will retain this particular
271 272
lease and proceed with other releases as usual. The argument holds the
client and transaction identification information.
273

274
% DHCP6_HOOK_LEASE6_RELEASE_PD_SKIP %1: prefix lease was not released because a callout set the skip flag
275 276 277 278 279
This debug message is printed when a callout installed on lease6_release
hook point set the skip flag. For this particular hook point, the
setting of the flag by a callout instructs the server to not release
a lease. If client requested release of multiples leases (by sending
multiple IA options), the server will retains this particular lease and
280 281
will proceed with other renewals as usual. The argument holds the
client and transaction identification information.
282

283
% DHCP6_HOOK_PACKET_RCVD_SKIP %1: packet is dropped, because a callout set the skip flag.
284
This debug message is printed when a callout installed on the pkt6_receive
285 286
hook point sets the skip flag. For this particular hook point, the
setting of the flag instructs the server to drop the packet.
287

288
% DHCP6_HOOK_PACKET_SEND_SKIP %1: prepared DHCPv6 response was not sent because a callout set the skip flag
289
This debug message is printed when a callout installed on the pkt6_send
290
hook point set the skip flag. For this particular hook point, the setting
291 292 293
of the flag by a callout instructs the server to drop the packet. This
effectively means that the client will not get any response, even though
the server processed client's request and acted on it (e.g. possibly
294 295
allocated a lease). The argument specifies the client and transaction
identification information.
296

297
% DHCP6_HOOK_SUBNET6_SELECT_SKIP %1: no subnet was selected because a callout set the skip flag
298
This debug message is printed when a callout installed on the
299
subnet6_select hook point set the skip flag. For this particular hook
300 301 302
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 or prefixes
303 304
will be assigned. The argument holds the client and transaction
identification information.
305

306 307
% DHCP6_INIT_FAIL failed to initialize Kea server: %1
The server has failed to establish communication with the rest of Kea,
Francis Dupont's avatar
Francis Dupont committed
308
failed to read JSON configuration file or encountered any other critical
309 310 311
issue that prevents it from starting up properly. Attached error message
provides more details about the issue.

312 313 314 315 316 317 318
% DHCP6_LEASE_ADVERT %1: lease for address %2 and iaid=%3 will be advertised
This debug message indicates that the server will advertise an
address to the client in the ADVERTISE message. The client will
request allocation of this address with the REQUEST message sent
in the next message exchange. The first argument includes the client
and transaction identification information. The remaining arguments
hold the allocated address and IAID.
319

320
% DHCP6_LEASE_ADVERT_FAIL %1: failed to advertise an address lease for iaid=%2
321 322 323
This message indicates that in response to a received SOLICIT, the server
failed to advertise a non-temporary lease for a given client. There may
be many reasons for such failure. Each failure is logged in a separate
324 325
log entry. The first argument holds the client and transaction identification
information. The second argument holds the IAID.
326

327
% DHCP6_LEASE_ALLOC %1: lease for address %2 and iaid=%3 has been allocated
328 329 330
This debug message indicates that in response to a client's REQUEST
message, the server successfully granted an non-temporary address
lease. This is a normal behavior and indicates successful operation.
331 332 333
The first argument includes the client and transaction identification
information. The remaining arguments hold the allocated address and
IAID.
334

335
% DHCP6_LEASE_ALLOC_FAIL %1: failed to grant an address lease for iaid=%2
336 337 338
This message indicates that in response to a received REQUEST, the server
failed to grant a non-temporary address lease for the client. There may
be many reasons for such failure. Each failure is logged in a separate
339 340 341 342 343 344 345 346 347
log entry. The first argument holds the client and transaction identification
information. The second argument holds the IAID.

% DHCP6_LEASE_DATA %1: detailed lease information for iaid=%2: %3
This debug message is used to print the detailed information about the
allocated lease or a lease which will be advertised to the client.
The first argument holds the client and the transaction identification
information. The second argument holds the IAID. The third argument
holds the detailed lease information.
348

349
% DHCP6_LEASE_DATABASE_TIMERS_EXEC_FAIL failed to execute timer-based functions for lease database: %1
350 351 352 353 354 355
A warning message executed when a server process is unable to execute
the periodic actions for the lease database. An example of the periodic
action is a Lease File Cleanup. One of the reasons for the failure is
a misconfiguration of the lease database, whereby the lease database
hasn't been selected.

356
% DHCP6_LEASE_NA_WITHOUT_DUID %1: address lease for address %2 does not have a DUID
357
This error message indicates a database consistency problem. The lease
358 359 360
database has an entry indicating that the given address is in use,
but the lease does not contain any client identification. This is most
likely due to a software error: please raise a bug report. As a temporary
361 362 363
workaround, manually remove the lease entry from the database. The first
argument includes the client and transaction identification information.
The second argument holds the address to be released.
Tomek Mrugalski's avatar
Tomek Mrugalski committed
364

365
% DHCP6_LEASE_PD_WITHOUT_DUID %1: lease for prefix %2/%3 does not have a DUID
366 367 368 369
This error message indicates a database consistency failure. The lease
database has an entry indicating that the given prefix is in use,
but the lease does not contain any client identification. This is most
likely due to a software error: please raise a bug report. As a temporary
370 371 372 373
workaround, manually remove the lease entry from the database. The
first argument includes client and transaction identification
information. The second and third argument hold the prefix and the
prefix length.
374

375 376 377 378 379 380 381 382
% DHCP6_NOT_RUNNING IPv6 DHCP server is not running
A warning message is issued when an attempt is made to shut down the
IPv6 DHCP server but it is not running.

% DHCP6_NO_INTERFACES failed to detect any network interfaces
During startup the IPv6 DHCP server failed to detect any network
interfaces and is therefore shutting down.

383 384 385 386 387
% 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.

388 389 390 391
% DHCP6_OPEN_SOCKET opening sockets on port %1
A debug message issued during startup, this indicates that the IPv6 DHCP
server is about to open sockets on the specified port.

392
% DHCP6_OPEN_SOCKET_FAIL failed to open socket: %1
393 394 395
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.

Francis Dupont's avatar
Francis Dupont committed
396
% DHCP6_PACKET_DROP_PARSE_FAIL failed to parse packet from %1 to %2, received over interface %3, reason: %4
397 398 399 400
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.

% DHCP6_PACKET_DROP_SERVERID_MISMATCH %1: dropping packet with server identifier: %2, server is using: %3
401 402 403
A debug message noting that server has received message with server identifier
option that not matching server identifier that server is using.

404 405 406 407 408
% DHCP6_PACKET_DROP_UNICAST %1: dropping unicast %2 packet as this packet should be sent to multicast
This debug message is issued when the server drops the unicast packet,
because packets of this type must be sent to multicast. The first argument
specifies the client and transaction identification information, the
second argument specifies packet type.
409

410 411 412 413 414
% DHCP6_PACKET_PROCESS_FAIL processing of %1 message received from %2 failed: %3
This is a general catch-all message indicating that the processing of the
specified packet type from the indicated address failed.  The reason is given in the
message.  The server will not send a response but will instead ignore the packet.

415 416 417 418 419 420 421 422
% DHCP6_PACKET_RECEIVED %1: %2 (type %3) received from %4 to %5 on interface %6
A debug message noting that the server has received the specified type of
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 DHCPv6 message and its numeric type
respectively. The remaining arguments specify the source address,
destination IP address and the name of the interface on which the
message has been received.
423

424 425
% DHCP6_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1
The IPv6 DHCP server tried to receive a packet but an error
426
occurred during this attempt. The reason for the error is included in
427 428
the message.

Marcin Siodelski's avatar
Marcin Siodelski committed
429
% DHCP6_PACKET_SEND_FAIL failed to send DHCPv6 packet: %1
430 431 432
This error is output if the IPv6 DHCP server fails to send an assembled
DHCP message to a client. The reason for the error is included in the
message.
433

434 435
% DHCP6_PACK_FAIL failed to assemble response correctly
This error is output if the server failed to assemble the data to be
436 437
returned to the client into a valid packet.  The reason is most likely
to be to a programming error: please raise a bug report.
438

439 440 441 442 443 444 445 446 447 448 449 450
% DHCP6_PARSER_COMMIT_EXCEPTION parser failed to commit changes
On receipt of message containing details to a change of the IPv6 DHCP
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.

% DHCP6_PARSER_COMMIT_FAIL parser failed to commit changes: %1
On receipt of message containing details to a change of the IPv6 DHCP
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.

451
% DHCP6_PARSER_CREATED created parser for configuration element %1
452 453
A debug message output during a configuration update of the IPv6 DHCP
server, notifying that the parser for the specified configuration element
454
has been successfully created.
455

456
% DHCP6_PARSER_EXCEPTION failed to create or run parser for configuration element %1
457
On receipt of message containing details to a change of its configuration,
458 459 460
the IPv6 DHCP 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 message has been output in
461
response to a non-Kea exception being raised.  Additional messages
462 463
may give further information.

464 465
The most likely cause of this is that the specification file for the
server (which details the allowable contents of the configuration) is
466 467
not correct for this version of Kea.  This may be the result of an
interrupted installation of an update to Kea.
468

469 470 471 472 473 474 475
% DHCP6_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,
the IPv6 DHCP 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.

476 477 478 479 480 481 482
% DHCP6_PD_LEASE_ADVERT %1: lease for prefix %2/%3 and iaid=%4 will be advertised
This debug message indicates that the server will advertise a
prefix to the client in the ADVERTISE message. The client will
request allocation of this prefix with the REQUEST message sent
in the next message exchange. The first argument includes the client
and transaction identification information. The remaining arguments
hold the allocated prefix, prefix length and IAID.
483

484
% DHCP6_PD_LEASE_ADVERT_FAIL %1: failed to advertise a prefix lease for iaid=%2
485
This message indicates that in response to a received SOLICIT, the
486
server failed to advertise a prefix lease for a given client. There may
487
be many reasons for such failure. Each failure is logged in a separate
488 489
log entry. The first argument holds the client and transaction identification
information. The second argument holds the IAID.
490

491
% DHCP6_PD_LEASE_ALLOC %1: lease for prefix %2/%3 and iaid=%4 has been allocated
492
This debug message indicates that in response to a client's REQUEST
493 494 495 496
message, the server successfully granted an non-temporary address
lease. This is a normal behavior and indicates successful operation.
The first argument includes the client and transaction identification
information. The remaining arguments hold the allocated prefix,
Francis Dupont's avatar
Francis Dupont committed
497
prefix length and and IAID.
498

499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518
% DHCP6_PD_LEASE_ALLOC_FAIL %1: failed to grant a prefix lease for iaid=%2
This message indicates that in response to a received REQUEST, the server
failed to grant a prefix lease for the client. There may be many reasons
for such failure. Each failure is logged in a separate log entry. The first
argument holds the client and transaction identification information.
The second argument holds the IAID.

% DHCP6_PROCESS_IA_NA_EXTEND %1: extending lease lifetime for IA_NA option with iaid=%2
This message is logged when the server is starting to extend the lifetime
of the address lease associated with the particular IAID. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.

% DHCP6_PROCESS_IA_NA_RELEASE %1: releasing lease for IA_NA option with iaid=%2
This message is logged when the server is trying to release the client's
as a result of receiving the RELEASE message. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.

% DHCP6_PROCESS_IA_NA_REQUEST %1: server is processing IA_NA option with iaid=%2 and hint=%3
519
This is a debug message that indicates the processing of a received
520 521 522 523 524 525 526 527 528 529 530 531 532 533
IA_NA option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
IA_NA option. The third argument may hold the hint for the server
about the address that the client would like to have allocated.
If there is no hint, the argument should provide the text indicating
that the hint hasn't been sent.

% DHCP6_PROCESS_IA_PD_EXTEND %1: extending lease lifetime for IA_PD option with iaid=%2
This message is logged when the server is starting to extend the lifetime
of the prefix lease associated with the particular IAID. The first argument
includes the client and transaction identification information. The second
argument contains the IAID.

% DHCP6_PROCESS_IA_PD_REQUEST %1: server is processing IA_PD option with iaid=%2 and hint=%3
534
This is a debug message that indicates a processing of received IA_PD
535 536 537 538 539 540 541 542 543 544 545 546
option. The first argument contains the client and the transaction
identification information. The second argument holds the IAID of the
IA_PD option. The third argument may hold the hint for the server
about the prefix that the client would like to have allocated.
If there is no hint, the argument should provide the text indicating
that the hint hasn't been sent.

% DHCP6_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.

547
% DHCP6_RAPID_COMMIT %1: Rapid Commit option received, following 2-way exchange
Francis Dupont's avatar
Francis Dupont committed
548
This debug message is issued when the server found a Rapid Commit option
549 550
in the client's message and 2-way exchanges are supported by the
server for the subnet on which the client is connected. The argument
551 552
specifies the client and transaction identification information.

553
% DHCP6_RELEASE_NA %1: binding for address %2 and iaid=%3 was released properly
554 555 556
This debug message indicates that an address was released properly. It
is a normal operation during client shutdown.

557
% DHCP6_RELEASE_NA_FAIL %1: failed to remove address lease for address %2 and iaid=%3
558
This error message indicates that the software failed to remove an address
559 560 561 562
lease from the lease database.  It 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
563 564 565 566
removed from the database during RELEASE message processing. The first
argument holds the client and transaction identification information.
The second and third argument hold the released address and IAID
respectively.
567

568
% DHCP6_RELEASE_NA_FAIL_WRONG_DUID %1: client tried to release address %2, but it belongs to another client using duid=%3
569 570 571 572 573 574
This warning message indicates that a client tried to release an address
that belongs to a different client. This should not happen in normal
circumstances and may indicate a misconfiguration of the client.  However,
since the client releasing the address will stop using it anyway, there
is a good chance that the situation will correct itself.

575
% DHCP6_RELEASE_NA_FAIL_WRONG_IAID %1: client tried to release address %2, but it used wrong IAID (expected %3, but got %4)
576 577 578 579 580
This warning message indicates that client tried to release an address
that does belong to it, but the address was expected to be in a different
IA (identity association) container. This probably means that the client's
support for multiple addresses is flawed.

581
% DHCP6_RELEASE_PD %1: prefix %2/%3 for iaid=%4 was released properly
582
This debug message indicates that a prefix was released properly. It
583 584
is a normal operation during client shutdown. The first argument holds
the client and transaction identification information. The second and
585
third argument define the prefix and its length. The fourth argument
586
holds IAID.
587

588
% DHCP6_RELEASE_PD_FAIL %1: failed to release prefix %2/%3 for iaid=%4
589 590 591 592 593
This error message indicates that the software failed to remove a prefix
lease from the lease database.  It 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
594 595 596
removed from the database during RELEASE message processing. The
first argument hold the client and transaction identification
information. The second and third argument define the prefix and
597
its length. The fourth argument holds the IAID.
598

599
% DHCP6_RELEASE_PD_FAIL_WRONG_DUID %1: client tried to release prefix %2/%3, but it belongs to another client (duid=%4)
600 601 602 603
This warning message indicates that client tried to release a prefix
that belongs to a different client. This should not happen in normal
circumstances and may indicate a misconfiguration of the client.  However,
since the client releasing the prefix will stop using it anyway, there
604 605 606 607 608
is a good chance that the situation will correct itself. The first
argument includes the client and the transaction identification
information. The second and third argument include the prefix and
prefix length. The last argument holds the DUID of the client holding
the lease.
609

610
% DHCP6_RELEASE_PD_FAIL_WRONG_IAID %1: client tried to release prefix %2/%3, but it used wrong IAID (expected %4, but got %5)
611 612 613
This warning message indicates that client tried to release a prefix
that does belong to it, but the address was expected to be in a different
IA (identity association) container. This probably means that the client's
614 615
support for multiple prefixes is flawed. The first argument includes the
client and transaction identification information. The second and third
616
argument identify the prefix. The fourth and fifth argument hold the
617
expected IAID and IAID found respectively.
618

Jeremy C. Reed's avatar
Jeremy C. Reed committed
619 620 621 622 623 624 625
% DHCP6_REQUIRED_OPTIONS_CHECK_FAIL %1 message received from %2 failed the following check: %3
This message indicates that received DHCPv6 packet is invalid.  This may be due
to a number of reasons, e.g. the mandatory client-id option is missing,
the server-id forbidden in that particular type of message is present,
there is more than one instance of client-id or server-id present,
etc. The exact reason for rejecting the packet is included in the message.

626
% DHCP6_RESPONSE_DATA responding with packet type %1 data is %2
627 628
A debug message listing the data returned to the client.

629
% DHCP6_SERVERID_GENERATED server-id %1 has been generated and will be stored in %2
630
This informational messages indicates that the server was not able to read
631 632 633 634 635 636 637 638 639 640 641 642 643
its server identifier (DUID) and has generated a new one. This server-id
will be stored in a file and will be read and used during next restart. It
is normal behavior when the server is started for the first time. If
this message is printed every start, please check that the server have
sufficient permission to write its server-id file and that the file is not
corrupt.

Changing the server identifier in a production environment is not
recommended as existing clients will not recognize the server and may go
through a rebind phase. However, they should be able to recover without
losing their leases.

% DHCP6_SERVERID_LOADED server-id %1 has been loaded from file %2
644
This debug message indicates that the server loaded its server identifier.
645 646 647 648 649 650 651
That value is sent in all server responses and clients use it to
discriminate between servers. This is a part of normal startup or
reconfiguration procedure.

% DHCP6_SERVERID_WRITE_FAIL server was not able to write its ID to file %1
This warning message indicates that server was not able to write its
server identifier (DUID) to a file. This likely indicates lack of write
652
permission to a given file or directory. This is not critical and the
653 654 655
server will continue to operate, but server will generate different DUID
during every start and clients will need to go through a rebind phase
to recover.
656

657 658 659 660
% DHCP6_SERVER_FAILED server failed: %1
The IPv6 DHCP server has encountered a fatal error and is terminating.
The reason for the failure is included in the message.

661 662 663 664 665 666 667 668
% DHCP6_SHUTDOWN server shutdown
The IPv6 DHCP server has terminated normally.

% DHCP6_SHUTDOWN_REQUEST shutdown of server requested
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.

669 670 671
% 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.

672 673 674 675 676 677 678 679 680 681 682 683
% 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)
has failed.  As a result, the server will exit.  The reason for the
failure is given within the message.

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

684 685 686 687 688
% 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
DHCPv6 packets.  The version is also printed.

689
% DHCP6_STARTING Kea DHCPv6 server version %1 starting
690
This informational message indicates that the IPv6 DHCP server has
691 692
processed any command-line switches and is starting. The version
is also printed.
693

Tomek Mrugalski's avatar
Tomek Mrugalski committed
694
% DHCP6_START_INFO pid: %1, port: %2, verbose: %3
695 696 697
This is a debug message issued during the IPv6 DHCP server startup.
It lists some information about the parameters with which the server
is running.
698

699 700 701
% DHCP6_SUBNET_DATA %1: the selected subnet details: %2
This debug message includes the details of the subnet selected for
the client. The first argument includes the client and the
702
transaction identification information. The second argument
703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718
includes the subnet details.

% DHCP6_SUBNET_SELECTED %1: the subnet with ID %2 was selected for client assignments
This is a debug message noting the selection of a subnet to be used for
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.

% DHCP6_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 cause is likely due to a misconfiguration of the server. The packet
processing will continue, but the response will only contain generic
configuration and no addresses or prefixes. The argument includes
the client and the transaction identification information.
719

Tomek Mrugalski's avatar
Tomek Mrugalski committed
720 721 722 723
% DHCP6_UNKNOWN_MSG_RECEIVED received unknown message (type %d) on interface %2
This debug message is printed when server receives a message of unknown type.
That could either mean missing functionality or invalid or broken relay or client.
The list of formally defined message types is available here:
724
http://www.iana.org/assignments/dhcpv6-parameters.