7.3 Starting and Stopping Daemons in the MC/ServiceGuard System

This section describes how to start and stop Systemwalker Operation Manager in the MC/ServiceGuard system.

Starting daemons

This section describes the procedure for starting the Systemwalker Operation Manager daemons.

On all servers on both the active and standby nodes, execute the soperationmgr command to start any Systemwalker Operation Manager daemons that are not registered with MC/ServiceGuard. In the case of the 1:1 active/standby configuration (with subsystems and partial cluster operation), the JobScheduler daemons and Job Execution Control daemons of subsystems that are not registered in cluster systems will also be started up.
```
# /opt/systemwalker/bin/soperationmgr
```
Start the Jobscheduler and Job Execution Control daemons registered with MC/ServiceGuard by starting the package.
```
# cmrunpkg -v -n node-name package-name
```
Example:
```
# cmrunpkg -v -n hp01 omgr
```

Stopping daemons

This section describes the procedure for stopping the Systemwalker Operation Manager daemons.

Stop the Jobscheduler and Job Execution Control daemons registered with MC/ServiceGuard by stopping the package.
```
# cmhaltpkg -v package name
```
Example:
```
# cmhaltpkg -v omgr
```
On all the servers on both the active and standby nodes, execute the poperationmgr command to stop any Systemwalker Operation Manager daemons that are not registered with MC/ServiceGuard. In the case of the 1:1 active/standby configuration (with subsystems and partial cluster operation), the JobScheduler daemons and Job Execution Control daemons of subsystems that are not registered in cluster systems will also be stopped.
```
# /opt/systemwalker/bin/poperationmgr
```

Note

Do not move the current directory to the shared disk when executing the soperationmgr command or the poperationmgr command. Otherwise, a failover may not be performed correctly.
Do not start or stop any services using the Service control section in the Systemwalker Operation Manager Environment Setup window.
Any packages where the Systemwalker Operation Manager service has been registered must be stopped before Systemwalker Operation Manager is stopped (if Systemwalker Operation Manager has been registered with a cluster system).
As a result, the shared disk and logical IP address registered with any such package will also stop, along with the Operation Manager service and any applications (such as Oracle or Interstage) registered with it.

Note

If the package is stopped and restarted, the "STATUS" and "STATE" of the cluster and package displayed with the cmviewcl command may become "down" or "halted", and the switching status may become "disabled". In such cases, switch the package status using the cmmodpkg command. Refer to "7.1.3 Starting and stopping the package" for details.