Log file behavior in IDM

  • 3756689
  • 30-Oct-2006
  • 26-Apr-2012

Environment

Novell Identity Manager Nsure Identity Manager 2.0
Novell Identity Manager Identity Manager 3.0

Situation

IDM log files roll before reaching the maximum specified size

Resolution

This is working as designed. When you do not limit the size of the IDM logs, you will find the entire log contained in one file. When you restrict the log file size, IDM will split the log into 10 files that are each 1/10th of the total of the specified maximum.

For example, If you specify a log limit of 100 MB, IDM will create xxxx_01.log. When that file reaches a size of 10 MB, IDM will begin logging to xxxx_02.log and so on up to xxxx_10.log. When xxxx_10.log reaches 10 MB, IDM will then overwrite xxxx_01.log and continue the process. The total amount of disk space will never exceed the total amount specified. (Please see note below on default Remote Loader log file naming)

This functionality insures the ability to look back through a trace. If IDM allowed a single log file to grow to the maximum size before overwriting it, information written to the log just prior to reaching the maximum size would be overwritten and lost.

Additional Information

The Remote Loader trace file name by default (you can change it) is the name of the remote loader instance followed by a'-trace.log'. If the file is not limited, then the filename is the same but an '_x' is added at the end. x is the number from 1 to 10 of the trace file.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.