CHAPTER 11

Troubleshooting the
Sun Internet Mail Server




This chapter covers some of the potential issues that you may encounter during the installation of SIMS 4.0, including diagnosing and then properly configuring your DNS setup. It also gives you information about the log file, where installation activities and error messages are recorded.

Configuring the DNS setup
Reading the SIMS installation log files
Rebooting after reinstalling
Configuring the Netscape browser
Missing the command tool
LDAP libraries not being removed
Cleaning up the corrupted quota file


Configuring the DNS Setup

Before installing SIMS 4.0, installation looks up the host name of your local machine. If this host name is not a fully qualified domain name, installation exits. You will then need to correctly configure your DNS setup before installing SIMS, as explained in "Diagnosing DNS," below.


What is a Fully Qualified Domain Name?

Fully Qualified Domain Name (FQDN) is the full name of a system, consisting of its local host name along with its domain name. Recall that a host name is the logical name assigned to a computer. For example, class is a host name and eng.stream.com is an FQDN.

A FQDN should be sufficient to determine a unique Internet address for any host on the Internet. The same naming scheme is also used for some hosts that are not on the Internet, but share the same name-space for electronic mail addressing. A host which does not have a FQDN must be addressed using a bang path.

A bang path is an address for sending e-mail via UUCP that specifies the entire route to the destination computer. It separates each host name with an exclamation point, which is known as a bang. For example, the bang path midearth!shire!eng!jsmith would go to the jsmith user account on the eng host, which is reached by first going to midearth and then shire.


Diagnosing DNS

SIMS 4.0 installation automatically diagnoses the host name to determine whether the name returned is a fully qualified domain name, but somehow cannot be accessed.

The following are the steps that SIMS installation takes:

  1. The procedure makes a function call to gethostbyname(), which in turn uses the file nsswitch.conf to check the host name.
  2. If the lookup results in a fully qualified domain name, the installation proceeds; otherwise, it runs the SIMS DNS lookup utility. This utility directly accesses the Internet Domain Name Server.
  3. The SIMS DNS lookup utility, in turn, uses the file etc/resolv.conf and directly queries the Internet Domain Name Servers.
  4. If the SIMS DNS lookup utility cannot find the DNS name in the system, it displays an error message and exits.
  5. If, however, the SIMS DNS lookup utility finds the DNS name in the system, it further searches to check whether the name is a fully qualified domain name.
  6. If the SIMS DNS lookup utility finds a DNS name that is not a fully qualified name, it displays a message indicating that the Administrator needs to configure the DNS on the machine correctly before installing.
  7. If the SIMS DNS lookup utility concludes that the name it found is a fully qualified domain name, it displays a message indicating that the name is good, but cannot be accessed. It then suggests that you check the file
/etc/nsswitch.conf for the search order for hosts or the /etc/hosts files if this file is being used.

FIGURE 11-1 shows the steps that SIMS 4.0 installation takes to check for a fully qualified domain name.

FIGURE  11-1 DNS Diagnostic Procedure


Configuring Files

Once the SIMS installation determines that the DNS setup you are using is in fact good, the next step for you is to configure your resolv.conf and nsswitch.conf files.

Recall that the order in which gethostbyname() consults the sources DNS, NIS, and /etc/hosts is configured in the file /etc/nsswitch.conf.

This section provides you with the steps that help you configure the order in which the sources are consulted.

  1. Configure the /etc/nsswitch.conf to specify the DNS source and the order in which it is looked up, for example:

hosts: dns files


Note - If you have placed files before dns, make sure that your /etc/hosts files contains fully qualified domain names for all hosts. Also, make sure that the fully qualified domain name for the local machine appears in /etc/nodename and
/etc/hostname.*.
  2. Configure the /etc/resolv.conf file to specify how to access the Internet Domain Name System.

domain <domain-name>
nameserver <name-server-IP-address>

Where,

domain-name specifies a local domain name that is used as the default domain, and

name-server-IP-address specifies the Internet address of one name server to which the resolver should direct any queries.


Note - name-server-IP-server cannot be the same as the IP of the local host name.

Example:

The following is an example of the contents of the /etc/resolv.conf file:

domain sun.com
nameserver 129.155.121
nameserver 129.155.125

The nslookup data for the marketing host name will then be:

nslookup marketing
Name: marketing.eng.sun.com


Reading the SIMS Installation Log Files

SIMS records installation activities in log files located in /var/opt/SUNWmail/log/SIMS_installation_log.n, where n is the date and time stamp of the form YYMMDD.HR:MM. This number is generated automatically. For example, SIMS_installation_log.97112012:40 is the log file for the install which was started at 12:40 on November 20, 1997.


Note - During installation, the log file is created in the /tmp directory. It is then moved to the directory /var/opt/SUNWmail/log after installation is completed. If the installation exits before it is completed, you can check the log file in /tmp.


Rebooting after Reinstalling

If you are reinstalling SIMS 4.0, make sure that you reboot your system after the installation of the new server. If you do not reboot, you may encounter errors while creating new calendar or mail users.

If you cannot create new users, check if you have rebooted the system after you have reinstalled the SIMS server.


Configuring the Netscape Browser

After you installed SIMS or SIMS/HA, you need to configure the Netscape property files by setting the defeat security level to low.

See "Netscape Browser Configuration" on page 70 in Chapter 8, "Post Installation Configurations," for instructions on configuring the Netscape browser.


Missing the Command Tool

The next step after you have selected the installation type and specified configurations for your selection is to run the setup install script. This will invoke the command tool to continue the installation. If, however, this command tool is not available, an error message will be displayed. You may check the path where the command tool should reside or check your operating system setup.


LDAP Libraries Not Being Removed

The uninstall -d command does not remove the SUNWlldap LDAP library packages or any associated patches which is part of Solaris 2.7.


Cleaning Up the Corrupted Quota File

If you are upgrading to SIMS 4.0 from SIMS 3.5, you need to initialize all the user quota files. The purpose for doing this procedure is to clean up the potential by corrupted message store user quota files. See the Sun Internet Mail Server 4.0 Administrator's Guide for instructions on how to set up user quotas.

After you have upgraded to SIMS 4.0, do the following steps:

  1.

# cd /opt/SUNWmail/ims/sbin

Change the directory.

  2. Initialize

# ./iminitquota -a

all the user quota files.

  3.

# ./imquotacheck -v -n

Print a user quota report.

  4. Verify that the information on a user quota report is correct.

TABLE  11-1   User Quota Report Sample
Username
Quota (Byte)
Total (Byte)
% used

u1  

NO LIMIT  

16840  

NA  

u2  

NO LIMIT  

250  

NA  

u3  

NO LIMIT  

500  

NA  

u4  

20000000  

750  

<1%  

u5  

20000000  

14750  

<1%  

u6  

20000000  

3000  

<1%  

u7  

10000000  

515650  

<6%  

u8  

10000000  

2343950  

<24%  

u9  

10000000  

3000  

<1%  

u10  

10000000  

753  

<1%  




Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.