topic Re: Ignite fails with error in Operating System - HP-UX

Ignite fails with error

sen_ux — Mon, 02 Nov 2009 19:23:48 GMT

make_net_recovery fails with below error.
ERROR: The list_expander command failed. This could be due to a problem with
parsing /etc/fstab or /etc/mnttab file - see messages above.

Ignite version - C.7.1.93
Ignite server - C.7.1.93
OS - B.11.00
Model - N4000

Re: Ignite fails with error

Torsten. — Mon, 02 Nov 2009 19:26:35 GMT

>> see messages above.

Did you do this?

Re: Ignite fails with error

sen_ux — Mon, 02 Nov 2009 20:29:48 GMT

Colud not find anything usefull. FInd below.

======= 11/02/09 20:13:25 MET Started /opt/ignite/bin/make_net_recovery. (Mon
Nov 02 20:13:25 MET 2009)
@(#)Ignite-UX Revision C.7.1.93
@(#)ignite/net_recovery (opt) $Revision: 10.862 $ $Date: 2006/11/07
22:27:51 $

* Testing for necessary pax patch.
* Recovery Archive Description = Recovery Archive

* Recovery Archive Location = ignite.server.com:/var/opt/i
gnite/recovery/archives/client

* Number of Archives to Save = 2

* Pax type = tar

** 0 - The Volume Group or Filesystem is Not included in the
System Recovery Archive
** 1 - The Volume Group or Filesystem is Partially included in the
System Recovery Archive
** 2 - The Volume Group or Filesystem is Fully included in the
System Recovery Archive

* Checking Versions of Recovery Tools
ERROR: The list_expander command failed. This could be due to a problem with
parsing /etc/fstab or /etc/mnttab file - see messages above.

Re: Ignite fails with error

Michael Steele_2 — Mon, 02 Nov 2009 21:19:48 GMT

Hi

What happens when you run this command:

/opt/ignite/lbin/list_expander -l -f
/var/opt/ignite/clients/hostname/recovery/fhist

...on another archive as well as the failed one?

Its easy enough to check /etc/mnttab also, just cat /etc/mnttab. If it doesn't look exact to /etc/fstab then

mv /etc/mnttab /etc/mnttab_old
mount -a

This will rebuild /etc/mnttab.

Re: Ignite fails with error

Armin Kunaschik — Tue, 03 Nov 2009 14:23:14 GMT

As suggested, run the list_expander and check the result!
I got this error once when I had a link under /usr which pointed to itself.
It may also be possible that you have errors in those files... or unmounted filesystems. Do you get any error when you do a "mount -a"?

My 2 cents,
Armin

PS: Please assign points!