From the BDII node, these 2 commands work and report good info:
ldapsearch -x -H ldap://lcg-ce01.usatlas.bnl.gov:2135/ -b
mds-vo-name=local,o=grid
ldapsearch -x -H ldap://lcg-se01.usatlas.bnl.gov:2135/ -b
mds-vo-name=local,o=grid
But querying the BDII node with this command doesn't report any
data (see below):
[root@lcg-bdii root]# ldapsearch -x -H ldap://lcg-bdii.usatlas.bnl.gov:2170/
-b mds-vo-name=local,o=grid
version: 2
#
# filter: (objectclass=*)
# requesting: ALL
#
# local, grid
dn: mds-vo-name=local,o=grid
objectClass: GlobusStub
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
I guess it must be a configuration problem but being a novice in LCG I am
having trouble identifying it.... Thanks.
Edward
> -----Original Message-----
> From: LHC Computer Grid - Rollout [mailto:[log in to unmask]]
> On Behalf Of Jiri Kosina
> Sent: Friday, October 22, 2004 2:34 PM
> To: [log in to unmask]
> Subject: Re: [LCG-ROLLOUT] Error testing LCG-2.2.0
>
> On Fri, 22 Oct 2004, Nicolescu, Edward L wrote:
>
> > [testuser@lcg-ui01 bin]$ edg-job-list-match --debug --vo atlas
> testJob.jdl
> > ===================== edg-job-list-match failure ======================
> > No Computing Element matching your job requirements has been found!
> > ======================================================================
>
> This just means, that the resource broker you were querying hasn't found
> any resource which you have specified in the JDL file. Is you resource
> broker configured to use BDII which is aware about your Computing Element?
>
> --
> Jiri Kosina
> Institute of Physics, Academy of sciences of the Czech Republic
|