Novell Cool Solutions

Novell iFolder Debug Logging Enabling and Uses


September 24, 2009 3:35 pm





Enabling Debug logging in Novell iFolder server/client

Novell iFolder provides exhaustive logging and debugging information for the administrator and the end-user to resolve typical configuration issues. Novell iFolder uses the apache log4net framework for logging all information.

Enabling the logging in debug mode is important to get the necessary information to take action for the problem. Based on the configuration the configuration file location and the log file location can be different.

Novell iFolder provides two different logs for the server and a single log for the client. The server administrator gets the “Access log” and the “Running information log”, while the client generates only the “Running information log”.

Simias Access Log

The iFolder access log is named as Simias.access.log as the core of iFolder is called “Simias”. This log is basically a Access control log, which provides information on “who did what on which iFolder”. For example the administrator can find the “User” who created an iFolder named “X” on what date and time. All access operations are logged in this file to enable administrator to get a hold on what information got changed in the system and when and by whom.

Running Information Log

The iFolder information log is named as Simias.log. This log contains the information of the server from the start of the server to current time. This log maintains the life time of the server and all operations that got carried over in the server along with the incoming API calls (Web Service calls). In case of exceptions the log maintains those exceptions along with a stack. It is generally advisable for the administrator or the user to share this log or at least the stack with the Novell support for resolution that cannot be done by the user. This log can be configured to maintain only the information, warning, fatal errors or Debug information. If there is a reproducible issue, then it is always better to set the log level in debug mode and generate the log for Novell support to help in resolving the issue. Same holds good for the client logs as well.

Both the access log and information logs are rolling logs. The rolling and the size can be configured. By default the size is 10MB and the log rolls after 10 iterations. For example, Simias.log will roll as Simias.log.1, Simias.log.2….Simias.log.9.

It is advisable to send all the logs to Novell support, so that the support can trace the life time of the server or client over a period of time to provide a better solution. Remember to zip the logs as these are text content and compression will be higher, so the user can save the transmission time.

Log configuration

For Server

The log configuration file is located at: /<ifolder>/<data>/<area>/<simias>/Simias.log4net

The configuration file is XML based. Following are the important elements to change (if needed beyond default configuration).

For Running Information log

<file value=”/<ifolder>/<data>/<area>/simias/log/Simias.log” />

Change the file value for the desired log file location.

      <maximumFileSize value="10MB" />
      <maxSizeRollBackups value="10" />

Change to suit your server logging needs, default might be insufficient if your server is serving more than 100 users. Set it to 500 MB and 20 backups, so that Novell Support gets sufficient information.

      <level value="INFO" />

Change it if there is an issue with the server and it is reproducible. The new value will be “DEBUG”.

      <level value="DEBUG" />

This can also take values like “WARN”, “FATAL” etc. But switch between “INFO” and “DEBUG”, as “INFO” collects least information(but logs program “Exceptions”). Use “DEBUG” if the log needs to be sent to Novell Support.

The logging levels can also be changed via the iFolder Admin console in the Server Page. Select the server for which the logging has to be configured and change the log levels. A screenshot is shown below.

For Access log

<file value=”/<ifolder>/<data>/<area>/simias/log/Simias.access.log” />

Change the file value for the desired log file location.

      <maximumFileSize value="10MB" />
      <maxSizeRollBackups value="10" />

Changing the above is only if the administrator need to maintain a larger database of access information(For example, more than a week – for > 100 users). Otherwise the defaults are good. This log will roll faster during the initial period, as all the users will be setting up iFolder and uploading data. But after a while, this log size is good enough to capture a decent data for the administrator.

For Client

The log configuration file is located @

For Windows

C:\Documents and Settings\<username>\Local Settings\Application Data\simias\Simias.log4net

For Linux


For Mac


The configuration changes are same as the server log file. On client the Access log is not generated with information even though the access log gets created. The Access log section in the configuration file can be removed if needed.

2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.