> I think you are right, it doesn't NEED that info ... but from what I
> have seen with the lcg-* tools, there are several situations in which it
> does not NEED the info, but it does LOOK for the info and fails if it is
> not there. I am not sure this is the case in the example you are
> discussing, but it *is* the case in other situations.
>
> I just looked back in my old mails, and I got it wrong, the case I was
> thinking about was not lcg-cp from a WN, it was lcg-cr to an SE, and was
> failing because the GlueCESEBindCEAccesspoint was not set for the target
> SE. Which is very strange because I was writing directly to the SE, the
> CE is not involved.
>
> lcg-cr --vo atlas -d tbn15.nikhef.nl \
> -l lfn:jeff.tst.3 file:///home/templon/tplinc
>
As I said, if your SE type is SRM1, it doesn't need CESEBind and access
point information, and also it doesn't check information system for it.
But if it found your SE type is disk, it will try to contact information
system to get those information. At least now your SE type is disk,
[dqing@pctwqing]$ ldapsearch -LLL -H ldap://lcg-bdii.cern.ch:2170 -x -b
mds-vo-name=local,o=grid 'GlueSEUniqueID=tbn15.nikhef.nl' GlueSEName dn:
GlueSEUniqueID=tbn15.nikhef.nl,mds-vo-name=nikheflcg2elprod,mds-vo-name=lo
cal,o=grid
GlueSEName: NIKHEF-ELPROD:disk
Di
|