On Thu, 24 Feb 2005, Emmanuel Medernach wrote:
> Maarten Litmaath a écrit:
>
> > That happens when the "default SE" in
> > /opt/edg/var/etc/edg-replica-manager/edg-replica-manager.conf
> > does _not_ appear in the information system.
> >
> > What is the "mds.url" in said file?
> >
> > Note that it will be overridden by the LCG_GFAL_INFOSYS env. var.
> > (but both should be the same anyway).
> >
> The default SE is 'clrlcgse01.in2p3.fr' and mds.url is
> 'ldap://lxn1178.cern.ch:2170'
>
> The UI uses 'egee-bdii-01.cnaf.infn.it:2170' in LCG_GFAL_INFOSYS.
You should avoid confusion and set both to the same value.
Anyway, your SE does appear in the info system, but now one gets this:
-----------------------------------------------------------------------------
$ edg-rm -v --vo dteam cr file:/etc/group -d clrlcgse01.in2p3.fr
edg-replica-manager starting..
Issuing command : cr
Parameters:
file:/etc/group
-d
clrlcgse01.in2p3.fr
Destination is a host : //clrlcgse01.in2p3.fr
Call replica manager copyAndRegister function
Problem with Storage Resource : clrlcgse01.in2p3.fr
Reason : Accesspoint is not defined for Classic SE : clrlcgse01.in2p3.fr
-----------------------------------------------------------------------------
There is no CE that publishes a GlueCESEBindCEAccesspoint for your SE.
The release documentation explains how to bind a Classic SE to a CE.
|