Hi Jeremy, all,
It could also be related to wrong mapfile config. See the three
parts LCG broadcast "LHCb VOMS Mapping" or in summary, one should
have in groups.conf:
for YAIM >= 3.0.1
"/VO=lhcb/GROUP=/lhcb/sgm":::sgm:
"/VO=lhcb/GROUP=/lhcb/lcgprod":::prd:
"/VO=lhcb/GROUP=/lhcb"::::
OR for YAIM < 3.0.1
"/VO=lhcb/GROUP=/lhcb/sgm/ROLE=NULL":::sgm:
"/VO=lhcb/GROUP=/lhcb/lcgprod/ROLE=NULL":::prd:
"/VO=lhcb/GROUP=/lhcb"::::
Note that the default setting in yaim is:
"/VO=lhcb/GROUP=/lhcb/ROLE=lcgadmin":::sgm:
"/VO=lhcb/GROUP=/lhcb/ROLE=production":::prd:
"/VO=lhcb/GROUP=/lhcb"::::
But, I may well have got it wrong :(
Yves
On Tue, 12 Jun 2007, Coles, J (Jeremy) wrote:
> Dear All
>
> LHCb are starting another major production run and this is a chance to
> see much higher utilisation of resources. Unfortunately there appear to
> be many sites where the software manager is unable to install the latest
> LHCb software. This *might* be related to the CA certificate version
> installed. If anyone can verify this or share the actual explanation
> please respond to this list. It seems sensible to check this on
> TB-SUPPORT before LHCb raises tickets against sites.
>
> Many thanks,
> Jeremy
>
|