Cisco Cisco Workload Automation 6.3 User Guide
24
Logging and Troubleshooting
Troubleshooting CWA when the Master or Client Manager Will Not Start
FaultMonitorLog=INFO
FaultToleranceLog=INFO
Troubleshooting CWA when the Master or Client Manager Will Not Start
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 CWA code cannot run.
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 CWA code cannot run.
To troubleshoot and resolve a Java problem
1.
Make sure Java is installed and in the PATH. Run this on a command line:
java -version
2.
Find where your java lives:
Unix:
which java
Windows:
where.exe java (only works on win 2003 and later)
3.
Make sure that your master.props or clientmgr.props files match this location.
Unix:
No further Unix troubleshoot should be required. Open a TAC case if you still have no success running the master or
Client Manager.
Client Manager.
Windows:
Make sure regedit matches this location in the following keys:
a.
Launch regedit.exe
b.
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.8 support
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.
"server" in the RuntimeLib string are correct. This is often the issue.
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.
are incorrect as discovered in steps 1 and 2.