Dear Storage Gurus,
No advice on this yet. IIRC the ops d1t0 space token is a token token
(if you see what I mean) - sort of only a demo thing.
Since it's causing grief with these new tests, is there any
reason it shouldn't be deleted?
And where are instruction on how to remove a space token please?
On Mon, 30 Nov 2009, Winnie Lacesso wrote:
>
> Dear Wise Storage people,
>
> The EGEE Bcast says "Please ensure that your SEs are passing the new test"
> CE-sft-lcg-rm-free
>
> Bris DPM SE lcgse01 is passing the test on "SA ops" but failing test on
> ops space token (don't really grok this) with WARNING:
>
> SA ops:srm2_d1t0:online :
> GlueSAFreeOnlineSize = 0 GB
> GlueSAStateAvailableSpace = 419430 KByte
> ACBRs for VO ops = ops
> WARNING: correct ACBR (VO:vo or VOMS:fqan) missing: ops
>
> In /opt/glite/etc/gip/ldif/static-file-SE.ldif is nothing about d1t0
> (should there be?)
>
> /opt/bdii/var/tmp/Provider.ldif has
> GlueVOInfoLocalID: ops:srm2_d1t0
> GlueVOInfoName: ops:srm2_d1t0
> GlueVOInfoPath: /dpm/phy.bris.ac.uk/home/ops
> GlueVOInfoTag: srm2_d1t0
> GlueVOInfoAccessControlBaseRule: VO:ops
>
> So, maybe a line
> GlueVOInfoAccessControlBaseRule: ops
> is missing, but that file is auto generated from other info.
> How to put that in there?
> Hints on how to fix this most welcome.
>
>
>
|