make_net_recovery error

[David Cassin]

I'm getting the following error when trying to run a make_net_recovery. Has anyone got any ideas on a fix?

Creating Ignite Image for hostA on hostB

* Creating NFS mount directories for configuration files.
ERROR: Could not make directory:
/var/opt/ignite/recovery/client_mnt/0x00306E5DD4AF: Permission denied
(errno = 13)
ERROR: Failed creating the directory
/var/opt/ignite/recovery/client_mnt/0x00306E5DD4AF:Permission denied
(errno = 13)
ERROR: Failed to create NFS mount directories for configuration files.

======= 06/08/06 14:14:54 BST make_net_recovery completed unsuccessfully

[JASH_2]

David,

This is a permissions problem on the ignite server. Either you have not exported the
/var/opt/ignite/recovery/client_mnt directory with the correct permissions, or the directory itself has very restrictive permissions.

Check the /etc/exports file and make sure that it has the above directory exported with -anon=2 in it. Check the permissions on the directory that it is global write.

Hope this helps.

JASH

[Ludovic Derlyn]

hi,

You execute this about a ignite server or not ?
if yes , verify /etc/exports host A et B must be set and execute exportfs -av

[David Cassin]

On ignite server, hostB, the directory /var/opt/ignite/recovery/client_mnt has the permissions 777.

The /etc/exports file has the following entry for hostA;

/var/opt/ignite/recovery/archives/hostA -anon=2,access=hostA

I've run the exportfs -av, and still get the same error when trying the make_net_recovery.

[JASH_2]

David,

Take off the hostA at the end of the line in exports, then run exportfs -av.

It will then work.(hopefully)

JASH

[JASH_2]

I mean take off the whole bit of access=HostA
off the end of the line, sorry.

[David Cassin]

Jash, that's not the problem as the ignite server has 150+ clients in the /etc/exports file, and those clients are able to run the make_net_recovery.

I actually think the issue is on the client side. I've been able to manually mount the directory /var/opt/ignite/recovery/client_mnt on hostA from hostB (ignite server). Therefore the export is working properly from the ignite host.

Any other ideas?

[JASH_2]

David,

Sorry, thought I had it there.

If hostA is a new server, do you have the .rhosts set up on BOTH servers for hostA on hostB and hostB on hostA?

You haven't, but any chance, made any network changes on hostA, recently. Has it ever worked?

Jash

[DCE]

David,

It sounds like you have everything configured correctly (especially since you 150 other servers working fine with the same config)

Two things that have tripped me up when adding a new client

directory ownership should be bin:bin

Ignite versions must be the same. I have corrected errrors like the one you are describing by
a. installing the same version of ignite on the client as on the server
b. reinstalling the ignite on the client

HTH
Dave

[David Cassin]

Just been checking the ignite versions, and they differ on the client and ignite server so i'm going to upgrade the versions to see if that solves the issue.

Thanks for the help so far, i'll update again on the outcome of the above.

[David Cassin]

I've updated the ignite version, although i'm still getting the same error so have decided to raise service call with HP.

Will update this thread with the outcome and any fixes from HP. Thanks for the help so far.

[JASH_2]

David,

Please let us know what it is, I know that it is something simple, but just cannot put my finger on it now!

Cheers,

JASH

[David Cassin]

With help from HP s/w engineer, found the problem to be with the ignite server, hostB, not having the directory /var/opt/ignite/recovery/clients/0x00306E5DD4AF, and the link for this directory /var/opt/ignite/recovery/clients/hostA -> 0x00306E5DD4A

Once this was created, and permissions set, the ignite image created successfully.

[David Cassin]

See previous