The following topics help you monitor and control the MTA from the MTA server console:
The MTA server console provides information, status, and message statistics about the MTA to help you assess its current functioning.
Figure 42-1 MTA Server Console
NetWare: |
The MTA server console always displays on the NetWare server console. |
Linux: |
You must use the --show startup switch in order to display the Linux MTA server console. See |
Windows: |
You can suppress the Windows MTA server console by running the Windows MTA as a service. See |
The MTA server console consists of several components:
Do not exit the MTA server console unless you want to stop the MTA.
NetWare: |
At a NetWare server console, you can use Alt+Esc to change screens. In a remote console window, you can use Alt+F1 to select a screen to view. Use these keystrokes to change screens without stopping the MTA. You can use these keystrokes to display the MTA server console if it is not immediately visible on the NetWare console. |
Linux: |
You can minimize the MTA server console, but do not close it unless you want to stop the MTA. |
Windows: |
You can minimize the MTA server console window, but do not close it unless you want to stop the MTA. |
The
box identifies the MTA whose MTA server console you are viewing, which is especially helpful when multiple MTAs are running on the same server.Domain: Displays the name of the domain serviced by this MTA.
Description: Displays the description provided in the Description field in the MTA Information page in ConsoleOne. If multiple administrators work at the server where the MTA runs, the description can include a note about who to contact before stopping the MTA.
Up Time: Displays the length of time the MTA has been running.
MTA Web Console The Status page also displays this information.
The
box displays the current status of the MTA and its backlog.Processing:
Displays a rotating bar when the MTA is running. If the bar is not rotating, the MTA has stopped. For assistance, see Message Transfer Agent Problems
in GroupWise 8 Troubleshooting 2: Solutions to Common Problems.
Domains: Displays the total number of domains the MTA links to and the number that are currently closed.
Post Offices: Displays the total number of post offices in the domain and the number that are currently closed.
Gateways: Displays the total number of gateways in the domain and the number that are currently closed.
If you have closed domains, post offices, or gateways, see MTA Status Box Shows a Closed Location
in Message Transfer Agent Problems
in GroupWise 8 Troubleshooting 2: Solutions to Common Problems for assistance.
MTA Web Console The Status page also displays this information. In addition, you can display detailed information about specific queue contents.
The
box displays the total statistics for the current up time, and 10-minute statistics for all messages the MTA has routed.Routed: Displays the number of messages successfully routed to the domains, post offices, and gateways serviced by the MTA.
Undeliverable:
Displays the number of messages that could not be delivered to a domain, post office, or gateway. For assistance, see MTA Statistics Box Shows Undeliverable Messages
in Message Transfer Agent Problems
in GroupWise 8 Troubleshooting 2: Solutions to Common Problems.
Errors:
Displays the number of errors the MTA encounters while processing messages in its input queues. For assistance, see MTA Statistics Box Shows Errors
n Message Transfer Agent Problems
in GroupWise 8 Troubleshooting 2: Solutions to Common Problems.
MTA Web Console The Status page also displays this information.
The
box displays important messages that could require an administrator’s attention.When you first start the MTA, you typically see a message informing you the MTA configuration has been loaded.
If the MTA encounters a problem that disrupts the flow of GroupWise messages, it displays an error message in the alert box. For assistance, see Message Transfer Agent Error Messages
in GroupWise 8 Troubleshooting 1: Error Messages.
The MTA admin thread updates the domain database (wpdomain.db) when domains, post offices, users, and other types of object information are added, modified, or removed, and repairs it when damage is detected.
To display the
Status box from the MTA server console, click .NetWare Note: Use
Figure 42-2 Admin Status Dialog Box
The following tasks pertain specifically to the MTA admin thread:
MTA Web Console You can display MTA admin thread status on the Configuration page. Under the heading, click . You can also change the admin settings for the current MTA session.
You can perform the following tasks to monitor and control the MTA from the MTA server console at the server where the MTA is running:
You might need to stop and restart the MTA for the following reasons:
Updating the agent software
Troubleshooting message flow problems
Backing up the domain database
Rebuilding the domain database
To stop the MTA from the MTA server console:
Click
to stop the MTA.
NetWare: |
Use Exit (F7). If the MTA does not respond to Exit, you can use the unload command to stop the MTA. However, this might not allow the MTA to shut down gracefully. In addition, the unload command stops all MTAs running on the server. |
Linux: |
If the Linux MTA does not respond to Exit, you can kill the MTA process, as described below, but include the -9 option. |
Windows: |
If the Windows MTA does not respond to Exit, you can close the MTA server console to stop the MTA or use the Task Manager to terminate the MTA task. |
Restart the MTA, as described in the following sections in the GroupWise 8 Installation Guide:
To stop the Linux MTA when it is running in the background as a daemon and you started it using the grpwise script:
Make sure you are logged in as root.
Change to the
directory.Enter the following command:
./grpwise stop
Use the following command to verify that the MTA has stopped.
./grpwise status
To stop the Linux MTA when it is running in the background as a daemon and you started it manually (not using the grpwise script):
Make sure you are logged in as root.
Determine the process IDs (PIDs) of the MTA:
ps -eaf | grep gwmta
The PIDs for all gwmta processes are listed.
You can also obtain this information from the Environment page of the MTA Web console.
Kill the first MTA process listed:
Syntax: kill PID
Example: kill 1483
It might take a few seconds for all MTA processes to terminate.
Use the ps command to verify that the MTA has stopped.
ps -eaf | grep gwmta
Restarting the MTA from the MTA server console causes it to reread the configuration information provided in ConsoleOne. However, the MTA does not reread its startup file when you restart it from the MTA server console.
At the server where the MTA is running, display the MTA server console.
Click
to restart the MTA.NetWare Note: Use
.If you want the MTA to reread its startup file, you must stop it, then restart it.
MTA Web Console You can restart the MTA from the Status page. Click in the upper right corner of the page.
You can cause the MTA to stop processing messages for a location without stopping the MTA completely. For example, you could suspend message processing for a post office while backing up the post office.
To suspend the MTA for a location:
At the server where the MTA is running, display the MTA server console.
Click
.Click the location (or multiple locations) to suspend, then click
.NetWare Note: Use
. Select the location, then click .Routing of all messages to and from the location remains suspended until you resume processing.
To resume the MTA for a location:
At the server where the MTA is running, display the MTA server console.
Click
Click the location (or multiple locations) to resume, then click
.NetWare Note: Use
. Select the location, then click Resume.MTA Web Console You can suspend and resume processing for a specific location on the Links page. Select one or more locations, then click Suspend or Resume as needed.
You can cause the MTA to stop updating the domain database (wpdomain.db) without stopping the MTA completely. For example, you could suspend the MTA admin thread while backing up the domain database.
To suspend the MTA admin thread:
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.The MTA admin thread no longer accesses the domain database until you resume processing.
To resume the MTA admin thread:
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
MTA Web Console You can suspend and resume the MTA admin thread from the Configuration page. Under the General Settings heading, click .
It is important to keep the MTA software up-to-date. You can display the date of the MTA software from the MTA server console.
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: To check the date of the MTA NLM, you can list the gwmta.nlm file in the agent installation directory (typically, the sys:\system directory) or use the modules gwmta.nlm command at the server console prompt.
MTA Web Console You also check the MTA software date on the Environment page.
You can list the current configuration settings of the MTA at the MTA server console.
To display the current MTA settings:
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
to check the MTA settings recorded at the top of the log file.For information about the MTA settings, see Section 44.0, Using MTA Startup Switches.
MTA Web Console You check the current MTA settings on the Configuration page.
The MTA server console displays essential information about the functioning of the MTA. More detailed information is also available.
To display detailed MTA configuration information:
At the server where the MTA is running, display the MTA server console.
Click
to display a list of the locations to which the MTA is connected.NetWare Note: Use
.The following information is provided:
Location Name: Displays the name of the location serviced by the MTA.
Location Type: Indicates whether the location is a domain, post office, or gateway.
Connection Status: Indicates whether the MTA has been successful in locating and opening the database in the location.
Open: The MTA can access the database or communicate with the agent at the location.
Closed:
The MTA cannot access the database or communicate with the agent at the location. For assistance, see MTA Configuration Status Isn’t Open
in Message Transfer Agent Problems
in GroupWise 8 Troubleshooting 2: Solutions to Common Problems.
Suspended: The MTA is not processing messages for the location because it has been suspended. See Suspending/Resuming MTA Processing for a Location.
Open Pending: Post offices in the domain are in the process of opening and the MTA is clearing its holding queues. After this is accomplished, the MTA begins processing current messages and the status changes to Open.
Home: Displays the full path to the database that the MTA services in the listed location. For a TCP/IP connection, it displays the IP address of the server that the MTA connects to in order to service the database.
Select a location, then click
to display the above information plus the following additional details:Hold: Displays the full path to the location of the mslocal directory structure used by the MTA to hold messages for closed locations.
Pull: Displays the transfer pull directory, if any. See Section 41.3.3, Using a Transfer Pull Configuration.
Version: Provides the version (8.0/7.0/6.x/5.x/4.x) of the database at the location.
Last Closed/Opened: Provides the date and time when the location was last closed and opened.
Last Closure Reason:
Indicates why a closed location is closed. To look up last closure reasons, see Message Transfer Agent Error Messages
in GroupWise 8 Troubleshooting 1: Error Messages.
Messages Written/Read: Provides statistics about throughput since the MTA was last started.
Applications: Displays the programs the MTA can deliver messages to. Depending on the configuration of your GroupWise system, you might see GroupWise agents or GroupWise 4.1 servers listed.
TCP/IP: Lists the IP port the MTA listens on.
MTA Web Console You can check the current MTA status on the Links page at the MTA Web console. Click a direct link to view its message queues.
You can monitor the live remote connections the MTA is servicing for Remote client users. For information about live remote processing, see Section 41.2.2, Enabling Live Remote.
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
The status information lists the GroupWise Remote client users who are connected to the MTA, along with the post offices and domains the MTA communicates with.
Status information for the MTA admin thread is displayed in a separate dialog box, rather than on the main MTA server console.
To display MTA admin thread status information:
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.The following status information is displayed:
Admin Message Box The Admin Message box provides the following information about the workload of the MTA admin thread:
Completed: Number of administrative message successfully processed.
Errors: Number of administrative messages not processed because of errors.
In Queue: Number of administrative messages waiting in the queue to be processed.
Send Admin Mail: Select this option to send a message to the administrator whenever a critical error occurs. See Section 42.7, Notifying the Domain Administrator.
Admin Database Box The
box provides the following information about the domain database:Status: Displays one of the following statuses:
Normal: The MTA admin thread is able to access the domain database normally.
Recovering: The MTA admin thread is recovering the domain database.
DB Error: The MTA admin thread has detected a critical database error. The domain database (wpdomain.db) cannot be recovered. Rebuild the domain database in ConsoleOne. See Section 26.3, Rebuilding Domain or Post Office Databases.
The MTA admin thread does not process any more administrative messages until the database status has returned to Normal.
Unknown: The MTA admin thread cannot determine the status of the domain database. Exit the MTA, then restart it, checking for errors on startup.
DB Sort Language: Displays the language code for the language that determines the sort order of lists displayed in ConsoleOne and the GroupWise Address Book.
Recovery Count: Displays the number of recoveries performed on the domain database for the current MTA session.
Admin Thread Box The
box provides the following information about the MTA admin thread:Status: Displays one of the following statuses:
Running: The MTA admin thread is active.
Suspended: The MTA admin thread is not processing administrative messages.
Starting: The MTA admin thread is initializing.
Terminated: The MTA admin thread is not running.
MTA Web Console You can display MTA admin thread status from the Configuration page. Under the heading, click Admin Task Processing.
The MTA admin thread can recover the domain database (wpdomain.db) when it detects a problem.
To enable/disable automatic domain database recovery:
At the server where the MTA is running, display the MTA server console.
Click
to toggle this feature on or off for the current MTA session.NetWare Note: Use Options (F10) > Admin Status > Automatic Recovery.
To recover the domain database immediately:
At the server where the MTA is running, display the MTA server console.
Click Configuration > Admin Status > Perform DB Recovery.
NetWare Note: Use
.For additional database repair procedures, see Section 26.0, Maintaining Domain and Post Office Databases.
MTA Web Console You can recover the post office database from the Configuration page. Under the heading, click . Select or as needed.
You can configure the MTA to perform Novell eDirectory user synchronization at regular intervals. See Section 41.4.1, Using eDirectory User Synchronization. You can also force eDirectory user synchronization to start immediately from the NetWare MTA server console.
To start eDirectory user synchronization manually:
At the server where the NetWare MTA is running, display the MTA server console.
Press F4.
MTA Web Console You can see when the next eDirectory user synchronization even will occur at the bottom of the Configuration page.
The MTA displays only the most urgent messages in the alert box. Additional information is written to the MTA log file. The amount of information depends on the current log settings for the MTA. See Section 42.3, Using MTA Log Files.
The information automatically scrolls up the screen as additional information is written. You can stop the automatic scrolling so you can manually scroll back through earlier information.
To browse the current MTA log file and control scrolling:
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.Deselect
to manually scroll back through parts of the log that have already scrolled out of the box.Click
to stop the MTA from logging information to the active log box.Click
when you want the MTA to resume logging information to the active log box.For explanations of messages in the MTA log file, see Message Transfer Agent Error Messages
in GroupWise 8 Troubleshooting 1: Error Messages.
MTA Web Console You can browse and search MTA log files on the Log Files page.
Reviewing log files is an important way to monitor the functioning of the MTA.
At the server where the MTA is running, display the MTA server console.
Click
Select a log file, then click
.NetWare Note: Use
.For explanations of messages in the MTA log file, see Message Transfer Agent Error Messages
in GroupWise 8 Troubleshooting 1: Error Messages.
MTA Web Console You can view and search MTA log files on the Log Files page.
You can have the MTA start a new log file as needed.
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.Default log settings are established when you start the MTA. However, they can be adjusted for the current MTA session from the MTA server console.
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.Adjust the values as needed for the current MTA session.
See Section 42.3, Using MTA Log Files.
MTA Web Console You can adjust MTA log settings from the Configuration page. Click the heading.
You can change the configuration of the MTA by editing the MTA startup file from the MTA server console.
At the server where the MTA is running, display the MTA server console.
Click
.NetWare Note: Use
.Make the necessary changes, then save and exit the startup file.
Stop and restart the MTA.
Click Help on the menu bar for information about the MTA server console. Click the
button in any dialog box for additional information.NetWare Note: Press F1 for information in any dialog box or menu.