1753509 Members
5078 Online
108795 Solutions
New Discussion юеВ

Ignite-UX failure

 
Dwyane Everts_1
Honored Contributor

Ignite-UX failure

All,

I just upgraded my Ignite software to the latest version (5.4.50), and now I'm getting the following error when I try to perform network archives. It seems very generic, and I'm not sure what it is telling me or what the problem is.

======= 08/23/04 09:29:23 EDT Started /opt/ignite/bin/make_net_recovery. (Mon
Aug 23 09:29:23 EDT 2004)
@(#) Ignite-UX Revision B.5.4.50
@(#) net_recovery (opt) $Revision: 10.637 $


* User interface starting.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x00306E0A40BC/recovery/defaults.

NOTE: vgdisplay -v unsuccessful
* User interface completed successfully.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x00306E0A40BC/recovery/defaults.

* Checking Versions of Recovery Tools
NOTE: vgdisplay -v unsuccessful
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
0306E0A40BC/recovery/2004-08-23,09:29/system_cfg
ERROR: A problem has been detected in determining which volume groups and/or
disks are to be part of the recovery archive. This could be due to a
failure of the "list_expander" command. Ensure that the
"/opt/ignite/lbin/list_expander" command returns valid output and
retry.


======= 08/23/04 09:33:23 EDT make_net_recovery completed unsuccessfully

Dwyane
6 REPLIES 6
Pete Randall
Outstanding Contributor

Re: Ignite-UX failure

Dwyane,

The "vgdisplay -v unsuccessful" error would seem to be the root issue here. Can you run the same manually?


Pete

Pete
Simon Hargrave
Honored Contributor

Re: Ignite-UX failure

have you verified the output of vgdisplay -v which it seems to have a problem with?

have you verified the output of /opt/ignite/lbin/list_expander as the output you posted suggests to?
Dwyane Everts_1
Honored Contributor

Re: Ignite-UX failure

Pete,

WOW! Thanks for the extrememly quick response! I looked and looked for this error, and missed it. I must need more coffee.

Yes, I can run this manually.

Dwyane
Dwyane Everts_1
Honored Contributor

Re: Ignite-UX failure

Simon,

Another quick response! Thanks!

I can run both commands manually on both the Ignite server and the remote server in question.

Dwyane
Dwyane Everts_1
Honored Contributor

Re: Ignite-UX failure

How is the command executed from the Ignite server?


vgdisplay -v = passed


vgdisplay -v = passed


remsh remotesvr vgdisplay -v = failed

Dwyane
Dwyane Everts_1
Honored Contributor

Re: Ignite-UX failure

Pete and Simon,

Thanks for the quick responses and help. Apparently, the lvmtab on the remote server was corrupted this past weekend during a maintenance outage. After correcting the lvmtab (re-creating/syncing it), Ignite is now able to read VG00 and conduct a recovery archive.

Thanks again!!!
Dwyane