dhcp_ddns_messages.mes 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596
  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::dhcp_ddns
  15. % DHCP_DDNS_INVALID_NCR application received an invalid DNS update request: %1
  16. This is an error message that indicates that an invalid request to update
  17. a DNS entry was received by the application. Either the format or the content
  18. of the request is incorrect. The request will be ignored.
  19. % DHCP_DDNS_NCR_FLUSH_IO_ERROR DHCP-DDNS Last send before stopping did not complete successfully: %1
  20. This is an error message that indicates the DHCP-DDNS client was unable to
  21. complete the last send prior to exiting send mode. This is a programmatic
  22. error, highly unlikely to occur, and should not impair the application's ability
  23. to process requests.
  24. % DHCP_DDNS_NCR_LISTEN_CLOSE_ERROR application encountered an error while closing the listener used to receive NameChangeRequests : %1
  25. This is an error message that indicates the application was unable to close the
  26. listener connection used to receive NameChangeRequests. Closure may occur
  27. during the course of error recovery or during normal shutdown procedure. In
  28. either case the error is unlikely to impair the application's ability to
  29. process requests but it should be reported for analysis.
  30. % DHCP_DDNS_NCR_RECV_NEXT_ERROR application could not initiate the next read following a request receive.
  31. This is a error message indicating that NameChangeRequest listener could not
  32. start another read after receiving a request. While possible, this is highly
  33. unlikely and is probably a programmatic error. The application should recover
  34. on its own.
  35. % DHCP_DDNS_NCR_SEND_CLOSE_ERROR DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests: %1
  36. This is an error message that indicates the DHCP-DDNS client was unable to
  37. close the connection used to send NameChangeRequests. Closure may occur during
  38. the course of error recovery or during normal shutdown procedure. In either
  39. case the error is unlikely to impair the client's ability to send requests but
  40. it should be reported for analysis.
  41. % DHCP_DDNS_NCR_SEND_NEXT_ERROR DHCP-DDNS client could not initiate the next request send following send completion: %1
  42. This is a error message indicating that NameChangeRequest sender could not
  43. start another send after completing the send of the previous request. While
  44. possible, this is highly unlikely and is probably a programmatic error. The
  45. application should recover on its own.
  46. % DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UDP watch socket failed to clear: %1
  47. This is an error message that indicates the application was unable to reset the
  48. UDP NCR sender ready status after completing a send. This is programmatic error
  49. that should be reported. The application may or may not continue to operate
  50. correctly.
  51. % DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests
  52. This is a debug message indicating that the listening on a UDP socket
  53. for DNS update requests has been canceled. This is a normal part of
  54. suspending listening operations.
  55. % DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1
  56. This is an error message indicating that an I/O error occurred while listening
  57. over a UDP socket for DNS update requests. This could indicate a network
  58. connectivity or system resource issue.
  59. % DHCP_DDNS_NCR_UDP_SEND_CANCELED UDP socket send was canceled while sending a DNS Update request to DHCP_DDNS: %1
  60. This is an informational message indicating that sending requests via UDP
  61. socket to DHCP_DDNS has been interrupted. This is a normal part of suspending
  62. send operations.
  63. % DHCP_DDNS_NCR_UDP_SEND_ERROR UDP socket send error while sending a DNS Update request: %1
  64. This is an error message indicating that an IO error occurred while sending a
  65. DNS update request to DHCP_DDNS over a UDP socket. This could indicate a
  66. network connectivity or system resource issue.
  67. % DHCP_DDNS_UDP_SENDER_WATCH_SOCKET_CLOSE_ERROR watch socket failed to close: %1
  68. This is an error message that indicates the application was unable to close
  69. the inbound or outbound side of a NCR sender's watch socket. While technically
  70. possible the error is highly unlikely to occur and should not impair the
  71. application's ability to process requests.
  72. % DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR unexpected exception thrown from the application receive completion handler: %1
  73. This is an error message that indicates that an exception was thrown but not
  74. caught in the application's request receive completion handler. This is a
  75. programmatic error that needs to be reported. Dependent upon the nature of
  76. the error the application may or may not continue operating normally.
  77. % DHCP_DDNS_UNCAUGHT_NCR_SEND_HANDLER_ERROR unexpected exception thrown from the DHCP-DDNS client send completion handler: %1
  78. This is an error message that indicates that an exception was thrown but not
  79. caught in the application's send completion handler. This is a programmatic
  80. error that needs to be reported. Dependent upon the nature of the error the
  81. client may or may not continue operating normally.