zonemgr_messages.mes 7.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151
  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. # No namespace declaration - these constants go in the global namespace
  15. # of the zonemgr messages python module.
  16. % ZONEMGR_CCSESSION_ERROR command channel session error: %1
  17. An error was encountered on the command channel. The message indicates
  18. the nature of the error.
  19. % ZONEMGR_JITTER_TOO_BIG refresh_jitter is too big, setting to 0.5
  20. The value specified in the configuration for the refresh jitter is too large
  21. so its value has been set to the maximum of 0.5.
  22. % ZONEMGR_KEYBOARD_INTERRUPT exiting zonemgr process as result of keyboard interrupt
  23. An informational message output when the zone manager was being run at a
  24. terminal and it was terminated via a keyboard interrupt signal.
  25. % ZONEMGR_LOAD_ZONE loading zone %1 (class %2)
  26. This is a debug message indicating that the zone of the specified class
  27. is being loaded.
  28. % ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master
  29. A command received by the zone manager from the Auth module did not
  30. contain the address of the master server from which a NOTIFY message
  31. was received. This may be due to an internal programming error; please
  32. submit a bug report.
  33. % ZONEMGR_NO_SOA zone %1 (class %2) does not have an SOA record
  34. When loading the named zone of the specified class the zone manager
  35. discovered that the data did not contain an SOA record. The load has
  36. been abandoned.
  37. % ZONEMGR_NO_TIMER_THREAD trying to stop zone timer thread but it is not running
  38. An attempt was made to stop the timer thread (used to track when zones
  39. should be refreshed) but it was not running. This may indicate an
  40. internal program error. Please submit a bug report.
  41. % ZONEMGR_NO_ZONE_CLASS internal BIND 10 command did not contain class of zone
  42. A command received by the zone manager from another BIND 10 module did
  43. not contain the class of the zone on which the zone manager should act.
  44. This may be due to an internal programming error; please submit a
  45. bug report.
  46. % ZONEMGR_NO_ZONE_NAME internal BIND 10 command did not contain name of zone
  47. A command received by the zone manager from another BIND 10 module did
  48. not contain the name of the zone on which the zone manager should act.
  49. This may be due to an internal programming error; please submit a
  50. bug report.
  51. % ZONEMGR_RECEIVE_NOTIFY received NOTIFY command for zone %1 (class %2)
  52. This is a debug message indicating that the zone manager has received a
  53. NOTIFY command over the command channel. The command is sent by the Auth
  54. process when it is acting as a slave server for the zone and causes the
  55. zone manager to record the master server for the zone and start a timer;
  56. when the timer expires, the master will be polled to see if it contains
  57. new data.
  58. % ZONEMGR_RECEIVE_SHUTDOWN received SHUTDOWN command
  59. This is a debug message indicating that the zone manager has received
  60. a SHUTDOWN command over the command channel from the Boss process.
  61. It will act on this command and shut down.
  62. % ZONEMGR_RECEIVE_UNKNOWN received unknown command '%1'
  63. This is a warning message indicating that the zone manager has received
  64. the stated command over the command channel. The command is not known
  65. to the zone manager and although the command is ignored, its receipt
  66. may indicate an internal error. Please submit a bug report.
  67. % ZONEMGR_RECEIVE_XFRIN_FAILED received XFRIN FAILED command for zone %1 (class %2)
  68. This is a debug message indicating that the zone manager has received
  69. an XFRIN FAILED command over the command channel. The command is sent
  70. by the Xfrin process when a transfer of zone data into the system has
  71. failed, and causes the zone manager to schedule another transfer attempt.
  72. % ZONEMGR_RECEIVE_XFRIN_SUCCESS received XFRIN SUCCESS command for zone %1 (class %2)
  73. This is a debug message indicating that the zone manager has received
  74. an XFRIN SUCCESS command over the command channel. The command is sent
  75. by the Xfrin process when the transfer of zone data into the system has
  76. succeeded, and causes the data to be loaded and served by BIND 10.
  77. % ZONEMGR_REFRESH_ZONE refreshing zone %1 (class %2)
  78. The zone manager is refreshing the named zone of the specified class
  79. with updated information.
  80. % ZONEMGR_SELECT_ERROR error with select(): %1
  81. An attempt to wait for input from a socket failed. The failing operation
  82. is a call to the operating system's select() function, which failed for
  83. the given reason.
  84. % ZONEMGR_SEND_FAIL failed to send command to %1, session has been closed
  85. The zone manager attempted to send a command to the named BIND 10 module,
  86. but the send failed. The session between the modules has been closed.
  87. % ZONEMGR_SESSION_ERROR unable to establish session to command channel daemon
  88. The zonemgr process was not able to be started because it could not
  89. connect to the command channel daemon. The most usual cause of this
  90. problem is that the daemon is not running.
  91. % ZONEMGR_SESSION_TIMEOUT timeout on session to command channel daemon
  92. The zonemgr process was not able to be started because it timed out when
  93. connecting to the command channel daemon. The most usual cause of this
  94. problem is that the daemon is not running.
  95. % ZONEMGR_SHUTDOWN zone manager has shut down
  96. A debug message, output when the zone manager has shut down completely.
  97. % ZONEMGR_STARTED zonemgr started
  98. This informational message is output by zonemgr when all initialization
  99. has been completed and it is entering its main loop.
  100. % ZONEMGR_STARTING zone manager starting
  101. A debug message output when the zone manager starts up.
  102. % ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running
  103. This message is issued when an attempt is made to start the timer
  104. thread (which keeps track of when zones need a refresh) but one is
  105. already running. It indicates either an error in the program logic or
  106. a problem with stopping a previous instance of the timer. Please submit
  107. a bug report.
  108. % ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager
  109. An XFRIN operation has failed but the zone that was the subject of the
  110. operation is not being managed by the zone manager. This can be either the
  111. result of a bindctl command to transfer in a currently unknown (or mistyped)
  112. zone, or, if this error appears without the administrator giving transfer
  113. commands, it can indicate an error in the program, as it should not have
  114. initiated transfers of unknown zones on its own.
  115. % ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone %1 (class %2) is not known to the zone manager
  116. A NOTIFY was received but the zone that was the subject of the operation
  117. is not being managed by the zone manager. This may indicate an error
  118. in the program (as the operation should not have been initiated if this
  119. were the case). Please submit a bug report.
  120. % ZONEMGR_UNKNOWN_ZONE_SUCCESS zone %1 (class %2) is not known to the zone manager
  121. An XFRIN operation has succeeded but the zone received is not being
  122. managed by the zone manager. This may indicate an error in the program
  123. (as the operation should not have been initiated if this were the case).
  124. Please submit a bug report.