Situation 1

The Alerts icon turns red and a log storage alert appears in the Alerts window. There are several different log storage alerts, each described in the following messages. For each alert, refer to the logging error file on the Operations Sentinel server if you need help determining the cause of the alert. This file is located at installation-folder\output\splog-pid-error.txt, where pid is the process ID of the Operations Sentinel logging service.

Alert

Log Storage error on write to log file.

Explanation

Operations Sentinel Logging is unable to write to the mass storage device where the log files are stored.

Solution

Examine the Operations Sentinel logging error file for detailed information.

Additional Alerts

Log Storage fail - Contact lost.

Log Storage fail - Cannot contact.

Log Storage maintenance - Contact lost.

Log Storage maintenance - Cannot contact.

Explanation

One of these alerts is raised if the Operations Sentinel services are not currently running or completely initialized, or if there is a transient network problem.

Solutions

Determine why the services are not running. Check the Operations Sentinel error files for information. Restart the services once the problem is found.

The "Contact lost" alerts indicate that contact with the services was made, but has been lost. This could indicate there is a transient network problem.

The "Cannot contact" alerts indicate that contact with the services was not made.

The "fail" alerts are raised by the logging service and the "maintenance" alerts are raised by the process that monitors mass storage.

Situation 2

Operations Sentinel services do not start after you remove a server and re-enter it in a domain. When the Operations Sentinel server is taken out of the domain and rejoined to the same or a different domain in the network, an attempt to start the Operations Sentinel services from the Administrative Tools menu might display an error message.

Message

The Operations Sentinel service failed to start in time.

Explanation

A domain user account is used to start the Operations Sentinel services. This problem does not occur if a local user account is used.

Under some circumstances, the domain user account is not authenticated properly for a Windows service account if the server is taken out of the domain and rejoined to the same or a different domain in the network.

Solution

Start the Operations Sentinel Service Account utility from the Operations Sentinel Administrative Tools menu and reset the service account and password.