To Collect Required Debug Data for Any Messaging Server Problem

All problems described in this technical note need basic information collected about when the problem occurred and about the system having the problem. Use this task to collect that basic information.

1. Note the day(s) and time(s) the problem occurred.

2. Provide a graphical representation of your deployment. Include all hosts and IP addresses, host names, operating system versions, role they perform, and other important systems such as load balancers, firewalls, and so forth.

3. Note the operating system.

   Solaris OS

   uname -a

   HP-UX

   uname -r

   Linux

   more /etc/redhat-release

   Windows

   C:\Program Files\Common files\Microsoft Shared\MSInfo\msinfo32.exe /report C:\report.txt

4. Note the patch level.

   Solaris OS

   patchadd -p

   HP-UX

   swlist

   Linux

   rpm -qa

   Windows

   Already provided in the C:\report.txt file above.

5. Note the version of Messaging Server.

   Be sure to send the entire screen output of the imsimta version command.

   • Sun Java System Messaging Server (Messaging Server 6):

     UNIX and Linux

     cd server-root/sbin./imsimta version

     Windows

     cd server-root\sbinimsimta.exe version

   • iPlanet Messaging Server (Messaging Server 5):

     UNIX and Linux

     cd server-root/msg-identifier./imsimta version

     Windows

     cd server-root\msg-identifierimsimta.exe version

6. Create a tar file of the Messaging Server configuration directory.

   • Sun Java System Messaging Server (Messaging Server 6):

     UNIX and Linux

     cd server-root/sbin./configutilCreate a tar file of the server-root/config directory.

     Windows

     cd server-root\configconfigutil.exeCreate a tar file of the server-root\config directory.

   • iPlanet Messaging Server (Messaging Server 5):

     UNIX and Linux

     cd server-root/msg-identifier./configutilCreate a tar file of the server-root/msg-identifier/imta/config directory.

     Windows

     cd server-root\msg-identifierconfigutil.exeCreate a tar file of the server-root\msg-identifier\imta\config directory.

   ---

   Note –

   If possible, provide just the relevant extracts of log files for the same time period that show the problem, with sufficient context to see what else was happening during the error occurrence and shortly before. Thus for relatively short log files (for example, MTA channel debug log files), send the entire log file, whereas for long-running hence large log files, an extract might be more appropriate, though be sure to include all the material from the time of the error as well as at least some lead-in logging from before the error apparently occurred.

   However, when questions arise about message structure or content, or about notification or bounced messages, then send an entire sample message, including all the outermost header (not just an excerpt of the message).

   ---