dhcpsrv_messages.mes 50 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943
  1. # Copyright (C) 2012-2017 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # This Source Code Form is subject to the terms of the Mozilla Public
  4. # License, v. 2.0. If a copy of the MPL was not distributed with this
  5. # file, You can obtain one at http://mozilla.org/MPL/2.0/.
  6. $NAMESPACE isc::dhcp
  7. % DHCPSRV_CFGMGR_ADD_IFACE listening on interface %1
  8. An info message issued when a new interface is being added to the collection of
  9. interfaces on which the server listens to DHCP messages.
  10. % DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet %1
  11. A debug message reported when the DHCP configuration manager is adding the
  12. specified IPv4 subnet to its database.
  13. % DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet %1
  14. A debug message reported when the DHCP configuration manager is adding the
  15. specified IPv6 subnet to its database.
  16. % DHCPSRV_CFGMGR_ALL_IFACES_ACTIVE enabling listening on all interfaces
  17. A debug message issued when the server is being configured to listen on all
  18. interfaces.
  19. % DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to: %1
  20. A debug message issued when the server's DHCP-DDNS settings are changed.
  21. % DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces
  22. A debug message issued when configuration manager clears the internal list
  23. of active interfaces. This doesn't prevent the server from listening to
  24. the DHCP traffic through open sockets, but will rather be used by Interface
  25. Manager to select active interfaces when sockets are re-opened.
  26. % DHCPSRV_CFGMGR_CONFIGURE_SERVERID server configuration includes specification of a server identifier
  27. This warning message is issued when the server specified configuration of
  28. a server identifier. If this new configuration overrides an existing
  29. server identifier, this will affect existing bindings of the clients.
  30. Clients will use old server identifier when they renew their bindings.
  31. The server will not respond to those renews, and the clients will
  32. eventually transition to rebinding state. The server should reassign
  33. existing bindings and the clients will subsequently use new server
  34. identifier. It is recommended to not modify the server identifier, unless
  35. there is a good reason for it, to avoid increased number of renewals and
  36. a need for rebinding (increase of multicast traffic, which may be received
  37. by multiple servers).
  38. % DHCPSRV_CFGMGR_NO_SUBNET4 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 IPv4 subnet for the specified address, but no such
  41. subnet exists.
  42. % DHCPSRV_CFGMGR_NO_SUBNET6 no suitable subnet is defined for address hint %1
  43. This debug message is output when the DHCP configuration manager has received
  44. a request for an IPv6 subnet for the specified address, but no such
  45. subnet exists.
  46. % DHCPSRV_CFGMGR_ONLY_SUBNET4 retrieved subnet %1 for address hint %2
  47. This is a debug message reporting that the DHCP configuration manager has
  48. returned the specified IPv4 subnet when given the address hint specified
  49. because it is the only subnet defined.
  50. % DHCPSRV_CFGMGR_ONLY_SUBNET6 retrieved subnet %1 for address hint %2
  51. This is a debug message reporting that the DHCP configuration manager has
  52. returned the specified IPv6 subnet when given the address hint specified
  53. because it is the only subnet defined.
  54. % DHCPSRV_CFGMGR_SOCKET_RAW_UNSUPPORTED use of raw sockets is unsupported on this OS, UDP sockets will be used
  55. This warning message is logged when the user specified that the
  56. DHCPv4 server should use the raw sockets to receive the DHCP
  57. messages and respond to the clients, but the use of raw sockets
  58. is not supported on the particular environment. The raw sockets
  59. are useful when the server must respond to the directly connected
  60. clients which don't have an address yet. If the raw sockets are
  61. not supported by Kea on the particular platform, Kea will fall
  62. back to use of the IP/UDP sockets. The responses to
  63. the directly connected clients will be broadcast. The responses
  64. to relayed clients will be unicast as usual.
  65. % DHCPSRV_CFGMGR_SOCKET_TYPE_DEFAULT "dhcp-socket-type" not specified , using default socket type %1
  66. This informational message is logged when the administrator hasn't
  67. specified the "dhcp-socket-type" parameter in configuration for interfaces.
  68. In such case, the default socket type will be used.
  69. % DHCPSRV_CFGMGR_SOCKET_TYPE_SELECT using socket type %1
  70. This informational message is logged when the DHCPv4 server selects the
  71. socket type to be used for all sockets that will be opened on the
  72. interfaces. Typically, the socket type is specified by the server
  73. administrator. If the socket type hasn't been specified, the raw
  74. socket will be selected. If the raw socket has been selected but
  75. Kea doesn't support the use of raw sockets on the particular
  76. OS, it will use an UDP socket instead.
  77. % DHCPSRV_CFGMGR_SUBNET4 retrieved subnet %1 for address hint %2
  78. This is a debug message reporting that the DHCP configuration manager has
  79. returned the specified IPv4 subnet when given the address hint specified
  80. as the address is within the subnet.
  81. % DHCPSRV_CFGMGR_SUBNET4_ADDR selected subnet %1 for packet received by matching address %2
  82. This is a debug message reporting that the DHCP configuration manager
  83. has returned the specified IPv4 subnet for a received packet. This particular
  84. subnet was selected, because an IPv4 address was matched which belonged to that
  85. subnet.
  86. % DHCPSRV_CFGMGR_SUBNET4_IFACE selected subnet %1 for packet received over interface %2
  87. This is a debug message reporting that the DHCP configuration manager
  88. has returned the specified IPv4 subnet for a packet received over
  89. the given interface. This particular subnet was selected, because it
  90. was specified as being directly reachable over the given interface. (see
  91. 'interface' parameter in the subnet4 definition).
  92. % DHCPSRV_CFGMGR_SUBNET4_RELAY selected subnet %1, because of matching relay addr %2
  93. This is a debug message reporting that the DHCP configuration manager has
  94. returned the specified IPv4 subnet, because detected relay agent address
  95. matches value specified for this subnet.
  96. % DHCPSRV_CFGMGR_SUBNET6 retrieved subnet %1 for address hint %2
  97. This is a debug message reporting that the DHCP configuration manager has
  98. returned the specified IPv6 subnet when given the address hint specified
  99. as the address is within the subnet.
  100. % DHCPSRV_CFGMGR_SUBNET6_IFACE selected subnet %1 for packet received over interface %2
  101. This is a debug message reporting that the DHCP configuration manager
  102. has returned the specified IPv6 subnet for a packet received over
  103. given interface. This particular subnet was selected, because it
  104. was specified as being directly reachable over given interface. (see
  105. 'interface' parameter in the subnet6 definition).
  106. % DHCPSRV_CFGMGR_SUBNET6_IFACE_ID selected subnet %1 (interface-id match) for incoming packet
  107. This is a debug message reporting that the DHCP configuration manager
  108. has returned the specified IPv6 subnet for a received packet. This particular
  109. subnet was selected, because value of interface-id option matched what was
  110. configured in the server's interface-id option for that selected subnet6.
  111. (see 'interface-id' parameter in the subnet6 definition).
  112. % DHCPSRV_CFGMGR_SUBNET6_RELAY selected subnet %1, because of matching relay addr %2
  113. This is a debug message reporting that the DHCP configuration manager has
  114. returned the specified IPv6 subnet, because detected relay agent address
  115. matches value specified for this subnet.
  116. % DHCPSRV_CFGMGR_UNICAST_LINK_LOCAL specified link local address %1 for unicast traffic on interface %2
  117. This warning message is logged when user specified a link-local address to
  118. receive unicast traffic. The warning message is issued because it is an
  119. uncommon use.
  120. % DHCPSRV_CFGMGR_USE_ADDRESS listening on address %1, on interface %2
  121. A message issued when the server is configured to listen on the explicitly specified
  122. IP address on the given interface.
  123. % DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address %1, on interface %2
  124. An info message issued when configuring the DHCP server to listen on the unicast
  125. address on the specific interface.
  126. % DHCPSRV_CLOSE_DB closing currently open %1 database
  127. This is a debug message, issued when the DHCP server closes the currently
  128. open lease database. It is issued at program shutdown and whenever
  129. the database access parameters are changed: in the latter case, the
  130. server closes the currently open database, and opens a database using
  131. the new parameters.
  132. % DHCPSRV_CQL_ADD_ADDR4 adding IPv4 lease with address %1
  133. A debug message issued when the server is about to add an IPv4 lease
  134. with the specified address to the Cassandra backend database.
  135. % DHCPSRV_CQL_ADD_ADDR6 adding IPv6 lease with address %1
  136. A debug message issued when the server is about to add an IPv6 lease
  137. with the specified address to the Cassandra backend database.
  138. % DHCPSRV_CQL_COMMIT committing to Cassandra database
  139. A commit call been issued on the server. For Cassandra, this is a no-op.
  140. % DHCPSRV_CQL_DB opening Cassandra lease database: %1
  141. This informational message is logged when a DHCP server (either V4 or
  142. V6) is about to open a Cassandra lease database. The parameters of
  143. the connection including database name and username needed to access it
  144. (but not the password if any) are logged.
  145. % DHCPSRV_CQL_DELETE_ADDR deleting lease for address %1
  146. A debug message issued when the server is attempting to delete a lease from the
  147. Cassandra database for the specified address.
  148. % DHCPSRV_CQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  149. A debug message issued when the server is removing reclaimed DHCPv4
  150. leases which have expired longer than a specified period of time.
  151. The argument is the amount of time Kea waits after a reclaimed
  152. lease expires before considering its removal.
  153. % DHCPSRV_CQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  154. A debug message issued when the server is removing reclaimed DHCPv6
  155. leases which have expired longer than a specified period of time.
  156. The argument is the amount of time Kea waits after a reclaimed
  157. lease expires before considering its removal.
  158. % DHCPSRV_CQL_GET_ADDR4 obtaining IPv4 lease for address %1
  159. A debug message issued when the server is attempting to obtain an IPv4
  160. lease from the Cassandra database for the specified address.
  161. % DHCPSRV_CQL_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
  162. A debug message issued when the server is attempting to obtain an IPv6
  163. lease from the Cassandra database for the specified address.
  164. % DHCPSRV_CQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  165. A debug message issued when the server is attempting to obtain a set of
  166. IPv4 leases from the Cassandra database for a client with the specified
  167. client identification.
  168. % DHCPSRV_CQL_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3
  169. A debug message issued when the server is attempting to obtain an IPv4
  170. lease from the Cassandra database for a client with the specified
  171. client ID, hardware address and subnet ID.
  172. % DHCPSRV_CQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  173. A debug message issued when the server is attempting to obtain expired
  174. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  175. is logged in the message.
  176. % DHCPSRV_CQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  177. A debug message issued when the server is attempting to obtain expired
  178. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  179. is logged in the message.
  180. % DHCPSRV_CQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  181. A debug message issued when the server is attempting to obtain a set of
  182. IPv4 leases from the Cassandra database for a client with the specified
  183. hardware address.
  184. % DHCPSRV_CQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %3
  185. A debug message issued when the server is attempting to obtain a set of IPv6
  186. leases from the Cassandra database for a client with the specified IAID
  187. (Identity Association ID) and DUID (DHCP Unique Identifier).
  188. % DHCPSRV_CQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
  189. A debug message issued when the server is attempting to obtain an IPv6
  190. lease from the Cassandra database for a client with the specified IAID
  191. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  192. % DHCPSRV_CQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  193. A debug message issued when the server is attempting to obtain an IPv4
  194. lease from the Cassandra database for a client with the specified
  195. subnet ID and client ID.
  196. % DHCPSRV_CQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  197. A debug message issued when the server is attempting to obtain an IPv4
  198. lease from the Cassandra database for a client with the specified
  199. subnet ID and hardware address.
  200. % DHCPSRV_CQL_GET_VERSION obtaining schema version information
  201. A debug message issued when the server is about to obtain schema version
  202. information from the Cassandra database.
  203. % DHCPSRV_CQL_ROLLBACK rolling back Cassandra database
  204. The code has issued a rollback call. For Cassandra, this is
  205. a no-op.
  206. % DHCPSRV_CQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  207. A debug message issued when the server is attempting to update IPv4
  208. lease from the Cassandra database for the specified address.
  209. % DHCPSRV_CQL_UPDATE_ADDR6 updating IPv6 lease for address %1
  210. A debug message issued when the server is attempting to update IPv6
  211. lease from the Cassandra database for the specified address.
  212. % DHCPSRV_DHCP4O6_RECEIVED_BAD_PACKET received bad DHCPv4o6 packet: %1
  213. A bad DHCPv4o6 packet was received.
  214. % DHCPSRV_DHCP_DDNS_ERROR_EXCEPTION error handler for DHCP_DDNS IO generated an expected exception: %1
  215. This is an error message that occurs when an attempt to send a request to
  216. kea-dhcp-ddns fails there registered error handler threw an uncaught exception.
  217. This is a programmatic error which should not occur. By convention, the error
  218. handler should not propagate exceptions. Please report this error.
  219. % DHCPSRV_DHCP_DDNS_HANDLER_NULL error handler for DHCP_DDNS IO is not set.
  220. This is an error message that occurs when an attempt to send a request to
  221. kea-dhcp-ddns fails and there is no registered error handler. This is a
  222. programmatic error which should never occur and should be reported.
  223. % DHCPSRV_DHCP_DDNS_NCR_REJECTED NameChangeRequest rejected by the sender: %1, ncr: %2
  224. This is an error message indicating that NameChangeSender used to deliver DDNS
  225. update requests to kea-dhcp-ddns rejected the request. This most likely cause
  226. is the sender's queue has reached maximum capacity. This would imply that
  227. requests are being generated faster than they can be delivered.
  228. % DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: %1
  229. A debug message issued when a NameChangeRequest has been successfully sent to
  230. kea-dhcp-ddns.
  231. % DHCPSRV_DHCP_DDNS_SENDER_STARTED NameChangeRequest sender has been started: %1
  232. A informational message issued when a communications with kea-dhcp-ddns has
  233. been successfully started.
  234. % DHCPSRV_DHCP_DDNS_SENDER_STOPPED NameChangeRequest sender has been stopped.
  235. A informational message issued when a communications with kea-dhcp-ddns has
  236. been stopped. This normally occurs during reconfiguration and as part of normal
  237. shutdown. It may occur if kea-dhcp-ddns communications breakdown.
  238. % DHCPSRV_DHCP_DDNS_SUSPEND_UPDATES DHCP_DDNS updates are being suspended.
  239. This is a warning message indicating the DHCP_DDNS updates have been turned
  240. off. This should only occur if IO errors communicating with kea-dhcp-ddns
  241. have been experienced. Any such errors should have preceding entries in the
  242. log with details. No further attempts to communicate with kea-dhcp-ddns will
  243. be made without intervention.
  244. % DHCPSRV_HOOK_LEASE4_RECOVER_SKIP DHCPv4 lease %1 was not recovered from the declined state because a callout set the skip status.
  245. This debug message is printed when a callout installed on lease4_recover
  246. hook point set the next step status to SKIP. For this particular hook point, this
  247. indicates that the server should not recover the lease from declined state.
  248. The server will leave the lease as it is, in the declined state. The
  249. server will attempt to recover it the next time decline recovery procedure
  250. takes place.
  251. % DHCPSRV_HOOK_LEASE4_RENEW_SKIP DHCPv4 lease was not renewed because a callout set the skip flag.
  252. This debug message is printed when a callout installed on lease4_renew
  253. hook point set the skip flag. For this particular hook point, the setting
  254. of the flag by a callout instructs the server to not renew a lease. The
  255. server will use existing lease as it is, without extending its lifetime.
  256. % DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.
  257. This debug message is printed when a callout installed on lease4_select
  258. hook point sets the skip flag. It means that the server was told that
  259. no lease4 should be assigned. The server will not put that lease in its
  260. database and the client will get a NAK packet.
  261. % DHCPSRV_HOOK_LEASE6_EXTEND_SKIP DHCPv6 lease lifetime was not extended because a callout set the skip flag for message %1
  262. This debug message is printed when a callout installed on lease6_renew
  263. or the lease6_rebind hook point set the skip flag. For this particular hook
  264. point, the setting of the flag by a callout instructs the server to not
  265. extend the lifetime for a lease. If the client requested renewal of multiple
  266. leases (by sending multiple IA options), the server will skip the renewal
  267. of the one in question and will proceed with other renewals as usual.
  268. % DHCPSRV_HOOK_LEASE6_RECOVER_SKIP DHCPv6 lease %1 was not recovered from declined state because a callout set the skip status.
  269. This debug message is printed when a callout installed on lease6_recover
  270. hook point set the next step status to SKIP. For this particular hook point, this
  271. indicates that the server should not recover the lease from declined state.
  272. The server will leave the lease as it is, in the declined state. The
  273. server will attempt to recover it the next time decline recovery procedure
  274. takes place.
  275. % DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.
  276. This debug message is printed when a callout installed on lease6_select
  277. hook point sets the skip flag. It means that the server was told that
  278. no lease6 should be assigned. The server will not put that lease in its
  279. database and the client will get a NoAddrsAvail for that IA_NA option.
  280. % DHCPSRV_INVALID_ACCESS invalid database access string: %1
  281. This is logged when an attempt has been made to parse a database access string
  282. and the attempt ended in error. The access string in question - which
  283. should be of the form 'keyword=value keyword=value...' is included in
  284. the message.
  285. % DHCPSRV_MEMFILE_ADD_ADDR4 adding IPv4 lease with address %1
  286. A debug message issued when the server is about to add an IPv4 lease
  287. with the specified address to the memory file backend database.
  288. % DHCPSRV_MEMFILE_ADD_ADDR6 adding IPv6 lease with address %1
  289. A debug message issued when the server is about to add an IPv6 lease
  290. with the specified address to the memory file backend database.
  291. % DHCPSRV_MEMFILE_COMMIT committing to memory file database
  292. The code has issued a commit call. For the memory file database, this is
  293. a no-op.
  294. % DHCPSRV_MEMFILE_CONVERTING_LEASE_FILES running LFC now to convert lease files to the current schema: %1.%2
  295. A warning message issued when the server has detected lease files that need
  296. to be either upgraded or downgraded to match the server's schema, and that
  297. the server is automatically running the LFC process to perform the conversion.
  298. This should only occur the first time the server is launched following a Kea
  299. installation upgrade (or downgrade).
  300. % DHCPSRV_MEMFILE_DB opening memory file lease database: %1
  301. This informational message is logged when a DHCP server (either V4 or
  302. V6) is about to open a memory file lease database. The parameters of
  303. the connection including database name and username needed to access it
  304. (but not the password if any) are logged.
  305. % DHCPSRV_MEMFILE_DELETE_ADDR deleting lease for address %1
  306. A debug message issued when the server is attempting to delete a lease
  307. for the specified address from the memory file database for the specified
  308. address.
  309. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  310. A debug message issued when the server is removing reclaimed DHCPv4
  311. leases which have expired longer than a specified period of time.
  312. The argument is the amount of time Kea waits after a reclaimed
  313. lease expires before considering its removal.
  314. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  315. A debug message issued when the server is removing reclaimed DHCPv6
  316. leases which have expired longer than a specified period of time.
  317. The argument is the amount of time Kea waits after a reclaimed
  318. lease expires before considering its removal.
  319. % DHCPSRV_MEMFILE_DELETE_EXPIRED_RECLAIMED_START starting deletion of %1 expired-reclaimed leases
  320. A debug message issued when the server has found expired-reclaimed
  321. leases to be removed. The number of leases to be removed is logged
  322. in the message.
  323. % DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1
  324. A debug message issued when the server is attempting to obtain an IPv4
  325. lease from the memory file database for the specified address.
  326. % DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
  327. A debug message issued when the server is attempting to obtain an IPv6
  328. lease from the memory file database for the specified address.
  329. % DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1
  330. A debug message issued when the server is attempting to obtain a set of
  331. IPv4 leases from the memory file database for a client with the specified
  332. client identification.
  333. % DHCPSRV_MEMFILE_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3
  334. A debug message issued when the server is attempting to obtain an IPv4
  335. lease from the memory file database for a client with the specified
  336. client ID, hardware address and subnet ID.
  337. % DHCPSRV_MEMFILE_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  338. A debug message issued when the server is attempting to obtain expired
  339. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  340. is logged in the message.
  341. % DHCPSRV_MEMFILE_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  342. A debug message issued when the server is attempting to obtain expired
  343. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  344. is logged in the message.
  345. % DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %1
  346. A debug message issued when the server is attempting to obtain a set of
  347. IPv4 leases from the memory file database for a client with the specified
  348. hardware address.
  349. % DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %3
  350. A debug message issued when the server is attempting to obtain a set of IPv6
  351. leases from the memory file database for a client with the specified IAID
  352. (Identity Association ID) and DUID (DHCP Unique Identifier).
  353. % DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
  354. A debug message issued when the server is attempting to obtain an IPv6
  355. lease from the memory file database for a client with the specified IAID
  356. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  357. % DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  358. A debug message issued when the server is attempting to obtain an IPv4
  359. lease from the memory file database for a client with the specified
  360. subnet ID and client ID.
  361. % DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  362. A debug message issued when the server is attempting to obtain an IPv4
  363. lease from the memory file database for a client with the specified
  364. subnet ID and hardware address.
  365. % DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information
  366. A debug message issued when the server is about to obtain schema version
  367. information from the memory file database.
  368. % DHCPSRV_MEMFILE_LEASE_FILE_LOAD loading leases from file %1
  369. An info message issued when the server is about to start reading DHCP leases
  370. from the lease file. All leases currently held in the memory will be
  371. replaced by those read from the file.
  372. % DHCPSRV_MEMFILE_LEASE_LOAD loading lease %1
  373. A debug message issued when DHCP lease is being loaded from the file to memory.
  374. % DHCPSRV_MEMFILE_LEASE_LOAD_ROW_ERROR discarding row %1, error: %2
  375. An error message issued the the DHCP lease being loaded from the given row of
  376. the lease file fails. The log message should contain the specific reason the
  377. row was discarded. The server will continue loading the remaining data.
  378. This may indicate a corrupt lease file.
  379. % DHCPSRV_MEMFILE_LFC_EXECUTE executing Lease File Cleanup using: %1
  380. An informational message issued when the Memfile lease database backend
  381. starts a new process to perform Lease File Cleanup.
  382. % DHCPSRV_MEMFILE_LFC_LEASE_FILE_RENAME_FAIL failed to rename the current lease file %1 to %2, reason: %3
  383. An error message logged when the Memfile lease database backend fails to
  384. move the current lease file to a new file on which the cleanup should
  385. be performed. This effectively means that the lease file cleanup
  386. will not take place.
  387. % 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!
  388. An error message logged when the Memfile lease database backend
  389. failed to re-open or re-create the lease file after renaming the
  390. lease file for lease file cleanup. The server will continue to
  391. operate but leases will not be persisted to disk.
  392. % DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to %1 sec
  393. An informational message logged when the Memfile lease database backend
  394. configures the LFC to be executed periodically. The argument holds the
  395. interval in seconds in which the LFC will be executed.
  396. % DHCPSRV_MEMFILE_LFC_SPAWN_FAIL lease file cleanup failed to run because kea-lfc process couldn't be spawned
  397. This error message is logged when the Kea server fails to run kea-lfc,
  398. the program that cleans up the lease file. The server will try again the
  399. next time a lease file cleanup is scheduled. Although this message should
  400. not appear and the reason why it did investigated, the occasional failure
  401. to start the lease file cleanup will not impact operations. Should the
  402. failure persist however, the size of the lease file will increase without bound.
  403. % DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
  404. An informational message issued when the Memfile lease database backend
  405. starts the periodic Lease File Cleanup.
  406. % DHCPSRV_MEMFILE_LFC_UNREGISTER_TIMER_FAILED failed to unregister timer 'memfile-lfc': %1
  407. This debug message is logged when Memfile backend fails to unregister
  408. timer used for lease file cleanup scheduling. There are several reasons
  409. why this could occur, although the most likely cause is that the system
  410. is being shut down and some other component has unregistered the timer.
  411. The message includes the reason for this error.
  412. % DHCPSRV_MEMFILE_NEEDS_DOWNGRADING version of lease file: %1 schema is later than version %2
  413. A warning message issued when the schema of the lease file loaded by the server
  414. is newer than the memfile schema of the server. The server converts the lease
  415. data from newer schemas to its schema as it is read, therefore the lease
  416. information in use by the server will be correct. Note though, that any data
  417. stored in newer schema fields will be dropped. What remains is for the
  418. file itself to be rewritten using the current schema.
  419. % DHCPSRV_MEMFILE_NEEDS_UPGRADING version of lease file: %1 schema is earlier than version %2
  420. A warning message issued when the schema of the lease file loaded by the server
  421. pre-dates the memfile schema of the server. Note that the server converts the
  422. lease data from older schemas to the current schema as it is read, therefore
  423. the lease information in use by the server will be correct. What remains is
  424. for the file itself to be rewritten using the current schema.
  425. % DHCPSRV_MEMFILE_NO_STORAGE running in non-persistent mode, leases will be lost after restart
  426. A warning message issued when writes of leases to disk have been disabled
  427. in the configuration. This mode is useful for some kinds of performance
  428. testing but should not be enabled in normal circumstances. Non-persistence
  429. mode is enabled when 'persist4=no persist6=no' parameters are specified
  430. in the database access string.
  431. % DHCPSRV_MEMFILE_READ_HWADDR_FAIL failed to read hardware address from lease file: %1
  432. A warning message issued when read attempt of the hardware address stored in
  433. a disk file failed. The parameter should provide the exact nature of the failure.
  434. The database read will continue, but that particular lease will no longer
  435. have hardware address associated with it.
  436. % DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database
  437. The code has issued a rollback call. For the memory file database, this is
  438. a no-op.
  439. % DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1
  440. A debug message issued when the server is attempting to update IPv4
  441. lease from the memory file database for the specified address.
  442. % DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1
  443. A debug message issued when the server is attempting to update IPv6
  444. lease from the memory file database for the specified address.
  445. % DHCPSRV_MULTIPLE_RAW_SOCKETS_PER_IFACE current configuration will result in opening multiple broadcast capable sockets on some interfaces and some DHCP messages may be duplicated
  446. A warning message issued when the current configuration indicates that multiple
  447. sockets, capable of receiving broadcast traffic, will be opened on some of the
  448. interfaces. It must be noted that this may lead to receiving and processing
  449. the same DHCP message multiple times, as it will be received by each socket
  450. individually.
  451. % DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %1
  452. A debug message issued when the server is about to add an IPv4 lease
  453. with the specified address to the MySQL backend database.
  454. % DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
  455. A debug message issued when the server is about to add an IPv6 lease
  456. with the specified address to the MySQL backend database.
  457. % DHCPSRV_MYSQL_COMMIT committing to MySQL database
  458. The code has issued a commit call. All outstanding transactions will be
  459. committed to the database. Note that depending on the MySQL settings,
  460. the committal may not include a write to disk.
  461. % DHCPSRV_MYSQL_DB opening MySQL lease database: %1
  462. This informational message is logged when a DHCP server (either V4 or
  463. V6) is about to open a MySQL lease database. The parameters of the
  464. connection including database name and username needed to access it
  465. (but not the password if any) are logged.
  466. % DHCPSRV_MYSQL_DELETED_EXPIRED_RECLAIMED deleted %1 reclaimed leases from the database
  467. A debug message issued when the server has removed a number of reclaimed
  468. leases from the database. The number of removed leases is included in the
  469. message.
  470. % DHCPSRV_MYSQL_DELETE_ADDR deleting lease for address %1
  471. A debug message issued when the server is attempting to delete a lease for
  472. the specified address from the MySQL database for the specified address.
  473. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  474. A debug message issued when the server is removing reclaimed DHCPv4
  475. leases which have expired longer than a specified period of time.
  476. The argument is the amount of time Kea waits after a reclaimed
  477. lease expires before considering its removal.
  478. % DHCPSRV_MYSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  479. A debug message issued when the server is removing reclaimed DHCPv6
  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_MYSQL_FATAL_ERROR Unrecoverable MySQL error occurred: %1 for <%2>, reason: %3 (error code: %4). Server exiting now!
  484. An error message indicating that communication with the MySQL database server
  485. has been lost. When this occurs the server exits immediately with a non-zero
  486. exit code. This is most likely due to a network issue.
  487. % DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  488. A debug message issued when the server is attempting to obtain an IPv4
  489. lease from the MySQL database for the specified address.
  490. % DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2
  491. A debug message issued when the server is attempting to obtain an IPv6
  492. lease from the MySQL database for the specified address.
  493. % DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  494. A debug message issued when the server is attempting to obtain a set
  495. of IPv4 leases from the MySQL database for a client with the specified
  496. client identification.
  497. % DHCPSRV_MYSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  498. A debug message issued when the server is attempting to obtain expired
  499. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  500. is logged in the message.
  501. % DHCPSRV_MYSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  502. A debug message issued when the server is attempting to obtain expired
  503. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  504. is logged in the message.
  505. % DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  506. A debug message issued when the server is attempting to obtain a set
  507. of IPv4 leases from the MySQL database for a client with the specified
  508. hardware address.
  509. % DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
  510. A debug message issued when the server is attempting to obtain a set of IPv6
  511. leases from the MySQL database for a client with the specified IAID (Identity
  512. Association ID) and DUID (DHCP Unique Identifier).
  513. % DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
  514. A debug message issued when the server is attempting to obtain an IPv6
  515. lease from the MySQL database for a client with the specified IAID
  516. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  517. % DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  518. A debug message issued when the server is attempting to obtain an IPv4
  519. lease from the MySQL database for a client with the specified subnet ID
  520. and client ID.
  521. % DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  522. A debug message issued when the server is attempting to obtain an IPv4
  523. lease from the MySQL database for a client with the specified subnet ID
  524. and hardware address.
  525. % DHCPSRV_MYSQL_GET_VERSION obtaining schema version information
  526. A debug message issued when the server is about to obtain schema version
  527. information from the MySQL database.
  528. % DHCPSRV_MYSQL_HOST_DB opening MySQL hosts database: %1
  529. This informational message is logged when a DHCP server (either V4 or
  530. V6) is about to open a MySQL hosts database. The parameters of the
  531. connection including database name and username needed to access it
  532. (but not the password if any) are logged.
  533. % DHCPSRV_MYSQL_HOST_DB_GET_VERSION obtaining schema version information for the MySQL hosts database
  534. A debug message issued when the server is about to obtain schema version
  535. information from the MySQL hosts database.
  536. % DHCPSRV_MYSQL_HOST_DB_READONLY MySQL host database opened for read access only
  537. This informational message is issued when the user has configured the MySQL
  538. database in read-only mode. Kea will not be able to insert or modify
  539. host reservations but will be able to retrieve existing ones and
  540. assign them to the clients communicating with the server.
  541. % DHCPSRV_MYSQL_ROLLBACK rolling back MySQL database
  542. The code has issued a rollback call. All outstanding transaction will
  543. be rolled back and not committed to the database.
  544. % DHCPSRV_MYSQL_START_TRANSACTION starting new MySQL transaction
  545. A debug message issued whena new MySQL transaction is being started.
  546. This message is typically not issued when inserting data into a
  547. single table because the server doesn't explicitly start
  548. transactions in this case. This message is issued when data is
  549. inserted into multiple tables with multiple INSERT statements
  550. and there may be a need to rollback the whole transaction if
  551. any of these INSERT statements fail.
  552. % DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  553. A debug message issued when the server is attempting to update IPv4
  554. lease from the MySQL database for the specified address.
  555. % DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
  556. A debug message issued when the server is attempting to update IPv6
  557. lease from the MySQL database for the specified address.
  558. % DHCPSRV_NOTYPE_DB no 'type' keyword to determine database backend: %1
  559. This is an error message, logged when an attempt has been made to access
  560. a database backend, but where no 'type' keyword has been included in
  561. the access string. The access string (less any passwords) is included
  562. in the message.
  563. % DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
  564. This warning message is issued when the current server configuration specifies
  565. no interfaces that the server should listen on, or when the specified interfaces are not
  566. configured to receive the traffic.
  567. % DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: %1
  568. A warning message issued when IfaceMgr fails to open and bind a socket.
  569. The reason for the failure is appended as an argument of the log message.
  570. % DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %1
  571. A debug message issued when the server is about to add an IPv4 lease
  572. with the specified address to the PostgreSQL backend database.
  573. % DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1
  574. A debug message issued when the server is about to add an IPv6 lease
  575. with the specified address to the PostgreSQL backend database.
  576. % DHCPSRV_PGSQL_COMMIT committing to MySQL database
  577. The code has issued a commit call. All outstanding transactions will be
  578. committed to the database. Note that depending on the PostgreSQL settings,
  579. the committal may not include a write to disk.
  580. % DHCPSRV_PGSQL_DB opening PostgreSQL lease database: %1
  581. This informational message is logged when a DHCP server (either V4 or
  582. V6) is about to open a PostgreSQL lease database. The parameters of the
  583. connection including database name and username needed to access it
  584. (but not the password if any) are logged.
  585. % DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
  586. This is an error message issued when a DHCP server (either V4 or V6) experienced
  587. and error freeing database SQL resources as part of closing its connection to
  588. the Postgresql database. The connection is closed as part of normal server
  589. shutdown. This error is most likely a programmatic issue that is highly
  590. unlikely to occur or negatively impact server operation.
  591. % DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1
  592. A debug message issued when the server is attempting to delete a lease for
  593. the specified address from the PostgreSQL database for the specified address.
  594. % DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED4 deleting reclaimed IPv4 leases that expired more than %1 seconds ago
  595. A debug message issued when the server is removing reclaimed DHCPv4
  596. leases which have expired longer than a specified period of time.
  597. The argument is the amount of time Kea waits after a reclaimed
  598. lease expires before considering its removal.
  599. % DHCPSRV_PGSQL_DELETE_EXPIRED_RECLAIMED6 deleting reclaimed IPv6 leases that expired more than %1 seconds ago
  600. A debug message issued when the server is removing reclaimed DHCPv6
  601. leases which have expired longer than a specified period of time.
  602. The argument is the amount of time Kea waits after a reclaimed
  603. lease expires before considering its removal.
  604. % DHCPSRV_PGSQL_FATAL_ERROR Unrecoverable PostgreSQL error occurred: Statement: <%1>, reason: %2 (error code: %3). Server exiting now!
  605. An error message indicating that communication with the MySQL database server
  606. has been lost. When this occurs the server exits immediately with a non-zero
  607. exit code. This is most likely due to a network issue.
  608. % DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  609. A debug message issued when the server is attempting to obtain an IPv4
  610. lease from the PostgreSQL database for the specified address.
  611. % DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)
  612. A debug message issued when the server is attempting to obtain an IPv6
  613. lease from the PostgreSQL database for the specified address.
  614. % DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  615. A debug message issued when the server is attempting to obtain a set
  616. of IPv4 leases from the PostgreSQL database for a client with the specified
  617. client identification.
  618. % DHCPSRV_PGSQL_GET_EXPIRED4 obtaining maximum %1 of expired IPv4 leases
  619. A debug message issued when the server is attempting to obtain expired
  620. IPv4 leases to reclaim them. The maximum number of leases to be retrieved
  621. is logged in the message.
  622. % DHCPSRV_PGSQL_GET_EXPIRED6 obtaining maximum %1 of expired IPv6 leases
  623. A debug message issued when the server is attempting to obtain expired
  624. IPv6 leases to reclaim them. The maximum number of leases to be retrieved
  625. is logged in the message.
  626. % DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  627. A debug message issued when the server is attempting to obtain a set
  628. of IPv4 leases from the PostgreSQL database for a client with the specified
  629. hardware address.
  630. % DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
  631. A debug message issued when the server is attempting to obtain a set of IPv6
  632. leases from the PostgreSQL database for a client with the specified IAID
  633. (Identity Association ID) and DUID (DHCP Unique Identifier).
  634. % DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
  635. A debug message issued when the server is attempting to obtain an IPv6
  636. lease from the PostgreSQL database for a client with the specified IAID
  637. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  638. % DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  639. A debug message issued when the server is attempting to obtain an IPv4
  640. lease from the PostgreSQL database for a client with the specified subnet ID
  641. and client ID.
  642. % DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  643. A debug message issued when the server is attempting to obtain an IPv4
  644. lease from the PostgreSQL database for a client with the specified subnet ID
  645. and hardware address.
  646. % DHCPSRV_PGSQL_GET_VERSION obtaining schema version information
  647. A debug message issued when the server is about to obtain schema version
  648. information from the PostgreSQL database.
  649. % DHCPSRV_PGSQL_HOST_DB opening PostgreSQL hosts database: %1
  650. This informational message is logged when a DHCP server (either V4 or
  651. V6) is about to open a PostgreSQL hosts database. The parameters of the
  652. connection including database name and username needed to access it
  653. (but not the password if any) are logged.
  654. % DHCPSRV_PGSQL_HOST_DB_GET_VERSION obtaining schema version information for the PostgreSQL hosts database
  655. A debug message issued when the server is about to obtain schema version
  656. information from the PostgreSQL hosts database.
  657. % DHCPSRV_PGSQL_HOST_DB_READONLY PostgreSQL host database opened for read access only
  658. This informational message is issued when the user has configured the PostgreSQL
  659. database in read-only mode. Kea will not be able to insert or modify
  660. host reservations but will be able to retrieve existing ones and
  661. assign them to the clients communicating with the server.
  662. % DHCPSRV_PGSQL_ROLLBACK rolling back PostgreSQL database
  663. The code has issued a rollback call. All outstanding transaction will
  664. be rolled back and not committed to the database.
  665. % DHCPSRV_PGSQL_START_TRANSACTION starting a new PostgreSQL transaction
  666. A debug message issued when a new PostgreSQL transaction is being started.
  667. This message is typically not issued when inserting data into a
  668. single table because the server doesn't explicitly start
  669. transactions in this case. This message is issued when data is
  670. inserted into multiple tables with multiple INSERT statements
  671. and there may be a need to rollback the whole transaction if
  672. any of these INSERT statements fail.
  673. % DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  674. A debug message issued when the server is attempting to update IPv4
  675. lease from the PostgreSQL database for the specified address.
  676. % DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1
  677. A debug message issued when the server is attempting to update IPv6
  678. lease from the PostgreSQL database for the specified address.
  679. % DHCPSRV_QUEUE_NCR %1: name change request to %2 DNS entry queued: %3
  680. A debug message which is logged when the NameChangeRequest to add or remove
  681. a DNS entries for a particular lease has been queued. The first argument
  682. includes the client identification information. The second argument
  683. indicates whether the DNS entry is to be added or removed. The third
  684. argument carries the details of the NameChangeRequest.
  685. % DHCPSRV_QUEUE_NCR_FAILED %1: queueing %2 name change request failed for lease %3: %4
  686. This error message is logged when sending a name change request
  687. to DHCP DDNS failed. The first argument includes the client identification
  688. information. The second argument indicates whether the DNS entry is to be
  689. added or removed. The third argument specifies the leased address. The
  690. last argument provides the reason for failure.
  691. % DHCPSRV_QUEUE_NCR_SKIP %1: skip queueing name change request for lease: %2
  692. This debug message is issued when the server decides to not queue the name
  693. change request because the lease doesn't include the FQDN, the forward and
  694. reverse update is disabled for this lease or the DNS updates are disabled
  695. in the configuration. The first argument includes the client identification
  696. information. The second argument includes the leased address.
  697. % DHCPSRV_TIMERMGR_CALLBACK_FAILED running handler for timer %1 caused exception: %2
  698. This error message is emitted when the timer elapsed and the
  699. operation associated with this timer has thrown an exception.
  700. The timer name and the reason for exception is logged.
  701. % DHCPSRV_TIMERMGR_REGISTER_TIMER registering timer: %1, using interval: %2 ms
  702. A debug message issued when the new interval timer is registered in
  703. the Timer Manager. This timer will have a callback function
  704. associated with it, and this function will be executed according
  705. to the interval specified. The unique name of the timer and the
  706. interval at which the callback function will be executed is
  707. included in the message.
  708. % DHCPSRV_TIMERMGR_RUN_TIMER_OPERATION running operation for timer: %1
  709. A debug message issued when the Timer Manager is about to
  710. run a periodic operation associated with the given timer.
  711. An example of such operation is a periodic cleanup of
  712. expired leases. The name of the timer is included in the
  713. message.
  714. % DHCPSRV_TIMERMGR_SOCKET_CLEAR_FAILED clearing watch socket for timer %1 failed: %2
  715. An error message indicating that the specified timer elapsed,
  716. the operation associated with the timer was executed but the
  717. server was unable to signal this to the worker thread responsible
  718. for dispatching timers. The thread will continue but it will
  719. not be able to dispatch any operations for this timer. The
  720. server reconfiguration or restart may solve the problem
  721. but the situation may repeat.
  722. % DHCPSRV_TIMERMGR_SOCKET_MARK_FAILED marking watch socket for timer %1 failed: %2
  723. An error message indicating that the specified timer elapsed,
  724. but the server was unable to flag that the handler function
  725. should be executed for this timer. The callback will not
  726. be executed this time and most likely the subsequent attempts
  727. will not be successful too. This error is highly unlikely.
  728. The name of the timer and the reason for failure is included
  729. in the message.
  730. % DHCPSRV_TIMERMGR_START_THREAD starting thread for timers
  731. A debug message issued when the Timer Manager is starting a
  732. worker thread to run started timers. The worker thread is
  733. typically started right after all timers have been registered
  734. and runs until timers need to be reconfigured, e.g. their
  735. interval is changed, new timers are registered or existing
  736. timers are unregistered.
  737. % DHCPSRV_TIMERMGR_START_TIMER starting timer: %1
  738. A debug message issued when the registered interval timer is
  739. being started. If this operation is successful the timer will
  740. periodically execute the operation associated with it. The
  741. name of the started timer is included in the message.
  742. % DHCPSRV_TIMERMGR_STOP_THREAD stopping thread for timers
  743. A debug message issued when the Timer Manager is stopping
  744. the worker thread which executes interval timers. When the
  745. thread is stopped no timers will be executed. The thread is
  746. typically stopped at the server reconfiguration or when the
  747. server shuts down.
  748. % DHCPSRV_TIMERMGR_STOP_TIMER stopping timer: %1
  749. A debug message issued when the registered interval timer is
  750. being stopped. The timer remains registered and can be restarted
  751. if necessary. The name of the timer is included in the message.
  752. % DHCPSRV_TIMERMGR_UNREGISTER_ALL_TIMERS unregistering all timers
  753. A debug message issued when all registered interval timers are
  754. being unregistered from the Timer Manager.
  755. % DHCPSRV_TIMERMGR_UNREGISTER_TIMER unregistering timer: %1
  756. A debug message issued when one of the registered interval timers
  757. is unregistered from the Timer Manager. The name of the timer is
  758. included in the message.
  759. % DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'
  760. The parameters for access the lease database were passed to the server through
  761. the named configuration parameter, but the code was expecting them to be
  762. passed via the parameter named "lease-database". If the database opens
  763. successfully, there is no impact on server operation. However, as this does
  764. indicate an error in the source code, please submit a bug report.
  765. % DHCPSRV_UNKNOWN_DB unknown database type: %1
  766. The database access string specified a database type (given in the
  767. message) that is unknown to the software. This is a configuration error.