hooks_messages.mes 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189
  1. # Copyright (C) 2013-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::hooks
  15. % HOOKS_ALL_CALLOUTS_DEREGISTERED hook library at index %1 removed all callouts on hook %2
  16. A debug message issued when all callouts on the specified hook registered
  17. by the library with the given index were removed. This is similar to
  18. the HOOKS_CALLOUTS_REMOVED message (and the two are likely to be seen
  19. together), but is issued at a lower-level in the hook framework.
  20. % HOOKS_CALLOUTS_BEGIN begin all callouts for hook %1
  21. This debug message is issued when callout manager begins to invoke callouts
  22. for the hook. The argument specifies the hook name.
  23. % HOOKS_CALLOUTS_COMPLETE completed callouts for hook %1 (total callouts duration: %2)
  24. This debug message is issued when callout manager has completed execution
  25. of all callouts for the particular hook. The arguments specify the hook
  26. name and total execution time for all callouts in milliseconds.
  27. % HOOKS_CALLOUTS_REMOVED callouts removed from hook %1 for library %2
  28. This is a debug message issued during library unloading. It notes that
  29. one of more callouts registered by that library have been removed from
  30. the specified hook. This is similar to the HOOKS_DEREGISTER_ALL_CALLOUTS
  31. message (and the two are likely to be seen together), but is issued at a
  32. higher-level in the hook framework.
  33. % HOOKS_CALLOUT_CALLED hooks library with index %1 has called a callout on hook %2 that has address %3 (callout duration: %4)
  34. Only output at a high debugging level, this message indicates that
  35. a callout on the named hook registered by the library with the given
  36. index (in the list of loaded libraries) has been called and returned a
  37. success state. The address of the callout is given in the message.
  38. The message includes the callout execution time in milliseconds.
  39. % HOOKS_CALLOUT_DEREGISTERED hook library at index %1 deregistered a callout on hook %2
  40. A debug message issued when all instances of a particular callouts on
  41. the hook identified in the message that were registered by the library
  42. with the given index have been removed.
  43. % HOOKS_CALLOUT_ERROR error returned by callout on hook %1 registered by library with index %2 (callout address %3) (callout duration %4)
  44. If a callout returns an error status when called, this error message
  45. is issued. It identifies the hook to which the callout is attached, the
  46. index of the library (in the list of loaded libraries) that registered
  47. it and the address of the callout. The error is otherwise ignored.
  48. The error message includes the callout execution time in milliseconds.
  49. % HOOKS_CALLOUT_EXCEPTION exception thrown by callout on hook %1 registered by library with index %2 (callout address %3): %4 (callout duration: $5)
  50. If a callout throws an exception when called, this error message is
  51. issued. It identifies the hook to which the callout is attached, the
  52. index of the library (in the list of loaded libraries) that registered
  53. it and the address of the callout. The error is otherwise ignored.
  54. The error message includes the callout execution time in milliseconds.
  55. % HOOKS_CALLOUT_REGISTRATION hooks library with index %1 registering callout for hook '%2'
  56. This is a debug message, output when a library (whose index in the list
  57. of libraries (being) loaded is given) registers a callout.
  58. % HOOKS_CLOSE_ERROR failed to close hook library %1: %2
  59. Kea has failed to close the named hook library for the stated reason.
  60. Although this is an error, this should not affect the running system
  61. other than as a loss of resources. If this error persists, you should
  62. restart Kea.
  63. % HOOKS_HOOK_LIST_RESET the list of hooks has been reset
  64. This is a message indicating that the list of hooks has been reset.
  65. While this is usual when running the Kea test suite, it should not be
  66. seen when running Kea in a production environment. If this appears,
  67. please report a bug through the usual channels.
  68. % HOOKS_INCORRECT_VERSION hook library %1 is at version %2, require version %3
  69. Kea has detected that the named hook library has been built against
  70. a version of Kea that is incompatible with the version of Kea
  71. running on your system. It has not loaded the library.
  72. This is most likely due to the installation of a new version of Kea
  73. without rebuilding the hook library. A rebuild and re-install of the
  74. library should fix the problem in most cases.
  75. % HOOKS_LIBRARY_LOADED hooks library %1 successfully loaded
  76. This information message is issued when a user-supplied hooks library
  77. has been successfully loaded.
  78. % HOOKS_LIBRARY_LOADING loading hooks library %1
  79. This is a debug message output just before the specified library is loaded.
  80. If the action is successfully, it will be followed by the
  81. HOOKS_LIBRARY_LOADED informational message.
  82. % HOOKS_LIBRARY_UNLOADED hooks library %1 successfully unloaded
  83. This information message is issued when a user-supplied hooks library
  84. has been successfully unloaded.
  85. % HOOKS_LIBRARY_UNLOADING unloading library %1
  86. This is a debug message called when the specified library is
  87. being unloaded. If all is successful, it will be followed by the
  88. HOOKS_LIBRARY_UNLOADED informational message.
  89. % HOOKS_LIBRARY_VERSION hooks library %1 reports its version as %2
  90. A debug message issued when the version check on the hooks library
  91. has succeeded.
  92. % HOOKS_LOAD_ERROR 'load' function in hook library %1 returned error %2
  93. A "load" function was found in the library named in the message and
  94. was called. The function returned a non-zero status (also given in
  95. the message) which was interpreted as an error. The library has been
  96. unloaded and no callouts from it will be installed.
  97. % HOOKS_LOAD_EXCEPTION 'load' function in hook library %1 threw an exception
  98. A "load" function was found in the library named in the message and
  99. was called. The function threw an exception (an error indication)
  100. during execution, which is an error condition. The library has been
  101. unloaded and no callouts from it will be installed.
  102. % HOOKS_LOAD_FRAMEWORK_EXCEPTION 'load' function in hook library %1 threw an exception: reason %2
  103. A "load" function was found in the library named in the message and
  104. was called. Either the hooks framework or the function threw an
  105. exception (an error indication) during execution, which is an error
  106. condition; the cause of the exception is recorded in the message.
  107. The library has been unloaded and no callouts from it will be
  108. installed.
  109. % HOOKS_LOAD_SUCCESS 'load' function in hook library %1 returned success
  110. This is a debug message issued when the "load" function has been found
  111. in a hook library and has been successfully called.
  112. % HOOKS_NO_LOAD no 'load' function found in hook library %1
  113. This is a debug message saying that the specified library was loaded
  114. but no function called "load" was found in it. Providing the library
  115. contained some "standard" functions (i.e. functions with the names of
  116. the hooks for the given server), this is not an issue.
  117. % HOOKS_NO_UNLOAD no 'unload' function found in hook library %1
  118. This is a debug message issued when the library is being unloaded.
  119. It merely states that the library did not contain an "unload" function.
  120. % HOOKS_NO_VERSION no 'version' function found in hook library %1
  121. The shared library named in the message was found and successfully loaded,
  122. but Kea did not find a function named "version" in it. This function
  123. is required and should return the version of Kea against which the
  124. library was built. The value is used to check that the library was built
  125. against a compatible version of Kea. The library has not been loaded.
  126. % HOOKS_OPEN_ERROR failed to open hook library %1: %2
  127. Kea failed to open the specified hook library for the stated
  128. reason. The library has not been loaded. Kea will continue to
  129. function, but without the services offered by the library.
  130. % HOOKS_STD_CALLOUT_REGISTERED hooks library %1 registered standard callout for hook %2 at address %3
  131. This is a debug message, output when the library loading function has
  132. located a standard callout (a callout with the same name as a hook point)
  133. and registered it. The address of the callout is indicated.
  134. % HOOKS_UNLOAD_ERROR 'unload' function in hook library %1 returned error %2
  135. During the unloading of a library, an "unload" function was found.
  136. It was called, but returned an error (non-zero) status, resulting in
  137. the issuing of this message. The unload process continued after this
  138. message and the library has been unloaded.
  139. % HOOKS_UNLOAD_EXCEPTION 'unload' function in hook library %1 threw an exception
  140. During the unloading of a library, an "unload" function was found. It was
  141. called, but in the process generated an exception (an error indication).
  142. The unload process continued after this message and the library has
  143. been unloaded.
  144. % HOOKS_UNLOAD_FRAMEWORK_EXCEPTION 'unload' function in hook library %1 threw an exception, reason %2
  145. During the unloading of a library, an "unload" function was found.
  146. It was called, but in the process either it or the hooks framework
  147. generated an exception (an error indication); the cause of the error
  148. is recorded in the message. The unload process continued after
  149. this message and the library has been unloaded.
  150. % HOOKS_UNLOAD_SUCCESS 'unload' function in hook library %1 returned success
  151. This is a debug message issued when an "unload" function has been found
  152. in a hook library during the unload process, called, and returned success.
  153. % HOOKS_VERSION_EXCEPTION 'version' function in hook library %1 threw an exception
  154. This error message is issued if the version() function in the specified
  155. hooks library was called and generated an exception. The library is
  156. considered unusable and will not be loaded.