On Mon, 17 Jan 2005, Andreas Unterkircher wrote:
> I manually set up an SECLASSIC (oplapro16.cern.ch) on IA64. I logged into
> the UI lxb1523.cern.ch and tried to copy/register a file:
>
> lcg-cr -v --vo dteam -d oplapro16.cern.ch -l lfn:openlabTest
> file:/afs/cern.ch/user/u/unterkir/CE-ia64-test/openlabTest.txt
>
> This yields:
>
> Using grid catalog type: edg
> lcg_cr: Protocol not supported
>
> Does anybody know what this error message means ? On the other hand the
> following command executes successful:
>
> globus-url-copy
> file:/afs/cern.ch/user/u/unterkir/CE-ia64-test/openlabTest.txt
> gsiftp://oplapro16.cern.ch
>
> Doing an ldapsearch on oplapro16.cern.ch also shows all the Glue entries
> defined.
There is a problem with the information published:
-----------------------------------------------------------------------------
$ edg-rm pi
WARNING: GetProtocols: Nothing found in MDS for the seID = oplapro16.cern.ch
This means that either MDS just crashed between two queries or that the
content of the GlueSE and GlueSEAccessProtocol is inconsistent: There is a
GlueSE ID oplapro16.cern.ch but no corresponding entry in the
GlueSEAccessProtocol was found.
[...]
SE at LCGCERTTB1
name : LCGCERTTB1
host : lxb1767.cern.ch
type : disk
accesspoint : /flatfiles/LCG-CERT-SE01
VOs : cms, lhcb, sixt, alice, atlas, dteam
VO dir for cms : /cms
VO dir for lhcb : /lhcb
VO dir for sixt : /sixt
VO dir for alice : /alice
VO dir for atlas : /atlas
VO dir for dteam : /dteam
protocols : gsiftp, rfio
[...]
SE at cern-openlab
name : cern-openlab
host : oplapro16.cern.ch
type : disk
accesspoint : /storage
VOs : ERROR: Query MDS Query for GlueSA: No entry found or
invalid SE ID for oplapro16.cern.ch
VO dir for ERROR: Query MDS Query for GlueSA: No entry found or invalid SE ID
for oplapro16.cern.ch : /<ERROR>
-----------------------------------------------------------------------------
The SE needs to be bound to a close CE (oplapro17), which defines the VOs
and their dirs.
|