cmdctl_messages.mes 3.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081
  1. # Copyright (C) 2011 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. # No namespace declaration - these constants go in the global namespace
  15. # of the cmdctl_messages python module.
  16. % CMDCTL_BAD_CONFIG_DATA error in config data: %1
  17. There was an error reading the updated configuration data. The specific
  18. error is printed.
  19. % CMDCTL_BAD_PASSWORD bad password for user: %1
  20. A login attempt was made to b10-cmdctl, but the password was wrong.
  21. Users can be managed with the tool b10-cmdctl-usermgr.
  22. % CMDCTL_CC_SESSION_ERROR error reading from cc channel: %1
  23. There was a problem reading from the command and control channel. The
  24. most likely cause is that the message bus daemon is not running.
  25. % CMDCTL_CC_SESSION_TIMEOUT timeout on cc channel
  26. A timeout occurred when waiting for essential data from the cc session.
  27. This usually occurs when b10-cfgmgr is not running or not responding.
  28. Since we are waiting for essential information, this is a fatal error,
  29. and the cmdctl daemon will now shut down.
  30. % CMDCTL_COMMAND_ERROR error in command %1 to module %2: %3
  31. An error was encountered sending the given command to the given module.
  32. Either there was a communication problem with the module, or the module
  33. was not able to process the command, and sent back an error. The
  34. specific error is printed in the message.
  35. % CMDCTL_COMMAND_SENT command '%1' to module '%2' was sent
  36. This debug message indicates that the given command has been sent to
  37. the given module.
  38. % CMDCTL_NO_SUCH_USER username not found in user database: %1
  39. A login attempt was made to b10-cmdctl, but the username was not known.
  40. Users can be added with the tool b10-cmdctl-usermgr.
  41. % CMDCTL_NO_USER_ENTRIES_READ failed to read user information, all users will be denied
  42. The b10-cmdctl daemon was unable to find any user data in the user
  43. database file. Either it was unable to read the file (in which case
  44. this message follows a message CMDCTL_USER_DATABASE_READ_ERROR
  45. containing a specific error), or the file was empty. Users can be added
  46. with the tool b10-cmdctl-usermgr.
  47. % CMDCTL_SEND_COMMAND sending command %1 to module %2
  48. This debug message indicates that the given command is being sent to
  49. the given module.
  50. % CMDCTL_SSL_SETUP_FAILURE_USER_DENIED failed to create an SSL connection (user denied): %1
  51. The user was denied because the SSL connection could not successfully
  52. be set up. The specific error is given in the log message. Possible
  53. causes may be that the ssl request itself was bad, or the local key or
  54. certificate file could not be read.
  55. % CMDCTL_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down
  56. There was a keyboard interrupt signal to stop the cmdctl daemon. The
  57. daemon will now shut down.
  58. % CMDCTL_UNCAUGHT_EXCEPTION uncaught exception: %1
  59. The b10-cdmctl daemon encountered an uncaught exception and
  60. will now shut down. This is indicative of a programming error and
  61. should not happen under normal circumstances. The exception message
  62. is printed.
  63. % CMDCTL_USER_DATABASE_READ_ERROR failed to read user database file %1: %2
  64. The b10-cmdctl daemon was unable to read the user database file. The
  65. file may be unreadable for the daemon, or it may be corrupted. In the
  66. latter case, it can be recreated with b10-cmdctl-usermgr. The specific
  67. error is printed in the log message.