Problem adding a Client

[Jose Javier Sianes Ruiz]

I'm newbie in IUX. Reading PDF document and makenetrec.txt docfile previuslly cant find a solution. The problem is I can not add a new machine. When I try it like explained on documents (Add New Client for Recovery ...) I get the response error displayed on attached JPG file. Also, in client swinstall.log file I find this:

======= 02/09/05 12:00:08 MET BEGIN swinstall SESSION
(non-interactive) (jobid=clientIUX-0074)

* Session started for user "root@clientIUX".

* Beginning Selection
* Target connection succeeded for "clientIUX:/".
ERROR: There is currently no depot software on host "serverIUX" at
location "/var/opt/ignite/depots/recovery_cmds". Make sure
that an absolute pathname is specified for location (beginning
with "/").
* Source connection failed for
"serverIUX:/var/opt/ignite/depots/recovery_cmds".
WARNING: More information may be found in the daemon logfile on this
target (default location is serverIUX:/var/adm/sw/swagentd.log).
* Selection had errors.



======= 02/09/05 12:00:23 MET END swinstall SESSION (non-interactive)
(jobid=clientIUX-0074)

And looking in /var/adm/sw/swagentd.log ServerIUX file:

ERROR: Failed to start source agent on
"/var/opt/ignite/depots/recovery_cmds" for
root@clientIUX
"/var/opt/ignite/depots/recovery_cmds" is not a valid depot.
02/09/05 12:00:22 MET

In serverIUX /var/opt/ignite/depots/recovery_cmds is an empty directory.

Here is IgniteUX version installed on HP-UX 11i client and server:

root@serverIUX:/var/opt/ignite/logs> swlist |grep -i ignite
B5725AA C.6.0.109 HP-UX Installation Utilities (Ignite-UX)
Ignite-UX-11-11 C.6.0.109 HP-UX Installation Utilities for Installing 11.11 Systems

Can anyone help me?

[Jose Javier Sianes Ruiz]

Aditionally, if I execute /opt/ignite/lbin/pkg_rec_depot in IgniteUX server I get this message:

root@serverIUX:/var/opt/ignite/logs> /opt/ignite/lbin/pkg_rec_depot
ERROR: The expected depot or root does not exist at
"/var/opt/ignite/depots/recovery_cmds".
ERROR: There is currently no depot software on host "serverIUX" at
location "/var/opt/ignite/depots/recovery_cmds". Make sure
that an absolute pathname is specified for location (beginning
with "/").
* Generating the product specification file.
* Removing old depot: /var/opt/ignite/depots/recovery_cmds

======= 02/09/05 13:13:14 MET BEGIN swreg SESSION (non-interactive)

* Session started for user "root@serverIUX".

* Beginning Selection
* Targets: serverIUX
* Objects: /var/opt/ignite/depots/recovery_cmds
ERROR: "serverIUX:/var/opt/ignite/depots/recovery_cmds": This depot
you are trying to unregister is not registered.
ERROR: More information may be found in the daemon logfile on this
target (default location is serverIUX:/var/adm/sw/swagentd.log).
* Selection had errors.



======= 02/09/05 13:13:14 MET END swreg SESSION (non-interactive)

* Creating depot: /var/opt/ignite/depots/recovery_cmds

======= 02/09/05 13:13:15 MET BEGIN swpackage SESSION

* Session started for user "root@serverIUX".

* Source: serverIUX:/var/tmp/rec_psf.13867
* Target: serverIUX:/var/opt/ignite/depots/recovery_cmds
* Software selections:
*


* Beginning Selection Phase.
* Reading the Product Specification File (PSF)
"/var/tmp/rec_psf.13867".
* Reading the product "Ignite-UX" at line 5.
* Reading the fileset "BOOT-COMMON-PA" at line 16.
* Reading the fileset "BOOT-KRN-11-11" at line 42.
* Reading the fileset "BOOT-SERVICES" at line 77.
* Reading the fileset "FILE-SRV-11-11" at line 104.
* Reading the fileset "IGNITE" at line 130.
ERROR: Cannot access the source file
"/opt/ignite/mx/icons/iux_console.l.gif": No such file or
directory (2).
ERROR: Invalid definition for the fileset "IGNITE", beginning at line
129. Details described above. The error(s) must be corrected
before the parsing can continue.
ERROR: Invalid definition for the product "Ignite-UX", beginning at
line 5. Details described above. The error(s) must be
corrected before the parsing can continue.

======= 02/09/05 13:13:20 MET END swpackage SESSION

swpackage command failed - see errors above for details

[Eric Antunes]

Hi Jose,

See if you really have all you need on the client side (same version and IUX-Recovery:

#swlist |grep -i ignite

Best Regards,

Eric Antunes

[Jose Javier Sianes Ruiz]

It looks like it fails in a internal lssf command, no idea why:


root@clientIUX:/opt> make_net_recovery -s serverIUX -a serverIUX:/var/opt/ignite/recovery/archives/clientIUX -x inc_entire=vg00
* Creating NFS mount directories for configuration files.

======= 02/10/05 08:44:16 MET Started make_net_recovery. (Thu Feb 10 08:44:16
MET 2005)
@(#) Ignite-UX Revision C.6.0.109
@(#) net_recovery (opt) $Revision: 10.655 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Recovery Tools
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
80009F7A4F2/recovery/2005-02-10,08:44/system_cfg vg00
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk
ERROR: /opt/ignite/bin/save_config failed

======= 02/10/05 08:44:36 MET make_net_recovery completed unsuccessfully

[Henk Geurts]

Jose
are all devicefiles present on the client?

run
#insf -e

and then try the ignite backup again...

regards.
Henk

[Jose Javier Sianes Ruiz]

After executing 'insf -e' nothing change.

[Jose Javier Sianes Ruiz]

Problems seems to be in save_config , if I try this its fails:

root@clientIUX:/opt> /opt/ignite/bin/save_config -f config_test_file vg00
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk


All disk hardware is claimed, only one ERRO on an ISA device:

ba 2 20/5 eisa CLAIMED BUS_NEXUS EISA Bus Adapter
unknown -1 20/5/1 ERROR UNKNOWN EISA card
lan 1 20/5/2 btlan0 CLAIMED INTERFACE EISA card INP0500

[Eric Antunes]

José,

Check this similar issue in this thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=262807

A good start is to see if you can do a vgdisplay:

#vgdisplay -v vg00

Best Regards,

Eric Antunes