5.3.7 Monitoring and Diagnosing Jobs

In addition to the dispatch.log file that records events for all jobs, the system creates a job log for each job. A job log records only the events that are applicable to that specific job. By default, a job log resides in the $KDD_PRODUCT_HOME/logs directory. You can configure the location of this log in the <OFSAAI Installed Directory>/behavior_detection/algorithms/MTS/mantas_cfg/install.cfg file.

Note:

$KDD_PRODUCT_HOME is the path of <OFSAAI Installed Directory>/behavior_detection/algorithms/MTS

If you do not know the location of the log directory, check the install.cfg file. The log.mantaslog.location property indicates the log location. The default is $KDD_PRODUCT_HOME/ logs, but this location is configurable.

When troubleshooting a job processing problem, first look at the file dispatch.log for the sequence of events that occurred before and after errors resulted from a job. Then, look at the job log to diagnose the cause of the errors. The job log provides detailed error information and clues that can help you determine why the job failed or generated errors.

The log file name for a job appears in the following format in the log directory:
job<job_id>-<date>-<time>.log

where Split p is the job ID and <date> and <time> represent the job’s starting time stamp.

If the job errors occurred due to a problem at the system level, you may must resolve it. If you believe that the job errors were generated due to incorrect setups in OFSBD, you should notify the System Administrator, who can correct the problem setups.

Note:

The dispatch.log may contain a JVM core dump. This does not indicate the actual cause of an error. In order to find the underlying error, you must refer to the job log.
To monitor a specific job or to look at the job log history for diagnostic purposes, follow these steps:
  1. Type tail -f <log> at the system prompt and press Enter, where <log> is the name of the job log file.

    The job log scrolls down the screen.

  2. Press Ctrl+C to stop the display.
  3. Type lpr job<job_id>-<date>-<time> at the system prompt and press Enter to print the job log.

    Note:

    This job log file may be a lengthy printout.