Error messages and other information about Monitor Application functioning are written to log files. Log files can provide a wealth of information for resolving problems with Monitor Application functioning. Logging is enabled by default.
The default location of the Monitor Application log files is the GroupWise Web application working directory.
You can change the location where the Monitor Application creates its log files, as described in Configuring WebAccess Application Log Settings.
Open the gwmonitor.cfg file in a text editor.
Search to find the Logging Information section.
Adjust the following log settings as needed:
Log.maxSize: Specify the maximum amount of disk space you want to use for Monitor Application log files. If the disk space limit is exceeded, the Monitor Application deletes log files, beginning with the oldest file, until the limit is no longer exceeded. The default disk space is 102400 KB (100 MB).
Log.maxAge: Specify the number of days you want to retain the log files. The Monitor Application retains log files for the specified number of days unless the maximum disk space for the log files is exceeded. The default age is 30 days.
Log.level: There are three log levels:
Normal (default) Displays warnings and errors.
Verbose: Displays the Normal log level information, plus information messages and user requests.
Diagnostic: Displays all possible information. Use Diagnostic only if you are troubleshooting a problem with the Monitor Application.
The Verbose and Diagnostic log levels do not degrade Monitor Application performance, but log files consume more disk space when Verbose or Diagnostic logging is in use.
Save the gwmonitor.cfg file.
For the default location of the Monitor log files, see Section 63.2.1, Locating WebAccess Application Log Files.
When logging is turned on, the Monitor Application creates a new log file each day and each time it is restarted (as part of the Web server startup). Therefore, you find multiple log files in the log file directory. The first four characters represent the date (mmdd). The next three characters identify the Monitor Application (mon). A three-digit extension allows for multiple log files created on the same day. For example, a log file named 0518mon.001 indicates that it is a Monitor Application log file, created on May 18.
Use your text editor of choice to view the Monitor Application log files.