Capturing iFolder 3.7 Logging information

  • 7002837
  • 26-Mar-2009
  • 27-Apr-2012

Environment

Novell iFolder 3.7
Novell Open Enterprise Server 2 (OES 2) SP1

Situation

Simias and Simias Access Logs can be helpful in troubleshooting iFolder 3.7 problems.  This document describes how to configure iFolder for debug logging, and how to capture the logs.

Resolution

When iFolder 3.7 is first configured, the iFolder data-store location is defined.  The default location of this file is /var/simias/data/simias.  Changes in this document will be made to the Simias.log4net file found in iFolder data-store directory (i.e. /var/simias/data/simias/Simias.log4net)
 
To enable debug logging, complete the following steps:
1.  Stop iFolder by issuing the following 'rcapache2 stop' command.
2.  Next, edit the Simias.log4net file in the data-store directory and modify the two 'level value="INFO"' entries to "DEBUG".  The resulting two entries should look like this:
 
<level value="DEBUG" />
 
3.  Change directories into the log directory below the data-store directory (i.e. cd /var/simias/data/simias/log) and rename both the Simias.log and Simias.access.log files. 
4.  Start ifolder and apache again with the rcapache2 start command
 
Once the iFolder error condition occurs stop the ifolder server (if possible) with the 'rcapache2 stop' command and capture both the Simias.log and Simias.access.log file for troubleshooting.  NOTE:  If it is NOT possible to stop the iFolder server, the logs will still contain the needed information, but it may be necessary to do extra digging in the log files to find the problem.
 
For best server results, do NOT leave the iFolder logging in debug mode, after the logs have been captured, undo the changes to the Simias.log4net file and restart the iFolder server.