config_messages.mes 5.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. # Copyright (C) 2011, 2014-2015 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::config
  15. % COMMAND_DEREGISTERED Command %1 deregistered
  16. This debug message indicates that the daemon stopped supporting specified
  17. command. This command can no longer be issued. If the command socket is
  18. open and this command is issued, the daemon will not be able to process it.
  19. % COMMAND_PROCESS_ERROR1 Error while processing command: %1
  20. This warning message indicates that the server encountered an error while
  21. processing received command. Additional information will be provided, if
  22. available. Additional log messages may provide more details.
  23. % COMMAND_PROCESS_ERROR2 Error while processing command: %1
  24. This warning message indicates that the server encountered an error while
  25. processing received command. The difference, compared to COMMAND_PROCESS_ERROR1
  26. is that the initial command was well formed and the error occurred during
  27. logic processing, not the command parsing. Additional information will be
  28. provided, if available. Additional log messages may provide more details.
  29. % COMMAND_RECEIVED Received command '%1'
  30. This informational message indicates that a command was received over command
  31. socket. The nature of this command and its possible results will be logged
  32. with separate messages.
  33. % COMMAND_REGISTERED Command %1 registered
  34. This debug message indicates that the daemon started supporting specified
  35. command. If the command socket is open, this command can now be issued.
  36. % COMMAND_RESPONSE_ERROR Server failed to generate response for command: %1
  37. This error message indicates that the server failed to generate response for
  38. specified command. This likely indicates a server logic error, as the server
  39. is expected to generate valid responses for all commands, even malformed
  40. ones.
  41. % COMMAND_SOCKET_ACCEPT_FAIL Failed to accept incoming connection on command socket %1: %2
  42. This error indicates that the server detected incoming connection and executed
  43. accept system call on said socket, but this call returned an error. Additional
  44. information may be provided by the system as second parameter.
  45. % COMMAND_SOCKET_CONNECTION_CLOSED Closed socket %1 for existing command connection
  46. This is an informational message that the socket created for handling
  47. client's connection is closed. This usually means that the client disconnected,
  48. but may also mean a timeout.
  49. % COMMAND_SOCKET_CONNECTION_OPENED Opened socket %1 for incoming command connection on socket %2
  50. This is an informational message that a new incoming command connection was
  51. detected and a dedicated socket was opened for that connection.
  52. % COMMAND_SOCKET_FAIL_NONBLOCK Failed to set non-blocking mode for socket %1 created for incoming connection on socket %2: %3
  53. This error message indicates that the server failed to set non-blocking mode
  54. on just created socket. That socket was created for accepting specific
  55. incoming connection. Additional information may be provided as third parameter.
  56. % COMMAND_SOCKET_READ Received %1 bytes over command socket %2
  57. This debug message indicates that specified number of bytes was received
  58. over command socket identified by specified file descriptor.
  59. % COMMAND_SOCKET_READ_FAIL Encountered error %1 while reading from command socket %2
  60. This error message indicates that an error was encountered while
  61. reading from command socket.
  62. % COMMAND_SOCKET_RESPONSE_TOOLARGE Server's response was larger (%1) than supported 64KB
  63. This error message indicates that the server received a command and generated
  64. an answer for it, but that response was larger than supported 64KB. Server
  65. will attempt to send the first 64KB of the response. Depending on the nature
  66. of this response, this may indicate a software or configuration error. Future
  67. Kea versions are expected to have better support for large responses.
  68. % COMMAND_SOCKET_UNIX_CLOSE Command socket closed: UNIX, fd=%1, path=%2
  69. This informational message indicates that the daemon closed a command
  70. processing socket. This was a UNIX socket. It was opened with the file
  71. descriptor and path specified.
  72. % COMMAND_SOCKET_UNIX_OPEN Command socket opened: UNIX, fd=%1, path=%2
  73. This informational message indicates that the daemon opened a command
  74. processing socket. This is a UNIX socket. It was opened with the file
  75. descriptor and path specified.
  76. % COMMAND_SOCKET_WRITE Sent response of %1 bytes over command socket %2
  77. This debug message indicates that the specified number of bytes was sent
  78. over command socket identifier by the specified file descriptor.
  79. % COMMAND_SOCKET_WRITE_FAIL Error while writing %1 bytes to command socket %2
  80. This error message indicates that an error was encountered while
  81. attempting to send a response to the command socket.