On Tue, 11 Oct 2005, Juan J. Saborido Silva wrote:
> Well... now it appears to be working OK.
>
> For some reason, after configuring back an forth my CE
> a number of times, the file "/opt/bdii/etc/bdii-update.conf" appeared
> with the full list corresponding to a "top level bdii". Now I think it
> is OK,
Indeed.
> it only contains these 2 lines:
>
> CE ldap://lcg-ce.usc.cesga.es:2135/mds-vo-name=local,o=grid
> SE ldap://lcg-se.usc.cesga.es:2135/mds-vo-name=local,o=grid
>
> In fact, before my CE started to go mad I edited the
Why did you think the file needed editing?
> file "bdii.conf" and set the variable BDII_AUTO_UPDATE to "yes", and
> restarted the bdii daemon. I wonder wether this caused the problem.
It did, and it caused a positive feedback loop: your site published
the whole grid as local resources, and since the BDII queried itself,
more resources were found etc.
This has exposed two bugs:
- YAIM shall leave the auto-update URL empty for a site BDII;
- the BDII shall not recursively include sites.
We will try and address these issues before the next release.
> I guess I should leave the variable BDII_AUTO_UPDATE set to "no",
> like the yaim configuration script does.
Exactly.
|