Print

---

Hi,
I have upgraded my rpms and lcg-cr is not complaining any more.

Thanx.

Regards,
Amardeep
----- Original Message -----
From: "Maarten Litmaath" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, August 02, 2005 5:53 PM
Subject: Re: [LCG-ROLLOUT] lcg-cr not working


> Hi,
> I believe you guys started last week from an LCG-2_6_0 "pre-version" with
> an older rpm list including an older YAIM.  Please update the rpm list on
> each node as follows:
>
>      apt-get update && apt-get upgrade
>
> Then rerun the YAIM configuration and your problem ought to be solved.
>
> > Maarten Litmaath wrote:
> >
> >> amardeep_pop wrote:
> >>
> >>> Hello,
> >>>
> >>> I have recently upgraded to LCG-2_6_0 version. and i am running my
> >>> own BDII ( with RB). but when i run lcg-cr command i get the
> >>> following error -
> >>>
> >>> [amardeep@ui amardeep]$ lcg-cr --vo testvo -v  -d se.barc.ernet.in -l
> >>> /grid/testvo/amardeep/myfile file://`pwd`/testjob.sh    Using grid
> >>> catalog type: lfc
> >>> SA Root not found
> >>> lcg_cr: Invalid argument
> >>> This command was running properly in LCG-2_4_0 version. I have
> >>> checked our BDII also the GlueSARoot is published properly in it -
> >>
> >>
> >>
> >> No, it is not.  It should be like this:
> >>
> >> GlueSARoot: testvo:/storage/testvo
> >
> >
> > In fact, it probably should rather be as follows:
> >
> >   GlueSARoot: testvo:testvo
> >
> > The path should be published by a GlueCESEBindSEUniqueID dn:
> >
> >   GlueCESEBindCEAccesspoint: /storage
> >
> >> Did you get warnings/complaints when you ran YAIM?
> >>
> >>> # testvo, se.barc.ernet.in, site-central, local, grid
> >>> dn:
> >>>
GlueSALocalID=testvo,GlueSEUniqueID=se.barc.ernet.in,mds-vo-name=site-cent
> >>>
> >>>  ral,mds-vo-name=local,o=grid
> >>> objectClass: GlueSATop
> >>> objectClass: GlueSA
> >>> objectClass: GlueSAPolicy
> >>> objectClass: GlueSAState
> >>> objectClass: GlueSAAccessControlBase
> >>> objectClass: GlueKey
> >>> objectClass: GlueSchemaVersion
> >>> GlueSARoot: /storage/testvo
> >>> GlueSAPath: /storage/testvo
> >>> GlueSAType: permanent
> >>> GlueSALocalID: testvo
> >>> GlueSAPolicyMaxFileSize: 10000
> >>> GlueSAPolicyMinFileSize: 1
> >>> GlueSAPolicyMaxData: 100
> >>> GlueSAPolicyMaxNumFiles: 10
> >>> GlueSAPolicyMaxPinDuration: 10
> >>> GlueSAPolicyQuota: 0
> >>> GlueSAPolicyFileLifeTime: permanent
> >>> GlueSAStateAvailableSpace: 3605868
> >>> GlueSAStateUsedSpace: 221400
> >>> GlueSAAccessControlBaseRule: testvo
> >>> GlueChunkKey: GlueSEUniqueID=se.barc.ernet.in
> >>> GlueSchemaVersionMajor: 1
> >>> GlueSchemaVersionMinor: 2
> >>> Any Hint where the problem is coming from.
> >>>
> >>> Regards,
> >>> Amardeep
> >>
> >>
> >>
> >>
> >
> >