dhcpsrv_messages.mes 31 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593
  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. % DHCPSRV_MEMFILE_DB opening memory file lease database: %1
  184. This informational message is logged when a DHCP server (either V4 or
  185. V6) is about to open a memory file lease database. The parameters of
  186. the connection including database name and username needed to access it
  187. (but not the password if any) are logged.
  188. % DHCPSRV_MEMFILE_DELETE_ADDR deleting lease for address %1
  189. A debug message issued when the server is attempting to delete a lease
  190. for the specified address from the memory file database for the specified
  191. address.
  192. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  193. A debug message issued when the server is removing reclaimed DHCPv4
  194. leases which have expired longer than a specified period of time.
  195. The argument is the amount of time Kea waits after a reclaimed
  196. lease expires before considering its removal.
  197. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  198. A debug message issued when the server is removing reclaimed DHCPv6
  199. leases which have expired longer than a specified period of time.
  200. The argument is the amount of time Kea waits after a reclaimed
  201. lease expires before considering its removal.
  202. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED_START starting deletion of %1 expired-reclaimed leases
  203. A debug message issued wheb the server has found expired-reclaimed
  204. leases to be removed. The number of leases to be removed is logged
  205. in the message.
  206. % DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1
  207. A debug message issued when the server is attempting to obtain an IPv4
  208. lease from the memory file database for the specified address.
  209. % DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
  210. A debug message issued when the server is attempting to obtain an IPv6
  211. lease from the memory file database for the specified address.
  212. % DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1
  213. A debug message issued when the server is attempting to obtain a set of
  214. IPv4 leases from the memory file database for a client with the specified
  215. client identification.
  216. % DHCPSRV_MEMFILE_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3
  217. A debug message issued when the server is attempting to obtain an IPv4
  218. lease from the memory file database for a client with the specified
  219. client ID, hardware address and subnet ID.
  220. % DHCPSRV_MEMFILE_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  221. A debug message issued when the server is attempting to obtain expired
  222. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  223. is logged in the message.
  224. % DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  225. A debug message issued when the server is attempting to obtain expired
  226. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  227. is logged in the message.
  228. % DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %1
  229. A debug message issued when the server is attempting to obtain a set of
  230. IPv4 leases from the memory file database for a client with the specified
  231. hardware address.
  232. % DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %3
  233. A debug message issued when the server is attempting to obtain a set of
  234. IPv6 lease from the memory file database for a client with the specified
  235. IAID (Identity Association ID) and DUID (DHCP Unique Identifier).
  236. % DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
  237. A debug message issued when the server is attempting to obtain an IPv6
  238. lease from the memory file database for a client with the specified IAID
  239. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  240. % DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  241. A debug message issued when the server is attempting to obtain an IPv4
  242. lease from the memory file database for a client with the specified
  243. subnet ID and client ID.
  244. % DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  245. A debug message issued when the server is attempting to obtain an IPv4
  246. lease from the memory file database for a client with the specified
  247. subnet ID and hardware address.
  248. % DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information
  249. A debug message issued when the server is about to obtain schema version
  250. information from the memory file database.
  251. % DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file %1
  252. An info message issued when the server is about to start reading DHCP leases
  253. from the lease file. All leases currently held in the memory will be
  254. replaced by those read from the file.
  255. % DHCPSRV_MEMFILE_LEASE_LOAD loading lease %1
  256. A debug message issued when DHCP lease is being loaded from the file to memory.
  257. % DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: %1
  258. An informational message issued when the Memfile lease database backend
  259. starts a new process to perform Lease File Cleanup.
  260. % DHCPSRV_MEMFILE_LFC_LEASE_FILE_RENAME_FAIL failed to rename the current lease file %1 to %2, reason: %3
  261. An error message logged when the Memfile lease database backend fails to
  262. move the current lease file to a new file on which the cleanup should
  263. be performed. This effectively means that the lease file cleanup
  264. will not take place.
  265. % 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!
  266. An error message logged when the Memfile lease database backend
  267. failed to re-open or re-create the lease file after renaming the
  268. lease file for lease file cleanup. The server will continue to
  269. operate but leases will not be persisted to disk.
  270. % DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to %1 sec
  271. An informational message logged when the Memfile lease database backend
  272. configures the LFC to be executed periodically. The argument holds the
  273. interval in seconds in which the LFC will be executed.
  274. % DHCPSRV_MEMFILE_LFC_SPAWN_FAIL lease file cleanup failed to run because kea-lfc process couldn't be spawned
  275. This error message is logged when the the Kea server fails to run kea-lfc,
  276. the program that cleans up the lease file. The server will try again the
  277. next time a lease file cleanup is scheduled. Although this message should
  278. not appear and the reason why it did investigated, the occasional failure
  279. to start the lease file cleanup will not impact operations. Should the
  280. failure persist however, the size of the lease file will increase without bound.
  281. % DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
  282. An informational message issued when the Memfile lease database backend
  283. starts the periodic Lease File Cleanup.
  284. % DHCPSRV_MEMFILE_NO_STORAGE running in non-persistent mode, leases will be lost after restart
  285. A warning message issued when writes of leases to disk have been disabled
  286. in the configuration. This mode is useful for some kinds of performance
  287. testing but should not be enabled in normal circumstances. Non-persistence
  288. mode is enabled when 'persist4=no persist6=no' parameters are specified
  289. in the database access string.
  290. % DHCPSRV_MEMFILE_READ_HWADDR_FAIL failed to read hardware address from lease file: %1
  291. A warning message issued when read attempt of the hardware address stored in
  292. a disk file failed. The parameter should provide the exact nature of the failure.
  293. The database read will continue, but that particular lease will no longer
  294. have hardware address associated with it.
  295. % DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database
  296. The code has issued a rollback call. For the memory file database, this is
  297. a no-op.
  298. % DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1
  299. A debug message issued when the server is attempting to update IPv4
  300. lease from the memory file database for the specified address.
  301. % DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1
  302. A debug message issued when the server is attempting to update IPv6
  303. lease from the memory file database for the specified address.
  304. % 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
  305. A warning message issued when the current configuration indicates that multiple
  306. sockets, capable of receiving brodcast traffic, will be opened on some of the
  307. interfaces. It must be noted that this may lead to receiving and processing
  308. the same DHCP message multiple times, as it will be received by each socket
  309. individually.
  310. % DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %1
  311. A debug message issued when the server is about to add an IPv4 lease
  312. with the specified address to the MySQL backend database.
  313. % DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
  314. A debug message issued when the server is about to add an IPv6 lease
  315. with the specified address to the MySQL backend database.
  316. % DHCPSRV_MYSQL_COMMIT committing to MySQL database
  317. The code has issued a commit call. All outstanding transactions will be
  318. committed to the database. Note that depending on the MySQL settings,
  319. the committal may not include a write to disk.
  320. % DHCPSRV_MYSQL_DB opening MySQL lease database: %1
  321. This informational message is logged when a DHCP server (either V4 or
  322. V6) is about to open a MySQL lease database. The parameters of the
  323. connection including database name and username needed to access it
  324. (but not the password if any) are logged.
  325. % DHCPSRV_MYSQL_DELETE_ADDR deleting lease for address %1
  326. A debug message issued when the server is attempting to delete a lease for
  327. the specified address from the MySQL database for the specified address.
  328. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  329. A debug message issued when the server is removing reclaimed DHCPv4
  330. leases which have expired longer than a specified period of time.
  331. The argument is the amount of time Kea waits after a reclaimed
  332. lease expires before considering its removal.
  333. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  334. A debug message issued when the server is removing reclaimed DHCPv6
  335. leases which have expired longer than a specified period of time.
  336. The argument is the amount of time Kea waits after a reclaimed
  337. lease expires before considering its removal.
  338. % DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted %1 reclaimed leases from the database
  339. A debug message issued when the server has removed a number of reclaimed
  340. leases from the database. The number of removed leases is included in the
  341. message.
  342. % DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  343. A debug message issued when the server is attempting to obtain an IPv4
  344. lease from the MySQL database for the specified address.
  345. % DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2
  346. A debug message issued when the server is attempting to obtain an IPv6
  347. lease from the MySQL database for the specified address.
  348. % DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  349. A debug message issued when the server is attempting to obtain a set
  350. of IPv4 leases from the MySQL database for a client with the specified
  351. client identification.
  352. % DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  353. A debug message issued when the server is attempting to obtain expired
  354. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  355. is logged in the message.
  356. % DHCPSRV_MYSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  357. A debug message issued when the server is attempting to obtain expired
  358. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  359. is logged in the message.
  360. % DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  361. A debug message issued when the server is attempting to obtain a set
  362. of IPv4 leases from the MySQL database for a client with the specified
  363. hardware address.
  364. % DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
  365. A debug message issued when the server is attempting to obtain a set of
  366. IPv6 lease from the MySQL database for a client with the specified IAID
  367. (Identity Association ID) and DUID (DHCP Unique Identifier).
  368. % DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
  369. A debug message issued when the server is attempting to obtain an IPv6
  370. lease from the MySQL database for a client with the specified IAID
  371. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  372. % DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  373. A debug message issued when the server is attempting to obtain an IPv4
  374. lease from the MySQL database for a client with the specified subnet ID
  375. and client ID.
  376. % DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  377. A debug message issued when the server is attempting to obtain an IPv4
  378. lease from the MySQL database for a client with the specified subnet ID
  379. and hardware address.
  380. % DHCPSRV_MYSQL_GET_VERSION obtaining schema version information
  381. A debug message issued when the server is about to obtain schema version
  382. information from the MySQL database.
  383. % DHCPSRV_MYSQL_ROLLBACK rolling back MySQL database
  384. The code has issued a rollback call. All outstanding transaction will
  385. be rolled back and not committed to the database.
  386. % DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  387. A debug message issued when the server is attempting to update IPv4
  388. lease from the MySQL database for the specified address.
  389. % DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
  390. A debug message issued when the server is attempting to update IPv6
  391. lease from the MySQL database for the specified address.
  392. % DHCPSRV_NOTYPE_DB no 'type' keyword to determine database backend: %1
  393. This is an error message, logged when an attempt has been made to access
  394. a database backend, but where no 'type' keyword has been included in
  395. the access string. The access string (less any passwords) is included
  396. in the message.
  397. % DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
  398. This warning message is issued when the current server configuration specifies
  399. no interfaces that the server should listen on, or when the specified interfaces are not
  400. configured to receive the traffic.
  401. % DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: %1
  402. A warning message issued when IfaceMgr fails to open and bind a socket.
  403. The reason for the failure is appended as an argument of the log message.
  404. % DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %1
  405. A debug message issued when the server is about to add an IPv4 lease
  406. with the specified address to the PostgreSQL backend database.
  407. % DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1
  408. A debug message issued when the server is about to add an IPv6 lease
  409. with the specified address to the PostgreSQL backend database.
  410. % DHCPSRV_PGSQL_COMMIT committing to MySQL database
  411. The code has issued a commit call. All outstanding transactions will be
  412. committed to the database. Note that depending on the PostgreSQL settings,
  413. the committal may not include a write to disk.
  414. % DHCPSRV_PGSQL_DB opening PostgreSQL lease database: %1
  415. This informational message is logged when a DHCP server (either V4 or
  416. V6) is about to open a PostgreSQL lease database. The parameters of the
  417. connection including database name and username needed to access it
  418. (but not the password if any) are logged.
  419. % DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
  420. This is an error message issued when a DHCP server (either V4 or V6) experienced
  421. and error freeing database SQL resources as part of closing its connection to
  422. the Postgresql database. The connection is closed as part of normal server
  423. shutdown. This error is most likely a programmatic issue that is highly
  424. unlikely to occur or negatively impact server operation.
  425. % DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1
  426. A debug message issued when the server is attempting to delete a lease for
  427. the specified address from the PostgreSQL database for the specified address.
  428. % DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  429. A debug message issued when the server is attempting to obtain an IPv4
  430. lease from the PostgreSQL database for the specified address.
  431. % DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)
  432. A debug message issued when the server is attempting to obtain an IPv6
  433. lease from the PostgreSQL database for the specified address.
  434. % DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  435. A debug message issued when the server is attempting to obtain a set
  436. of IPv4 leases from the PostgreSQL database for a client with the specified
  437. client identification.
  438. % DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  439. A debug message issued when the server is attempting to obtain a set
  440. of IPv4 leases from the PostgreSQL database for a client with the specified
  441. hardware address.
  442. % DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
  443. A debug message issued when the server is attempting to obtain a set of
  444. IPv6 lease from the PostgreSQL database for a client with the specified IAID
  445. (Identity Association ID) and DUID (DHCP Unique Identifier).
  446. % DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
  447. A debug message issued when the server is attempting to obtain an IPv6
  448. lease from the PostgreSQL database for a client with the specified IAID
  449. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  450. % DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  451. A debug message issued when the server is attempting to obtain an IPv4
  452. lease from the PostgreSQL database for a client with the specified subnet ID
  453. and client ID.
  454. % DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  455. A debug message issued when the server is attempting to obtain an IPv4
  456. lease from the PostgreSQL database for a client with the specified subnet ID
  457. and hardware address.
  458. % DHCPSRV_PGSQL_GET_VERSION obtaining schema version information
  459. A debug message issued when the server is about to obtain schema version
  460. information from the PostgreSQL database.
  461. % DHCPSRV_PGSQL_ROLLBACK rolling back PostgreSQL database
  462. The code has issued a rollback call. All outstanding transaction will
  463. be rolled back and not committed to the database.
  464. % DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  465. A debug message issued when the server is attempting to update IPv4
  466. lease from the PostgreSQL database for the specified address.
  467. % DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1
  468. A debug message issued when the server is attempting to update IPv6
  469. lease from the PostgreSQL database for the specified address.
  470. % DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'
  471. The parameters for access the lease database were passed to the server through
  472. the named configuration parameter, but the code was expecting them to be
  473. passed via the parameter named "lease-database". If the database opens
  474. successfully, there is no impact on server operation. However, as this does
  475. indicate an error in the source code, please submit a bug report.
  476. % DHCPSRV_UNKNOWN_DB unknown database type: %1
  477. The database access string specified a database type (given in the
  478. message) that is unknown to the software. This is a configuration error.