Where can I find log files of a modeling tool, Cameo Collaborator and Teamwork Cloud?
When you report an issue with your modeling tool, Cameo Collaborator or Teamwork Cloud, always include related log files. Log files provide useful information that we need to investigate and troubleshoot your problem.
Accessing log files
- For a modeling tool
Open your modeling tool and in the main menu go to Help > About <modeling tool name>. In the Environment tab, click the link provided in the Log File line to open a log file.
- For Cameo Collaborator
Go to Alfresco Community installation directory, and obtain the alfresco.log, share.log and solr.log files.
Go to <Alfresco Community installation directory>\tomcat\logs, and obtain the alfrescotomcat-stderr.log, alfrescotomcat-stdout.log and catalina.log files.
- For Teamwork Cloud
Go to <user home directory>\.twcloud\<server version>, and obtain the server.log and client.log files.
Go to <Cassandra installation directory>\logs on Windows OS or /var/lib/Cassandra on Linux, and obtain the Cassandra log file.
Generating a log file
If the performance of your modeling tool declines or it freezes, go to <modeling tool installation directory>\bin, and run the submit_issue.exe file several times. It dumps threads into the log file of your modeling tool. Then you can access the log file, as described above.
Java crash log files
If your modeling tool crashes (disappears), try searching for Java crash log files. They are stored in the running location of the modeling tool, e.g., the <modeling tool installation directory>/bin or <modeling tool installation directory> directory. The names of these log files start with "hs_err", e.g., hs_err_pid15693.log. If you find the Java crash log file, the reason your modeling tool crashed was that Java crashed.