31.3 Using Log Files

31.3.1 Vibe Log File

The Vibe log file (ssf.log) is available from the Vibe site.

  1. Log in as the Vibe site administrator.

  2. Click your linked name in the upper right corner of the page, then click the Administration Console icon .

  3. Under System, click Reports, click System Error Logs.

  4. In the Run a Report drop-down list, select System Error Logs.

  5. Click Download Log.

    You are prompted to open or save a file named logfiles.zip, which contains the current appserver.log file. This file contains any stack traces or warning messages because of unexpected events encountered by the Vibe program.

  6. Save the appserver.log file to a convenient location on the Vibe server.

    This file is helpful when you need assistance resolving a problem with your Vibe site.

If you are unable to start Vibe and therefore cannot retrieve the log file as described above, the Vibe log file is also available in the following directory of your Vibe installation:

Linux:

 
/opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/logs

Windows:

 
c:\Program Files\Novell\Teaming\apache-tomcat\webapps\ssf\WEB-INF\logs

31.3.2 Tomcat Log File

In addition to the Vibe error log file (ssf.log), the Tomcat error log file (catalina.out on Linux and stdout_*.log on Windows when Vibe runs as a service) is also useful. The Tomcat log file contains more information than the Vibe log file, because it includes problems encountered by Tomcat outside of the Vibe application itself. The location of the Tomcat log file varies by platform:

Linux:

/opt/novell/teaming/apache-tomcat/logs

Windows:

c:\Program Files\Novell\Teaming\apache-tomcat\logs

NOTE:When Vibe and Tomcat run as a Windows application, rather than as a Windows service, the information displayed in the command prompt window where you started Vibe 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 Vibe site, to help you isolate and reproduce the problem.

    NOTE:The Vibe product name prior to version 3 is Novell Teaming. If your Vibe site was originally installed as a Teaming 2.0 or Vibe 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 Vibe site.

Adjusting the Log Level for the Tomcat Log File

The log levels for various Tomcat functions are set in the log4j2.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 log4j2.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.

  1. Open the log4j2.properties file in a text editor.

    The location of the log4j2.properties file varies by platform.

    Linux:

    		 
    /opt/novell/teaming/luceneserver/indexserver/lib

    Windows:

    		 
    C:\Program Files\Novell\Teaming\apache-tomcat\conf                                         

  2. Change log level settings as needed for the type of information you want to gather.

  3. Comment or uncomment lines, depending on the type of information you want to gather.

  4. Save the log4j2.properties file, then exit the text editor.

  5. Stop Vibe, then start Vibe to put the new logging level into effect.