3.2 Configuring an Auto-Restart

The Auto-Restart monitoring utility ensures that Operations Center software and its ancillary processing run continuously. The Auto-Restart utility probes Operations Center and other processes launched by the daemon process at periodic intervals. If it determines that a process can no longer be accessed using CORBA or that a process has stopped, it attempts to restart the process. Optionally, the Auto-Restart utility can be configured to restart the daemon process.

The Auto-Restart utility can be launched using one of the following methods, depending on the purpose for using it:

A potential conflict exists for UNIX systems that run cron jobs that detect when Operations Center software is down and restart it. The cron jobs must be disabled before using the Operations Center Auto-Restart utility.

To configure an auto-start:

3.2.1 Configuring the Windows Service

By default, the Auto-Restart utility is installed as a Windows service and is set to run automatically. Under Windows and UNIX, the daemon can be restarted if necessary because the Auto-Restart utility runs as an independent process.

To launch the Auto-Restart utility as a Windows Service:

  1. From the desktop, click Start > Control Panel.

  2. Double-click Administration Tools.

  3. Double-click Services to display the Services window:

    Services Window
  4. Double-click NetIQ Operations Center Auto-Restart Service.

    Managed Auto-Restart Properties (Local Computer) Dialog Box
  5. From Startup Type drop-down list, select one of the following options:

    Startup Type

    Description

    Automatic

    The Auto-Restart service automatically starts when Windows starts. If running, the Auto-Restart service automatically starts Operations Center software when the server stops running.

    Manual

    The Auto-Restart service does not start when Windows starts, but can be manually started and stopped. Use a command line to start the Operations Center server.

    Disable

    The Auto-Restart service is disabled. To start the Operations Center server, reset this option to Manual and use a command line to start it.

  6. Click the Start button.

  7. Click OK to start the service.

3.2.2 Configuring Daemon Control

Launch the Auto-Restart utility under daemon control if network stability problems or environmental issues cause the Operations Center Java process to exit. Using this method, the daemon cannot be restarted because the Auto-Restart process is launched as a child process of the daemon. The Auto-Restart monitoring process inherits the daemon’s resources if the daemon exists for any reason.

To configure the Auto-Restart utility to start under daemon control:

  1. In Configuration Manager, select the Daemon pane on the Components tab.

  2. In the Automatically Start Servers field, enter the server names in the list of servers that start automatically from the daemon.

    By default, this is set to Image Formula.

    Use a space to separate server names. Append with EveConfigManager EveAgentManager EveAlarmServer to start Event Manager components, or append with RemoteContainer_name to start Remote Containers on the same server.

    For information on Event Manager, see Operations Center Event Manager Guide. For information on Remote Containers, see Using Remote Containers in the Operations Center Adapter and Integration Guide.

  3. To pause the daemon between server startups, enter the keyword pause(n) between the server names, where n is the number of seconds.

    If you enter 30 for n, Daemon.trc will contain the message: Pausing for 30 seconds.

    Entering pause Formula without specifying any seconds pauses the daemon for one second.

  4. Click Save to save all of the changes in Configuration Manager.

    Regardless of whether the database setting is specified for this property, if there is an active database definition set up to use the Operations Center embedded database for Configuration Storage, the embedded database starts when the server starts.

3.2.3 Stopping mosmonitor from Automatically Restarting Operations Center

The mosmonitor service ensures that Operations Center software is running. If the Operations Center process stops, or if the daemon process stops, mosmonitor automatically restarts Operations Center software. However, you can shut down mosmonitor so that it won’t automatically restart Operations Center.

To shut down the mosmonitor service, enter mosmonitor ‑shutdown at a command prompt.

The daemon.trc file logs that the monitor service has been shut down.