Using the log files to troubleshoot

Log files are the one of the primary sources of information used to troubleshoot issues in BMC Atrium Orchestrator.

For most issues, the grid.log file, located in AO_HOME/tomcat/logs is the most helpful.
If you experience a problem when running your own workflows, the processes.log, located in AO_HOME/tomcat/logs, might be the most useful in diagnosing the problem.
If the server has stopped or will not come up, the catalina.log (for Windows) or catalina.out (*for Linux or UNIX) file, located in *AO_HOME/tomcat/logs might be the most helpful.

What to look for in the logs

Each of the logs has key words or phrases to search for. If you find the word or words, look for the time stamp on the same line as or just before the word or phrase. Look also for the next time stamp after the word or phrase. The information between the time stamps contains details about the problem.

In the grid.log file, search for the following terms:

In the processes.log file, search for the following terms: 

In the catalina.log file or the catalina.out file, search for the following term: 

Search the BMC Knowledge Base

After you search for the key words, review the information on the lines closest to the key words. Look for any error messages or other distinctive information. Then use the BMC Knowledge Base to search for information relevant to the error message that you find.
You can access the BMC Knowledge Base from the BMC Customer Support web page at http://www.bmc.com/support.

grid.log example

In this example, you would search the knowledge base for the phrase "OutOfMemoryError" or "PermGen Space."

catalina.log example

In this example, you would search the knowledge base for the phrase "Error initializing endpoint" or "Address already in use."