4.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 <INSTALL_DIR>/behavior_detection/algorithms/MTS/mantas_cfg/
install.cfg file.
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 <job_id> is the job ID and <date> and
<time> represent the job’s starting timestamp.
Note:
Thedispatch.log may contain a JVM core dump. This does not
indicate the actual cause of an error; you must See the job log for the underlying
error.
To monitor a specific job or to look at the job log history for diagnostic purposes, follow these steps:
- 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. - Press Ctrl+C to stop the display.
- 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.