Hi Placi,
Please check that the following file exists.
/opt/glite/etc/gip/provider/glite-info-provider-egee
If the top level BDII has been missconfigured. From your discription, it
seems that you have configured your top-level BDII as a site-level BDII.
Laurence
Placi Flury wrote:
> Dear all,
>
> we've installed the latest production top level BDII and stumbled over
> the following problem:
>
> querying the top level BDII with:
>
> ldapsearch -x -LLL -H ldap://<BDII_top>:2170 -b "mds-vo-name=local,
> o=grid"
>
> didn't return any records. By changing the query to
>
> ldapsearch -x -LLL -H ldap://<BDII_top>:2170 -b "mds-vo-name=resource,
> o=grid"
>
> we just get the records of our local site BDII (which is a gLite 3.1
> slc4 on top of a lcg-CE) and nothing more.
>
> Notice that the site BDII's records can only be queried via
> "mds-vo-name=resource", that is:
> ldapsearch -x -LLL -H ldap://<BDII_site>:2170 -b
> "mds-vo-name=resource, o=grid" Above situation is not very
> satisfactory since our WMS will not see our local resources, as it
> queries the top level BDII with "mds-vo-name=local". By replacing
> above top level BDII with a backup of an slc3 BDII everything worked
> fine again, so we do rather exclude a misconfiguration on either the
> WMS or the site-BDII.
>
> Did anyone have a similar experience?
>
> Best regards,
>
> Placi
>
> ps. the top level BDII has been configured with : yaim -c -s
> site-info.def -n BDII_top
|