Руководство Пользователя для Cisco Cisco Tidal Enterprise Scheduler 6.2
14-416
Cisco Tidal Enterprise Scheduler 6.2 User Guide
6.2.1
Chapter 14 Troubleshooting
Troubleshooting the Master
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.
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.
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.
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.
To run the Windows master in Debug mode:
Step 1
Open a command prompt screen from the Start button menu by selecting
Programs>Accessories>Command Prompt.
Programs>Accessories>Command Prompt.
Step 2
Type the directory path to the master executable file and then place a debug parameter after, e.g.,
“C:\Program Files\Tidal\TES\master\samaster.exe” -debug
Turn off the debugging mode by killing the samaster.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.
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.
From the command line program on the Unix master machine, type:
tesm -debug start
Turn off the debugging mode by killing the debug process that you started.
OCSEXIT Jobs
If you find that jobs created using the OCSEXIT variable, and that run on Windows agents, consistently
end in Completed Abnormally you may need to update your system path.
end in Completed Abnormally you may need to update your system path.
To update your system path:
Step 1
Click the Windows Start menu button and select Settings>Control Panel.
Step 2
Start the System Properties
control panel.