2.3 Stopping Daemons

Stop daemons from the Management Server and Managed Server. Normally, they are automatically stopped on system shutdown.

To stop daemons on a server, execute the following command on the server:

# /opt/swstorage/bin/stopacm

Note

Before executing the stopacm command, confirm that the SWSTGNODE environment variable is not defined.
The Management Server of AdvancedCopy Manager uses Symfoware. Stopping the service may fail if Symfoware is monitored by other software.

When the Management Server or Managed Server is in cluster operation, stop the daemon(s) from the clustered system. For the stop procedure, refer to the relevant cluster software manual.

To stop the daemon separately

To stop the daemon separately on AdvancedCopy Manager transactions in a clustered system, follow the steps described below:

Communication daemon:
You must stop the daemon in each AdvancedCopy Manager transaction (including local transactions) using the following procedure for the respective transactions.
1. Execute the following command.
```
# ps -elf | grep stgxfws
```
  Confirm that command execution displays the following strings. If the strings are not displayed, the daemon(s) has already stopped.
```
/opt/FJSVswstf/bin/stgxfws <logical-node-name>
```
2. For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
3. Stop the communication daemon.
  For the stop command, refer to "8.5.1 Starting and stopping the communication daemon".
  Point
  Terminating the communication daemon, may take up to 10 seconds to complete successfully.

For daemons other than the communication daemon:
1. For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
2. Refer to the following sections to stop the daemon.
  - RMI daemon: "8.5.2 Starting and stopping the RMI daemon"
  - RDB daemon: "8.5.3 Starting and stopping the RDB daemon"