To close this thread, we fixed things a lot easier by installing a new
site BDII on a VM. The only caveat that we found was SELinux blocked the
bdii startup script. Oh, and that I only just remembered to alter the
site-BDII entry in the GOCDB to the new node.
Behold our new (bprobably still needing some polishing) site bdii:
ldapsearch -x -H ldap://fal-pygrid-14.lancs.ac.uk:2170 -b
Mds-Vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid
Thanks to Stephen and Ewan for the advice, I'm wishing I had spent my
time working smarter rather then harder.
Have a good weekend all,
Matt
Matt Doidge wrote:
> The script works when run by hand, and produces lots of nice
> mds-vo-name=UKI-NORTHGRID-LANCS-HEP type entries, but for some reason
> these don't sink into the bdii. I'm tinkering now whilst I set up a
> fresh VM for a new site BDII, it would have been nice to have fixed our
> current run to cover us in the meantime but it looks like that's not to be.
>
> Thanks for all the advice,
> Matt
>
> Stephen Burke wrote:
>> Testbed Support for GridPP member institutes
>>> [mailto:[log in to unmask]] On Behalf Of Matt Doidge said:
>>> [root@fal-pygrid-17 ~]# cat glite-info-provider-site
>>> #!/bin/sh
>>> /opt/glite/libexec/glite-info-provider-ldap -c
>>> /opt/glite/etc/gip/site-urls.conf -m UKI-NORTHGRID-LANCS-HEP
>>
>> I think that's the critical one - the -m should be putting it on the
>> right DN ... you could try running it by hand, but indeed it may be
>> simpler just to upgrade, you'll have to move to glite 3.2 at some point
>> anyway.
>>
>> Stephen
|