Sun Studio 12 Installation Reference Guide

Chapter 3 Troubleshooting

This chapter describes how to fix problems that can occur during Sun Studio 12 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.

Preventing the Installer from Bypassing the Symbolic Link

Become a superuser (root) by typing:
su Password: root-password

Save the existing symbolic link by typing:
mv /opt/SUNWspro /mytemp

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

Mount the target directory so it is available as /opt/SUNWspro by typing:
mount -F lofs localhost:/export/opt_SUNWspro /opt/SUNWspro

Install the product in the /opt directory.

Unmount the target directory by typing:
umount /opt/SUNWspro

Remove the empty /opt/SUNWspro mount point by typing:
rmdir /opt/SUNWspro

Restore the symbolic link that you moved in step 2:
mv /mytemp /opt/SUNWspro

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 Solaris^TM Product Registry Tool to locate and fix the problem.

Identifying and Fixing a Failed Installation

If some packages are not properly installed, you will have problems using the Sun 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.

Verifying Whether All Packages are Installed Properly

Become a superuser (root) by typing:
su Password: root-password

Open the Solaris Product Registry tool by typing:
/usr/bin/prodreg &

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.

Select the product name and click the Uninstall button. The Uninstall Failed dialog box opens.

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

The Interactive Uninstall dialog box opens.

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 the Sun Studio 12 Quick Installation guide for product installation instructions.

Exit from superuser privileges by typing:
exit

Fixing 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:

Removing the Product Files with the Solaris Product Registry Tool

Become a superuser (root) by typing:
su Password: root-password

Open the Solaris Product Registry tool by typing:
/usr/bin/prodreg &

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

The Uninstall Failed dialog box opens.

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

The Interactive Uninstall dialog box opens.

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.

Exit from superuser privileges by typing:
exit

What To Do If the `productregistry` File Is Corrupted

If you attempted to fix the failed installation or uninstallation by using the steps in “Identifying and Fix a Failed Installation" or “Fixing 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 12 software and the registry entries for the Solaris Operating System (OS) and other products. Review the steps in “Identifying and Fix a Failed Installation" or “Fixing a Failed Uninstallation” before proceeding with the steps below.

Deleting a Corrupted Product Registry File

Become a superuser (root) by typing:
su Password: root-password

Go to the productregistry file by typing:
cd /var/sadm/install

Remove the productregistry file by typing:
rm productregistry

Exit from superuser privileges by typing:
exit

Viewing the Installation Log Files

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

Troubleshooting Installation Problems By Viewing the Log File

Go to the logs directory by typing:
cd /var/sadm/install/logs

View the file by typing:
more Sun_Studio_Software_install.A03200125
The file extension is different for each log file.

Installing With a Remote Display

The following problems can occur during a remote display installation.

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 these instructions. See "Choosing Local Display or Remote Display of the Installer" in the Sun Studio 12 Quick Installation guide for more information about installing on an NFS-mounted filesystem.

Checking for Write Permission

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

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

Initializing a ToolTalk Software Session During Remote Display Installation

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

Initializing a ToolTalk Session

Exit from the installer.

If you are not currently superuser (root), become a superuser by typing:
su Password: root-password

Start the session by typing:
/usr/dt/bin/ttsession -c

Ensure that the DISPLAY environment variable is set. The section Choosing Local or Remote Display of the Installer in Sun Studio 12 Quick Installation describes how to set the remote display.

Start the installer by typing:
./installer

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 are including two different directory names or invoking the installer when you do not have enough disk space.

Restarting the Batch Installer

View the log files for any error messages by typing:
cd /var/sadm/install/logs

To stop the installer, press Ctrl+C.

To install the product using the batch installer, see Sun Studio 12 Quick Installation.