Cisco Cisco Workload Automation 6.3 User Guide
385
Troubleshooting
Troubleshooting the Master
and then create another similar job to return the diagnostic logging levels to their original settings after recording the
system information. This job will limit how long the diagnostic logging runs to prevent massive amounts of information
from clogging your disk space.
system information. This job will limit how long the diagnostic logging runs to prevent massive amounts of information
from clogging your disk space.
To run diagnostic logging as a job:
1.
Click the Add Job button on the CWA toolbar or right-click in the Jobs pane and select Add Job to display the Job
Definition dialog.
Definition dialog.
2.
Type a name for the job.
3.
In the Command field on the Program tab, type
java
.
4.
In the Command Parameters field, modify the following command parameters as needed:
java -DTidal_HOME=/opt/Tidal/master -cp/opt/Tidal/lib/scheduler.jar com.tidalsoft.scheduler.SetDebugLevel
-m <Master Machine Name>
-p ClientPort(defaults to correct number)
-S (Scheduler Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-CL (Client Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-A (Agent Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-CO (Compiler Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-J (Job Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-E (Event Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-Q (Queue Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-D (Database Log) SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-COM(Comununcations Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-m <Master Machine Name>
-p ClientPort(defaults to correct number)
-S (Scheduler Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-CL (Client Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-A (Agent Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-CO (Compiler Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-J (Job Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-E (Event Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-Q (Queue Manager Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-D (Database Log) SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
-COM(Comununcations Log)SEVERE|WARNING|INFO|LOW|MEDIUM|HIGH
Do not include any of the explanatory text that is in parentheses or brackets. Replace the text in brackets with the
name of the machine that the master resides upon. The section of the first line “opt/Tidal” should be the directory
location where the master is installed. Select just one of the logging levels to use with only the components you wish
to enable for diagnostic logging. Any component log that is not included in the parameters is not affected by the
logging job and retains its original setting. Don’t forget to run another job to return the diagnostics to the original
setting.
name of the machine that the master resides upon. The section of the first line “opt/Tidal” should be the directory
location where the master is installed. Select just one of the logging levels to use with only the components you wish
to enable for diagnostic logging. Any component log that is not included in the parameters is not affected by the
logging job and retains its original setting. Don’t forget to run another job to return the diagnostics to the original
setting.
Running the Windows Master in Debug Mode
Even if you have configured the master to log diagnostic information, there is still a period of time between when the
master starts and when it begins logging information. If the issue you are trying to troubleshoot occurs in this time window
before diagnostic information is recorded than you should configure the master to run in debug mode. This will ensure
that information is collected the entire time the master runs.
master starts and when it begins logging information. If the issue you are trying to troubleshoot occurs in this time window
before diagnostic information is recorded than you should configure the master to run in debug mode. This will ensure
that information is collected the entire time the master runs.
To run the Windows master in Debug mode:
1.
Open a command prompt screen from the Start button menu by selecting All Programs>Accessories>Command
Prompt.
Prompt.
2.
Type the directory path to the master executable file and then place a debug parameter after, e.g.,
“C:\Program Files\TIDAL\Scheduler\Master\saMaster64.exe” -debug
Turn off the debugging mode by killing the saMaster64.exe process that you started.
Running the Unix Master in Debug Mode
Even if you have configured the master to log diagnostic information, there is still a period of time between when the
master starts and when it begins logging information. If the issue you are trying to troubleshoot occurs in this time window
before diagnostic information is recorded than you should configure the master to run in debug mode. This will ensure
that information is collected the entire time the master runs.
master starts and when it begins logging information. If the issue you are trying to troubleshoot occurs in this time window
before diagnostic information is recorded than you should configure the master to run in debug mode. This will ensure
that information is collected the entire time the master runs.