Problem with Ignite 5.3.35

[Hooi Siew Hoong_1]

All along we had been using Ignite 3.5 with no problem but recently we upgraded the ignite server to the latest version 5.3.35. And we started to see problems with some of the installs. This is how it goes

We have a customised golden image we always use to ignite a new server.


* Loading_software: Begin

* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Backing up LVM configuration for "vg_apps".
* Processing the archive source (HP-UX Core Operating System Archives).
* Mon Jun 07 18:32:38 SST 2004: Starting archive load of the source
(HP-UX 11.11 SOE 64 Bit OS).
* Processed 10% of archive
* Processed 20% of archive
* Processed 30% of archive
* Processed 40% of archive
* Processed 50% of archive
* Processed 60% of archive
pax_iux: opt/ignite/bin : File exists
* Processed 70% of archive
* Processed 80% of archive
* Processed 90% of archive
* Completed 100% of archive
ERROR: Cannot load OS archive (HP-UX 11.11 SOE 64 Bit OS)

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]): *


At this stage, I went to console, type "Y" to get a shell and then type "exit 2" to ignore the error message. And the install just continue.

Response was: y

* Executing user specified script:
"/var/opt/ignite/scripts/pg_os_arch_post_l".
* Running the ioinit command ("/sbin/ioinit -c")
* Creating device files via the insf command.
insf: Installing special files for sdisk instance 0 address 0/0/2/0.6.0
insf: Installing special files for sdisk instance 1 address 0/0/2/1.6.0
insf: Installing special files for btlan instance 0 address 0/0/0/0
insf: Installing special files for pseudo driver dlpi
insf: Installing special files for pseudo driver kepd
insf: Installing special files for pseudo driver framebuf
insf: Installing special files for pseudo driver sad
* Running "/opt/upgrade/bin/tlinstall -v" and correcting transition link
permissions.
* Creating the system file.


Does anyone knows what is wrong here? I have no idea what is the configuration process error is. And thus I do not know what to fix.

Thanks

[Bharat Katkar]

Hi,
I think file "SYSCMDS" file is corrupt or not compatible with the current version. Also check for INSTALL,WINSTALL,INSTCMDS and INSTALLFS files.

This all file are in /opt/ignite/data except INSTALLFS is in /opt/ignite/boot.

Hope that helps.
Regards,

[Hooi Siew Hoong_1]

I am not sure whether I know those files are corrupted or not. I will try to install this new ignite on to another server and compare.

But the error does not appear all the time.

For the above server, I remove the client from the Ignite GUI and did an install again. And this time it work, strange.

[Hooi Siew Hoong_1]

I had checked on all the files, it does not seem to be corrupted.

Does anyone knows what is being executed straight after the image is downloaded?

[Hooi Siew Hoong_1]

This is my suspicion of what is wrong.

I had installed the latest Ignite into the model server to make a golden image. And there is a directory /opt/ignite/bin which was a directory in the older ignite version but now becomes a soft link

lrwxr-xr-x 1 root sys 17 Jun 1 19:12 /opt/ignite/bin -> /opt/ignite/binpa

During the Download_mini-system stage of the Ignite installation, a file

"x ./opt/ignite/bin/print_manifest, 40960 bytes, 80 tape blocks"

was copied to the client. Thus when the golden image was being downloaded into the client, the softlink /opt/ignite/bin could not overwrite the directory created by the minisystem. Therefore resulted in the error message:

"pax_iux: opt/ignite/bin : File exists"

This error somehow raise a flag or change the exit code of the image download routine, that the download was not successful.

So I need to push for a shell, type "exit 2" to ignore the error. And after the installation, create the softlink /opt/ignite/bin manually.


Have anyone experienced the same issue? Or can someone confirm my suspicion? Or are there already a fix for this issue?

[Cheryl Griffin]

Try answering "y" at the prompt and then "exit 2" to ignore to have the install complete.

Remove /opt/ignite/bin and recreate it as a symbolic link to /opt/ignite/binpa or /opt/ignite/binia. Note the PA (risc) or IA (itanium) in that path.
# /usr/bin/ln -s /opt/ignite/binpa /opt/ignite/bin

[Markus Nickola]

I have the same Problem as you described.

I think you're right, that the error comes from the clint from which the golden image is.
I have tested an older golden image with the same configuration settings on the same ignite server and it worked fine.

I'm also interested to get a solution without interacting with the client (exit 2)

[Oved]

Hey,

It happens to me too, but only when I try to clone systems. I make_net_recovery to one system, and then I load the image to another system (different hw).

When I use the image in order to restore the original system it works fine.

1. Does anyone know how to solve it ? (besides to answer "y" and enter "exit 2").
2. Is there a way to answer from the remote GUI ? If not, is there a timeout that causes it to continue ? (I tried a remote GUI recovery and it answered "n" automatically).

Thanx,
Oved

[jmb]

I'm getting this error now also. I've used 5.3.35 for a while, but for some reason haven't run across this until now.

Is this a bug in Ignite? If not, how do we prevent this from happening? Workarounds aren't really solutions...

[Hooi Siew Hoong_1]

Finally, I had found out that there is really indeed a bug within 5.3 and 5.4 version of Ignite. I think this will get fixed in version 6. This issue is specific to image created by make_sys_image, but not make_net_recovery.


The workaround is to add logic to the archive config files in the
sw_source "core archive" stanza. The specific logic is:


is_hppa {
pre_load_cmd += "
if [[ ! -d /opt/ignite/binpa ]]
then
/sbin/mkdir /opt/ignite/binpa
/sbin/chmod 555 /opt/ignite/binpa
/sbin/chown bin:bin /opt/ignite/binpa
/sbin/mv /opt/ignite/bin/print_manifest /opt/ignite/binpa
/usr/bin/rmdir /opt/ignite/bin
/usr/bin/ln -s /opt/ignite/binpa /opt/ignite/bin
fi
"
}

This code will remove the directory /opt/ignite/bin and re-create as a softlink instead before loading your golden image.

Hope this helps guys.

[Oved]

Is there a way to add it automatically in the make_net_recovery procedure ?

(I run make_net_recovery for more than 60 servers, and it is very uncomfortable to add it manually for everyone of them).

Thanx,
Oved