Ignite/UX Server

[Marcia Ferreira_5]

Hi
I´m using make_net_recovery (on a Ignite/Ux client) and this message appeared:
Creating NFS mount directories for configuration files.
nfs mount: get_fh: lxhp250:: RPC: Timed out
nfs mount: get_fh: lxhp250/var/opt/ignite/clients: server not responding : RPC: Timed out
nfs mount: retry: retrying(1) for: /var/opt/ignite/recovery/client_mnt after 5 seconds
nfs mount: retry: giving up on: /var/opt/ignite/recovery/client_mnt
ERROR: Could not NFS mount directory /var/opt/ignite/clients on lxhp250. The
exports file on lxhp250 should contain the entry
"/var/opt/ignite/clients -anon=2". Ensure that /var/opt/ignite/clients
has been exported using the "exportfs -av" command.
ERROR: Failed mounting directory /var/opt/ignite/recovery/client_mnt:/Error 0
(errno = 0)
ERROR: Failed to creaet NFS mount directories for configuration files.

The point is: all the process above has been solved, but the problem persist.
How can I solve this problem ?
tks
Marcia

[harry d brown jr]

What OS revision are you running?
What hardware?

Do you have the latest patch bundle installed?

WHat options on make_net_recovory are you using?

live free or die
harry d brown jr

[Marcia Ferreira_5]

What OS revision are you running? HP-UX 11.11 (server and client)
What hardware? L2000 (server) / D390 (client)

Do you have the latest patch bundle installed? Feb/200 (server) / Jun/2003 (client)

WHat options on make_net_recovory are you using? make_net_recovery -s lxhp250 -x inc_entire=vg00 #on client

they are on a diff network, but I can mount a NFS FS; all of NFS deamons are ok ...

[harry d brown jr]

You need to patch to at least Dec 2004: http://www1.itrc.hp.com/service/patch/releaseIndexPage.do?BC=patch.breadcrumb.main|patch.breadcrumb.bundle|

Also, when you say they are on different networks, do you mean different subnets or different subnets separated by possibly a firewall?

If my memory serves me right, I don't think you can cross subnets.

live free or die
harry d brown jr

[Steven E. Protter]

I would agree the system should be patched.

The problem is may not be patch related.

Some kind of disruption in the networking seems to have occurred and the D390 box can't communicate with the NFS server.

Is the directory /var/opt/ignite/clients in /etc/exports ?

What are the results on the server of exportfs -av ?

A networking problem on the D390 with its NIC or switch port settings or even cable can create these conditions. The NIC on those servers do tend to get flaky and fail over time.

Going out to the patch database and getting the three star NFS patches may help as well.

SEP

[Marcia Ferreira_5]

Hi Steve

Is the directory /var/opt/ignite/clients in /etc/exports ? Yes ->
[lxhp250:/] exportfs
/var/opt/ignite/clients -anon=2
/ignite/recovery/archives/lxhp46 -anon=2,access=lxhp46


What are the results on the server of exportfs -av ?
[lxhp250:/] exportfs -av
re-exported /ignite/recovery/archives/lxhp46
re-exported /var/opt/ignite/clients
re-exported /ignite/recovery/archives/lxhp46

and the configuration of /etc/opt/ignite/instl_boottab is correct.

Help !!!
rgs
Marcia

[RolandH]

You wrote:

Is the directory /var/opt/ignite/clients in /etc/exports ? Yes ->
[lxhp250:/] exportfs
/var/opt/ignite/clients -anon=2
/ignite/recovery/archives/lxhp46 -anon=2,access=lxhp46

Check permissions for
/ignite/recovery/archives/lxhp46
should belong to bin:bin and have 755 access rights

Change the export from:
/ignite/recovery/archives/lxhp46 -anon=2,access=lxhp46
to:
/ignite/recovery/archives/lxhp46 -anon=2

Does that work?

Roland

[RolandH]

I saw one more mistake in your make_net_recovery command

You wrote:
WHat options on make_net_recovory are you using? make_net_recovery -s lxhp250 -x inc_entire=vg00 #on client

Try this:
make_net_recovery -s lxhp250 -a lxhp250:/ignite/recovery/archives/lxhp46 -x inc_entire=vg00

Roland