Sun Java System Messaging Server 6.3 Administration Guide

26.2.5 Check the Log Files

If MTA processing jobs run properly but messages stay in the message queue directory, you can examine the log files to see what is happening. All MTA log files are created in the directory /msg-svr-base/log. Log file name formats for various MTA processing jobs are shown in Table 26–1.

Table 26–1 MTA Log Files

File Name  

Log File Contents  

channel_master.log-uniqueid

Output of master program (usually client) for channel.

channel_slave.log-uniqueid

Output of slave program (usually server) for channel.

dispatcher.log-uniqueid

Dispatcher debugging. This log is created regardless if the Dispatcher DEBUG option is set. However, to get detailed debugging information, you should set the DEBUG option to a non-zero value.

imta

ims-ms channel error messages when there is a problem in delivery.

job_controller.log-uniqueid

Job controller logging. This log is created regardless if the Job Controller DEBUG option is set. However, to get detailed debugging information, you should set the DEBUG option to a non-zero value.

tcp_smtp_server.log-uniqueid

Debugging for the tcp_smtp_server. The information in this log is specific to the server, not to messages.

return.log-uniqueid

Debug output for the periodic MTA message bouncer job; this log file is created if the return_debug option is used in the option.dat


Note –

Each log file is created with a unique ID (uniqueid) to avoid overwriting an earlier log created by the same channel. To find a specific log file, you can use the imsimta view utility. You can also purge older log files by using the imsimta purge command. Note, however, that by default this command is run on a regular basis (see 4.6.2 Pre-defined Automatic Tasks). For more information, see the MTA command-line utilities chapter in theimsimta purge in Sun Java System Messaging Server 6.3 Administration Reference.


The channel_master.log-uniqueid and channel_slave.log-uniqueid log files will be created in any of the following situations:

For more information on debugging channel master and slave programs, see the Sun Java System Messaging Server Administration Reference.