The Novell Teaming log file (ssf.log) is available from the Teaming site.
Log in as the Teaming site administrator.
Click , then expand .
Click .
You are prompted to open or save a file named logfiles.zip, which contains the current ssf.log file. This file contains any stack traces or warning messages due to unexpected events encountered by the Teaming program.
Save the ssf.log file to a convenient location on the Teaming server.
This file is helpful when you need assistance resolving a problem with your Teaming site.
The Teaming log file is also available in the following directory of your Teaming installation:
|
Linux: |
/opt/novell/teaming/apache-tomcat-version/webapps/ssf/WEB-INF/logs
|
|
Windows: |
c:\Program Files\Novell\Teaming\apache-tomcat-version\
webapps\ssf\WEB-INF\logs
|
This is helpful if Teaming does not start.
In addition to the Novell Teaming error log file (ssf.log), the Tomcat error log file (catalina.out on Linux and stdout_*.log on Windows when Teaming runs as a service) is also useful. The Tomcat log file contains more information than the Teaming log file, because it includes problems encountered by Tomcat outside of the Teaming application itself. The location of the Tomcat log file varies by platform:
|
Linux: |
/opt/novell/teaming/apache-tomcat-version/logs |
|
Windows: |
c:\Program Files\Novell\Teaming\apache-tomcat-version\logs |
NOTE:When Teaming and Tomcat run as a Windows application, rather than as a Windows service, the information displayed in the Command Prompt window where you started Teaming is your only source of information. The data displayed in the Command Prompt window is not logged by Tomcat on Windows.
The Tomcat log file provides the following useful information:
At the top, the Tomcat log file lists Tomcat startup messages.
The System Properties section lists information about the supporting software packages that Tomcat relies on (for example, Java) and information about their current location and configuration.
The System Environment section lists the currently set environment variables (for example, HOSTNAME, PATH, and JAVA_HOME).
Exception and error data includes sufficient information for you to determine what user was trying to perform what action in what location on the Teaming site, to help you isolate and reproduce the problem.
NOTE:If your Teaming site was originally installed as a Teaming 2.0 site, the root of your site is referred to as org.kablink in the Tomcat error log. If you updated from a Teaming 1.0 site or a Teaming 2.0 beta site, the root of your site is referred to as com.liferay.
This file is helpful when you need assistance resolving a problem with your Teaming site.
The log levels for various Tomcat functions are set in the log4j.properties file. Each type of information that is logged can have a log level of INFO, WARN, ERROR, FATAL, or DEBUG, depending on the type and quantify of information that you want logged. Some lines in the log4j.properties file are commented out with a pound sign (#), so that no information of that type is gathered. You can change the log level for each type of information and comment or uncomment lines to adjust the information gathered in the Tomcat log file to meet your troubleshooting needs.
Open the log4j.properties file in a text editor.
The location of the log4j.properties file varies by platform.
Change log level settings as needed for the type of information you want to gather.
Comment or uncomment lines, depending on the type of information you want to gather.
Save the log4j.properties file, then exit the text editor.
Stop Teaming, then start Teaming to put the new logging level into effect.