Universal Messaging 10.7 | Administration Guide | Using Command Central to Manage Universal Messaging | Run-time Monitoring Statuses for Universal Messaging Server
 
Run-time Monitoring Statuses for Universal Messaging Server
The following table lists the run-time statuses that a Universal Messaging server instance can return in response to the sagcc get monitoring state command, and the meaning of each status.
Important:
When a Universal Messaging server instance is running as a service, you cannot perform administrative tasks such as check the status, or start and stop the server instance.
Note:
The Universal Messaging server instance does not return the STOPPING and STARTING statuses.
Run-time Status
Meaning
ONLINE
Universal Messaging server instance is running.
FAILED
Universal Messaging server instance is not running due to some failure. LOCK file exists.
STOPPED
Universal Messaging server instance is not running because it was shut down normally. LOCK file does not exist.
UNRESPONSIVE
Universal Messaging server instance does not respond to a ping operation. LOCK file exists and the Universal Messaging server instance is running.
UNKNOWN
The status of Universal Messaging server instance cannot be determined.
ONLINE_MASTER
Server instance is online and it is the master node in the cluster.
ONLINE_SLAVE
Server instance is online and it is the slave node in the cluster.
ERROR
Server instance is part of a cluster that does not satisfy the requisite quorum.