topic Re: make_net_recovery question in Operating System - HP-UX

make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 09:09:44 GMT

I just started tinkering with Ignite and attempted to make a network recovery archive and I'm getting this error.

Unable to mount or write host:/var/opt/ignite/recovery/archive/host2
On host you may need to:
mkdir -p /var/opt/ignite/recovery/archives/host2
chown bin:bin /var/opt/ignite/recovery/archives/host2
vi /etc/exports (add or modify an entry)
exportfs -av

I've done all of these things so I'm not sure where my problem is. Any help would be greatly appreciated.

Thanks

Re: make_net_recovery question

Bernhard Mueller — Thu, 13 May 2004 09:19:23 GMT

Brent

is NFS running?

check /etc/rc.config.d/nfsconf
NFS_CLIENT=
NFS_SERVER=

set both to 1 on the server, and set NFS_CLIENT to 1 on the client.

run
/sbin/inti.d/nfs.core start
/sbin/init.d/nfs.client start
/sbin/init.d/nfs.server start

Regards,
Bernhard

Re: make_net_recovery question

Mark Greene_1 — Thu, 13 May 2004 09:22:08 GMT

on host2, run rpcinfo to see if you have all the required rpc stuff needed for nfs, then run the following on host2 to verify the processes:

UNIX95= ps -efH|head -1; UNIX95= ps -efH|egrep "inetd|rpc|mount|nfs"|grep -v grep; rpcinfo -p|egrep "service|nfs"; showmount -e; mount -p

the last two commands in that string should show you the exported and mounted file systems for host2.

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 09:34:01 GMT

Bernhard,

On my ignite server:

NFS_CLIENT=1
NFS_SERVER=1

On the client:

NFS_CLIENT=1
NFS_SERVER=1

Re: make_net_recovery question

Bernhard Mueller — Thu, 13 May 2004 09:37:06 GMT

Brent

try if you can maunally mount and umount an exported filesystem.

Also use nslookup to verify hostname resolution and reverse lookup of ip adress match.

Regards,
Bernhard

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 09:41:21 GMT

Mark,

Looks like everything is there.

host:/var/opt/ignite/clients /var/opt/ignite/recovery/client_mnt nfs defaults,NFSv3 0 0

Re: make_net_recovery question

Elena Leontieva — Thu, 13 May 2004 10:12:08 GMT

Brent,

How your /etc/exports file looks like on the Ignite server? On my Ignite server I have:

more /etc/exports

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

HTH,

Elena.

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 10:26:55 GMT

Elena,

I have the same thing.

$ more /etc/exports
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/host2 -anon=2,access=host2

Re: make_net_recovery question

Francesco Campalastri — Thu, 13 May 2004 10:50:12 GMT

It should work!

Try to mount it manually from host2
On host2
# mount \
host:/var/opt/ignite/recovery/archives/host2 \
/mnt/

# touch /mnt/test

What happens?

Where /var/opt/ignite/recovery/archives/host2 stays? What logical volume on?

On host:
# exportfs
# mount

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 12:12:25 GMT

This is from the recovery.log

# more recovery.log

======= 05/13/04 11:20:51 EDT Started /opt/ignite/bin/make_net_recovery. (Thu
May 13 11:20:51 EDT 2004)
@(#) Ignite-UX Revision B.5.3.35
@(#) net_recovery (opt) $Revision: 10.624 $

* User interface starting.
NOTE: vgdisplay -v unsuccessful
Permission denied
ERROR: Could not NFS mount the directory
"/var/opt/ignite/recovery/archives/earl" from "ej". Ensure that the
directory has been exported using the "exportfs" command.
Permission denied
ERROR: Could not NFS mount the directory
"/var/opt/ignite/recovery/archives/earl" from "ej". Ensure that the
directory has been exported using the "exportfs" command.
* User interface was cancelled.

======= 05/13/04 11:50:29 EDT make_net_recovery completed unsuccessfully

Re: make_net_recovery question

Francesco Campalastri — Thu, 13 May 2004 12:16:55 GMT

Ok, on ej:

# mount
# exportfs

and give us the output please,
francesco

Re: make_net_recovery question

Elena Leontieva — Thu, 13 May 2004 12:31:22 GMT

Brent,

I wonder if you have a problem with the /etc/lvmtab? Do strings /etc/lvmtab and vgdisplay -v vg00. Do your Cur PV and Act Pv are consistent and lvmtab looks as you expect?

Just a thought,
Elena.

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 12:47:54 GMT

# mount
/ on /dev/vg00/lvol3 log on Wed May 5 06:28:06 2004
/stand on /dev/vg00/lvol1 defaults on Wed May 5 06:28:07 2004
/web/test3.morris.com on /dev/vg00/test3 delaylog,nodatainlog on Wed May 5 06:28:16 2004
/web/test3.morris.com/wayne on /dev/vg00/wayne delaylog,nodatainlog on Wed May 5 06:28:16 2004
/web/ows1 on /dev/vg00/owslog delaylog,nodatainlog on Wed May 5 06:28:16 2004
/var on /dev/vg00/lvol8 delaylog,nodatainlog on Wed May 5 06:28:16 2004
/var/spool/apfeed on /dev/vg00/apfeed delaylog,nodatainlog on Wed May 5 06:28:16 2004
/var/opt/perforce on /dev/vg00/lvol_perforce delaylog,nodatainlog on Wed May 5 06:28:17 2004
/var/opt/nms on /dev/vg00/lvol_var_nms delaylog,nodatainlog on Wed May 5 06:28:17 2004
/var/opt/inn on /dev/vg00/inn delaylog,nodatainlog on Wed May 5 06:28:17 2004
/var/adm/sw on /dev/vg00/vasw delaylog,nodatainlog on Wed May 5 06:28:17 2004
/usr on /dev/vg00/lvol7 delaylog,nodatainlog on Wed May 5 06:28:17 2004
/u02 on /dev/vg00/u02 delaylog,nodatainlog on Wed May 5 06:28:17 2004
/u01 on /dev/vg00/u01 delaylog,nodatainlog on Wed May 5 06:28:17 2004
/tmp on /dev/vg00/lvol4 delaylog,nodatainlog on Wed May 5 06:28:18 2004
/opt on /dev/vg00/lvol6 delaylog,nodatainlog on Wed May 5 06:28:18 2004
/opt/nms on /dev/vg00/lvol_opt_nms delaylog,nodatainlog on Wed May 5 06:28:18 2004
/opt/gnome on /dev/vg00/lvol_gnome delaylog,nodatainlog on Wed May 5 06:28:18 2004
/opt/Netscape on /dev/vg00/lvol_opt_Netscape delaylog,nodatainlog on Wed May 5 06:28:18 2004
/home on /dev/vg00/lvol5 delaylog,nodatainlog on Wed May 5 06:28:18 2004
/home/rnelson on /dev/vg00/lvol_home_rnelson delaylog,nodatainlog on Wed May 5 06:28:19 2004
/home/rnelson/projects on /dev/vg00/jungrm delaylog,nodatainlog on Wed May 5 06:28:19 2004
# exportfs
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/earl.morris.com -anon=2,access=earl.morris.com

Re: make_net_recovery question

Marvin Strong — Thu, 13 May 2004 13:16:32 GMT

hmm just a wild guess,

are sure certain the ownership is bin:bin for /var/opt/ignite/recovery on both sides? And the permissions are set correctly 755.

Re: make_net_recovery question

Brent DeGennaro — Thu, 13 May 2004 13:41:37 GMT

755 on both hosts

Re: make_net_recovery question

Bernhard Mueller — Thu, 13 May 2004 13:56:33 GMT

Brent,

this looks like you have an exported directory /var/opt/ignite/recovery/archives/earl.morris.com on ej

but earl wants to mount
ej:/var/opt/ignite/recovery/archives/earl

....

So you should check /etc/hosts and /etc/nsswitch.conf plus your DNS servers to get things straight.

For your current issue it *might* help to
run exportfs -ua cd /var/opt/ignite/recovery/archives
mv earl.morris.com earl
edit /etc/exports and remove .morris.com
run exportfs -va

Regards,
Bernhard

Re: make_net_recovery question

Francesco Campalastri — Thu, 13 May 2004 17:01:37 GMT

I totally agree with Bernhard,
probably the servers have two different name resolution.

Probably
/etc/hosts differ between two servers or
/etc/resolv.conf differs or
/etc/nsswitch.conf differ.

Francesco