Error messages and other information about MTA functioning are written to log files and can be displayed in the POA console. Log files can provide a wealth of information for resolving problems with MTA functioning or message flow. This section covers the following subjects to help you get the most from MTA log files:
The default location of the MTA log files varies by platform:
|
Linux: |
/var/log/novell/groupwise/domain_name.mta |
|
Windows: |
mslocal subfolder in the folder specified by the ‑‑work switch |
You can change the location where the MTA creates its log files, as described in Configuring MTA Log Settings and Switches.
When installing or troubleshooting the MTA, a logging level of Verbose can be useful. However, when the MTA is running smoothly, you can set the logging level down to Normal to conserve disk space occupied by log files.
In the GroupWise Administration Console, browse to and click the MTA.
Click the Log Settings tab.
Set the desired settings for logging.
Log File Path: Browse to and select the folder where you want this MTA to store its log files.
Logging Level: Select the amount of data displayed on the MTA agent console and written to the MTA log file.
Off: Turns off disk logging and sets the logging level for the MTA to its default. Logging information is still displayed on the MTA agent console.
Normal: Displays only the essential information suitable for a smoothly running MTA.
Verbose: Displays the essential information, plus additional information that can be helpful for troubleshooting.
Maximum Log File Age: Specifies how many days to keep MTA log files on disk. The default is 30 days.
Maximum Log Disk Space: Sets the maximum amount of disk space for all MTA log files. When the specified disk space is consumed, the MTA deletes existing log files, starting with the oldest. The default is 100 MB. The maximum allowable setting is 1000 (1 GB).
Corresponding Startup Switches: You can also use the ‑‑log, ‑‑loglevel, ‑‑logdays, ‑‑logmax, and ‑‑logdiskoff switches in the MTA startup file to configure logging.
You can view the contents of the MTA log file in the MTA console.
In the MTA console, click Log Files.
To view a log file, select the log file, and then click View Events.
To select specific types of MTA processing to search for, select one or more of the following types:
Message Logging (MLG): The message logging threads write information into the message log file if message logging has been turned on. See Enabling MTA Message Logging.
Event Logging (LOG): The event logging thread writes information into the event log files that you can search on this page. See Using MTA Log Files.
Dispatcher (DIS): The dispatcher thread starts other MTA threads as needed to meet the demands being put on the MTA at any given time.
Message Transfer (MTP): The message transfer threads communicate with other MTAs and with POAs in the local domain to transfer messages to domains and post offices to which the local MTA is linked by way of TCP/IP.
Routing (RTR): The router threads process messages in the routing queue and prepare them for transfer to the next hop in the link path to their destinations. See Optimizing the Routing Queue.
Admin (ADM): The admin thread updates the domain database (wpdomain.db) whenever administrative information changes.
Scanner (SCA): The scanner threads check for incoming messages when UNC or mapped links are in use.
To search for a specific string, select the log files to search, specify the string in the Events Containing field, and then click View Events.
HINT:To search all log files, select Select All.
To create a new log file, click Cycle Log.
On startup, the MTA records the MTA settings currently in effect. Thereafter, it logs events that take place, including errors.
Because the MTA consists of multiple threads, you might find it useful to retrieve the log file into an editor and sort it on the thread ID that follows the date and time information. Sorting groups all messages together for the same MTA thread.