view agent/cli/src/main/resources/com/redhat/thermostat/agent/cli/impl/strings.properties @ 898:5a2d3c43b551

Remove stale mongo PID file and start storage. I can't think of a reason why removing a stale pid file and starting mongo afterwards would do us any harm. Previously thermostat was refusing to start storage if a stale pid file was present. This makes integration tests consistently fail on mongodb 2.2.2. Seems to be a bug in mongodb 2.2.2. Reviewed-by: omajid Review-thread: http://icedtea.classpath.org/pipermail/thermostat/2013-January/005040.html
author Severin Gehwolf <sgehwolf@redhat.com>
date Tue, 08 Jan 2013 19:22:32 +0100
parents 92f9af1bcd3a
children
line wrap: on
line source

STARTING_AGENT = starting agent now...

COMMAND_STORAGE_ARGUMENT_REQUIRED = either --start or --stop must be given

ERROR_STARTING_DB = error starting db
STORAGE_ALREADY_RUNNING = Storage is already running. Please use "agent --start" to start the agent
STORAGE_ALREADY_RUNNING_WITH_PID = Storage is already running with pid {0}
SERVER_SHUTDOWN_COMPLETE = server shutdown complete: {0}
LOG_FILE_AT = log file is here: {0}
CANNOT_START_SERVER = cannot start server {0}, exit status: {1}. Please check that your configuration is valid
CANNOT_SHUTDOWN_SERVER = cannot shutdown server {0}, exit status: {1}. Please check that your configuration is valid
STALE_PID_FILE = stale pid file: {0}
STALE_PID_FILE_NO_MATCHING_PROCESS = A stale pid file ({0}) is present but there is no matching {1} process. Removing stale pid file.
STARTING_STORAGE_SERVER = starting storage server...
CANNOT_EXECUTE_PROCESS = can not execute {0} process. is it installed?
SERVER_LISTENING_ON = server listening on ip: {0}
PID_IS = pid: {0}