d2_messages.mes 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108
  1. # Copyright (C) 2013 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::d2
  15. % D2CTL_STARTING DHCP-DDNS controller starting, pid: %1
  16. This is an informational message issued when controller for DHCP-DDNS
  17. service first starts.
  18. % D2CTL_STOPPING DHCP-DDNS controller is exiting
  19. This is an informational message issued when the controller is exiting
  20. following a shut down (normal or otherwise) of the DDHCP-DDNS process.
  21. % D2PRC_SHUTDOWN DHCP-DDNS process is performing a normal shut down
  22. This is a debug message issued when the service process has been instructed
  23. to shut down by the controller.
  24. % D2PRC_PROCESS_INIT DHCP-DDNS application init invoked
  25. This is a debug message issued when the D2 process enters its
  26. init method.
  27. % D2PRC_RUN_ENTER process has entered the event loop
  28. This is a debug message issued when the D2 process enters its
  29. run method.
  30. % D2PRC_RUN_EXIT process is exiting the event loop
  31. This is a debug message issued when the D2 process exits the
  32. in event loop.
  33. % D2PRC_FAILED process experienced a fatal error: %1
  34. This is a debug message issued when the D2 process encounters an
  35. unrecoverable error from within the event loop.
  36. % D2PRC_CONFIGURE new configuration received: %1
  37. This is a debug message issued when the D2 process configure method
  38. has been invoked.
  39. % D2PRC_COMMAND command directive received, command: %1 - args: %2
  40. This is a debug message issued when the D2 process command method
  41. has been invoked.
  42. % D2CTL_INIT_PROCESS initializing application proces
  43. This debug message is issued just before the controller attempts
  44. to create and initialize its process instance.
  45. % D2CTL_SESSION_FAIL failed to establish BIND 10 session: %1
  46. The controller has failed to establish communication with the rest of BIND
  47. 10 and will exit.
  48. % D2CTL_DISCONNECT_FAIL failed to disconnect from BIND 10 session: %1
  49. This message indicates that while shutting down, the DHCP-DDNS controller
  50. encountered an error terminating communication with the BIND10. The service
  51. will still exit. While theoretically possible, this situation is rather
  52. unlikely.
  53. % D2CTL_STANDALONE skipping message queue, running standalone
  54. This is a debug message indicating that the controller is running in the
  55. process in standalone mode. This means it will not connected to the BIND10
  56. message queue. Standalone mode is only useful during program development,
  57. and should not be used in a production environment.
  58. % D2CTL_RUN_PROCESS starting application proces event loop
  59. This debug message is issued just before the controller invokes
  60. the application process run method.
  61. % D2CTL_FAILED process failed: %1
  62. The controller has encountered a fatal error and is terminating.
  63. The reason for the failure is included in the message.
  64. % D2CTL_CCSESSION_STARTING starting control channel session, specfile: %1
  65. This debug message is issued just before the controller attempts
  66. to establish a session with the BIND 10 control channel.
  67. % D2CTL_CCSESSION_ENDING ending control channel session
  68. This debug message is issued just before the controller attempts
  69. to disconnect from its session with the BIND 10 control channel.
  70. % D2CTL_CONFIG_STUB configuration stub handler called
  71. This debug message is issued when the dummy handler for configuration
  72. events is called. This only happens during intial startup.
  73. % D2CTL_CONFIG_LOAD_FAIL failed to load configuration: %1
  74. This critical error message indicates that the initial process
  75. configuration has failed. The service will start, but will not
  76. process requests until the configuration has been corrected.
  77. % D2CTL_COMMAND_RECEIVED received command %1, arguments: %2
  78. A debug message listing the command (and possible arguments) received
  79. from the BIND 10 control system by the controller.
  80. % D2CTL_NOT_RUNNING The application process instance is not running
  81. A warning message is issued when an attempt is made to shut down the
  82. the process when it is not running.
  83. % D2CTL_CONFIG_UPDATE updated configuration received: %1
  84. A debug message indicating that the controller has received an
  85. updated configuration from the BIND 10 configuration system.