igniting golden image from server fails

[Don Bertsch_1]

Thanks in advance to all repliers
1)system archive successfully created on ignite server
2)archive recognized on server
3)nfs exported ignite directories
4)bootsys succesfully enabled client
5)installation initiated
-config file prepared
-disks configured
-mini system downloaded
x ./etc/hosts, 486 bytes, 1 tape blocks
x ./etc/services, 10908 bytes, 22 tape blocks
x ./etc/inetsvcs.conf, 15 bytes, 1 tape blocks
x ./etc/nsswitch.conf, 382 bytes, 1 tape blocks
x ./configure3, 450560 bytes, 880 tape blocks
x ./monitor_bpr, 20480 bytes, 40 tape blocks


* Download_mini-system: Complete



* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (HP-UX Core Operating System Archives).
* Fri Oct 31 16:29:35 EST 2003: Starting archive load of the source
(English HP-UX 11.00 CDE - 64 Bit OS).
cat: Cannot open /tmp/ign_configure/archive_nfs/B.11.00_64bitCDE.gz: No such file or directory
* Completed 0 KBytes of archive

[Scot Bean]

Just like the msg says, ignite is looking for your golden image here:

/tmp/ign_configure/archive_nfs/B.11.00_64bitCDE.gz

And not finding it. Seems strange to store something as improtant as a golden image in /tmp.

Double check that the image
- config file
- NFS export path
- actual image location
are all pointing to the same location.

[Steven E. Protter · Accepted solution]

The INDEX file on the Ignite server refers to this file: /tmp/ign_configure/archive_nfs/B.11.00_64bitCDE.gz:

If its not there you stop. If its not on an exported NFS filesystem, you stop.

The file needs to be relocated to a NFS exported filesysetm and the INDEX file needs to be updated on the Ignite server.

instl_adm -T to test the configuration files after a change.

SEP

[Don Bertsch_1]

My system archive was not available. I had put it on a seperate physical disk because it required required a larger PE size and the largefiles option.During testing I invariably unmounted this filesytem, so server couldn't locate during ignition process.I cannot confirm everything is corrected yet. Lan boot process fails from an L-class server for some reason. ???Consequently, I have to reinstall base OS on the L-class target and reinitiate ignite process via bootsys.

[Don Bertsch_1]

I reinstalled client, mounted directory containing system archive on server and reinitiated client install. It failed again with the same error.Is B.11.00_64bitCDE.gz a software source? I only followed directions in manual for creating and installing golden images. It said nothing about software sources.Under "Installing Ignite UX Server" Chapter, manual says...C: Set Up or Update the Software Source Ignite-UX allows many options for installing software on clients. The basic option is to install all software from SD depots on the server. This step describes setting up the software to install on the server.If file is software source, what about all the other software in my system archive, does it have to be loaded as sources too?

[Steven E. Protter]

Please post the output on the ignite server of instl_adm -T

I believe configuration changes are required to fix this.

Wherever the archive is MUST be on an NFS exported filesystem. The configuration files must reflect the archive location.

You may need to swcopy the core OS to the new location.

SEP

[Don Bertsch_1]

Results as follow...(TCI-brutus) /home/dbertsch $ instl_adm -T * Checking file: /opt/ignite/data/Rel_B.11.22/config * Checking file: /opt/ignite/data/Rel_B.11.22/hw_patches_cfg * Checking file: /var/opt/ignite/config.local * Checking file: /opt/ignite/data/Rel_B.10.20/config * Checking file: /opt/ignite/data/Rel_B.10.20/hw_patches_cfg * Checking file: /opt/ignite/data/Rel_B.11.00/config * Checking file: /opt/ignite/data/Rel_B.11.00/hw_patches_cfg * Checking file: /opt/ignite/data/Rel_B.11.11/config * Checking file: /opt/ignite/data/Rel_B.11.11/hw_patches_cfg * Checking file: /var/opt/ignite/data/Rel_B.11.11/tci_dbserv_archive_cfg(TCI-brutus) /home/dbertsch $My configuration files seem Ok. What is the "environments:" field, under the basic tab, about. Reviewing my install, it looks like I selected my golden image in the "configurations:" field and then in the "environments:" field, I chose "English HP-UX 11.00 CDE 64 bit OS". My archive is named tci_dbserv.gz

[Steven E. Protter]

Please post /etc/exports

Output of exportfs -av

ll of the directory the archive is supposed to be in.

Realistically, this is best suited for an Ignite software call, but I've had all these issues before and we should be able to get through this.

SEP

[Don Bertsch_1]

# exportfs -avre-exported /var/opt/ignite/clientsre-exported /var/opt/ignite/archives/Rel_B.11.11 $ ll /var/opt/ignite/archives/Rel_B.11.11/total 3858672-rw-rw-rw- 1 root sys 1983 Oct 30 18:03 make_sys_image.log-rw-rw-rw- 1 root sys 1975627584 Oct 30 18:03 tci_dbserv.gz

[Don Bertsch_1]

I solved issue myself, and here's the scoop. Anybody desiring to install golden images, take heed. Your golden image must appear as Operating Environment entry! My problem related to template file "/opt/ignite/data/examples/core11.cfg" file. The manual says to copy this file, edit and use as archive configuration file.This I did. The manual doesn't tell you though that ignite sees each configuration file in Configurations and sw_sel clauses in each configuration file appear as Operating Environments. It also doesn't say that default file has two default sw_sel clauses.To make a long story... short, I entered the correct information in the wrong place. I entered info for a 64 bit archive in the 32 bit section.When attemping to install golden image, ignite recognized my configuration file, but my golden image didn't appear as an Operating Environment choice.The 64bit default entry (English HP-UX 11.00 CDE - 64 Bit OS) was the only selection. Using ignite for the first time I didn't know anything was wrong, so I ran it. Of course it failed when it couldn't find the corresponding system archive for the selected OE.After moving my edits from 32bit sw_sel clause to 64bit sw_sel clause, everything worked like a charm. DB