dhcp4_messages.mes 21.9 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
% 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.

22
% DHCP4_CCSESSION_STARTED control channel session started on socket %1
23
A debug message issued during startup after the DHCPv4 server has
24
successfully established a session with the Kea control channel.
25
26

% DHCP4_CCSESSION_STARTING starting control channel session, specfile: %1
27
This debug message is issued just before the DHCPv4 server attempts
28
to establish a session with the Kea control channel.
29

30
31
% DHCP4_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
32
class or classes. This is a normal behavior and indicates successful operation.
33

34
35
36
37
% DHCP4_CLIENT_NAME_PROC_FAIL failed to process the fqdn or hostname sent by a client: %1
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
name was malformed or due to internal server error.
38

39
% DHCP4_COMMAND_RECEIVED received command %1, arguments: %2
40
A debug message listing the command (and possible arguments) received
41
from the Kea control system by the DHCPv4 server.
42

43
44
45
46
47
48
% 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.

49
50
51
52
53
% 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.
54

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

59
60
61
62
% 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.
63

64
65
66
67
% 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.

68
69
% 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
70
configuration. That happens at start up and also when a server configuration
71
72
change is committed by the administrator.

73
% DHCP4_CONFIG_UPDATE updated configuration received: %1
74
A debug message indicating that the DHCPv4 server has received an
75
updated configuration from the Kea configuration system.
76

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

82
83
84
85
86
% 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.

87
88
89
90
91
% DHCP4_DHCID_COMPUTE_ERROR failed to compute the DHCID for lease: %1, reason: %2
This error message is logged when the attempt to compute DHCID for a specified
lease has failed. The lease details and reason for failure is logged in the
message.

92
93
94
95
% DHCP4_DISCOVER_CLASS_PROCESSING_FAILED client class specific processing failed for DHCPDISCOVER
This debug message means that the server processing that is unique for each
client class has reported a failure. The response packet will not be sent.

Francis Dupont's avatar
Francis Dupont committed
96
% DHCP4_DYNAMIC_RECONFIGURATION initiate server reconfiguration using file: %1, after receiving SIGHUP signal
97
98
99
100
101
102
103
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.

104
105
106
107
108
% DHCP4_EMPTY_HOSTNAME received empty hostname from the client, skipping processing of this option
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
option is skipped.

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

114
115
116
117
118
119
120
121
122
123
124
125
% DHCP4_HOOK_BUFFER_RCVD_SKIP received DHCPv4 buffer was dropped because a callout set the skip flag.
This debug message is printed when a callout installed on buffer4_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.

% DHCP4_HOOK_BUFFER_SEND_SKIP prepared DHCPv4 response was dropped because a callout set the skip flag.
This debug message is printed when a callout installed on buffer4_send
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.

Tomek Mrugalski's avatar
Tomek Mrugalski committed
126
% DHCP4_HOOK_LEASE4_RELEASE_SKIP DHCPv4 lease was not released because a callout set the skip flag.
127
128
129
This debug message is printed when a callout installed on lease4_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
Tomek Mrugalski's avatar
Tomek Mrugalski committed
130
a lease.
131

132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
% DHCP4_HOOK_PACKET_RCVD_SKIP received DHCPv4 packet was dropped, because a callout set the skip flag.
This debug message is printed when a callout installed on the pkt4_receive
hook point sets the skip flag. For this particular hook point, the
setting of the flag instructs the server to drop the packet.

% DHCP4_HOOK_PACKET_SEND_SKIP prepared DHCPv6 response was not sent, because a callout set skip flag.
This debug message is printed when a callout installed on the pkt4_send
hook point sets the skip flag. For this particular hook point, the setting
of the flag instructs the server to drop the packet. This means that
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).

% DHCP4_HOOK_SUBNET4_SELECT_SKIP no subnet was selected, because a callout set skip flag.
This debug message is printed when a callout installed on the
subnet4_select hook point sets the skip flag. For this particular hook
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.
150

151
152
153
154
% DHCP4_INFORM_CLASS_PROCESSING_FAILED client class specific processing failed for DHCPINFORM
This debug message means that the server processing that is unique for each
client class has reported a failure. The response packet will not be sent.

155
156
157
158
159
% 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.

160
% DHCP4_INVALID_ADDRESS_INIT_REBOOT invalid address %1 requested by INIT-REBOOT client (id: %2, hwaddr: %3)
161
162
163
164
This debug message is issued when the client being in the INIT-REBOOT state
requested an address which is not assigned to him. The server will respond
to this client with DHCPNAK.

165
% DHCP4_LEASE_ADVERT lease %1 advertised (client client-id %2, hwaddr %3)
166
This debug message indicates that the server successfully advertised
Francis Dupont's avatar
Francis Dupont committed
167
a lease. It is up to the client to choose one server out of other advertised
168
169
170
and continue allocation with that server. This is a normal behavior and
indicates successful operation.

171
% DHCP4_LEASE_ADVERT_FAIL failed to advertise a lease for client-id %1, hwaddr %2, client sent ciaddr %3, requested-ip-address %4
172
173
174
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
many possible reasons for such a failure.
175

176
177
178
% DHCP4_LEASE_ALLOC lease %1 has been allocated for client-id %2, hwaddr %3
This debug message indicates that the server successfully granted a lease
in response to client's REQUEST message. This is a normal behavior and
179
indicates successful operation.
180

181
% DHCP4_LEASE_ALLOC_FAIL failed to grant a lease for client-id %1, hwaddr %2, client sent ciaddr %3, requested-ip-address %4
182
183
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
184
185
possible reasons for such a failure. Additional messages will indicate the
reason.
186

187
% DHCP4_LEASE_DATABASE_TIMERS_EXEC_FAIL failed to execute timer-based functions for lease database: %1
188
189
190
191
192
193
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.

194
195
196
197
198
199
% DHCP4_NAME_GEN_UPDATE_FAIL failed to update the lease after generating name for a client: %1
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 message argument indicates the reason for the
failure.

200
% DHCP4_NCR_CREATION_FAILED failed to generate name change requests for DNS: %1
201
This message indicates that server was unable to generate NameChangeRequests
202
which should be sent to the kea-dhcp_ddns module to create
203
204
205
206
new DNS records for the lease being acquired or to update existing records
for the renewed lease. The reason for the failure is printed in the logged
message.

207
208
209
210
% 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.

211
212
213
214
% DHCP4_NO_LEASE_INIT_REBOOT no lease for address %1 requested by INIT-REBOOT client (id: %2, hwaddr: %3)
This debug message is issued when the client being in the INIT-REBOOT state
requested an address but this client is unknown. The server will not respond.

215
216
217
218
219
% 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.

220
% DHCP4_NO_SUBNET_FOR_DIRECT_CLIENT no suitable subnet configured for a direct client sending packet with transaction id %1, on interface %2, received message is dropped
Francis Dupont's avatar
Francis Dupont committed
221
This info message is logged when received a message from a directly connected
222
223
224
225
226
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.

227
% DHCP4_OPEN_SOCKET opening sockets on port %1
228
A debug message issued during startup, this indicates that the DHCPv4
229
server is about to open sockets on the specified port.
230

231
% DHCP4_OPEN_SOCKET_FAIL failed to open socket: %1
232
233
234
235
236
237
238
A warning message issued when IfaceMgr fails to open and bind a socket. The reason
for the failure is appended as an argument of the log message.

% DHCP4_PACKET_DROP_NO_TYPE packet received on interface %1 dropped, because of missing msg-type option
This is a debug message informing that incoming DHCPv4 packet did not
have mandatory DHCP message type option and thus was dropped.

239
% DHCP4_PACKET_NOT_FOR_US received DHCPv4 message (transid=%1, iface=%2) dropped because it contains foreign server identifier
240
241
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
242
243
244
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.
245

246
% DHCP4_PACKET_PARSE_FAIL failed to parse incoming packet: %1
247
The DHCPv4 server has received a packet that it is unable to
248
interpret. The reason why the packet is invalid is included in the message.
249

250
% DHCP4_PACKET_PROCESS_FAIL failed to process packet received from %1: %2
251
252
253
254
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
will not send a response but will instead ignore the packet.

255
% DHCP4_PACKET_RECEIVED %1 (type %2) packet received on interface %3
256
257
258
259
A debug message noting that the server has received the specified type of
packet on the specified interface.  Note that a packet marked as UNKNOWN
may well be a valid DHCP packet, just a type not expected by the server
(e.g. it will report a received OFFER packet as UNKNOWN).
260

261
% DHCP4_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1
262
The DHCPv4 server tried to receive a packet but an error
263
occurred during this attempt. The reason for the error is included in
264
265
the message.

Marcin Siodelski's avatar
Marcin Siodelski committed
266
% DHCP4_PACKET_SEND_FAIL failed to send DHCPv4 packet: %1
267
This error is output if the DHCPv4 server fails to send an assembled
268
269
DHCP message to a client. The reason for the error is included in the
message.
270

271
% DHCP4_PARSER_COMMIT_EXCEPTION parser failed to commit changes
272
On receipt of message containing details to a change of the DHCPv4
273
274
275
276
277
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
278
On receipt of message containing details to a change of the DHCPv4
279
280
281
282
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.

283
% DHCP4_PARSER_CREATED created parser for configuration element %1
284
A debug message output during a configuration update of the DHCPv4
285
server, notifying that the parser for the specified configuration element
286
has been successfully created.
287

288
% DHCP4_PARSER_EXCEPTION failed to create or run parser for configuration element %1
289
On receipt of message containing details to a change of its configuration,
290
the DHCPv4 server failed to create a parser to decode the contents of
291
292
the named configuration element, or the creation succeeded but the parsing
actions and committal of changes failed.  The message has been output in
293
response to a non-Kea exception being raised.  Additional messages
294
295
may give further information.

296
297
% 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,
298
the DHCPv4 server failed to create a parser to decode the contents
299
300
301
302
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.

303
% DHCP4_QUERY_DATA received packet type %1, data is <%2>
304
A debug message listing the data received from the client.
305

306
307
308
309
310
% DHCP4_QUEUE_NCR name change request to %1 DNS entry queued: %2
A debug message which is logged when the NameChangeRequest to add or remove
a DNS entries for a particular lease has been queued. The first parameter of
this log message indicates whether the DNS entry is to be added or removed.
The second parameter carries the details of the NameChangeRequest.
311

312
% DHCP4_RELEASE address %1 belonging to client-id %2, hwaddr %3 was released properly.
313
314
315
This debug message indicates that an address was released properly. It
is a normal operation during client shutdown.

316
% DHCP4_RELEASE_EXCEPTION exception %1 while trying to release address %2
317
318
319
320
321
This message is output when an error was encountered during an attempt
to process a RELEASE message. The error will not affect the client,
which does not expect any response from the server for RELEASE
messages. Depending on the nature of problem, it may affect future
server operation.
322

323
% DHCP4_RELEASE_FAIL failed to remove lease for address %1 for duid %2, hwaddr %3
324
325
326
327
328
329
330
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
removed from the database during RELEASE message processing.

331
% DHCP4_RELEASE_FAIL_NO_LEASE client (client-id %1, hwaddr %2) tried to release address, %3, but there is no such lease.
332
This warning message is printed when client attempts to release a lease,
333
but no such lease is known to the server.
334

335
% DHCP4_RELEASE_FAIL_WRONG_CLIENT_ID client (client-id %2) tried to release address %1, but it belongs to client (client-id %3)
336
337
338
339
340
341
This warning message indicates that 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.

342
% DHCP4_RELEASE_FAIL_WRONG_HWADDR client (client-id %2) tried to release address %1, but sent from a wrong hardware address (%3)
343
This warning message indicates that client tried to release an address
344
345
346
347
that does belong to it, but the lease information was associated with
a different hardware address. One possible reason for using different
hardware address is that a cloned virtual machine was not updated and
both clones use the same client-id.
348

349
350
351
352
% DHCP4_REQUEST_CLASS_PROCESSING_FAILED client class specific processing failed for DHCPREQUEST
This debug message means that the server processing that is unique for each
client class has reported a failure. The response packet will not be sent.

353
% DHCP4_RESPONSE_DATA responding with packet type %1, data is <%2>
354
355
A debug message listing the data returned to the client.

356
% DHCP4_SERVER_FAILED server failed: %1
357
The DHCPv4 server has encountered a fatal error and is terminating.
358
359
The reason for the failure is included in the message.

360
% DHCP4_SHUTDOWN server shutdown
361
The DHCPv4 server has terminated normally.
362
363

% DHCP4_SHUTDOWN_REQUEST shutdown of server requested
364
This debug message indicates that a shutdown of the DHCPv4 server has
365
366
been requested via a call to the 'shutdown' method of the core Dhcpv4Srv
object.
367
368

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

374
375
376
377
378
% 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.

379
% DHCP4_STARTING Kea DHCPv4 server version %1 starting
380
This informational message indicates that the DHCPv4 server has
381
382
processed any command-line switches and is starting. The version
is also printed.
383

Tomek Mrugalski's avatar
Tomek Mrugalski committed
384
% DHCP4_START_INFO pid: %1, port: %2, verbose: %3
385
This is a debug message issued during the DHCPv4 server startup.
386
387
It lists some information about the parameters with which the server
is running.
388
389

% DHCP4_SUBNET_SELECTED the %1 subnet was selected for client assignment
390
391
392
393
394
395
396
397
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.

% DHCP4_SUBNET_SELECTION_FAILED failed to select a subnet for incoming packet, src: %1, type: %2
This warning message is output when a packet was received from a subnet
for which the DHCPv4 server has not been configured. The most probable
cause is a misconfiguration of the server.
398

399
400
401
402
403
404
405
406
407
408
409
% DHCP4_UNRECOGNIZED_RCVD_PACKET_TYPE received message (transaction id %1) has unrecognized type %2 in option 53
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.
The message will not be processed by the server.

% DHCP4_UNSUPPORTED_RCVD_PACKET_TYPE received message (transaction id %1), having type %2 is not supported
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
messages being normally sent by the server to the client, such as Offer, ACK,
NAK etc.