Operating System - HP-UX
1837277 Members
2942 Online
110115 Solutions
New Discussion

Ignite Make network recovery error

 
SOLVED
Go to solution
Richard Murden
Regular Advisor

Ignite Make network recovery error

Ignite server is running 11.0 and client that i am trying to archive is runn 11.0 also. I get this error when trying to perform the "Create network recovery Archive"
Thanks,
Richard

ERROR: WARNING: Failed creating symlink from clients lanic id to clients
hostname.
File exists (errno = 17)
WARNING: Could not open client status file
"/var/opt/ignite/recovery/client_mnt
/0x080009C4D4C5/recovery/client_status" :Permission denied
(errno =
13).
ERROR: Could not make directory:
/var/opt/ignite/recovery/client_mnt/0x080009
C4D4C5/recovery/2004-03-11,12:44: Permission denied (errno =
13)
ERROR: Failed creating the directory
/var/opt/ignite/recovery/client_mnt/0x08
0009C4D4C5/recovery/2004-03-11,12:44 Permission denied (errno
= 13) to
store configuration files for the client

ERROR: Failed to creaet NFS mount directories for configuration
files.

9 REPLIES 9
RAC_1
Honored Contributor

Re: Ignite Make network recovery error

Post showmount -e "ignite_server"

Are you running this netrecovery as root on client? If yes, you need appropriate options in /etc/exports file on server. Root is always treated as unknown user unless specified.

Anil
There is no substitute to HARDWORK
Sundar_7
Honored Contributor
Solution

Re: Ignite Make network recovery error

Hi,

root in the NFS client by default will not get mapped to root in the NFS server.

Make sure ignite-ux server is exporting the NFS filesystems with the following options

-anon=2,access=

In the ignite-ux server

# mkdir -p /var/opt/ignite/recovery/archives/igniteclient1

# chown bin:bin /var/opt/ignite/recovery/archives/igniteclient1

# exportfs -iv -o -anon=2,access=igniteclient1 /var/opt/ignite/recovery/archives/igniteclient1

and then try the command. See if it helps

Sundar.
Learn What to do ,How to do and more importantly When to do ?
Richard Murden
Regular Advisor

Re: Ignite Make network recovery error

Anil, here is the showmount:
showmount -e sdc9008
export list for sdc9008:
/ignite_images/ignite/recovery/archives/sdc9002.sdc.sentara.com sdc9002.sdc.sentara.com
/ignite_images/ignite/recovery/archives/sdc9007.sdc.sentara.com sdc9007.sdc.sentara.com
/ignite_images/ignite/clients (everyone)
/ignite_images/ignite/recovery/archives/sdc9001-fe1.sdc.sentara.com sdc9001-fe1.sdc.sentara.com
Richard Murden
Regular Advisor

Re: Ignite Make network recovery error

Anil,
I am running it as root. Attached is the /etc/exports file from the ignite server.
RAC_1
Honored Contributor

Re: Ignite Make network recovery error

/etc/exports file looks ok. What are the perms on /var/opt/ignite/recovery/archives/sdc9001-fe1.sdc.sentara.com. Should be bin:bin ownership and rw for owner and group.

Anil
There is no substitute to HARDWORK
RAC_1
Honored Contributor

Re: Ignite Make network recovery error

Also what are the perms on var/opt/ignite/recovery/client_mnt/0x080009
C4D4C5/recovery/2004-03-11,12:44?

Anil
There is no substitute to HARDWORK
Richard Murden
Regular Advisor

Re: Ignite Make network recovery error

I changed the perms on the sdc9001-fe1.sdc.sentara.com file. There are no files in the client_mnt directory on the server or client.
RAC_1
Honored Contributor

Re: Ignite Make network recovery error

Try restarting nfs client and server on both machines

Anil
There is no substitute to HARDWORK
Richard Murden
Regular Advisor

Re: Ignite Make network recovery error

We got it to work. File permissions and ownership on client_mnt and client. Things are working a lot better now. Thanks to you both! Points have been assigned for both of you.
Richard