Print

---

Hello all,
We up here in Lancaster have been having a spot of trouble with the site 
BDII after an unfortunate yum accident "updated" our bdii with a newer, 
non-glite version. We've managed, with much wailing and gnashing of 
teeth, to *almost* fix things. But we have a catch, the standard 
test-your-bdii search doesn't work for us (I've included what we get 
below), but if I omit the mds-vo-name=<site-name> and generically query 
the server I get a lot of reasonable looking site information (although 
of course it could be wrong but we'll cross that bridge later).

I've been bashing away at this for a while and I can't see where things 
are wrong. There are no sneaky "mds-vo-name=resource" or similar lines 
in my configs that I can find, and I even see an entry:
dn: Mds-Vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid
in my generic ldap query. But my ldap knowledge is weak and I can't for 
the life of me figure out why all the information isn't binding to our 
sitename. The most relevent line that I can find (in the bdii.conf) 
seems to be right:

BDII_BIND=mds-vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid

Has anyone seen anything like this before, or would perhaps be able to 
point me towards where things are likely to be going wrong? Any help 
would be greatly appreciated.

Thanks in advance,
Matt

What I'm currently getting whilst querying the site bdii:
# ldapsearch -x -H ldap://fal-pygrid-17.lancs.ac.uk:2170 -b 
mds-vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid
# extended LDIF
#
# LDAPv3
# base <mds-vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid> with scope sub
# filter: (objectclass=*)
# requesting: ALL
#

# UKI-NORTHGRID-LANCS-HEP, grid
dn: Mds-Vo-name=UKI-NORTHGRID-LANCS-HEP,o=grid
objectClass: GlueTop
objectClass: Mds
Mds-Vo-name: UKI-NORTHGRID-LANCS-HEP

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1