server_common_messages.mes 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859
  1. # Copyright (C) 2012 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 config_messages python module.
  16. # since these messages are for the python server_common library, care must
  17. # be taken that names do not conflict with the messages from the c++
  18. # server_common library. A checker script should verify that, but we do not
  19. # have that at this moment. So when adding a message, make sure that
  20. # the name is not already used in src/lib/config/config_messages.mes
  21. % PYSERVER_COMMON_DNS_TCP_SEND_DONE completed sending TCP message to %1 (%2 bytes in total)
  22. Debug message. A complete DNS message has been successfully
  23. transmitted over a TCP connection, possibly after multiple send
  24. operations. The destination address and the total size of the message
  25. (including the 2-byte length field) are shown in the log message.
  26. % PYSERVER_COMMON_DNS_TCP_SEND_ERROR failed to send TCP message to %1 (%2/%3 bytes sent): %4
  27. A DNS message has been attempted to be sent out over a TCP connection,
  28. but it failed due to some network error. Although it's not expected
  29. to happen too often, it can still happen for various reasons. The
  30. administrator may want to examine the cause of the failure, which is
  31. included in the log message, to see if it requires some action to
  32. be taken at the server side. When this message is logged, the
  33. corresponding TCP connection was closed immediately after the error
  34. was detected.
  35. % PYSERVER_COMMON_DNS_TCP_SEND_PENDING sent part TCP message to %1 (up to %2/%3 bytes)
  36. Debug message. A part of DNS message has been transmitted over a TCP
  37. connection, and it's suspended because further attempt would block.
  38. The destination address and the total size of the message that has
  39. been transmitted so far (including the 2-byte length field) are shown
  40. in the log message.
  41. % PYSERVER_COMMON_TSIG_KEYRING_DEINIT Deinitializing global TSIG keyring
  42. A debug message noting that the global TSIG keyring is being removed from
  43. memory. Most programs don't do that, they just exit, which is OK.
  44. % PYSERVER_COMMON_TSIG_KEYRING_INIT Initializing global TSIG keyring
  45. A debug message noting the TSIG keyring storage is being prepared. It should
  46. appear at most once in the lifetime of a program. The keyring still needs
  47. to be loaded from configuration.
  48. % PYSERVER_COMMON_TSIG_KEYRING_UPDATE Updating global TSIG keyring
  49. A debug message. The TSIG keyring is being (re)loaded from configuration.
  50. This happens at startup or when the configuration changes. The old keyring
  51. is removed and new one created with all the keys.