Ignite-UX errors (make_net_recovery)

[James Clay_2]

Hi,

I am attempting to rebuild an ignite server but am having difficulties when creating make_net_recovery images.
I am using revision B.3.4.115 but get some errors when initiating the GUI from the client. Firstly when an entry is added to the /etc/exports file with access specific to the server being backed up it complains about being unable to mount the filesystem. (see attached).

Second If I modify the exports file to include access to any host I can progress, however when creating the archive a gzip error is encountered and the image build fails with error status 1.

Can anyone help???

Thanks

[Jordan Bean · Accepted solution]

From the Ignite server, show us the portions of the log file,

/var/opt/ignite/clients//recovery/latest/recovery.log

If you're using short hostnames in /etc/exports, then be sure the Ignite server can correctly resolve these short hostnames to their respective IPs.

I have not comment as of yet regarding the gzip error.

[James Clay_2]

Thanks. I think I have got to the bottom of the gzip issue now (Installed a newer version).


I can see the server fine when I ping it, the hostname comes via DNS, however having put the fully qualified name in the hosts file I no longer get the NFS error.

What is the best way to overcome the name resolution problem?

[Helen French]

Having the domain in your /etc/resolv.conf should take care of that so you don't have to use the fully qualified name. Or try using ip address although I don't know if ignite will accept ip - never tried it....

[James Clay_2]

OK this is the problem that is bugging me the most from my exports file the client I am trying to make an image of has been automatically entered:
/var/opt/ignite/recovery/archives/bssloan -anon=2,access=bssloan

If this line is left in then I get errors regarding ownership of the directory etc. However if I change it as such I can progress:

/var/opt/ignite/recovery/archives/bssloan -anon=2

My /etc/resolv.conf file looks like this:

domain jim.com
nameserver 172.20.1.3
nameserver 172.20.1.4

[Jordan Bean]

Hi James,

Are you getting the attached error?

What name is the Ignite server resolving for the client's IP address?

I'm guessing that you still have a name resolution problem... perhaps a mismatch in DNS between the A and PTR records... Or in /etc/hosts the client's IP has a different name (typo maybe)... Or the client's IP is not what it should be...

Tell us what these come up with:

grep hosts /etc/nsswitch.conf
nslookup ..
nslookup
nslookup

[Jordan Bean]

Oh, I should point out that my exports look like this:

/var/opt/ignite/clients -anon=2,access=server1:client1:client2:client3:@192.168.10
/var/opt/ignite/depots -anon=2,access=server1:client1:client2:client3:@192.168.10
/var/opt/ignite/recovery/archives/client1 -anon=2,access=client1
/var/opt/ignite/recovery/archives/client2 -anon=2,access=client2
/var/opt/ignite/recovery/archives/client3 -anon=2,access=client3


So in my case, make_net_recovery bombed immediately trying to mount /var/opt/ignite/clients rather than later when it would try /var/opt/ignite/recovery/archives/clientN.

[James Clay_2]

Hi Jordan,

Below is the output from the commands you recommended typing, and also the contents of the logfile.

hostsys1 #grep hosts /etc/nsswitch.conf
hosts: files [NOTFOUND=continue] dns
hostsys1 #nslookup rem2.domain.com
Using /etc/hosts on: hostsys1

looking up FILES
Name: rem2.domain.com
Address: 172.20.115.232


hostsys1 #nslookup rem2
Using /etc/hosts on: hostsys1

looking up FILES
Trying DNS
Name: rem2.domain.com
Address: 172.20.115.232

hostsys1 #nslookup 172.20.115.232
Using /etc/hosts on: hostsys1

looking up FILES
Name: rem2.domain.com
Address: 172.20.115.232
hostsys1


#more /var/opt/ignite/clients/rem2/recovery/latestrecovery.log


======= 06/20/02 09:12:19 BST Started /opt/ignite/bin/make_net_recovery. (Thu
Jun 20 09:12:19 BST 2002)
@(#) Ignite-UX Revision B.3.4.115
@(#) net_recovery (opt) $Revision: 10.547 $


* User interface starting.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x00306E036A22/recovery/defaults.

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


======= 06/20/02 09:12:55 BST make_net_recovery completed unsuccessfully

hostsys1 #


Hope this is not tooo much to get through.

Thanks

[Sridhar Bhaskarla]

Hi James,

on hostsys1:

#exportfs

Make sure it displays this entry

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

If it doesn't list out the above, then
edit your /etc/exports file and add the above entry and do an exportfs -a

on rem2:

#mkdir /tmp_hostsys1
#mount hostsys1:/var/opt/ignite/recovery/archives/rem2 /tmp_hostsys1

It should mount. Then

#unmount /tmp_hostsys1

Then try doing make_net_recovery.

-Sri

[Jordan Bean]

Host name resolution looks good. Tell me that the client's IP address is correct.

I can see that the client is able to mount ignite/clients/0x00306E036A22, but not ignite/recovery/archives/rem2

make_net_recovery first attempts to mount /var/opt/ignite/clients//, not /var/opt/ignite/clients//. It later assumes that the archive you want is /var/opt/ignite/recover/archives// based on the name it finds in /var/opt/ignite/clients//client_name.

If you cannot access the archive when it is exported with access=rem2, then the clients IP must not be what hostsys1 is expecting.