dhcpsrv_messages.mes 39 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747
  1. # Copyright (C) 2012-2015 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # Permission to use, copy, modify, and/or distribute this software for any
  4. # purpose with or without fee is hereby granted, provided that the above
  5. # copyright notice and this permission notice appear in all copies.
  6. #
  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  9. # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  13. # PERFORMANCE OF THIS SOFTWARE.
  14. $NAMESPACE isc::dhcp
  15. % DHCPSRV_CFGMGR_ADD_IFACE listening on interface %1
  16. An info message issued when a new interface is being added to the collection of
  17. interfaces on which the server listens to DHCP messages.
  18. % DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet %1
  19. A debug message reported when the DHCP configuration manager is adding the
  20. specified IPv4 subnet to its database.
  21. % DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet %1
  22. A debug message reported when the DHCP configuration manager is adding the
  23. specified IPv6 subnet to its database.
  24. % DHCPSRV_CFGMGR_ALL_IFACES_ACTIVE enabling listening on all interfaces
  25. A debug message issued when the server is being configured to listen on all
  26. interfaces.
  27. % DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to: %1
  28. A debug message issued when the server's DHCP-DDNS settings are changed.
  29. % DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces
  30. A debug message issued when configuration manager clears the internal list
  31. of active interfaces. This doesn't prevent the server from listening to
  32. the DHCP traffic through open sockets, but will rather be used by Interface
  33. Manager to select active interfaces when sockets are re-opened.
  34. % DHCPSRV_CFGMGR_NO_SUBNET4 no suitable subnet is defined for address hint %1
  35. This debug message is output when the DHCP configuration manager has received
  36. a request for an IPv4 subnet for the specified address, but no such
  37. subnet exists.
  38. % DHCPSRV_CFGMGR_NO_SUBNET6 no suitable subnet is defined for address hint %1
  39. This debug message is output when the DHCP configuration manager has received
  40. a request for an IPv6 subnet for the specified address, but no such
  41. subnet exists.
  42. % DHCPSRV_CFGMGR_ONLY_SUBNET4 retrieved subnet %1 for address hint %2
  43. This is a debug message reporting that the DHCP configuration manager has
  44. returned the specified IPv4 subnet when given the address hint specified
  45. because it is the only subnet defined.
  46. % DHCPSRV_CFGMGR_ONLY_SUBNET6 retrieved subnet %1 for address hint %2
  47. This is a debug message reporting that the DHCP configuration manager has
  48. returned the specified IPv6 subnet when given the address hint specified
  49. because it is the only subnet defined.
  50. % DHCPSRV_CFGMGR_SOCKET_RAW_UNSUPPORTED use of raw sockets is unsupported on this OS, UDP sockets will be used
  51. This warning message is logged when the user specified that the
  52. DHCPv4 server should use the raw sockets to receive the DHCP
  53. messages and respond to the clients, but the use of raw sockets
  54. is not supported on the particular environment. The raw sockets
  55. are useful when the server must respond to the directly connected
  56. clients which don't have an address yet. If the raw sockets are
  57. not supported by Kea on the particular platform, Kea will fall
  58. back to use of the IP/UDP sockets. The responses to
  59. the directly connected clients will be broadcast. The responses
  60. to relayed clients will be unicast as usual.
  61. % DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type %1
  62. This informational message is logged when the administrator hasn't
  63. specified the "dhcp-socket-type" parameter in configuration for interfaces.
  64. In such case, the default socket type will be used.
  65. % DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type %1
  66. This informational message is logged when the DHCPv4 server selects the
  67. socket type to be used for all sockets that will be opened on the
  68. interfaces. Typically, the socket type is specified by the server
  69. administrator. If the socket type hasn't been specified, the raw
  70. socket will be selected. If the raw socket has been selected but
  71. Kea doesn't support the use of raw sockets on the particular
  72. OS, it will use an UDP socket instead.
  73. % DHCPSRV_CFGMGR_SUBNET4 retrieved subnet %1 for address hint %2
  74. This is a debug message reporting that the DHCP configuration manager has
  75. returned the specified IPv4 subnet when given the address hint specified
  76. as the address is within the subnet.
  77. % DHCPSRV_CFGMGR_SUBNET4_RELAY selected subnet %1, because of matching relay addr %2
  78. This is a debug message reporting that the DHCP configuration manager has
  79. returned the specified IPv4 subnet, because detected relay agent address
  80. matches value specified for this subnet.
  81. % DHCPSRV_CFGMGR_SUBNET6 retrieved subnet %1 for address hint %2
  82. This is a debug message reporting that the DHCP configuration manager has
  83. returned the specified IPv6 subnet when given the address hint specified
  84. as the address is within the subnet.
  85. % DHCPSRV_CFGMGR_SUBNET6_IFACE selected subnet %1 for packet received over interface %2
  86. This is a debug message reporting that the DHCP configuration manager
  87. has returned the specified IPv6 subnet for a packet received over
  88. given interface. This particular subnet was selected, because it
  89. was specified as being directly reachable over given interface. (see
  90. 'interface' parameter in the subnet6 definition).
  91. % DHCPSRV_CFGMGR_SUBNET6_IFACE_ID selected subnet %1 (interface-id match) for incoming packet
  92. This is a debug message reporting that the DHCP configuration manager
  93. has returned the specified IPv6 subnet for a received packet. This particular
  94. subnet was selected, because value of interface-id option matched what was
  95. configured in the server's interface-id option for that selected subnet6.
  96. (see 'interface-id' parameter in the subnet6 definition).
  97. % DHCPSRV_CFGMGR_SUBNET6_RELAY selected subnet %1, because of matching relay addr %2
  98. This is a debug message reporting that the DHCP configuration manager has
  99. returned the specified IPv6 subnet, because detected relay agent address
  100. matches value specified for this subnet.
  101. % DHCPSRV_CFGMGR_UNICAST_LINK_LOCAL specified link local address %1 for unicast traffic on interface %2
  102. This warning message is logged when user specified a link-local address to
  103. receive unicast traffic. The warning message is issued because it is an
  104. uncommon use.
  105. % DHCPSRV_CFGMGR_USE_ADDRESS listening on address %1, on interface %2
  106. A message issued when the server is configured to listen on the explicitly specified
  107. IP address on the given interface.
  108. % DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address %1, on interface %2
  109. An info message issued when configuring the DHCP server to listen on the unicast
  110. address on the specific interface.
  111. % DHCPSRV_CLOSE_DB closing currently open %1 database
  112. This is a debug message, issued when the DHCP server closes the currently
  113. open lease database. It is issued at program shutdown and whenever
  114. the database access parameters are changed: in the latter case, the
  115. server closes the currently open database, and opens a database using
  116. the new parameters.
  117. % DHCPSRV_DHCP_DDNS_ERROR_EXCEPTION error handler for DHCP_DDNS IO generated an expected exception: %1
  118. This is an error message that occurs when an attempt to send a request to
  119. kea-dhcp-ddns fails there registered error handler threw an uncaught exception.
  120. This is a programmatic error which should not occur. By convention, the error
  121. handler should not propagate exceptions. Please report this error.
  122. % DHCPSRV_DHCP_DDNS_HANDLER_NULL error handler for DHCP_DDNS IO is not set.
  123. This is an error message that occurs when an attempt to send a request to
  124. kea-dhcp-ddns fails and there is no registered error handler. This is a
  125. programmatic error which should never occur and should be reported.
  126. % DHCPSRV_DHCP_DDNS_NCR_REJECTED NameChangeRequest rejected by the sender: %1, ncr: %2
  127. This is an error message indicating that NameChangeSender used to deliver DDNS
  128. update requests to kea-dhcp-ddns rejected the request. This most likely cause
  129. is the sender's queue has reached maximum capacity. This would imply that
  130. requests are being generated faster than they can be delivered.
  131. % DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: %1
  132. A debug message issued when a NameChangeRequest has been successfully sent to
  133. kea-dhcp-ddns.
  134. % DHCPSRV_DHCP_DDNS_SENDER_STARTED NameChangeRequest sender has been started: %1
  135. A informational message issued when a communications with kea-dhcp-ddns has
  136. been successfully started.
  137. % DHCPSRV_DHCP_DDNS_SENDER_STOPPED NameChangeRequest sender has been stopped.
  138. A informational message issued when a communications with kea-dhcp-ddns has
  139. been stopped. This normally occurs during reconfiguration and as part of normal
  140. shutdown. It may occur if kea-dhcp-ddns communications breakdown.
  141. % DHCPSRV_DHCP_DDNS_SUSPEND_UPDATES DHCP_DDNS updates are being suspended.
  142. This is a warning message indicating the DHCP_DDNS updates have been turned
  143. off. This should only occur if IO errors communicating with kea-dhcp-ddns
  144. have been experienced. Any such errors should have preceding entries in the
  145. log with details. No further attempts to communicate with kea-dhcp-ddns will
  146. be made without intervention.
  147. % DHCPSRV_HOOK_LEASE4_RENEW_SKIP DHCPv4 lease was not renewed because a callout set the skip flag.
  148. This debug message is printed when a callout installed on lease4_renew
  149. hook point set the skip flag. For this particular hook point, the setting
  150. of the flag by a callout instructs the server to not renew a lease. The
  151. server will use existing lease as it is, without extending its lifetime.
  152. % DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.
  153. This debug message is printed when a callout installed on lease4_select
  154. hook point sets the skip flag. It means that the server was told that
  155. no lease4 should be assigned. The server will not put that lease in its
  156. database and the client will get a NAK packet.
  157. % DHCPSRV_HOOK_LEASE6_EXTEND_SKIP DHCPv6 lease lifetime was not extended because a callout set the skip flag for message %1
  158. This debug message is printed when a callout installed on lease6_renew
  159. or the lease6_rebind hook point set the skip flag. For this particular hook
  160. point, the setting of the flag by a callout instructs the server to not
  161. extend the lifetime for a lease. If the client requested renewal of multiple
  162. leases (by sending multiple IA options), the server will skip the renewal
  163. of the one in question and will proceed with other renewals as usual.
  164. % DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.
  165. This debug message is printed when a callout installed on lease6_select
  166. hook point sets the skip flag. It means that the server was told that
  167. no lease6 should be assigned. The server will not put that lease in its
  168. database and the client will get a NoAddrsAvail for that IA_NA option.
  169. % DHCPSRV_INVALID_ACCESS invalid database access string: %1
  170. This is logged when an attempt has been made to parse a database access string
  171. and the attempt ended in error. The access string in question - which
  172. should be of the form 'keyword=value keyword=value...' is included in
  173. the message.
  174. % DHCPSRV_MEMFILE_ADD_ADDR4 adding IPv4 lease with address %1
  175. A debug message issued when the server is about to add an IPv4 lease
  176. with the specified address to the memory file backend database.
  177. % DHCPSRV_MEMFILE_ADD_ADDR6 adding IPv6 lease with address %1
  178. A debug message issued when the server is about to add an IPv6 lease
  179. with the specified address to the memory file backend database.
  180. % DHCPSRV_MEMFILE_COMMIT committing to memory file database
  181. The code has issued a commit call. For the memory file database, this is
  182. a no-op.
  183. % DHCPRSV_MEMFILE_CONVERTING_LEASE_FILES running LFC now to convert lease files to the current schema: %1.%2
  184. A warning message issued when the server has detected lease files that need
  185. to be either upgraded or downgraded to match the server's schema, and that
  186. the server is automatically running the LFC process to perform the conversion.
  187. This should only occur the first time the server is launched following a Kea
  188. installation upgrade (or downgrade).
  189. % DHCPSRV_MEMFILE_DB opening memory file lease database: %1
  190. This informational message is logged when a DHCP server (either V4 or
  191. V6) is about to open a memory file lease database. The parameters of
  192. the connection including database name and username needed to access it
  193. (but not the password if any) are logged.
  194. % DHCPSRV_MEMFILE_DELETE_ADDR deleting lease for address %1
  195. A debug message issued when the server is attempting to delete a lease
  196. for the specified address from the memory file database for the specified
  197. address.
  198. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  199. A debug message issued when the server is removing reclaimed DHCPv4
  200. leases which have expired longer than a specified period of time.
  201. The argument is the amount of time Kea waits after a reclaimed
  202. lease expires before considering its removal.
  203. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  204. A debug message issued when the server is removing reclaimed DHCPv6
  205. leases which have expired longer than a specified period of time.
  206. The argument is the amount of time Kea waits after a reclaimed
  207. lease expires before considering its removal.
  208. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED_START starting deletion of %1 expired-reclaimed leases
  209. A debug message issued wheb the server has found expired-reclaimed
  210. leases to be removed. The number of leases to be removed is logged
  211. in the message.
  212. % DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1
  213. A debug message issued when the server is attempting to obtain an IPv4
  214. lease from the memory file database for the specified address.
  215. % DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
  216. A debug message issued when the server is attempting to obtain an IPv6
  217. lease from the memory file database for the specified address.
  218. % DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1
  219. A debug message issued when the server is attempting to obtain a set of
  220. IPv4 leases from the memory file database for a client with the specified
  221. client identification.
  222. % DHCPSRV_MEMFILE_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3
  223. A debug message issued when the server is attempting to obtain an IPv4
  224. lease from the memory file database for a client with the specified
  225. client ID, hardware address and subnet ID.
  226. % DHCPSRV_MEMFILE_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  227. A debug message issued when the server is attempting to obtain expired
  228. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  229. is logged in the message.
  230. % DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  231. A debug message issued when the server is attempting to obtain expired
  232. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  233. is logged in the message.
  234. % DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %1
  235. A debug message issued when the server is attempting to obtain a set of
  236. IPv4 leases from the memory file database for a client with the specified
  237. hardware address.
  238. % DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %3
  239. A debug message issued when the server is attempting to obtain a set of
  240. IPv6 lease from the memory file database for a client with the specified
  241. IAID (Identity Association ID) and DUID (DHCP Unique Identifier).
  242. % DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
  243. A debug message issued when the server is attempting to obtain an IPv6
  244. lease from the memory file database for a client with the specified IAID
  245. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  246. % DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  247. A debug message issued when the server is attempting to obtain an IPv4
  248. lease from the memory file database for a client with the specified
  249. subnet ID and client ID.
  250. % DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  251. A debug message issued when the server is attempting to obtain an IPv4
  252. lease from the memory file database for a client with the specified
  253. subnet ID and hardware address.
  254. % DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information
  255. A debug message issued when the server is about to obtain schema version
  256. information from the memory file database.
  257. % DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file %1
  258. An info message issued when the server is about to start reading DHCP leases
  259. from the lease file. All leases currently held in the memory will be
  260. replaced by those read from the file.
  261. % DHCPSRV_MEMFILE_LEASE_LOAD loading lease %1
  262. A debug message issued when DHCP lease is being loaded from the file to memory.
  263. % DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: %1
  264. An informational message issued when the Memfile lease database backend
  265. starts a new process to perform Lease File Cleanup.
  266. % DHCPSRV_MEMFILE_LFC_LEASE_FILE_RENAME_FAIL failed to rename the current lease file %1 to %2, reason: %3
  267. An error message logged when the Memfile lease database backend fails to
  268. move the current lease file to a new file on which the cleanup should
  269. be performed. This effectively means that the lease file cleanup
  270. will not take place.
  271. % DHCPSRV_MEMFILE_LFC_LEASE_FILE_REOPEN_FAIL failed to reopen lease file %1 after preparing input file for lease file cleanup, reason: %2, new leases will not be persisted!
  272. An error message logged when the Memfile lease database backend
  273. failed to re-open or re-create the lease file after renaming the
  274. lease file for lease file cleanup. The server will continue to
  275. operate but leases will not be persisted to disk.
  276. % DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to %1 sec
  277. An informational message logged when the Memfile lease database backend
  278. configures the LFC to be executed periodically. The argument holds the
  279. interval in seconds in which the LFC will be executed.
  280. % DHCPSRV_MEMFILE_LFC_SPAWN_FAIL lease file cleanup failed to run because kea-lfc process couldn't be spawned
  281. This error message is logged when the the Kea server fails to run kea-lfc,
  282. the program that cleans up the lease file. The server will try again the
  283. next time a lease file cleanup is scheduled. Although this message should
  284. not appear and the reason why it did investigated, the occasional failure
  285. to start the lease file cleanup will not impact operations. Should the
  286. failure persist however, the size of the lease file will increase without bound.
  287. % DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
  288. An informational message issued when the Memfile lease database backend
  289. starts the periodic Lease File Cleanup.
  290. % DHCPSRV_MEMFILE_LFC_UNREGISTER_TIMER_FAILED failed to unregister timer 'memfile-lfc': %1
  291. This error message is logged when Memfile backend fails to unregister
  292. timer used for lease file cleanup scheduling. This is highly unlikely
  293. and indicates programming error. The message include the reason for this
  294. error.
  295. % DHCPSRV_MEMFILE_NEEDS_DOWNGRADING version of lease file: %1 schema is later than version %2.
  296. A warning message issued when the schema of the lease file loaded by the server
  297. is newer than the memfile schema of the server. The server converts the lease
  298. data from newer schemas to its schema as it is read, therefore the lease
  299. information in use by the server will be correct. Note though, that any data
  300. data stored in newer schema fields will be dropped. What remains is for the
  301. file itself to be rewritten using the current schema.
  302. % DHCPSRV_MEMFILE_NEEDS_UPGRADING version of lease file: %1 schema is earlier than version %2.
  303. A warning message issued when the schema of the lease file loaded by the server
  304. pre-dates the memfile schema of the server. Note that the server converts the
  305. lease data from older schemas to the current schema as it is read, therefore
  306. the lease information in use by the server will be correct. What remains is
  307. for the file itself to be rewritten using the current schema.
  308. % DHCPSRV_MEMFILE_NO_STORAGE running in non-persistent mode, leases will be lost after restart
  309. A warning message issued when writes of leases to disk have been disabled
  310. in the configuration. This mode is useful for some kinds of performance
  311. testing but should not be enabled in normal circumstances. Non-persistence
  312. mode is enabled when 'persist4=no persist6=no' parameters are specified
  313. in the database access string.
  314. % DHCPSRV_MEMFILE_READ_HWADDR_FAIL failed to read hardware address from lease file: %1
  315. A warning message issued when read attempt of the hardware address stored in
  316. a disk file failed. The parameter should provide the exact nature of the failure.
  317. The database read will continue, but that particular lease will no longer
  318. have hardware address associated with it.
  319. % DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database
  320. The code has issued a rollback call. For the memory file database, this is
  321. a no-op.
  322. % DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1
  323. A debug message issued when the server is attempting to update IPv4
  324. lease from the memory file database for the specified address.
  325. % DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1
  326. A debug message issued when the server is attempting to update IPv6
  327. lease from the memory file database for the specified address.
  328. % DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple brodcast capable sockets on some interfaces and some DHCP messages may be duplicated
  329. A warning message issued when the current configuration indicates that multiple
  330. sockets, capable of receiving brodcast traffic, will be opened on some of the
  331. interfaces. It must be noted that this may lead to receiving and processing
  332. the same DHCP message multiple times, as it will be received by each socket
  333. individually.
  334. % DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %1
  335. A debug message issued when the server is about to add an IPv4 lease
  336. with the specified address to the MySQL backend database.
  337. % DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
  338. A debug message issued when the server is about to add an IPv6 lease
  339. with the specified address to the MySQL backend database.
  340. % DHCPSRV_MYSQL_COMMIT committing to MySQL database
  341. The code has issued a commit call. All outstanding transactions will be
  342. committed to the database. Note that depending on the MySQL settings,
  343. the committal may not include a write to disk.
  344. % DHCPSRV_MYSQL_DB opening MySQL lease database: %1
  345. This informational message is logged when a DHCP server (either V4 or
  346. V6) is about to open a MySQL lease database. The parameters of the
  347. connection including database name and username needed to access it
  348. (but not the password if any) are logged.
  349. % DHCPSRV_MYSQL_DELETE_ADDR deleting lease for address %1
  350. A debug message issued when the server is attempting to delete a lease for
  351. the specified address from the MySQL database for the specified address.
  352. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  353. A debug message issued when the server is removing reclaimed DHCPv4
  354. leases which have expired longer than a specified period of time.
  355. The argument is the amount of time Kea waits after a reclaimed
  356. lease expires before considering its removal.
  357. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  358. A debug message issued when the server is removing reclaimed DHCPv6
  359. leases which have expired longer than a specified period of time.
  360. The argument is the amount of time Kea waits after a reclaimed
  361. lease expires before considering its removal.
  362. % DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted %1 reclaimed leases from the database
  363. A debug message issued when the server has removed a number of reclaimed
  364. leases from the database. The number of removed leases is included in the
  365. message.
  366. % DHCPSRV_MYSQL_FATAL_ERROR Unrecoverable MySQL error occurred: %1 for <%2>, reason: %3 (error code: %4). Server exiting now!
  367. An error message indicating that communication with the MySQL database server
  368. has been lost. When this occurs the server exits immediately with a non-zero
  369. exit code. This is most likely due to a network issue.
  370. % DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  371. A debug message issued when the server is attempting to obtain an IPv4
  372. lease from the MySQL database for the specified address.
  373. % DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2
  374. A debug message issued when the server is attempting to obtain an IPv6
  375. lease from the MySQL database for the specified address.
  376. % DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  377. A debug message issued when the server is attempting to obtain a set
  378. of IPv4 leases from the MySQL database for a client with the specified
  379. client identification.
  380. % DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  381. A debug message issued when the server is attempting to obtain expired
  382. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  383. is logged in the message.
  384. % DHCPSRV_MYSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  385. A debug message issued when the server is attempting to obtain expired
  386. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  387. is logged in the message.
  388. % DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  389. A debug message issued when the server is attempting to obtain a set
  390. of IPv4 leases from the MySQL database for a client with the specified
  391. hardware address.
  392. % DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
  393. A debug message issued when the server is attempting to obtain a set of
  394. IPv6 lease from the MySQL database for a client with the specified IAID
  395. (Identity Association ID) and DUID (DHCP Unique Identifier).
  396. % DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
  397. A debug message issued when the server is attempting to obtain an IPv6
  398. lease from the MySQL database for a client with the specified IAID
  399. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  400. % DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  401. A debug message issued when the server is attempting to obtain an IPv4
  402. lease from the MySQL database for a client with the specified subnet ID
  403. and client ID.
  404. % DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  405. A debug message issued when the server is attempting to obtain an IPv4
  406. lease from the MySQL database for a client with the specified subnet ID
  407. and hardware address.
  408. % DHCPSRV_MYSQL_GET_VERSION obtaining schema version information
  409. A debug message issued when the server is about to obtain schema version
  410. information from the MySQL database.
  411. % DHCPSRV_MYSQL_ROLLBACK rolling back MySQL database
  412. The code has issued a rollback call. All outstanding transaction will
  413. be rolled back and not committed to the database.
  414. % DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  415. A debug message issued when the server is attempting to update IPv4
  416. lease from the MySQL database for the specified address.
  417. % DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
  418. A debug message issued when the server is attempting to update IPv6
  419. lease from the MySQL database for the specified address.
  420. % DHCPSRV_NOTYPE_DB no 'type' keyword to determine database backend: %1
  421. This is an error message, logged when an attempt has been made to access
  422. a database backend, but where no 'type' keyword has been included in
  423. the access string. The access string (less any passwords) is included
  424. in the message.
  425. % DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
  426. This warning message is issued when the current server configuration specifies
  427. no interfaces that the server should listen on, or when the specified interfaces are not
  428. configured to receive the traffic.
  429. % DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: %1
  430. A warning message issued when IfaceMgr fails to open and bind a socket.
  431. The reason for the failure is appended as an argument of the log message.
  432. % DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %1
  433. A debug message issued when the server is about to add an IPv4 lease
  434. with the specified address to the PostgreSQL backend database.
  435. % DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1
  436. A debug message issued when the server is about to add an IPv6 lease
  437. with the specified address to the PostgreSQL backend database.
  438. % DHCPSRV_PGSQL_COMMIT committing to MySQL database
  439. The code has issued a commit call. All outstanding transactions will be
  440. committed to the database. Note that depending on the PostgreSQL settings,
  441. the committal may not include a write to disk.
  442. % DHCPSRV_PGSQL_DB opening PostgreSQL lease database: %1
  443. This informational message is logged when a DHCP server (either V4 or
  444. V6) is about to open a PostgreSQL lease database. The parameters of the
  445. connection including database name and username needed to access it
  446. (but not the password if any) are logged.
  447. % DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
  448. This is an error message issued when a DHCP server (either V4 or V6) experienced
  449. and error freeing database SQL resources as part of closing its connection to
  450. the Postgresql database. The connection is closed as part of normal server
  451. shutdown. This error is most likely a programmatic issue that is highly
  452. unlikely to occur or negatively impact server operation.
  453. % DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1
  454. A debug message issued when the server is attempting to delete a lease for
  455. the specified address from the PostgreSQL database for the specified address.
  456. % DHCPSRV_PGSQL_FATAL_ERROR Unrecoverable PostgreSQL error occurred: Statement: <%1>, reason: %2 (error code: %3). Server exiting now!
  457. An error message indicating that communication with the MySQL database server
  458. has been lost. When this occurs the server exits immediately with a non-zero
  459. exit code. This is most likely due to a network issue.
  460. % DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  461. A debug message issued when the server is attempting to obtain an IPv4
  462. lease from the PostgreSQL database for the specified address.
  463. % DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)
  464. A debug message issued when the server is attempting to obtain an IPv6
  465. lease from the PostgreSQL database for the specified address.
  466. % DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  467. A debug message issued when the server is attempting to obtain a set
  468. of IPv4 leases from the PostgreSQL database for a client with the specified
  469. client identification.
  470. % DHCPSRV_PGSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  471. A debug message issued when the server is attempting to obtain expired
  472. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  473. is logged in the message.
  474. % DHCPSRV_PGSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  475. A debug message issued when the server is attempting to obtain expired
  476. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  477. is logged in the message.
  478. % DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  479. A debug message issued when the server is removing reclaimed DHCPv4
  480. leases which have expired longer than a specified period of time.
  481. The argument is the amount of time Kea waits after a reclaimed
  482. lease expires before considering its removal.
  483. % DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  484. A debug message issued when the server is removing reclaimed DHCPv6
  485. leases which have expired longer than a specified period of time.
  486. The argument is the amount of time Kea waits after a reclaimed
  487. lease expires before considering its removal.
  488. % DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  489. A debug message issued when the server is attempting to obtain a set
  490. of IPv4 leases from the PostgreSQL database for a client with the specified
  491. hardware address.
  492. % DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
  493. A debug message issued when the server is attempting to obtain a set of
  494. IPv6 lease from the PostgreSQL database for a client with the specified IAID
  495. (Identity Association ID) and DUID (DHCP Unique Identifier).
  496. % DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
  497. A debug message issued when the server is attempting to obtain an IPv6
  498. lease from the PostgreSQL database for a client with the specified IAID
  499. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  500. % DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  501. A debug message issued when the server is attempting to obtain an IPv4
  502. lease from the PostgreSQL database for a client with the specified subnet ID
  503. and client ID.
  504. % DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  505. A debug message issued when the server is attempting to obtain an IPv4
  506. lease from the PostgreSQL database for a client with the specified subnet ID
  507. and hardware address.
  508. % DHCPSRV_PGSQL_GET_VERSION obtaining schema version information
  509. A debug message issued when the server is about to obtain schema version
  510. information from the PostgreSQL database.
  511. % DHCPSRV_PGSQL_ROLLBACK rolling back PostgreSQL database
  512. The code has issued a rollback call. All outstanding transaction will
  513. be rolled back and not committed to the database.
  514. % DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  515. A debug message issued when the server is attempting to update IPv4
  516. lease from the PostgreSQL database for the specified address.
  517. % DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1
  518. A debug message issued when the server is attempting to update IPv6
  519. lease from the PostgreSQL database for the specified address.
  520. % DHCPSRV_QUEUE_NCR %1: name change request to %2 DNS entry queued: %3
  521. A debug message which is logged when the NameChangeRequest to add or remove
  522. a DNS entries for a particular lease has been queued. The first argument
  523. includes the client identification information. The second argument
  524. indicates whether the DNS entry is to be added or removed. The third
  525. argument carries the details of the NameChangeRequest.
  526. % DHCPSRV_QUEUE_NCR_FAILED %1: queueing %2 name change request failed for lease %3: %4
  527. This error message is logged when sending a name change request
  528. to DHCP DDNS failed. The first argument includes the client identification
  529. information. The second argument indicates whether the DNS entry is to be
  530. added or removed. The third argument specifies the leased address. The
  531. last argument provides the reason for failure.
  532. % DHCPSRV_QUEUE_NCR_SKIP %1: skip queueing name change request for lease: %2
  533. This debug message is issued when the server decides to not queue the name
  534. change request because the lease doesn't include the FQDN, the forward and
  535. reverse update is disabled for this lease or the DNS updates are disabled
  536. in the configuration. The first argument includes the client identification
  537. information. The second argument includes the leased address.
  538. % DHCPSRV_TIMERMGR_CALLBACK_FAILED running handler for timer %1 caused exception: %2
  539. This error message is emitted when the timer elapsed and the
  540. operation associated with this timer has thrown an exception.
  541. The timer name and the reason for exception is logged.
  542. % DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: %1, using interval: %2 ms
  543. A debug message issued when the new interval timer is registered in
  544. the Timer Manager. This timer will have a callback function
  545. associated with it, and this function will be executed according
  546. to the interval specified. The unique name of the timer and the
  547. interval at which the callback function will be executed is
  548. included in the message.
  549. % DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: %1
  550. A debug message issued when the Timer Manager is about to
  551. run a periodic operation associated with the given timer.
  552. An example of such operation is a periodic cleanup of
  553. expired leases. The name of the timer is included in the
  554. message.
  555. % DHCPSRV_TIMERMGR_SOCKET_CLEAR_FAILED clearing watch socket for timer %1 failed: %2
  556. An error message indicating that the specified timer elapsed,
  557. the operation associated with the timer was executed but the
  558. server was unable to signal this to the worker thread responsible
  559. for dispatching timers. The thread will continue but it will
  560. not be able to dispatch any operations for this timer. The
  561. server reconfiguration or restart may solve the problem
  562. but the situation may repeat.
  563. % DHCPSRV_TIMERMGR_SOCKET_MARK_FAILED marking watch socket for timer %1 failed: %2
  564. An error message indicating that the specified timer elapsed,
  565. but the server was unable to flag that the handler function
  566. should be executed for this timer. The callback will not
  567. be executed this time and most likely the subsequent attempts
  568. will not be successful too. This error is highly unlikely.
  569. The name of the timer and thre reason for failure is included
  570. in the message.
  571. % DHCPSRV_TIMERMGR_START_THREAD starting thread for timers
  572. A debug message issued when the Timer Manager is starting a
  573. worker thread to run started timers. The worker thread is
  574. typically started right after all timers have been registered
  575. and runs until timers need to be reconfigured, e.g. their
  576. interval is changed, new timers are registered or existing
  577. timers are unregistered.
  578. % DHCPSRV_TIMERMGR_START_TIMER starting timer: %1
  579. A debug message issued when the registered interval timer is
  580. being started. If this operation is successful the timer will
  581. periodically execute the operation associated with it. The
  582. name of the started timer is included in the message.
  583. % DHCPSRV_TIMERMGR_STOP_THREAD stopping thread for timers
  584. A debug message issued when the Timer Manager is stopping
  585. the worker thread which executes interval timers. When the
  586. thread is stopped no timers will be executed. The thread is
  587. typically stopped at the server reconfiguration or when the
  588. server shuts down.
  589. % DHCPSRV_TIMERMGR_STOP_TIMER stopping timer: %1
  590. A debug message issued when the registered interval timer is
  591. being stopped. The timer remains registered and can be restarted
  592. if necessary. The name of the timer is included in the message.
  593. % DHCPSRV_TIMERMGR_UNREGISTER_ALL_TIMERS unregistering all timers
  594. A debug message issued when all registered interval timers are
  595. being unregistered from the Timer Manager.
  596. % DHCPSRV_TIMERMGR_UNREGISTER_TIMER unregistering timer: %1
  597. A debug message issued when one of the registered interval timers
  598. is unregistered from the Timer Manager. The name of the timer is
  599. included in the message.
  600. % DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'
  601. The parameters for access the lease database were passed to the server through
  602. the named configuration parameter, but the code was expecting them to be
  603. passed via the parameter named "lease-database". If the database opens
  604. successfully, there is no impact on server operation. However, as this does
  605. indicate an error in the source code, please submit a bug report.
  606. % DHCPSRV_UNKNOWN_DB unknown database type: %1
  607. The database access string specified a database type (given in the
  608. message) that is unknown to the software. This is a configuration error.