config_messages.mes 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. # Copyright (C) 2011-2017 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # This Source Code Form is subject to the terms of the Mozilla Public
  4. # License, v. 2.0. If a copy of the MPL was not distributed with this
  5. # file, You can obtain one at http://mozilla.org/MPL/2.0/.
  6. $NAMESPACE isc::config
  7. % COMMAND_DEREGISTERED Command %1 deregistered
  8. This debug message indicates that the daemon stopped supporting specified
  9. command. This command can no longer be issued. If the command socket is
  10. open and this command is issued, the daemon will not be able to process it.
  11. % COMMAND_EXTENDED_REGISTERED Command %1 registered
  12. This debug message indicates that the daemon started supporting specified
  13. command. The handler for the registered command includes a parameter holding
  14. entire command to be processed.
  15. % COMMAND_HOOK_RECEIVE_SKIP command %1 has been handled by the hook library which returned the skip state
  16. This debug message is issued when a hook library has processed the control
  17. command and returned the skip status. The callout should have set the
  18. 'response' argument which contains the result of processing the command.
  19. The Command Manager skips processing of this command and simply returns
  20. the response generated by the hook library.
  21. % COMMAND_PROCESS_ERROR1 Error while processing command: %1
  22. This warning message indicates that the server encountered an error while
  23. processing received command. Additional information will be provided, if
  24. available. Additional log messages may provide more details.
  25. % COMMAND_PROCESS_ERROR2 Error while processing command: %1
  26. This warning message indicates that the server encountered an error while
  27. processing received command. The difference, compared to COMMAND_PROCESS_ERROR1
  28. is that the initial command was well formed and the error occurred during
  29. logic processing, not the command parsing. Additional information will be
  30. provided, if available. Additional log messages may provide more details.
  31. % COMMAND_RECEIVED Received command '%1'
  32. This informational message indicates that a command was received over command
  33. socket. The nature of this command and its possible results will be logged
  34. with separate messages.
  35. % COMMAND_REGISTERED Command %1 registered
  36. This debug message indicates that the daemon started supporting specified
  37. command. If the command socket is open, this command can now be issued.
  38. % COMMAND_RESPONSE_ERROR Server failed to generate response for command: %1
  39. This error message indicates that the server failed to generate response for
  40. specified command. This likely indicates a server logic error, as the server
  41. is expected to generate valid responses for all commands, even malformed
  42. ones.
  43. % COMMAND_SOCKET_ACCEPT_FAIL Failed to accept incoming connection on command socket %1: %2
  44. This error indicates that the server detected incoming connection and executed
  45. accept system call on said socket, but this call returned an error. Additional
  46. information may be provided by the system as second parameter.
  47. % COMMAND_SOCKET_CLOSED_BY_FOREIGN_HOST Closed command socket %1 by foreign host
  48. This is an information message indicating that the command connection has been
  49. closed by a command control client.
  50. % COMMAND_SOCKET_CONNECTION_CLOSED Closed socket %1 for existing command connection
  51. This is an informational message that the socket created for handling
  52. client's connection is closed. This usually means that the client disconnected,
  53. but may also mean a timeout.
  54. % COMMAND_SOCKET_CONNECTION_CLOSE_FAIL Failed to close command connection: %1
  55. This error message is issued when an error occurred when closing a
  56. command connection and/or removing it from the connections pool. The
  57. detailed error is provided as an argument.
  58. % COMMAND_SOCKET_CONNECTION_OPENED Opened socket %1 for incoming command connection
  59. This is an informational message that a new incoming command connection was
  60. detected and a dedicated socket was opened for that connection.
  61. % COMMAND_SOCKET_CONNECTION_SHUTDOWN_FAIL Encountered error %1 while trying to gracefully shutdown socket
  62. This message indicates an error while trying to gracefully shutdown command
  63. connection. The type of the error is included in the message.
  64. % COMMAND_SOCKET_CONNECTION_TIMEOUT Timeout occurred for connection over socket %1
  65. This is an informational message that indicates that the timeout has
  66. occurred for one of the command channel connections. The response
  67. sent by the server indicates a timeout and is then closed.
  68. % COMMAND_SOCKET_READ Received %1 bytes over command socket %2
  69. This debug message indicates that specified number of bytes was received
  70. over command socket identified by specified file descriptor.
  71. % COMMAND_SOCKET_READ_FAIL Encountered error %1 while reading from command socket %2
  72. This error message indicates that an error was encountered while
  73. reading from command socket.
  74. % COMMAND_SOCKET_WRITE Sent response of %1 bytes over command socket %2
  75. This debug message indicates that the specified number of bytes was sent
  76. over command socket identifier by the specified file descriptor.
  77. % COMMAND_SOCKET_WRITE_FAIL Error while writing to command socket %1 : %2
  78. This error message indicates that an error was encountered while
  79. attempting to send a response to the command socket.