make_net_recovery/ldap problem?

[Onyedika Onwudiwe]

I'm having trouble creating a make_net_recovery archive after upgrading to Ignite 6.2 from 6.0. I upgraded because I saw it fixed a problem with ignite and ldap. However I am still not able to create a make_net_recovery archive of a server using ldap. Here is the error I'm getting:

-----


* /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_m
nt/0x0012799E235C/recovery/2005-09-14,15:53/archive_cfg -g /var/opt/ig
nite/recovery/client_mnt/0x0012799E235C/recovery/2005-09-14,15:53/flis
t -n 2005-09-14,15:53 -r ipf -b 64 -d Recovery\ Archive -L
/var/opt/ignite/recovery/arch_mnt -l
cpafisr0:/var/opt/ignite/recovery/archives/cpafisr3 -i 2 -m t
ERROR: Must specify directory where archive is stored with -l option
ERROR: Must specify directory where archive is stored with -l option
ERROR: Failure creating the archive configuration
ERROR: make_arch_config failed.


-----

[Sameer_Nirmal]

You need to specify the directory where you want to store the archive.

Which syntex you are using with make_net_recovery???

You might be aware that, the archive server should be a NFS server and its directory should be exported.

[Ermin Borovac]

This is belated reply, but I just came across the same problem.

Ignite version is the latest currently available, which I believe is C.6.2.241.

We use LDAP in our environment to store user account information and some host information.

After changing /etc/nsswitch.conf

from

hosts: files [NOTFOUND=continue] ldap [NOTFOUND=continue] dns

to

hosts: files [NOTFOUND=continue] dns [NOTFOUND=continue] ldap

make_net_recovery, which calls /opt/ignite/lbin/make_arch_config, works fine. So after switching the order of ldap and dns in nsswitch.conf, make_net_recovery works fine.

It looks like make_arch_config has trouble (no idea why) with hostname resolution of archive host specified with -l option. BTW in my case archive hostname is resolved from DNS not from LDAP.

Anyway, hope this is of help to someone ...

[Onyedika Onwudiwe]

Ermin, your reply was a great troubleshooting tip. I was able to get it to work by adding the ignite servers ip to the host file and switching nsswitch to use files before ldap. It's a work around, for now, but definately not a solution.

It pretty much proves there is still an LDAP problem with hostname resolution, but the appropriate labs have been notified.

Thanks.

[Onyedika Onwudiwe]

closing thread