Hi,
I think this may be the same problem that Santanu saw when he upgraded
(which I also saw) where you need to symlink
/opt/glue/schema/ldap to /opt/glue/schema/openldap-2.0
and restart the globus-mds service.
At the moment I suspect the BDII is running but since the mds's aren't
the bdii has no info to forward.
You'll need to make the symlink on all the nodes that publish through
the BDII, CE, SE, LFC, RB ...
Yours,
Chris.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of David Robson
> Sent: 18 July 2007 14:18
> To: [log in to unmask]
> Subject: Major problems after "upgrading" EFDA-JET
>
> Hi,
>
> We have had major problems after attempting to ipgrade the EFDA-JET
> site, resulting in us failing all SAM tests.
> Some of the problems include
>
> 1) Jobs submitting to the site are failing with "Cannot plan:
> BrokerHelper: no compatible resources", although I
> can globus-job-run to the PBS and fork managers
> 2) Cannot query the CE with ldapsearch -x -H
> ldap://grid002.jet.efda.org:2170 -b
> mds-vo-name=EFDA-JET,o=grid, although
> netstat reports that the bdii-fwd is listening on this port
> 3) Cannot access all files from SE with lcg-cp. e.g.
>
> lcg-cp --vo fusion lfn:/grid/fusion/drobson/edge2d.tgz
> file:`pwd`/edge2d.tgz works
> lcg-cp --vo fusion lfn:/grid/fusion/jet/jacenv.tgz
> file:`pwd`/jacenv.tgz fails
>
> 4) voms search error messages in /var/log/yaimlog (see
> below) somewhat
> reduced when omitting lhcb in configuration
>
> Any help gratefully received
>
> Dave
>
>
> David Robson wrote:
> > After further investigation, it looks like there were
> several problems
> > during configuration.
> > Looking at /var/log/yaimlog, I see the following errors reported ...
> >
> > voms
> >
> search(https://voms.cern.ch:8443/voms/lhcb/services/VOMSCompat
> ibility?method=getGridmapUsers&container=%2Flhcb%2Fsgm%2FRole%
> 3DNULL):
> > Internal Server Error
> > voms
> >
> search(https://voms.cern.ch:8443/voms/lhcb/services/VOMSCompat
> ibility?method=getGridmapUsers&container=%2Flhcb%2Flcgprod%2FR
> ole%3DNULL):
> > Internal Server Error
> > voms
> >
> search(https://voms.cern.ch:8443/voms/lhcb/services/VOMSCompat
> ibility?method=getGridmapUsers&container=%2Flhcb%2Fsgm%2FRole%
> 3DNULL):
> > Internal Server Error
> > voms
> >
> search(https://voms.cern.ch:8443/voms/lhcb/services/VOMSCompat
> ibility?method=getGridmapUsers&container=%2Flhcb%2Flcgprod%2FR
> ole%3DNULL):
> > Internal Server Error
> > voms
> >
> search(https://voms.cern.ch:8443/voms/lhcb/services/VOMSCompat
> ibility?method=getGridmapUsers&container=%2Flh
> >
> >
> > Which presumably means that there is something wrong in my
> > configuration. For lhcb, I have in my
> > site.info
> >
> > VO_LHCB_SW_DIR=/opt/exp_soft/lhcb
> > VO_LHCB_DEFAULT_SE=grid001.jet.efda.org
> > VO_LHCB_STORAGE_DIR=/storage/lhcb
> > VO_LHCB_VOMSES='lhcb lcg-voms.cern.ch 15003
> > /DC=ch/DC=cern/OU=computers/CN=lcg-voms.cern.ch lhcb' 'lhcb
> > voms.cern.ch 15003 /DC=ch/DC=cern/OU=computers/CN=voms.cern.ch lhcb'
> > VO_LHCB_VOMS_EXTRA_MAPS="lcgprod lhcbprod"
> >
> > In groups.conf I have
> >
> > "/VO=lhcb/GROUP=/lhcb/sgm/ROLE=NULL":::sgm:
> > "/VO=lhcb/GROUP=/lhcb/lcgprod/ROLE=NULL":::prd:
> > "/VO=lhcb/GROUP=/lhcb"::::
> >
> > In users.conf I have
> > 12238:lhcb001:1470:lhcb:lhcb::
> > ....
> > 43199:lhcb199:1470:lhcb:lhcb::
> > 43000:lhcbprd:1470:lhcb:lhcb:prd:
> > 18945:lhcbsgm:1470:lhcb:lhcb:sgm:
> >
> > What have I got wrong??
> >
> > Thanks in advance
> >
> > Dave
> >
> >
> > David Robson wrote:
> >> Afer a recent upgrade, we are having PBS problems on our nodes.
> >>
> >> Firstly, after the upgrades, we noticed that pbs_mom wasn't being
> >> started automatically
> >> on the WN nodes, and we had to resort to a manual chkconfig
> >>
> >> Secondly,
> >>
> >> Most groups cannot submit from the CE. The error is "qsub:
> >> Unauthorized Request"
> >> This seems to fail for the ops, atlas and fusion VOs, but
> works for
> >> dteam.
> >>
> >> I suspect something with the GROUP_ENABLE variables, but can't see
> >> anything wrong.
> >> At the moment. we have ...
> >>
> >> FUSION_GROUP_ENABLE="fusion"
> >> ALICE_GROUP_ENABLE="alice /VO=alice/GROUP=/alice/ROLE=lcgadmin
> >> /VO=alice/GROUP=/alice/ROLE=production"
> >> ATLAS_GROUP_ENABLE="atlas /VO=atlas/GROUP=/atlas/ROLE=lcgadmin
> >> /VO=atlas/GROUP=/atlas/ROLE=production"
> >> BIOMED_GROUP_ENABLE="biomed /VO=biomed/GROUP=/biomed/ROLE=lcgadmin
> >> /VO=biomed/GROUP=/biomed/ROLE=production"
> >> CMS_GROUP_ENABLE="cms /VO=cms/GROUP=/cms/ROLE=lcgadmin
> >> /VO=cms/GROUP=/cms/ROLE=production"
> >> DTEAM_GROUP_ENABLE="dteam /VO=dteam/GROUP=/dteam/ROLE=lcgadmin
> >> /VO=dteam/GROUP=/dteam/ROLE=production"
> >> LHCB_GROUP_ENABLE="lhcb /VO=lhcb/GROUP=/lhcb/sgm
> >> /VO=lhcb/GROUP=/lhcb/lcgprod"
> >> OPS_GROUP_ENABLE="ops /VO=ops/GROUP=/ops/ROLE=lcgadmin"
> >>
> >> Any help welcome,
> >>
> >> thanks
> >>
> >> Dave
> >>
> >
>
|