C H A P T E R  5

Troubleshooting

This chapter describes how to fix problems that can occur during Suntrademark Studio 10 software installation and uninstallation.


Installing in a Directory That Is Reached by a Symbolic Link

You can install in a directory where part of the path is a symbolic link. An example for installing in a path reached by a symbolic link is if the default directory /opt does not have enough disk space. You need to complete the steps below to prevent the installer from bypassing the symbolic link and installing in an actual filesystem.



Note - For example, if you choose to install in /opt, the following steps show you how to create a symbolic link of /opt/SUNWspro that points to /export/opt_SUNWspro. You can substitute your directory names for the example names.



1. Become a superuser (root) by typing:


% su
Password: root-password

2. Save the existing symbolic link by typing:


# mv /opt/SUNWspro /mytemp

3. Make a new /opt/SUNWspro directory, which will serve as a mount point, by typing:


# mkdir /opt/SUNWspro

4. Mount the target directory so it is available as /opt/SUNWspro by typing:


# mount -F lofs localhost:/export/opt_SUNWspro /opt/SUNWspro

5. Install the product in the /opt directory.

6. Unmount the target directory by typing:


# umount /opt/SUNWspro

7. Remove the empty /opt/SUNWspro mount point by typing:


# rmdir /opt/SUNWspro

8. Restore the symbolic link that you moved in Step 2:


# mv /mytemp /opt/SUNWspro

9. Exit from superuser privileges by typing:


# exit


Product Registry Problems

If you encounter installation or uninstallation problems that involve a corrupt productregistry file, you can sometimes use the Solaristrademark Product Registry Tool to locate and fix the problem.

How Do I Identify and Fix a Failed Installation?

If some packages are not properly installed, you will have problems using the Suntrademark Studio software. For example, if you used the pkgadd command to install the software, you have corrupted the productregistry file. To verify whether all packages are installed properly, follow these instructions:

1. Become a superuser (root) by typing:


% su
Password: root-password

2. Open the Solaris Product Registry tool by typing:


% /usr/bin/prodreg &

3. In the left column of the tool, look at the list under the heading Registered Software.

If a yellow triangle appears adjacent to the product name, then the product is not installed properly.

4. Select the product name and click the Uninstall button.

The Uninstall Failed dialog box opens.

5. Read the message in the box, and then click OK if you want to uninstall the product.

The Interactive Uninstall dialog box opens.

6. Follow the instructions in the subsequent dialog boxes until uninstallation is complete.

Once the uninstallation is complete, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.

How Do I Fix a Failed Uninstallation?

If the uninstaller quits before all the product files are deleted, rerunning the uninstaller will not delete the remaining product files. The product files have been marked as deleted in the productregistry file, so the uninstaller does not remove the remaining files. To completely remove the product files, use the Solaris Product Registry tool, as described in the following procedure:

1. Become a superuser (root) by typing:


% su
Password: root-password

2. Open the Solaris Product Registry tool by typing:


# /usr/bin/prodreg &

3. In the left column of the tool, select all product names containing S1S8 or Sun Studio 10 and click the Uninstall button.

The Uninstall Failed dialog box opens.

4. Read the message in the box, and then click OK if you want to uninstall the product.

The Interactive Uninstall dialog box opens.

5. Follow the instructions in the subsequent dialog boxes until uninstallation is complete.

Once the uninstallation is complete, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.

What Can I Do If the productregistry File Is Corrupted?

If you attempted to fix the failed installation or uninstallation by using the steps in How Do I Identify and Fix a Failed Installation? or How Do I Fix a Failed Uninstallation?, and you are still having problems, you need to delete the corrupted productregistry file from your system. The productregistry file is typically corrupted if you attempt to install or uninstall the software using the pkgadd command or pkgrm command.



Note - Deleting the productregistry file removes the entries for the Sun Studio 10 software and the registry entries for the Solaris Operating System (OS) and other products. Review the steps in How Do I Identify and Fix a Failed Installation? and How Do I Fix a Failed Uninstallation? before proceeding with the steps below.



1. Become a superuser (root) by typing:


% su
Password: root-password

2. Go to the productregistry file by typing the following command at the prompt:


% cd /var/sadm/install

3. Remove the productregistry file by typing:


# rm productregistry

4. Exit from superuser privileges by typing:


# exit

Once you have removed the productregistry file, you can reinstall the product software using the product installer. See Chapter 2 for product installation instructions.


Log Files and Serial Number Files

When you install the Sun Studio software, log files that contain a record of the installation are automatically generated.

How Can I View the Installation Log Files?

To troubleshoot installation problems by viewing the log files, do the following:

1. Go to the logs directory by typing at the prompt:


% cd /var/sadm/install/logs

2. View the file by typing:


% more Sun_Studio_Software_install.A03200125

The file extension varies for each log file.

How Do I Find the Installed Serial Number?

You need the serial number to register the product. You can find the serial number by using the snit tool.

To find and view the contents of the serial.dat file, type the following:


% /install-directory/SUNWspro/bin/snit -d -f /install-directory/SUNWspro/prod/lib/serial.dat

For more information, see the snit(1) man page. If snit is not recognized as a command, set your PATH environment variable, as described in Setting Up Access to the Developer Tools and Man Pages.

What Can I Do If I Lose My Serial Number?

If you lose your serial number and cannot view the contents of the serial.dat file or display your serial number with the snit command, contact customer support by doing one of the following:


Installing With a Remote Display Installation

The following topics include problems that can occur during a remote display installation.

What If the Installation Fails on an NFS-Mounted Filesystem?

If the installation fails on an NFS-mounted filesystem, ensure that you have write permission on that filesystem. You can check for write permission by following the instructions below. See Choosing Local Display or Remote Display of the Installer for more information about installing on an NFS-mounted filesystem.

1. Check for write permission by typing:


% touch /net/remote-system/opt/testfile

If you receive an error message, then you do not have write permission. For example:


% touch /net/harker/opt/testfile
touch: /net/harker/opt/testfile cannot create

2. Choose another installation directory on which you have write permission, or contact your system administrator to change the filesystem permissions.

How Do I Initialize a ToolTalk Software Session During Remote Display Installation?

If the graphical user interface installer stalls during installation, you can initialize a ToolTalktrademark software session by doing the following:

1. Exit from the installer.

2. If you are not currently superuser (root), become a superuser by typing:


% su
Password: root-password

3. Type at the prompt:


# /usr/dt/bin/ttsession -c

4. Ensure that the $DISPLAY is set.

The sections Choosing Local Display or Remote Display of the Installer and Installing to an NFS-mounted Filesystem describe how to set the remote display.

5. Start the installer by typing:


# /cdrom/studio_8_sol_arch/installer

Follow the instructions in Chapter 2 to complete the installation.


What Can I Do If the Batch Installer Stalls?

If you enter an invalid parameter when you start the batch installer, the installer stalls and does not complete the installation. Some common errors include typing an incorrect serial number, including two different directory names, or invoking the installer when you do not have enough disk space.

Follow these steps to restart the batch installer:

1. View the log files for any error messages by typing:


% cd /var/sadm/install/logs

2. To stop the installer, press Control+C.

3. To install the product using the batch installer, see Using the Batch Installer of Chapter 2.