Cisco Cisco Workload Automation 6.3 User Guide
384
Troubleshooting
Troubleshooting the Master
It is the current log file that the master is still creating.
Note: Do not delete the current log file, which is always the log file with the latest timestamp. Even if the file does not
exist, the master will continue to relay diagnostic information to the log file until it has relayed 1 MB of information. At
that point, the master starts a new log file but any diagnostic information from the time between the deletion of the
current log file and the creation of a new log file is lost.
exist, the master will continue to relay diagnostic information to the log file until it has relayed 1 MB of information. At
that point, the master starts a new log file but any diagnostic information from the time between the deletion of the
current log file and the creation of a new log file is lost.
Diagnostic Logging Tasks
Adjusting the Log File Retention
Each time the log file for the master reaches one megabyte in size, it is saved and another log file started. By default, the
master is configured to store the 25 most recent log files. When the log files exceed the maximum number, the oldest
log file is automatically deleted to make room for a newer log file.
master is configured to store the 25 most recent log files. When the log files exceed the maximum number, the oldest
log file is automatically deleted to make room for a newer log file.
You may need to adjust the log file retention number whenever you are running diagnostic logging. A higher level of
diagnostic detail will create log files that add up quickly. Increase the log file retention number whenever you run
diagnostic logging to compensate or you will start deleting the earliest log files before you have a chance to examine
them.
diagnostic detail will create log files that add up quickly. Increase the log file retention number whenever you run
diagnostic logging to compensate or you will start deleting the earliest log files before you have a chance to examine
them.
To adjust the log file retention:
1.
From the command line of the master machine, stop the master:
tesm stop
2.
Locate the Master.Props file in the config directory of the master machine and open it.
3.
Add the following line to the Master.Props file:
MaxLogFiles=<number of log files>
where
<number of log files>
is the maximum number of log files to retain before deleting the oldest file.
The minimum number of log files to be retained is three. There is no maximum number.
4.
From the command line, restart the master:
tesm start
Purging Old Job Data
On occasion, the CWA database and CWA schema will not stop growing in size and very old data builds up in the
database. This old data should be purged on a regular basis or the database will continue to bloat.
database. This old data should be purged on a regular basis or the database will continue to bloat.
To purge old job data:
1.
Select the System Configuration option from the Activities main menu to check the data retention value in the
System Configuration dialog.
System Configuration dialog.
2.
On the Master tab, verify that the Automatic Daily History Cleanup option is selected and select it if it is not already
selected. If you are using a database alias other than the default “Admiral,” this feature may not operate correctly.
selected. If you are using a database alias other than the default “Admiral,” this feature may not operate correctly.
Running Diagnostic Logging as a Job
If a problem is occurring at a time that is difficult for an operator to monitor, say when a certain job deep in the production
schedule runs, you can run a job to enable diagnostic logging just as the suspected job runs. You can create a logging
job from the command line using a Java utility that CWA provides. Configure the job to run just before the problem occurs
schedule runs, you can run a job to enable diagnostic logging just as the suspected job runs. You can create a logging
job from the command line using a Java utility that CWA provides. Configure the job to run just before the problem occurs