This looks weird. The GlueVOInfo objects are occasionally intentionally missing:
we should be publishing them iff the storage area has a space token descr.
In release 1.1.2, adapted to enable the above shenanigans, SA.ACBRs would drop
out for SAs with no VOInfo objects. However, this should have been fixed now
from the 1.1.3 release, and the SA.ACBR should be published correctly for
Atlas (and everybody else, too).
Weirder still, GlueSARoot is static and comes from the GIP proper.
I'll take a look. Thanks for sending me this.
--jens
-----Original Message-----
From: GRIDPP2: Deployment and support of SRM and local storage management on behalf of Greig A. Cowan
Sent: Wed 21/01/2009 14:30
To: [log in to unmask]
Subject: RAL CASTOR information publishing broken
Hi Jens,
Is the CASTOR information publishing broken?
[BDII] lcg-bdii.gridpp.ac.uk:2170: Warning, no GlueVOInfo information found about tag '(null)' and SE 'srm-atlas.gridpp.rl.ac.uk'
[BDII] lcg-bdii.gridpp.ac.uk:2170: No GlueSA information found about atlas VO and SE srm-atlas.gridpp.rl.ac.uk
Similar messages for other VO endpoints as well, i.e., missing
GlueSARoot for dteam.
Cheers,
Greig
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
--
Scanned by iCritical.
|