dhcpsrv_messages.mes 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524
  1. # Copyright (C) 2012-2014 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_ADDRESS4_ALLOC_ERROR error during attempt to allocate an IPv4 address: %1
  16. An error occurred during an attempt to allocate an IPv4 address, the
  17. reason for the failure being contained in the message. The server will
  18. return a message to the client refusing a lease.
  19. % DHCPSRV_ADDRESS4_ALLOC_FAIL failed to allocate an IPv4 address after %1 attempt(s)
  20. The DHCP allocation engine gave up trying to allocate an IPv4 address
  21. after the specified number of attempts. This probably means that the
  22. address pool from which the allocation is being attempted is either
  23. empty, or very nearly empty. As a result, the client will have been
  24. refused a lease.
  25. This message may indicate that your address pool is too small for the
  26. number of clients you are trying to service and should be expanded.
  27. Alternatively, if the you know that the number of concurrently active
  28. clients is less than the addresses you have available, you may want to
  29. consider reducing the lease lifetime. In this way, addresses allocated
  30. to clients that are no longer active on the network will become available
  31. available sooner.
  32. % DHCPSRV_ADDRESS6_ALLOC_ERROR error during attempt to allocate an IPv6 address: %1
  33. An error occurred during an attempt to allocate an IPv6 address, the
  34. reason for the failure being contained in the message. The server will
  35. return a message to the client refusing a lease.
  36. % DHCPSRV_ADDRESS6_ALLOC_FAIL failed to allocate an IPv6 address after %1 attempt(s)
  37. The DHCP allocation engine gave up trying to allocate an IPv6 address
  38. after the specified number of attempts. This probably means that the
  39. address pool from which the allocation is being attempted is either
  40. empty, or very nearly empty. As a result, the client will have been
  41. refused a lease.
  42. This message may indicate that your address pool is too small for the
  43. number of clients you are trying to service and should be expanded.
  44. Alternatively, if the you know that the number of concurrently active
  45. clients is less than the addresses you have available, you may want to
  46. consider reducing the lease lifetime. In this way, addresses allocated
  47. to clients that are no longer active on the network will become available
  48. available sooner.
  49. % DHCPSRV_CFGMGR_ADD_IFACE listening on interface %1
  50. An info message issued when a new interface is being added to the collection of
  51. interfaces on which the server listens to DHCP messages.
  52. % DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet %1
  53. A debug message reported when the DHCP configuration manager is adding the
  54. specified IPv4 subnet to its database.
  55. % DHCPSRV_CFGMGR_ADD_SUBNET6 adding subnet %1
  56. A debug message reported when the DHCP configuration manager is adding the
  57. specified IPv6 subnet to its database.
  58. % DHCPSRV_CFGMGR_ALL_IFACES_ACTIVE enabling listening on all interfaces
  59. A debug message issued when the server is being configured to listen on all
  60. interfaces.
  61. % DHCPSRV_CFGMGR_CFG_DHCP_DDNS Setting DHCP-DDNS configuration to: %1
  62. A debug message issued when the server's DHCP-DDNS settings are changed.
  63. % DHCPSRV_CFGMGR_CLEAR_ACTIVE_IFACES stop listening on all interfaces
  64. A debug message issued when configuration manager clears the internal list
  65. of active interfaces. This doesn't prevent the server from listening to
  66. the DHCP traffic through open sockets, but will rather be used by Interface
  67. Manager to select active interfaces when sockets are re-opened.
  68. % DHCPSRV_CFGMGR_NO_SUBNET4 no suitable subnet is defined for address hint %1
  69. This debug message is output when the DHCP configuration manager has received
  70. a request for an IPv4 subnet for the specified address, but no such
  71. subnet exists.
  72. % DHCPSRV_CFGMGR_NO_SUBNET6 no suitable subnet is defined for address hint %1
  73. This debug message is output when the DHCP configuration manager has received
  74. a request for an IPv6 subnet for the specified address, but no such
  75. subnet exists.
  76. % DHCPSRV_CFGMGR_ONLY_SUBNET4 retrieved subnet %1 for address hint %2
  77. This is a debug message reporting that the DHCP configuration manager has
  78. returned the specified IPv4 subnet when given the address hint specified
  79. because it is the only subnet defined.
  80. % DHCPSRV_CFGMGR_ONLY_SUBNET6 retrieved subnet %1 for address hint %2
  81. This is a debug message reporting that the DHCP configuration manager has
  82. returned the specified IPv6 subnet when given the address hint specified
  83. because it is the only subnet defined.
  84. % DHCPSRV_CFGMGR_SUBNET4 retrieved subnet %1 for address hint %2
  85. This is a debug message reporting that the DHCP configuration manager has
  86. returned the specified IPv4 subnet when given the address hint specified
  87. as the address is within the subnet.
  88. % DHCPSRV_CFGMGR_SUBNET4_RELAY selected subnet %1, because of matching relay addr %2
  89. This is a debug message reporting that the DHCP configuration manager has
  90. returned the specified IPv4 subnet, because detected relay agent address
  91. matches value specified for this subnet.
  92. % DHCPSRV_CFGMGR_SUBNET6 retrieved subnet %1 for address hint %2
  93. This is a debug message reporting that the DHCP configuration manager has
  94. returned the specified IPv6 subnet when given the address hint specified
  95. as the address is within the subnet.
  96. % DHCPSRV_CFGMGR_SUBNET6_IFACE selected subnet %1 for packet received over interface %2
  97. This is a debug message reporting that the DHCP configuration manager
  98. has returned the specified IPv6 subnet for a packet received over
  99. given interface. This particular subnet was selected, because it
  100. was specified as being directly reachable over given interface. (see
  101. 'interface' parameter in the subnet6 definition).
  102. % DHCPSRV_CFGMGR_SUBNET6_IFACE_ID selected subnet %1 (interface-id match) for incoming packet
  103. This is a debug message reporting that the DHCP configuration manager
  104. has returned the specified IPv6 subnet for a received packet. This particular
  105. subnet was selected, because value of interface-id option matched what was
  106. configured in the server's interface-id option for that selected subnet6.
  107. (see 'interface-id' parameter in the subnet6 definition).
  108. % DHCPSRV_CFGMGR_SUBNET6_RELAY selected subnet %1, because of matching relay addr %2
  109. This is a debug message reporting that the DHCP configuration manager has
  110. returned the specified IPv6 subnet, because detected relay agent address
  111. matches value specified for this subnet.
  112. % DHCPSRV_CFGMGR_UNICAST_LINK_LOCAL specified link local address %1 for unicast traffic on interface %2
  113. This warning message is logged when user specified a link-local address to
  114. receive unicast traffic. The warning message is issued because it is an
  115. uncommon use.
  116. % DHCPSRV_CFGMGR_USE_ADDRESS listening on address %1, on interface %2
  117. A message issued when the server is configured to listen on the explicitly specified
  118. IP address on the given interface.
  119. % DHCPSRV_CFGMGR_USE_UNICAST listening on unicast address %1, on interface %2
  120. An info message issued when configuring the DHCP server to listen on the unicast
  121. address on the specific interface.
  122. % DHCPSRV_CLOSE_DB closing currently open %1 database
  123. This is a debug message, issued when the DHCP server closes the currently
  124. open lease database. It is issued at program shutdown and whenever
  125. the database access parameters are changed: in the latter case, the
  126. server closes the currently open database, and opens a database using
  127. the new parameters.
  128. % DHCPSRV_DHCP_DDNS_ERROR_EXCEPTION error handler for DHCP_DDNS IO generated an expected exception: %1
  129. This is an error message that occurs when an attempt to send a request to
  130. kea-dhcp-ddns fails there registered error handler threw an uncaught exception.
  131. This is a programmatic error which should not occur. By convention, the error
  132. handler should not propagate exceptions. Please report this error.
  133. % DHCPSRV_DHCP_DDNS_HANDLER_NULL error handler for DHCP_DDNS IO is not set.
  134. This is an error message that occurs when an attempt to send a request to
  135. kea-dhcp-ddns fails and there is no registered error handler. This is a
  136. programmatic error which should never occur and should be reported.
  137. % DHCPSRV_DHCP_DDNS_NCR_REJECTED NameChangeRequest rejected by the sender: %1, ncr: %2
  138. This is an error message indicating that NameChangeSender used to deliver DDNS
  139. update requests to kea-dhcp-ddns rejected the request. This most likely cause
  140. is the sender's queue has reached maximum capacity. This would imply that
  141. requests are being generated faster than they can be delivered.
  142. % DHCPSRV_DHCP_DDNS_NCR_SENT NameChangeRequest sent to kea-dhcp-ddns: %1
  143. A debug message issued when a NameChangeRequest has been successfully sent to
  144. kea-dhcp-ddns.
  145. % DHCPSRV_DHCP_DDNS_SENDER_STARTED NameChangeRequest sender has been started: %1
  146. A informational message issued when a communications with kea-dhcp-ddns has
  147. been successfully started.
  148. % DHCPSRV_DHCP_DDNS_SENDER_STOPPED NameChangeRequest sender has been stopped.
  149. A informational message issued when a communications with kea-dhcp-ddns has
  150. been stopped. This normally occurs during reconfiguration and as part of normal
  151. shutdown. It may occur if kea-dhcp-ddns communications breakdown.
  152. % DHCPSRV_DHCP_DDNS_SUSPEND_UPDATES DHCP_DDNS updates are being suspended.
  153. This is a warning message indicating the DHCP_DDNS updates have been turned
  154. off. This should only occur if IO errors communicating with kea-dhcp-ddns
  155. have been experienced. Any such errors should have preceding entries in the
  156. log with details. No further attempts to communicate with kea-dhcp-ddns will
  157. be made without intervention.
  158. % DHCPSRV_HOOK_LEASE4_RENEW_SKIP DHCPv4 lease was not renewed because a callout set the skip flag.
  159. This debug message is printed when a callout installed on lease4_renew
  160. hook point set the skip flag. For this particular hook point, the setting
  161. of the flag by a callout instructs the server to not renew a lease. The
  162. server will use existing lease as it is, without extending its lifetime.
  163. % DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.
  164. This debug message is printed when a callout installed on lease4_select
  165. hook point sets the skip flag. It means that the server was told that
  166. no lease4 should be assigned. The server will not put that lease in its
  167. database and the client will get a NAK packet.
  168. % DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.
  169. This debug message is printed when a callout installed on lease6_select
  170. hook point sets the skip flag. It means that the server was told that
  171. no lease6 should be assigned. The server will not put that lease in its
  172. database and the client will get a NoAddrsAvail for that IA_NA option.
  173. % DHCPSRV_INVALID_ACCESS invalid database access string: %1
  174. This is logged when an attempt has been made to parse a database access string
  175. and the attempt ended in error. The access string in question - which
  176. should be of the form 'keyword=value keyword=value...' is included in
  177. the message.
  178. % DHCPSRV_MEMFILE_ADD_ADDR4 adding IPv4 lease with address %1
  179. A debug message issued when the server is about to add an IPv4 lease
  180. with the specified address to the memory file backend database.
  181. % DHCPSRV_MEMFILE_ADD_ADDR6 adding IPv6 lease with address %1
  182. A debug message issued when the server is about to add an IPv6 lease
  183. with the specified address to the memory file backend database.
  184. % DHCPSRV_MEMFILE_COMMIT committing to memory file database
  185. The code has issued a commit call. For the memory file database, this is
  186. a no-op.
  187. % DHCPSRV_MEMFILE_DB opening memory file lease database: %1
  188. This informational message is logged when a DHCP server (either V4 or
  189. V6) is about to open a memory file lease database. The parameters of
  190. the connection including database name and username needed to access it
  191. (but not the password if any) are logged.
  192. % DHCPSRV_MEMFILE_DELETE_ADDR deleting lease for address %1
  193. A debug message issued when the server is attempting to delete a lease
  194. for the specified address from the memory file database for the specified
  195. address.
  196. % DHCPSRV_MEMFILE_GET_ADDR4 obtaining IPv4 lease for address %1
  197. A debug message issued when the server is attempting to obtain an IPv4
  198. lease from the memory file database for the specified address.
  199. % DHCPSRV_MEMFILE_GET_ADDR6 obtaining IPv6 lease for address %1 and lease type %2
  200. A debug message issued when the server is attempting to obtain an IPv6
  201. lease from the memory file database for the specified address.
  202. % DHCPSRV_MEMFILE_GET_CLIENTID obtaining IPv4 leases for client ID %1
  203. A debug message issued when the server is attempting to obtain a set of
  204. IPv4 leases from the memory file database for a client with the specified
  205. client identification.
  206. % DHCPSRV_MEMFILE_GET_CLIENTID_HWADDR_SUBID obtaining IPv4 lease for client ID %1, hardware address %2 and subnet ID %3
  207. A debug message issued when the server is attempting to obtain an IPv4
  208. lease from the memory file database for a client with the specified
  209. client ID, hardware address and subnet ID.
  210. % DHCPSRV_MEMFILE_GET_HWADDR obtaining IPv4 leases for hardware address %1
  211. A debug message issued when the server is attempting to obtain a set of
  212. IPv4 leases from the memory file database for a client with the specified
  213. hardware address.
  214. % DHCPSRV_MEMFILE_GET_IAID_DUID obtaining IPv6 leases for IAID %1 and DUID %2 and lease type %3
  215. A debug message issued when the server is attempting to obtain a set of
  216. IPv6 lease from the memory file database for a client with the specified
  217. IAID (Identity Association ID) and DUID (DHCP Unique Identifier).
  218. % DHCPSRV_MEMFILE_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3 and lease type %4
  219. A debug message issued when the server is attempting to obtain an IPv6
  220. lease from the memory file database for a client with the specified IAID
  221. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  222. % DHCPSRV_MEMFILE_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  223. A debug message issued when the server is attempting to obtain an IPv4
  224. lease from the memory file database for a client with the specified
  225. subnet ID and client ID.
  226. % DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  227. A debug message issued when the server is attempting to obtain an IPv4
  228. lease from the memory file database for a client with the specified
  229. subnet ID and hardware address.
  230. % DHCPSRV_MEMFILE_GET_VERSION obtaining schema version information
  231. A debug message issued when the server is about to obtain schema version
  232. information from the memory file database.
  233. % DHCPSRV_MEMFILE_LEASES_RELOAD4 reloading leases from %1
  234. An info message issued when the server is about to start reading DHCPv4 leases
  235. from the lease file. All leases currently held in the memory will be
  236. replaced by those read from the file.
  237. % DHCPSRV_MEMFILE_LEASES_RELOAD6 reloading leases from %1
  238. An info message issued when the server is about to start reading DHCPv6 leases
  239. from the lease file. All leases currently held in the memory will be
  240. replaced by those read from the file.
  241. % DHCPSRV_MEMFILE_LEASE_LOAD4 loading lease %1
  242. A debug message issued when DHCPv4 lease is being loaded from the file to
  243. memory.
  244. % DHCPSRV_MEMFILE_LEASE_LOAD6 loading lease %1
  245. A debug message issued when DHCPv6 lease is being loaded from the file to
  246. memory.
  247. % DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to %1 sec
  248. An informational message logged when the Memfile lease database backend
  249. configures the LFC to be executed periodically. The argument holds the
  250. interval in seconds in which the LFC will be executed.
  251. % DHCPSRV_MEMFILE_LFC_START starting Lease File Cleanup
  252. An informational message issued when the Memfile lease database backend
  253. starts the periodic Lease File Cleanup.
  254. % DHCPSRV_MEMFILE_NO_STORAGE running in non-persistent mode, leases will be lost after restart
  255. A warning message issued when writes of leases to disk have been disabled
  256. in the configuration. This mode is useful for some kinds of performance
  257. testing but should not be enabled in normal circumstances. Non-persistence
  258. mode is enabled when 'persist4=no persist6=no' parameters are specified
  259. in the database access string.
  260. % DHCPSRV_MEMFILE_READ_HWADDR_FAIL failed to read hardware address from lease file: %1
  261. A warning message issued when read attempt of the hardware address stored in
  262. a disk file failed. The parameter should provide the exact nature of the failure.
  263. The database read will continue, but that particular lease will no longer
  264. have hardware address associated with it.
  265. % DHCPSRV_MEMFILE_ROLLBACK rolling back memory file database
  266. The code has issued a rollback call. For the memory file database, this is
  267. a no-op.
  268. % DHCPSRV_MEMFILE_UPDATE_ADDR4 updating IPv4 lease for address %1
  269. A debug message issued when the server is attempting to update IPv4
  270. lease from the memory file database for the specified address.
  271. % DHCPSRV_MEMFILE_UPDATE_ADDR6 updating IPv6 lease for address %1
  272. A debug message issued when the server is attempting to update IPv6
  273. lease from the memory file database for the specified address.
  274. % DHCPSRV_MYSQL_ADD_ADDR4 adding IPv4 lease with address %1
  275. A debug message issued when the server is about to add an IPv4 lease
  276. with the specified address to the MySQL backend database.
  277. % DHCPSRV_MYSQL_ADD_ADDR6 adding IPv6 lease with address %1, lease type %2
  278. A debug message issued when the server is about to add an IPv6 lease
  279. with the specified address to the MySQL backend database.
  280. % DHCPSRV_MYSQL_COMMIT committing to MySQL database
  281. The code has issued a commit call. All outstanding transactions will be
  282. committed to the database. Note that depending on the MySQL settings,
  283. the committal may not include a write to disk.
  284. % DHCPSRV_MYSQL_DB opening MySQL lease database: %1
  285. This informational message is logged when a DHCP server (either V4 or
  286. V6) is about to open a MySQL lease database. The parameters of the
  287. connection including database name and username needed to access it
  288. (but not the password if any) are logged.
  289. % DHCPSRV_MYSQL_DELETE_ADDR deleting lease for address %1
  290. A debug message issued when the server is attempting to delete a lease for
  291. the specified address from the MySQL database for the specified address.
  292. % DHCPSRV_MYSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  293. A debug message issued when the server is attempting to obtain an IPv4
  294. lease from the MySQL database for the specified address.
  295. % DHCPSRV_MYSQL_GET_ADDR6 obtaining IPv6 lease for address %1, lease type %2
  296. A debug message issued when the server is attempting to obtain an IPv6
  297. lease from the MySQL database for the specified address.
  298. % DHCPSRV_MYSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  299. A debug message issued when the server is attempting to obtain a set
  300. of IPv4 leases from the MySQL database for a client with the specified
  301. client identification.
  302. % DHCPSRV_MYSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  303. A debug message issued when the server is attempting to obtain a set
  304. of IPv4 leases from the MySQL database for a client with the specified
  305. hardware address.
  306. % DHCPSRV_MYSQL_GET_IAID_DUID obtaining IPv6 leases for IAID %1, DUID %2, lease type %3
  307. A debug message issued when the server is attempting to obtain a set of
  308. IPv6 lease from the MySQL database for a client with the specified IAID
  309. (Identity Association ID) and DUID (DHCP Unique Identifier).
  310. % DHCPSRV_MYSQL_GET_IAID_SUBID_DUID obtaining IPv6 leases for IAID %1, Subnet ID %2, DUID %3, lease type %4
  311. A debug message issued when the server is attempting to obtain an IPv6
  312. lease from the MySQL database for a client with the specified IAID
  313. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  314. % DHCPSRV_MYSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  315. A debug message issued when the server is attempting to obtain an IPv4
  316. lease from the MySQL database for a client with the specified subnet ID
  317. and client ID.
  318. % DHCPSRV_MYSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  319. A debug message issued when the server is attempting to obtain an IPv4
  320. lease from the MySQL database for a client with the specified subnet ID
  321. and hardware address.
  322. % DHCPSRV_MYSQL_GET_VERSION obtaining schema version information
  323. A debug message issued when the server is about to obtain schema version
  324. information from the MySQL database.
  325. % DHCPSRV_MYSQL_ROLLBACK rolling back MySQL database
  326. The code has issued a rollback call. All outstanding transaction will
  327. be rolled back and not committed to the database.
  328. % DHCPSRV_MYSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  329. A debug message issued when the server is attempting to update IPv4
  330. lease from the MySQL database for the specified address.
  331. % DHCPSRV_MYSQL_UPDATE_ADDR6 updating IPv6 lease for address %1, lease type %2
  332. A debug message issued when the server is attempting to update IPv6
  333. lease from the MySQL database for the specified address.
  334. % DHCPSRV_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic
  335. This warning message is issued when the current server configuration specifies
  336. no interfaces that the server should listen on, or when the specified interfaces are not
  337. configured to receive the traffic.
  338. % DHCPSRV_NOTYPE_DB no 'type' keyword to determine database backend: %1
  339. This is an error message, logged when an attempt has been made to access
  340. a database backend, but where no 'type' keyword has been included in
  341. the access string. The access string (less any passwords) is included
  342. in the message.
  343. % DHCPSRV_OPEN_SOCKET_FAIL failed to open socket: %1
  344. A warning message issued when IfaceMgr fails to open and bind a socket.
  345. The reason for the failure is appended as an argument of the log message.
  346. % DHCPSRV_PGSQL_ADD_ADDR4 adding IPv4 lease with address %1
  347. A debug message issued when the server is about to add an IPv4 lease
  348. with the specified address to the PostgreSQL backend database.
  349. % DHCPSRV_PGSQL_ADD_ADDR6 adding IPv6 lease with address %1
  350. A debug message issued when the server is about to add an IPv6 lease
  351. with the specified address to the PostgreSQL backend database.
  352. % DHCPSRV_PGSQL_COMMIT committing to MySQL database
  353. The code has issued a commit call. All outstanding transactions will be
  354. committed to the database. Note that depending on the PostgreSQL settings,
  355. the committal may not include a write to disk.
  356. % DHCPSRV_PGSQL_DB opening PostgreSQL lease database: %1
  357. This informational message is logged when a DHCP server (either V4 or
  358. V6) is about to open a PostgreSQL lease database. The parameters of the
  359. connection including database name and username needed to access it
  360. (but not the password if any) are logged.
  361. % DHCPSRV_PGSQL_DEALLOC_ERROR An error occurred deallocating SQL statements while closing the PostgreSQL lease database: %1
  362. This is an error message issued when a DHCP server (either V4 or V6) experienced
  363. and error freeing database SQL resources as part of closing its connection to
  364. the Postgresql database. The connection is closed as part of normal server
  365. shutdown. This error is most likely a programmatic issue that is highly
  366. unlikely to occur or negatively impact server operation.
  367. % DHCPSRV_PGSQL_DELETE_ADDR deleting lease for address %1
  368. A debug message issued when the server is attempting to delete a lease for
  369. the specified address from the PostgreSQL database for the specified address.
  370. % DHCPSRV_PGSQL_GET_ADDR4 obtaining IPv4 lease for address %1
  371. A debug message issued when the server is attempting to obtain an IPv4
  372. lease from the PostgreSQL database for the specified address.
  373. % DHCPSRV_PGSQL_GET_ADDR6 obtaining IPv6 lease for address %1 (lease type %2)
  374. A debug message issued when the server is attempting to obtain an IPv6
  375. lease from the PostgreSQL database for the specified address.
  376. % DHCPSRV_PGSQL_GET_CLIENTID obtaining IPv4 leases for client ID %1
  377. A debug message issued when the server is attempting to obtain a set
  378. of IPv4 leases from the PostgreSQL database for a client with the specified
  379. client identification.
  380. % DHCPSRV_PGSQL_GET_HWADDR obtaining IPv4 leases for hardware address %1
  381. A debug message issued when the server is attempting to obtain a set
  382. of IPv4 leases from the PostgreSQL database for a client with the specified
  383. hardware address.
  384. % DHCPSRV_PGSQL_GET_IAID_DUID obtaining IPv4 leases for IAID %1 and DUID %2, lease type %3
  385. A debug message issued when the server is attempting to obtain a set of
  386. IPv6 lease from the PostgreSQL database for a client with the specified IAID
  387. (Identity Association ID) and DUID (DHCP Unique Identifier).
  388. % DHCPSRV_PGSQL_GET_IAID_SUBID_DUID obtaining IPv4 leases for IAID %1, Subnet ID %2, DUID %3, and lease type %4
  389. A debug message issued when the server is attempting to obtain an IPv6
  390. lease from the PostgreSQL database for a client with the specified IAID
  391. (Identity Association ID), Subnet ID and DUID (DHCP Unique Identifier).
  392. % DHCPSRV_PGSQL_GET_SUBID_CLIENTID obtaining IPv4 lease for subnet ID %1 and client ID %2
  393. A debug message issued when the server is attempting to obtain an IPv4
  394. lease from the PostgreSQL database for a client with the specified subnet ID
  395. and client ID.
  396. % DHCPSRV_PGSQL_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID %1 and hardware address %2
  397. A debug message issued when the server is attempting to obtain an IPv4
  398. lease from the PostgreSQL database for a client with the specified subnet ID
  399. and hardware address.
  400. % DHCPSRV_PGSQL_GET_VERSION obtaining schema version information
  401. A debug message issued when the server is about to obtain schema version
  402. information from the PostgreSQL database.
  403. % DHCPSRV_PGSQL_ROLLBACK rolling back PostgreSQL database
  404. The code has issued a rollback call. All outstanding transaction will
  405. be rolled back and not committed to the database.
  406. % DHCPSRV_PGSQL_UPDATE_ADDR4 updating IPv4 lease for address %1
  407. A debug message issued when the server is attempting to update IPv4
  408. lease from the PostgreSQL database for the specified address.
  409. % DHCPSRV_PGSQL_UPDATE_ADDR6 updating IPv6 lease for address %1
  410. A debug message issued when the server is attempting to update IPv6
  411. lease from the PostgreSQL database for the specified address.
  412. % DHCPSRV_UNEXPECTED_NAME database access parameters passed through '%1', expected 'lease-database'
  413. The parameters for access the lease database were passed to the server through
  414. the named configuration parameter, but the code was expecting them to be
  415. passed via the parameter named "lease-database". If the database opens
  416. successfully, there is no impact on server operation. However, as this does
  417. indicate an error in the source code, please submit a bug report.
  418. % DHCPSRV_UNKNOWN_DB unknown database type: %1
  419. The database access string specified a database type (given in the
  420. message) that is unknown to the software. This is a configuration error.