To edit any of the configuration settings in a CMN configuration file:
2 |
For the Mail Connector’s SMTP.log file (only): If you want to enable or disable SMTP logging altogether, find the section <logger name="CMN. SmtpProtocol.logging" ...>, and then: |
3 |
For a Directory Connector or Mail Connector log (only): Find the corresponding section in the open file (section name also appears in the right-hand column above). |
4 |
For any/all component log files: Make any desired changes. Values must be enclosed in double quotation marks and followed by a trailing space and slash character as shown in the field notes below. |
• |
<file value="[PathAndFilename]" />: Location and name of the log file that log4net will generate. The path specification can be absolute (e.g., "C:\log4net\CMN.log") or relative to the installation directory (e.g., ".\log4net\CMN.log"). |
• |
<threshhold value="INFO" />: Scope and level of detail to appear in the logs. A valid value is any of these single words: OFF FATAL ERROR WARN INFO DEBUG ALL |
• |
<rollingStyle value="Size" />: Determines what will trigger log4net’s closing of a current log file and opening of a new one: either a change in calendar date, or a log file reaching a particular size. Parameter value is set to "Size" by default, or change to "Date" for the alternative. |
• |
<maximumFileSize value="10MB" />: Maximum log file size—the size at which log4net will close the current log file and open a new one (applies only if <rollingStyle value="Size" />. |
• |
<maxSizeRollBackups value="25" />: Maximum number of log files to keep—after which log4net deletes the oldest log file to create a new one. |
5 |
Close and Save the configuration file under the same filename. |
NOTE: Note: Any changes to the log42net.config file are immediately applied by the CMN service when the configuration file is saved. |
For more detailed information about the log4net utility and how its log files can be configured, see the log4net Config Examples at the Apache.org web site.
2 |
Navigate to the log configuration file at C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\tools\log42net.config. |
4 |
There are two entries for <threshold value="INFO" />. |
6 |
Delete, rename, or move the current log file at C:\Program Files (x86)\Quest\Coexistence Manager for Notes\Directory Connector\Logs\Sync.log. |
8 |
<!-- Only log the INFO messages, change to DEBUG if you want more
details in the ERROR log. This will have a substantial impact on
<appender-ref ref="LogFileAppender" />
<appender-ref ref="UdpAppender" />
<appender-ref ref="ErrorLogFileAppender" />
<!-- Write to CONSOLE when running console application. -->
<appender-ref ref="ColorConsoleAppender" />
<appender name="LogFileAppender" type="log42net.Appender.RollingFileAppender" >
<file value="..\Logs\Sync.wlog" displayName="Directory Sync Service Main Log" />
<!-- Change this to include more or less information in main log. -->
<datePattern value="yyyyMMdd".wlog"" />
<!-- Change this setting to change the max log size. -->
<maximumFileSize value="10MB" />
<!-- Change this setting to change the max number of logs. -->
<maxSizeRollBackups value="25" />
<!-- Newest files have smaller numbers. -->
<layout type="log42net.Layout.PatternLayout">
<conversionPattern value="%date %-5level %logger [%t] - %message%newline" />
The Open Log File button in the Management Console’s Health screen is enabled only when at least one module has the UdpAppender defined in its log42net.config file. During a new installation, the Log Viewer installer installs a file with the required UdpAppender. During an upgrade, however, the installer does not overwrite the log42net.config file, so the UdpAppender is not present, and this makes the Open Log File button invisible.
For upgrades or installations prior to the current release, the log42net.config file must be modified in each module to enable live log viewing. In the <log4net> root in each module directory, add the following lines:
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center