SPARC and x86 Client Installation Messages and Errors

The following situations and display messages are common to both SPARC and X86 installations.

1. Automated Installation Started Message

2. Auto Install Succeeded Message

3. Automated Installation Failed Message

4. Unable to Contact Valid Package Server Message

5. install_log Reports Missing Package

6. Install Fails With Error 800 Message

1. Automated Installation Started Message

If the client is able to successfully boot and download the install files, then the following displays:

Automated Installation started
   The progress of the Automated Installation can be followed by viewing the
   logfile at /tmp/install_log

You can login as root with the password, “opensolaris,” to monitor the install_log. Once the installation of packages from IPS has started, there may not be updates to this log file for an extended period. You can continue to monitor progress by following the IPS updates in the log file, /var/svc/log/application-auto-installer:default.log.

2. Auto Install Succeeded Message

If you see the message, “Auto install succeeded. You may wish to reboot the system at this time,” then the installation is successful. You can manually reboot., Or, if you have setup automatic reboot in the AI manifest, then the system reboots at this time.

3. Automated Installation Failed Message

If there is a failure during installation, then the following message displays:

Automated Installation failed. Please refer to /tmp/install_log file for
   details
   Apr  9 14:28:09 opensolaris svc.startd[7]: application/auto-installer:default
   failed fatally: transitioned to maintenance (see 'svcs -xv' for details)

4. Unable to Contact Valid Package Server Message

If there is a failure during installation, check the log file, /tmp/install_log. If the AI client could not access the package server for installing packages, you may see the following error messages:

installation will be performed from http://pkg.opensolaris.org (opensolaris.org)
   list of packages to be installed is: 
                entire
                SUNWcsd
                SUNWcs
                babel_install
   pkg: The URL 'http://pkg.opensolaris.org' does not appear to point to a
   valid pkg server.
   Please check the server's address and client's network configuration.
   Additional details:

   Unable to contact valid package server: http://pkg.opensolaris.org/
   Encountered the following error(s):
   Transport errors encountered when trying to contact depot server.
   Reported the following errors:
   Could not retrieve versions from 'opensolaris.org'
   URLError, reason: (8, 'node name or service name not known')
   Unable to initialize the pkg image area at /a

The problem may caused by one of the following reasons:

The pkg_server is down. Try to access the pkg_server and check status.
If you are using DNS, check whether the AI client is setup with DNS:
```
# svcs -a | grep /network/dns/client
```
If the install service is disabled, then the client is not setup with DNS. Check your DHCP server configuration to see whether DNS information is sent with the DHCP offer. If not, add the DNS information to the client's DHCP macro.
If you are not using DNS, add the HTTP proxy information to the AI manifest and try the installation again. See Specifying an HTTP Proxy to Reach an IPS Repository.

5. `install_log` Reports Missing Package

If one of the packages specified in the AI manifest cannot be located in the IPS repositories, then the installer fails before installing any packages on the disk. In the following example, the installer could not find the package, SUNWTestPkg, in the IPS repository. You may see the following error message in the install_log:

<AI Feb 12 20:15:40> installation will be performed from
   http://pkg.opensolaris.org/dev (opensolaris.org)
   <AI Feb 12 20:15:40> list of packages to be installed is:
   <AI Feb 12 20:15:40> entire
                SUNWcsd
                SUNWcs
                babel_install
   <AI Feb 12 20:15:40> SUNWTestPkg
   <OM Feb 12 20:15:40> Set zfs root pool device
   <OM Feb 12 20:15:40> creating zpool
   <OM Feb 12 20:15:43> /usr/sbin/zfs get -Hp -o value available rpool
   <OM Feb 12 20:15:43> Creating swap and dump on ZFS volumes
   <OM Feb 12 20:16:00> TI process completed successfully
   <OM Feb 12 20:16:00> Transfer process initiated
   <TRANSFERMOD Feb 12 20:16:59> IPS initilization finished
   <TRANSFER_MOD Feb 12 20:52:33> pkg missing
   <TRANSFERMOD Feb 12 20:52:33> IPS transfer failed
   <TRANSFERMOD Feb 12 20:52:33> IPS transfer finished
   <OM Feb 12 20:52:33> Transfer failed with error 15
   <AI Feb 12 20:52:42> om_perform_install failed with error 114
   <AI Feb 12 20:52:42> Auto install failed

Check whether the package in question is a valid package. If this package is available on a different IPS repository, add that IPS repository in the AI manifest by using the tag, <ai_pkg_repo_default_authority>.

6. Install Fails With Error 800 Message

The error, “om_perform_install_failed with error 800,” indicates that the installer successfully installed all the packages, but one of installer tasks that prepares the system prior to reboot has failed. Scan the install_log for other failures. Usually when this error is returned, one of Install Completion Tasks (ICTs) has failed.

This error can also indicate that the version of the AI ISO image that is used for the automated installation is different from the version of the OpenSolaris OS being installed. The AI ISO image version must match the OpenSolaris OS version. Check the install_log to see whether there is any message indicating that the version of the AI ISO image is different from the OpenSolaris OS version being installed. If so, change the AI ISO image to correspond to the OpenSolaris version you are trying to install. For instructions, see 5. How do I Install a Particular OpenSolaris Development Build?

For further troubleshooting information, see 2. What if the Client Installation Fails?