To stop ArkManager, enter the following command at the server console command prompt:
arkstop
After typing arkstop, make sure ArkManager is shutting down cleanly before running it again. You can check this in two ways:
If is enabled for the server (that is, the <displayLog/> tag is placed in the arkconfig.xml file), go to the server’s Logger screen and wait until the ArkManager shutdown is completed message appears.
On the archive server’s console screen, use the java -show command to check that no ArkManager Java thread is running.
It might take a while for ArkManager to shut down because it needs to wait for its current file archiving process to finish. Under normal circumstances, ArkManager should eventually shut down cleanly.
If you need to stop the ArkSQL instance of MySQL, see Section 11.4, Stopping the MySQL Server and ArkSQL.
If you suspect the shutdown process is taking an unreasonably long time, and it might be hanging, use the following procedure to get ArkManager’s thread ID and kill the ArkManager process manually.
At the server console command prompt, enter
java -show
This returns a list of current process IDs.
Get ArkManager’s process ID from the list.
At the server console command prompt, enter
java -killxx
where xx is ArkManager’s process ID.
For a clustered server solution, stop ArkManager and ArkSQL by stopping the cluster resources. For information, see the OES 2: Novell Cluster Services 1.8.4 for NetWare Administration Guide.