The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to set TES log levels and provides troubleshooting information:
TES supports logging of all actions by all TES components. This section provides the location of the log files, and describes how to control the logging levels for each:
Here is the location of the log files for TES components:
Client Manager sync logs (for information between the CM and it's cache DB):
<CM install dir>\plugins\tes-6.0\logs
<master install dir>\services\<GUID of adapter name, found in the adapter button in the client>\log\
<agent install dir>\<agent instance name>\logs\ES_<name of master>_<date optional>.log
Logging is controlled in different ways depending on the TES component as described in these sections:
To set the logging level for the Master:
Step 1 Open the TES Web or Java Client.
Step 2 Select Activities > System Configuration.
Step 3 Select the Logging tab.
Step 4 Choose the logging level from the drop down menus for each of the objects listed below. Logging levels include: None, Severe, Warning, Info, Low Debug, Medium Debug, or High Debug.
To set the logging level for the Client Manager:
Step 1 Add the following to the bottom of the ClientManager/config/tesXXX.dsp:
To set the logging level for Windows agents:
Step 1 Open the TIDAL Service Manager on the agent machine.
Step 2 Select the agent in the drop down list.
Step 3 Click on the dots [...].
Step 4 In the Service tab, change the path to include the DEBUG option to read "DEBUG=HIGH".
Step 5 Click OK to save changes.
To set the logging level for Unix agents:
Step 1 Go to the agent machine and go to the directory the agent is installed in.
Step 2 Go to "Bin/" and edit "tagent.ini".
To set the logging level for adapters:
Step 1 Open the TES Web or Java Client.
Step 2 In the Navigator, click Connections.
Step 3 Locate and double-click the Master connection (Type=Master) to open its editor.
To set the logging level for Transporter:
Step 1 Edit transporter.props in the Transporter’s config directory:
To set the logging level for Fault Monitor:
Step 1 Edit Primary Master and Backup Master master.props file.
Step 2 Edit Fault Monitor master.props file:
If your Master or Client Manager will not start and no logs are created in the logs directories, your system probably has a problem loading the Java Virtual Machine (JVM). Java uses a JVM to execute its processes inside, so if the system cannot launch the JVM, then the TES code cannot run.
To troubleshoot and resolve a Java problem
Step 1 Make sure Java is installed and in the PATH. Run this on a command line:
Step 2 Find where your java lives:
Step 3 Make sure that your master.props or clientmgr.props files match this location.
No further Unix troubleshoot should be required. Open a TAC case if you still have no success running the master or Client Manager.
Make sure regedit matches this location in the following keys:
b. HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.7*
The JavaHome and the RuntimeLib should have their locations verified for accuracy. Make sure that "client" and "server" in the RuntimeLib string are correct. This is often the issue.
*If you have multiple 1.7 and 1.7.0.X keys here, make sure that both are correct.
If you are trying to install the Java client, edit the tesclient.bat file and verify the paths inside. These can be edited if they are incorrect as discovered in steps 1 and 2.