Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 35

MTA Shuts Down Unexpectedly
Problem: The MTA has been running smoothly, but stops unexpectedly.
Action: If the MTA agent console is still displayed, exit it. If the normal exit procedure
does not work, use the system procedure for terminating a program.
• If you are using the NetWare MTA, use the NetWare unload command. If
• If you are using the Linux MTA, kill the first MTA process. You might
• If you are using the Windows MTA, close the MTA window.
Action: After the MTA agent console is no longer displayed, restart the MTA as you
normally would. See
Agent" in the
Action: If the MTA shuts down again, exit it again, reboot the server, then start the
MTA again.
Action: Set the MTA log level to Verbose for troubleshooting. See
Files" in
Possible Cause: Occasionally, a badly damaged message file can cause the MTA to shut down.
Action: Check the contents of the MTA input queues in the domain and post offices.
For the locations of the MTA input queues, see
Directories" in
Structure.
Move the message files out of the priority subdirectories of each input queue,
start the MTA, then copy the message files back in groups, watching the MTA
carefully to see if it shuts down on a particular message file. If it does, delete
the problem message file so normal processing can resume.
Possible Cause: Occasionally, a damaged domain database (wpdomain.db) can cause the
MTA to shut down.
Action: In ConsoleOne, perform maintenance to correct any problems with the domain
database. See
"Databases" in the
Possible Cause: Network connections are unstable.
Action: Make sure the connections between the server where the MTA is running and
the servers where the domain database (wpdomain.db) and post office
database (wphost.db) are located are stable. Repeatedly losing connections
to servers can cause damage to databases.
Possible Cause: The MTA is encountering a problem with one specific aspect of its
functioning.
Action: MTA startup switches are available to disable specific MTA functions while
allowing other functions to continue normally. For example, the /noada switch
disables the MTA admin thread. If a specific MTA function is causing the
you have other MTAs running on the same server, you should exit them
before using the unload command. The unload command unloads all
MTAs running on the same server and might not enable them to terminate
gracefully.
need to use kill -9.
"Installing and Starting the
GroupWise 7 Administration
"Message Transfer Agent" in the
GroupWise 7 Troubleshooting 3: Message Flow and Directory
"Maintaining Domain and Post Office
GroupWise 7 Administration
MTA" in "Message Transfer
Guide.
"Using MTA Log
GroupWise 7 Administration
"Message Transfer/Storage
Databases" in
Guide.
Message Transfer Agent Problems
Guide.
35