5.2.3 Stopping the Dispatcher

You do not normally shut down the dispatcher except for reasons such as the following:

• Problems while executing scenarios, make it necessary to stop processing.
• The dispatcher and job processes are reporting errors.
• The dispatcher is not performing as expected.
• You must shut down the system for scheduled maintenance.
• You want to run the start_mantas.sh, restart_mantas.sh, or recover_mantas.sh script without the dispatcher already running. You can then save your log files to the server on which you are working rather than the server running the dispatcher.

  Note:

  The dispatcher which started from the Behavior Detection jobs in the UI should be stopped before restarting servers.

  Note:

  If you shut down the dispatcher, all active jobs shut down with errors.

When you are ready to restart the dispatcher and you want to see which jobs had real errors and which jobs generated errors only because they were shut down during processing, review the error messages in the job logs.

For those jobs that shut down and generate errors because the dispatcher shut down, a message similar to the following appears: Received message from dispatcher to abort job. If the job generates a real error, a message in the job log file indicates the nature of the problem.

To view active jobs and then shut down the dispatcher, follow these steps:

1. Type ps -efw | grep mantas and press Enter at the system prompt.

   All instances of the MANTAS process that are running appear on the screen. Only one instance of MANTAS should run for each active job.

2. Type stop_chkdisp.sh <dispatcher name> and press Enter at the system prompt.

   This script shuts down the dispatcher.