From Wiki-UX.info

Wiki-UX / Why make depot fails with missing config clauses
Jump to: navigation, search

Why make depot fails with missing config clauses

Contents


Problem description

Running a similar make_depots command to build an Ignite-UX SD depot may failed with the following error:

# /opt/ignite/bin/make_depots -s /dev/dsk/c3t2d0 -d /var/optignite/depots/Rel_B.11.31/mcoe_core
.
.
.
*********EXECUTING: /opt/ignite/bin/manage_index -a -f /var/opt/ignite/data/Rel_ B.11.31/core_cfg -c "HP-UX B.11.31 Default"

NOTE: Config clause "HP-UX B.11.31 Default"
        not found in index file: /var/opt/ignite/INDEX.
ERROR:  Couldn't accomplish the requested operation.

ERROR:   The command "/opt/ignite/bin/manage_index -a -f /var/opt/ignite/data/Rel_B.11.31/core_cfg -c "HP-UX B.11.31 Default"" failed.

The most common cause for missing config clauses in the /var/opt/ignite/INDEX is an incomplete Ignite-UX installation. These clause are added into the file when the Ignite-UX bundles required to support network booting are installed on the Ignite-UX server. This frequently occur on system were only the "IUX-Recovery bundle" is installed.

A typical config clause in /var/opt/ignite/INDEX looks like:

# cat /var/opt/ignite/INDEX
.
.
.
}
cfg "HP-UX B.11.31 Default" {
        description "This selection supplies the default system configuration that HP supplies for the B.11.31 release."
        "/opt/ignite/data/Rel_B.11.31/config"
        "/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
        "/var/opt/ignite/config.local"
}
.
.
.

Identify the installed Ignite-UX bundles

Use the swlist -l bundle command | grep -i ignite command.

IUX-Recovery

# swlist -l bundle | grep -i ignite
  IUX-Recovery          C.7.7.98       Ignite-UX network recovery tool subset
  Ignite-UX-11-31       C.7.7.98       HP-UX Installation Utilities for Installing 11.31 Systems

Ignite-UX

# swlist | grep -i ignite
  IGNITE                        C.7.7.98       HP-UX Installation Utilities (Ignite-UX)
  Ignite-UX-11-31               C.7.7.98       HP-UX Installation Utilities for Installing 11.31 Systems

In the previous outputs note that the bundle IGNITE - HP-UX Installation Utilities (Ignite-UX) must be installed instead of the IUX-Recovery - Ignite-UX network recovery tool subset.

Solution

Install the required Ignite-UX components.

Reference

Additional Information

The following is a copy of the INDEX files of a fresh Ignite-UX 7.7.98 installation that support Network Boot on the current HP-UX 11i (v1 - v3) releases.

# /var/opt/ignite/INDEX
# This file is used to define the Ignite-UX configurations
# and to define which config files are associated with each
# configuration.  See the ignite(5), instl_adm(4), and
# manage_index(1M) man pages for details.
#
# NOTE: The manage_index command is used to maintain this file.
#       Comments, logic expressions and formatting changes are not
#       preserved by manage_index.
#
# WARNING: User comments (lines beginning with '#' ), and any user
#          formatting in the body of this file are _not_ preserved
#          when the version of Ignite-UX is updated.
#
cfg "HP-UX B.11.11 Default" {
        description "This selection supplies the default system configuration that HP supplies for the B.11.11 release."
        "/opt/ignite/data/Rel_B.11.11/config"
        "/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
        "/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.23 Default" {
        description "This selection supplies the default system configuration that HP supplies for the B.11.23 release."
        "/opt/ignite/data/Rel_B.11.23/config"
        "/opt/ignite/data/Rel_B.11.23/hw_patches_cfg"
        "/var/opt/ignite/config.local"
}
cfg "HP-UX B.11.31 Default" {
        description "This selection supplies the default system configuration that HP supplies for the B.11.31 release."
        "/opt/ignite/data/Rel_B.11.31/config"
        "/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
        "/var/opt/ignite/config.local"
}

Authors

This page was last modified on 22 July 2011, at 17:27. This page has been accessed 1,400 times.