1. Automatically Installing Oracle Solaris 11.4 Systems
  2. Troubleshooting Automated Installations
  3. SPARC and x86 Error Messages
  4. IPS Server Not Available

IPS Server Not Available

The client needs to reach the IPS package repository defined in the AI manifest in order to install Oracle Solaris. If the client cannot access the package repository, the installation fails and the application/auto-installer service transitions to maintenance. The following output is an example of what is displayed on the console: 

15:54:46    Creating IPS image
15:54:46    Error occurred during execution of 'generated-transfer-1341-1' checkpoint.
15:54:47    Failed Checkpoints:
15:54:47
15:54:47        generated-transfer-1341-1
15:54:47
15:54:47    Checkpoint execution error:
15:54:47
15:54:47        Framework error: code: 6 reason: Couldn't resolve host 'pkg.example.com'
15:54:47        URL: 'http://pkg.example.com/solaris/release/versions/0/'.
15:54:47
15:54:47    Automated Installation Failed.  See install log at /system/volatile/install_log
Automated Installation failed
Please refer to the /system/volatile/install_log file for details
Aug 21 15:54:47 line2-v445 svc.startd[8]: application/auto-installer:default failed fatally:
transitioned to maintenance (see 'svcs -xv' for details)
...
SUNW-MSG-ID: SMF-8000-YX, TYPE: defect, VER: 1, SEVERITY: major
EVENT-TIME: Wed Aug 21 15:54:47 UTC 2013
PLATFORM: SUNW,Sun-Fire-V445, CSN: -, HOSTNAME: line2-v445
SOURCE: software-diagnosis, REV: 0.1
EVENT-ID: c8a5b809-ece4-4399-9646-d8c64d78aac7
DESC: A service failed - a start, stop or refresh method failed.
AUTO-RESPONSE: The service has been placed into the maintenance state.
IMPACT: svc:/application/auto-installer:default is unavailable.
REC-ACTION: Run 'svcs -xv svc:/application/auto-installer:default' to determine the generic reason
why the service failed, the location of any logfiles, and a list of other services impacted. Please
refer to the associated reference document at https://support.oracle.com/msg/SMF-8000-YX for the latest service
procedures and policies regarding this diagnosis.

Check the /system/volatile/install_log file for messages similar to the following: 

TransportFailures: Framework error: code: 6 reason: Couldn't resolve host
'pkg.example.com'
URL: 'http://example.com/solaris/versions/0/'
TransportFailures: Framework error: code: 7 reason: Failed connect to
pkg.example.com:80; Connection refused
URL: 'http://example.com/solaris/versions/0/'
TransportFailures: http protocol error: code: 404 reason: Not Found
URL: 'http://example.com/mysolaris/versions/0/'

Depending on which messages you see, try the following possible remedies:

  • Try to reach the package server from the failed client, for example, by using ping.

  • If you are using DNS, check whether DNS is correctly configured on the client. See Check DNS.

  • If you are using a local repository, check whether you have made the repository accessible to all clients. See Chapter 3, Providing Access To Your Repository in Creating Package Repositories in Oracle Solaris 11.4.

  • Make sure the URI in the AI manifest does not have a typographical error.

  • Use a command such as the following command to check whether the package repository is valid:

    $ pkg list -g http://pkg.example.com/solaris/ entire

    You might need to refresh the catalog or rebuild the index.