2 versions of ignite causing problems

[John J Read]

I am recovering a server using network ignite. However, I am getting a mismatch of versions on server and client. This is odd because the Ignite client is backed up to this ignite server. however, it looks to me liket here are mulitple Ignite boot kernels installed on the server. Would anyone have a recommendation on how to fix this?

Should I swremove Ignite-UX.BOOT-KERNEL or re-install Ignite B.4.2.110?

Here's the error:
ERROR: The version of Ignite-UX on the server you are using (B.4.2.110) is
different than the version of Ignite-UX that the client booted
(B.3.7.96). The versions must match in order to ensure correct
behavior. You may need to update the device you booted from with the
components found on the server.
Continuing the installation with a server version mismatch is likely
to cause indeterminate problems. Do you want to continue anyway? (y/[n]): *
Response was: y

I hit "y" and the ignite continued but then hung at:
Executing user specified script:
"/opt/ignite/data/scripts/os_arch_post_l".
* Running in recovery mode (os_arch_post_l).

I reset the box after waiting 2 hours, then it did not come up properly.



# swlist -l fileset Ignite-UX
# Initializing...
# Contacting target "icovgmp"...
#
# Target: icovgmp:/
#

# Ignite-UX B.4.2.110 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL-IA B.4.2.110 Installation Boot Kernel for IA64 clients
Ignite-UX.BOOT-KERNEL-PA B.4.2.110 Installation Boot Kernel for S700/S800 clients
Ignite-UX.BOOT-SERVICES B.4.2.110 Network Boot Services for System Installations
Ignite-UX.CFG-FILE-11-22 B.4.2.110 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-10-20 B.4.2.110 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-00 B.4.2.110 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILE-SRV-11-11 B.4.2.110 File Archives Used By Clients During HP-UX Install
Ignite-UX.FILESRV-1122IA B.4.2.110 File Archives Used By Clients During HP-UX Install
Ignite-UX.IGNITE B.4.2.110 Graphical Ignite User Interface for Installations
Ignite-UX.IGNT-ENG-A-MAN B.4.2.110 Ignite-UX Manual Pages
Ignite-UX.MGMT-TOOLS B.4.2.110 Tools for Managing Data Files on an Ignition Server
Ignite-UX.OBAM-RUN B.4.2.110 User Interface Libraries Needed for Older Systems
Ignite-UX.RECOVERY B.4.2.110 System disaster recovery tools
# Ignite-UX B.3.7.96 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL B.3.7.96 Installation Boot Kernel for S700/S800 clients

[Jov]

Hi John,

The following fileset seems out of place:

>> # Ignite-UX B.3.7.96 HP-UX System Installation Services
Ignite-UX.BOOT-KERNEL B.3.7.96 Installation Boot Kernel for S700/S800 clients

You have Ignite B.4.2.110 installed, and it seems consistent other than the fileset listed above.


Jov

[Tim Nelson]

You need to get rid of your B.3.7.96 . but.. I do not know what effect this will have trying to recover your client.

Is the ignite version kept in the client archive ? If so it will never match unless you downgrade your Ignite server.

This is still weird though as I assume you booted the client from the Ignite server. The ignite server should have used the newer version to of the installer ??

Look at your clients recover log in /var/opt/ignite/clients/hostname/recovery/latest/recovery.log

What version does it state ?

[John J Read]

I agree with both of those 2 posts above.

My client was backed up to the ignite server I am booting from and it shows the higher version. However, for some reason, It is getting that old version when booting. I see the out of date fileset. I can't really just make changes to the Ignite server due to change control so I am hoping I can tell the client to really use the later version when booting.

Upon closer inspection ( swlist -l file ) the filesets have the same files.




07/09/08 01:30:01 EDT Started /opt/ignite/bin/make_net_recovery. (Wed
Jul 09 01:30:01 EDT 2008)
@(#) Ignite-UX Revision B.4.2.110
@(#) net_recovery (opt) $Revision: 10.601 $


# cd recovery
# swlist -l file Ignite-UX.BOOT-KERNEL-PA
# Initializing...
# Contacting target "icovgmp"...
#
# Target: icovgmp:/
#

# Ignite-UX.BOOT-KERNEL-PA B.4.2.110 Installation Boot Kernel for S700/S800 clients
/
/opt
/opt/ignite
/opt/ignite/boot
/opt/ignite/boot/INSTALL
/opt/ignite/boot/INSTALLFS
/opt/ignite/boot/VINSTALL
/opt/ignite/boot/VINSTALLFS
/opt/ignite/boot/WINSTALL
/opt/ignite/boot/WINSTALLFS
/opt/ignite/boot/boot_lif
/opt/ignite/boot/fs_cfg.def
/opt/ignite/data
/opt/ignite/data/INSTCMDS
/opt/ignite/data/RECCMDS
/sbin
/sbin/ch_hostname.d
# swlist -l file Ignite-UX.BOOT-KERNEL
# Initializing...
# Contacting target "icovgmp"...
#
# Target: icovgmp:/
#

# Ignite-UX.BOOT-KERNEL B.3.7.96 Installation Boot Kernel for S700/S800 clients
/
/opt
/opt/ignite
/opt/ignite/boot
/opt/ignite/boot/INSTALL
/opt/ignite/boot/INSTALLFS
/opt/ignite/boot/VINSTALL
/opt/ignite/boot/VINSTALLFS
/opt/ignite/boot/WINSTALL
/opt/ignite/boot/WINSTALLFS
/opt/ignite/boot/boot_lif
/opt/ignite/boot/fs_cfg.def
/opt/ignite/data
/opt/ignite/data/INSTCMDS
/opt/ignite/data/RECCMDS
/sbin
/sbin/ch_hostname.d
/sbin/ch_hostname.d/ignite_ch_ip

[John J Read]

This doesn't make any sense to me at all but the Ignite recovery completed anyway even though the error still is present. I am going to do further testing, perhaps remove and re-install Ignite until that error goes away.