dhcp_ddns_messages.mes 5.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  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_LISTEN_CLOSE_ERROR application encountered an error while closing the listener used to receive NameChangeRequests : %1
  20. This is an error message that indicates the application was unable to close the
  21. listener connection used to receive NameChangeRequests. Closure may occur
  22. during the course of error recovery or during normal shutdown procedure. In
  23. either case the error is unlikely to impair the application's ability to
  24. process requests but it should be reported for analysis.
  25. % DHCP_DDNS_NCR_RECV_NEXT_ERROR application could not initiate the next read following a request receive.
  26. This is a error message indicating that NameChangeRequest listener could not
  27. start another read after receiving a request. While possible, this is highly
  28. unlikely and is probably a programmatic error. The application should recover
  29. on its own.
  30. % DHCP_DDNS_NCR_SEND_CLOSE_ERROR DHCP-DDNS client encountered an error while closing the sender connection used to send NameChangeRequests : %1
  31. This is an error message that indicates the DHCP-DDNS client was unable to
  32. close the connection used to send NameChangeRequests. Closure may occur during
  33. the course of error recovery or during normal shutdown procedure. In either
  34. case the error is unlikely to impair the client's ability to send requests but
  35. it should be reported for analysis.
  36. % DHCP_DDNS_NCR_SEND_NEXT_ERROR DHCP-DDNS client could not initiate the next request send following send completion.
  37. This is a error message indicating that NameChangeRequest sender could not
  38. start another send after completing the send of the previous request. While
  39. possible, this is highly unlikely and is probably a programmatic error. The
  40. application should recover on its own.
  41. % DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests: %1
  42. This is an informational message indicating that the listening over a UDP socket for DNS update requests has been canceled. This is a normal part of suspending listening operations.
  43. % DHCP_DDNS_NCR_UDP_RECV_ERROR UDP socket receive error while listening for DNS Update requests: %1
  44. This is an error message indicating that an IO error occurred while listening
  45. over a UDP socket for DNS update requests. This could indicate a network
  46. connectivity or system resource issue.
  47. % DHCP_DDNS_NCR_UDP_SEND_CANCELED UDP socket send was canceled while sending a DNS Update request to DHCP_DDNS: %1
  48. This is an informational message indicating that sending requests via UDP
  49. socket to DHCP_DDNS has been interrupted. This is a normal part of suspending
  50. send operations.
  51. % DHCP_DDNS_NCR_UDP_SEND_ERROR UDP socket send error while sending a DNS Update request: %1
  52. This is an error message indicating that an IO error occurred while sending a
  53. DNS update request to DHCP_DDNS over a UDP socket. This could indicate a
  54. network connectivity or system resource issue.
  55. % DHCP_DDNS_UNCAUGHT_NCR_RECV_HANDLER_ERROR unexpected exception thrown from the application receive completion handler: %1
  56. This is an error message that indicates that an exception was thrown but not
  57. caught in the application's request receive completion handler. This is a
  58. programmatic error that needs to be reported. Dependent upon the nature of
  59. the error the application may or may not continue operating normally.
  60. % DHCP_DDNS_UNCAUGHT_NCR_SEND_HANDLER_ERROR unexpected exception thrown from the DHCP-DDNS client send completion handler: %1
  61. This is an error message that indicates that an exception was thrown but not
  62. caught in the application's send completion handler. This is a programmatic
  63. error that needs to be reported. Dependent upon the nature of the error the
  64. client may or may not continue operating normally.
  65. % DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1
  66. This is an error message that indicates the application was unable to close
  67. the outbound side of a NCR sender's watch socket. While technically possible
  68. this error is highly unlikely to occur and should not impair the application's
  69. ability to process requests.
  70. % DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1
  71. This is an error message that indicates the application was unable to close
  72. the inbound side of a NCR sender's watch socket. While technically possible
  73. this error is highly unlikely to occur and should not impair the application's
  74. ability to process requests.