auth_messages.mes 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262
  1. # Copyright (C) 2011 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::auth
  15. % AUTH_AXFR_ERROR error handling AXFR request: %1
  16. This is a debug message produced by the authoritative server when it
  17. has encountered an error processing an AXFR request. The message gives
  18. the reason for the error, and the server will return a SERVFAIL code to
  19. the sender.
  20. % AUTH_AXFR_UDP AXFR query received over UDP
  21. This is a debug message output when the authoritative server has received
  22. an AXFR query over UDP. Use of UDP for AXFRs is not permitted by the
  23. protocol, so the server will return a FORMERR error to the sender.
  24. % AUTH_COMMAND_FAILED execution of command channel instruction '%1' failed: %2
  25. Execution of the specified command by the authoritative server failed. The
  26. message contains the reason for the failure.
  27. % AUTH_CONFIG_CHANNEL_CREATED configuration session channel created
  28. This is a debug message indicating that authoritative server has created
  29. the channel to the configuration manager. It is issued during server
  30. startup is an indication that the initialization is proceeding normally.
  31. % AUTH_CONFIG_CHANNEL_ESTABLISHED configuration session channel established
  32. This is a debug message indicating that authoritative server
  33. has established communication the configuration manager over the
  34. previously-created channel. It is issued during server startup is an
  35. indication that the initialization is proceeding normally.
  36. % AUTH_CONFIG_CHANNEL_STARTED configuration session channel started
  37. This is a debug message, issued when the authoritative server has
  38. posted a request to be notified when new configuration information is
  39. available. It is issued during server startup is an indication that
  40. the initialization is proceeding normally.
  41. % AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1
  42. An attempt to configure the server with information from the configuration
  43. database during the startup sequence has failed. (The reason for
  44. the failure is given in the message.) The server will continue its
  45. initialization although it may not be configured in the desired way.
  46. % AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1
  47. At attempt to update the configuration the server with information
  48. from the configuration database has failed, the reason being given in
  49. the message.
  50. % AUTH_DATA_SOURCE data source database file: %1
  51. This is a debug message produced by the authoritative server when it accesses a
  52. datebase data source, listing the file that is being accessed.
  53. % AUTH_DNS_SERVICES_CREATED DNS services created
  54. This is a debug message indicating that the component that will handling
  55. incoming queries for the authoritative server (DNSServices) has been
  56. successfully created. It is issued during server startup is an indication
  57. that the initialization is proceeding normally.
  58. % AUTH_HEADER_PARSE_FAIL unable to parse header in received DNS packet: %1
  59. This is a debug message, generated by the authoritative server when an
  60. attempt to parse the header of a received DNS packet has failed. (The
  61. reason for the failure is given in the message.) The server will drop the
  62. packet.
  63. % AUTH_LOAD_TSIG loading TSIG keys
  64. This is a debug message indicating that the authoritative server
  65. has requested the keyring holding TSIG keys from the configuration
  66. database. It is issued during server startup is an indication that the
  67. initialization is proceeding normally.
  68. % AUTH_LOAD_ZONE loaded zone %1/%2
  69. This debug message is issued during the processing of the 'loadzone' command
  70. when the authoritative server has successfully loaded the named zone of the
  71. named class.
  72. % AUTH_MEM_DATASRC_DISABLED memory data source is disabled for class %1
  73. This is a debug message reporting that the authoritative server has
  74. discovered that the memory data source is disabled for the given class.
  75. % AUTH_MEM_DATASRC_ENABLED memory data source is enabled for class %1
  76. This is a debug message reporting that the authoritative server has
  77. discovered that the memory data source is enabled for the given class.
  78. % AUTH_NO_STATS_SESSION session interface for statistics is not available
  79. The authoritative server had no session with the statistics module at the
  80. time it attempted to send it data: the attempt has been abandoned. This
  81. could be an error in configuration.
  82. % AUTH_NO_XFRIN received NOTIFY but XFRIN session is not running
  83. This is a debug message produced by the authoritative server when it receives
  84. a NOTIFY packet but the XFRIN process is not running. The packet will be
  85. dropped and nothing returned to the sender.
  86. % AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY
  87. This debug message is logged by the authoritative server when it receives
  88. a NOTIFY packet that an RR type of something other than SOA in the
  89. question section. (The RR type received is included in the message.) The
  90. server will return a FORMERR error to the sender.
  91. % AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY
  92. This debug message is logged by the authoritative server when it receives
  93. a NOTIFY packet that contains zero or more than one question. (A valid
  94. NOTIFY packet contains one question.) The server will return a FORMERR
  95. error to the sender.
  96. % AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1
  97. This is a debug message, generated by the authoritative server when an
  98. attempt to parse a received DNS packet has failed due to something other
  99. than a protocol error. The reason for the failure is given in the message;
  100. the server will return a SERVFAIL error code to the sender.
  101. % AUTH_PACKET_PROTOCOL_ERROR DNS packet protocol error: %1. Returning %2
  102. This is a debug message, generated by the authoritative server when an
  103. attempt to parse a received DNS packet has failed due to a protocol error.
  104. The reason for the failure is given in the message, as is the error code
  105. that will be returned to the sender.
  106. % AUTH_PACKET_RECEIVED message received:\n%1
  107. This is a debug message output by the authoritative server when it
  108. receives a valid DNS packet.
  109. Note: This message includes the packet received, rendered in the form of
  110. multiple lines of text. For this reason, it is suggested that this log message
  111. not be routed to the syslog file, where the multiple lines could confuse
  112. programs that expect a format of one message per line.
  113. % AUTH_PROCESS_FAIL message processing failure: %1
  114. This message is generated by the authoritative server when it has
  115. encountered an internal error whilst processing a received packet:
  116. the cause of the error is included in the message.
  117. The server will return a SERVFAIL error code to the sender of the packet.
  118. This message indicates a potential error in the server. Please open a
  119. bug ticket for this issue.
  120. % AUTH_RECEIVED_COMMAND command '%1' received
  121. This is a debug message issued when the authoritative server has received
  122. a command on the command channel.
  123. % AUTH_RECEIVED_SENDSTATS command 'sendstats' received
  124. This is a debug message issued when the authoritative server has received
  125. a command from the statistics module to send it data. The 'sendstats'
  126. command is handled differently to other commands, which is why the debug
  127. message associated with it has its own code.
  128. % AUTH_RESPONSE_RECEIVED received response message, ignoring
  129. This is a debug message, this is output if the authoritative server
  130. receives a DNS packet with the QR bit set, i.e. a DNS response. The
  131. server ignores the packet as it only responds to question packets.
  132. % AUTH_SEND_ERROR_RESPONSE sending an error response (%1 bytes):\n%2
  133. This is a debug message recording that the authoritative server is sending
  134. an error response to the originator of the query. A previous message will
  135. have recorded details of the failure.
  136. Note: This message includes the packet sent, rendered in the form of
  137. multiple lines of text. For this reason, it is suggested that this log message
  138. not be routed to the syslog file, where the multiple lines could confuse
  139. programs that expect a format of one message per line.
  140. % AUTH_SEND_NORMAL_RESPONSE sending an error response (%1 bytes):\n%2
  141. This is a debug message recording that the authoritative server is sending
  142. a response to the originator of a query.
  143. Note: This message includes the packet sent, rendered in the form of
  144. multiple lines of text. For this reason, it is suggested that this log message
  145. not be routed to the syslog file, where the multiple lines could confuse
  146. programs that expect a format of one message per line.
  147. % AUTH_SERVER_CREATED server created
  148. An informational message indicating that the authoritative server process has
  149. been created and is initializing. The AUTH_SERVER_STARTED message will be
  150. output when initialization has successfully completed and the server starts
  151. accepting queries.
  152. % AUTH_SERVER_FAILED server failed: %1
  153. The authoritative server has encountered a fatal error and is terminating. The
  154. reason for the failure is included in the message.
  155. % AUTH_SERVER_STARTED server started
  156. Initialization of the authoritative server has completed successfully
  157. and it is entering the main loop, waiting for queries to arrive.
  158. % AUTH_SQLITE3 nothing to do for loading sqlite3
  159. This is a debug message indicating that the authoritative server has
  160. found that the data source it is loading is an SQLite3 data source,
  161. so no further validation is needed.
  162. % AUTH_STATS_CHANNEL_CREATED STATS session channel created
  163. This is a debug message indicating that the authoritative server has
  164. created a channel to the statistics process. It is issued during server
  165. startup is an indication that the initialization is proceeding normally.
  166. % AUTH_STATS_CHANNEL_ESTABLISHED STATS session channel established
  167. This is a debug message indicating that the authoritative server
  168. has established communication over the previously created statistics
  169. channel. It is issued during server startup is an indication that the
  170. initialization is proceeding normally.
  171. % AUTH_STATS_COMMS communication error in sending statistics data: %1
  172. An error was encountered when the authoritative server tried to send data
  173. to the statistics daemon. The message includes additional information
  174. describing the reason for the failure.
  175. % AUTH_STATS_TIMEOUT timeout while sending statistics data: %1
  176. The authoritative server sent data to the statistics daemon but received
  177. no acknowledgement within the specified time. The message includes
  178. additional information describing the reason for the failure.
  179. % AUTH_STATS_TIMER_DISABLED statistics timer has been disabled
  180. This is a debug message indicating that the statistics timer has been
  181. disabled in the authoritative server and no statistics information is
  182. being produced.
  183. % AUTH_STATS_TIMER_SET statistics timer set to %1 second(s)
  184. This is a debug message indicating that the statistics timer has been
  185. enabled and that the authoritative server will produce statistics data
  186. at the specified interval.
  187. % AUTH_UNSUPPORTED_OPCODE unsupported opcode: %1
  188. This is a debug message, produced when a received DNS packet being
  189. processed by the authoritative server has been found to contain an
  190. unsupported opcode. (The opcode is included in the message.) The server
  191. will return an error code of NOTIMPL to the sender.
  192. % AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created
  193. This is a debug message indicating that the authoritative server has
  194. created a channel to the XFRIN (Transfer-in) process. It is issued
  195. during server startup is an indication that the initialization is
  196. proceeding normally.
  197. % AUTH_XFRIN_CHANNEL_ESTABLISHED XFRIN session channel established
  198. This is a debug message indicating that the authoritative server has
  199. established communication over the previously-created channel to the
  200. XFRIN (Transfer-in) process. It is issued during server startup is an
  201. indication that the initialization is proceeding normally.
  202. % AUTH_ZONEMGR_COMMS error communicating with zone manager: %1
  203. This is a debug message output during the processing of a NOTIFY request.
  204. An error (listed in the message) has been encountered whilst communicating
  205. with the zone manager. The NOTIFY request will not be honored.
  206. % AUTH_ZONEMGR_ERROR received error response from zone manager: %1
  207. This is a debug message output during the processing of a NOTIFY
  208. request. The zone manager component has been informed of the request,
  209. but has returned an error response (which is included in the message). The
  210. NOTIFY request will not be honored.
  211. % AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified
  212. An error was encountered when the authoritiative server specified
  213. statistics data which is invalid for the auth specification file.